Release <2012-10> SAP HR Slovenia (HR-SI) Gross Payroll Customizing Documentation CUSTOMER Document Version: 1.0 – October 22, 2012
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Release <2012-10>
SAP HR Slovenia (HR-SI)
Gross Payroll
Customizing Documentation
CUSTOMER
Document Version: 1.0 – October 22, 2012
Copyright© Copyright 2012 SAP AG. All rights reserved.
SAP Library document classification: PUBLIC
No part of this publication may be reproduced or transmitted in any form or for any purposewithout the express permission of SAP AG. The information contained herein may bechanged without prior notice.
No part of this publication may be reproduced or transmitted in any form or for any purposewithout the express permission of SAP AG. The information contained herein may bechanged without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietarysoftware components of other software vendors.
Microsoft, Windows, Excel, Outlook, PowerPoint, Silverlight, and Visual Studio are registeredtrademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x,System z, System z10, z10, z/VM, z/OS, OS/390, zEnterprise, PowerVM, Power Architecture,Power Systems, POWER7, POWER6+, POWER6, POWER, PowerHA, pureScale, PowerPC,BladeCenter, System Storage, Storwize, XIV, GPFS, HACMP, RETAIN, DB2 Connect, RACF,Redbooks, OS/2, AIX, Intelligent Miner, WebSphere, Tivoli, Informix, and Smarter Planet aretrademarks or registered trademarks of IBM Corporation.
Linux is the registered trademark of Linus Torvalds in the United States and other countries.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are trademarks or registeredtrademarks of Adobe Systems Incorporated in the United States and other countries.
Oracle and Java are registered trademarks of Oracle and its affiliates.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin aretrademarks or registered trademarks of Citrix Systems Inc.
HTML, XML, XHTML, and W3C are trademarks or registered trademarks of W3C®, WorldWide Web Consortium, Massachusetts Institute of Technology.
Apple, App Store, iBooks, iPad, iPhone, iPhoto, iPod, iTunes, Multi-Touch, Objective-C,Retina, Safari, Siri, and Xcode are trademarks or registered trademarks of Apple Inc.
IOS is a registered trademark of Cisco Systems Inc.
RIM, BlackBerry, BBM, BlackBerry Curve, BlackBerry Bold, BlackBerry Pearl, BlackBerryTorch, BlackBerry Storm, BlackBerry Storm2, BlackBerry PlayBook, and BlackBerry AppWorld are trademarks or registered trademarks of Research in Motion Limited.
Google App Engine, Google Apps, Google Checkout, Google Data API, Google Maps,Google Mobile Ads, Google Mobile Updater, Google Mobile, Google Store, Google Sync,Google Updater, Google Voice, Google Mail, Gmail, YouTube, Dalvik and Android aretrademarks or registered trademarks of Google Inc.
INTERMEC is a registered trademark of Intermec Technologies Corporation.
Wi-Fi is a registered trademark of Wi-Fi Alliance.
Bluetooth is a registered trademark of Bluetooth SIG Inc.
Motorola is a registered trademark of Motorola Trademark Holdings LLC.
Computop is a registered trademark of Computop Wirtschaftsinformatik GmbH.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer,StreamWork, SAP HANA, and other SAP products and services mentioned herein as well astheir respective logos are trademarks or registered trademarks of SAP AG in Germany andother countries.
Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, CrystalDecisions, Web Intelligence, Xcelsius, and other Business Objects products and servicesmentioned herein as well as their respective logos are trademarks or registered trademarks ofBusiness Objects Software Ltd. Business Objects is an SAP company.
Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybaseproducts and services mentioned herein as well as their respective logos are trademarks orregistered trademarks of Sybase Inc. Sybase is an SAP company.
Crossgate, m@gic EDDY, B2B 360°, and B2B 360° Services are registered trademarks ofCrossgate AG in Germany and other countries. Crossgate is an SAP company.
All other product and service names mentioned are the trademarks of their respectivecompanies. Data contained in this document serves informational purposes only. Nationalproduct specifications may vary.
These materials are subject to change without notice. These materials are provided by SAPAG and its affiliated companies ("SAP Group") for informational purposes only, withoutrepresentation or warranty of any kind, and SAP Group shall not be liable for errors oromissions with respect to the materials. The only warranties for SAP Group products andservices are those that are set forth in the express warranty statements accompanying suchproducts and services, if any. Nothing herein should be construed as constituting anadditional warranty.
Icons in Body TextIcon Meaning
Caution
Example
Note
Recommendation
Syntax
Additional icons are used in SAP Library documentation to help you identify different types ofinformation at a glance. For more information, see Help on Help General InformationClasses and Information Classes for Business Information Warehouse on the first page of anyversion of SAP Library.
Typographic ConventionsType Style Description
Example text Words or characters quoted from the screen. These include field names, screentitles, pushbuttons labels, menu names, menu paths, and menu options.
Cross-references to other documentation.
Example text Emphasized words or phrases in body text, graphic titles, and table titles.
EXAMPLE TEXT Technical names of system objects. These include report names, programnames, transaction codes, table names, and key concepts of a programminglanguage when they are surrounded by body text, for example, SELECT andINCLUDE.
Example text Output on the screen. This includes file and directory names and their paths,messages, names of variables and parameters, source text, and names ofinstallation, upgrade and database tools.
Example text Exact user entry. These are words or characters that you enter in the systemexactly as they appear in the documentation.
<Example text> Variable user entry. Angle brackets indicate that you replace these words andcharacters with appropriate entries to make entries in the system.
EXAMPLE TEXT Keys on the keyboard, for example, F2 or ENTER.
1. Purpose and scope of this document .............................................................................. 7
2. Indirect Valuation Modules ............................................................................................. 8
2.1. 62POI Number of points .......................................................................................... 8
2.2. 62PTS Value of point............................................................................................... 8
2.3. 62TAH Tarif – hourly ............................................................................................... 9
2.4. 62TAM Tarif – monthly ............................................................................................ 9
2.5. 62YRS Working age bonus – on the first day in month ............................................. 9
2.6. 62YRL Working age bonus – on the last day in month ........................................... 10
3. Valuation bases ............................................................................................................ 11
3.1. Valuation bases from infotype 0008 ....................................................................... 11
3.2. Valuation bases from previous periods .................................................................. 11
3.3. Special valuation bases ......................................................................................... 12
4. Cumulations ................................................................................................................. 13
4.1. Obligatory SAP standard cumulations .................................................................... 13
4.2. Bases for social insurance paid by EE and sent to authorities ................................ 13
4.3. Bases for social insurance paid by EE and not sent to authorities .......................... 13
4.4. Bases for social insurance paid by ER – standard contracts................................... 13
4.5. Bases for social insurance paid by ER – special contracts ..................................... 14
4.6. Bases for tax paid by EE – standard contracts ....................................................... 14
4.7. Bases for tax paid by EE – special contracts .......................................................... 14
4.8. Bases for tax paid by ER – standard contracts ....................................................... 14
4.9. Bases for tax paid by ER – special contracts ......................................................... 14
4.10. Obsolete cumulations......................................................................................... 15
5. Template wage types ................................................................................................... 16
5.1. M001, M00A Number of points – infotype 0008 ...................................................... 16
5.2. M002 – M005 Value of point – infotype 0008 ......................................................... 16
5.3. M010, M020, M030, M040 and M050 Monthly basic pay – infotype 0008 ............... 16
5.4. M015, M025, M035, M045 and M055 Hourly basic pay – infotype 0008 ................. 17
5.4.1. M045 Working years bonus H..................................................................... 17
5.5. M060 Students ...................................................................................................... 17
5.6. M080 Difference in pay - court order and M081 Difference in regres - court order .. 17
5.7. M097 13th salary – disabled employee ................................................................... 18
5.8. M099 Annual bonus 13th salary............................................................................. 18
5.9. M120 Public Holiday NotWorked ........................................................................... 18
5.10. Wage types for absences ................................................................................... 18
5.11. M160 – M175 Illnesses paid by company ........................................................... 19
5.12. M500 - M528 Illnesses refunded ........................................................................ 19
5.13. M180, M195 Overtime (basic pay part and bonus part) ....................................... 19
5.14. M1A0 – M1A4 Part-time illnesses – automatic split ............................................. 19
5.15. M400 Vacation compensation ............................................................................ 20
5.16. M430 – M435 Regres......................................................................................... 20
5.17. M580 Disability - compensation .......................................................................... 20
5.18. M600 – M610 Reimbursement for food and transport to work ............................. 21
5.19. M610 – M644, M310 – M344 Netto/Brutto wage types........................................ 21
5.19.1. M620 Separate living .................................................................................. 21
5.19.2. M625 Solidarity help (death of employee) ................................................... 21
5.19.3. M626 Solidarity help (others) ...................................................................... 22
5.19.4. M630 Compensation for pension ................................................................ 22
5.19.5. M641 – M644 Jubilee awards ..................................................................... 22
5.20. M650 Voluntary pension insurance (contribution of company) ............................ 22
5.21. M440 – M443 Participation in company profit ..................................................... 22
5.22. Gross wage types without social insurances ....................................................... 23
5.23. M700 Arrangement for authors BRUTTO ........................................................... 23
5.24. M701 Arrangement for authors NETTO .............................................................. 23
5.25. M755, M756 Students working directly without agency ....................................... 23
5.26. MJ* Travel expenses.......................................................................................... 23
5.27. MJ1A TE: km ..................................................................................................... 24
6. Absence types .............................................................................................................. 25
6.1. 0100 Vacation ....................................................................................................... 29
6.2. 0200, 0210, 0220, 0230 and 0235 Illnesses ........................................................... 29
6.3. 0300 - 0345 Casual leaves .................................................................................... 29
6.4. 0370 Blood donation.............................................................................................. 29
6.5. COMx Compensation of illness .............................................................................. 30
7. Processing of absences................................................................................................ 31
7.1. Illnesses customizing and calculation .................................................................... 31
7.1.1. Customizing of illnesses’ split ..................................................................... 31
7.2. Blood donation customizing and calculation ........................................................... 33
7.3. Part-time absences in infotype 2001 ...................................................................... 33
7.4. Part-time absences in infotype 0014 – alternative method ...................................... 34
7.5. Average from previous month as hourly rate for absences ..................................... 34
7.6. Average from previous year as hourly rate for refunded illnesses ........................... 35
7.6.1. Hourly rate calculation - /0I0 and /0I1.......................................................... 35
7.6.2. Revalorization index ................................................................................... 37
7.6.3. Check of resulting hourly rate ..................................................................... 39
8. Voluntary pension insurance (PDPZ) ............................................................................ 40
8.1. Customizing of PDPZ ............................................................................................ 41
1. Purpose and scope of this document
This document describes gross payroll calculation process: basic pay is read, valuation basesare calculated, all time wage types are valuated, additional payments are imported andprocessed.
Document concentrates on technical design and customizing instructions. Various methods ofbasic pay calculation are explained through indirect valuation modules and samplecustomizing. Valuation bases are listed, as well as cumulations used for various bases (i.e.social insurances, taxes). Model wage types are described - their purpose, functionality andsettings. At the end, absence types and their processing are explained.
2. Indirect Valuation Modules
Indirect valuation modules can be used for wage types used in infotype 0008 to get somevalues calculated dynamically from customizing and other wage types, in contrast to enteringvalues into each wage type directly in infotype 0008.
Indirect modules can be used for wage types used in infotype 0008 only. You can find theimplementation of individual modules iwith SE19, where the “Implementation name” iscomposed from “HR_IV_”+ the name of the module.
2.1. 62POI Number of points
Module 62POI seeks infotype 1050 related to employee’s current position (P0001-PLANS)and the subtype equal to wage type being valuated (eg. M00A). If such entry exists, thenumber of points is read from there, from field EVPTS.
If such entry does not exist, the module seeks infotype 1050 related to employee’s current job(P0001-STELL) and the subtype equal to wage type being valuated (eg. M00A). If such entryexists, the number of points is read from there, from field EVPTS.Module variant ' 'Number of points is stored into AMT field of valuated wage type.Module variant 'A'Value coming from infotype 1050 is divided by 100 and stored into AMT field of valuatedwage type.Module variant 'B'Number of points is stored into NUM field of valuated wage type.Module variant 'C'Value coming from infotype 1050 is divided by 100 and stored into NUM field of valuatedwage type.
2.2. 62PTS Value of point
Module 62PTS seeks T7SITA table for valid value of one point and stores it into amount fieldof valuated wage type. T7SITA can hold value of one point for various basic pay calculationmethods, which represent maluation module’s variants:
A: Basic Pay – monthly paymentB: Basic Pay – hourly paymentC: Bonus/Stimulation – monthly paymentD: Bonus/Stimulation – hourly payment
Module 62PTS seeks T7SITA table for:
MOLGA = employee’s molga GRPV1 = Employee subgroup grouping for point values defined in V_T7SI03 – used only
if it is needed (otherwise blank) GRPV2 = Personal subarea grouping for point values defined in V_T7SI01P – used only
if it is needed (otherwise blank) PTTYP = module variant of the wage type which is being evaluated (T511-MOD03) TRFAR = pay scale type of the employee (P0008-TRFAR)
The value of point is stored into AMT field of the wage type.
2.3. 62TAH Tarif – hourly
Module 62TAH multiplies values of wage types defined in table T539J.
Example:Wage type M015 is valuated with 62TAH. Table T539J is customized as follows:
62TAH 62 M015 01 M001 100,0062TAH 62 M015 02 M004 100,0062TAH 62 M015 03 M00A 100,00
Wage types M001, M004 and M00A are read from infotype 0008 and multiplied; multiplicationtakes place only if those wage types exist in infotype 0008. Percentage in T539J (used inmodules PRZNT, SUMME, etc.) is used during multiplication.
The result is stored into AMT field of the wage type M015.
2.4. 62TAM Tarif – monthly
Module 62TAM multiplies values of wage types defined in table T539J.
ExampleWage type M010 is valuated with 62TAM. Table T539J is customized as follows:
62TAM 62 M010 01 M001 100,0062TAM 62 M010 02 M002 100,0062TAM 62 M010 03 M00A 100,00
Wage types M001, M002 and M00A are read from infotype 0008 and multiplied; multiplicationtakes place only if those wage types exist in infotype 0008. Percentage in T539J (used inmodules PRZNT, SUMME, etc.) is used during the multiplication.
The result is stored into AMT field of the wage type M010.
2.5. 62YRS Working age bonus – on the first day in month
Module 62YRS calculates all possible types of working age for employee. Calculation takesplace on the FIRST day of payroll period, result is number of years, months and days. Modulethen tries to find appropriate percentage in customizing table T7SIWA and calculates amountfor working age bonus.
Valuation has 2 steps:
1. Finding the right percentage for the employee’s current working ageModule calculates all possible working ages for employee on the FIRST day of accountedperiod (accounted period is WPBP split). The decision “which working age is to be used” isgiven in customizing table T7SIWA. Module tries to find appropriate records in this table for allworking age types. Several wage types can be customized and used, each can read differenttype of working age = different line in infotype 0605. Module seeks the T7SIWA table for: GRAG1 = Employee subgroup grouping for working age bonus defined in V_T7SI03 –
used only if it is needed (otherwise blank) GRAG2 = Personal subarea grouping for working age bonus defined in V_T7SI01P –
used only if it is needed (otherwise blank) LGART = Wage type which is being valuated DURTY = Type of working age GENDE = Gender of employee YRSLO = Years of working age - Lower limit YRSHI = Years of working age - Upper limit
Result – percentage for working age - is saved into NUM field of valuated wage type ininfotype 0008. From here on, valuation is done the same way as percentage would bemanualy entered into field NUMBER.
2. Finding the base and applying the percentage
Standard indirect evaluation module PRZNT is called => in T539J base for wage type isdefined (base = M010):
PRZNT 62 M040 01 M010 100,00
Example for two working age types:
Wage type XXXX uses 62YRS and should take 1st grey line of infotype 0605 (delovna dobapo zadnjem vstopu).
Wage type YYYY uses 62YRS and should take 4th grey line of infotype 0605 (skupnadelovna doba).
In table T7SIWA following key areas must be created:LGART DURTY YRSLO YRSHI WARESXXXX 01 00 01 value...XXXX 01 01 02 value...YYYY 04 00 01 value...YYYY 04 01 02 value...
Even if wage type is not specified in T7SIWA table, indirect module 62YRS works without it.
Sample customizing in T7SIWA table
2.6. 62YRL Working age bonus – on the last day in month
Another indirect valuation module 62YRL is available. It is identical to the 62YRS module butthe working age is calculated to the LAST day of the accounted period (compared to theFIRST day used by 62YRS).
3. Valuation bases
Valuation is a process in which gross wage type obtains its value - amount in EUR.Calculated amount directly depends on valuation base, which in general is hourly rate.Valuation base can be calculated from various sources, for example from basic pay or fromprevious payroll periods.
Calculation of valuation bases takes place in the beginning of gross payroll calculation.Resulting valuation base amounts are stored in wage types /0*.
Infotype 0008 - modules for indirect valuations are used - no other valuation bases areneeded.
Infotypes 0015, 2010 - if an amount is entered, no valuation base is needed.
Other wage types (from 0015, 0014, 2010, 2001 …), which have only hours or days, have tobe multiplied by appropriate valuation base => this is the task of this step.
Valuation base is a technical wage type starting with "/0", used in X015 rule, operation VALBSand referred in T512W.
3.1. Valuation bases from infotype 0008
Following wage types hold valuation bases, calculated from basic pay:
/001 all wage types from infotype 0008 that have amount – used generally/002 only basic pay from infotype 0008 (M010, M015) – used generally/003 comparison base for illness valuation – maximum hourly rate (“as if worked”).Which wage type from IT0008 is included into which valuation bases depend on processingclass 01. described in Processing class: 01 Assignment to valuation bases in “SIC1000_ENPayroll in SAP System.pdf”.
Processing is performed in schema SIT0, rules SI10, SI13, SI14 and SI15.
Rule SI10 loops at IT table, summarizes relevant wage types and creates /001 … /003. Rule SI13 divides (for monthly EE only) summarized values by hours from infotype 8. Rule SI14 divides (for monthly EE only) wage types (processing class 10, value "B" -
customer copies of M010, M020, etc) values by hours from infotype 8. Before the divisionthe AMT is multiplied with 100 for increased precision.
Rule SI15 divides AMT and RTE of monthly wage types with 100 (to conclude theprecision from rule SI14).
Recommendation
If you need to use algorithm for SAP default monthly salary, you must perform followingsetup:
Wage types /001, /002, /003 - processing class 01, value "B" is to be changed to "A". Wage types M010, M020, M030, M050 - processing class 10, value "B" is to be changed
to "1" Wage types M040 - processing class 10, value "B" is to be changed to "2" Generation of M010, M020, M030, M040, and M050 wage types should be stopped in
T510S. No changes in schema are needed
3.2. Valuation bases from previous periods
Following wage types hold valuation bases, calculated from previous payroll period(s):
/0H0 average for holidays compensation - from previous month/0I0 average for refunded illnesses - from previous calendar year increased by inflation For
more information about Illnesses see Illnesses customizing and calculation in“SIC3000_EN Gross Payroll.pdf”.)
/0I1 average for current illness - used for proper calculation of illness, consideringrevalorization indexes.
3.3. Special valuation bases
Following wage type holds valuation bases, calculated from some other wage types in currectpayroll period:/004 base for disability refundation (disabled persons)
This base is used only for wage type M580 (and its copies). The base cannot be calculated intime schema SIT0 like other bases because wage types from infotype 0014/0015 must beincluded into the base, too. This is also the reason, why time wage types may not be sent toRT table yet at the end of time schema SIT0. They must remain in IT table until valuation ofdisability takes place.
Calculation of the base is performed in schema SIAL and subschema SIIN in rules SIC4,SIC7 and SIC8. Wage types in IT tables are processed in the rule according the value ofprocessing class 61.1 AMT of the wage type is included into the base2 NUM of the wage type is included into the base3 NUM and AMT of the wage type is included into the baseAfter this rule, wage type /004 contains:AMT amount of disability compensationNUM hours of disability compensationCalculation of M580 follows immediately, in rule SIC5.
4. Cumulations
Cumulations are interface between gross and net processing. No other wage types shouldflow into net payroll processing except cumulations. Cumulations are used for example asinsurance base or tax base and are stored as numbers and amounts in wage types /1*.
For calculation see Overview of net calculation in “SIC4000_EN Net Payroll.pdf” and theCumulations in “SID3000_EN Gross Payroll.pdf”.
Recommendation
Template wage types have been customized to be included into right cumulations. Despitethis, prior testing and go-live, we strongly recommend to review the cumulations of allcustomer wage types; reports RPDLGA20 or HSIU512W can be used as a tool. Performreview together with customer specialist! Errors of this type (for example, wage type ismissing in cumulation of tax base) cannot be corrected retroactively.
4.1. Obligatory SAP standard cumulations
/101 brutto amount: consists of wage types representing general employee’s gross salary.They flow into final payment for employee and amount is subject of taxation. In mostcases, these wage types’ amount is subject also for social insurance (SI) calculation
/110 netto amount: consists of various wage types, which are not subject of tax or SI.
4.2. Bases for social insurance paid by EE and sent to authorities
Most of wage types contribute to all social insurance bases; however, there are someexceptions, which do not. That's why separate cumulation is required for each socialinsurance base./111 Health insurance/112 Pension and disability insurance/113 Employment insurance/114 Maternity insurance
4.3. Bases for social insurance paid by EE and not sent to authorities
Various wage types, for example employee’s disability, are refunded by authorities and aresubject of social insurance calculation. To prevent double money flow, insurances for suchwage tpes are deducted from EE's salary but not sent to authorities’ bank account. Suchamounts must be reported separately on reports and in files./121 Health insurance/122 Pension and disability insurance/123 Employment insurance/124 Maternity insurance
4.4. Bases for social insurance paid by ER – standard contracts
Wage types, contributing to bases for social insurance charged to employee, in generalcompose also bases for social insurance charged to employer. Base for each socialinsurance is stored in separate wage type.
/131 Health insurance/132 Pension and disability insurance/133 Employment insurance/134 Maternity insurance/135 Injuries at work insurance/136 Beneficial insurance (only for employees with beneficial working age in infotype 0605)
4.5. Bases for social insurance paid by ER – special contracts
Bases of respective social insurances for special contractors are stored in following wagetypes:
/161 PD Special work contract - Health insurance/162 PD Special work contract - Pension insurance/163 Comitee attendance fee – Pension insurance/165 Apprentice – Health insurance/166 Apprentice 1st class – Pension insurance/167 Apprentice 2nd class – Pension insurance/168 Apprentice 3rd class – Pension insurance/169 Students – Pension Insurance
4.6. Bases for tax paid by EE – standard contracts
Bases for respective tax charged to employee are stored in following wage types:
/141 Income tax/142 Average tax
4.7. Bases for tax paid by EE – special contracts
Bases for respective tax charged to special contractors are stored in following wage types:
/171 Authors (APD)/172 Arrangement for work (PD)/173 Comitee attendance fee/174 Sponzorship/175 Rent without equipment (“oprema“)/176 Rent with equipment (“oprema“)/177 Rent of a land/178 Other income/179 Costs refund
4.8. Bases for tax paid by ER – standard contracts
From year 2009 this tax is discontinued; none the less, cumulation is still calculated andstored in the system. The tax is disabled by setting its rate to zero in customizing tableT7SIST.
/151 DIP - tax on paid salaries
4.9. Bases for tax paid by ER – special contracts
For special contracts, base for tax charged to employer is stored in following wage types:
/152 PD – tax from arrangements
/153 SP – tax from sponsorship
4.10. Obsolete cumulations
/102 minimal wage comparison base.
Wage type /102 was used in former releases, but is not used anymore, neither it is preparedin payroll. Solution for minimal wage calculation was moved to averages /203 and /204.
5. Template wage typesSettings overview of template wage types is provided with HSIU512W report. Wage types notdescribed in next chapter do not have any special functional features and thus they are notdescribed in more details. However, you still have to pay attention to proper assignment ofthese wage types to processing classes and cumulations – to achieve proper calculation ofinsurances, taxes, influence to averages etc.
Caution
It is important to follow standard SAP procedure and always copy template wage types tocustomer name range.
5.1. M001, M00A Number of points – infotype 0008
Use wage type M001 for employees, whose number of points cannot be read fromposition/job using module 62POI described in 62POI Number of points in “SIC3000_EN GrossPayroll.pdf” or when you want to have the possibility to overwrite number of points fromposition/job.
Use wage type M00A for employees whose number of points is always read from position/jobwithout exceptions.
5.2. M002 – M005 Value of point – infotype 0008
Value of point (wage types M002, M003, M004 and/or M005) is used in infotype 0008 to getthe amount for multiplication with number of points. This technic is used to accommodate thegeneral business practice in Slovenia where the basic pay and company bonus are calculatedfrom customizing and other wage types.
To get the amount in those wagetypes the indirect valuation mudule 62PTS is used. For moreinformation about this module see 62PTS Value of point in “SIC3000_EN Gross Payroll.pdf”.
5.3. M010, M020, M030, M040 and M050 Monthly basic pay – infotype 0008
Template monthly wage types stored in infotype 0008 (M010, M020, M030, M040, M050) aredesigned to contain monthly values. According to common business practice in Sloveniathose are divided by hours in infotype 8 and multiplied by hours coming from time evaluation(table ZL, generated in T510S or entered in P2010).
If you need to use SAP default monthly salary algorithm (monthly value divided by plannedhours of particular month and multiplied by really worked hours), you must perform setupdescribed in Valuation bases from infotype 0008 in “SIC3000_EN Gross Payroll.pdf”.
Note
Some of those wage types use Slovenian indirect valuation modules that are described inmore detail in Indirect Valuation Modules in “SIC3000_EN Gross Payroll.pdf”.
Wage type M010 uses indirect valuation module 62TAM described in 62TAM Tarif –monthly in document “SIC3000_EN Gross Payroll.pdf”.
Wage type M040 uses indirect valuation module 62YRS or 62YRL both described in62YRS Working age bonus – on the first day in month in document “SIC3000_ENGross Payroll.pdf”.
5.4. M015, M025, M035, M045 and M055 Hourly basic pay – infotype 0008
Template hourly wage types stored in infotype 0008 (M010, M020, M030, M040, M050) aredesigned to contain hourly values. Those values are normaly multiplied by hours coming fromtime evaluation (table ZL, generated in T510S or entered in P2010).
Note
Some of those wage types use Slovenian indirect valuation modules that are described inmore detail in Indirect Valuation Modules in document “SIC3000_EN Gross Payroll.pdf”.
Wage type M015 uses the indirect valuation module 62TAH described in 62TAH Tarif– hourly in document “SIC3000_EN Gross Payroll.pdf”..
Wage type M045 uses the indirect valuation module 62YRS or 62YRL both describedin 62YRS Working age bonus – on the first day in month in document “SIC3000_ENGross Payroll.pdf”.
5.4.1. M045 Working years bonus H
Wage type M045 has monthly character despite it is used for hourly wages. The hourly valueis multiplied by planned hours of employee reduced by hours of public holidays and strike.Rule SIOA (schema SIAP).
To calculate the percentage for working age, indirect valuation module 62YRS or 62YRL isused. For more information about those two modules see 62YRS Working age bonus – on thefirst day in month in “SIC3000_EN Gross Payroll.pdf”.
5.5. M060 Students
Wage type is prepared to hold hourly rate in infotype 0008 for students, working via student’sagency. Work schedule is set to FREE – which causes no generation of time wage types innegative time recording. If customer wants to generate time wage types, it is necessary eitherto:A enter substitution record in infotype 2003 + WT generation in T510S set unconditionality
(if substitution exists, all must be paid with no other condition)B enter hours with time wage types in infotype 2010C do generation via T510S on time management side (schema TC00) if time evaluation is
active.
5.6. M080 Difference in pay - court order and M081 Difference in regres - court order
These two wage types are special types of payment that is required to properly report courtorders to the REK-1 report. The key here is that these types of payments are tipically paid forprevious years and in some cases require averaging for REK-1 report.
Wage type M080 has value Q in evaluation class 09 (=assignment for REK-1 legal report)and wage type M081 has value R.
Note
Special note on usage of these wage types in REK-1 report, to fill fields payment period(REK-1 field 011) and averaging (REK-1 field 010a):
When payment refers to one year, enter it in form of MM.YYYY into field ZUORD(Stevilka dodelitve) in corresponding infotype record
When payment refers to more than one year, enter start and end year in form ofMM.YYYY - MM.ZZZZ into field ZUORD (Stevilka dodelitve) in corresponding infotyperecord
When payment refers to more than one year, averaging is automaticaly turned on and field010a is filled with value Da. Each payment from one of these wage types will be reported oncorresponding REK-1 income type.
5.7. M097 13th salary – disabled employee
This wage type is prepared to calculate annual bonus for disabled employees.
Use: Prepare input data for annual bonus (13th pay) for non-disabled and disabled persons.Use wage type for disabled persons based on model M097 (EVCLS 09='JC').
Wage type can be used within either regular or off-cycle run.
5.8. M099 Annual bonus 13th salary
This wage type is prepared to calculate annual bonus for non-disabled employees.
Use: Prepare input data for annual bonus (13th pay) for non-disabled and disabled persons.Use wage type for non-disabled persons based on model M099 (EVCLS 09='J').
Wage type can be used within either regular or off-cycle run.
5.9. M120 Public Holiday NotWorked
When working day falls on public holiday, wage type is (as a template) generated from workschedule automatically as secondary wage type of /844. During implementation, model wagetype M120 in valuation base of /844 should be replaced by customer wage type.
Generation rule in T510S:
DWS class > 0 (there are planned hours) PH class > 0 (it is a public holiday) Day Type = 1 (EE should not work even if it is PH) Other restrictions should not be used
If employee comes to work that day, wage type will be generated anyway (at least in negativetime evaluation). In that case manual correction (in hours) via 2010 must be done.
By default, M120 uses monthly average /0H0 as hourly rate, as written in valuation base of/844.
5.10. Wage types for absences
All wage types for absences are created automatically from absences recorded in infotype2001. These are following model wage types:
M110 Waiting for work
M102 Trade union work
M104 Employee’s council
M115 Non-paid absence
M116 Unallowed absence
M131 Vacation - previous year
M130 Vacation - current year
M140 Casual paid leave
M158 Suspension
M156 Strike
5.11. M160 – M175 Illnesses paid by company
These wage types are created automatically from absences.
The whole calculation of illnesses is described in Processing of absences in “SIC3000_ENGross Payroll.pdf”.
5.12. M500 - M528 Illnesses refunded
These wage types are created automatically from absences.
The whole calculation of illnesses is described in Processing of absences in document“SIC3000_EN Gross Payroll.pdf”.
5.13. M180, M195 Overtime (basic pay part and bonus part)
Wage type M180 is used to hold overtime hours in negative time recording. In valuationphase it gets rate for regular hours and secondary wage type M195 with bonus for overtimeis created.
5.14. M1A0 – M1A4 Part-time illnesses – automatic split
Note
Solution, described here, was replaced by solution to enter the part time illnesses in IT 2001the same way as full time illnesses. The older solution stays in place for customers that haveimplemented it. The whole current calculation of illnesses is described in Illnessescustomizing and calculation in “SIC3000_EN Gross Payroll.pdf”.
The wage types M1A0 to M1A4 are special wage types taking care of automatic split of part-time illnesses from company-paid to refunded after certain number of days.
M1A0 Bolezen (do/nad) -> Illness (below/above) => M160/M500
M1A1 Bolezen z dela (do/nad) -> Professional illness (below/above) =>M162/M502
M1A2 Pošk.na delu (do/nad) -> Injury at work (below/above) =>M165/M505
M1A3 Pošk.izv.dela (do/nad) -> Injury out of work (below/above) =>M170/M510
M1A4 Pošk.izv.dela 3.os.(do/nad) -> Injury out of work 3rd person (below/above) =>M175/M517
If an employee is on a part-time illness, infotype 0007 is set to percentage lower than 100%,corresponding to actual worked hours. At the same time, one of above wage types should beentered into infotype 0014 with following data:
BEGDA = first day of part-time illness
ENDDA = end of the part-time illness
Number/unit = number of hours per day to be paid as illness
Assignment number (ZUORD) = actual start of illness if earlier than BEGDA in formatDD.MM.YYYY or DDMMYYYY. This date is important for evaluation which averageshould be used for illness. If this date lies in current month, average /0I0 is used. If it liesin previous months, /0I1 (average of long-lasting illness) is used instead.
5.15. M400 Vacation compensation
To compensate vacation quotas (infotype 2006) with influence to remaining quota, specialinfotype 0416 must be used. Enter date and number of vacation units (=days) to becompensated. However, there is no place to enter number of months to which compensationrelates; it is required for tax calculation. Therefore, number of months is calculatedautomatically in SIOT rule by following formula:
Number of months = ((Hours of compensation / Daily Hours) / Constant LVCOM) * 12Example
Daily hours = 8, Hours of compensation = 40
Number of months = ((40 / 8) / 22) * 12 = 2,77 month
Constant LVCOM defines average number of workdays per month to be used for thiscalculation.
Daily hours are taken from infotype 0007
Wage type M400 is created from infotype 0416 with standard payroll function P0416 inschema SIT0.
5.16. M430 – M435 Regres
These wage types are used for payment of regres (=recourse). It can be paid either in regularor off-cycle payroll. Enter wage type amount as well as number of months, on which paymentrelates. It is important for taxation – see description of average tax in net Payroll document.
Wage type M430 is subject of taxation only (average tax), M432 and M434 are also subject ofsocial insurances.
There is no automation provided for splitting entered value into 3 types of regres payments.Wage types are included into SI and tax bases with amount of input wage type and exactlyaccording to wage type customizing.
In current version, no automation is provided for partial payments of regres during thecalendar year either.
M435 is model wage type for calculating regres without social insurances. It is reported onREK-1 income type 1089 (see SAP note 1294588).
5.17. M580 Disability - compensation
To calculate the compensation for part time employment of disabled employees you have toenter percentage of working time spent on work in infotype 0007 and enter record in infotype0014 (customer copy of wage type M580) with starting and ending date of the compensation.This ensures full working age calculation.
Payroll program calculates the difference between employee’s reduced daily hours (frominfotype 0007) and daily hours for full time (of the same work schedule). This difference is putfor each working day as number of hours into wage type, coming from infotype 0014.
Employee may receive disability compensation directly from the insurance company (meaningpension for disability is not paid by employer). For this case, customer should create thesame entry in infotype 0007 (considering reduced working hours) and customer copy of wagetype M580 in infotype 0014. In addition to this, there should be a mark in check box“Refundation not paid” (field PSUDD) in the infotype 0604. This will insure that during payrollcalculation disability compensation will not be calculated and paid out, but the calculation ofworking age remain correct.
Note
Part-time working schedule in infotype 0007 (fields P0007-EMPCT and P0007-TEILK)reduces working age calculation to percent in P0007-EMPCT for validity period of infotype0007. However, entering customer copy of wage type M580 into infotype 0014 automaticallyreturns working age calculation to 100%.
5.18. M600 – M610 Reimbursement for food and transport to work
These wage types are used for food and travel reimbursements:
M600 Food reimbursement – money
M605 Food reimbursement – tickets
M610 Reimbursement for transport to work
Wage types are automatically generated by function P0606 and are stored into IT table.
The entitlement for meal money/ticket or transport to work is calculated day by day accordingto work schedule (table PSP), absences and attendances as business trip. The day is validfor reimbursement if there is no absence/attendance which goes across that day.
Customizing is described in more details in Infotype 0606 – Transport and food SI in“SIC2000_EN Infotypes.pdf”.
5.19. M610 – M644, M310 – M344 Netto/Brutto wage types
Processing class 66 controls the way how the wage type is split to brutto/netto part. If thevalue of the wage type exceeds the limit, the brutto wage type M3xx defined in valuation base2 is created with the overlimit part. The underlimit part remains in the M6xx wage type.
5.19.1. M620 Separate living
The limit for split between underlimit and overlimit part is based on constant T511K-LIMR2Split limit for Separate living.
5.19.2. M625 Solidarity help (death of employee)
The limit for split between underlimit and overlimit part is based on constant T511K-LIMR4Split limit for Solidarity help (death of the employee).
5.19.3. M626 Solidarity help (others)
The limit for split between underlimit and overlimit part is based on constant T511K-LIMR3Split limit for Solidarity help (others).
5.19.4. M630 Compensation for pension
The limit for split between under limit and overlimit part is based on constant T511K-LIMR5Split limit for leaving to pension.
5.19.5. M641 – M644 Jubilee awards
The limit for split between underlimit and overlimit part is based on constants:
T511K-LIMR6 Split limit for Jubilee award 10 years,
T511K-LIMR7 Split limit for Jubilee award 20 years
T511K-LIMR8 Split limit for Jubilee award 30/40 years.
5.20. M650 Voluntary pension insurance (contribution of company)
The functionality of the PDPZ solution is following:
the company contribution of PDPZ can be evaluated by following optional ways: fixed value (in EUR) entered in infotype 0014 fixed percentage of upper flexible limit entered in infotype 0014 fixed percentage of upper flexible limit defined on company level (T510J - wage type
constants, grouping possible) fixed percentage of company base entered in infotype 0014 fixed percentage of company base defined on company level (T510J - wage type
constants, grouping possible) the company contribution of PDPZ is checked to the limits:
upper fixed limit - exceeding part placed to wage type dedicated for overlimit PDPZupper flexible limit - exceeding part placed to wage type dedicated for overlimit PDPZ.Employees that are full-month absent because of Maternity leave (Porodnice M530) -the upper flexible limit is not checked, the whole amount remains in under limit (netto)Employees that are part-month absent because of Maternity leave (Porodnice M530)and exceed the upper flexible limit - a warning message is displayed but division ofthe value to under/overlimit is performed anywaylower fixed limit - if not reached a message is displayed
if the contribution of the company does not reach any of the upper limits, the difference isstored for use in infotype 0011. The difference value can be used to determine optionalcontribution of the employee to PDPZ in following way:
fixed percentage of the difference entered in infotype 0011 the company contribution of PDPZ (one wage type without any splits) is distributed
proportionally according to company base.The functionality is prepared for possible enhancements by company specific algorithms.
See Voluntary pension insurance in document “SIC3000_EN Gross Payroll.pdf” for details.
5.21. M440 – M443 Participation in company profit
Wage types M440 to M443 cover all possible combinations, connected to participation incompany profit.
M440 Participation in company profit - brutto
M441 Participation in company profit - PDPZ - bruto
M442 Participation in company profit - neto
M443 Participation in company profit PDPZ - neto
Income is reported on REK-1 report with types 1130 to 1133. See note 1294588 for moredetails.
5.22. Gross wage types without social insurances
In certain circumstances, social insurances need not be calculated for selected “gross” wagetypes. They are reported on REK-1 income type 1089. These are following:
M089 Regular work Month - no SI
M255 Boniteta – no SI
M435 Regres – no SI
M335 Compensation for dismissal – no SI
M421 Bonus for project work – no SI
These wage types have values D1 to D9 in evaluation class 09 (assignment for REK report).
See also SAP note 1294588.
5.23. M700 Arrangement for authors BRUTTO
Wage type is an example of special contract. The value is subject of special taxation and SIcalculation (described in netto part of documentation).
5.24. M701 Arrangement for authors NETTO
Wage type is example of special contracts. Because the taxation is done by fixed rates, it ispossible to re-calculate the value from expected netto to brutto. The gross-up re-calculationcoefficient is stored in T512W – 1st valuation base. For example the value 90 means that theentered netto value will be divided by 0.90 to obtain requested brutto. After this gross-up, theID of the wage type is changed to T512W 1st valuation base = to M700.
5.25. M755, M756 Students working directly without agency
M755 must be used when student works for the 1st time for the company in calendar year.
M756 must be used in following months for the same student.
5.26. MJ* Travel expenses
Set of wage types for manual input of various travel expenses reimbursement:MJ1* under limit (netto wage types)MJ2* over limit (brutto wage types)
No automation is provided for calculation and split between net and gross wage types exceptfor MJ1A, which is described below.
5.27. MJ1A TE: km
Wage type is used for manual input of transport expenses, when each kilometre is reimursed(so called “kilometrina”). Split to overlimit part is automatic. Tax limit is 15% (constant T511K -GASLM) of price for one litre (stored in constant T511K-GASRS). Overlimit part is sent toMJ2A wage type.
Number of kilometres should be entered into infotype 0015, wage type field Number/Unit. Thevalue per kilometre can be calculated as follows:
If in T512W valuation base 1 valuation via constants from T510J is switched on (=value„K“) => this value is used. Suitable for companies that pay more than tax limit is.Template value in T510J wage type for one kilometre reimbursement is 0,25 EUR/km. Ifthere is no rate stored in T510J under wage type code (i.e. MJ1A), limit from T511K-GASLM & GASRS is used as a rate, meaning everything is under tax limit.
If in T512W valuation base 1 is empty => value per kilometre is set to the limit which isspecified by constants GASRS and GASLM.
If amount exceeds the limit, overlimit part is stored into wage type defined in valuation base 2(in template, this is MJ2A as mentioned above).
6. Absence typesOverview of template absence types can be displayed with HSIUABS0 report:
- in client 000 template settings- in production client your settings.
In next chapters, absences with special processing are descibed. They are automatically splitinto several parts according to customizing table T7SI0C in function SINAB Absence splittingdescribed in “SIC1000_EN Payroll in SAP System.pdf” before the processing in function PAB.
Note
Absence types “COMA”, “COMC”, “COMP” and “COMR” are reserved for SAP (generatedand used during processing of part-time illnesses entered in infotype 0014) and you shouldnot use them in infotype 2001.
Below is a simple table with major absence types for Slovenia and their major properties.Names are in original, SL language.
Konfiguracija odsotnosti HR SI 1
----------------------------------------------------------------------------------------------------------
Krajš. Verar Pla .Tip odsotn. Klbew -> Klbew Razr. Enota Tip pla e
----------------------------------------------------------------------------------------------------------
0200 Bolezen 40 04 41 Bolezen do 30 dni 41 X RH X M160 Bolezen do 30 dni 04 70 Bolezen 31-90dni 70 X RH X M501 Bolezen 31 do 90 dni 04 42 Bolezen > 90dni 42 X RH X M500 Bolezen 90%r0210 Poklicna bolezen 46 04 47 Bolezen iz d. 30dni 47 X RH X M162 Bolezen iz dela do 30 dni 04 48 Bolezen iz d.>30dni 48 X RH X M502 Bolezen iz dela nad 30dni0220 Poškodbe na delu 52 04 53 Pošk.na delu < 30dni 53 X RH X M165 Pošk. na delu do 30 dni 04 54 Pošk.na delu > 30dni 54 X RH X M505 Pošk. na delu nad 30 dni0225 Poškodba 18. lan 55 55 Poškodba po 18.clenu 55 X RH X M528 Poškodba po 18. lenu ZZVZ0230 Poškodba izven dela 58 04 59 Pošk.izven d. 30dni 59 X RH X M170 Pošk.izven dela do 30 dni 04 72 Pošk.izven d. 31-90d 72 X RH X M511 Pošk.izven dela 31-90 dni 04 60 Pošk.izven d.>90dni 60 X RH X M510 Pošk.izven dela 80%r0235 Poškodba izv.dela 3 osebi 43 04 44 Pošk.po 3.os.do30dni 44 X RH X M175 Pošk.izv.dela 3.os. do30d 04 71 Pošk.po 3 os. 31-90d 71 X RH X M516 Pošk.izv.dela 3.os.31-90d 04 45 Pošk.po 3.os. >90dni 45 X RH X M517 Pošk.izv.dela 3.os. 80%r0240 Nega družinskega lana 64 64 Nega druz.clana 64 X RH X M515 Nega družinskega lana0245 Transplantacija 50 06 73 Transplantac. 90dni 73 X RH X M519 Transplantacija do 90 dni 06 74 Transplantac. >90dni 74 X RH X M518 Transplantacija 100%r0250 Spremstvo družinsk. lana 65 06 75 Spremstvo 90dni 75 X RH X M521 Spremstvo do 90 dni 06 76 Spremstvo > 90dni 76 X RH X M520 Spremstvo 80%r0255 Uspo.za rehab.otroka 51 51 Uspos.rehab.otroka 51 X RH X M527 Usposablj.za rehab.otroka0260 Izolacija REF. 100 % 66 06 77 Izolacija 90dni 77 X RH X M526 Izolacija do 90 dni 06 78 Izolacija > 90dni 78 X RH X M525 Izolacija 100%r0370 Krvodajalstvo 06 05 68 Krvodajalstvo 1.dan 68 X RH X M535 Krvodajalstvo-refund. 05 06 Krvodajalstvo > 1 06 X RH X M151 Krvodajastvo0400 Vojaške vaje/ter.obr. 20 20 Voj.vaje/ter.obr. 20 X RH X M550 Vojaške vaje0410 Civilna zaš ita 21 21 Civilna zaš ita 21 X RH X M555 Civilna zaš ita0420 Sodni pozivi REF. 22 22 Sodni pozivi REF. 22 X RH X M560 Sodni poziv
----------------------------------------------------------------------------------------------------------
Whole list of absences with all properties from HSIUABS0 is on next pages.
Absence Configuragion HR SI
---------------------------------------------------------------------------------------------------------------------------------------------
Constr Abrev Verar Paid
Absence type Scrn Counting rule Klbew -> Klbew Class Unit Wage type
---------------------------------------------------------------------------------------------------------------------------------------------
0100 Vacation 2001 01 001 Vacation with 200 D 01 01 02 Vacation Prev.Year 02 X RH X M131 Vacation previous year
01 03 Vacation Curr.Year 03 X RH X M130 Vacation current year
0200 Illness 2008 02 011 Strong absence 40 04 41 Illness < 30 days 41 X RH X M160 Illness less than 30 days
04 70 Illness < 30 days 70 X RH X M501
04 42 Illness REFUNDED 42 X RH X M500 Illness refunded
0210 Illness caus.by work 2008 02 011 Strong absence 46 04 47 Illness WK< 30 days 47 X RH X M162 Illness from work
04 48 Illness WK REFUNDED 48 X RH X M502 Illness caused by work
0220 Work accident 2008 02 011 Strong absence 52 04 53 WrkAcc < 30 days 53 X RH X M165 Work accident less than 3
04 54 WrkAcc REFUNDED 54 X RH X M505 Work accident refund
0225 Work accident 2008 02 011 Strong absence 55 55 WrkAcc REFUNDED 55 X RH X M528
0230 Non-Work accident 2008 02 011 Strong absence 58 04 59 NonAcc < 30 days 59 X RH X M170 NonWork accident less tha
04 72 Illness WK REFUNDED 72 X RH X M511
04 60 NonAcc REFUNDED 60 X RH X M510 NonWork accident
0235 Non-Work accident 2008 02 011 Strong absence 43 04 44 Illness < 30 days 44 X RH X M175
04 71 Illness REFUNDED 71 X RH X M516
04 45 Illness REFUNDED 45 X RH X M517
0240 Family member nursing 2008 02 011 Strong absence 64 64 Family member nursin 64 X RH X M515 Fam.memb.nursing
0245 Family member nursing 2008 02 011 Strong absence 50 06 73 Family member nursin 73 X RH X M519
06 74 Family member nursin 74 X RH X M518
0250 Family member accomp. 2008 02 011 Strong absence 65 06 75 Family member accomp 75 X RH X M521
06 76 Family member accomp 76 X RH X M520 Fam.memb.accompaning
0255 Family member accomp. 2008 02 011 Strong absence 51 51 Family member accomp 51 X RH X M527
0260 Isolation 2008 02 011 Strong absence 66 06 77 Isolation 77 X RH X M526
06 78 Isolation 78 X RH X M525 Isolation
0270 Maternity leave 2008 02 011 Strong absence 67 67 Maternity leave 67 RH X M530 Maternity protection
0300 Marriage 2001 02 002 Casual leave with 05 05 Casual paid leave 05 X RH X M140 Casual paid leave
0305 Job search 2001 02 002 Casual leave with 05 05 Casual paid leave 05 X RH X M140 Casual paid leave
0310 Movement (interest of ER) 2001 02 002 Casual leave with 05 05 Casual paid leave 05 X RH X M140 Casual paid leave
0315 Movement (interest of EE) 2001 02 002 Casual leave with 05 05 Casual paid leave 05 X RH X M140 Casual paid leave
0320 Child birth 2001 02 002 Casual leave with 05 05 Casual paid leave 05 X RH X M140 Casual paid leave
0325 Child marriage 2001 02 002 Casual leave with 05 05 Casual paid leave 05 X RH X M140 Casual paid leave
0330 Family member death 2001 02 002 Casual leave with 05 05 Casual paid leave 05 X RH X M140 Casual paid leave
0335 Health examinations 2001 02 002 Casual leave with 05 05 Casual paid leave 05 X RH X M140 Casual paid leave
0340 Elementary catastrophies 2001 02 002 Casual leave with 05 05 Casual paid leave 05 X RH X M140 Casual paid leave
0345 Other casual leaves 2001 02 002 Casual leave with 05 05 Casual paid leave 05 X RH X M140 Casual paid leave
0370 Blood donation 2000 02 010 Weak absence 06 05 68 Blood donation 1 day 68 X RH X M535
05 06 Blood donation >1 D 06 X RH X M151 Blood donation
0375 Educational leave 2000 02 010 Weak absence 07 07 Educational leave 07 X RH X M152 Study with work
0380 Vocational training 2000 02 010 Weak absence 08 08 Vocational training 08 X RH X M153 Vocational training
0400 Military exercise 2000 02 010 Weak absence 20 20 Military exercise 20 X RH X M550 Military exercises
0410 Civil protection 2000 02 010 Weak absence 21 21 Civil protection 21 X RH X M555 Civil protection
0420 Court appeals 2002 02 010 Weak absence 22 22 Court appeals 22 X RH X M560 Court appeals
0500 Trade union work 2002 02 010 Weak absence 23 23 Trade union work 23 X RH X M102 Trade union work
0510 Labor board 2002 02 010 Weak absence 24 24 Labor board 24 X RH X M104 Labor board
0600 Waiting for work 2000 02 010 Weak absence 25 25 Waiting for work 25 X RH X M110 Waiting
0605 Suspension 2000 02 011 Strong absence 26 26 Suspension 26 X RH X M158 Suspension
0610 Prison 2000 02 010 Weak absence 28 28 Prison 28
0620 Strike 2000 02 010 Weak absence 27 27 Strike 27 X RH X M156 Strike
0700 Unpaid leave 2002 02 010 Weak absence 29 29 Unpaid leave 29 RH X M115 Not paid absence
0710 Unallowed absence 2000 02 010 Weak absence 30 30 Unallowed absence 30 RH X M116 Unallowed absence
COMA (Compensation of Illness) 2000 00 000 Weak absence 00 00 00
COMC (Compensation of Illness) 2000 00 000 Weak absence 00 00 00
COMD (Compensation of Illness) 2000 00 000 Weak absence 00 00 00
COMP (Compensation of Illness) 2000 00 000 Weak absence 00 00 00
COMR (Compensation of Illness) 2000 00 000 Weak absence 00 00 00
LEGEND:Scrn - screen number from T554S Verar - splitting algorithm from T7SI0CConstr - time constraint from T554S Klbew - valuation class of the absence after processing of T7SI0C tableAbrev - single letter abreviation from T554S Class - counting class from T554CKlbew - valuation class of the absence from T554S Unit - value (days, hours-..) to be stored into generated wage type in T554CPaid - „paid/unpaid: from T554C
6.1. 0100 Vacation
This absence is connected to absence quota in infotype 2006. Quota can be used till the endof June of the next year. Generation of quota can be performed by program RPTQTA00which was extended to meet Slovenian specifics: the calculation can be controlled by tablesT7SIL1, T7SIL2 and T7SIL3. See description of report HSITLEA1 for details.
Absence Vacation is automatically split to separate wage types for quota deduction fromprevious and from current year. Splitting is done by settings in table T7SI0C where splittingalgorithm 01 Vacation old/new is used. Splitting is enabled in function SINAB.
6.2. 0200, 0210, 0220, 0230 and 0235 Illnesses
Illnesses of types 0200, 0210, 0220, 0230 and 0235 are split into 2 or 3 parts according tofollowing rules:
For some absence types, first 30 working days according to employee’s work schedule iscompensated by employer company
o Note: Some absence types are not compensated by employer company at all,rather are refunded by ZZZS from the first day of absence
starting with 31st working day, absence is refunded by ZZZS as follows:A. 90 calendar days with lower rate, if refundation started on 31.05.2012 or later.
Counting starts on the 31st working day (and not on a day after 30th working day,which can be Saturday!). If first day of refundation was before 31.05.2012, thispart is skipped – whole refundation period falls in B.
B. Till the end of absence with classic rate.Special additional rules apply: Max. 120 days of the same illness may be paid by company in the same calendar year
10 day gap rule applies for so called recidiv: if gap between respective absences causedby the same illness is shorter than 10 days, the later part of absence is refunded from thefirst day.
Users often enter illnesses in several parts, usually month by month. If some records ininfotype 2001 or 0014 are logically connected (they belong to one illness), logical start of thisillness must be entered in field 2001-KBBEG or P0014-ZUORD.
Splitting is done by settings in table T7SI0C where splitting algorithms 04 Illness 30 days from2003 and 06 Illness 90 days from 2012 are used. Splitting is enabled in function SINAB.
Whole calculation of illnesses is described in “Processing of absences“ in “SIC3000_ENGross Payroll.pdf”.
6.3. 0300 - 0345 Casual leaves
Absences 0300 to 0345 are connected to absence quota in infotype 2006. Quota can be usedtill the end of June the next year.
6.4. 0370 Blood donation
Blood donation absence is split into two parts. The first day is refunded and following days (ifexist) are paid by company.
Splitting is done by settings in table T7SI0C where splitting algorithm 05 Blood donation isused. Splitting is enabled in function SINAB.
(C) SAP AG 30
6.5. COMx Compensation of illness
These are artificial absences types which are generated by the system during compensationcalculation of part time employment caused by illness; it is entered in infotype 0014. It maynot be entered into infotype 2001.
Whole calculation of illnesses is described in “Processing of absences“ in “SIC3000_ENGross Payroll.pdf”.
(C) SAP AG 31
7. Processing of absences
7.1. Illnesses customizing and calculation
Program automatically divides illnesses to parts paid by company and refunded by ZZZS withrespect to valid legislation:
For some absence types, first 30 working days according to employee’s work schedule iscompensated by employer company
o Note: Some absence types are not compensated by employer company at all,rather are refunded by ZZZS from the first day of absence
starting with 31st working day, absence is refunded by ZZZS as follows:C. 90 calendar days with lower rate, if refundation started on 31.05.2012 or later.
Counting starts on the 31st working day (and not on a day after 30th working day,which can be Saturday!). If first day of refundation was before 31.05.2012, thispart is skipped – whole refundation period falls in B.
D. Till the end of absence with classic rate.Special additional rules apply: Max. 120 days of the same illness may be paid by company in the same calendar year
10 day gap rule applies for so called recidiv: if gap between respective absences causedby the same illness is shorter than 10 days, the later part of absence is refunded from the1st day.
Only one infotype entry for whole absence is required. However, users often enter illnesses inseveral parts, usually month by month. If some records in infotype 2001 or 0014 are logicallyconnected (they belong to one illness), logical start of this illness must be entered in field2001-KBBEG or P0014-ZUORD.
7.1.1. Customizing of illnesses’ split
The splitting itself is triggered by payroll function SINAB. Split customizing table is T7SI0Cwhere splitting algorithms are used:
Algorithm 04 Illness 30 days from 2003 is used from year 2003 for absences, whichare paid by company and refunded by ZZZS, each for certain period. Before year2003, algorithm 02 Illness 30 days till 2002 was used.On 31.05.2012, when rules were changed by law ZUJF and 90 calendar days rulewas introduced for some illness types, algorithm 04 was enhanced to be able to splitillnesses into three parts (other rules from year 2003 were not changed):
First 30 working days of illness paid by employer company, the rest refunded First 90 calendar days with lowered percentage of refundation; 90 calendar
days period starts on 31st working day (and not on a day folowing 30th
working day, which might be a day-off!) From the 91st calendar day of refundation till end of illness with classic
percentage of refundation – same as before ZUJF
New rules are NOT valid for absences already in refundation period before31.05.2012!
It is important to use separate record for algorithm 04 in table T7SI0C from31.05.2012 on, to be able to assign three absence valuation rules to one illness onlyfrom that day, when new rules with law ZUJF were inforced.
It is recommended to use the new record for algorithm 04 also for absences that havethe same percentage from the last year’s base for whole refundation period,regardless of 90 calendar days rule.
(C) SAP AG 32
Algorithm 06 Bolezen 90 dni do 2012 is used only for absences, refunded from thefirst day. It is valid from 31.05.2012, when rules were changed by ZUJF law and the90 calendar days rule was introduced to split the refunded illness into two parts:
First 90 calendar days with lowered percentage of refundation Refunded illness from the 91st calendar day till end of illness with higher
percentage of refundation – same percentage as before ZUJF.
You can use HSIUABS0 report to find out which records in T7SI0C are used for whichabsences.
See note 1726924 for detailed explanation of all the changes caused by law ZUJF per31.05.2012.
Evaluation class 08 setting is used when processing part-time illnesses from infotype 0014. Itis assumed that values bellow (40, 41, and 42) are used in T554C for evaluation of illnessesto wage types; these values are used in templates delivered by SAP. Set evaluation class 08in wage types that are created from SAP template wage types according to following table:
40 Illness that will be automatically divided to Company/Refunded M1A0 Bolezen (do/nad) M1A1 Bolezen z dela (do/nad) M1A2 Pošk.na delu (do/nad) M1A3 Pošk.izv.dela (do/nad) M1A4 Pošk.izv.dela 3.os.(do/nad)41 Illness paid by Company
M160 Bolezen do 30 dni M162 Bolezen iz dela do 30 dni M165 Pošk. na delu do 30 dni M170 Pošk.izven dela do 30 dni M175 Pošk.izv.dela 3.os. do 30 dni42 Illness Refunded M500 Bolezen 90%r M502 Bolezen iz dela nad 30 dni M505 Pošk. na delu nad 30 dni M510 Pošk.izven dela 80%r M517 Pošk.izv.dela 3.os. 80%r
There are 3 constants in T511K related to absence splitting mechanism. You need notchange those.
ILGAP Max.gap for the same illnesses 10,00ILONE Max.illness days paid by company 30,00ILYEA Max.illness days annual paid by comp. 120,00
Technical wage type /0I2 is created automatically during payroll and contains number of dayspaid by company for all illnesses that start in particular year. This wage type is used to checkthe 120 day quota. Cumulative value is stored in wage type in payroll result table CRT. If youneed to manually change number in this wage type, you can enter it in infotype 0015 infollowing way:
BEGDA should be the 1st day in particular month. The values entered woulddefine how many days were paid by company up till entered BEGDA (BEGDAday is not included).Example: BEGDA = 01.03.2003 => the number field in IT 0015 (P0015-ANZHL)tells how many days were paid by company up to 28.2.2003 inclusive.
Place number of days into NUMBER field. If you need to define the day when 120 day quota was spent, enter it into field
AMOUNT in format: YYYYMMDD.The value entered in infotype 0015 is taken into payroll processing, replaces anyvalues coming from the previous payroll periods. During payroll it is increased byillnesses paid by company in current month.
(C) SAP AG 33
If you use this manual correction, it is not possible to use special programs thatrestore the CRT table without running payroll – it is necessary to restore the CRTstatus using retro calculation.
Template absence types and wage types are delivered.
Report HSICBOL0 Refunded illnesses – claim is prepared to display all types of illnessesand to send the claim for refundation to ZZZS. To achieve correct program functionality it isnecessary to connect your customizing of absences and wage types with delivered programs.
7.2. Blood donation customizing and calculation
Program automatically divides blood donation (Krvodajalstvo): first day is refunded and therest is paid by company.
Algorithm 05 Blood donation is used in T7SI0C for splitting blood donation.
7.3. Part-time absences in infotype 2001
Due to technical principle of SAP calculation it is not possible to enter part-time absences(each day few hours) in infotype 2001 as one single absence that would cover all days. If youwould do this, the whole day would be considered as not-worked.
Enter individual short absences in infotype 2001 for each single day of the part-time illness;leave infotype 0007 unchanged (full employment percentage). To make the calculationprogram aware, that these entries represent logically one illness, you have to enter illnessstart date into every such absence record (field „Certified start“, P2001-KBBEG).
In fact this approach is similar to one when you enter several multi-day whole-day absencesand connect them logically to one illness. However, there is a small difference if such part-time illness goes across a public holiday: in solution with part-time illness in infotype 0014 (senext chapter) the amount paid by the system for the public holiday is reduced properly(because employment percentage in infotype 0007 is lower). When you use approach withseveral records in infotype 2001 the amount paid for the public holiday remains the same – itis not reduced by part-time illness share = it is necessary to manually correct the amount paidfor the public holiday.
For easier input of individual part-time absences use utility program HSIISLV0. Programcreates new records in infotype 2001 according to entered parameters on selection screen. Itdoes not perform any subsequent change of the infotype 2001 records – this has to be donemanually.
Report specific parameters:
Absence From/To (Bolezen od/do) – starting / ending day of the part-time illness periodOrig.start of the absence (Prvi dan odsotnosti) – if you enter new absence it isidentical to the „Illness From“Absence type (Tip odsotnosti) – subtype of 2001 that will be usedReduction % (Skrajšan D - %) - individual daily absences will be calculated fromplanned time of particular day using specified percentage. Program will propose time atthe end of the planned shift (as if the EE would leave sooner each day).Reduction hour (Skrajšan D - ure) – individual daily absences will be calculated usinghours entered. Program will propose time at the end of planned shift (as if the EE wouldleave sooner each day).Data generation options (Opcije generiranja podatkov)
Batch input map (Seja paketnega vnosa) – program will create batch input map forlater processingCall transaction (Klic transakcije) – the proposed absences will be inserted into theinfotype 2001 immediately
Execution:
(C) SAP AG 34
Program displays a table with proposed entries for infotype 2001
On the right side, the columns 2001 and 2002 check if there are / are not overlappingrecords in infotypes 2001 and 2002. Green hyphen = no conflict, red cross = conflict – therecord will not be processed.
Mark records that should be created by the available buttons (individually / all)
Press „Processing“ – either batch input session is generated or the Call transaction(direct execution) is performed.
7.4. Part-time absences in infotype 0014 – alternative method
Note
This solution was replaced with new solution to enter part time illnesses in IT 2001 the sameway as full time illnesses. New solution is more suitable for customers, who are using anylevel of time management. Here described older solution stays in place for customers thathave already implemented it; it is simpler in data entry and can be suitable for customerswithout time management and simple entry of agregated time data.
Wage types M1A0 to M1A4 are special wage types featuring automatic split of part-timeillnesses to part paid by company and part refunded.
M1A0 Bolezen (do/nad) M1A1 Bolezen z dela (do/nad) M1A2 Pošk.na delu (do/nad) M1A3 Pošk.izv.dela (do/nad) M1A4 Pošk.izv.dela 3.os.(do/nad)
Employee works part time – with this solution infotype 0007 should be set to really workedpercentage and hours, not for full time.
Above wage types should be entered into infotype 0014 with following data:
Begda = start of the part-time illnessEndda = end of the part-time illnessNumber/unit = number of hours per day to be paid as illnessAssignment number (ZUORD) = first day of illness (enter it if earlier than Begda). Thisdate is important to determine which average should be used for illness calculation. If thisdate lies in current month, average from wage type /0I0 is used. If it lies in previousmonths, average of long-lasting illness /0I is used instead.
Calculation program reads wage type data from infotype 0014, performs the split and createswage types as specified in T512W in primary and secondary outgoing wage type.
Wage type M1Ax, entered in infotype 0014, is eliminating during further processing (it neednot be posted to FI ...). It serves only for easier data entry in 0014.
To use this functionality, copy M1Ax wage types to customer ones. Based on processingclass 65, program will recognize wage type and perform correct split in operation SIILC withthe same logic as for illnesses from infotype 2001 – customizing in table T7SI0C is taken asinstruction.
Note
This solution used secondary wage types, entered in T512W, for outgoing wage types afterautomatic split. Even model wage types M1Ax still have secondary wage types entered.However, solution was changed and unified with new rules enforced by ZUJF on 31.05.2012.Outgoing wage types are determined based on outgoing absence valuation rules in T7SI0Ccustomizing for absences coming from infotype 0014, too.
7.5. Average from previous month as hourly rate for absences
(C) SAP AG 35
Wage type /0H0 holds average hourly rate from previous payroll result. It is used as hourlyrate (=valuation base) for several absences, like vacation and all types of illnesses,compensated by employer company.
Calculation is performed in schema SIAV, function SIAVG Average calculation Sloveniadescribed in “SIC1000_EN Payroll in SAP System.pdf”. Wage type /0H0 is stored into IT asoutput of the function. Technical wage type /202 stored in previous result is base for theaverage:
AMT = amounts of wage types specified in T512WNUM = hours of wage types specified in T512W
Formula: /0H0.RTE = /202.AMT divided by /202.NUM.
Average /0H0 is stored in current payroll result. Figures amount and number are also filled:/0H0.AMT = /202.AMT/0H0.NUM = /202.NUM.
This average can be used for valuation like any other SAP standard valuation base - it can beentered in T512W-GVBLA and it will be used in rule X015 for valuation.
Note
Average calculation is valid only for ordinary EE. Students, PD and APD are not relevant. Thisis controlled by T503-ANSTA. The value “9” inhibits the calculation.
Manual input of average
Manual input of average is possible in infotype 0015 using wage type /0H0. Following fieldsmust be filled:Amount: average for vacationBegda: date must lie within start/end date of the period for which you run payroll.
Takeover from infotype 0015 is done in schema SIAV, rule SIA1.
Caution
Store average /0H0 in infotype 0015 when prepairing for the first payroll run in SAP as well asduring hiring new employee. It is mandatory data for the first payroll – payroll will finishunsuccessfully with error, if /0H0 is not available in infotype 0015 when there is no previouspayroll result to take it from there.
7.6. Average from previous year as hourly rate for refunded illnesses
Once illness falls in period, when it is refunded by ZZZS, its valuation is determined by ZZZSrules. Company should follow this rules in illness calculation, compensate employee withcalculated amount and request refundation from ZZZS on special request form BOL-0.
7.6.1. Hourly rate calculation - /0I0 and /0I1
Hourly rate is determined based on average hourly rate for worked hours in a preceding yearrelated to very first day of illness.
Example
Illness starts 20.12.2010. First 30 working days are not refunded. The 1st refunded day is31.1.2011. Average will be calculated based on payroll results whose paydays lie within1.1.2009 - 31.12.2009.
Average hourly rate must be calculated each year from salaries with payday in particular year.Technical wage type /201 is the base for average hourly rate calculation; it is stored in eachpayroll result (each month):
/201.AMT = amounts of wage types for worked hours – specified in T512W/201.NUM = hours of wage types for worked hours – specified in T512W
(C) SAP AG 36
Average hourly rate is calculated with aggregation of all /201.AMT and /201.NUM respectivelyfor given period (previous year) and then with dividing aggregated /201.AMT by /201.NUM. Itis stored into wage type /0I0, field NUM (infotype 0015). Using this calculation, base for illnessin current year is from previous year. This data is not written anywhere – it is assumed bySAP as a default.
Field /0I0.AMT should additionally be filled with annual average gross salary in RS for thesame period. In most cases the period is the whole previous year, which is considered in SAPas default. Exceptions are handled with wage type /0I4, described later in this document. Ifemployee did not work whole previous year, average from /201 is evaluated from only thosemonths when worked.
Recommendation
Field /0I0.AMT can be filled with amount 1,00 EUR for periods after 01.01.2007 sincerevalorization method changed with this date.
Program HSICAVG0 is performing average calculation. It should be ran as batch for allemployees each year. It is also able to store hourly rates into infotype 0015. For moreinformation on usage of this program please see program’s description in document SIC 7000Reports.
During payroll, the latest hourly rate /0I0 is read from infotype 0015 and stored in payrollresult.
As an alternative, average hourly rate calculation can be performed once per yearautomatically during payroll run. It is triggered in schema SIAV, function SIAVG Averagecalculation Slovenia described in “SIC1000_EN Payroll in SAP System.pdf”, when wage type/0I0 is not found in infotype 0015 and parameter Par2 is not set to OFF. Wage type /0I0 isstored into IT as output of the function. By default, parameter Par2 is set to OFF (preventingautomatic calculation in payroll run).
Once the average hourly rate from /0I0 is used for new illness, it has to be used till the end ofthe respective absence even if the absence spans into next calendar years. In SAP it is called"frozen" average and is stored in wage type /0I1. Procedure: for each new illness in currentpayroll period, a copy of the /0I0 is stored in wage type /0I1. This wage type accompanies thewage type of specific illness till very end of the illness.
Note
Average calculation is valid only for regular employees. Students, PD and APD are notrelevant. This is controlled by T503-ANSTA. The value “9” inhibits the calculation.
Changed functionalities in year 2008
In year 2008, some functionalities were changed and enhanced. However, all corefunctionalities remain the same! Record with correct /0I0 still has to exist in infotype 0015 foreach employee with illness absence. Actual hourly rate is taken from field Number (P0015-ANZHL) and then revaluated.
1. Please note that system takes hourly rate from record in IT 0015, which is valid onthe very first day of each illness; before 2008, it took record valid on the first day,when illness was refunded by ZZZS.
2. Manually entered average /0I1 in infotype 0015 will be directly used in valuation. Thisis useful for manual corrections and migrated employee’s data.
Manual input of average hourly rate
Manual input of the average hourly rate is possible in infotype 0015 using wage type /0I0.Following fields must be filled:Amount: average annual gross salary in RS, related to periods from which the base foraverage was readNumber/Unit: employee’s hourly rate for refunded illnessBegda: the date must lie within start/end date of the period for which you run payroll.Takeover from infotype 0015 is done in schema SIAV, rule SIA1.
(C) SAP AG 37
7.6.2. Revalorization index
Average hourly rate, used for illness (/0I1), is corrected each month with revalorization indexwhich is in general calculated based on average salaries in Slovenia. Rules of revalorizationchanged during years significantly and many times. It is important to know, that rules for longlasting illnesses do not change for the past: illness, started in 2005 and ended in 2011, mustconsider all revalorization rules, valid during this period!
Several customizing tables are involved to determine correct revalorization index for particularillness.
For more information about calculation revalorization index see also SAP notes:1021785 Sick leave refundation - calculation in 20071021646 Sick leave refundation - calculation in 20081240205 Sick leave refundation - calculation in 20081613622 Sick leave refundation - all index values in T7SIRI8
Revalorization index till 31.12.2006
Base for revalorization is inflation, which is measured by officially announced average grosssalary for each month (average of Republic Slovenia (RS)).
Example
Jan 2001 204.500,00 SIT (monthly average gross salary)Feb 2001 206.687,00 SITMar 2001 206.892,00 SITetc.
Average gross salary is published in gazette „Uradni list (UL)“ for month before previous (2months ago) and is meant to be used for payroll in current month. When running payroll forJune, the average gross salary for April is already known and should be entered into SAPsystem into customizing table T7SIRS. Average is published also on Statistical Agency pagehttp://www.stat.si/indikatorji.asp?id=6.
Official average gross salary in RS of the period, from which the average hourly rate /0I0 wascalculated is also important for revalorization. This is usually annual average gross salary,also published in gazette Uradni list as well as on Statistical Agency page(http://www.stat.si/indikatorji.asp?id=30). This amount should be entered in wage type /0I0,field AMT.
Revalorization index = AVcurr / AVper
AVcurr = official average salary for current month from Uradni listAVper = official average salary of the period from which the average hourly rate /0I0 wascalculated
Actual revalorization is performed in schema SIAV, rule SIA4. Processing class 65 controlswhich wage type is „illness“. Following cases occur:
Refundation of illness starts in current month (FOR period)The /0I0.RTE is multiplied by last known average gross salary in RS, stored in tableT7SIRS, and divided by /0I0.AMT (annual average gross salary in RS in a year, fromwhich base is taken). The result is stored into RTE field of illness wage type (M5xx). Copyof /0I0 is stored into /0I1 with ABZNR split for evaluation in reports and takeover ofaverage for long-lasting illnesses.
Refundation of illness has started in previous monthsHourly rate for such illness is always read from /0I1 from previous regular payroll result.The /0I1.RTE is multiplied by last known average gross salary in RS, stored in tableT7SIRS, and divided by /0I1.AMT (annual average gross salary in RS in a year, fromwhich base is taken). The result is stored into RTE field of illness wage type (M5xx).Wage type /0I1 is stored in the IT table with ABZNR split for evaluation in reports andtakeover of average for long-lasting illnesses.
(C) SAP AG 38
Note
Customizing table T7SIRS should have the last and only visible record as follows:BEGDA ENDDA PABRP PABRJ AVGRS------------------------------------------------------------------------------------------------------------xx.12.2006 31.12.9999 10 2006 293.121,00------------------------------------------------------------------------------------------------------------
This record is most important in this table for correct revalorization of long lasting illnesses.
Revalorization index in year 2007
Starting with 01.01.2007, revalorization of hourly rate is not performed each month, but ratheronly once per year. For payroll periods in year 2007 actually no revalorization is needed –latest revalorization index for old long lasting illnesses is calculated based on last valid recordin T7SIRS. Newer illnesses are revaluated for the first time in a year, in which base for hourlyrate is 2 years old.
Example
Illness starts in 04.2007, base for it is from year 2006. First revalorization must be in year2008.
Wage type /0I4 is used to override SAP’s default, that base for illness hourly rate is illnessstart year-1. It covers special case, described by Case 6 in ZZZS letter: base for illness isfrom the same year as illness start.
Example
Illness starts in 04.2007, base for it is from year 2007. First revalorization must be in July2009. SAP considers that base is from an illness start year-1 by default, which would be 2006in this case. New wage type /0I4 is used to signalize exception to this rule.
Enter wage type /0I4 into infotype 0015 with following data:
Number: year of the base (for above example it would be 2.007,00)
Begda: date of origin - enter start date of the illness; when employee has many illnesses thatyear, one record with same data is enough for all illnesses starting that year.
Hourly rates for illnesses, started in 2007, are not revaluated.
Year 2007 is actually declared as transition period.
Revalorization index from 01.01.2008 to 30.06.2008
New customizing table T7SIRI was introduced to hold annual revalorization index - in fact onlyindex for year 2007, since method changed in July 2008 again. Index is published by ZZZS.
Hourly rate for illness, started before 01.01.2007, is revalorizated by adequate index up toend of year 2006 (see description above) and then multiplied by revalorization index fromtable T7SIRI.
Hourly rate for illness, started in a year before current one (=2007), is not revaluated.
Actual revalorization for payroll periods after 01.01.2008 is performed in schema SIAV, innewly introduced rule SIA6. It uses a call to newly created operation SIARI, which wasdesigned to calculate correct revalorization index in 2008 and later. Its processing can betraced in payroll log (check Old log (Stari zapisnik) via button in the log). Operation followsrounding rules, which were defined in letter sent by ZZZS in 07/2008.
Caution
Table T7SIRI was used only for half a year (for all payroll periods 01.01.2008 to 30.06.2008)and then replaced by table T7SIRI8 (see description below). However, it must stay intact - it isused for retro calculation of periods in first half of 2008 (called from operation SIARI).
(C) SAP AG 39
Revalorization index from 01.07.2008 on
In payroll periods from 01.07.2008, revalorization of hourly rate is performed twice a year.New customizing table T7SIRI8 was introduced to hold half-annual revalorization index. Indexis recorded for a month, which closes the period for index calculation.
Example
ZZZS publishes index for period January - June 2008, which is 1,0410. This index is used forrefunded illness calculations in payroll period 07/2008. Entry in table T7SIRI8 holds value1,0410 for year 2008 and month 06.
Maintenance of T7SIRI8 table is under customer responsibility (class C) throughcorresponding maintenance view T7SIRI8. SAP provides valid indexes (T7SIRI8 tableentries) in SAP note 1613622. Check this note periodically and during go-live preparation.
For payroll periods in year 2008 and later, actual revalorization is performed in schema SIAV,rule SIA6.
7.6.3. Check of resulting hourly rate
After above processing, illness wage type contains:NUM – number of hours (evaluated in function PAB)RTE – hourly rate for illness already increased by revalorization
Calculated hourly rate is then multiplied with percentage specific for absence type, stored withwage type’s valuation base.
At the end, hourly rate is compared with valuation base /003 (basic pay for comparison torefunded illnesses). The lower of the two values is used. Legal rationale: absence may not bepaid higher than regular work.
This step is performed in schema SIAV, rule SIA4 and SIA6 (depends on payroll period –bofore or after 01.01.2008).
(C) SAP AG 40
8. Voluntary pension insurance (PDPZ)Used terms:
Upper fixed limit - maximal PDPZ contribution defined in the law in EUR Upper flexible limit - maximal PDPZ contribution defined as percentage of pension
insurance Lower fixed limit - minimal PDPZ contribution defined in the law in EUR Company base - base for calculation "how much does company want to contribute to
PDPZ for particular employee"
Functionality of new PDPZ solution
Company contribution of PDPZ can be evaluated in following alternative ways:
fixed value (in EUR) entered in infotype 0014 fixed percentage of upper flexible limit entered in infotype 0014 fixed percentage of upper flexible limit defined on company level (T510J - wage type
constants, grouping possible) fixed percentage of company base entered in infotype 0014 fixed percentage of company base defined on company level (T510J - wage type
constants, grouping possible)
Company contribution of PDPZ is checked to the limits (compatible with older solution):
upper fixed limit - exceeding part placed to wage type dedicated for overlimit PDPZupper flexible limit - exceeding part placed to wage type dedicated for overlimit PDPZ.For employees that are absent whole month due to Maternity leave (Porodnice M530)upper flexible limit is not checked, whole amount remains in under limit (netto)For employees that are absent part of the month due to Maternity leave (PorodniceM530) and exceed the upper flexible limit - a warning message is displayed butdivision of the value to under/overlimit is performed anywaylower fixed limit - if not reached a message is displayed.
If company contribution does not reach any of the upper limits, difference is stored for use ininfotype 0011. Difference value can be used to determine optional employee contribution withfixed percentage of the difference entered in infotype 0011.
Company contribution of PDPZ (one wage type without any splits) is distributed proportionallyaccording to company base.This functionality is enabled for possible enhancements with company specific algorithms.
Limitations
You can define several wage types with different algorithms for your calculation of PDPZ,but there must be only one of them for one employee and one payroll period entered ininfotype 0014/0015.
Distribution of company contribution is based on current month's company base (currentmonth's "brutto" in most cases).
If this way of distribution is not acceptable, you can use the FI-CO tools for the distributioninstead.
Retroactive calculationsPDPZ is an external money transfer and as such it may not be changed in the past.Scenarios of the most typical situations when retroactive accounting is triggered: wage type that contributed to company base was increased retroactively
(C) SAP AG 41
=> PDPZ calculated in the past period remains the same, the difference of thecompany base is transferred to current period and added to company base that canbe used for calculation of PDPZ for current period. This is in compliance with thecalculation of pension insurance that is used for the upper flexible limit.The distribution of PDPZ to different WPBP splits and cost centres may changebecause the increase of brutto may change the proportions in the past payroll periods
cost centre of employee was changed retroactively in infotype 0001=> all wage types will remain the same. The distribution of PDPZ will change =>distributed wage type will point to WPBP with different cost centre => during HR-FIposting, the originally posted costs will be reposted to new cost centre(s).
8.1. Customizing of PDPZ
To keep compatibility with previous solution:
Wage typesCustomer copies of "M650 PDPZ Netto" must be assigned to PRCLS 71 = 'A'.New wage types will appear in payroll results: /270 Osnova PDPZ podj/limit - contains:
NUM - company base. During PDPZ calculation it is increased by differencesfrom possible retro calculations. When stored in RT table it contains only thecompany base from current payroll period (retro differences are excluded)
AMT - base for pension insurance with differences from retro calculation - basefor flexible upper limito /272 PDPZ DD Netto - contains netto part of company's PDPZ contributiono /273 PDPZ DD Brutto - contains brutto part of company's PDPZ contribution
(overlimit)o /274 PDPZ DJ - contains difference between company's contribution and
upper limits - the base for employee's contributionThese wage types need not be posted to FI, they exist in the payroll results to documentthe calculation process and to be used as interface for customer enhancements.
SchemasAssuming that you did not modify the SIPD subschema, you need not change anyschema.
RulesAssuming that you did not modify any of the standard rules for PDPZ calculations (SIP*),you need not change any rule.
To use some of prepared algorithms
Fixed value (in EUR) entered in infotype 0014You need not set up anything to allow this option. It is available also for all otheralgorithms bellow - whenever amount is entered in EUR, the calculation is suppressed.
Fixed percentage of upper flexible limit entered in infotype 0014 (compatibility with oldsolution)
o Customer copies of "M650 PDPZ Netto" must be assigned to PRCLS 71 = 'A'.
Fixed percentage of upper flexible limit defined on company level (T510J - wage typeconstants, grouping possible) Percentage must be entered in T510J. Customer copies of "M650 PDPZ Netto" must be changed in T512W:
o Valuation base 0: Base = 'K', Outgoing wage type = none, Percentage = 100%o PRCLS 47 = '6' - this ensures that the percentage is read from T510J and placed
to NUM of the wage typeo PRCLS 71 = 'A' - usage of upper flexible limit is activated
If you enter the percentage to both T510J and to infotype 0014, value from infotype0014 will be used.
(C) SAP AG 42
Fixed percentage of company base entered in infotype 0014 assign your brutto wage types that should be used as a base into one of PRCLS 71
values:'1' - Included into company base before reduction by absences STANDARD
o monthly wage types (abart=3): (wage type value / TSDIVI ) * TSSOLLo hourly wage types (abart=1): value of the wage type * TSSOLL
'2' - Included into company base before reduction by absences SDIVP*SSOLLo monthly employees (abart=3): (wage type value / TSDIVP) * TSSOLLo hourly employees (abart=1): wage type value * TSSOLL
'4' - Included into company base reduced by absencesMarked wage types are summarized into the base regardless of themonthly/hourly characteristic
Customer copies of "M650 PDPZ Netto" must be assigned to PRCLS 71 = 'B'
Fixed percentage of company base defined on company level (T510J - wage typeconstants, grouping possible) assign your brutto wage types that should be used as a base into one of PRCLS 71
values:'1' - Included into company base before reduction by absences STANDARD
o monthly wage types (abart=3): (wage type value / TSDIVI ) * TSSOLLo hourly wage types (abart = 1): wage type valu * TSSOLL
'2' - Included into company base before reduction by absences SDIVP*SSOLLo monthly employees (abart=3): (wage type value / TSDIVP) * TSSOLLo hourly employees (abart=1): wage type value * TSSOLL
'4' - Included into company base reduced by absencesMarked wage types are summarized into the base regardless of themonthly/hourly characteristic
percentage must be entered in T510J. Customer copies of "M650 PDPZ Netto" must be changed in T512W:
o Valuation base 0: Base = 'K', Outgoing wage type = none, Percentage =100%
o PRCLS 47 = '6' - this ensures that the percentage is read from T510J andplaced to NUM of the wage type
o PRCLS 71 = 'B' - usage of company base is activated If you enter the percentage to both T510J and to infotype 14, the value from infotype
0014 will be used.
New wage types will appear in payroll results (on top of those that were described above)
/271 Osnova PDPZ distrib. - in the NUM field you should see the brutto valuesidentical to /270.NUM but splitted by ABART, WPBP and C1 split. Later on it is usedfor cost distribution of PDPZ.
Fixed percentage of difference entered in infotype 0011Use the new value in processing class 64 = "H". Functionality is identical to Trade unions- value can be automatically determined from a base and percentage set in table T7SIV2.You can use /274 as the base. You can also specify the percentage (from the T7SIV2base) in infotype 0011 or to enter the employee's contribution in EUR.
To enhance functionality with customer specificsChanging the company base
Use Subschema SIT0GENPS S** * Generiranje ODU z izmenskimi zamenjavami
PARTT Delni parametri obdobja
PIT SIP4 P71 Baza podjetja za PDPZ I
PIT ZIP4 P71 * Baza podjetja za PDPZ I Customer
(C) SAP AG 43
IF X064 Izvajanje kompenzacije zamenj.izmene
PITAB D DPS Inicializacija tabele DPS
Set PRCLS 71 value to 3 for wage types from which you want to make the base.
This value is reserved for customer algorithms that could be implemented by customercalculation rule placed to place where the "ZIP4" rule is mentioned. The calculation rule mustassure that: all wage types coming on the input appear on the output without any change at the end of the rule, the base for calculation of the contribution of the company must be
placed to: /270.NUM without any splits /271.NUM with ABART, WPBP and C1 splits (ABART, APZNR and C1ZNR)
no other fields in /271 and/or /270 may be filled by this customer ruleSubschema SIAL
PIT SI12 E01 NOAB Prepare brutto (and netto) for trade un
PIT SIP5 P71 NOAB Baza podjetja za PDPZ II
PIT ZIP5 P71 NOAB * Baza podjetja za PDPZ II Custom
COPY XWM0 * Urejanje podatkov za vzdrževanje pla
ENDIF Endif period is special run
PIT X023 P20 NOAB Bruto vnos in skladiš enje
Set PRCLS 71 value to 5 for wage types from which you want to make the base.
This value is reserved for customer algorithms that could be implemented by customercalculation rule placed to place where the "ZIP4" rule is mentioned. The calculation rule mustassure that: all wage types coming on the input appear on the output without any change the base for calculation of the contribution of the company must be placed to:
/270.NUM without any splits /271.NUM with ABART, WPBP and C1 splits (ABART, APZNR and C1ZNR)
no other fields in /271 and/or /270 may be filled by this customer ruleChanging the calculation Base -> PDPZ (total, before checking the limits)
Subschema SIPDSIPCU SIP7 NOAB ..Correct /270 and /271 by retro del
PIT SIP8 P66 NOAB ..Calc.company contribution P66+P71
PIT ZIP8 P66 NOAB * ..Cust.spec.calc.of contrib.ER->/272
PIT SIP9 NOAB ..Overlimit part to /273, check low
Deactivate SIP8 and create customer one (example = ZIP8).
If you want to use the base for pension insurance as a base for PDPZ, use IT./270.AMT.
If you want to use the company base, use IT./270.NUM value. After the SIPCU SIP7 function,value of IT./270.NUM is increased by differences of company base from retro calculation.
Outgoing value is to be written to /272.AMT.
To distinguish between different customer algorithms inside your rule, you can use PRCLS71, values V, W, X, Y, and Z.
Changing the limits
The upper flexible limit is automatically calculated by the system = there is no need to changethis algorithm.
The upper fixed limit and lower fixed limit are not reduced by the delivered standard becauselegislation does not give rules if this reduction is required or not. If you need to reduce thelimits by (for example) hire + fire periods, part-time work, etc. You may perform followingenhancement:
(C) SAP AG 44
Subschema SIPDPIT ZIP8 P66 NOAB * ..Cust.spec.calc.of contrib.ER->/27
ACTIO SIPD ..Put fixed limits to /272.RTE and
ACTIO ZIPD * ..Cust.modifications of fixed limit
PIT SIP9 NOAB ..Overlimit part to /273, check low
After the rule SIPD the fixed limits are stored in wage type /272:NUM = upper fixed limitRTE = lower fixed limit
You can define your own calculation rule (like ZIPD) and reduce the limits. You may changeonly /272.NUM and /272.RTE fields!
Stopping overlimit part from being paid
If you want to automatically stop payment of any overlimit PDPZ contribution etc, you canmake following enhancement:
Subschema SIPDPIT SIP9 NOAB ..Overlimit part to /273, check
ACTIO SIPI * ..Cust rule for stopping overli
SICSP IT /271 NUM ..Create weight table based on
After the rule SIP9 the overlimit part of PDPZ is stored in wage type /273, field AMT. You canmodify the value immediately after this rule or even delete the wage type (if you want to stopany overlimit PDPZ).
Next rule SIPA reads customer copy of M650, reads final netto PDPZ from /272.AMT andsends to Result Table. If there is an overlimit part (/273 exists), it is placed to wage typedefined in T512W (for WT M650) as Valuation base 1 (M350 in template) and sent to ResultTable as well. We do not recommend you to change this algorithm.
Distribution of costs
The distribution to cost centres is performed by function SICSP and by operation SIPA->SIWT. If you would like to perform the distribution of costs in FI-CO (and not to do it inpayroll), please deactivate the function SICSP in the SIPD schema.
Changing the value paid by employee
Create your copy of SI55 rule. Use section valid for PRCLS 64 = H as a template.
Related Documents
