Download - SAP HR Understanding Schema

SAP Labs, Inc.R/3 Simplification Group

Understanding OvertimeSchemas and Rules in Payrolland Time Evaluation

For R/3 Release 3.0 F

Understanding Overtime Schemas and Rules in Payroll and Time EvaluationCopyright

© 1998 SAP Labs, Inc. 1

Copyright

1998 including screenshots by SAP Labs, Inc. All rights reserved.

Neither this documentation nor any part of it may be copied or reproduced in any form or by any means ortranslated into another language, without the prior consent of SAP Labs, Inc.

SAP Labs, Inc. makes no warranties or representations with respect to the content hereof and specificallydisclaims any implied warranties of merchantability or fitness for any particular purpose. SAP Labs, Inc.assumes no responsibility for any errors that may appear in this document. The information contained inthis document is subject to change without notice. SAP Labs, Inc. reserves the right to make any suchchanges without obligation to notify any person of such revision or changes. SAP Labs, Inc. makes nocommitment to keep the information contained herein up to date.

SAP is a registered trademark of SAP Labs, Inc.

All other products mentioned in this documentation are registered or unregistered trademarks of theirrespective companies.

Understanding Overtime Schemas and Rules in Payroll and TimeEvaluation

Understanding Overtime Schemas and Rules in Payroll and Time EvaluationError! No text of specified style in document.

© 1998 SAP Labs, Inc. iii

Understanding Overtime Schemas and Rules in Payroll and Time Evaluation

ContentsIntroduction to Overtime ........................................................................................................................................................................................v

Overview ........................................................................................................................................................................................................... vRelease 3.0F, U.S. Country-Specific................................................................................................................................................................. vWho Should Use This Guide ............................................................................................................................................................................. vSome Commonly Asked Questions.................................................................................................................................................................. vi

On What is an R/3 Overtime Payment Based? ........................................................................................................................................ viHow is the Hourly Rate Calculated?......................................................................................................................................................... viHow is the Hours Threshold Determined?................................................................................................................................................ viHow Can I Configure Overtime According to the FLSA Regulations?...................................................................................................... viWhat If Overtime Is Compensated by Additional Leave or a Combination of Leave and Extra Payments? ........................................... viiWhat If There Are Different Workweek Definitions?................................................................................................................................ viiHow Can I Set Up Different Overtime Rules for the Fifty Unions in My Company? ................................................................................ vii

Chapter 1: Generating Overtime in the System ..........................................................................................................................................1–1Overview .......................................................................................................................................................................................................1–1Automatic Overtime Generation ....................................................................................................................................................................1–1Manual Data Entry.........................................................................................................................................................................................1–1

Chapter 2: Schemas and Rules—The Basics..............................................................................................................................................2–1Overview .......................................................................................................................................................................................................2–1The Payroll Calculation Program...................................................................................................................................................................2–1Schemas .......................................................................................................................................................................................................2–2

Subschema UT00..................................................................................................................................................................................2–3Accessing Schemas and Rules.....................................................................................................................................................................2–5

Accessing Help When Looking at the Source Text ...............................................................................................................................2–5Schemas and Rules Documentation (RPDSYS00).......................................................................................................................................2–5Schema Functions.........................................................................................................................................................................................2–6

Accessing Rules Using Functions PIT and PORT.................................................................................................................................2–7Accessing Rules and Relating Employee Subgroups to Certain Table Settings using Function MOD.................................................2–8Accessing Different Rule Variants .......................................................................................................................................................2–11

Grouping Employees with Different Payment Structures Using Rule Variants and Operation OUTWP .....................................................2–12Grouping Using Rule Variants .............................................................................................................................................................2–12Grouping Using Operation OUTWP ....................................................................................................................................................2–13

Copying and Amending Delivered Schemas and Rules..............................................................................................................................2–15Naming Conventions ...........................................................................................................................................................................2–15

Tracking Customer Schemas and Rules.....................................................................................................................................................2–16Documenting New or Amended Schemas and Rules .................................................................................................................................2–18

Changing the Schema or Rule Description and Documentation .........................................................................................................2–18

Chapter 3: Wage Type Valuation..................................................................................................................................................................3–1Overview .......................................................................................................................................................................................................3–2Number x Rate = Amount..............................................................................................................................................................................3–2Valuation Using Rules ...................................................................................................................................................................................3–2Wage Type Valuation Flow: A High-Level Summary ....................................................................................................................................3–3Wage Type Valuation Flow ...........................................................................................................................................................................3–4

Filling the Payroll Input Table with an Hourly Rate Using Rules X010 and X013..................................................................................3–4Rule X010..............................................................................................................................................................................................3–5Rule X013..............................................................................................................................................................................................3–6Rule X015..............................................................................................................................................................................................3–7


iv © 1998 SAP Labs, Inc.

Rule X016..............................................................................................................................................................................................3–9Rule X017............................................................................................................................................................................................3–10Rule X018............................................................................................................................................................................................3–10

Configuring Wage Type Valuation in the IMG.............................................................................................................................................3–12Create Constant Valuation Bases .......................................................................................................................................................3–12Create Person-Related Valuation Bases (linked to Basic pay) ...........................................................................................................3–19Assign Valuation Bases.......................................................................................................................................................................3–26

Valuating Time Wage Types with Average Amounts over a Given Period .................................................................................................3–29Primary Wage Types to be Included in Evaluation Bases...................................................................................................................3–30Primary (Time) Wage Types to be Evaluated by Averages Processing..............................................................................................3–31

Chapter 4: Calculating Daily and Weekly Overtime....................................................................................................................................4–1Overview .......................................................................................................................................................................................................4–1The Time Evaluation Program.......................................................................................................................................................................4–2Schema TM04 (Negative Time Processing)..................................................................................................................................................4–2The USA Fair Labor Standards Act (FLSA) ..................................................................................................................................................4–2

Federal Law verses State Law ..............................................................................................................................................................4–3Exempt and Nonexempt Employees .....................................................................................................................................................4–3Regular Rate of Pay ..............................................................................................................................................................................4–3

Daily Balance Table TES and Monthly Balance Table SALDO.....................................................................................................................4–4Calculating Weekly Overtime (TW30 or TW20) ............................................................................................................................................4–5

Subschema TW30—Weekly Overtime for Different Workweeks ..........................................................................................................4–6Employees with Workweeks that Have Start Times..............................................................................................................................4–6Employees with Workweeks that Do Not Have Start Times................................................................................................................4–11Subschema TW20: Weekly Overtime for One Workweek...................................................................................................................4–12

Calculating Daily Overtime (Subschema TW15) .........................................................................................................................................4–14Rule TO01 ...........................................................................................................................................................................................4–15Rule TO02 ...........................................................................................................................................................................................4–16

Calculating Overtime Based on Consecutive Attendance Days (TW10).....................................................................................................4–17Rule TW00 ..........................................................................................................................................................................................4–17Rule TO00 ...........................................................................................................................................................................................4–18

Chapter 5: Compensating Overtime with Remuneration or Vacation ......................................................................................................5–1Overview .......................................................................................................................................................................................................5–1Choosing a Compensation Type...................................................................................................................................................................5–2Configuring Processing Class 17 for Overtime Wage Types ........................................................................................................................5–2

Data Flow: Rules TC20, TC21, TC22....................................................................................................................................................5–3Data Flow: TC10, TC11, TC12..............................................................................................................................................................5–3

Configuring Overtime Compensation in Rules TC20, TC21, and TC22........................................................................................................5–3Rule TC20 .............................................................................................................................................................................................5–4Rule TC21 .............................................................................................................................................................................................5–5Rule TC22 .............................................................................................................................................................................................5–6

Configuring Overtime Compensation in Rules TC10, TC11, TC12...............................................................................................................5–7Rule TC10 .............................................................................................................................................................................................5–7Rule TC11 .............................................................................................................................................................................................5–8Rule TC12 .............................................................................................................................................................................................5–9

Chapter 6: Overtime in Schema TM00 (Positive Time Processing) ..........................................................................................................6–1Overview .......................................................................................................................................................................................................6–1Schema TM00—Positive Time Recording ....................................................................................................................................................6–1

Subschema TO00 .................................................................................................................................................................................6–2Subschema TC20..................................................................................................................................................................................6–2


© 1998 SAP Labs, Inc. v

Chapter 7: Main Steps in Overtime Processing, Steps 1–8 .......................................................................................................................7–1Overview .......................................................................................................................................................................................................7–1Steps 1–8: The Time Evaluation Program ....................................................................................................................................................7–1

Schema TM04 .......................................................................................................................................................................................7–2Step 1: Function MOD sets Table Modifiers..........................................................................................................................................7–4Step 2: Hours Collection........................................................................................................................................................................7–5Step 3: Assign Hours to Time Pairs in T555Y .......................................................................................................................................7–5Step 4: Calculate Overtime Hours and Flag Overtime Pairs .................................................................................................................7–9Step 5: Generate Time Wage Types from Time Pairs.........................................................................................................................7–10Step 6: Further Processing of Overtime Wage Types.........................................................................................................................7–15Step 7: Check Overtime Compensation Account ................................................................................................................................7–16Step 8: Export Results to Payroll Input File PCL2. ..............................................................................................................................7–17

Chapter 8: Main Steps in Overtime Processing, Steps 9–16 .....................................................................................................................8–1Overview .......................................................................................................................................................................................................8–1Steps 9–16: The Payroll Calculation Program ..............................................................................................................................................8–1

Step 9: Schema U000—Subschema UODP Imports Data From PCL2 Cluster B2...............................................................................8–2Step 10: Rules X010 and X013 Commence Wage Type Valuation ......................................................................................................8–4Step 11: Function MOD Sets Table Modifiers .......................................................................................................................................8–4Step 12: Import Cluster B2 Data for PDC Employees and Process TC00 ............................................................................................8–5Step 13: Weekly Overtime Analysis ......................................................................................................................................................8–7Step 14: Process Infotype 2010 Data in X930.......................................................................................................................................8–9Step 15: U.S. FLSA Regular Rate of Pay Valuation............................................................................................................................8–10Step 16: The Final Step in Wage Type Valuation, Rule X015.............................................................................................................8–14

Introduction to OvertimeOverview

© 1998 SAP Labs, Inc. v

Introduction to Overtime

ContentsOverview ..................................................................................................................................................................................................................v

Release 3.0F, U.S. Country-Specific......................................................................................................................................................................v

Who Should Use This Guide ..................................................................................................................................................................................v

Some Commonly Asked Questions .....................................................................................................................................................................viWhat is an R/3 Overtime Payment Based On? ................................................................................................................................................ viHow is the Hourly Rate Calculated?................................................................................................................................................................. viHow is the Hours Threshold Determined? ....................................................................................................................................................... viHow Can I Configure Overtime According to the FLSA Regulations? ............................................................................................................. viWhat If Overtime Is Compensated by Additional Leave or a Combination of Leave and Extra Payments? ................................................... viiWhat If There Are Different Workweek Definitions?........................................................................................................................................ viiHow Can I Set Up Different Overtime Rules for the Fifty Unions in My Company? ........................................................................................ vii

Overview

This documentation is intended as an introduction to R/3 overtime configuration. We have approachedthis subject from a business perspective, with specific topics that address the most important issues facedby customers.

Technical detail is provided where necessary. However, it should be noted that the informationsupplements, and does not replace, formal SAP HR and Payroll training courses that provide the correctapproach to learning HR and Payroll configuration. This documentation also does not attempt to explainthe detailed workings of the Payroll Calculation or Time Evaluation programs or how they relate to eachother and the master data. SAP master data, Payroll, and Time Evaluation courses are the prerequisites tousing this documentation.

Release 3.0F, U.S. Country-Specific

This documentation is based on U.S. release 3.0F and explains U.S. overtime business requirements andlegislation. In other countries, business requirements and legislation may differ from those discussed here.Different releases, or different country versions of the system might use the wage types, schemas, and rulesin this document in different ways. Later releases may also contain different configuration solutions to thebusiness requirements discussed in this document. This documentation is a guide to the general workingsof the system, not an exact mapping of the area’s configurations.

Who Should Use This Guide

This documentation is for consultants and customers who are familiar with HR master data and who wantto configure Payroll and Time Management. The majority of customers who implement Payroll willrequire some overtime configuration, so this documentation uses this common customer requirement toexplain the basic workings of the Payroll and Time Management programs.

Introduction to OvertimeSome Commonly Asked Questions

vi © 1998 SAP Labs, Inc.

Anyone relatively new to Payroll and Time Management configuration will find that one of the hardestconcepts to master is how wage types, schemas, and rules work and relate to each other.

This documentation attempts to:

• Introduce this relationship and its impact on overtime configuration

• Explain the operations in the relevant rules

With this information, we hope that beginners will quickly become familiar with the most commonly usedschemas, rules, functions, and operations and will acquire the knowledge to intuitively expand their skillsinto other Payroll and Time Management areas.

Finally, for experienced consultants who need a reliable reference, this documentation should be seen as achecklist to see how schemas and rules are used for particular aspects of overtime configuration. We hopethis documentation will bridge the gap between HR master data configuration and the more complexPayroll and Time Management configuration.

Some Commonly Asked Questions

Overtime configuration depends upon a number of factors that relate to actual customer requirements. Thefollowing business requirements are discussed in this documentation:

On What is an R/3 Overtime Payment Based?Is an R/3 Overtime payment based on a percentage of basic pay a straight amount, regardless of howmany hours are worked (such as a bonus), or is it calculated from the average earnings over a period oftime? See chapter 3, Wage Type Valuation for the various alternatives to see how these payments can beconfigured.

How is the Hourly Rate Calculated?Most overtime calculations involve the use of an hourly rate, which comes from either a percentage of basicpay elements or from an average of basic pay over different periods. R/3 calculates this using wage typevaluation. See chapter 3, Wage Type Valuation for how different hourly rates can be configured.

How is the Hours Threshold Determined?With R/3 you can apply an hours threshold so that the calculated overtime is based on excess hours perday, per week, and so on. See chapter 4, Calculating Overtime on a Daily or Weekly Basis for furtherdetails.

How Can I Configure Overtime According to the FLSA Regulations?Chapter 4 contains a summary of the FLSA regulations and details how the system can be configured tocalculate overtime and comploy with these regulations.

Introduction to OvertimeSome Commonly Asked Questions

© 1998 SAP Labs, Inc. vii

What If Overtime Is Compensated by Additional Leave or a Combination of Leave and ExtraPayments?Each of these options can be configured into an overtime wage type, so that the wage type automaticallybehaves in a certain way when additional hours are worked. See chapter 6, Com pensating Overtime withRemuneration or Vacation for details.

What If There Are Different Workweek Definitions?Your company may have a requirement, for example, to calculate overtime for some workers using aMonday-to-Sunday workweek, while other workers have their overtime calculated using a Sunday-to-Saturday workweek. Chapter 5 contains details on configuring the system to calculate overtime foremployees who have different workweeks.

How Can I Set Up Different Overtime Rules for the Fifty Unions in My Company?Chapter 3, the section Grouping Employees with Different Payment Structures Using Rule Variants andOperation OUTWP describes how you can configure different calculation rules for different groups ofemployees.

Generating Overtime in the SystemOverview

© 1998 SAP Labs, Inc. 1–1

Chapter 1: Generating Overtime in the System

ContentsOverview ..............................................................................................................................................................................................................1–1

Automatic Overtime Generation ........................................................................................................................................................................1–1

Manual Data Entry...............................................................................................................................................................................................1–1

Overview

The system generates overtime details either automatically or manually. Whether you use automaticgeneration or manual data entry depends upon the customer’s needs and the system’s configuration.

Automatic Overtime Generation

When using positive time to record clock-in and clock-out times, you can configure the system toautomatically generate overtime remuneration compensation.

Manual Data Entry

To manually record overtime, the overtime hours, or start-and-end times, enter the information in thefollowing infotypes:

• Infotype 2010 (EE Remuneration)

The user chooses a wage type, it determines the compensation type and rate.

Infotype 2010 also allows the user to choose a premium, which can have different pre-configuredamounts or percentages dependent on different personnel subarea groupings. This premium is not awage type, but would valuate a relevant wage type for an employee.

• Infotype 2005 (Overtime)

The user does not have to choose a wage type. The wage type or time bonus that is generated willdepend on the following type of information:- The employee grouping- The public holiday class- The duration of overtime

• Infotype 2007 (Attendance Quotas)

This infotype enables the user to add a number of hours to quota type 01 (Approved Overtime).

For infotypes 2005 and 2007, the user can choose whether additional hours are rewarded byadditional remuneration, compensation, or both. However, the only wage types that can bevaluated by this choice are those with processing class 17; values 6, 7, 8, and 9; or D, E, and F.This configuration is explained in chapter 5, Compensating Overtime with Remuneration orVacation.

Generating Overtime in the SystemManual Data Entry

1–2 © 1998 SAP Labs, Inc.

• Infotype 2002 (Attendances)

Attendance types can be configured to correspond to time pairs that have processing type M forovertime in T555Y. The user can choose the relevant attendance type, and enter the number of hoursattended for overtime.

Schemas and Rules—The BasicsOverview


Chapter 2: Schemas and Rules—The Basics


The Payroll Calculation Program.......................................................................................................................................................................2–1

Schemas ..............................................................................................................................................................................................................2–2Subschema UT00..........................................................................................................................................................................................2–3

Accessing Schemas and Rules .........................................................................................................................................................................2–5Accessing Help When Looking at the Source Text .......................................................................................................................................2–5

Schemas................................................................................................................................................................................................2–5Rules .....................................................................................................................................................................................................2–5

Schemas and Rules Documentation (RPDSYS00) ...........................................................................................................................................2–5

Schema Functions ..............................................................................................................................................................................................2–6Accessing Rules Using Functions PIT and PORT ........................................................................................................................................2–7

SCHEMA xxxx .......................................................................................................................................................................................2–7Accessing Rules and Relating Employee Subgroups to Certain Table Settings using Function MOD.........................................................2–8Accessing Different Rule Variants...............................................................................................................................................................2–11

Grouping Employees with Different Payment Structures Using Rule Variants and Operation OUTWP ..................................................2–12Grouping Using Rule Variants.....................................................................................................................................................................2–12Grouping Using Operation OUTWP ............................................................................................................................................................2–13

Copying and Amending Delivered Schemas and Rules................................................................................................................................2–15Naming Conventions ...................................................................................................................................................................................2–15

Schemas..............................................................................................................................................................................................2–16Rules ...................................................................................................................................................................................................2–16

Tracking Customer Schemas and Rules ........................................................................................................................................................2–16

Documenting New or Amended Schemas and Rules....................................................................................................................................2–18Changing the Schema or Rule Description and Documentation .................................................................................................................2–18

Overview

The chapters that follow discuss the different Payroll Calculation rules that affect wage type valuation andovertime calculations. These rules are part of the larger Payroll Calculation and Time Evaluation programs.The principals involved in these programs are the same because they each use schemas and rules to call orprocess data.

The Payroll Calculation Program

The Payroll Calculation program evaluates basic employee time data as part of payroll processing andgenerates time wage types so that payments can be made. To understand how schemas and rules worktogether in R/3, we must first examine the Payroll Calculation program. The delivered internationalpayroll program is RPCALCX0.

Schemas and Rules—The BasicsSchemas


Each country has its own specific version of this program, for example:

• RPCALCU0 is the Payroll Calculation program for the U.S.

• RPCALCK0 is the Payroll Calculation program for Canada

When running RPCALCU0, the following selection screen appears:

In the General program control box, notice the field called Schema. The first step of the Payroll program isto choose a schema. This top-level schema contains many subschemas, each of which is responsible forcarrying out a function-dependent task, such as reading the time data and performing tax calculations.

Schemas

The screenshot below shows schema U000 for U.S. payroll. The Func. column lists all of the functions inthis schema and the Text column summarizes the tasks that function is undertaking.



One of the most commonly used functions is Copy,which calls subschemas. Line 000090 on thisscreenshot shows that schema U000 is callingsubschema UT00. If you double-click on UT00, thesystem opens and displays this subschema in detail.

Subschema UT00The screenshot below shows subschema UT00, which processes general time data for the U.S. and callsrules X010, X013, and X015, which are used in wage type valuation.



The function PIT on lines 000100,000110, and 000370 call rules X010,X013, and X015.

If you double-click on any of theseentries, the system opens the rule andshows the decisions and calculationsthat the rule makes. These rules aredescribed in chapter 3, Wage TypeValuation, using screenshots anddetailed explanations.

Schemas and Rules—The BasicsAccessing Schemas and Rules


Accessing Schemas and Rules

Now that you know how schemas and rules work, we encourage you to enter the system, look at someexamples online, and get comfortable with moving around or drilling down. There are two different waysof accessing schemas and rules:

• From the appropriate IMG line (the structured way to approaching your overall configuration)

• Entering Transactions PE01 for a schema or PE02 for a rule

Transactions PE01 and PE02 will take you to the initial schema or rules screen. Enter the name of theschema or rule you want to see and click:

• Source Text and Display to see the actual schema or rule

• Attributes and Display to see the program class and the country grouping

• Documentation and Display to see an overall explanation of what the schema or rule does

Accessing Help When Looking at the Source Text

Schemas

When displaying or changing a schema, click on a function (such as PIT), and then click to see thefunction’s description and how it uses the schema parameters.

Rules

When displaying or changing a rule, click on the name of the operation (such as MODIF), and click tosee the operation’s description and what types of values can be attached to it.

Schemas and Rules Documentation (RPDSYS00)

For releases 2, 3, and 4, schemas and rules documentation can be found in program RPDSYS00. Areplacement for RPDSYS00 is planned in release 4.5A. The documentation discussed on the previous pageis taken directly from RPDSYS00, which contains descriptions of all of the major schemas, rules, functions,and operations in the delivered system.

Schemas and Rules—The BasicsSchema Functions


To look at RPDSYS00 in its entirety:

1. Choose System → Services →Reporting.

2. Enter RPDSYS00 in Program.

3. Click Execute.

4. Click Execute again on the nextscreen to see the screen on theright.

Double-clicking on a line takes you tothe documentation for PersonnelCalculation Schemas, PersonnelCalculation Rules, etc. On this list,notice that RPDSYS00 also contains thedocumentation for Wage Types,Features, etc.

Schema Functions

Schema functions can be divided into the following categories:

• Read data

For example, function P2003 reads data from infotype 2003 (Substitutions). Function WPBP (Wor kPlace Basic Pay) reads data from infotypes 0000, 0001, 0027, 0007, and 0008.

• Process data, including those that call rules

For example, function PIT, which calls rules, or function IMPRT, which imports data to be used in theprogram.

• Display data

For example, function PRINT.

• Set valid entries in tables

For example, function MOD.

Each function uses the schema parameters in different ways. However, there are three functions that youshould be aware of, because they play a major role in deciding which particular wage types a rule shouldprocess or how particular employee groups are affected by certain rules or table settings.

These functions are:

• PIT

• PORT

• MOD

These functions are discussed in detail in the next sections.



Accessing Rules Using Functions PIT and PORTThe screenshot of subschema UT00 showed the calling of rules X010, X013, and X015, using the ProcessInput Table (PIT) function. A similar function, the Process Old Results Table (PORT), calls rules to processold results. These functions use a selection procedure to decide which wage types or employee subgroupsshould be processed by the rule (see the illustration below):

SCHEMA xxxx

FUNCTION PAR 1 PAR 2 PAR 3

Process InputTable

PIT

Process OldResults Table

PORT

OR Name of rule tobe processed.

GEN to process allwage types.

Pnn to only process thewage types with arelevant value inprocessing class nn.

Enn to only processthe wage types with arelevant value inevaluation class nn.

OR

OR

OR

NOAB will processwithout looking forthe employeesubgrouping for PCR(from T503)

1, 2, 3, etc., willprocess according tothe employeesubgrouping for PCRentered here.

OR

Left blank where therule is accessed by aspecific wage type. (Thiswould be stated on thefirst screen of the rule).



Accessing Rules and Relating Employee Subgroups to Certain Table Settings using FunctionMOD

In the screenshot of schema UT00, notice that online 000120, the function MOD calls rule UMOD.Par2 (parameter 2) is marked GEN and behavesin the method set up in the PIT and PORTcharts. It calls all wage types for furtherprocessing, regardless of their processing orevaluation class.

If you double-click on UMOD in schema UT00,the system displays rule UMOD. The ruledetermines different table modifiers, dependingon the Employee Subgroup Grouping forPersonnel Calculation Rules (ESG for PCR),which is configured in the master data. Rulescan be configured to have different variants,depending on the ESG for PCR or the wage andtime type. Maintaining rule variants for specificwage types or time types is quite labor intensive,so this step is something you will not do veryoften. However, maintaining rule variantsaccording to the ESG for PCR is a majorcomponent for how the system fits together.

To illustrate how this process works, see the three sample screenshots from rule $MOD that follow. Each ofthese screenshots show a different variant of rule $MOD. This rule (copied from delivered rule UMOD)only contains one line with three operations, each of which activates a different setting for operationMODIF.



1. Line 000010 on $MOD EmployeeSubgroup Grouping 1 states thatfor all employees with ESG forPCR value 1:

MODIF A = 01

MODIF 2 = 01

MODIF B = 01

2. Line 000010 on $MOD EmployeeSubgroup Grouping 2 states thatfor all employees with ESG forPCR value 2:

MODIF A = 02

MODIF 2 = 02

MODIF B = 02

1

2


2–10 © 1998 SAP Labs, Inc.

3. Line 000010 $MOD EmployeeSubgroup Grouping 3 states thatfor all employees with ESG forPCR value 3:

MODIF A = 03

MODIF 2 = 03

MODIF B = 03

When these screenshots are examined, a certain pattern is apparent. The key to this pattern can be foundby clicking MODIF and click Help, which states that:

• MODIF A= nn

The value entered for MODIF A relates to the absence valuation group value in T554C. An absencevaluation group can have one or more valuation rules attached to it, which determine, for example,how different types of absence should be paid.

• MODIF 2= nn

The value entered for MODIF 2 relates to the payroll modifier in T510J. A payroll modifier can berelated to one or more wage types for constant wage type valuation, where a constant value can be setfor special payments (for example, $50 for working Saturdays).

• MODIF B= nn

The value entered for MODIF B relates to the payroll modifier in table T51D1, which sets limits for netpayroll deductions for different groups of employees.

In examples 1, 2, and 3, the operation MODIF in rule $MOD shows that:

• Employees that belong to ESG for PCR 1 are linked to:- Absence valuation group

01 in T554C- Payroll modifier

01 in T510J- Payroll modifier

01 in T51D1

3


© 1998 SAP Labs, Inc. 2–11




02 in T51D1




03 in T51D1

The above example only describes operations MODIF A, MODIF 2, and MODIF B. There areactually eleven different ways to use MODIF. For additional information, see Help on MODIF.

Function MOD is used by various schemas throughout Payroll and Time Evaluation to call thedifferent rules that use operation MODIF. For example, MODIF appears in rules MODT andTMON in Time Evaluation.

Accessing Different Rule VariantsWhen you first access $MOD, for example, you will see the following screen for ESG for PCR and wagetype or time type.

To select a variant:

1. Click Overview.

2. A pop-up window displays allvariants.

3. Double-click to select the nextvariant.

You can use this method to select a variant in the Display or Change modes.

1

23

Schemas and Rules—The BasicsGrouping Employees with Different Payment Structures Using Rule Variants and Operation OUTWP

2–12 © 1998 SAP Labs, Inc.

4. Once you are in a variant, click and to scroll between variants.

Grouping Employees with Different Payment Structures Using Rule Variants andOperation OUTWP

In the previous section, we saw how different variants of the rule $MOD could be related to differentemployees based on their EE subgrouping for PCR. These relations allow us to have up to nine differentvariants of the same rule (the only ESG allowed for PCR values are 1–9), and this method of configuringvariants can be used with any rule.

In general, rule variants only exist in the delivered system for the rules that need to behave differently forhourly and salaried staff (and for some time type variants that are beyond the scope of thisdocumentation). Therefore, you will find that many rules do not have variants delivered for them.

What if you want your rule to have more than nine variants? What if you have 50 unions in your companyand each one has a different agreement and a different way of calculating overtime? To handle suchsituations, first group using rule variants then group using operation OUTWP.

Grouping Using Rule VariantsFor example, in our 50-union scenario, we recommend analyzing and configuring your rules in thefollowing manner:

1. Analyze which groups of employees are paid hourly and which are salaried, and the different payfrequencies for each.

This portion of your analysis is essential because your hourly paid staff should always be given ESGfor PCR value 1 in master data configuration. The reason for this step is that some rules in the deliveredsystem contain a variant for ESG for PCR value 1 that is configured to process an hourly rate, ratherthan an amount. (These rules are explained in more detail in chapter 3, Wage Type Valuation).

For ESG for PCR values 2–9, the rule variants are configured to process an amount. These valuesshould be assigned to salaried employees. You can change the rule variants for values 2–9 so they relateto hourly rates, but for the purposes of this illustration, we will discuss the rules as they are delivered.

2. At the end of Grouping Using Rule Variants, ensure that your analysis looks like the following:

Hourly staff, weekly paid ESG for PCR value 1

Salaried staff, weekly paid ESG for PCR value 2

Salaried staff, semi-monthly paid ESG for PCR value 3

The analysis so far has only split your employees into three groups. But what do you do if, for example,your hourly staff is subdivided into 46 different groups, each belonging to a different union, and eachunion with a different agreement about how overtime is calculated? What if your staff, who are paid semi-monthly, are subdivided into three different groups, based on the unions to which they belong?


© 1998 SAP Labs, Inc. 2–13

To configure the scenarios in step 2:

3. Configure your employee subgroups in the master data.

In a simple scenario, your employee subgroups could be the same as in step 2 above.

4. Assign the appropriate ESG for PCR value to each EE subgroup.

These assignments automatically relate each EE subgroup to the correct variant in the delivered rulesthat you copy, amend, and rename.

5. For each new rule created, ensure that, where necessary, there are variants for ESG for PCR values 1, 2,and 3.

If some of your customer rules behave similarly for all employees, regardless of their ESG for PCRvalue, do not create variants for those rules, and the rule will be valid for all (ESG for PCR value and W/time type).

Now that you have finished grouping with rule variants, the next stage is to group using operationOUTWP.

Grouping Using Operation OUTWPTo subdivide your hourly paid staff into 46 different types of calculations based on their union, forexample, see the screenshot below that shows the variant for ESG for PCR value 1 for rule $MOD:

Initially, this variant of $MOD had the same settings for all hourly employees, with the followingdefinitions:

• MODIF A = 01 All hourly employees have absence valuation group in T554C

• MODIF 2 = 01 All hourly employees have payroll modifier 01 in T510J

• MODIF B = 01 All hourly employees have payroll modifier 01 in T51D1

What if you want each union to have a different absence valuation group in T554C, a different payrollmodifier in T510J, and a different payroll modifier in T51D1? The next screenshot shows the variant forESG for PCR value 1 for rule $MOD, but it has now been amended using operation OUTWP.


2–14 © 1998 SAP Labs, Inc.

Operation OUTWP is an extremely useful way of getting a rule to make a decision according to thedifferent fields in employee infotype 0001 (Organizational Assignment), infotype 0007 (Planned WorkTime), and infotype 0008 (Basic Pay).

To see a full explanation of OUTWP, examine the documentation in Schemas and Rules Docum entation(RPDYSYS00) of this chapter. That section tells you how to get to RPDSYS00. Once there, double-click onthe Payroll Operations line, and scroll down the list of operations until you see OUTWP. Then double-clickon OUTWP for an explanation of how it works.

In the screenshot of $MOD above, in column T (rule type column), a decision D has been made onoperation OUTWPEMPLR.

This operation comprises:

• OUTWP, the name of the operation

• EMPLR, the name of the field on which OUTWP is making a decision.

EMPLR is the Contract field in infotype 0001. To configure the Contract field, in the IMG, choose PersonnelAdministration and Payroll Accounting → Personnel Administration → Organizational Assignment →Define International Terms of Employment. $MOD is making a decision using the Contract field ininfotype 0001 in the following fashion:

Line VarKey Operation Descriptions

000020 ** If the employee does not have an entry in the Contract field, pass on without furtherprocessing.

000030 01 If the employee has 01 in the Contract field, apply the settings MODIF A = 01,MODIF 2 = 01, and MODIF B = 01.




Lines 000070 and 000080 continue with the same pattern.

Schemas and Rules—The BasicsCopying and Amending Delivered Schemas and Rules

© 1998 SAP Labs, Inc. 2–15

Once you configure the variant for ESG for PCR value 1 for rule $MOD (for hourly employees), go to thevariant for ESG for PCR value 2 (for weekly paid salaried staff), and variant ESG for PCR value 3 (for semi-monthly paid staff) and add the decision configuration described above. Therefore, one way to configurethe rules to behave differently based on the various unions that employees belong to it is to configure theContract field in infotype 0001 to represent a union and then configure rules to make a decision on theContract field, as described above. The Contract field is alphanumeric, which gives you up to 99 differentnumeric variables, and all of the alpha, alphanumeric variables.

You will see from the RPDSYS00 documentation that some of the other fields on which OUTWP can makedecisions include:

• Person subgroup (now renamed employee subgroup)

• Payroll subunit (now renamed payroll area)

• Plant section (now renamed personnel subarea)

• Company code

• Cost center

• Shift indicator

• Pay scale type, area, group, or level

You, therefore, have many ways to configure your master data decisions and your employee infotypefields.

Copying and Amending Delivered Schemas and Rules

Whenever you configure schemas and rules, first try to find the schema or rule that closely fits yourrequirements, then copy and rename it. Your new configuration should be written to your new renamedschema or rule.

Never configure your customer requirements into a delivered schema or rule without firstcopying and renaming it as described above! We stress this cautionary statement for thefollowing reasons:

• If you do not copy and rename the schema or rule, you will be unable to compare yourcustomer configuration against the delivered configuration if you get errors.

• When upgrading your system, all delivered schemas and rules will be overwritten by theirnamesakes in the new version. However, your renamed customer schemas and rules willnot be affected.

Naming ConventionsTo make your new schemas and rules identifiable and to protect them from being overwritten by futuresystem upgrades always make the first character in your renamed schema or rule a special character (forexample, do not use numbers or letters).

We recommend the following naming conventions:

Schemas and Rules—The BasicsTracking Customer Schemas and Rules

2–16 © 1998 SAP Labs, Inc.

Schemas• When copying and renaming an SAP-delivered schema, replace the first character of the name with a

“ /.” For example, TM04 should be copied and renamed /M 04.

• New customer schemas should also begin with “/.”

Rules

• When copying and renaming an SAP-delivered rule, replace the first character of the name with $.

For example, X010 should be copied and renamed $010.

• When creating a new customer rule, the name should begin with an &.

Tracking Customer Schemas and Rules

If the naming conventions above are followed, to quickly access customer-configured schemas and rules:

1. Enter Transaction PE01 forschemas or PE02 for rules.

2. In the initial screen, if a schema orrule appears, delete the name.

3. Click possible entries.3

1

2

Schemas and Rules—The BasicsTracking Customer Schemas and Rules

© 1998 SAP Labs, Inc. 2–17

4. Enter, for example, $* for a list ofall rules that have been copied andrenamed, or &* to see all rulescreated from scratch.

5. Click Execute.

6. In Program class, to further restrictthe options for Payroll or TimeManagement rules, enter C forPayroll or T for TimeManagement.

7. Click possible entries.

8. In the pop-up window, double-click on 3.

9. Click Enter.

46

9

8

7

5

Schemas and Rules—The BasicsDocumenting New or Amended Schemas and Rules

2–18 © 1998 SAP Labs, Inc.

Documenting New or Amended Schemas and Rules

In addition to renaming your customer-configured schemas and rules, you should also document theirnew or changed functionality. To do this, change both the description and documentation for the schemaor rule.

Changing the Schema or Rule Description and DocumentationEvery schema and rule has a description attached to its name on the initial screen. For example, ruleUMOD is described as Modifiers for Payroll Accounting. If you copy and change UMOD to $MOD, alsochange its description to Modifiers for Payroll Accounting: Copy of UMOD. This way, anyone trackingyour customer configuration can instantly see from which rule your customer rule was copied.

You should also document the new or changed functionality for your new schema or rule, so that yourcustomer configuration is transparent to someone who will be changing the original customerrequirements.

To change your schema or rule description:

1. Enter Transaction PE01 forschemas and PE02 for rules.

2. Enter the name of your customerschema or rule (such as $MOD).

3. Select Documentation.

4. Click Change.

5. If you have copied an existingschema or rule, you will then seeits documentation.

6. Select the heading in thedocumentation (for example,Modifiers for Payroll Accounting,if you copied and renamedUMOD).

7. Click Edit.

You would then see the screensimilar to the one on the right.

8. Double-click on <== output.

9. Click Enter to see the followingscreen. The line marked H is theheading.

1

3

2

4

9

8

Schemas and Rules—The BasicsDocumenting New or Amended Schemas and Rules

© 1998 SAP Labs, Inc. 2–19

10. In this example, on 000010, entercopy of UMOD.

11. Click Save.

12. To see the results of your change,return to the initial screen, whereyour amended description will bedisplayed.

To change your documentation:

1. Follow steps 1–5 above, except in step 5, select a line in the documentation, not the heading.

2. Then follow steps 6–9 above, andyou will see this screen.

3. Click on the line where you wantto add text (for example 000080)and click Insert Line . (Each

click adds a new line.) Then addyour new documentation.

4. When you have finished, clickSave. To view your newdocumentation, return to theinitial screen and clickDocumentation and Display.

When you save your new documentation, the system will concatenate your lines. To preventthe first three characters of your documentation from disappearing, insert three spaces at thebeginning of each line. To insert spaces between your lines, to represent new paragraphs, forexample, add a “ / ” at the beginning of the line. This is basic SAPscript coding.

11

10

3

4

Wage Type ValuationOverview


Chapter 3: Wage Type Valuation


Number x Rate = Amount ...................................................................................................................................................................................3–2

Valuation Using Rules ........................................................................................................................................................................................3–2

Wage Type Valuation Flow: A High-Level Summary .......................................................................................................................................3–3

Wage Type Valuation Flow.................................................................................................................................................................................3–4Filling the Payroll Input Table with an Hourly Rate Using Rules X010 and X013 .........................................................................................3–4Rule X010......................................................................................................................................................................................................3–5Rule X013......................................................................................................................................................................................................3–6

Variant for ESG for PCR 1.....................................................................................................................................................................3–6Variant for ESG for PCR 2.....................................................................................................................................................................3–6

Rule X015......................................................................................................................................................................................................3–7Variant for ESG for PCR 1.....................................................................................................................................................................3–7Variant for ESG for PCR 2-9 .................................................................................................................................................................3–9

Rule X016......................................................................................................................................................................................................3–9Rule X017....................................................................................................................................................................................................3–10Rule X018....................................................................................................................................................................................................3–10

Configuring Wage Type Valuation in the IMG ................................................................................................................................................3–12Create Constant Valuation Bases ...............................................................................................................................................................3–12

Constants Dependant on Wage Types................................................................................................................................................3–13Constants Dependant on the Pay Scale..............................................................................................................................................3–18

Create Person-Related Valuation Bases (linked to Basic pay) ...................................................................................................................3–19Maintain Basic Pay for Valuation Basis ...............................................................................................................................................3–20Form Valuation Bases (Addition).........................................................................................................................................................3–21Form Valuation Bases (Division) .........................................................................................................................................................3–23General Processing of Time Data USA...............................................................................................................................................3–24

Assign Valuation Bases...............................................................................................................................................................................3–26Current Wage Type .............................................................................................................................................................................3–281st Derived Wage Type.......................................................................................................................................................................3–292nd-Derived Wage Type......................................................................................................................................................................3–29

Valuating Time Wage Types with Average Amounts over a Given Period..................................................................................................3–29Primary Wage Types to be Included in Evaluation Bases...........................................................................................................................3–30Primary (Time) Wage Types to be Evaluated by Averages Processing......................................................................................................3–31

T511A: Averages Calculation Rules....................................................................................................................................................3–36T511B: Cumulation Types...................................................................................................................................................................3–38T511C: Adjustment Rules for Averages Bases ...................................................................................................................................3–38T510C: Adjust Average Bases according to Pay Scale.......................................................................................................................3–39

Wage Type ValuationOverview


Overview

Wage type valuation is used to calculate different payment amounts for either basic working hours orchanges in an employee’s work patterns. For example, if extra hours are worked, or, if an employee goeson long- or short-term disability leave, their rate of pay may change.

Wage type valuaton is used to calculate different payment amounts for either basic working hours orchanges in an employee’s work pattern. A time wage type is generated for the number of hours for aparticular type of time (e.g., overtime, holidays, absences, and so on).

Number x Rate = Amount

In the overtime example, wage type valuation takes the Number of hours generated for an overtime wagetype in Time Management and then looks at the valuation basis configured for that wage type. Thisvaluation basis is how the system calculates the Rate for overtime pay.

The following is a list of valuation bases that can be configured for time wage types:

• An hourly Rate based on basic payThe time wage type is configured with a valuation basis of nn that corresponds to a technical wagetype. The accumulating basic pay amounts are then divided by the total hours worked in rule X013 toget an hourly Rate. For detailed information on rule X013, please see the following page.

• A constant amount stored in a tableThe time wage type is configured with a valuation basis of K, where the Rate for the time wage type isa set amount stored in table T510J.

• A constant amount based on a pay scale group and levelThe time wage type is configured with a valuation basis of TS, where the Rate for the time wage type isa set pay scale level amount from the pay scale table.

• A constant amount based on a pay scale groupThe time wage type is configured with a valuation basis of TG, where the Rate for the time wage typeis a set pay scale group amount from the pay scale table.

• A constant amount according to a pay scale type and areaThe time wage type is configured with a valuation basis of T, where the Rate for the time wage type isa set amount stored for a particular pay scale type and area.

Once the system has the Number of hours (from the time wage type) and the Rate (from the time wagetype’s valuation basis), it multiplies N x R to get the Amount to be paid.

Valuation Using Rules

Wage type valuation is processed by the system using several different rules that work together to form avaluation flow. The next section provides a high-level summary explaining how this valuation flow fitstogether. The following section provides rule-by-rule details of the valuation flow, with charts andscreenshots. The final section in this chapter explains how the valuation flow is configured in the IMG.

Wage Type ValuationWage Type Valuation Flow: A High-Level Summary


Wage Type Valuation Flow: A High-Level Summary

The delivered R/3 system contains a set of Payroll Calculation rules and technical wage types that are pre-configured to enable wage type valuation to work in different ways.

The following list summarizes the main valuation flow in the following rules:

• Rule X010

This rule places amounts in technical wage types /00n, to calculate the hourly Rate. This rule looks forbasic pay wage types with processing class 01 values 1–4, and places these wage type amounts intocertain technical wage types, such as /001, /002, /003, and /004, depending on the PC01 value.

• Rule X013This rule calculates an hourly rate. It looks for wage types with a processing class 01 value of 5. Youwill usually find only technical wage types /001, 2, 3, and 4 with this value. The rule takes the amountsfrom these wage types and calculates an hourly Rate to be used in further processing. The exception tothis rule is the X013 variant for ESG for PCR 1, which processes hourly employees. Wage types forthese employees already contain the hourly rate, so the types are passed on unprocessed by X013. Theflowchart, Filling the Input table with Hourly Rate in this chapter illustrates how rules X010 and X013work together.

• Rule X015

This rule first checks if the wage type already has an Amount. If it does, the wage type is passed onwithout additional processing. If the wage type does not have an Amount, the rule checks if the wagetype has a Number of hours. If hours have been entered by a user or generated in Time Management,the rule checks if a Rate has been entered.

If the user enters a Rate in infotype 2010, the rule multiplies the Number of hours by the hourly Rate toget an Amount for the payroll output table. If the user has not entered a Rate, the rule checks if thewage type has a valuation basis. If the wage type does not have a valuation basis, it branches to ruleX016, to see if this rule is configured for averages processing. If the wage type has a valuation basis, thisbasis is applied appropriately to one or more of the following:- Base wage type- First-derived wage type- Second-derived wage typeIf the valuation basis is nn, the Rate will come from X013. If there is nothing in the Amount andNumber fields, the wage type is passed on without further processing.

• Rules X016, X017, and X018

These rules do averages processing. Rule X016 checks if the wage type has a value in processing class15:- If the wage type does not, the wage type is passed on without further processing.- If it has a PC15 value, the wage type is processed by the appropriate averages rule in T511, which

first processes X017 for the period’s relevancy test, then processes X018 to calculate the averagehourly Rate. The wage type is passed back to X016, which multiplies the Number of hours and theRate to get the Amount.

Wage Type ValuationWage Type Valuation Flow


Wage Type Valuation Flow

This section uses screenshots and charts to describe the wage type valuation flow. To understand how thisvaluation flow moves from rule to rule, review the following flowchart:

Filling the Payroll Input Table with an Hourly Rate Using Rules X010 and X013

1.

2.

Rule X010 (in schema UT00) looks forwage types with processing class 01values 0, 1, 2, 3, or 4.

Wage types with value 0are not included in thevaluation.

Creates valuationbasis in wage type/001

Creates valuationbasis in wage types/001 and /002


Value 1 Value 2 Value 3 Value 4

Rule X013 looks for wage types withprocessing class 01 value 5 (usually /001,/002, /003, or /004).

Value 5

Rule X013 performs the following operationson the selected wage type.

Operation:RTE=TSDIVP

This operationdecides whichset of hoursshould be usedfor the hourlycalculation.

Operation: DIVID ARR

This calculationdecides thehourly rate.

Operation:ZERO = A

This operationensures that theoriginal amount(before thecalculations) isnot sent to theoutput table.

Operation:ADDWT *

This operationadds the resultof DIVID ARRto the outputtable.

1st 2nd 3rd 4th

then then then

RTE is the rate.TSDIVP is what therate should be. In thiscase TSDIVP means“total working timein working hours.”

Use DIVID to divide.ARR is to divide theAmount of the wagetype by the Rate ofthe first operation,and store the resultin the Rate field ofthe output table.

ZERO is to initialize(make zero) in theoutput table. A is thetotal amount thatshould be initialized.

ADDWT means add tothe wage type.

* means add to this wagetype, (the result couldhave been added to adifferent wage type).




Rule X010All of the delivered variants for rule X010 (for ESG for PCR values 1–9) must be configured as you see inthe following screen:

Although the coding looks complex, you can see what the rule is doing by placing the cursor on eachoperation and clicking Help.

The following table explains the lines in the screenshot above:

Line Operation Descriptions

000010 This line contains the decision (D) operation VWTCL. This operation makes decisions based onthe processing class 01 value assigned to the selected wage type(s).

000020 This line states that if the wage type has one of the following values [(*) 4,5,6,7,8, or 9] againstprocessing class 01, the system should produce an error message. Processing would thenterminate for this personnel number.

000030 This line states that if the wage type has value 0 against processing class 01, its amount shouldbe transferred to the output table without further processing by this rule (ADDWT *).

000040 This line means that if the wage type has value 1 against processing class 01, the value of thewage type should be added to the output table (ADDWT *). ELIMI means that the periodindicators should be removed from the wage type time unit (Z). This removal is requiredbefore values from different wage types can be combined for valuation calculations. ZERO= Nmeans that the number field (N) should be reduced to zero in the output table. ADDWT /001states that the value of the wage type should also be copied to wage type /001 in the outputtable.

000050and000060

These lines are similar to line 000040, except that the value of the wage type is copied to wagetypes /002, and wage types / 001 and / 002 in the output table.



Rule X013Rule X013 is delivered with two different configurations:

Variant for ESG for PCR 1

This variant is for hourly employees.

Rule X013 calculates the hourly Rate. Since hourly employees already have hourly Rates, this variant isconfigured to pass on wage types for hourly employees without further processing.

Lines Operation Descriptions

000010 This line contains the decision (D) operation VWTCL, which makes decisions based on theprocessing class 01 value assigned to the selected wage type(s).

000020 This line states that, regardless of the value against processing class 01, the amount shouldbe passed on to the output table without further processing, (ADDWT *).


This variant is for salaried employees, and the delivered variants for ESG for PCR 2–9 should beconfigured as in the following screenshot:



Lines Operation Descriptions

000010 This line again contains the decision (D) operation VWTCL and makes a decision based onthe processing class 01 value assigned to the selected wage type(s).

000020 This line states that if the wage type has a value other than 5 (*) against processing class 01,its amount should be transferred to the output table without further processing by this rule(ADDWT *).

000030 This line calculates the hourly Rate. The flowchart in the beginning of this chapter, Fillingthe Payroll Input Table with an Hourly Rate, summarizes how rules X010 and X013 worktogether to determine hourly rate calculations.

Rule X015As we have seen in the previous pages, the result of the X010 and X013 processing is an hourly Rate for agiven wage type. However, the hourly Rate calculation in X013 is only one of several different ways tocalculate the Rate. Rule X015 examines which evaluation basis have been configured for the wage typebeing processed and then applies the valuation basis to this type.


The next screenshot shows the X015 variant for ESG for PCR 1 (hourly employees). Variants for ESG forPCR 2–9 (salaried employees) behave in almost the same way. The following screenshot will help explainhow rule X015 works:




000010 The rule makes a decision (D) on the amount field of the wage type (AMT?0) by comparing theamount stored in the wage type to zero.

000020 The “*” means if the wage type already has an Amount (*), it does not need any furtherprocessing for wage type valuation. It is passed on to the payroll output table without furtherprocessing (ADDWT).

000030 The “=” means if the wage type does not have an Amount (for example, if AMT = 0), the rulemakes a decision (D) on the Number field of the wage type (NUM?0).

The “=” means that the wage type does not have an amount.

The “*” means that NUM is not equal to zero, so a decision (D) is made to compare RTC to zero(RTE?0).

000040 The “= *” means the rule makes a decision (D) on the rate field of the wage type RTE?0 if thewage type:

• Does not have an Amount (for example, if AMT= 0)

• Does have the Number of hours entered by a user or generated by the system [NUM issomething (*)]

000050 The “= * *” means the rule multiplies the Number and the Rate and adds the resulting Amount(MULTI NRA) to the output table (ADDWT *) if the wage type:

• Does not have an Amount (for example, if AMT= 0)

• Does have the Number of hours entered by a user or generated by the system [NUM issomething (*)]

• Has a Rate that would have been entered by a user in infotype 2010

000060 The “= * =” means the rule makes a decision (D) on the valuation basis of the wage type(VALBS?) if the:

• Wage type does not have an Amount (for example, if AMT= 0)

• Wage type does have the Number of hours entered by a user or generated by the system[NUM is something (*)]

• User has not entered a Rate in infotype 2010

000070 The “= * = *” means the rule branches to rule X016 and checks for averages processing if the:


• Wage type does have the Number of hours entered by a user or generated by the system[NUM is something (*)]

• User has not entered a Rate in infotype 2010 (such as RTE = 0)

• Wage type does not have a valuation basis (such as VALBS is something other than X)

000080 The “= * = X” means if the:


• Wage type had the Number of hours entered by a user or generated by the system [NUM issomething (*)]




• User has not entered a rate in infotype 2010, and the wage type has a valuation basis (suchas VALBS = X)

Then:1. VALBS0 means the base (current) wage type is valuated according to its valuation basis.

(For example, the base wage type takes its Rate from basic pay nn—or from a constantamount—and multiplies it by the Number of hours to get the Amount.) If the valuationbasis is nn, the Rate will come from X013.

2. ADDNA adds the Number and the Amount to the output table.3. FILLF N restores the original value of the wage type number.4. WGTYP=* places the current wage type in the output table.5. NEXTR means continue onto the next line.

000090 This line is the same as line 000080, except that the first-derived wage type is valuated(VALBS1).

000100 This line is the same as 000090, except that the second-derived wage type is valuated.

000110 The “= =” means if the wage type does not have an Amount or a number, it should be passedon without further processing.

Variant for ESG for PCR 2-9

This variant, for salaried employees, follows the same process as the variant described above. Thedifference for this variant occurs in line 000080, where it branches to rule X115 to process wage types thathave a valuation basis. Rule X115 makes a decision on alternative payments (VAKEYALZNR), andprocessing class 18 (VWTCL 18), which is used to process workcenter-related remuneration beforeprocessing VALBS0, VALBS1, and VALBS2 as described for the previous variant.

Rule X016Rule X016 is the first step in averages processing, but there are no variants for X016. This rule, therefore,processes all ESG for PCR values the same way.


3–10 © 1998 SAP Labs, Inc.


000010 The rule makes a decision (D) on the wage type processing class 15 value (VWTCL 15)

000020 For all PC15 values other than 1, 2, or A, the wage type is added to the output table withoutfurther processing (ADDWT *).

000030 For wage types with processing class 15 value 1, MEANV 01 processes the wage type based oncalculation rule 01 in table T511A. Calculation rule 01 from T511A in the delivered system thenprocesses rule X017 for the relevancy test and X018 for final processing. Rule X018 takes thecumulated value in the Amount field of the cumulation table for averages calculation (tableMV) and divides it by the cumulated value in the Number field of table MV. The result is a Ratethat gets re-entered in X016 as the Rate in operation MULTI NRA. MULTI NRA multiplies theNumber of hours by the Rate calculated in X018 to get an Amount. ADDNA * cumulates theNumber and the Amount (but not the Rate) in the output table for the current wage type.

000040 For wage types with processing class value 2, MEANV 02 processes the wage type according tocalculation rule 02 in T511A. The processing is the same as line 000030.

000050 –000090

These lines relate to the frozen averages calculations that are outside of the scope of thisdocument.

Rule X017Rule X017 contains operation MEANV REL, which checks for relevant periods for averages processing. Inthe delivered system, this operation is configured to treat all periods as relevant. For an example of anactual relevancy test, please see rule X019.

Rule X018Rule X018 is ready, as delivered, to process the final averages calculation (see the section on rule X016above for more information).


© 1998 SAP Labs, Inc. 3–11

A wage type is sent to this rule by calculation rules 01 and 02 in T511A.


000010 NUM=M takes the Number from the accumulated value in the number field of table MV,(cumulation table for averages calculation). This is the accumulated number of hours from thetechnical wage types specified in the relevant cumulation rule in T511A. NUM?0.00 compares thehours of the previous operation to zero.

000020 If there are hours in the number field of table MV (*):

• AMT=M takes the Amount accumulated in table MV, and puts it in the Amount field of thenext operation.

• DIVID ANR takes the Amount accumulated in MV and divides it by the Number of hoursaccumulated in MV to get the Rate used in operation MULTI NRA in rule X016 (as describedabove).

000030 If there are no hours in the number field of MV (= 0,00), there is no averages calculation.

Wage Type ValuationConfiguring Wage Type Valuation in the IMG

3–12 © 1998 SAP Labs, Inc.

Configuring Wage Type Valuation in the IMG

To access the main valuation options, choose IMG → Personnel Administration and Payroll Accounting →Payroll: USA →Time Wage Type Valuation → Create Valuation Bases.

Beneath Create Valuation Bases, theoptions are:

• Create Constant Valuation Bases

• Create person-related valuationbases

• Assign valuation bases

The following sections will explaineach of these options and describe thesubsequent screens.

Create Constant Valuation BasesConstant valuation enables you toconfigure time wage types that, ifcertain qualifying times are worked,have a fixed value. There are twoways these wage types can beconfigured, through:

• Constants dependent on wagetypes (U.S.)

• Constants dependent on wagetypes (Canada)

• Constants dependent on the payscale


© 1998 SAP Labs, Inc. 3–13

Constants Dependant on Wage Types

This option under Create Constant Valuation Bases on the previous screen allows you to configure fixedpayments with wage types (for example, a $50 bonus for working on Saturday, a $100 weekend allowance,and an $80 nightshift allowance).

On the previous screen, place yourcursor on the line Constantsdependant on wage types and clickExecute. Three additional optionsappear:

• Modifier for constant evaluation

• General processing of time dataUSA

• Determine constant valuation perwage type

Determine Constant Valuation per Wage Type

First choose the Determine constant valuation per wage type line on the above screen.

1. Place your cursor on Determineconstant valuation per wage type,and click Choose.

2. Specify the Country grouping(such as 10 for the U.S.) by usingpossible entries or entering theproper number.

3. Click Continue.

You are taken to a country-specificview of T510J (constantvaluations).

1

2

1

3


3–14 © 1998 SAP Labs, Inc.

4. Earlier in your configuration, bychoosing Environment forMaintaining Wage Types, youwould have analyzed andconfigured the different timerelated fixed payment wage typesneeded in your company.

5. New wage types created for thispayment type can be copied fromthe delivered wage type MM00(overtime base). Any wage typecopied from MM00 should nowappear in this view of T510J.

Now analyze two additionalitems. If you created a wage typefor working on Saturday, willdifferent staff groups receivedifferent amounts? (For example,your hourly employees receive$40, and your salaried employeesreceive $50 for working onSaturday). If so, create copies ofthis wage type.

6. To create copies, select the wagetype and click Copy.

7. Do not change the name, but giveeach copy:

• The correct amount underValue

• A new P. Mod number (thenext section has moreinformation on P. Mods)

5

6

7


© 1998 SAP Labs, Inc. 3–15

Modifier for Constant Evaluation

This option is listed under Constants dependant on wage types.

1. Place your cursor on Modifier forconstant evaluation, and clickChoose.

2. This option takes you to ruleUMOD, explained in detail inchapter 2, the section AccessingRules, and Relating EmployeeSubgroups to Certain TableSettings using Function MOD.Chapter 2 shows that UMODcontains operation MODIF 2 thatrelates to the payroll modifier P.Mod you created in T510J. MODIF2 = can relate up to 99 different P.Mod numbers in T510J. You cancreate up to 99 different amountsfor your Saturday working wagetype in T510J, and with MODIF 2,assign them to different groups ofemployees.

3. To copy UMOD, click Copy.

4. In To rule, rename it /MOD.

5. Click Continue.

1

1

3

4

5


3–16 © 1998 SAP Labs, Inc.

6. Create variants of this rule foreach of your employeesubgroupings for PCR, based onthe Grouping Employees withDifferent Payment Structuresguidelines in chapter 2.

If necessary, using theseguidelines, configure operationOUTWP to make additionaldecisions on your employeegroupings.

7. Amend operation MODIF2=nn,for each employee grouping, sothat nn corresponds to theappropriate P. Mod number andvalue in T510J.

General Processing of Time Data USA

This option also appears under the line Constants depen dant on wage types.

1. Place your cursor on Generalprocessing of time data USA andclick choose.

6

1

1


© 1998 SAP Labs, Inc. 3–17

2. This action takes you to schemaUT00 (see chapter 2 for details).This subschema calls rule UMODwith function MOD.

3. Choose Edit → Replace to replacethe entry UMOD with yourrenamed /MOD.

4. In Search, enter UMOD.

5. In Replace using, enter /013.

6. Click Continue.

2

3

4

6

5


3–18 © 1998 SAP Labs, Inc.

7. UMOD has been replaced by/ MOD.

Constants Dependant on the Pay Scale

This line appears last under Create Constant Valuation Bases. This option enables you to configure payscale groups, or groups and levels for fixed payments.

1. Click Execute next to Constantsdependent on the pay scale.

7


© 1998 SAP Labs, Inc. 3–19

2. Enter the Country grouping.

3. Enter the Pay scale type.

4. Enter the Pay scale area.

These items should have alreadybeen configured. (To configurethese items, choose PersonnelAdministration → Payroll Data →Basic Pay.)

5. Click Enter.

6. Create entries for the pay scalegroups or the levels you wouldlike valuated.

Create Person-Related Valuation Bases (linked to Basic pay)The first Create person-relatedvaluation bases line represents one ofthree options when configuring wagetype valuation in the IMG. This optionenables you to choose one or morebasic pay wage types, and assign theiramount to a technical wage type (forexample, /001), which is then used tocalculate an hourly rate for overtimeor other calculations.

1. Click Execute next to the firstCreate person-related valuationbases line.

4

5

2

3

1


3–20 © 1998 SAP Labs, Inc.

2. This action takes you to a screenwith a list of four options.

Maintain Basic Pay for Valuation Basis

1. In the above screen, place yourcursor on Maintain basic pay forvaluation bases, and click Choose.

2. Select the Country grouping andclick Continue.

A screen appears with the wagetypes configured for basic payinfotype 0008.

3. Select a wage type.

4. Click Details.

You will then see the processingclass 01 value for the wage type.Processing class 01 determines theassignment of this wage type to avaluation base.

2

4

3


© 1998 SAP Labs, Inc. 3–21

5. Click on possible entries to see theavailable valuation bases.

6. Choose the technical wage type( /001, /002, etc.) that your wagetype will valuate.

7. Click Enter.

If you need to select values other than 1–3, rule X010 will need to be changed in the next step.

Form Valuation Bases (Addition)

Two Form valuation bases lines appear under Create person-related valuation bases, one for division andthe other for addition. The addition option takes you to rule X010 (see Wage Type Valuation Flow earlierthis chapter for a full explanation of how this works). Rule X010 processes the /00 1 and /00 2 technicalwage types selected in the previous step with processing class 01.

5

6

7


3–22 © 1998 SAP Labs, Inc.

1. Place your cursor on Formvaluation bases (addition), andclick Choose.

2. To copy rule X010, click Copy.

3. In To rule, rename it /010.

4. Click Continue.

5. If necessary, amend the rule andits links to the processing class 01values.

6. If you are working in yourRecording client, you will see thescreen to the right.

1

1

3

2

4

6


© 1998 SAP Labs, Inc. 3–23

Form Valuation Bases (Division)

The other Form valuation bases line appearing under Create person-related valuation bases is for division.This option takes you to rule X013 (see Wage Type Valuation Flow earlier this chapter for a detaileddescription of rules X010 and X013). You will see from these descriptions that rule X013 has differentvariants for hourly employees (variant ESG for PCR 1) and salaried employees (variant ESG for PCR 2–9).Rule X013 calculates hourly rates, and because hourly staff already have hourly rates, the variant forhourly staff is configured to pass data on without further processing (ADDWT *). Your configuration inthis view relates only to salaried employees.

Operation RTE=TSDIVP states that the amount in technical wage type /0 01 should be divided by the totalworking time in working hours to get an hourly rate. The total working time (TSDIVP) is taken from thefield Working Hours per Payroll Period in infotype 0008. To find out the other ways that operation RTEcalculates the hourly rate, please see the operation Help.

Complete the following steps:

1. Place your cursor on Formvaluation bases (division) andclick Choose.

2. Select the Country grouping andclick Continue.

3. To copy rule X013, click Copy.

4. In To rule, enter /013.

5. Click Continue.

1

1

3

45


3–24 © 1998 SAP Labs, Inc.

You will see the screen to theright.

6. Create variants of this rule for each of your employee sub-groupings for PCR 2–9.

7. If RTE=TSDIVP is the correct hourly calculation for each EESG for PCR 2–9, no further action isnecessary.

8. If different calculations are needed for different EESGs for PCR, change RTE= as appropriate for eachrule variant.

General Processing of Time Data USA

This line is the third option under Create person-related valuation bases. This choice takes you tosubschema UT00.

1. Place your cursor on Generalprocessing of time data USA andclick Choose.

1

1


© 1998 SAP Labs, Inc. 3–25

2. This action takes you tosubschema UT00 (see chapter 2 fordetails).

3. This subschema calls rule X013with function PIT.

4. Choose Edit → Replace to replacethe entry X013 with your renamed/ 013.

5. In Search, enter X013.

6. In Replace using, enter /013.

7. Click Continue.

2

3

4

5

67


3–26 © 1998 SAP Labs, Inc.

9. / 013 has replaced X013.

Assign Valuation BasesThe line Assign valuation bases is the last option when configuring wage type valuation in the IMG. Bythis point, you have successfully configured your different valuation bases. You must now assign thosevaluation bases to the appropriate overtime (time) wage types. Some time wage types might need:

• Constant valuation based on wage types

• Constant valuation based on basic pay

• Person-related valuation basis

1. Click Execute next to Assignvaluation bases.

2. Select the Country grouping, andclick Continue.

9


© 1998 SAP Labs, Inc. 3–27

3. Select a wage type.

4. Click Details.

The Change View “ValuationBases”: Details window appears.The configuration for the fields onthis screen is described below.

4

3


3–28 © 1998 SAP Labs, Inc.

Current Wage Type

The Current wage type box shows the valuation for the currently selected time wage type, displayed at thetop of the screen. In this box are the Valuation basis, StatemntWT, and %rate fields:

• Valuation Basis

The selected valuation basis is used by the displayed wage type. In this basis, the following options areavailable:- nn

A numeric entry relates to the secondary wage type from which this wage type takes its value. Forexample, 01 is technical wage type / 001, and 02 is technical wage type /0 02. If an entry appears, thecurrent wage type will multiply the Number of hours and the Rate calculated in rule X013 (theresult of operation DIVID ARR) to get the Amount.

- KThis option signifies that the wage type will take its valuation from the appropriate line in T510J, asdescribed in the entries under the Constants Dependant on Wage Types line earlier this section.

- TSThis valuation basis means that the wage type takes its valuation from the appropriate line inConstants Dependant on the Pay Scale and takes into account the pay scale group and level.

- TGThis option means that the wage type takes its valuation from the appropriate line in ConstantsDependant on the Pay Scale and takes into account the pay scale group, but not the level.

- TThis option signifies that the wage type takes its valuation from the appropriate line in ConstantsDependant on the Pay Scale and takes into account the pay type, area, and wage type, but not thepay scale group or level.

• StatemnWT

This is the wage type where the result of the chosen valuation is placed in the payroll output table. Ablank space in this field means that the valuation is placed in the displayed wage type in the payrolloutput table.

• %rate

Once the current wage type has been valuated, a percentage can be applied to the valuated amount. Ifthe valuated amount should be paid in full, enter 100; if the current wage type should only pay half ofthe valuated amount, enter 50, etc.

You may, for example, pay and record overtime at time-and-a-half in one of the following two ways:- Configure one wage type, for example Overtime 150%, which multiplies the valuated amount by

150 percent.or

- Configure two wage types, for example Overtime 100% and Overtime 50%, which multiplies thevaluated amounts by the appropriate percentages for the same total result. This second option givesyou more flexibility to record payment splits and valuate derived wage types.

Wage Type ValuationValuating Time Wage Types with Average Amounts over a Given Period

© 1998 SAP Labs, Inc. 3–29

1st Derived Wage Type

In the 1st derived wage type box, the displayed wage type can have up to two derived wage types that arevaluated by the hours (Number) of the current wage type. If the current wage type already has an Amountor a Rate, nothing will be triggered in its derived wage types or its statement wage type. Usually, wagetypes that have derived wage types have hours generated in Time Management or hours entered ininfotype 2010. These hours (Number) are applied to the valuation basis (Rate) of their derived wage type toget an Amount.

A derived wage type can be configured differently from the current wage type, with different processingand evaluation classes so that different combinations of tax settings, valuation settings, etc., can beconfigured for the same original hours. A derived wage type can in turn have its own derived wage types.

The 1st derived wage type box contains the following fields:

• Valuation basis

The Rate for a derived wage type is obtained from its valuation basis, using the options nn, K, TS, TG,T, as described above.

• StatemntWT

Enter the name of the first-derived wage type here.

• %rate

Enter the percentage of the valuated amount to be applied to the first-derived wage type.

2nd-Derived Wage Type

The entries for the second-derived wage type have the same meaning as the first-derived wage type.

Valuating Time Wage Types with Average Amounts over a Given Period

Averages configuration helps you accumulate Amounts, Rates, and the Number of working hours fromprimary wage types into secondary wage types, and average the totals over different periods of time. Theresulting average rates are used to valuate time wage types. Averages are used to calculate vacation, shortand long term disability entitlements, etc., where the entitlement depends on the earnings or percentage ofdays worked in the previous payroll period or several previous payroll periods. Overtime payments mayalso be calculated in this way. The 3.0F delivered system for the U.S. and Canada does not containcomplete averages configuration. The screenshots and descriptions explain how to configure basicaverages processing from scratch.

In general, to configure basic averages processing you need primary wage types to be included inevaluation bases and evaluated by averages processing (see the steps below).


3–30 © 1998 SAP Labs, Inc.

Primary Wage Types to be Included in Evaluation Bases1. In the IMG, choose Time Wage

Type Valuation → Averages →Form bases for calculatingaverages.

2. Click Execute next to Form basesfor calculating averages.

3. Select the Country code, and clickContinue.

4. Select each primary wage typewhose Rate, Number, or Amountshould be used to calculateaverage Rates.

5. Click Details.

12

4

5


© 1998 SAP Labs, Inc. 3–31

5. In the next screen, select whetherits Rate, Number of hours, andAmount should be cumulated in/ 201 Average bases and thepercentage for each.

/ 201 is the only /2nn wage typeavailable for selection in thedelivered U.S. version.

Primary (Time) Wage Types to be Evaluated by Averages Processing1. Choose Payroll: USA → Basic

Settings → Environment forMaintaining Wage Types →Logical Views → Checkassignment to wage type group.Before time wage types can beevaluated by averages processing,make sure that they are assignedto the delivered wage type group0510, wage type generation.

2. Click Execute next to Checkassignment to wage type group.

6

12


3–32 © 1998 SAP Labs, Inc.

3. Choose Time Wage TypeValuation → Averages → Assignvaluation of averages to primarywage type.

4. Click Execute next to Assignvaluation of averages to primarywage type.

5. Select the Country grouping, andclick Continue.

6. On this screen, choose the timewage types that should have theirhourly Rate calculated as anaverage over a period of time.

7. Click Details.

7

34

6


© 1998 SAP Labs, Inc. 3–33

8. Choose the appropriate processingclass 15 value for your time wagetype.

9. The three delivered values are 1, 2,and A.

These PC15 values are processedby rule X016, which makes thefollowing decision (VWTCL 15):

• For PC15 value 1, rule X016goes to T511A and processescalculation rule 01 (MEANV01).

• For PC15 value 2, rule X016goes to T511A and processescalculation rule 02 (MEANV02).

• PC15 value A relates to frozenaverages that are outside of thescope of this document.

8

9


3–34 © 1998 SAP Labs, Inc.

10. Choose Time Wage TypeValuation → Averages → Basesfor valuation of averages.

11. Click Execute next to Bases forvaluation of averages.

12. This IMG screen should show theaverages calculations rules that areset up in T511A. However, theU.S. delivered version (3.0F) doesnot yet have a standard entry inthis view.

1011


© 1998 SAP Labs, Inc. 3–35

13. To see what is set up for countryversion 01 (Germany), in the IMG,choose Time Wage Type Valuation→ Averages → Create cumulationrules for bases for calculatingaverages.

14. Click Execute next to Createcumulation rules for bases forcalculating averages.

15. Place your cursor on HR:Averages, Start on second level.

16. Click Choose.

17. For Country grouping, select 01.

18. Click Continue.

1314

15

16

17

18


3–36 © 1998 SAP Labs, Inc.

19. For Country grouping, reselect 01.

20. Click Enter.

21. Click Average type.

You will then see the screen to theright, which is the starting point todescribe averages processing.

T511A: Averages Calculation Rules

19

20

21


© 1998 SAP Labs, Inc. 3–37

The screen above shows the different average calculation rules configured for country 01 in T511A. Thefollowing is a description of the fields and their functionalities:

• Calc. rule

This field gives the number of the averages calculation rule. Calc. Rule 01 is called by operationMEANV 01 in rule X016. Therefore, time wage types that should be valuated by this calculation ruleare given processing class 15 value 1.

• Rel. test

Cal. rule 01 goes to rule X017 to process a relevancy test, which determines which previous payrollperiods are relevant for averages calculations. Rule X017 is configured to make all previous periodsrelevant. See rule X019 for an example of how a relevancy tests are set up in a rule.

Generally, payroll periods which immediately precede the current payroll period are used toaccumulate the Numbers, Rates, or Amounts used in averages calculations. However, if an employee isabsent for part or all of a previous period, their earnings or hours of work may not be relevant to theaverages calculation.

• Cumulation

This column refers to a cumulation type called by the calculation rule. Calc. rule 01 calls cumulationtype 01. Cumulation types are described in the next section.

• F. process

This column contains the rule usded in final averages processing. In this example, Calc. rule 01 goes torule X018 for final processing. Rule X018 calculates the average Rate, using the values accumulated inthe table MV (cumulation table for averages processing). These values come from the /2nn wage typesselected by the cumulation type.

• Max.No.Per

This column stands for the maximum number of previous payroll periods that can be used to calculatethe average Number, Rate, or Amount. Calc. rule 01 is configured to return to a maximum of threepayroll periods.

• No.rel. per

This column stands for the minimum number of previous payroll periods that can be used to calculatethe average Number, Rate, or Amount. Calc. rule 01 is configured to return to a minimum of threepayroll periods.

• Wage type

A wage type entered in this column can be configured with a predefined average value, which can bechosen by users when they enter data in infotype 2010. This value is useful for employees who, forexample, are new and have not worked long enough for average processing to calculate an averagevalue.


3–38 © 1998 SAP Labs, Inc.

T511B: Cumulation Types

Select Calc. Rule 01 and click Cumulation Type for Average, which is found near the menu bar to see thefollowing screen:

This screen shows Cumulation type 01, which is called by Calc. Rule 01. In this example, Cumulation Type01 is accumulating values collected in wage types /2 04 and /2 07. For /2 04, the wage type Amountaccumulates in table MV and is ready to be included in the average rate calculations in rule X018. For /207,the wage type number and Rate accumulates in table MV, ready to be included in the average Ratecalculations in X018.

The Adjustment field determines how retroactive pay increases are handled by averages processing. Thisentry relates to an adjustment rule. Cumulation Type 01 calls Adjustment rule 01 for /20 4 and /20 7 . Noticethat each /2nn wage type is related to a different adjustment rule. To see the adjustment rules screen, clickModification Feature for AV and you will see the following screen:

T511C: Adjustment Rules for Averages Bases

Average calculation rule 01 is configured to return to three payroll periods and accumulate combinationsof Numbers, Rates, and Amounts from / 204 and /2 07 to be included in averages calculations. If a payincrease is activated in the system, and that increase is effective from the current pay period, the averagecalculations will take into account the new Numbers, Rates, and Amounts, without further adjustment.However, if the pay increase is retroactive, and it is effective from two pay periods prior, adjust youraverages processing to consider the increased amounts, not the amounts that have accumulated so far forthose periods.


© 1998 SAP Labs, Inc. 3–39

Different adjustment rules can be configured and attached to /2 nn wage types in cumulation types, so thatindividual /2nn wage types can be adjusted in different ways to consider retroactive pay increases.

The fields in the Adjustment Rules for Bases for Calculating Average Values screen have the followingfunctionality:

• Adjustment

Adjustment rule number related to / 2nn wage types in cumulation types.

• Ind:NUM

• Ind:RTE

• Ind:AMT

These three fields reflect the Numbers, Rates, and Amounts of the /2 nn wage types related to thisadjustment rule. The following options are available for using each of these fields when increasing your/ 2nn wage types during a retroactive pay increase:

• To store the increase factor as percentage in table T510C, which is explained on the following page.

• To divide the basic pay on day of the increase (using EE pay scale group/Level assignment) for currentpay period by the basic pay of previous period to increase.Apply this formula to the Number, Rate, or Amount that was stored for the retroactive period.

• To divide basic pay on day of the increase (using EE pay scale group/level assignment) on day ofincrease by the basic pay of previous period to increase.

Apply this formula to the Number, Rate, or Amount that was stored for the retroactive period.

• To divide the selected /0nn rate on the day of the pay increase by the selected /0n n rate on theprevious period to increase.

Apply this formula to the Number, Rate, or Amount that was stored for the retroactive period.

In the Ind:NUM field, you can only select option 1, and in Ind:RTE and Ind:AMT you can select any of thefollowing options:

• ID: Vbasis

If you chose option 4 above, enter the / 0nn wage type you want your retroactive increase to your /2nnNumber, Rate, or Amount to be based upon. If you enter 01, this will look at the Rate for wage type/ 001, entering 02 will look at / 002, etc.

• WTy for Percentage

If you need to enter individual retroactive average increases for specific employees, enter the wagetype to be selected as a once-only payment in infotype 2010 to apply a percentage increase. Theseemployee-specific increases take precedence over non-specific percentage increases.

• No.periods

If you do not want to increase the average bases for all the retroactive pay increase pay periods, in thisfield, enter the number of periods you want to return to (adjustment rule 01 will return three periods).

T510C: Adjust Average Bases according to Pay Scale

In the description of adjustment rules above, option 1 stated that increase factor is stored as a percentage intable T510C. To see how this functionality works, click Features of standard pay increase to see thefollowing screen.


3–40 © 1998 SAP Labs, Inc.

The settings will be applied to the Rates or Numbers of the /2 nn wage types that have option 1 chosen inthe adjustment rules. The increases applied to these wage types can vary according to the pay scale type,the area, and the EE subgroup grouping for the collective agreement provision that applies to theemployees being processed. The same / 2nn wage type can have its average bases increased by differentfactors, according to the different percentage increases configured for different groups of employees inT510C.

• Percent 1

Enter the percentage increase to be applied to the valuation bases for employees who receive a payincrease and continue to work the same number of hours.

• Percent 2

This field should only be used if employees are to have their working hours reduced, but continue toreceive the same pay. In this case, enter the reduction factor to be applied.

Calculating Daily and Weekly OvertimeOverview


Chapter 4: Calculating Daily and Weekly Overtime


The Time Evaluation Program ...........................................................................................................................................................................4–2

Schema TM04 (Negative Time Processing) ......................................................................................................................................................4–2

The USA Fair Labor Standards Act (FLSA).......................................................................................................................................................4–2Federal Law verses State Law ......................................................................................................................................................................4–3Exempt and Nonexempt Employees .............................................................................................................................................................4–3

Exempt Employees................................................................................................................................................................................4–3Nonexempt Employees .........................................................................................................................................................................4–3

Regular Rate of Pay ......................................................................................................................................................................................4–3

Daily Balance Table TES and Monthly Balance Table SALDO........................................................................................................................4–4

Calculating Weekly Overtime (TW30 or TW20).................................................................................................................................................4–5Subschema TW30—Weekly Overtime for Different Workweeks ..................................................................................................................4–6Employees with Workweeks that Have Start Times......................................................................................................................................4–6

Rule TW31.............................................................................................................................................................................................4–6Rule TW32.............................................................................................................................................................................................4–8Rule TW06.............................................................................................................................................................................................4–8Rule TW04.............................................................................................................................................................................................4–9Rule TW33...........................................................................................................................................................................................4–10

Employees with Workweeks that Do Not Have Start Times........................................................................................................................4–11Rule TW34...........................................................................................................................................................................................4–11Rule TW35...........................................................................................................................................................................................4–11Rule TW04...........................................................................................................................................................................................4–12Rule TW36...........................................................................................................................................................................................4–12

Subschema TW20: Weekly Overtime for One Workweek...........................................................................................................................4–12Rule TW01...........................................................................................................................................................................................4–13Rule TW02...........................................................................................................................................................................................4–13Rule TW04...........................................................................................................................................................................................4–14Rule TW03...........................................................................................................................................................................................4–14

Calculating Daily Overtime (Subschema TW15) ............................................................................................................................................4–14Rule TO01 ...................................................................................................................................................................................................4–15Rule TO02 ...................................................................................................................................................................................................4–16

Calculating Overtime Based on Consecutive Attendance Days (TW10) .....................................................................................................4–17Rule TW00 ..................................................................................................................................................................................................4–17Rule TO00 ...................................................................................................................................................................................................4–18

Overview

Chapter 3 described how wage type valuation is performed with schemas and rules in Payroll Calculation.Wage type valuation is applied to time wage types, which can be configured to generate payments when,for example, additional hours classified as overtime are worked. This chapter looks at the Time Evaluationprogram and the schemas and rules specifically designed to generate overtime hours for application totime wage types.

Calculating Daily and Weekly OvertimeThe Time Evaluation Program


The Time Evaluation Program

The delivered Time Evaluation program is RPTIME00, which evaluates basic employee time data, like thePayroll Calculation program does. This program can also be used to:

• Form and store time daily balances in time types (for example, flextime hours, overtime hours, etc.),which can then be converted into payments or vacation compensation, if appropriate

• Update infotype records, such as 0005 (Leave Entitlement)

• Generate messages

• Implement clock-in and clock-out time recording systems

The program is generally run each night and is started by scheduling a batch job. The results of RPTIME00are then stored in cluster B in the payroll input file (PCL2), ready for pickup in the next RPCALCX0 run.

RPTIME00 is an international program, so there are no country-specific versions. The following are themain top-level schemas appropriate for the U.S.:

• TM00 to evaluate PDC time recording, where start and end times are directly entered into the systemor are entered with a time recording system (for example, positive time processing)

• TM04 to evaluate attendances and absences recorded without clock times (for example, elapsed hours),where only the exceptions to planned work time are entered (for example, negative time processing)

This chapter describes the overtime configuration options available in schema TM04 for employeesevaluated with negative time processing.

Schema TM04 (Negative Time Processing)

Chapter 7 highlights the main processing steps that affect overtime configuration in TM04. The followingscreenshot and the remainder of this chapter describe in detail step 4, which involves calculating overtimehours and flagging overtime time pairs.

TM04-lines 000410–000430

Excess hours can be flagged asovertime based on the number of daysworked per week, or the number ofhours worked per day or per week.

The USA Fair Labor Standards Act (FLSA)

The delivered schema TM04 contains subschemas and rules that have been designed to comply with U.S.federal and state laws that stipulate when overtime should be paid for certain employees. This sectionprovides an overview of the FLSA legislation.

Calculating Daily and Weekly OvertimeThe USA Fair Labor Standards Act (FLSA)


Federal Law verses State LawThe Federal wage-hour law (FLSA) requires most employers to pay at least the federal minimum wage andan overtime premium to certain employees. Many states also impose their own minimum wage andovertime requirements. If the state law is more beneficial to the employee, then the employer must complywith the state law.

Exempt and Nonexempt EmployeesEmployees may be exempt (or nonexempt) from FLSA legislation. The category they belong to depends onthe duties they perform, not their job title.

Exempt Employees

Exempt employees do not have to be paid the minimum wage or overtime rates, because they are usuallypaid a set salary. The most common types of exempt employees include:

• White collar employees, such as:- Executives- Administrators- Professionals (including highly skilled computer professionals)- Outside salespersons

• Retail and service industry commission salespersons

• Publicly elected officials and their appointees

• Local or state government employees, other than a library or school board

Nonexempt Employees

Nonexempt employees are protected by FLSA legislation and must be paid at least the minimum wage forhours worked, and extra overtime pay for hours worked over a 40-hour week.

Federal law does not stipulate that overtime rates should be paid for working on Saturday,Sunday, or a public holiday, unless the hours exceed 40 hours a week. Federal law also doesnot stipulate that overtime rates should be paid when someone works more than eight hoursa day. However, some state laws, and union contracts require that overtime is paid whenthese conditions are met. Schema TM04 contains subschemas and rules that deal with thesevariables.

Regular Rate of PayNonexempt employees must be paid at least one-and-a-half times their regular rate of pay for physicallyworking over 40 hours during a workweek. The definition for “physically worked” does not include sickpay, vacation pay, jury duty pay, etc., unless it is the employer’s policy to do so. As an exception, state orlocal government employees can be given compensatory time off instead of overtime pay.

Calculating Daily and Weekly OvertimeDaily Balance Table TES and Monthly Balance Table SALDO


The regular rate of pay determines the rate at which excess hours should be paid and is defined as follows:

• For hourly paid employees, usually the hourly rate at which they are paid

• For salaried employees, usually the salary divided by the number of hours for which that salarycompensates

• For employees paid on a piecework or commission basis, usually the total earnings for the weekdivided by the hours worked

The following are examples of payments that should be included in the regular rate of pay:

• Non-discretionary bonuses

Any agreed upon or previously announced bonus or incentive plan related to production, efficiency,attendance, quality, or some other performance measure must be included in the regular rate of payfor the workweek in which it was earned.

• Shift premiums

An amount added to the hourly rate for working an evening, late night, or other undesirable shift.

• Non-cash payments

The reasonable cost to the employer or the fair market value of payments made in the form of goods orservices, such as meals and lodging.

• Retroactive pay or back pay awards

• On-call pay

• Cost of living adjustments

In chapter 9, USA FLSA Regular Rate of Pay Valuation describes how the Payroll Calculation program canbe configured to calculate an hourly rate according to the FLSA regular rate of pay legislation.

Daily Balance Table TES and Monthly Balance Table SALDO

RPTIME00 runs daily and keeps both daily and running (monthly) hour totals. Different types of hours arestored in time types, and the rules described in this chapter use the following utility time types totemporarily store hours or times:

• 0903 Hours (that can count towards overtime) stored for this week

• 0904 Hours (that can count towards overtime) stored for next week

• 0905 Sequence of attendance days

• 0906 Start time of the workweek

• 0900 Daily overtime after X hours (threshold)

• 0040 Overtime hours

Calculating Daily and Weekly OvertimeCalculating Weekly Overtime (TW30 or TW20)


The following operations involve TES and the monthly balance table SALDO:

• The operation that takes the hours from TES (used to process in a rule) is Dnnnn, where nnnn is thetime type number.

For example, D0903 takes the daily balance of hours for time type 0903 from TES.

• The operation that takes the hours from SALDO is Mnnn. For example, M0903 takes the monthlybalance of hours for time type 0903 from table SALDO.

• The operation to update the daily balance table TES in a rule is ADDDB (for example, ADDDB0903updates the daily balance of time type 0903).

In the above example, if the new daily balance overrides the previous entry in TES, the operation willhave a Z added to it (ADDDB0903Z).

• SALDO is not directly updated by these rules.

Rather, it is updated each day ongoing daily totals are accumulated.

Configuring in TM04

1. If your company needs to implement overtime for employees with negative timeprocessing, be aware of the subschemas and rules in this chapter.

2. Make a customer copy of all of the schemas and rules you need to use.

3. Depending on your company requirements, you might need to only make minor changesto the delivered rules. (For example, if your employees are paid overtime after workingnine hours, instead of eight, you would only need to change the overtime threshold value.Everything else could remain the same.)

4. Most of the delivered rules discussed in this chapter have no variants, which means theyare configured for ESG for PCR*. If you have less than nine sets of overtime regulations inyour company, you may use the same rule, with different variants for ESG for PCR (linkedto employee subgroup in master data), to process various sets of employees in differentways.

Calculating Weekly Overtime (TW30 or TW20)

Schema TM04 has two subschemas that can be used to set the weekly hours threshold:

• Subschema TW30 should be used where a company has two or more workweek definitions, withdifferent start days or start times.

In this case, different workweeks can be defined in T559A and defaulted to different groups ofemployees in infotype 0007 with the feature WWEEK.

• Subschema TW20 should be used where there is only one workweek definition for the entire company.

TW20 is not called in the delivered TM04. To include TW20 instead of TW30, replace TW30 with TW20in the Copy function line in TM04.



To configure overtime calculations, choose IMG → Personnel Administration and Payroll Accounting →Time Management → Time Evaluation → Time Accounting Without Clock Times → Time Data Processing→ Overtime Calculation → Calculate Overtime According to the Working Week.

Subschema TW30—Weekly Overtime for Different WorkweeksThe screenshot below shows subschema TW30.

TW30 uses IF and ELSE functions toselect different rules for differentgroups of employees as follows:

1. IF and WW if the employee has aworkweek selected in infotype0007.

2. IF and WWTI if the employee’sworkweek has a start time.

3. Rules TW31, TW32, and TW33 areprocessed.

4. ELSE if the employee has aworkweek selected in infotype0007, but their workweek does nothave a start time.

5. Rules TW34, TW35, and TW36 areprocessed.

The main reason for these two different types of processing is the need to create splits in the time pairswhere an employee begins a shift during one workweek and ends it during another. At the beginning ofthe day, the system automatically splits the time pairs when an employee’s new workweek begins (forexample, at midnight). However, if the new workweek begins during the day (for example, Monday at 2:00p.m.), additional processing is required to create new time pairs for the hours worked before and after 2:00p.m. If an employee’s workweek does not have a start time, the system assumes that the new workweekbegins at midnight on the first day.

Employees with Workweeks that Have Start TimesThe following sequence of subschemas and rules is called by TW30 to process weekly overtime foremployees who have workweeks with a start time.

Rule TW31

The IF statements in TW30 state that if the employee has a workweek selected in infotype 0007 and if theirworkweek has a start time, their hours will be processed by rules TW31, TW32, and TW33.

1

2

3

4

5



Function ACTIO in TW30 calls rule TW31, as shown below:


000010 This line takes the monthly balance of the number of hours for the current week(HRS=M0903) and adds it to the daily balance of hours for the current week, which overridesthe previous daily balance (ADDDB0903Z).

The monthly balance of the number of hours for the following week (HRS=M0904) is addedto the daily balance of hours for the following week, which overrides the previous dailybalance (ADDDB0904Z).

000020 A decision (D) is made whether this is the first day of the workweek (VARSTFDYWW).

000030 If this is not the first day of the workweek (N), a decision (D) is made whether this is the lastday of the workweek (VARSTLDYWW).

000040 If this is not the first day of the workweek (N) and not the last day of the workweek (N), 48hours are added to the start time of the workweek time type (HRS=48,00 ADDDB0906Z).Now, the system ensures that all hours worked on the current day will be included in thecurrent week and temporarily moves the start time of the next week forward by 48 hours.This process might be necessary for shift workers, whose start and end times cross over thestart and end of workweeks.

000050 If this is not the first day of the workweek (N) but the last day of the workweek (Y), 24 hoursare added to the start time of the workweek recorded in infotype 0007(HRS=IWWEEKHRS+24). This amount also added to the start of the workweek time type(ADDDB0906Z). Now, the system ensures that all hours worked during the current day willbe included in the current week; it temporarily moves the start time of the next weekforward by 24 hours.

000060 If this is the first day of the workweek (Y), the start time of the workweek recorded ininfotype 0007 is loaded into the start of the workweek time type (IWWEEKADDDB0906Z).This step ensures that time type 0906 always has the correct start time at the beginning ofeach new workweek.



Rule TW32

After TW31 has been processed, function PTIP in TW30 calls rule TW32, as shown below:

The main purpose of TW32 is to see if the time pairs assigned in T555Y (described in step 3 of chapter 7)have both start and end times (D OUTTPEXTIM). If they do not, the data is transferred back to internaltable TIP without further processing (COLOP*). If start and end times exist, the data passes to rule TW06for further processing (GCY TW06).

Rule TW06


000010 TW06 first makes a decision on the processing type of the time pair (OUTTPVTYPE).

000020 If the processing type is anything other than S (Planned Work Time), the data is transferredback to internal table TIP without further processing (COLOP*).

000030 If the processing type is S, for planned work time, it then makes a decision on the pair type ofthe time pair (OUTTPPTYPE).

000040 (S *) If the processing type is S (Planned Work Time) and the pair type is not 0 or 2, the starttime of today’s shift (HRS=PBEG) is compared to the start time of the workweek(HRS?D0906). Time type 0906 was initialized in rule TW31.

000050 (S * *) If the processing type is S (Planned Work Time), today’s hours (HRS=PNUM) areadded to the daily balance for time type 0904 [hours for the following week (ADDDB0904)],then transferred back to TIP (COLOP).

000060 (S * < ) If the start time of today’s shift is before the start time of the workweek (S * <), the end



Line Operation Descriptionstime of today’s shift (HRS=PEND) is compared to the start time of the current workweek(HRS?D0906).

000070 (S * < *) If the start time of today’s shift is before the start time of the workweek, and the endtime of today’s shift is before the start of the workweek, the data passes to rule TW04 forfurther processing (Z GCY TW04).

000080 (S * < > ) If the start time of today’s shift is before the start time of the workweek and the endtime of today’s shift is after the start of the workweek, the difference between the start of thisworkweek and the end of today’s shift (HRS=R, the result of the previous decision in line000060) is added to the daily balance for time type 0904 [hours for the following week(ADDDB0904)]. A partial time pair is created for these hours (GENTPE *) and passed toTW04 for further processing (GCY TW04).

000090and000100

If the pair type is 0 or 2 (non-recorded time or recorded absence), the data is transferred backto internal table TIP without further processing (COLOP*). However, the comment on the lastline states that if recorded absences can be counted toward overtime, they should have thehours added to time type 0903.

Rule TW04

TW04 now receives data for time pairs with processing type S (Planned Work), for all hours except non-recorded time and recorded absence. Separate time pairs have also been created by TW06 for hours thatcross the start time of the workweek.


000010 TW04 now compares the hours in the daily balance table for time type 0903 [Hours in theCurrent Week (HRS=D0903)] with the weekly overtime threshold stored in table entryOVERT in T511K under country grouping 10 [USA (HRS?COVERT)].

000020 Any excess hours from the previous operation are transferred to internal table TIP as timetype 0040 [Overtime Hours (COLOP 0040)]. Their time pair processing type is changed from S(Planned Work) to M [Overtime (FILLPVM)].

000030 If the hours in the current week are less than the threshold stored in T511K (<), today’s hoursare added to the daily balance in 0903 (HRS+PNUM), and the result is again compared to theweekly overtime threshold stored in T511K (HRS?COVERT).

000040 The new hours total after line 000030 is added to the daily balance table for 0903 (overwritingthe previous balance) and transferred to internal table TIP (ADDDB0903ZCOLOP).


4–10 © 1998 SAP Labs, Inc.


000050 If the T511K threshold is exceeded as a result of today’s planned hours, a partial time pair isgenerated for the hours in excess of this threshold in T511K (HRS=COVERTHRS-D0903GENTPB S). Its processing type is changed from S (Planned Work) to M [Overtime(FILLPVM)], and the excess hours are transferred to internal table TIP as time type 0040[overtime hours (COLOP 0040)].

At the end of the TW04 processing, excess hours that should count as overtime are stored in time type 0040(overtime hours). They have also had their time pair processing type changed from S (Planned Work) to M(Overtime), ready for selection by T510S, as described in chapter 7, Step 5: Generate Time Wage Typesfrom Time Pairs.

Rule TW33

After TW04 has been processed, subschema TW30 calls rule TW33 with the function ACTIO.

TW33 now updates time types 0903 and 0904 in the daily balance table TES. These updates continue therollover of the updates performed in TW31, which began the overtime processing for subschema TW30.

In TW31, the monthly balance in the hours for the current week (0903) and hours in the following week(0904) was added to the daily balance for 0903 and 0904, overriding the previous entries. In TW33, theserolling updates are performed differently, according to whether this is the first day of the workweek (DVARSTFDYWW).

• If this is not the first day of the workweek (N)

The monthly balance of hours for the current week (HRS-M0903) is subtracted from the daily balance ofhours for the current week (HRS=D0903), and the monthly balance of hours for the following week(HRS-M0904) is subtracted from the daily balance of hours for the following week (HRS=D0904).

The new totals become today’s daily balance for the current and the following week. These balances arethen added to the daily balance table TES, overriding the previous entries for the current(ADDDB0903Z) and the following week (ADDDB0904Z).

• If this is the first day of the workweek (Y)

The monthly balance for the hours for the current week (M0903) is deducted from the daily balance forthe hours for the following week (D0904), and the total is added to the daily balance for the hours forthe current week (ADDDB0903Z). This process takes today’s daily balance of hours and states thatthese are now the current, or new, weeks hours, not the following week’s hours.


© 1998 SAP Labs, Inc. 4–11

The daily balance of hours for the following week is then set to zero by:

HRS=0,00 HRS-M0904 ADDDB0904Z

Employees with Workweeks that Do Not Have Start TimesThe following sequence of subschemas and rules is called by TW30 to process overtime on a weekly basisfor employees who have workweeks that do not have a start time.

Rule TW34

In TW30, the ELSE statement means if the employee has a workweek selected in infotype 0007 and theirworkweek does not have a start time, then their hours will be processed by rules TW34, TW35, and TW36.

Function ACTIO in TW30 calls rule TW34, shown below:

TW34 first decides whether this is the first day of the workweek (D VARSTFDYWW). If this is not the firstday of the workweek (N), the daily balance of the hours for the current week in table TES is updated(ADDB0903Z) by the monthly balance of the hours for the current week (HRS=M0903) from SALDO. If thisis the first day of the workweek, the daily balance of the hours for the current week is set to zero(HRS=0,00 ADDDB0903Z).

Rule TW35

After TW34 has been processed, function PTIP in subschema TW30 calls rule TW35, shown below:

TW35 first makes a decision on the processing type of the time pair (OUTTPVTYPE). If the processing typeis anything other than S (Planned Work), the data is transferred back to internal table TIP without furtherprocessing (COLOP*). If the processing type is S, for planned work time, it then makes a decision on thepair type of the time pair (OUTTPPTYPE).

If the pair type is 0 or 2 (Non-Recorded Time or Recorded Absence), the data is transferred back to internaltable TIP without further processing (COLOP*). However, the comment on the last line states that if


4–12 © 1998 SAP Labs, Inc.

recorded absences can be counted toward overtime, they should have the hours added to time type 0903. Ifthe processing type is S (Planned Work), and the pair types are not 0 or 2 (*), the data is transferred to ruleTW04 for further processing (Z GCY TW04).

Rule TW04

TW04 has now been passed data for time pairs with processing class S (Planned Work), for all hours exceptnon-recorded time and recorded absence. Please see the screenshot and description of TW04 on page 10 fordetails before the next stage in processing.

Rule TW36

After TW04 has been processed, subschema TW30 calls rule TW36 with the function ACTIO.

TW36 takes the daily balance for this week’s hours (HRS=D0903), and subtracts from it the monthlybalance for this week’s hours (HRS-M0903). The new total is today’s balance for this week’s hours, which isadded to the daily balance table TES (ADDDB0903Z), overriding the previous entry.

Subschema TW20: Weekly Overtime for One Workweek.The screenshot below shows subschema TW20, which is used as an alternative to subschema TW30 tocalculate weekly overtime when a company only has one workweek definition for all employees.

TW20 behaves similarly to TW30 because:

• Rule TW01 initializes TES

• Rule TW02 compares the hours worked weekly to the threshold in T511K and flags overtime time pairswith processing type M

• Rule TW03 resets the daily balance table TES after processing is complete


© 1998 SAP Labs, Inc. 4–13

Rule TW01

TW01 decides whether this is the first day of the workweek (D VARSTWDY 7). In the above screenshot,VARSTWDY is set to 7, indicating that a new week begins on a Sunday. If, for example, your companyworkweek begins on a Monday, change the 7 to a 1.

If today is not the first day of the workweek (for example, it is not day 7), the daily balance for this week’shours is updated in table TES (ADDDB0903Z) with the monthly balance for this week’s hours(HRS=M0903). If this is the first day of the workweek, the daily balance for this week’s hours is set to 0,00hours (HRS=0,00 ADDDB0903Z).

Rule TW02

Rule TW02 behaves identically to rule TW35 in subschema TW30 because:

• It first makes a decision on the processing type of the time pair (OUTTPVTYPE).

• If the processing type is anything other than S (Planned Work), the data is transferred back to internaltable TIP without further processing (COLOP*).

• If the processing type is S, for planned work time, it then makes a decision on the pair type of the timepair (OUTTPPTYPE).

• If the pair type is 0 or 2, (Non-Recorded Time or Recorded Absence), the data is transferred back tointernal table TIP without further processing (COLOP*). However, the comment on the last line statesthat if recorded absences can be counted toward overtime, they should have the hours added to timetype 0903.

• If the processing type is S (Planned Work), and the pair type is not 0 or 2 (*), the data is transferred torule TW04 for further processing (Z GCY TW04).

Calculating Daily and Weekly OvertimeCalculating Daily Overtime (Subschema TW15)

4–14 © 1998 SAP Labs, Inc.

Rule TW04

TW04 has now been passed data for time pairs with processing class S (Planned Work), for all hours exceptnon-recorded time and recorded absence. Please see the screenshot and description of TW04 on page 9 fordetails before the next stage in processing.

Rule TW03

After TW04 has been processed, subschema TW20 calls rule TW03, with the function ACTIO.

Rule TW03 behaves identically to rule TW36 in subschema TW30. In this case, TW03 takes the dailybalance for this week’s hours (HRS=D0903), and subtracts from it the monthly balance for this week’shours (HRS-M0903). The new total is today’s balance for this week’s hours, which is added to the dailybalance table TES (ADDDB0903Z), overriding the previous entry.

Calculating Daily Overtime (Subschema TW15)

Schema TM04 uses subschema TW15 to calculate overtime on a daily basis. To configure overtimecalculations, choose IMG → Personnel Administration and Payroll Accounting → Time Management →Time Evaluation → Time Accounting Without Clock Times → Time Data Processing → OvertimeCalculation → Calculate Overtime on a Daily Basis.

Subschema TW15 first calls rule TO01, shown on the following page.


© 1998 SAP Labs, Inc. 4–15

Rule TO01TO01 sets the limits after which overtime becomes payable.


000010 A decision (D) is made on the day type being worked by the employee (VARSTDAYTY).

000020 For all day types except 0 (work, paid), 1 (off, paid), and 2 (off, not paid), the time type 0900(Daily Overtime After X Hours), is set at greater than 8,00 hours in the daily balance table TESfor planned hours worked (HRS=S HRS>8,00 ADDDB0900).

000030 For day type 0 (work, paid), the rule decides whether this is a free day in the employee’s workschedule (D VARSTFREE).

000040and000050

If this is not a free day (N), the system has two settings:

• Line 000040 adds 99,00 hours to time type 0900 (Daily Overtime After X Hours) in TES.This setting, means for that day, the employee will not work sufficient hours to qualify forovertime.

• Line 000050 adds 8,00 hours to time type 0900 (Daily Overtime After X Hours) in TES forplanned hours worked. This line is deactivated by the * in column T.

Essentially, in delivered rule TO01, overtime is not automatically paid after eight hours. Tomake overtime payable after eight hours, delete the * in column T to activate line 000050 andadd an * in column T to deactivate line 000040.

000060 If this is a free day (Y), the system adds 8,00 hours to time type 0900, but does not attach thislimit to planned hours (HRS=8,00 ADDDB0900Z). This setting means that the hours workedover eight hours on a free day qualify for overtime.

000070 For day type 1 (off, paid), 0,00 hours are added to time type 0900 (HRS=0,00 ADDDB0900Z).This setting means that overtime will be paid for the hours worked on a paid day off.

000080 For day type 2 (off, unpaid), 99,00 hours are added to time type 0900 (HRS=99,00ADDDB0900Z). This means that overtime will not be paid for the hours worked on an unpaidday off.


4–16 © 1998 SAP Labs, Inc.

Rule TO02After the processing of TO01, subschema TW15 calls rule TO02.


000010 A decision (D) is made on the processing type of the time pair being processed(OUTTPVTYPE).

000020 (*) Time pairs with processing types other than S (Planned Hours) are passed on withoutfurther processing (COLOP*).

000030 (S) For time pairs with processing type S, a decision is made (D) on the time pair type(OUTTPPTYPE).

000040 (S *) For all time types with processing type S, and with time pair types other than 0 (Non-Recorded Time), and 2 (Recorded Absence), the rule compares the daily balance for hours forthe following week (HRS=D0904) with the daily balance stored in the daily overtime after-x-hours time type (HRS?D0900).

000050 (S * *) Excess hours in the previous line are transferred to internal table TIP as time type 0040[Overtime Hours (COLOP 0040)]. Their time pair processing type is changed from S (PlannedWork) to M [Overtime (FILLPVM)].

000060 (S * <) If the hours in D0904 are less than the hours in D0900, today’s hours are added to thehours in D0904 and again compared to the hours in D0900 (D HRS+PNUM HRS?D0900).

000070 (S * < *) The result of line 000060 is added to the daily balance of 0904 in the daily input table(overriding the previous balance), and transferred to internal table TIP (ADDDB0904ZCOLOP).

000080 (S * < >) If the hours in D0904 are now greater than the hours in D0900, a partial time pair isgenerated for the excess hours (HRS=D0900 HRS-D0904 GENTPB S), and its processing typeis changed from S (Planned Work) to M [Overtime (FILLPVM)]. The excess hours are alsotransferred to internal table TIP as time type 0040 [Overtime Hours (COLOP 0040)].

000090 For time types with processing type S, and with time pair type 0 (Non-Recorded Time), thedata passes on without further processing (COLOP*).

Calculating Daily and Weekly OvertimeCalculating Overtime Based on Consecutive Attendance Days (TW10)

© 1998 SAP Labs, Inc. 4–17


000100 For time types with processing type S, and with time pair type 2 (Recorded Absence), the datapasses on without further processing (COLOP*). However, the comment on the last line statesthat if recorded absences can be counted toward overtime, they should have the hours addedto time type 0904.

Calculating Overtime Based on Consecutive Attendance Days (TW10)

Schema TM04 uses subschema TW10 to calculate overtime based on the number of consecutive attendancedays. TW10 is delivered deactivated. To configure overtime calculations, choose IMG → PersonnelAdministration and Payroll Accounting → Time Management → Time Evaluation → Time AccountingWithout Clock Times → Time Data Processing → Overtime Calculation → Calculate Overtime Accordingto Days Worked.

In subschema TW10, function IF calls rule TW00.

Rule TW00


000010 A decision (D) is made on whether the employee is present today (VARSTPRSNT).

000020 If the employee is absent (N), the IF statement is called false (SCOND=F), and the dailybalance in time type 0905 (Sequence of Attendance Days) is set to zero (HRS=0,00ADDDB0905Z), with no further processing in subschema TW10.

000030 If the employee is present (Y), a decision (D) is made on whether this is the start of the

Calculating Daily and Weekly OvertimeCalculating Overtime Based on Consecutive Attendance Days (TW10)

4–18 © 1998 SAP Labs, Inc.

Line Operation Descriptionsworkweek (VARSTWDY 7). The first day of the week is set for day number 7 (Sunday).

000040 If the employee is present, and this is not the first day of the workweek, the previous day’sbalance in 0905 is made available, and 1,00 day is added to it (HRS=L0905 HRS+1,00), and thedaily balance in 0905 is updated by the new total (ADDDB0905Z). The new balance is thencompared to 6,00 [the consecutive days threshold, after which overtime becomes payable(HRS?6,00)].

000050 If the result of the previous line is not greater than 6,00, the IF statement is false (SCOND=FIF) and no further processing is carried out in TW10.

000060 If the result of the previous line is greater than 6,00 (Y N >), the IF statement is true(SCOND=T IF) and further processing will be carried out by TW10 in rule TO00.

000070 If the employee is present, and this is the first day of the workweek (Y Y), then the IFstatement is false (SCOND=F IF) and the daily balance for 0905 is set to 1,00, for the first dayof the week (HRS=1,00 ADDDB0905Z). No further processing is carried out in TW10.

Rule TO00If the employee is present, this is not the first day of the workweek, and he or she has exceeded sixconsecutive working days, TW10 processes rule TO00 to convert the planned hours for the seventh, eighth,etc., consecutive working days to overtime hours.

TO00 makes a decision on the processing and pair type of the time pairs passed on from TW00. All timepairs with processing type P (Planned Hours) and other than 0 (Non-Recorded Time) and 2 (RecordedAbsence) have their processing type changed to M [Overtime (FILLPVM)] and are ready to be selected byT510S, as described in chapter 7, Step 5: Generate Time Wage Types from Time Pairs. The excess hours arealso transferred to internal table TIP as time type 0040 [Overtime Hours (COLOP 0040)].

Compensating Overtime with Remuneration or VacationOverview


Chapter 5: Compensating Overtime with Remuneration or Vacation


Choosing a Compensation Type .......................................................................................................................................................................5–2

Configuring Processing Class 17 for Overtime Wage Types..........................................................................................................................5–2Data Flow: Rules TC20, TC21, TC22............................................................................................................................................................5–3Data Flow: TC10, TC11, TC12......................................................................................................................................................................5–3

Configuring Overtime Compensation in Rules TC20, TC21, and TC22..........................................................................................................5–3Rule TC20 .....................................................................................................................................................................................................5–4Rule TC21 .....................................................................................................................................................................................................5–5Rule TC22 .....................................................................................................................................................................................................5–6

Configuring Overtime Compensation in Rules TC10, TC11, TC12.................................................................................................................5–7Rule TC10 .....................................................................................................................................................................................................5–7Rule TC11 .....................................................................................................................................................................................................5–8Rule TC12 .....................................................................................................................................................................................................5–9

Overview

Examine the screenshot of lines 000440–000610 in schema TM04 below. This screenshot highlights the oneof main processing steps that affects overtime configuration in TM04.

This chapter describes rule TC20, which is processed in step 6 (the further processing of overtime wagetypes), as discussed in chapter 7. In this step, remuneration or vacation combinations can be generated forwage types that contain hours generated as overtime. This chapter also describes rule TC10, which workslike TC20 and, if required, can also be processed by schema TM04.

Compensating Overtime with Remuneration or VacationChoosing a Compensation Type


Choosing a Compensation Type

Chapter 1 described the ways that overtime is entered in the system. Overtime hours are entered usinginfotypes 2005 (Overtime) and 2007 (Attendance Quotas). The user can choose one of the followingcompensation types:

Compensation type left blank The compensation type will depend on the wage type chosen.

Compensation type 1 Compensate with remuneration only.

Compensation type 2 Compensate with remuneration and vacation.

Compensation type 3 Compensate with vacation only.

Configuring Processing Class 17 for Overtime Wage Types

Some companies compensate overtime by providing additional vacation hours, or a combination ofvacation and extra payments. Each of these options can be configured into an overtime wage type, so thatthis wage type automatically behaves as expected when additional hours are worked. This configuration isset up by assigning an appropriate value to wage type processing class 17 (PC17) in T512W. PC17 must beset up for all overtime wage types.

To configure PC17, choose IMG → Personnel Administration and Payroll Accounting → TimeManagement → Time Evaluation → Time Accounting Without Clock Times → Time Wage Type Selectionand Overtime Compensation → Compensate Overtime.

Depending on the PC17 value, the wage type is processed by rules TC20, TC21, and TC22, or by rulesTC10, TC11, and TC12. The main differences between rules TC20–22 and TC10–12 are:

• Rules TC20–22These rules process wage types with PC17 values A–E, which allow you to configure additionalremuneration and/or additional leave compensation for additional hours worked. The amount ofvacation compensation is either on a one-to-one basis, or is determined by the percentages of thederived wage types, based on the chosen PC17 value.

• Rules TC10–12These rules process wage types with PC17 values 0–9, and V, which allow you to configure additionalremuneration and/or additional leave compensation for additional hours worked. However, theamount of additional leave compensation is determined by fixed factors (1:1.25, 1:1.5, etc), based on thechosen PC17 value.

Compensating Overtime with Remuneration or VacationConfiguring Overtime Compensation in Rules TC20, TC21, and TC22


Data Flow: Rules TC20, TC21, TC22• TC20

This rule looks for wage types with PC17 values A–F.- If the wage type being processed has PC17 values A, B, and C it will be processed by rule TC20.- If the wage type being processed has PC17 values D, E, and F, the wage type is passed to TC21 for

processing.

• TC21

This rule looks at wage types with PC17 values D, E, and F, and checks to see if the user has input anovertime compensation type against them in infotypes 2005 or 2007.- If the user has selected a compensation type, (1, 2, or 3), TC21 processes the wage type based on the

entered compensation type.- If a compensation type was not selected, TC21 passes on the wage type to TC22.

• TC22

This rule processes the wage types according to defaults for PC17 values D, E, and F.

Data Flow: TC10, TC11, TC12• TC10

This rule looks for wage types with PC17 values 1–9 and V.- If the wage type has values 1–5 and V, TC10 will process it.- If the wage type has PC17 values 6–9, TC10 passes it to TC11 for processing.

• TC11

This rule looks at wage types with PC17 values 6–9 and checks if the user has input an overtimecompensation type against them in infotypes 2005 or 2007.- If the user has selected compensation type 1–2, TC11 processes the wage type according to the

compensation type selected.- If compensation type 3 was selected, TC11 passes the wage type to TC12.

• TC12

This rule processes the wage types according to defaults for PC17 values 6–9.

Configuring Overtime Compensation in Rules TC20, TC21, and TC22

Rules TC20, TC21, and TC22 are configured to process wage types by using processing class 17, values A–F. Once the system has the Number of hours (from the time wage type) and a Rate (from the time wagetype’s valuation basis), it multiplies N x R to get the Amount to be paid.



Rule TC20

As seen in the above screenshot, TC20 makes a decision (D) on the wage type processing class 17 value(VWTCL 17).

• For values other than A, B, C, D, E, and F, the wage type number and time specifications are passed onto the time wage types internal table ZL without further processing (ADDZLM*).

• For PC17 value A (compensate overtime with remuneration only):- ADDDB0042 adds the number of hours to time type 0042 (Overtime to Remunerate) in the daily

balance table TES.- ADDZLM* adds the Number and time specifications to the time wage type being processed in ZL.

The number is the Number of hours to be applied to the overtime Rate in wag e type valuation toget the Amount to be paid.

• For PC17 value B (compensate overtime with remuneration and vacation on a 1:1 basis):- ADDDB0043 and ADDDB0410 add the number of hours to time types 0043 (Overtime Basic/Time

Off) and 0410 (Time Off from Overtime) in TES.- UPDTQA02 also adds the number of hours to time quota 02 (Time Off Entitlement).- ADDZML1 and ADDZML2 then add the Number and time specifications to the first and second

derived wage types in ZL, without taking into account their percentages in T512W. The numberwill be the Number of hours to be applied to the overtime Rate in wage type valuation, to get theAmount to be paid. Remuneration will be paid by one, or both, of the derived wage types, and notby the original wage type.

• For PC17 value C (compensate overtime with vacation, with a factor from the derived wage typepercentages):- ADDDB0041 adds the number of hours to time type 0041 (Overtime to Compensate) in TES.- HRS*%012 then takes the number of hours and multiplies it (*) by the sum of the percentages in the

base, first, and second derived wage types (%012).- The result of HRS*%012 is then added to time type 0410 (Time Off from Overtime) in TES

(ADDDB0410), and time quota 02 [Time Off Entitlement (UPDTQA02)].

• For PC17 values D, E, F:

The number and time specifications are passed to rule TC21 for further processing (GCY TC21).



Rule TC21

Rule TC21 makes a decision (D) on the overtime compensation type (OUTOTCLTYP) selected by the userfor the wage type in infotype 2005 (Overtime) or 2007 (Attendance Quotas).

• Where the user did not select an overtime compensation type (*), the number and time specificationsare passed to rule TC22 to process the default values for PC17 values D, E, and F (GCY TC22).

• For wage types where overtime compensation type 1 was selected (compensate overtime withremuneration only):- ADDDB0042 adds the number of hours to time type 0042 (Overtime to Remunerate) in TES.- ADDZLM* adds the Number and time specifications to the time wage type being processed in ZL.

The number will be the Number of hours to be applied to the overtime Rate in wage type valuationto get the Amount to be paid.

• For wage types where overtime compensation type 2 was selected (compensate overtime withremuneration and vacation):- ADDDB0043 and ADDDB0410 add the number of hours to time types 0043 (Overtime Basic/Time


derived wage types in ZL, without taking into account their percentages in T512W. The numberwill be the Number of hours to be applied to the overtime Rate in wage type valuation to get theAmount to be paid. Remuneration will be paid by one, or both, of the derived wage types, and notby the original wage type.

• For wage types where overtime compensation type 3 was selected (compensate overtime withvacation only):- ADDDB0041 adds the number of hours to time type 0041 (Overtime to Compensate) in TES.- HRS*%012 then takes the number of hours and multiplies it (*) by the sum of the percentages in the





Rule TC22

Rule TC22 processes the defaults for wage type processing class 17 values D, E, and F.

• For PC17 value D (compensate overtime with remuneration only):- ADDDB0042 adds the number of hours to time type 0042 (Overtime to Remunerate) in TES.- ADDZLM* adds the Number and time specifications to the time wage type being processed in ZL.

The number will be the Number of hours to be applied to the overtime Rate in wage type valuationto get the Amount to be paid.

• For PC17 value E (compensate overtime with remuneration and vacation, on a 1:1 basis):- ADDDB0043 and ADDDB0410 add the number of hours to time types 0043 (Overtime Basic/Time


derived wage types in ZL, without taking into account their percentages in T512W. The numberwill be the Number of hours for application to the overtime Rate in wage type valuation, to get theAmount to be paid. Remuneration will be paid by one, or both, of the derived wage types, and notby the original wage type.

• For PC17 value F (compensate overtime with vacation, with a factor from the derived wage typepercentages):- ADDDB0041 adds the number of hours to time type 0041 (Overtime to Compensate) in TES.- HRS*%012 then takes the number of hours and multiplies it (*) by the sum of the percentages in the



Compensating Overtime with Remuneration or VacationConfiguring Overtime Compensation in Rules TC10, TC11, TC12


Configuring Overtime Compensation in Rules TC10, TC11, TC12

Rules TC20, TC21, and TC22 are configured to process wage types with processing class 17 values 1–9, andV, as follows:

Rule TC10

Rule TC10 processes wage types with processing class 17 values 0–9, and V, as follows:

It first makes a decision on WT processing class 17 value (VWTCL 17).

• For values other than 1–9 and V:

The wage type number and time specifications are passed back to ZL without further processing(ADDZLM*).

• For value 1 (compensate overtime with remuneration, and vacation on a 1:1 basis):- ADDDB0043 and ADDDB0410 add the number of hours to time types 0043 (Overtime Basic/Time

Off) and 0410 (Time Off From Overtime) in TES.- UPDTQA02 adds the number of hours to time quota 02 (Time Off Entitlement).- ADDZML1 and ADDZML2 then add the Number and time specifications to the first and second

derived wage types in ZL, without taking into account their percentages in T512W. The numberwill be the Number of hours to be applied to the overtime Rate in wage type valuation to get theAmount to be paid. Remuneration will be paid by one, or both, of the derived wage types, and notby the original wage type.

• For value 2 (compensate overtime with vacation only, on a 1:1 ratio):- ADDDB0041 adds the number of hours to time type 0041 (Overtime to Compensate).- HRS*1,00 then multiplies the hours by a factor of 1:1.- The result of HRS*1,00 is then added to time type 0410 (Time Off from Overtime) in TES




• For values 3, 4, 5:

The operations are the same as value 2, except that the vacation compensation ratios are 1,25; 1,50; and2,00, respectively.

• For values 6–9:

The number and time specifications are passed to rule TC11 for further processing (GCY TC11).

• For value V (Remuneration):- ADDDB0042 adds the number of hours to time type 0042 (Overtime to Remunerate) in TES.- ADDZLM* adds the Number and time specifications to the time wage type being processed in ZL.

The number will be the Number of hours to be applied to the overtime Rate in wage type valuationto get an Amount to be paid.

Rule TC11

Rule TC11 makes a decision on the overtime compensation type (OUTOTCLTYP) selected by the user forthe wage type in infotype 2005 (Overtime) or 2007 (Attendance Quotas).

• For wage types where overtime compensation type 1 (compensate overtime with remuneration only)was selected, or a compensation type was not selected:- ADDDB0042 adds the number of hours to time type 0042 (Overtime to Remunerate) in TES.- ADDZLM* adds the Number and time specifications to the time wage type being processed, in

table ZL. The number will be the Number of hours to be applied to the overtime Rate in wage typevaluation to get the Amount to be paid.

• For wage types where overtime compensation type 2 was selected (compensate overtime withremuneration and vacation):- ADDDB0043 and ADDDB0410 add the number of hours to time types 0043 (OvertimeBasic/Time


derived wage types in ZL, without taking into account their percentages in T512W. The numberwill be the Number of hours to be applied to the overtime Rate in wage type valuation to get theAmount to be paid. Remuneration will be paid by one or both of the derived wage types, and notby the original wage type.



• For wage types where overtime compensation type 3 was selected (compensate overtime withvacation only):

The number and time specifications pass to rule TC12 for further processing (GCY TC12).

Rule TC12

Rule TC12 processes the defaults for WT processing class 17 values 6, 7, 8, and 9.

For PC17 value 6 (compensate overtime with vacation, with a factor 1:1):- ADDDB0041 adds the number of hours to time type 0041 (Overtime to Compensate) in TES.- HRS*1,00 then takes the number of hours and multiplies it (*) by the factor 1:1.- The result of HRS*1,00 is then added to time type 0410 (Time Off from Overtime) in TES


For values 7, 8, and 9:

The operations are the same as value 6, except that the vacation compensation ratios are 1,25; 1,50; and 2,00respectively.

Overtime in Schema TM00 (Positive Time Processing)Overview


Chapter 6: Overtime in Schema TM00 (Positive Time Processing)


Schema TM00—Positive Time Recording.........................................................................................................................................................6–1Subschema TO00 .........................................................................................................................................................................................6–2Subschema TC20..........................................................................................................................................................................................6–2

Overview

The purpose of this chapter is to provide a high-level summary of some of the subschemas and rules thatcan be used to process overtime in schema TM00. A complete summary of all of the available overtimeconfiguration options is outside the scope of this document.

Schema TM00—Positive Time Recording

TM00 calls the following rules:

Rule Purpose

MODT Determines table modifiers using MODIF W (T510S), MODIF T (T555Z), and MODIF A(T554C).

TO20 Determines overtime from employee’s absence and attendance times on a quota basis. Formsovertime pairs for hours in excess of planned work time for the day. Overtime approval mustexist, and maximum daily work time as per constant TGMAX in T511K cannot be exceeded.Parameter 2 in schema function GOT determines which overtime quota is checked.

TO15 Checks OVPOS field in T550A for general overtime approval for each daily work schedule. Ifovertime is approved for EEs daily work schedule, it calls TO16.

TO16 Selects all time pairs outside of planned work time, to calculate overtime. Can either be usedwith TO15 above, so that only approved overtime is paid, or can be used without TO15, sothat overtime is paid without approval. Calls TO11 for final calculation of overtime.

TM00 calls subschema TO00 (Rounding Overtime Hours), which is used where approved overtime hoursshould not be paid in full but should be rounded up or down to a predetermined amount.

Overtime in Schema TM00 (Positive Time Processing)Schema TM00—Positive Time Recording


Subschema TO00This subschema calls the following rules:

Rules Functions

TO30 This rule is an alternative to rule TO20. Time pairs that fulfill the conditions for overtime arenot converted to overtime at this point, but are assigned processing type U.

TO50 Time pairs with processing type U are rounded off with the rounding factor ZMRND fromT511K, using operation RNDOT, to a set number of hours.

TO50 This rule is called using function GOT, which checks for overtime approval in the appropriatequota type, (specified in parameter 2). If overtime is approved, it is generated from time pairswith processing type U.

Subschema TC20This subschema calls the following rule:

Rules Functions

TC20 Looks at WT processing class 17 values A, B, C, D, E, and F, to decide if an employee shouldbe paid, or given time off for overtime hours. Updates time types, and time off quota, usingT556A. Calls rule TC21 for further processing if applicable.

Main Steps in Overtime Processing, Steps 1–8Overview


Chapter 7: Main Steps in Overtime Processing, Steps 1–8


Steps 1–8: The Time Evaluation Program ........................................................................................................................................................7–1Schema TM04 ...............................................................................................................................................................................................7–2Step 1: Function MOD sets Table Modifiers..................................................................................................................................................7–4Step 2: Hours Collection................................................................................................................................................................................7–5Step 3: Assign Hours to Time Pairs in T555Y ...............................................................................................................................................7–5

Assigning Collected Hours to Time Pairs in T555Y...............................................................................................................................7–8Step 4: Calculate Overtime Hours and Flag Overtime Pairs .........................................................................................................................7–9Step 5: Generate Time Wage Types from Time Pairs ................................................................................................................................7–10

Time Wage Type Selection Rule Table (T510S) .................................................................................................................................7–13Function GWT .....................................................................................................................................................................................7–15

Step 6: Further Processing of Overtime Wage Types.................................................................................................................................7–15Step 7: Check Overtime Compensation Account ........................................................................................................................................7–16Step 8: Export Results to Payroll Input File PCL2.......................................................................................................................................7–17

Overview

Chapter 7 provides a high-level, chronological overview, of the main processing steps in the TimeEvaluation program RPTIME00, schema TM04, and the Payroll Calculation program RPCALCU0, whichaffect overtime payments.

Chapter 3 described how wage type valuation calculates an hourly Rate, and applies it to a Numb er ofhours in time wage types, to get the Amount to be paid. Chapter 4 showed you how different rules in TimeManagement schema TM04 configure different overtime calculations, which then formulate the Number ofovertime hours for generation in time wage types. Chapters 7 and 8 describe how these processes arebrought together in RPTIME00 and RPCALCU0. This chapter focuses on steps 1–8, which are processed inRPTIME00, and chapter 8 provides details on steps 9–16, which are processed in RPCALCU0.

Steps 1–8: The Time Evaluation Program

The delivered Time Evaluation program is RPTIME00. In addition to evaluating basic employee time data,like the Payroll Calculation program, RPTIME00 also:

• Forms and stores time balances in time types (for example, flextime hours and overtime hours), whichcan be converted into payments, or vacation compensation.

• Updates infotype records such as 0005 (Leave Entitlement)

• Generates messages

• Implements clock-in and clock-out time recording systems.

Main Steps in Overtime Processing, Steps 1–8Steps 1–8: The Time Evaluation Program


The program generally runs overnight, and is started by scheduling a batch job. The results of RPTIME00are stored in the payroll input files PREL, PCL1, and PCL2 and are ready for pickup during the next run ofRPCALCX0.

RPTIME00 is an international program, so there are no country-specific versions. The following are themain top-level schemas appropriate to the U.S.:

• TM00 to evaluate PDC time recording, where start and end times are directly entered into the systemor with a time recording system.

• TM04 to evaluate attendances and absences recorded without clock times (for example, elapsed hours),including negative time processing, where only exceptions to planned work time are entered.

For the purposes of this documentation we will make two assumptions:

• The customer runs RPTIM00 on a daily basis.

• The customer’s top-level schema is a copy of TM04.

This chapter sets out the main daily processing performed by RPTIME00, schema TM04.

Schema TM04The screenshots on the following pages show how schema TM04 performs eight of the main steps inovertime processing.



Schema TM04

1. Function MOD sets table modifers(line 000080).

2. The next step is hours collection (line000180–000250).

3. Function TYPES assigns hours totime pairs in T555Y (line 000320).

4. Overtime hours and flag overtimetime pairs are calculated (line000410–000430).

5. Time wage types from time pairs aregenerated (lines 000440–000490).

6. Overtime wage types are furtherprocessed (line 000500–000520).

1

2

3

4

6

5



7. Overtime compensationaccount is checked (line000610).

8. Function EXPRT exportsresults to payroll input filesPREL, PCL1, and PCL2 (line000760).

The above steps are described in detail in the following pages.

Step 1: Function MOD sets Table Modifiers1. In line 000080, function MOD calls

the ESG for PCR variants for ruleTMON, which set the modifiersfor the following tables:

• MODIF W

Selects the time wage typeselection group in T510S.

• MODIF T

Selects the time typedetermination group in T555Yand T555Z.

• MODIF A

Selects the employee groupingfor absence valuation inT554C.

You will see the effects of thesetable modifiers in steps 3 and step5 later in this chapter.

8

7

1



Step 2: Hours CollectionIn lines 000180–000250 the processingis divided into two stages:

• First stage:- Function IF parameter POS

states that if actual times arebeing recorded, function P2000should load the planned hoursin the daily work schedule,without the start and endtimes.

- Function ELSE states that ifactual times are not beingrecorded, function P2000should load the planned hoursin the daily work schedulewith the start and end times.

• Second stage:- Function ENDIF ends the IF

function.- Functions P2002, P2003, and

P2001 load the attendances,the substitutions, and theabsences for the day.

Step 3: Assign Hours to Time Pairs in T555Y1. In this step, line 000320, function

TYPES collects the hours from step2 and assigns them processingtypes and time pair types inT555Y.

1



2. To access the configuration forT555Y (schema TM04), in the IMG,choose: Time Management →Time Evaluation → TimeAccounting Without Clock Times→ Time Data Processing → Assigntime types and processing types.

3. Click Execute next to Assign timetypes and processing types.

4. This path divides into fouradditional options. The fourchoices are described below.

• Define time types

This option contains the time types used to record start and end times on the system. Each time type isassigned to a personnel subarea grouping for time recording, which is used as part of the selectioncriteria in T555Y.

• Define class processing type /time type for absence

This option assigns classes for Time Evaluation to absence types. This configuration is outside thescope of this document. The view also assigns each absence type a processing type and time type class,which is used as part of the selection criteria in T555Y.

23

4



The delivered processing type and time type class definitions are:

01 Leave types or general working hours

02 Periods of illness

03 Time off for overtime

04 Other absences

05 Overtime

• Define class processing type /time type for attendance

The configuration here is the same as for absence above.

• Assign processing type and time type

This view takes you to T555Y, which takes the hours collected in step 2 of TM04 and assigns them tothe appropriate time pairs. Each time pair in T555Y contains a time type, which has been configuredand assigned in the views above, and a processing type. The time type accumulates the collected hoursinto time balances.

The processing type for each time type is configurable in T555Y, and the following processing types areused in the delivered table T555Y:

Planned working hours Processing type S

Overtime hours Processing type M

Absence hours Processing type A

Attendance hours Processing type P

In the delivered system, step 4 (overtime calculation subschemas), and step 5 (generate time wagetypes from time pairs in T510S), process the following time pair processing types:



Remember that steps 4 and step 5 can be configured to process any processing typeconfigured in T555Y.



Assigning Collected Hours to Time Pairs in T555Y

See the screenshot below of T555Y and the description of how it assigns the collected hours to theappropriate time pairs:

T555Y assigns the collected hours to the appropriate time pairs in the following sequence:1. In column 1 (PSgrpg), T555Y restricts the available time pairs based on the personnel subarea grouping

for Time Management that were assigned to the time type in the time pair (columns Pair Type 1, 2, and3). In the screenshot above, only employees with pers subarea group 01 will have their hoursprocessed.

2. Then, in column 2 (Group), T555Y restricts the available time pairs based on the time typedetermination group value that is assigned to employee groups in operation MODIF T in rule TMON(step 1 of schema TM04). In the screen above, we can see that employees with a MODIF T value of 01will have their hours processed differently from employees with a MODIF T value of 02.

3. In column 3 (P /T), T555Y restricts the time pairs based on the processing and time type class assignedto the absence or attendance type used to enter the hours. If the hours have defaulted from the workschedule with P2000 (for negative time), it assigns class 00.

4. At this point, the available time pairs should have been reduced to one line.

The final assignment is made to time pair 1, time pair 2, or time pair 3, based on the following criteria:

• Pair Type 1

This type relates to one of the following options:- If there is a positive time recording, attendance hours entered into the system with infotype 2011

(Time Recording Terminals), (function IF P2000)- If there is a negative time recording, attendance hours taken from the specifications in the daily

work schedule in infotype 0007 (Planned Work Time), (function ELSE P2000)

• Pair Type 2

This type relates to absence hours that have been entered into the system in infotype 2001 (functionP2001).

• Pair Type 3

This type relates to attendance hours that have been entered into the system in infotype 2002 (functionP2002).



By the end of the processing in T555Y, the collected hours will have been assigned to the appropriate timepair, which will contain a time type and a processing type. The time type accumulates the collected hoursinto time balances. The processing type, in step 4 (overtime calculation subschemas), and step 5 (generatetime wage types from time pairs based on the conditions in T510S) identify which hours should begenerated in time wage types. In release 3.0F, the delivered system generates only those time wage typesthat have the following processing types:



The time types in each line, and the processing types assigned to them, can be configured inT555Y based on customer requirements.In the example above, PSG 01 and MODIF T grouping 01 relates to positive paid employees.The processing type assigned to the time pairs in these lines is P for attendances and A forabsences. PSG 01 and MODIF T grouping 02 relate to negative paid employees. Theprocessing classes assigned to the time pairs are S for attendances (from planned work hours),and S for absences (the assumption here is that all absences are paid).Time pair processing types are used in TM04 step 5 as part of the rules in T510S to selectwhether a time wage type should be generated. This field, therefore, plays a major role indeciding whether certain hours should, or should not be paid for different staff. The time pairprocessing type is also used for decision making in the rules in TM04 step 4.

Step 4: Calculate Overtime Hours and Flag Overtime PairsIn step 3, we saw that T555Y assignstime pairs and processing types tocollected hours. In the final line ofT555Y, notice that pair types 1 and 3(Attendances) generate processingtype M for overtime, if the attendancetype used to enter the hours hadprocessing and time type class 05(Overtime). Step 4 (lines 000410–000430) occurs if the user decides thatan employee was entitled to overtime,and then directly entered the hoursusing an overtime attendance type.

If we want the system to check to see if an employee has exceeded overtime hours thresholds, we need toconfigure the appropriate subschema.


7–10 © 1998 SAP Labs, Inc.

The subschemas are:

TW10 Overtime after 6 consecutive working days

TW15 Overtime after 8 hours per day

TW30andTW20

Overtime after 40 hours per week

Please see chapter 4 for a full description of how these subschemas work. One of the results of theprocessing in these schemas is that hours that qualify for overtime are assigned processing type M forovertime. The system then moves to step 5 for the next overtime processing stage.

Step 5: Generate Time Wage Types from Time PairsIn the delivered system, when TM04reaches step 5 (lines 000440–000490),all of the attendance hours collected instep 2 for employees not usingpositive time recording (PDC) havebeen assigned time pairs that haveprocessing type S for planned hoursor processing type M for overtimehours. Employees using PDC areprocessed by TM00, which is outsidethe scope of this document.

In step 5, the system generates timewage types from these time pairs,based on the rules configured inT510S (Time Wage Type SelectionRule table). Time wage typesgenerated from time pairs withprocessing type S are entered intointernal table DZL, with processingtype S. Time wage types generatedfrom time pairs with processing typeM will be entered into internal tableZML with processing type M.


© 1998 SAP Labs, Inc. 7–11

1. To access this step, in the IMG,choose Time Evaluation → TimeAccounting Without Clock Times→ Time Wage Type Selection andOvertime Compensation.

2. This menu path subdivides intoeight options. Several of theselines are described below.

Define valuation classes for period work schedules

With this option you can assign valuation classes to period work schedules. Different valuation classescan then be attached to the time wage type generation rules in T510S, so that a time wage type can havedifferent settings based on the period work schedule being worked.

Define groupings

This option takes you to schema TM04, where you should scroll down to the function DAYMO. Thesettings in DAYMO enable you attach different settings to the time wage type rules in T510S, based onwhich day of the week is being processed.

• Parameter 01

This parameter states that if the day being processed is between Monday and Saturday, but is not apublic holiday, (for example, it is Holiday Class 0), in T510S, use DayMo grouping 01.

• Parameter 02

This parameter states that if the day being processed is a Sunday, but is not classed as a publicholiday, in T510S, use DayMo grouping 02.

• Parameter 03

This parameter states that if the day being processed is between Monday and Saturday, and it is apublic holiday, in T510S, use DayMo grouping 02.

• Parameter 04

This parameter states that if the day being processed is a Sunday, and it is a public holiday, inT510S, use DayMo grouping 02.

You can also configure MODIF D in TMON in TM04 step 1 to set the DayMo grouping in T510S. Now,you can relate different groups of employees directly to the T510S DayMo grouping, so that differentgroups of employees can have different T510S rules based on the day of the week being processed. The

1

2


7–12 © 1998 SAP Labs, Inc.

best way to use function DAYMO and MODIF D together, is to have the DAYMO settings as set outabove, or all as 01, then control the final settings from MODIF D.

Define processing types

This option allows you to define additional processing types, if necessary.

Create wage type catalogue

This option is where your customer time wage types are created.

Set rules for wage type generation.

This line takes you to a list of the time wage types that have been defined in the system. To see how thewage type generation rules are configured for this wage type in T510S:

1. Click Execute next to Set rulesfor wage type generation.

2. Select a Country grouping andclick Continue.

3. Choose a wage type.

4. Click Details to see the screenthat begins the next section.

3

4


© 1998 SAP Labs, Inc. 7–13

Time Wage Type Selection Rule Table (T510S)

The main task of T510S is to take a given wage type and check all of the different conditions that have beenset for it for groups of employees, sets of hours, and days of the week. If all of the conditions have beenmet, the wage type is generated. The different wage type generation rules for a given wage type can bequickly looked at by clicking and at the top of the screen and scrolling from one rule to another.

The functionality of the fields is as follows:

• Tm WT Sel. Rule Group

This setting indicates the time wage type selection group assigned to MODIF W in function MOD inTM04 step 1. The same wage type can therefore have different conditions applied to it for differentgroups of employees.

• Day grouping

This setting indicates the value set in function DAYMO and MODIF D in function MOD. The samewage type can therefore have different conditions attached to it for different groups of employees ondifferent days of the week.

• Subsequent number

This is used if you have different conditions within the same time wage type selection group, and thesame day grouping. You then assign a sequential number to the same groupings. This number wouldbe used where, for example, the same wage type should be generated for more than one set of hours inthe same day.

• Valid processing types

Time pairs with the processing types listed here will have this time wage type generated.


7–14 © 1998 SAP Labs, Inc.

• Fixed Val.

In this field you can enter a fixed number of hours to be paid if an employee’s time pair meets all otherconditions, and overlaps with the conditions Start and End times at the bottom of the screen.

In this way you can, for example, pay a fixed number of hours overtime regardless of the actual hoursworked, provided the employee worked at some point during the start and end conditions.

• Cond.exit and Uncon.exit

Please read the system Help if you would like to use conditional and unconditional exits.

• Conditions Day

The following fields appear in the Conditions Day box:

Weekdays (the day of the week this wage type is valid for, where 1 = Monday, 2 = Tuesday, etc.), PHPre. Day, PH Cur. Day, PH n. day, Val. Class, and DWS class.- The top line of these fields (b1234 etc) is the public holiday class.- b stands for “holiday class blank” or 0, meaning the day is not a holiday.- Holiday class 1 is “Off, Paid”- Holiday class 2 is “Off, Unpaid”- An X under the appropriate holiday class means that the wage type is valid for these holiday

classes if the previous day, current day, or next day is a public holiday.

The example in the above screen indicates that the wage type will be generated regardless of theprevious and subsequent days, (hence b123456789 all have X), and as long as the current day has aholiday class of b or 0, (meaning the day is not a holiday).

• Conditions Time

The wage type will be generated for the hours that fall between the Start and End times.

• Min. (Minimum)

By entering a number of hours here (X) you can specify that the wage type can only be generated if theprocessing type (such as M for overtime) already contains X number of hours for the day beingprocessed.

• Symb.

This field behaves in a similar way to Min., except that X becomes a minimum of either:- S Planned hours for the day from the work schedule.- T Planned hours for the day if the employment percentage is 100%.- V Average hours per day according to the work schedule rule.

• Max. (Maximum)

By entering X number of hours in this field, you can specify that the wage type can only be generatedfor the first X hours for a particular processing type for each day.

• Symb.

This field behaves in a similar way to Max., except that X becomes a maximum of either:- S Planned hours for the day from the work schedule.- T Planned hours for the day if the employment percentage is 100%.- V Average hours per day according to the work schedule rule.


© 1998 SAP Labs, Inc. 7–15

• Relevant processing types

In this field, specify which processing types are to be taken into account in the requirement of aminimum or a maximum number of hours, in other words, which time pairs are to be counted for thosehours.

• Interval

If this field is selected, the minimum or maximum number of hours entered must have been reachedbefore the start and end times conditions.

Function GWT

In the final stage of step 5, function GWT generates time wage types from time pairs, according to therules configured in T510S, (Time Wage Type Selection Rule Table). Time wage types generated fromtime pairs with processing type S (Planned Hours) are entered in the internal table DZL withprocessing type S. Time wage types generated from time pairs with processing type M (OvertimeHours) are entered into internal table ZML, with processing type M.

Step 6: Further Processing of Overtime Wage TypesAt the end of step 5, time wage types are generated, with a number of planned or overtime hours assignedto them. In step 6 (lines 000500–000520), the addition processing is applied to the generated overtime wagetypes. Addition processing proceeds as follows:

1. Subschema TW00 is commentedout in the delivered system, but itcan be reactivated, if necessary.

This subschema is configured togenerate a higher bonus if anemployee works more than 10hours of overtime in a givenweek. It checks the overtimehours generated in MM10, and ifthey exceed 10 hours, it generatesMM20 for the additional hours.

2. Rule TC20 checks to see if thegenerated wage types have anentry in processing class 17, whichdetermines if the overtime hoursshould be paid, compensated withvacation, or both.

Rule TC20 is explained in detail inchapter 5, CompensatingOvertime with Renumeration orVacation.

1

2


7–16 © 1998 SAP Labs, Inc.

Step 7: Check Overtime Compensation AccountIn step 7 (line 000610), the overtime compensation account is checked.

1. Function ACTIO calls rule TR91.

At the end of the current payrollperiod, TR91 checks to see if all ofthe hours accumulated in timetype 0410 (Time Off for Overtime)have been used up. The rule takesthe accumulated hours for thepresent payroll period in time type0410 (Time Off from Overtime),(HRS=X0410), and adds the hoursfrom the daily balance table TESfor 0410 (HRS+D0410) andcompares the result to 0(HRS?0,00).

If the result is greater than 0 (for example, if all the hours in 0410 have not been used up), COLER40generates an error message 40 in T555E and transfers the excess hours to internal table FEHLER.ADDZLMMM00 then adds the current number and time specifications to wage type MM00 in table ZL.ADDDB0410 deducts the excess hours from time type 0410 in the daily balance table TES. MM00 thenremunerates the unused hours.

1


© 1998 SAP Labs, Inc. 7–17

Step 8: Export Results to Payroll Input File PCL2.Step 8 (line 000760) represents the final major step in the Time Evaluation program.

1. The function EXPRT stores theTime Evaluation results in thefollowing payroll input files:

• PREL

• PCL1

• PCL2, cluster B2.

The data is now ready for pickupand further processing in the nextpayroll run.

1

Main Steps in Overtime Processing, Steps 9–16Overview


Chapter 8: Main Steps in Overtime Processing, Steps 9–16


Steps 9–16: The Payroll Calculation Program..................................................................................................................................................8–1Step 9: Schema U000—Subschema UODP Imports Data From PCL2 Cluster B2 ......................................................................................8–2

Subschema UT00..................................................................................................................................................................................8–3Step 10: Rules X010 and X013 Commence Wage Type Valuation ..............................................................................................................8–4Step 11: Function MOD Sets Table Modifiers ...............................................................................................................................................8–4Step 12: Import Cluster B2 Data for PDC Employees and Process TC00 ....................................................................................................8–5

Subschema TC00..................................................................................................................................................................................8–5Overtime Functionality Comparison: TM04 (RPTIME00) Compared to TC00 (RPCALCU0) ................................................................8–7

Step 13: Weekly Overtime Analysis ..............................................................................................................................................................8–7Step 14: Process Infotype 2010 Data in X930. .............................................................................................................................................8–9Step 15: U.S. FLSA Regular Rate of Pay Valuation....................................................................................................................................8–10

Function IF UTRR................................................................................................................................................................................8–11Subschema UTR0 ...............................................................................................................................................................................8–12Rule UTR0...........................................................................................................................................................................................8–13Determining the Relevant Amounts and Number of Hours with Processing Class 85 ........................................................................8–14

Step 16: The Final Step in Wage Type Valuation, Rule X015.....................................................................................................................8–14

Overview

Chapter 7 explained steps 1–8 of overtime processing—the steps that occur in the Time Evaluationprogram RPTIME00, schema TM04. This chapter continues with steps 9–16, which take place in the PayrollCalculation program.

Steps 9–16: The Payroll Calculation Program

At the end of step 8 in the previous chapter, the results of RPTIME00 were stored in files PREL, PCL1, andPCL2. The planned and overtime hours generated for time wage types were stored in cluster B2 of PCL2,waiting for pickup in the next payroll run.

Steps 9–16 show you how the Payroll Calculation program continues the processing of the overtime hours.The delivered Payroll Calculation program for the U.S. is RPCALCU0, which can be run for as manydifferent payroll periods as the customer requires. If RPTIME00 is run every day, the payroll program hasseveral days worth of data waiting for pickup in cluster B2.

Main Steps in Overtime Processing, Steps 9–16Steps 9–16: The Payroll Calculation Program


Step 9: Schema U000—Subschema UODP Imports Data From PCL2 Cluster B2The following screenshot shows schema U000 for RPCALCU0:

Schema U000 imports and processesthe RPTIME data in the followingfashion:

1. Subschema UODP (line 000030)imports the following data fromPCL2 with function IMPRT:

• The previous payroll resultsfrom cluster RU (for the U.S.).

• The results of RPTIME00 fromcluster B.

2. Double-click on UODP to see thefunctions it contains, such asIMPRT.

3. Subschema UT00 (line 000090)processes time data forRPCALC00, including theimported RPTIME00 data.

The following screenshot of subschema UT00 highlights processing steps 10–16 for time wage types.

2

3

1



Subschema UT00

Subschema UT00 completes the following steps:

10. Rules X010 and X013 begin wagetype valuation (lines 000100–000110).

11. Function MOD sets tablemodifiers (line 000120).

12. Import cluster B2 data for PDCemployees and process TC00(lines 000150–000210).

13. Weekly overtime analysis (line000220).

14. Process infotype 2010 data in X930line 000280).

15. FLSA, regular rate of payvaluation (line 000320–000350).

16. Rule X015, the final step in wagetype valuation (line 000370).

Steps 10–16 above complete the processing of time wage types, such as overtime payments. These steps aredescribed in detail in the remainder of this chapter.

11

13

12

15

14

10

16



Step 10: Rules X010 and X013 Commence Wage Type ValuationIn step 10 (lines 000100–000110), thePayroll Calculation program callsrules X010 and X013, which calculatean hourly Rate for wage types thathave valuation basis nn. See chapter 3,Wage Type Valuation for a fulldescription of how these rules work.

Step 11: Function MOD Sets Table ModifiersIn step 11 (line 000120), function MOD calls the ESG for PCR variants for rule UMOD, which sets themodifiers for the following tables:

• MODIF A

Selects the employee grouping forabsence valuation in T554C.

• MODIF 2

Selects the payroll modifier forconstant valuations in T510J.

• MODIF B

Selects the payroll modifier forlimits in deductions in T51D1.This is net payroll and is outsidethe scope of this document.

You will see the effects of MODIF 2 instep 16 (rule X015, final wage typevaluation).



Step 12: Import Cluster B2 Data for PDC Employees and Process TC00In step 12 (lines 000150–000210), UT00 uses an IF and ELSE statement to call subschema TC00 in thefollowing fashion:

1. The IF statement means that IFPDC is active for an employee, (forexample, if an employee has aTime Management status of 2 ininfotype 0007), cluster B2 of tablePCL2 should be made availablefor processing in subschema TC00.

2. PRINT means that the time wagetypes in table ZL should beprinted on a new page (NP) in theprogram log.

3. The series DAYPR TC00 PDCinitiates the daily processing oftime data in subschema TC00,taking into account the data fromcluster B2.

4. ELSE states that if PDC is not active for an employee, (for example, if an employee does not have aTime Management status of 2 in infotype 0007), the daily processing of time data (DAYPR) insubschema TC00 will be undertaken without accessing cluster B2.

Subschema TC00

In the IF and ELSE statements in step 10, the Payroll Calculation program calls subschema TC00, whichprocesses daily time data within the Payroll program.

At this point, it is not essential for a customer to implement RPTIME00 in their system. If theyonly have basic requirements for time recording and time evaluation, then the PayrollCalculation program alone may have sufficient functionality for their needs. Please see chapter4 for a summary of the additional functionality supplied with RPTIME00.

1. Double-click on TC00 in line000180 of subschema UT00.

1

234

1



Notice that subschema TC00duplicates much of thefunctionality of schema TM04,which completed steps 1–8 of theovertime processing.

Subschema TC00 functions asfollows:

2. Function MOD calls rule TMOD,which sets table modifiers inT510S and T555Z.

3. Function TIMTP assigns aprocessing type and a time type totime pairs with T555Z.

T555Z processes hours in a similarway to T555Y (discussed in step3), and assigns processing typesand time types to time pairs.Processing types S and M flagplanned and overtime hours forfurther processing by T510S. Timepairs formed in RPTIME00 willretain the same processing typesand time types.

4. Function DAYMO sets the daygroupings for T510S.

5. Function GWT takes the hoursfrom the time pairs that meet theconditions set in T510S andgenerates time wage types.

6. Function POVT calls rule TC00 tocheck if the user has selected anovertime compensation type forthe generated time wage types.

Chapter 5 discusses the options that are available to compensate overtime by vacation and byremuneration. In TM04, this vacation and remuneration is processed in rules TC20, TC21, and TC22, andTC10, TC11, and TC12. However, because it is part of RPCALU0, and not RPTIME00, rule TC00 cannotupdate overtime time types and time quotas like TM04 would. Rule TC00 is therefore configured to updatewage type MM70 (Claim to Time Off for Overtime). MM70 is not one of the U.S.-delivered wage types.

2

3

45

6



Subschema TC00 processes daily time data for:

• All employees for whom Time Evaluation is not carried out.

• All days in a payroll period for which Time Evaluation has not been carried out up to thetime the payroll was run.

Subschema TC00 evaluates time data where only the exceptions to the work schedule havebeen recorded in infotypes 2002 (Attendances), 2001 (Absences), and 2005 (Overtime).Planned time pairs are formed in T555Z based on the specifications in the work schedule.Additional time pairs are formed where hours differ from the work schedule. SubschemaTC00 only processes RPTIME00 results for PDC employees, (who would be processed byschema TM00 in RPTIME00).

Overtime Functionality Comparison: TM04 (RPTIME00) Compared to TC00 (RPCALCU0)

The following sections compare the overtime functionality of rules TMO4 and TC00.

Schema TM04 in RPTIME00

Chapter 4 describes the different ways in which overtime can be calculated. These methods involve variousrules in schema TM04, which can be used for all employees except those whose clock-in and clock-outtimes are directly entered into the system, or entered with a time recording system (positive employees).

Modification of the rules in TM04 allows the customer greater flexibility to automatically configure thesystem to:

• Generate overtime on a daily basis, a weekly basis, and so on, with different conditions for differentgroups of staff.

• Generate overtime according to FLSA regulations.

• Generate additional vacation for overtime hours, if required.

• Accumulate daily time balances, which can then be reported.

Schema TC00 in RPCALCU0TC00 automatically generates overtime for all attendances recorded in infotypes 2002 and 2005 that areoutside of the planned hours in the work schedule. A comparison is made attendance-by-attendance,rather than on a weekly basis. The overtime wage type generation depends on the processing typeassigned to the time pair, which is assigned to the attendance in T555Z.

Step 13: Weekly Overtime AnalysisAt the end of step 12, the results of RPTIME00 are imported to RPCALCU0, and subschema UT00 hasperformed daily time data processing in TC00 for all employees not included in RPTIME00 and clock-inand clock-out employees who have been processed by schema TM00 in RPTIME00.



1. In Step 13 (line 000220),subschema XT01 analyzes theovertime wage types by period.

2. Double-click on XT01.

Subschema XT01 has been deactivated in the delivered system by the * in the execute functioncolumn (E).

A screen showing subschemaXT01 appears.

Schema XT01 goes through the following processes:

Func. Par1 Par2 Par3 Par4 Operation Descriptions

IMPRT 01 ZL Time wage types (ZL) are imported from the previouspayroll period and placed into table ZH (the current period)

INSZL 01 M The overtime wage types are extracted from the ZH table(processing type M).

SORT ZL The ZL table is sorted alphabetically.

PRINT NP ZL A new page (NP) is created in the log for all of the currentperiod and last period time wage types.

PZL X940 GEN NOAB M The ZL table is processed in rule X940 for the overtime wagetypes (processing type M). Rule X940 only processes wagetype MM01 and converts wage type MM01 to MM02 if morethan 10 overtime hours have been worked in a week.

DELZ 00 N The wage types are deleted from the previous period thatwas added to ZL by function INSZL.

1 2



Func. Par1 Par2 Par3 Par4 Operation Descriptions

PRINT NP ZL A new page is created in the log for all of the current periodovertime wage types.

EXPRT ZL The current period overtime wage types are exported back totable ZL.

Step 14: Process Infotype 2010 Data in X930.By the time we get to this step, data from all infotypes (except 2010) will have been included in the timewage type processing.

In step 14 (line 000280), the programlooks at any data entered into anemployee record in infotype 2010 andprocesses the data in rule X930.

The screenshot to the right shows anexample of infotype 2010.

In infotype 2010, the user can:

• Enter a number of hours for a wage type, an amount, or a number and unit.

• Valuate the wage type based on:- An extra pay valuation- A pay scale group or level- A pay scale group or level from a selected position or work center

ValuationBasis *

ValuationBasis X


8–10 © 1998 SAP Labs, Inc.

- An overtime compensation type- A premium- An external document, such as an invoice

The screenshot to the right shows ruleX930. Notice that the rule first makes adecision on the valuation basisentered by the user in infotype 2010.


000010 A decision (D) is made on the valuation basis entered for the wage type in infotype 2010(VALBS?0).

000020 to000060

If the valuation basis is * (for example, data has been entered in the first part of infotype 2010,as highlighted on the previous page), the wage type is processed in the following fashion:

• If the wage type has an Amount entered (D AMT = BETRGAMT?0), pass it on withoutfurther processing (OPIND ADDWT *).

• If there is not an Amount but there is a Number (of hours), (D NUM?0).

• If there is something in the Number field, pass it on without further processing (ADDWT*).

• If there is no Amount, and there is no Number (of hours), fill the wage type Number withthe value from the number/units fields in 2010 (NUM= ANZHLADDWT *).

000070 If the valuation basis is X (for example, the data has been entered in the second part of 2010,as highlighted on the previous page), the wage type passes to rule X935 for further processing(Z GCY X935). Rule X935 then leads to a series of rules that process the wage type based onthe entries in the second part of infotype 2010. This area of processing is outside the scope ofthis document, but please read the documentation for these rules for a description of howthey work.

Step 15: U.S. FLSA Regular Rate of Pay ValuationChapter 4 summarizes the U.S. Fair Labor Standards Act (FLSA), which stipulates that certain employeesshould be paid overtime for excess hours worked per week. In addition, some state laws legislate thatovertime is paid for excess hours worked per day. Chapter 4 described the rules in schema TM04 inRPTIME00, which are used to calculate the excess hours per day or per week and should count towardsovertime. The FLSA legislation also lends the second part to the overtime equation, called the Regular Rateof Pay, which helps determine the Rate at which excess hours should be paid.


© 1998 SAP Labs, Inc. 8–11

Chapter 3 described the different ways in which an hourly Rate can be calculated, using wage typevaluation. Step 15 (lines 000320–000350) contains a different type of wage type valuation that is designed towork according to the regular rate of pay set out in the FLSA laws.

In short, the FLSA regular rate of pay can be defined as follows:

• For hourly paid employees, their rate of pay is the hourly rate at which they are usually paid.

• For salaried employees, their rate of pay is the salary divided by the number of hours for which thesalary is intended to compensate.

• For employees paid on a piecework or commission basis, their rate of pay is the total earnings for theweek, divided by the hours worked.

The following list of payment examples should be included in the regular rate of pay:

• Non-discretionary bonuses

Any agreed upon or previously announced bonus or incentive plan related to production, efficiency,attendance, quality, or some other measure of performance, must be included in the regular rate of payfor the workweek in which it was earned.

• Shift premiums

An amount added to the hourly rate for working an evening, late night, or other undesirable shift.

• Non-cash payments

The reasonable cost to the employer or the fair market value of payments made in the form of goods orservices, (for example, meals and lodging).

• Retroactive pay or back pay awards

• On-call pay

• Cost of living adjustments

Function IF UTRR

Step 15 (lines 000320–000350) comprises the following functions:

1. IF calls rule UTRR.

2. Double-click on UTRR.

1 2


8–12 © 1998 SAP Labs, Inc.

Rule UTRR appears. The lines ofthis rule are described below.


000010 A decision (D) is made on the employee subgrouping for the PCR value (OUTWPABART).

000020 A second IF condition is set. SCOND=F IF means that if the ESG for PCR value is not 1, thecondition is false.

000030 A decision (D) is made on the setting in the Working Week field in infotype 0007(OUTWPWWEEK).

000040 If the ESG for PCR value is 1, but the Working Week field in infotype 0007 is less than twocharacters, the condition is not fulfilled (1 *).

000050 If the ESG for PCR value is 1, and both fields in the Working Week field are filled (for example,with 01), the condition is fulfilled (1 **). If the condition is fulfilled, subschema UTR0 isprocessed in the next function.

Subschema UTR0

1. In subschema UT00 (step 15) inline 000330, the copy function callssubschema UTR0, which processeshourly paid employees (ESG forPCR value 1) who have aworkweek entered in infotype0007.

2. Double-click on schema UTR0.

1 2


© 1998 SAP Labs, Inc. 8–13

3. In schema UTR0, the line ZLITUTRO GEN NOAB * puts thewage types from the ZL table intothe payroll input table accordingto rule UTR0, which processesthese wage types as described inthe following section.

4. Double-click on rule UTR0.

Rule UTR0

1. Rule UTR0 makes a decision (D)on the value of processing class 85for the wage type being processed(VWTCL 85).

2. If the wage type has a PC85 valueof anything other than 1–5, it ispassed on without furtherprocessing in rule UTR0 (ADDWT*).

3. For wage types with PC85 values1–5, SETIN X= WWADDWT * setsvariable splits based on theworkweek selected in infotype0007, and attaches that split to thewage type.

Processing continues in subschema UTR0 in the following fashion:

4. PRINT NP V0 creates a new pagein the log for the variable splits.

5. X015 then valuates every wagetype (GEN, NOAB) selected by thedecision rule UTRR, so the FLSAqualifying wage types will nowhave a Number of hours (fromTime Management) and anAmount (calculated in X015).However, the Amount will notnecessarily have been calculatedby X015 using the correct Rate forthe FLSA qualifying wage types.

6. RGRT calculates regular Rate of pay for FLSA qualifying wage types. To follow FLSA regulations,wage types that are considered to be regular rates of pay should be configured with a value in

34

12

3

4567


8–14 © 1998 SAP Labs, Inc.

processing class 85. RGRT looks for wage types that have processing class 85 values and processesthese values again in the input table. This process takes the relevant Amounts and Number of hours(according to the PC85 value), and determines the Rate for the relevant workweek by dividing therelevant Amount by the relevant Number of hours.

7. UTR1 GEN NOAB deletes any special wage types and is deactivated in the delivered system.Processing now returns to subschema UT00 for step 16.

Determining the Relevant Amounts and Number of Hours with Processing Class 85

The processing class 85 values work in the following fashion:

• Value 1 contributes the Number of hours and the Amount to the regular rate.

This value should be used for wage types that are not valuated against basic pay (for example, theirvaluation basis is not nn).

• Value 2 contributes the Number of hours only to the regular rate.

This value should be used for wage types that are not valuated against basic pay (for example, theirvaluation basis is not nn).

• Value 3 contributes the Number of hours and the Amount to the regular rate.

This value should be used for wage types that are valuated against basic pay, (for example, theirvaluation basis is nn).

• Value 4 contributes the Number of hours only to the regular rate.

This value should be used for wage types that are valuated against basic pay, (for example, theirvaluation basis is nn).

• Value 5 does not contribute to the regular rate.

Step 16: The Final Step in Wage Type Valuation, Rule X015In step 16 (line 000370), rule X015performs the final step in theprocessing and calculates the overtimeAmount to be paid for all wage types,except the FLSA qualifying wagetypes that were valuated in step 14.Rule X015 is described in detail inchapter 3, Wage Type Valuation.

GlossaryError! No text of specified style in document.


GlossaryModifiers Used in rule UMOD to set value ranges for tables.

The following tables use modifers:

• MODIF1 = T510S Wage Type Generation

• MODIF2 = T510J Constant Valuation

• MODIF3 = T030 Fixed Accounts

• MODIFA = T554C Absence Valuation

• MODIFB = T51D1 Limits for Deductions

• MODIFC = Valuation Basis for Month-endAccrual

• MODIFD = Wage Type Processing with Regardto Month-end Accruals

• MODIFW = T510S Wage Type Generation

The modifiers allow you to set a specific range oftable entries for different groups of employees.

Operation Building block for rules that is used to process wagetypes.

PIT Processing Input Table

Based on designated rules, PIT accesses a personnelcalculation rule that processes contents of inputtable IT.

PORT Transfers data from the previous payroll; based onspecified rules, PORT initiates a cycle whichprocesses the wage types of the old results table.

Processing Class Stored in T512W, this item is used in rules todetermine which version of the rule should beselected for a particular wage type.

PZL Process time wage type table ZL.

RPTIME00 The time evaluation drive, it is used to evaluateemployee time data which has been recorded usingtime infotypes or at time recording systems.

Rte, Num, Amt The elements of a wage type.

Rule Controls how wage types are processed duringpayroll processing (rules consist of operations).

Schemas A series of sequential processing steps for payrolland time evaluation.

Main schema

GlossaryError! No text of specified style in document.

2 © 1998 SAP Labs, Inc.

U000 – U.S. Payroll accounting schema forRPCALCUO

K000 – Canadian payroll accounting schema forRPCALCUO

TM00 – Main schema for Time Management

TM01 – Time evaluation schema for exceptions tothe work schedule.

TM04 – Time evaluation schema without clocktimes.

Subschema Contains processing steps needed by payroll.Subschemas are called from a main schema usingfunction “copy.”

Time types An allocation of times based on payment aspects.

Time Wage Type A wage type that needs to be valuated because itcarries only a unit (i.e., hours, days, etc.)

Valuation Basis Technical Wage types 100X (i.e. /001) and is used tostore hourly rates that will be used against timewage types that need to be paid.

Valuation Rule Class Assigned to absences to determine how they will beprocessed in payroll.

Wage types Represents deductions, earnings, or tax codes.

IndexError! No text of specified style in document.


IndexA

Absence hours 7–8processing type A 7–7

Absence typesassigning classes 7–6assigning processing types 7–6

Absence valuation grouphaving different 2–13MODIF A 2–10, 7–4, 8–4

Absences 7–5, 7–7, 7–9, 8–7evaluating using TM04 7–2recorded 4–9, 4–12, 4–13

Absensesrecorded 4–17

Accessingdifferent rule variants 2–11Help to view source text 2–5rules using IMG or PE02 2–5rules using MOD 2–8rules using PIT and PORT 2–7schemas using IMG or PE01 2–5

ACTIO4–7, 4–10, 4–11, 4–12, 4–14,7–16

ADDB0903Z 4–11ADDDB

updating daily balance table TES4–5

ADDDB00415–4, 5–5, 5–6, 5–7, 5–9

ADDDB0042 5–4, 5–5, 5–6, 5–8ADDDB00435–4, 5–5, 5–6, 5–7, 5–

8ADDDB04105–4, 5–5, 5–6, 5–7, 5–

8, 5–9ADDDB0900 4–15ADDDB0900Z 4–15ADDDB0903Z4–5, 4–7, 4–10, 4–11,

4–12, 4–13, 4–14ADDDB0903ZCOLOP 4–9ADDDB0904 4–8, 4–9ADDDB0904Z4–7, 4–10, 4–11, 4–

16ADDDB0905Z 4–17, 4–18ADDDB0906Z 4–7Addition processing 7–15ADDNA 3–9ADDNA * 3–10ADDWT 3–8ADDWT *3–4, 3–5, 3–6, 3–7, 3–8,

3–10, 3–23, 8–10, 8–13ADDWT /001 3–5ADDZLM* 5–4, 5–5, 5–6, 5–7, 5–8

ADDZLMMM00 7–16ADDZML1 5–4, 5–5, 5–6, 5–7, 5–8ADDZML2 5–4, 5–5, 5–6, 5–7, 5–8Adjust average bases to pay scale3–

39Adjustment field 3–39Adjustment rules

cumulation types 3–39fields 3–39for averages bases 3–38

Amending schemas and rules 2–15AMT = BETRGAMT?0 8–10AMT?0 3–8AMT=M 3–11Asences

recorded 4–2Assigning

collected hours to time pairs 7–8hours to time pairs 7–5valuation bases to overtime wage

types 3–26Attendance days, consecutive

calculating using TW10 4–17Attendance hours 7–8, 7–10

Processing type P 7–7Attendance quotas

infotype 2007 1–1Attendance types

configuring to time pairs 1–2defining classes 7–7

Attendancesevaluating using TM04 7–2infotype 2002 1–2schema TC00 8–7

Attributes buttonviewing program class and

country grouping 2–5Automatic overtime generation 1–1Average rates

valuating time wage types 3–29Averages calculation

adjustment rules 3–38fields and funcitionalities 3–36no hours in number field of MV3–

11rule X018 processes final 3–10rules 3–34table MV 3–10, 3–11

Averages configurationvaluating time wage types 3–29

Averages processingconfiguring from scratch 3–29configuring wage types for 3–3

evaluating primary wage types3–31

first step, rule X016 3–9including primary wage types3–

29rule X015 branches to X016 3–8rules X016, X017, and X018 3–3

B

B2 8–1, 8–3, 8–5importing data for PDC

employees and process TC008–5

Back pay 4–4, 8–11Basic pay

infotype 0008 2–14maintaining for valuation bases3–

20Basic pay wage types 3–3, 3–19

C

Calc. rule 3–37Calculating overtime

according to consecutiveattendance days 4–17

daily 4–14hours 7–9on daily or weekly basis 4–1

Clock-in, clock-out1–1, 4–2, 7–1, 8–7

Cluster B 4–2COLER40 7–16Collected hours

assigning to time pairs 7–8COLOP 4–8, 4–10, 4–16, 4–18COLOP*4–8, 4–9, 4–11, 4–13, 4–

16, 4–17Compensating overtime

choosing compensation types 5–2vacation with derived wage type

percentages 5–4, 5–6with remuneration5–4, 5–5, 5–6,

5–8with remuneration and vacation5–

1, 5–4, 5–5, 5–6, 5–7, 5–8with vacation 5–5, 5–7, 5–9

Compensationinfotypes 2005 and 2007 1–1

Compensation types 5–3choosing 5–2overtime 5–5, 5–8

Cond.exit 7–14Conditions



Day 7–14Time 7–14

Configuringcustomer requirements 2–15overtime calculations4–6, 4–14,

4–17overtime compensation 5–3, 5–7processing class 17 for overtime

wage types 5–2schemas and rules 2–15wage type valuation 3–12

Configuring wage type valuation3–19, 3–26

Constant valuationconstants dependant on pay scale

3–18creating bases 3–12dependant on wage types 3–13determining per wage type 3–13general processing of time data3–

16modifier for 3–15

Constant wage type valuation 2–10Constants dependant on pay scale3–

18Constants dependant on wage types

3–13determine constant valuation per

wage type 3–13general processing of time data3–

16modifier for constant evaluation3–

15Contract field

configuring in IMG 2–14Copy function

calling subschemas 2–3Copying

schemas and rules 2–15Cost of living adjustments 4–4, 8–11Country grouping 3–13Create constant valuation bases 3–12

constants dependant on pay scale3–18

constants dependant on wagetypes 3–13

Create person-related valuation bases3–19

form valuation bases 3–21, 3–23general processing of time data3–

24Create wage type catalogue 7–12Cumulation field

averages calculation 3–37Cumulation types 3–37

adjustment rules 3–39

for averages 3–38Customer configuration

requirements 2–15tracking schemas and rules2–16,

2–18Customer rules 2–13Customer time wage types 7–12

D

D0904 4–10Daily balance table TES4–4, 4–5, 4–

15, 5–5operation ADDDB 4–5rule TC10 5–7, 5–8rule TC11 5–8rule TC12 5–9rule TC20 5–4rule TC21 5–5rule TC22 5–6rule TO01 4–15rule TW01 4–13rule TW03 4–14rule TW33 4–10rule TW34 4–11rule TW36 4–12subschema TW20 4–12time type 0410 7–16

Daily overtime after X hourstime type 0900 4–4, 4–15

Data flowrules TC10, TC11, TC12 5–3rules TC20, TC21, TC22 5–3

Day grouping 7–13Day types 4–15DAYMO 7–11, 7–13, 8–6DAYPR 8–5Define groupings 7–11Define processing types 7–12DELZ 8–8Derived wage types3–29, 5–2, 5–4,

5–5, 5–6, 5–7, 5–8Descriptions, schemas and rules

changing or ammending 2–18Determine constant valuation per

wage type 3–13Disability entitlements

using averages configuration 3–29Display data 2–6DIVID ANR 3–11DIVID ARR 3–4, 3–28Documentation button

explaining schemas or rules 2–5Documentation, schemas and rules

changing or ammending 2–18new 2–18RPDSYS00 program 2–5

E

EEpay scale group 3–39remuneration 1–1subgroup grouping 3–40

ELIMI 3–5ELSE function 4–6, 4–11

schema TM04 7–5schema UT00 8–5subschema TC00 8–5

Employee groupingsusing rule variants 2–12

Employee groupings 2–12Employee Subgroup Grouping for

Personnel Calculation Rules (ESGfor PCR) 2–8

Employee Subgroupsrelating to table settings 2–8

Employees groupingsoperation OUTWP 2–13

Employees with workweekshaving start times 4–6without start times 4–11

EMPLR 2–14ENDIF 7–5Entering overtime

automatic generation 1–1manual data entry 1–1

ESG for PCR value 1 2–9, 8–12employee table links 2–10exception to rule X013 3–3hourly paid staff 2–12rule X013 3–6

ESG for PCR value 2 2–9employee table links 2–11rule X013 3–6

ESG for PCR value 3 2–10employee table links 2–11

ESG for PCR variantsconfiguring 2–15

Evaluation bases See Valuation basesExempt employees 4–3Exporting results to PCL2 7–17EXPRT 7–4, 7–17, 8–9

F

F. process 3–37Fair Labor Standards Act (FLSA)4–

2, 8–7exempt and nonexempt employees

4–3federal law verses state law 4–3qualifying wage types 8–13, 8–14regular rate of pay 4–3, 8–3, 8–10

FILLF N 3–9



FILLPVM 4–9, 4–10, 4–16, 4–18First-derived wage type 3–9

fields for valuation 3–29rule TC10 5–7rule TC11 5–8rule TC20 5–4rule TC21 5–5rule TC22 5–6

Fixed Val. 7–14Flextime 4–2

timetypes 7–1FLSA See Fair Labor Standards ActForm valuation bases

addition 3–21division 3–23

Functions of schemas 2–6

G

GCY4–8, 4–9, 4–12, 4–13, 5–4, 5–5,5–8, 5–9, 8–10

GEN 2–7, 2–8, 8–8, 8–13, 8–14General processing of time data USA

3–16, 3–24GENTPB 4–10, 4–16GENTPE 4–9Grouping employees

using operation OUTWP2–12, 2–13

using rule variants 2–12with different payment structures

2–12GWT 7–15, 8–6

H

Helpclicking for operation descriptions

3–5consulting on MODIF 2–11using to view source text 2–5

Hourly paid staffESG for PCR value 1 2–12regular rate of pay 8–11subdividing 2–13subschema UTR0 8–12

Hourly rateprocessing with configured rule

variant 2–12using rules X010 and X013 to fill

PIT 3–4Hours

assigning to time pairs 7–5, 7–8Hours collection

schema TM04 7–3, 7–5Hours reduced 3–40Hours stored for next week

time type 0904 4–4

Hours stored for this weektime type 0903 4–4

HRS*%012 5–4, 5–5, 5–6HRS*1,00 5–7, 5–9HRS?0,00 7–16HRS?6,00 4–18HRS?COVERT 4–9HRS?D0900 4–16HRS?D0906 4–8, 4–9HRS+1,00 4–18HRS+D0410 7–16HRS+PNUM 4–9, 4–16HRS=0,00 4–11, 4–13, 4–15, 4–17HRS=1,00 4–18HRS=48,00 4–7HRS=8,00 4–15HRS=99,00 4–15HRS=COVERTHRS-D0903 4–10HRS=D0900 4–16HRS=D0903 4–9, 4–10, 4–12, 4–14HRS=D0904 4–10, 4–16HRS=IWWEEKHRS+24 4–7HRS=L0905 4–18HRS=M0903 4–7, 4–11, 4–13HRS=M0904 4–7HRS=PBEG 4–8HRS=PEND 4–9HRS=PNUM 4–8HRS=R 4–9HRS=S 4–15HRS=X0410 7–16HRS>8,00 4–15HRS-D0904 4–16HRS-M0903 4–10, 4–12, 4–14HRS-M0904 4–10, 4–11

I

ID: Vbasis 3–39IF function 7–5

rule TW00 4–17, 4–18rule TW31 4–6rule UTRR 8–11, 8–12schema TM04 7–5schema UT00 8–5subschema TC00 8–5subschema TW10 4–17subschema TW30 4–6

IMPRT 2–6, 8–2, 8–8Ind:AMT 3–39Ind:NUM 3–39Ind:RTE 3–39Infotype 0001

Organizational Assignment 2–14using the Contract field 2–14

Infotype 0005Leave Entitlement 4–2

Time Evaluation 7–1Infotype 0007 4–6, 4–11

pair type 1 7–8Planned Work Time 2–14rule TW31 4–6, 4–7rule UTR0 8–13rule UTRR 8–12schema UT00 8–5subschema TW30 4–5subschema UTR0 8–12

Infotype 0008Basic Pay 2–14basic pay configurations 3–20total working time 3–23

Infotype 2001pair type 2 7–8subschema TC00 8–7

Infotype 2002entering overtime manually 1–2pair type 3 7–8subschema TC00 8–7

Infotype 2005choosing compensation types 5–2choosing remuneration or

compensation 1–1entering overtime manually 1–1rule TC11 5–3, 5–8rule TC21 5–3, 5–5subschema TC00 8–7

Infotype 2007choosing compensation types 5–2choosing remuneration or

compensation 1–1entering overtime manually 1–1rule TC11 5–3, 5–8rule TC21 5–3, 5–5

Infotype 2010 8–9as factor in rate 3–9averages processing 3–37entering overtime manually 1–1rule X930 8–9, 8–10subschema UT00 8–3

Infotype 2011time recording terminals 7–8

INSZL 8–8Interval field 7–15IWWEEKADDDB0906Z 4–7

L

Leave compensation 5–2Leave entitlement

infotype 0005 4–2

M

M0903 4–10



Maintain basic pay for valuationbasis 3–20

Manual data entry 1–1infotype 2002 1–2infotype 2005 1–1infotype 2007 1–1infotype 2010 1–1

Master data configuration2–12, 2–15Max. 7–14Max.No.Per 3–37MEANV 01 3–10, 3–33, 3–37MEANV 02 3–10, 3–33MEANV REL 3–10Min. 7–14Minimum wage 4–3MM00, wage type 3–14, 7–16MM01, wage type 8–8MM02, wage type 8–8MM10, wage type 7–15MM20, wage type 7–15MM70, wage type 8–6MOD function

accessing rules 2–8calling rule UMOD 2–8in schema UT00 3–17relating employee subgroups to

table settings 2–8setting table modifiers7–3, 7–4,

8–4subschema TC00 8–6subschema UT00 8–3

MODIF 2 8–4payroll modifier in T510J 2–10

MODIF A 7–4, 8–4absence valuation group 2–10

MODIF B 8–4payroll modifier in T51D1 2–10

MODIF D 7–11, 7–13MODIF function

different uses 2–11MODIF T 7–4, 7–8, 7–9MODIF W 7–4, 7–13Modifier for constant evaluation3–15Monthly balance table SALDO4–4,

4–5rule TW34 4–11

MULTI NRA 3–8, 3–10, 3–11

N

Naming conventionscustomer-configured schemas and

rules 2–18schemas and rules 2–15

Negative time processing4–2, 4–5,7–2schema TM04 4–2

Negative time recordingpair type 1 7–8

NEXTR 3–9No.periods 3–39No.rel. per 3–37NOAB 2–7, 8–8, 8–13, 8–14Non-cash payments 4–4, 8–11Non-discretionary bonuses 4–4, 8–11Nonexempt employees 4–3NP 8–5, 8–8, 8–13NUM?0 3–8, 8–10NUM?0.00 3–11NUM= ANZHLADDWT * 8–10Number of hours

determing with PC 85 8–14

O

On-call pay 4–4, 8–11Operation descriptions

rule TO01 4–15rule TO02 4–16rule TW00 4–17rule TW06 4–8rule TW31 4–7rule X010 3–5rule X013 3–6, 3–7rule X015 3–8

Operation OUTWPgetting rules to make decisions2–

14grouping employees 2–12, 2–13other field decisions 2–15

OPIND 8–10Organizational Assignment

infotype 0001 2–14OUTOTCLTYP 5–5, 5–8OUTTPEXTIM 4–8OUTTPPTYPE 4–8, 4–13, 4–16OUTTPVTYPE4–8, 4–11, 4–13, 4–

16OUTWP See Operation OUTWPOUTWPABART 8–12OUTWPEMPLR 2–14OUTWPWWEEK 8–12OVERT 4–9Overtime

attendance types 7–9calculating consecutive attendance

days 4–17calculating daily 4–1calculating daily 4–14calculating on a weekly basis4–1,

4–5compensating with remuneration

and vacation 5–1

compensation account checked7–4

compensation account,checking of7–16

configuring compensation in rulesTC10, TC11, TC12 5–7

configuring compensation in rulesTC20, TC21, TC22 5–3

generating, modifying rules 8–7processing, Payroll Calculation

program 8–1requirements, state and federal4–3weekly analysis 8–3, 8–7

Overtime compensation types5–5, 5–8type 1 5–5, 5–8type 2 5–5, 5–8type 3 5–5, 5–9

Overtime hourscalculating 7–9processing type M 7–7, 7–9time type 0040 4–4

Overtime time pairsflagging 7–9schema TM04 7–3subschema TW20 4–12

Overtime time typesrule TC00 8–6

Overtime wage types 3–2configuring processing class 175–

2depending on attendance in

T555Z 8–7further processing of 7–15schema TM04 7–3subschema XT01 8–8, 8–9

P

P. Mod 3–14, 3–15, 3–16P2000 7–5, 7–8P2001 7–5P2002 7–5P2003 7–5Pay increase 3–40Pay scale 3–28Payment structures

grouping employees 2–12Payroll Calculation program2–1, 4–

2, 8–1RPCALCU0 2–2, 7–1subschema TC00 8–5wage type valuation rules 3–3

Payroll input fileexporting results to PCL2 7–17PCL2 4–2

Payroll input table



subschema UTR0 8–13Payroll Input Table

filling with hourly rate using rulesX010 and X013 3–4

Payroll modifierhaving different in T510J and

T51D1 2–13in T510J, MODIF 2 2–10, 8–4in T51D1, MODIF B 2–10table T51D1, MODIF B 8–4

Payroll output table 3–28Payroll periods

adjustment rules 3–38averages calculation 3–37averages processing 3–37

PCL1 7–17, 8–1PCL2 7–17, 8–1, 8–2, 8–5

exporting results to 7–17PDC 8–5PDC employees 8–3, 8–7

importing cluster B2 data 8–5PDC time recording 4–2

evaluating with TM00 7–2PE01 See Transaction PE01PE02 See Transaction PE02Percent 1 3–40Percent 2 3–40Percentage

applied to valuated amount 3–28increases, adjusting average bases

3–40Period work schedules

assigning valuation classes 7–11PIT See Process Input TablePlanned work time

infotype 0007 2–14processing type S 4–8, 7–7, 7–9

PORT See Process Old Results TablePORT function

set up charts 2–8POS 7–5Positive time 1–1Positive time recording (PDC) 7–10POVT 8–6PREL 7–17, 8–1PRINT 2–6, 8–5, 8–8, 8–9, 8–13Process data 2–6Process Input Table (PIT) 2–4

accessing rules 2–7processing data 2–6set up charts 2–8

Process Old Results Table (PORT)2–7accessing rules 2–7

Processing class 171–1, 5–2, 5–3, 5–4, 5–7

configuring for overtime wagetypes 5–2

rule TC20 7–15rules TC10–12 5–2, 5–3rules TC20–22 5–2, 5–3value 1 5–7value 2 5–7value A 5–4value B 5–4value C 5–4value V 5–8values 1–9 and V 5–7values 3, 4, 5 5–8values 6–9 5–8, 5–9values D, E, and F 5–4, 5–5, 5–6

Processing class 85 8–13, 8–14determining number of hours 8–14determining relevant amounts8–

14regular rate of pay 8–14

Processing typeM 7–10

Processing type Atable T555Y 7–7

Processing type M1–2, 7–7, 7–9, 7–10changed from S 4–9, 4–10, 4–16rule TO00 4–18rule TO02 4–16subschema TC00 8–6subschema TW20 4–12subschema XT01 8–8table T555Y 7–7, 7–9table ZML 7–15

Processing type Prule TO00 4–18table T555Y 7–7

Processing type S 7–10planned work time 4–8rule TO02 4–16, 4–17rule TW02 4–13rule TW04 4–9rule TW06 4–8rule TW35 4–11subschema TC00 8–6table DZL 7–15table T555Y 7–7, 7–9

Processing types 7–9, 8–6assigned by absences types 7–6assigned by attendance types 7–7assigned to time pairs 8–6assigning to time pairs 7–7defining additional 7–12relevant 7–15table T555Y 7–7valid 7–13

PTIP 4–8, 4–11PZL 8–8

Q

Quota type 01 1–1

R

Rate of pay See Regular rate of payRead data 2–6Reduction in hours

same pay 3–40Regular rate of pay 4–3, 8–10

configuring in processing class 858–13

definition 8–11payment examples 8–11processing class 85 values 8–14

Rel. test 3–37Relating employee subgroups to

table settings 2–8Relevancy tests

averages calculation 3–37Relevant amounts

determining with PC 85 8–14Relevant cumulation rule in T511A

3–11Relevant processing types 7–15Remuneration1–1, 3–9, 5–1, 5–2, 5–

4, 5–7, 5–8, 8–6infotypes 2005 and 2007 1–1overtime compensation5–1, 5–4,

5–5Retroactive pay 3–38, 4–4, 8–11

increases, four options 3–39or back pay awards 4–4

RGRT 8–13RPCALCK0

Payroll Calculation program,Canada 2–2

RPCALCU0 7–1, 8–1, 8–2, 8–7in schema TC00 8–7Payroll Calculation program, U.S.

2–2RPCALCX0 7–2RPCALU0 8–6RPDSYS00 program 2–14

fields OUTWP makes decisionson 2–15

schemas and rules documentation2–5

RPTIME004–2, 4–4, 7–1, 8–1, 8–2,8–5, 8–6, 8–7schema TM04 in 8–7subschema TC00 8–7Time Evaluation program 4–2

RTE 3–23



RTE?0 3–8RTE=TSDIVP 3–4, 3–23, 3–24RU 8–2Rule TC00 8–6, 8–7Rule TC10 5–1, 5–3, 5–7

configuring compensation 5–2PC17 values 1-9 and V 5–3

Rule TC11 5–3, 5–8configuring compensation 5–2PC17 values 6-9 5–3

Rule TC12 5–3, 5–9configuring compensation 5–2PC17 values 6-9 5–3

Rule TC20 5–1, 5–4configuring compensation 5–2configuring overtime

compensation 5–3PC17 values A-F 5–3processing class 17 7–15

Rule TC21 5–3, 5–4, 5–5, 6–2configuring compensation 5–2configuring overtime

compensation 5–3PC17 values D, E, and F 5–3

Rule TC22 5–5, 5–6configuring compensation 5–2configuring overtime

compensation 5–3PC17 values D, E, and F 5–3

Rule TMOD 8–6Rule TO00 4–18Rule TO01 4–14, 4–15, 4–16

operation descriptions 4–15Rule TO02 4–16

operation descriptions 4–16Rule TR91 7–16Rule TW00 4–17, 4–18

called by subschema TW10 4–17operation descriptions 4–17

Rule TW01 4–13subschema TW20 4–12

Rule TW02 4–13behaves like rule TW35 4–13subschema TW20 4–12

Rule TW03 4–14behaves like rule TW36 4–14subschema TW20 4–12

Rule TW044–9, 4–10, 4–12, 4–13,4–14

Rule TW06 4–8, 4–9operation descriptions 4–8

Rule TW31 4–6, 4–7, 4–8, 4–10operation descriptions 4–7

Rule TW32 4–6, 4–8Rule TW33 4–6, 4–10Rule TW34 4–6, 4–11

Rule TW35 4–6, 4–11behaves like rule TW02 4–13

Rule TW36 4–6, 4–11, 4–12behaves like rule TW03 4–14

Rule UMOD 3–15, 3–17, 3–18, 8–4called by function MOD 2–8variant $MOD 2–8

Rule UTR0 8–13Rule UTRR 8–11, 8–12, 8–13Rule variants

accessing 2–11configuring 2–8grouping employees 2–12maintaining 2–8processing an amount 2–12processing an hourly rate 2–12rule X013 3–6rule X015 3–7, 3–9

Rule X010 3–5, 3–7commence wage type valuation8–

4filling PIT with hourly rate 3–4form valuation bases, addition3–

21operation descriptions 3–5subschema UT00 8–3summary, valuation flow 3–3

Rule X013 3–6, 3–7commence wage type valuation8–

4filling PIT with hourly rate 3–4form valuation bases, division3–

23operation descriptions 3–6, 3–7subschema UT00 8–3summary, valuation flow 3–3variant for ESG for PCR 1 3–6variant for ESG for PCR 2 3–6

Rule X015 3–7, 8–4, 8–13, 8–14operation descriptions 3–8summary, valuation flow 3–3variant for ESG for PCR 1 3–7variant for ESG for PCR 2-9 3–9wage type valuation, final step8–

3, 8–14Rule X016 3–8, 3–9, 3–33

averages calculation 3–37averages processing 3–3

Rule X017 3–10averages calculation 3–37averages processing 3–3processed by calculation rule 3–10

Rule X018 3–10averages processing 3–3, 3–37cumulation types 3–38

processing final averagescalculation 3–10

Rule X115 3–9Rule X930 8–9, 8–10

processing infotype 2010 8–9Rule X935 8–10Rule X940 8–8Rules

accessing using IMG or PE02 2–5changing descriptions 2–18configuring 2–15configuring variants 2–8copying and ammending 2–15documentation, RPDSYS00 2–5documenting new or ammended2–

18maintaining variants 2–8naming conventions 2–16tracking customer rules 2–16upgrading 2–15wage type valuation 3–2

S

Salaried employeesassigning rule variant values 2–12regular rate of pay 8–11semi-monthly paid 2–12weekly paid 2–12

SALDOSee Monthly balance tableSALDO

SchemaTM04 7–1

Schema TC00 See Subschema TC00Schema TM00 7–10

evaluating PDC time recording4–2

in RPTIME00 8–7Time Evaluation program 7–2

Schema TM04 5–1, 7–11, 8–1, 8–6compared to rule TC00 8–6, 8–7configuring tips 4–5evaluating attendances and

absences 4–2in RPTIME00 8–7negative time processing 4–2screenshot 7–3subschema TW10 4–17subschemas TW30 and TW20 4–5Time Evaluation program 7–2using subschema TW15 4–14

Schema U000 2–2UODP importing data from B28–

2Schema UT00 3–17

general processing of time data3–24



screenshot 2–8Schema XT01 See Subschema XT01Schemas 2–2

accessing using IMG or PE01 2–5changing descriptions 2–18configuring 2–15copying and amending 2–15documentation, RPDSYS00 2–5documenting new or ammended2–

18functions 2–6naming conventions 2–16tracking customer schemas 2–16upgrading 2–15

SCOND=F 4–17, 4–18SCOND=T 4–18Second-derived wage type 3–9

rule TC10 5–7rule TC11 5–8rule TC20 5–4rule TC21 5–5rule TC22 5–6valuation fields 3–29

Sequence of attendance daystime type 0905 4–4

Set valid entries in tables 2–6SETIN 8–13Shift premiums 4–4, 8–11SORT 8–8Source Text button

viewing schema or rule 2–5Start time of the workweek

time type 0906 4–4Start times

workweeks having 4–6Subdividing

hourly paid staff 2–13Subschema TC00 8–5, 8–6, 8–7

called by Payroll Calculationprogram 8–5

called by schema UT00 8–5compared to TM04 8–7in RPCALCU0 8–7RPTIME00 8–7

Subschema TW00 7–15Subschema TW10 4–17

calling rule TW00 4–17configuring overtime hours 7–10consecutive attendance days 4–17processing rule TO00 4–18rule TW00 4–17, 4–18

Subschema TW15calculating daily overtime 4–14calling rule TO02 4–16configuring overtime hours 7–10

Subschema TW20

configuring overtime hours 7–10rule TW01 4–12rule TW02 4–12rule TW03 4–12, 4–14weekly overtime for one

workweek 4–5, 4–12Subschema TW30

calling rule TW34 4–11calling rule TW35 4–11calling rule TW36 4–12configuring overtime hours 7–10different workweek definitions4–

5, 4–6IF and ELSE functions 4–6PTIP calls rule TW32 4–8rule TW33 4–10workweeks without start times4–

11Subschema UODP

importing data from B2 8–2Subschema UT008–3, 8–5, 8–14.

See also Schema UT00processing time date for

RPCALC00 8–2time data processing in TC00 8–7

Subschema UTR0 8–12, 8–13Subschema XT01 8–8Subschemas 2–2Subsequent number 7–13Symb. 7–14

T

Table DZL 7–10, 7–15Table FEHLER 7–16Table modifers

setting, MOD 7–3Table modifiers

T510S and T555Z 8–6Table MV3–10, 3–11, 3–38. See also

Averages calculationaverages processing 3–37cumulation types 3–38

Table settingsrelating to employee subgroups2–

8Table T510C 3–39

adjust average bases to pay scale3–39

Table T510J 2–10, 3–2, 3–28country-specific view of 3–13having different payroll modifier

2–13Table T510S 7–9, 7–10

attaching time wage type rules7–11

MODIF W 7–4

rule TO00 4–18rule TW04 4–10subschema TC00 8–6time wage type selection rules7–

13Table T511A 3–33

averages calculation rules 3–37processing calculation rules from

3–10Table T511B

cumulation types 3–38Table T511C

adjustment rules for averagesbases 3–38

Table T511K 4–9rule TW04 4–9, 4–10subschema TW20 4–12

Table T512Wrule TC10 5–7rule TC11 5–8rule TC20 5–4rule TC21 5–5rule TC22 5–6

Table T51D1 2–10having different payroll modifier

2–13Table T554C 2–10

having different absence valuationgroup 2–13

MODIF A 7–4Table T555E 7–16Table T555Y 1–2

assigning hours to time pairs in7–5

MODIF T 7–4processing types 7–7rule TW32 4–8schema TM04 7–3

Table T555ZMODIF T 7–4subschema TC00 8–6, 8–7time pairs, TC00 8–7

Table T559Adifferent workweeks 4–5

Table TIP 4–9rule TO00 4–18rule TO02 4–16rule TW02 4–13rule TW04 4–9, 4–10rule TW06 4–8, 4–9rule TW32 4–8rule TW35 4–11

Table ZH 8–8Table ZL 7–16, 8–8, 8–9

rule TC10 5–7, 5–8rule TC11 5–8



rule TC20 5–4rule TC21 5–5rule TC22 5–6schema UT00 8–5subschema UTR0 8–13

Table ZML 7–10, 7–15Technical wage types3–11, 3–19, 3–

23, 3–28choosing to valuate 3–21wage type valuation 3–3

TES See Daily balance table TESTime balances 7–9Time daily balances 4–2Time data 4–2Time Evaluation program 4–1

final major step 7–17RPTIME00 4–2, 7–1, 8–1steps 1-8 7–1

Time Managementderived wage types 3–29

Time pairs1–2, 4–2, 4–6, 6–1, 6–2,7–7, 7–8, 7–9, 7–10, 7–13, 7–15,8–6, 8–7assigning processing type 7–7creating splits 4–6formed in RPTIME00 8–6generating time wage types7–10,

8–6in table T555Y 7–5, 7–8overtime, subschema TW20 4–12pair type 1 7–8pair type 2 7–8pair type 3 7–8partial 4–9planned 8–7processing type and time type

assigned to 8–6rule TO00 4–18rule TO02 4–16, 4–17rule TW02 4–13rule TW04 4–9, 4–12, 4–14rule TW06 4–8rule TW35 4–11table T555Z 8–7

Time Pairs 4–10Time quota 02 5–4

rule TC10 5–7rule TC11 5–8rule TC12 5–9rule TC20 5–4rule TC21 5–5rule TC22 5–6

Time quotasrule TC00 8–6

Time recording 7–6Time specifications 5–4, 5–7, 5–9

Time type 0040 4–4rule TO00 4–18rule TO02 4–16rule TW04 4–9, 4–10

Time type 0041rule TC10 5–7rule TC12 5–9rule TC20 5–4rule TC21 5–5rule TC22 5–6



Time type 0410 7–16rule TC10 5–7rule TC11 5–8rule TC12 5–9rule TC20 5–4rule TC21 5–5rule TC22 5–6rule TR91 7–16

Time type 0900 4–4, 4–15rule TO01 4–15

Time type 0903 4–4, 4–5rule TW04 4–9rule TW06 4–9rule TW33 4–10rule TW35 4–12

Time type 0904 4–4rule TO02 4–17rule TW06 4–8, 4–9rule TW33 4–10

Time type 0905 4–4rule TW00 4–17

Time type 0906 4–4rule TW06 4–8rule TW31 4–7

Time types 7–9, 8–6assigned to time pairs 8–6defining 7–6hours stored in 4–4in Time Evaluation program 7–1list of 4–4rule TO02 4–16, 4–17storing daily balances 4–2with processing type S 4–16

Time wage types3–12, 3–26, 3–31,3–32, 3–37, 4–1, 7–1, 7–7, 7–10,7–15, 8–1, 8–2, 8–6assigning valuation bases 3–26calculating Amount to be paid 7–1choosing processing class 3–33creating customer 7–12displaying valuation 3–28evaluated by averages processing

3–31function GWT 7–15generated by time pairs 8–6generating from time pairs7–9, 7–

10generation rules 7–12processing of in UT00 8–3rule TC10 5–8rule TC11 5–8rule TC20 5–4rule TC21 5–5rule TC22 5–6schema TM04 7–3selection rule table, T510S 7–13subschema XT01 8–8table T555Y 7–9valuating average amounts 3–29valuation bases 3–2viewing generation rules 7–13

Time Wage Types 4–18TIMTP 8–6Tm WT Sel. Rule Group 7–13TMON 7–4, 7–8, 7–11Transaction PE01

accessing schemas 2–5, 2–16Transaction PE02

accessing rules 2–5, 2–16TSDIVP 3–23TW30 7–10TYPES 7–3, 7–5

U

Uncon.exit 7–14UPDTQA0 5–6UPDTQA02 5–4, 5–5, 5–6, 5–7, 5–8Upgrading schemas and rules 2–15UTR1 8–14UTRO 8–13

V

V0 8–13Vacation 1–1, 4–3, 5–2, 8–6, 8–7

compensation 4–2, 5–1, 5–2compensation ratios 5–8, 5–9compensation, time types 7–1using averages configuration 3–29

VAKEYALZNR 3–9



VALBS?0 8–10VALBS0 3–9, 3–9VALBS1 3–9VALBS2 3–9Valid processing types 7–13Valuating time wage types

with average amounts 3–29Valuation bases 3–7

assigning 3–26averages processing 3–31configuring time wage types 3–2constants dependant on pay scale

3–18create constant 3–12create person-related 3–19field selections 3–28form by addition 3–21form by division 3–23general processing of time data3–

24including primary wage types3–

30infotype 2010 8–10maintaining basic pay for 3–20

Valuation basis See Valuation basesValuation classes

assigning to work schedules 7–11Valuation rules 2–10Variants See Rule VariantsVARSTDAYTY 4–15VARSTFDYWW 4–7, 4–10, 4–11VARSTFREE 4–15VARSTLDYWW 4–7VARSTPRSNT 4–17VARSTWDY 4–13, 4–18VWTCL 3–5, 3–6, 3–7VWTCL 15 3–10, 3–33VWTCL 17 5–4, 5–7VWTCL 18 3–9

VWTCL 85 8–13

W

Wage typeMM00 3–14, 7–16MM01 8–8MM02 8–8MM10 7–15MM20 7–15MM70 8–6

Wage type fieldaverages processing 3–37

Wage type valuation 3–1configuring in IMG 3–12constants dependant on wage

types 3–13create constant valuation bases3–

12equation 3–2final step, rule X015 8–3, 8–14flow, summary 3–3flowchart 3–4regular rate of pay 8–11rule TC10 5–8rule TC11 5–8rule TC20 5–4rule TC21 5–5rule TC22 5–6rule X010 3–3rule X013 3–3rule X015 3–3rules and technical wage types3–3subschema UT00 8–3using rules 3–2

Wage typesSee also Basic pay wagetype; Derived wage type;Overtime wage type; Technicalwage type; Time wage typecalled by function GEN 2–8

configuring for averagesprocessing 3–3

copying 3–14current 3–28, 3–29giving new value and P. Mod3–14primary 3–29processing class 85 values 8–14valuating for remuneration or

compensation 1–1Weekly overtime analysis 8–3WGTYP 3–9Work schedules, period

assigning valuation classes 7–11Workweek definitions

beginning day 4–13different 4–5, 4–6employees with start times 4–6employees without start times4–

11only one 4–5, 4–12

WPBP 2–6WTy for Percentage 3–39WW 4–6WWTI 4–6

X

X= WWADDWT * 8–13X015 8–13X940 8–8

Z

ZERO= N 3–5ZERO=A 3–4ZL 8–8ZLIT 8–13

Download - SAP HR Understanding Schema

Top Related