Schema

Understanding Overtime Schemas and Rules in Payroll and Time Evaluation
SAP Labs, Inc. R/3 Simplification Group
Fo rR /3 Re se lea 3.0 F
Understanding Overtime Schemas and Rules in Payroll and Time Evaluation Copyright
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 or translated 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 specifically disclaims 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 in this document is subject to change without notice. SAP Labs, Inc. reserves the right to make any such changes without obligation to notify any person of such revision or changes. SAP Labs, Inc. makes no commitment 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 their respective companies.
1998 SAP Labs, Inc.
Understanding Overtime Schemas and Rules in Payroll and Time Evaluation Error! No text of specified style in document.
Contents
Introduction to Overtime ........................................................................................................................................................................................v Overview ...........................................................................................................................................................................................................v Release 3.0F, U.S. Country-Specific.................................................................................................................................................................v Who Should Use This Guide .............................................................................................................................................................................v Some Commonly Asked Questions.................................................................................................................................................................. vi On What is an R/3 Overtime Payment Based? ........................................................................................................................................ vi How is the Hourly Rate Calculated?......................................................................................................................................................... vi How is the Hours Threshold Determined?................................................................................................................................................ vi How Can I Configure Overtime According to the FLSA Regulations?...................................................................................................... vi What If Overtime Is Compensated by Additional Leave or a Combination of Leave and Extra Payments? ........................................... vii What If There Are Different Workweek Definitions?................................................................................................................................ vii How Can I Set Up Different Overtime Rules for the Fifty Unions in My Company? ................................................................................ vii Chapter 1: Generating Overtime in the System ..........................................................................................................................................11 Overview .......................................................................................................................................................................................................11 Automatic Overtime Generation ....................................................................................................................................................................11 Manual Data Entry.........................................................................................................................................................................................11 Chapter 2: Schemas and RulesThe Basics..............................................................................................................................................21 Overview .......................................................................................................................................................................................................21 The Payroll Calculation Program...................................................................................................................................................................21 Schemas .......................................................................................................................................................................................................22 Subschema UT00..................................................................................................................................................................................23 Accessing Schemas and Rules.....................................................................................................................................................................25 Accessing Help When Looking at the Source Text ...............................................................................................................................25 Schemas and Rules Documentation (RPDSYS00).......................................................................................................................................25 Schema Functions.........................................................................................................................................................................................26 Accessing Rules Using Functions PIT and PORT.................................................................................................................................27 Accessing Rules and Relating Employee Subgroups to Certain Table Settings using Function MOD.................................................28 Accessing Different Rule Variants.......................................................................................................................................................211 Grouping Employees with Different Payment Structures Using Rule Variants and Operation OUTWP .....................................................212 Grouping Using Rule Variants.............................................................................................................................................................212 Grouping Using Operation OUTWP ....................................................................................................................................................213 Copying and Amending Delivered Schemas and Rules..............................................................................................................................215 Naming Conventions ...........................................................................................................................................................................215 Tracking Customer Schemas and Rules.....................................................................................................................................................216 Documenting New or Amended Schemas and Rules .................................................................................................................................218 Changing the Schema or Rule Description and Documentation .........................................................................................................218 Chapter 3: Wage Type Valuation ..................................................................................................................................................................31 Overview .......................................................................................................................................................................................................32 Number x Rate = Amount..............................................................................................................................................................................32 Valuation Using Rules ...................................................................................................................................................................................32 Wage Type Valuation Flow: A High-Level Summary ....................................................................................................................................33 Wage Type Valuation Flow ...........................................................................................................................................................................34 Filling the Payroll Input Table with an Hourly Rate Using Rules X010 and X013..................................................................................34 Rule X010..............................................................................................................................................................................................35 Rule X013..............................................................................................................................................................................................36 Rule X015..............................................................................................................................................................................................37
1998 SAP Labs, Inc.
iii
Rule X016..............................................................................................................................................................................................39 Rule X017............................................................................................................................................................................................310 Rule X018............................................................................................................................................................................................310 Configuring Wage Type Valuation in the IMG.............................................................................................................................................312 Create Constant Valuation Bases .......................................................................................................................................................312 Create Person-Related Valuation Bases (linked to Basic pay) ...........................................................................................................319 Assign Valuation Bases.......................................................................................................................................................................326 Valuating Time Wage Types with Average Amounts over a Given Period .................................................................................................329 Primary Wage Types to be Included in Evaluation Bases...................................................................................................................330 Primary (Time) Wage Types to be Evaluated by Averages Processing..............................................................................................331 Chapter 4: Calculating Daily and Weekly Overtime....................................................................................................................................41 Overview .......................................................................................................................................................................................................41 The Time Evaluation Program.......................................................................................................................................................................42 Schema TM04 (Negative Time Processing)..................................................................................................................................................42 The USA Fair Labor Standards Act (FLSA) ..................................................................................................................................................42 Federal Law verses State Law ..............................................................................................................................................................43 Exempt and Nonexempt Employees .....................................................................................................................................................43 Regular Rate of Pay ..............................................................................................................................................................................43 Daily Balance Table TES and Monthly Balance Table SALDO.....................................................................................................................44 Calculating Weekly Overtime (TW30 or TW20) ............................................................................................................................................45 Subschema TW30Weekly Overtime for Different Workweeks ..........................................................................................................46 Employees with Workweeks that Have Start Times..............................................................................................................................46 Employees with Workweeks that Do Not Have Start Times................................................................................................................411 Subschema TW20: Weekly Overtime for One Workweek...................................................................................................................412 Calculating Daily Overtime (Subschema TW15) .........................................................................................................................................414 Rule TO01 ...........................................................................................................................................................................................415 Rule TO02 ...........................................................................................................................................................................................416 Calculating Overtime Based on Consecutive Attendance Days (TW10).....................................................................................................417 Rule TW00 ..........................................................................................................................................................................................417 Rule TO00 ...........................................................................................................................................................................................418 Chapter 5: Compensating Overtime with Remuneration or Vacation ......................................................................................................51 Overview .......................................................................................................................................................................................................51 Choosing a Compensation Type...................................................................................................................................................................52 Configuring Processing Class 17 for Overtime Wage Types ........................................................................................................................52 Data Flow: Rules TC20, TC21, TC22....................................................................................................................................................53 Data Flow: TC10, TC11, TC12..............................................................................................................................................................53 Configuring Overtime Compensation in Rules TC20, TC21, and TC22........................................................................................................53 Rule TC20 .............................................................................................................................................................................................54 Rule TC21 .............................................................................................................................................................................................55 Rule TC22 .............................................................................................................................................................................................56 Configuring Overtime Compensation in Rules TC10, TC11, TC12...............................................................................................................57 Rule TC10 .............................................................................................................................................................................................57 Rule TC11 .............................................................................................................................................................................................58 Rule TC12 .............................................................................................................................................................................................59 Chapter 6: Overtime in Schema TM00 (Positive Time Processing) ..........................................................................................................61 Overview .......................................................................................................................................................................................................61 Schema TM00Positive Time Recording ....................................................................................................................................................61 Subschema TO00 .................................................................................................................................................................................62 Subschema TC20..................................................................................................................................................................................62
iv
1998 SAP Labs, Inc.
Chapter 7: Main Steps in Overtime Processing, Steps 18 .......................................................................................................................71 Overview .......................................................................................................................................................................................................71 Steps 18: The Time Evaluation Program ....................................................................................................................................................71 Schema TM04 .......................................................................................................................................................................................72 Step 1: Function MOD sets Table Modifiers..........................................................................................................................................74 Step 2: Hours Collection........................................................................................................................................................................75 Step 3: Assign Hours to Time Pairs in T555Y .......................................................................................................................................75 Step 4: Calculate Overtime Hours and Flag Overtime Pairs .................................................................................................................79 Step 5: Generate Time Wage Types from Time Pairs.........................................................................................................................710 Step 6: Further Processing of Overtime Wage Types.........................................................................................................................715 Step 7: Check Overtime Compensation Account ................................................................................................................................716 Step 8: Export Results to Payroll Input File PCL2...............................................................................................................................717 Chapter 8: Main Steps in Overtime Processing, Steps 916 .....................................................................................................................81 Overview .......................................................................................................................................................................................................81 Steps 916: The Payroll Calculation Program ..............................................................................................................................................81 Step 9: Schema U000Subschema UODP Imports Data From PCL2 Cluster B2...............................................................................82 Step 10: Rules X010 and X013 Commence Wage Type Valuation ......................................................................................................84 Step 11: Function MOD Sets Table Modifiers .......................................................................................................................................84 Step 12: Import Cluster B2 Data for PDC Employees and Process TC00 ............................................................................................85 Step 13: Weekly Overtime Analysis ......................................................................................................................................................87 Step 14: Process Infotype 2010 Data in X930.......................................................................................................................................89 Step 15: U.S. FLSA Regular Rate of Pay Valuation............................................................................................................................810 Step 16: The Final Step in Wage Type Valuation, Rule X015.............................................................................................................814
1998 SAP Labs, Inc.
Introduction to Overtime Overview
Introduction to Overtime
Contents
Overview ..................................................................................................................................................................................................................v Release 3.0F, U.S. Country-Specific......................................................................................................................................................................v Who Should Use This Guide ..................................................................................................................................................................................v Some Commonly Asked Questions .....................................................................................................................................................................vi What is an R/3 Overtime Payment Based On? ................................................................................................................................................ vi How is the Hourly Rate Calculated?................................................................................................................................................................. vi How is the Hours Threshold Determined? ....................................................................................................................................................... vi How Can I Configure Overtime According to the FLSA Regulations? ............................................................................................................. vi What If Overtime Is Compensated by Additional Leave or a Combination of Leave and Extra Payments? ................................................... vii What If There Are Different Workweek Definitions?........................................................................................................................................ vii How 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 approached this subject from a business perspective, with specific topics that address the most important issues faced by customers. Technical detail is provided where necessary. However, it should be noted that the information supplements, and does not replace, formal SAP HR and Payroll training courses that provide the correct approach to learning HR and Payroll configuration. This documentation also does not attempt to explain the detailed workings of the Payroll Calculation or Time Evaluation programs or how they relate to each other and the master data. SAP master data, Payroll, and Time Evaluation courses are the prerequisites to using 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 and legislation. 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 rules in this document in different ways. Later releases may also contain different configuration solutions to the business requirements discussed in this document. This documentation is a guide to the general workings of the system, not an exact mapping of the areas configurations.
Who Should Use This Guide

This documentation is for consultants and customers who are familiar with HR master data and who want to configure Payroll and Time Management. The majority of customers who implement Payroll will require some overtime configuration, so this documentation uses this common customer requirement to explain the basic workings of the Payroll and Time Management programs.
1998 SAP Labs, Inc.
Introduction to Overtime Some Commonly Asked Questions
Anyone relatively new to Payroll and Time Management configuration will find that one of the hardest concepts 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 used schemas, rules, functions, and operations and will acquire the knowledge to intuitively expand their skills into other Payroll and Time Management areas. Finally, for experienced consultants who need a reliable reference, this documentation should be seen as a checklist to see how schemas and rules are used for particular aspects of overtime configuration. We hope this documentation will bridge the gap between HR master data configuration and the more complex Payroll and Time Management configuration.
Some Commonly Asked Questions

Overtime configuration depends upon a number of factors that relate to actual customer requirements. The following 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 how many hours are worked (such as a bonus), or is it calculated from the average earnings over a period of time? See chapter 3, Wage Type Valuation for the various alternatives to see how these payments can be configured.
How is the Hourly Rate Calculated?

Most overtime calculations involve the use of an hourly rate, which comes from either a percentage of basic pay elements or from an average of basic pay over different periods. R/3 calculates this using wage type valuation. 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 per day, per week, and so on. See chapter 4, Calculating Overtime on a Daily or Weekly Basis for further details.
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 to calculate overtime and comploy with these regulations.
vi
1998 SAP Labs, Inc.
Introduction to Overtime Some Commonly Asked Questions
What If Overtime Is Compensated by Additional Leave or a Combination of Leave and Extra Payments?
Each of these options can be configured into an overtime wage type, so that the wage type automatically behaves in a certain way when additional hours are worked. See chapter 6, Com p ensating Overtime with Remuneration 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 a Monday-to-Sunday workweek, while other workers have their overtime calculated using a Sunday-toSaturday workweek. Chapter 5 contains details on configuring the system to calculate overtime for employees 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 and Operation OUTWP describes how you can configure different calculation rules for different groups of employees.
1998 SAP Labs, Inc.
vii
Generating Overtime in the System Overview
Chapter 1: Generating Overtime in the System

Contents
Overview ..............................................................................................................................................................................................................11 Automatic Overtime Generation ........................................................................................................................................................................11 Manual Data Entry...............................................................................................................................................................................................11
Overview
The system generates overtime details either automatically or manually. Whether you use automatic generation or manual data entry depends upon the customers needs and the systems configuration.
Automatic Overtime Generation

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

To manually record overtime, the overtime hours, or start-and-end times, enter the information in the following 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-configured amounts or percentages dependent on different personnel subarea groupings. This premium is not a wage 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 will depend 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 by additional remuneration, compensation, or both. However, the only wage types that can be valuated 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, Comp ensating Overtime with Remuneration or Vacation.
1998 SAP Labs, Inc.
11
Generating Overtime in the System Manual Data Entry
Infotype 2002 (Attendances) Attendance types can be configured to correspond to time pairs that have processing type M for overtime in T555Y. The user can choose the relevant attendance type, and enter the number of hours attended for overtime.
12
1998 SAP Labs, Inc.
Schemas and RulesThe Basics Overview
Chapter 2: Schemas and RulesThe Basics

Contents
Overview ..............................................................................................................................................................................................................21 The Payroll Calculation Program.......................................................................................................................................................................21 Schemas ..............................................................................................................................................................................................................22 Subschema UT00..........................................................................................................................................................................................23 Accessing Schemas and Rules .........................................................................................................................................................................25 Accessing Help When Looking at the Source Text .......................................................................................................................................25 Schemas................................................................................................................................................................................................25 Rules .....................................................................................................................................................................................................25 Schemas and Rules Documentation (RPDSYS00) ...........................................................................................................................................25 Schema Functions ..............................................................................................................................................................................................26 Accessing Rules Using Functions PIT and PORT ........................................................................................................................................27 SCHEMA xxxx.......................................................................................................................................................................................27 Accessing Rules and Relating Employee Subgroups to Certain Table Settings using Function MOD.........................................................28 Accessing Different Rule Variants...............................................................................................................................................................211 Grouping Employees with Different Payment Structures Using Rule Variants and Operation OUTWP ..................................................212 Grouping Using Rule Variants.....................................................................................................................................................................212 Grouping Using Operation OUTWP ............................................................................................................................................................213 Copying and Amending Delivered Schemas and Rules................................................................................................................................215 Naming Conventions ...................................................................................................................................................................................215 Schemas..............................................................................................................................................................................................216 Rules ...................................................................................................................................................................................................216 Tracking Customer Schemas and Rules ........................................................................................................................................................216 Documenting New or Amended Schemas and Rules....................................................................................................................................218 Changing the Schema or Rule Description and Documentation .................................................................................................................218
Overview
The chapters that follow discuss the different Payroll Calculation rules that affect wage type valuation and overtime 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 or process data.
The Payroll Calculation Program

The Payroll Calculation program evaluates basic employee time data as part of payroll processing and generates time wage types so that payments can be made. To understand how schemas and rules work together in R/3, we must first examine the Payroll Calculation program. The delivered international payroll program is RPCALCX0.
1998 SAP Labs, Inc.
21
Schemas and RulesThe Basics Schemas
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 is to choose a schema. This top-level schema contains many subschemas, each of which is responsible for carrying 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 in this schema and the Text column summarizes the tasks that function is undertaking.
22
1998 SAP Labs, Inc.
One of the most commonly used functions is Copy, which calls subschemas. Line 000090 on this screenshot shows that schema U000 is calling subschema UT00. If you double-click on UT00, the system opens and displays this subschema in detail.
Subschema UT00
The screenshot below shows subschema UT00, which processes general time data for the U.S. and calls rules X010, X013, and X015, which are used in wage type valuation.
1998 SAP Labs, Inc.
23
The function PIT on lines 000100, 000110, and 000370 call rules X010, X013, and X015. If you double-click on any of these entries, the system opens the rule and shows the decisions and calculations that the rule makes. These rules are described in chapter 3, Wage Type Valuation, using screenshots and detailed explanations.
24
1998 SAP Labs, Inc.
Schemas and RulesThe Basics Accessing 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 some examples online, and get comfortable with moving around or drilling down. There are two different ways of 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 the schema 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 functions description and how it uses the schema parameters. to see the
Rules
When displaying or changing a rule, click on the name of the operation (such as MODIF), and click see the operations description and what types of values can be attached to it. to
Schemas and Rules Documentation (RPDSYS00)

For releases 2, 3, and 4, schemas and rules documentation can be found in program RPDSYS00. A replacement for RPDSYS00 is planned in release 4.5A. The documentation discussed on the previous page is taken directly from RPDSYS00, which contains descriptions of all of the major schemas, rules, functions, and operations in the delivered system.
1998 SAP Labs, Inc.
25
Schemas and RulesThe Basics Schema 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 next screen to see the screen on the right. Double-clicking on a line takes you to the documentation for Personnel Calculation Schemas, Personnel Calculation Rules, etc. On this list, notice that RPDSYS00 also contains the documentation 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 k Place 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 the program. 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 you should be aware of, because they play a major role in deciding which particular wage types a rule should process 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.
26
1998 SAP Labs, Inc.
Accessing Rules Using Functions PIT and PORT

The screenshot of subschema UT00 showed the calling of rules X010, X013, and X015, using the Process Input Table (PIT) function. A similar function, the Process Old Results Table (PORT), calls rules to process old results. These functions use a selection procedure to decide which wage types or employee subgroups should be processed by the rule (see the illustration below):
SCHEMA xxxx
FUNCTION PAR 1 PAR 2
GEN to process all wage types. Process Input Table PIT OR OR Process Old Results Table PORT OR Name of rule to be processed. OR Enn to only process the wage types with a relevant value in evaluation class nn. OR 1, 2, 3, etc., will process according to the employee subgrouping for PCR entered here. Pnn to only process the wage types with a relevant value in processing class nn.
PAR 3
NOAB will process without looking for the employee subgrouping for PCR (from T503)
Left blank where the rule is accessed by a specific wage type. (This would be stated on the first screen of the rule).
1998 SAP Labs, Inc.
27
Accessing Rules and Relating Employee Subgroups to Certain Table Settings using Function MOD
In the screenshot of schema UT00, notice that on line 000120, the function MOD calls rule UMOD. Par2 (parameter 2) is marked GEN and behaves in the method set up in the PIT and PORT charts. It calls all wage types for further processing, regardless of their processing or evaluation class. If you double-click on UMOD in schema UT00, the system displays rule UMOD. The rule determines different table modifiers, depending on the Employee Subgroup Grouping for Personnel Calculation Rules (ESG for PCR), which is configured in the master data. Rules can be configured to have different variants, depending on the ESG for PCR or the wage and time type. Maintaining rule variants for specific wage types or time types is quite labor intensive, so this step is something you will not do very often. However, maintaining rule variants according to the ESG for PCR is a major component for how the system fits together. To illustrate how this process works, see the three sample screenshots from rule $MOD that follow. Each of these 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 operation MODIF.
28
1998 SAP Labs, Inc.
1. Line 000010 on $MOD Employee Subgroup Grouping 1 states that for all employees with ESG for PCR value 1: MODIF A = 01 MODIF 2 = 01 MODIF B = 01
1
2. Line 000010 on $MOD Employee Subgroup Grouping 2 states that for all employees with ESG for PCR value 2: MODIF A = 02 MODIF 2 = 02 MODIF B = 02
2
1998 SAP Labs, Inc.
29
3. Line 000010 $MOD Employee Subgroup Grouping 3 states that for all employees with ESG for PCR value 3: MODIF A = 03 MODIF 2 = 03 MODIF B = 03
3
When these screenshots are examined, a certain pattern is apparent. The key to this pattern can be found by 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 absence valuation 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 be related to one or more wage types for constant wage type valuation, where a constant value can be set for 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 net payroll 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
210
1998 SAP Labs, Inc.
Employees that belong to ESG for PCR 2 are linked to: - Absence valuation group 02 in T554C - Payroll modifier 02 in T510J - Payroll modifier 02 in T51D1 Employees that belong to ESG for PCR 3 are linked to: - Absence valuation group 03 in T554C - Payroll modifier 03 in T510J - Payroll modifier 03 in T51D1 The above example only describes operations MODIF A, MODIF 2, and MODIF B. There are actually eleven different ways to use MODIF. For additional information, see Hel p on MODIF. Function MOD is used by various schemas throughout Payroll and Time Evaluation to call the different rules that use operation MODIF. For example, MODIF appears in rules MODT and TMON in Time Evaluation.
Accessing Different Rule Variants

When you first access $MOD, for example, you will see the following screen for ESG for PCR and wage type or time type. To select a variant: 1. Click Overview. 2. A pop-up window displays all variants. 3. Double-click to select the next variant.
3 2
You can use this method to select a variant in the Display or Change modes.
1998 SAP Labs, Inc.
211
Schemas and RulesThe Basics Grouping Employees with Different Payment Structures Using Rule Variants and Operation OUTWP
4. Once you are in a variant, click
and
to scroll between variants.
Grouping Employees with Different Payment Structures Using Rule Variants and Operation OUTWP
In the previous section, we saw how different variants of the rule $MOD could be related to different employees based on their EE subgrouping for PCR. These relations allow us to have up to nine different variants of the same rule (the only ESG allowed for PCR values are 19), and this method of configuring variants can be used with any rule. In general, rule variants only exist in the delivered system for the rules that need to behave differently for hourly and salaried staff (and for some time type variants that are beyond the scope of this documentation). 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 company and each one has a different agreement and a different way of calculating overtime? To handle such situations, first group using rule variants then group using operation OUTWP.
Grouping Using Rule Variants

For example, in our 50-union scenario, we recommend analyzing and configuring your rules in the following manner: 1. Analyze which groups of employees are paid hourly and which are salaried, and the different pay frequencies for each. This portion of your analysis is essential because your hourly paid staff should always be given ESG for PCR value 1 in master data configuration. The reason for this step is that some rules in the delivered system contain a variant for ESG for PCR value 1 that is configured to process an hourly rate, rather than an amount. (These rules are explained in more detail in chapter 3, Wag e Type Valuation). For ESG for PCR values 29, the rule variants are configured to process an amount. These values should be assigned to salaried employees. You can change the rule variants for values 29 so they relate to 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 Salaried staff, weekly paid Salaried staff, semi-monthly paid
ESG for PCR value 1 ESG for PCR value 2 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 each union with a different agreement about how overtime is calculated? What if your staff, who are paid semimonthly, are subdivided into three different groups, based on the unions to which they belong?
212
1998 SAP Labs, Inc.
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 rules that 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 PCR value, 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 operation OUTWP.
Grouping Using Operation OUTWP

To subdivide your hourly paid staff into 46 different types of calculations based on their union, for example, 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 following definitions: MODIF A = 01 MODIF 2 = 01 MODIF B = 01 All hourly employees have absence valuation group in T554C All hourly employees have payroll modifier 01 in T510J 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 payroll modifier in T510J, and a different payroll modifier in T51D1? The next screenshot shows the variant for ESG for PCR value 1 for rule $MOD, but it has now been amended using operation OUTWP.
1998 SAP Labs, Inc.
213
Operation OUTWP is an extremely useful way of getting a rule to make a decision according to the different fields in employee infotype 0001 (Organizational Assignment), infotype 0007 (Planned Work Time), 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 on the Payroll Operations line, and scroll down the list of operations until you see OUTWP. Then double-click on 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 on operation 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 Personnel Administration and Payroll Accounting Personnel Administration Organizational Assignment Define International Terms of Employment. $MOD is making a decision using the Contract field in infotype 0001 in the following fashion: Line 000020 000030 000040 000050 000060 VarKey Operation Descriptions ** 01 02 03 04 If the employee does not have an entry in the Contract field, pass on without further processing. If the employee has 01 in the Contract field, apply the settings MODIF A = 01, MODIF 2 = 01, and MODIF B = 01. If the employee has 02 in the Contract field, apply the settings MODIF A = 02, MODIF 2 = 02, and MODIF B = 02. If the employee has 03 in the Contract field, apply the settings MODIF A = 03, MODIF 2 = 03, and MODIF B = 03. If the employee has 04 in the Contract field, apply the settings MODIF A = 04, MODIF 2 = 04, and MODIF B = 04.
Lines 000070 and 000080 continue with the same pattern.
214
1998 SAP Labs, Inc.
Schemas and RulesThe Basics Copying and Amending Delivered Schemas and Rules
Once you configure the variant for ESG for PCR value 1 for rule $MOD (for hourly employees), go to the variant for ESG for PCR value 2 (for weekly paid salaried staff), and variant ESG for PCR value 3 (for semimonthly paid staff) and add the decision configuration described above. Therefore, one way to configure the rules to behave differently based on the various unions that employees belong to it is to configure the Contract field in infotype 0001 to represent a union and then configure rules to make a decision on the Contract field, as described above. The Contract field is alphanumeric, which gives you up to 99 different numeric 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 make decisions 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 infotype fields.
Copying and Amending Delivered Schemas and Rules

Whenever you configure schemas and rules, first try to find the schema or rule that closely fits your requirements, then copy and rename it. Your new configuration should be written to your new renamed schema or rule. Never configure your customer requirements into a delivered schema or rule without first copying and renaming it as described above! We stress this cautionary statement for the following reasons: If you do not copy and rename the schema or rule, you will be unable to compare your customer configuration against the delivered configuration if you get errors. When upgrading your system, all delivered schemas and rules will be overwritten by their namesakes in the new version. However, your renamed customer schemas and rules will not be affected.
Naming Conventions
To make your new schemas and rules identifiable and to protect them from being overwritten by future system upgrades always make the first character in your renamed schema or rule a special character (for example, do not use numbers or letters). We recommend the following naming conventions:
1998 SAP Labs, Inc.
215
Schemas and RulesThe Basics Tracking Customer Schemas and Rules
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 for schemas or PE02 for rules. 2. In the initial screen, if a schema or rule appears, delete the name. 3. Click possible entries.
2 3
216
1998 SAP Labs, Inc.
Schemas and RulesThe Basics Tracking Customer Schemas and Rules
4. Enter, for example, $* for a list of all rules that have been copied and renamed, or &* to see all rules 5 created from scratch. 5. Click Execute. 6. In Program class, to further restrict the options for Payroll or Time Management rules, enter C for Payroll or T for Time Management. 7. Click possible entries.
6 7
8. In the pop-up window, doubleclick on 3.

9.
Click Enter.
1998 SAP Labs, Inc.
217
Schemas and RulesThe Basics Documenting New or Amended Schemas and Rules
Documenting New or Amended Schemas and Rules

In addition to renaming your customer-configured schemas and rules, you should also document their new or changed functionality. To do this, change both the description and documentation for the schema or rule.
Changing the Schema or Rule Description and Documentation

Every schema and rule has a description attached to its name on the initial screen. For example, rule UMOD is described as Modifiers for Payroll Accounting. If you copy and change UMOD to $MOD, also change its description to Modifiers for Payroll Accounting: Copy of UMOD. This way, anyone tracking your 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 your customer configuration is transparent to someone who will be changing the original customer requirements. To change your schema or rule description: 1. Enter Transaction PE01 for schemas and PE02 for rules. 2. Enter the name of your customer schema or rule (such as $MOD). 3. Select Documentation. 4. Click Change. 5. If you have copied an existing schema or rule, you will then see its documentation. 6. Select the heading in the documentation (for example, Modifiers for Payroll Accounting, if you copied and renamed UMOD). 7. Click Edit. You would then see the screen similar to the one on the right. 8. Double-click on <== output. 9. Click Enter to see the following screen. The line marked H is the heading.
8 9 2
3 4
218
1998 SAP Labs, Inc.
Schemas and RulesThe Basics Documenting New or Amended Schemas and Rules
10. In this example, on 000010, enter copy of UMOD. 11. Click Save. 12. To see the results of your change, return to the initial screen, where your amended description will be displayed.
11
10
To change your documentation: 1. Follow steps 15 above, except in step 5, select a line in the documentation, not the heading. 2. Then follow steps 69 above, and you will see this screen. 3. Click on the line where you want to add text (for example 000080) and click Insert Line . (Each click adds a new line.) Then add your new documentation. 4. When you have finished, click Save. To view your new documentation, return to the initial screen and click Documentation and Display.
3 4
When you save your new documentation, the system will concatenate your lines. To prevent the first three characters of your documentation from disappearing, insert three spaces at the beginning of each line. To insert spaces between your lines, to represent new paragraphs, for example, add a / at the beginning of the line. This is basic SAPscript coding.
1998 SAP Labs, Inc.
219
Wage Type Valuation Overview
Chapter 3: Wage Type Valuation

Contents
Overview ..............................................................................................................................................................................................................32 Number x Rate = Amount ...................................................................................................................................................................................32 Valuation Using Rules ........................................................................................................................................................................................32 Wage Type Valuation Flow: A High-Level Summary .......................................................................................................................................33 Wage Type Valuation Flow.................................................................................................................................................................................34 Filling the Payroll Input Table with an Hourly Rate Using Rules X010 and X013 .........................................................................................34 Rule X010......................................................................................................................................................................................................35 Rule X013......................................................................................................................................................................................................36 Variant for ESG for PCR 1.....................................................................................................................................................................36 Variant for ESG for PCR 2.....................................................................................................................................................................36 Rule X015......................................................................................................................................................................................................37 Variant for ESG for PCR 1.....................................................................................................................................................................37 Variant for ESG for PCR 2-9 .................................................................................................................................................................39 Rule X016......................................................................................................................................................................................................39 Rule X017....................................................................................................................................................................................................310 Rule X018....................................................................................................................................................................................................310 Configuring Wage Type Valuation in the IMG ................................................................................................................................................312 Create Constant Valuation Bases ...............................................................................................................................................................312 Constants Dependant on Wage Types................................................................................................................................................313 Constants Dependant on the Pay Scale..............................................................................................................................................318 Create Person-Related Valuation Bases (linked to Basic pay) ...................................................................................................................319 Maintain Basic Pay for Valuation Basis...............................................................................................................................................320 Form Valuation Bases (Addition).........................................................................................................................................................321 Form Valuation Bases (Division) .........................................................................................................................................................323 General Processing of Time Data USA...............................................................................................................................................324 Assign Valuation Bases...............................................................................................................................................................................326 Current Wage Type .............................................................................................................................................................................328 1st Derived Wage Type.......................................................................................................................................................................329 2nd-Derived Wage Type......................................................................................................................................................................329 Valuating Time Wage Types with Average Amounts over a Given Period ..................................................................................................329 Primary Wage Types to be Included in Evaluation Bases...........................................................................................................................330 Primary (Time) Wage Types to be Evaluated by Averages Processing......................................................................................................331 T511A: Averages Calculation Rules....................................................................................................................................................336 T511B: Cumulation Types...................................................................................................................................................................338 T511C: Adjustment Rules for Averages Bases ...................................................................................................................................338 T510C: Adjust Average Bases according to Pay Scale.......................................................................................................................339
1998 SAP Labs, Inc.
31
Wage Type Valuation Overview
Overview
Wage type valuation is used to calculate different payment amounts for either basic working hours or changes in an employees work patterns. For example, if extra hours are worked, or, if an employee goes on 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 or changes in an employees work pattern. A time wage type is generated for the number of hours for a particular type of time (e.g., overtime, holidays, absences, and so on).
Number x Rate = Amount

In the overtime example, wage type valuation takes the Num b er of hours generated for an overtime wage type in Time Management and then looks at the valuation basis configured for that wage type. This valuation 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 pay The time wage type is configured with a valuation basis of nn that corresponds to a technical wage type. The accumulating basic pay amounts are then divided by the total hours worked in rule X013 to get an hourly Rate. For detailed information on rule X013, please see the following page. A constant amount stored in a table The time wage type is configured with a valuation basis of K, where the Rate for the time wage type is a set amount stored in table T510J. A constant amount based on a pay scale group and level The time wage type is configured with a valuation basis of TS, where the Rate for the time wage type is a set pay scale level amount from the pay scale table. A constant amount based on a pay scale group The time wage type is configured with a valuation basis of TG, where the Rate for the time wage type is a set pay scale group amount from the pay scale table. A constant amount according to a pay scale type and area The time wage type is configured with a valuation basis of T, where the Rate for the time wage type is a 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 wage types valuation basis), it multiplies N x R to get the Amo unt to be paid.
Valuation Using Rules

Wage type valuation is processed by the system using several different rules that work together to form a valuation flow. The next section provides a high-level summary explaining how this valuation flow fits together. The following section provides rule-by-rule details of the valuation flow, with charts and screenshots. The final section in this chapter explains how the valuation flow is configured in the IMG.
32
1998 SAP Labs, Inc.
Wage Type Valuation Wage 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 preconfigured 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 for basic pay wage types with processing class 01 values 14, and places these wage type amounts into certain technical wage types, such as /001, /002, /003, and /004, depending on the PC01 value. Rule X013 This rule calculates an hourly rate. It looks for wage types with a processing class 01 value of 5. You will usually find only technical wage types /001, 2, 3, and 4 with this value. The rule takes the amounts from these wage types and calculates an hourly Rate to be used in further processing. The exception to this rule is the X013 variant for ESG for PCR 1, which processes hourly employees. Wage types for these employees already contain the hourly rate, so the types are passed on unprocessed by X013. The flowchart, Filling the Input table with Hourly Rate in this chapter illustrates how rules X010 and X013 work together. Rule X015 This rule first checks if the wage type already has an Amount. If it does, the wage type is passed on without additional processing. If the wage type does not have an Amount, the rule checks if the wage type 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 to get an Amount for the payroll output table. If the user has not entered a Rate, the rule checks if the wage type has a valuation basis. If the wage type does not have a valuation basis, it branches to rule X016, to see if this rule is configured for averages processing. If the wage type has a valuation basis, this basis is applied appropriately to one or more of the following: - Base wage type - First-derived wage type - Second-derived wage type If the valuation basis is nn, the Rate will come from X013. If there is nothing in the Amount and Number 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 class 15: - 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 periods relevancy test, then processes X018 to calculate the average hourly Rate. The wage type is passed back to X016, which multiplies the Number of hours and the Rate to get the Amount.
1998 SAP Labs, Inc.
33
Wage Type Valuation Wage Type Valuation Flow
Wage Type Valuation Flow

This section uses screenshots and charts to describe the wage type valuation flow. To understand how this valuation 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.
Rule X010 (in schema UT00) looks for wage types with processing class 01 values 0, 1, 2, 3, or 4. Wage types with value 0 are not included in the valuation.
Value 1
Value 2
Value 3
Value 4
Creates valuation basis in wage type /001
Creates valuation basis in wage types /001 and /002
2.
Rule X013 looks for wage types with processing class 01 value 5 (usually /001, /002, /003, or /004).
Value 5
Rule X013 performs the following operations on the selected wage type.
1st
2nd
Operation: DIVID ARR This calculation decides the hourly rate.
3rd
4th
Operation: RTE=TSDIVP This operation decides which set of hours should be used for the hourly calculation. RTE is the rate. TSDIVP is what the rate should be. In this case TSDIVP means total working time in working hours.
Operation: ZERO = A
Operation: ADDWT *
then
then
Use DIVID to divide. ARR is to divide the Amount of the wage type by the Rate of the first operation, and store the result in the Rate field of the output table.
This operation ensures that the original amount (before the calculations) is not sent to the output table. ZERO is to initialize (make zero) in the output table. A is the total amount that should be initialized.
then
This operation adds the result of DIVID ARR to the output table.
ADDWT means add to the wage type. * means add to this wage type, (the result could have been added to a different wage type).
34
1998 SAP Labs, Inc.
Rule X010
All of the delivered variants for rule X010 (for ESG for PCR values 19) must be configured as you see in the following screen:
Although the coding looks complex, you can see what the rule is doing by placing the cursor on each operation and clicking Help. The following table explains the lines in the screenshot above: Line 000010 000020 Operation Descriptions This line contains the decision (D) operation VWTCL. This operation makes decisions based on the processing class 01 value assigned to the selected wage type(s). This line states that if the wage type has one of the following values [(*) 4,5,6,7,8, or 9] against processing class 01, the system should produce an error message. Processing would then terminate for this personnel number. This line states that if the wage type has value 0 against processing class 01, its amount should be transferred to the output table without further processing by this rule (ADDWT *). This line means that if the wage type has value 1 against processing class 01, the value of the wage type should be added to the output table (ADDWT *). ELIMI means that the period indicators should be removed from the wage type time unit (Z). This removal is required before values from different wage types can be combined for valuation calculations. ZERO= N means that the number field (N) should be reduced to zero in the output table. ADDWT /001 states that the value of the wage type should also be copied to wage type /001 in the output table. These lines are similar to line 000040, except that the value of the wage type is copied to wage types /002, and wage types / 001 and / 002 in the output table.
000030 000040
000050 and 000060
1998 SAP Labs, Inc.
35
Rule X013
Rule 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 is configured to pass on wage types for hourly employees without further processing. Lines 000010 000020 Operation Descriptions This line contains the decision (D) operation VWTCL, which makes decisions based on the processing class 01 value assigned to the selected wage type(s). This line states that, regardless of the value against processing class 01, the amount should be passed on to the output table without further processing, (ADDWT *).

This variant is for salaried employees, and the delivered variants for ESG for PCR 29 should be configured as in the following screenshot:
36
1998 SAP Labs, Inc.
Lines 000010 000020
Operation Descriptions This line again contains the decision (D) operation VWTCL and makes a decision based on the processing class 01 value assigned to the selected wage type(s). 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 *). This line calculates the hourly Rate. The flowchart in the beginning of this chapter, Filling the Payroll Input Table with an Hourly Rate, summarizes how rules X010 and X013 work together to determine hourly rate calculations.
000030
Rule X015
As we have seen in the previous pages, the result of the X010 and X013 processing is an hourly Rate for a given wage type. However, the hourly Rate calculation in X013 is only one of several different ways to calculate the Rate. Rule X015 examines which evaluation basis have been configured for the wage type being 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 for PCR 29 (salaried employees) behave in almost the same way. The following screenshot will help explain how rule X015 works:
1998 SAP Labs, Inc.
37
Line 000010 000020
Operation Descriptions The rule makes a decision (D) on the amount field of the wage type (AMT?0) by comparing the amount stored in the wage type to zero. The * means if the wage type already has an Amount (*), it does not need any further processing for wage type valuation. It is passed on to the payroll output table without further processing (ADDWT). The = means if the wage type does not have an Amount (for example, if AMT = 0), the rule makes 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).
000030
000040
The = * means the rule makes a decision (D) on the rate field of the wage type RTE?0 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 is something (*)]
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 is something (*)] 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 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 (such as RTE = 0) Wage type does not have a valuation basis (such as VALBS is something other than X)
000070
The = * = * means the rule branches to rule X016 and checks for averages processing if the:
000080
The = * = X means if the: Wage type does not have an Amount (for example, if AMT= 0) Wage type had the Number of hours entered by a user or generated by the system [NUM is something (*)]
38
1998 SAP Labs, Inc.
Line
Operation Descriptions User has not entered a rate in infotype 2010, and the wage type has a valuation basis (such as 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 nnor from a constant amountand multiplies it by the Number of hours to get the Amount.) If the valuation basis 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 000100 000110 This line is the same as line 000080, except that the first-derived wage type is valuated (VALBS1). This line is the same as 000090, except that the second-derived wage type is valuated. The = = means if the wage type does not have an Amount or a number, it should be passed on without further processing.
Variant for ESG for PCR 2-9

This variant, for salaried employees, follows the same process as the variant described above. The difference for this variant occurs in line 000080, where it branches to rule X115 to process wage types that have a valuation basis. Rule X115 makes a decision on alternative payments (VAKEYALZNR), and processing class 18 (VWTCL 18), which is used to process workcenter-related remuneration before processing VALBS0, VALBS1, and VALBS2 as described for the previous variant.
Rule X016
Rule 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.
1998 SAP Labs, Inc.
39
Line 000010 000020
Operation Descriptions The rule makes a decision (D) on the wage type processing class 15 value (VWTCL 15) For all PC15 values other than 1, 2, or A, the wage type is added to the output table without further processing (ADDWT *). For wage types with processing class 15 value 1, MEANV 01 processes the wage type based on calculation rule 01 in table T511A. Calculation rule 01 from T511A in the delivered system then processes rule X017 for the relevancy test and X018 for final processing. Rule X018 takes the cumulated value in the Amount field of the cumulation table for averages calculation (table MV) and divides it by the cumulated value in the Number field of table MV. The result is a Rate that gets re-entered in X016 as the Rate in operation MULTI NRA. MULTI NRA multiplies the Number of hours by the Rate calculated in X018 to get an Amount. ADDNA * cumulates the Number and the Amount (but not the Rate) in the output table for the current wage type. For wage types with processing class value 2, MEANV 02 processes the wage type according to calculation rule 02 in T511A. The processing is the same as line 000030. These lines relate to the frozen averages calculations that are outside of the scope of this document.
000030
000040 000050 000090
Rule X017
Rule X017 contains operation MEANV REL, which checks for relevant periods for averages processing. In the delivered system, this operation is configured to treat all periods as relevant. For an example of an actual relevancy test, please see rule X019.
Rule X018
Rule X018 is ready, as delivered, to process the final averages calculation (see the section on rule X016 above for more information).
310
1998 SAP Labs, Inc.
A wage type is sent to this rule by calculation rules 01 and 02 in T511A.
Line 000010
Operation Descriptions 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 the technical wage types specified in the relevant cumulation rule in T511A. NUM?0.00 compares the hours of the previous operation to zero. 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 the next operation. DIVID ANR takes the Amount accumulated in MV and divides it by the Number of hours accumulated in MV to get the Rate used in operation MULTI NRA in rule X016 (as described above).
000020
000030
If there are no hours in the number field of MV (= 0,00), there is no averages calculation.
1998 SAP Labs, Inc.
311
Wage Type Valuation Configuring Wage Type Valuation in the IMG
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, the options are: Create Constant Valuation Bases Create person-related valuation bases Assign valuation bases
The following sections will explain each of these options and describe the subsequent screens.
Create Constant Valuation Bases

Constant valuation enables you to configure time wage types that, if certain qualifying times are worked, have a fixed value. There are two ways these wage types can be configured, through: Constants dependent on wage types (U.S.) Constants dependent on wage types (Canada) Constants dependent on the pay scale
312
1998 SAP Labs, Inc.
Constants Dependant on Wage Types

This option under Create Constant Valuation Bases on the previous screen allows you to configure fixed payments 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 your cursor on the line Constants de pendant on wage types and click Execute. Three additional options appear: Modifier for constant evaluation General processing of tim e data USA Determine constant valuation per wage type
1 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 Determine constant valuation per wage type, and click Choose. 2. Specify the Country grouping (such as 10 for the U.S.) by using possible entries or entering the proper number. 3. Click Continue. You are taken to a country-specific view of T510J (constant valuations).
3 2
1998 SAP Labs, Inc.
313
4. Earlier in your configuration, by choosing Environment for Maintaining Wage Types, you would have analyzed and configured the different time related fixed payment wage types needed in your company. 5. New wage types created for this payment type can be copied from the delivered wage type MM00 (overtime base). Any wage type copied from MM00 should now appear in this view of T510J. Now analyze two additional items. If you created a wage type for working on Saturday, will different staff groups receive different amounts? (For example, your hourly employees receive $40, and your salaried employees receive $50 for working on Saturday). If so, create copies of this wage type. 6. To create copies, select the wage type and click Copy. 7. Do not change the name, but give each copy: The correct amount under Value A new P. Mod number (the next section has more information on P. Mods)
6 5
314
1998 SAP Labs, Inc.
Modifier for Constant Evaluation
This option is listed under Constants dependant on wage types. 1. Place your cursor on Modifier for constant evaluation, and click Choose. 2. This option takes you to rule UMOD, explained in detail in chapter 2, the section Accessing Rules, and Relating Employee Subgroups to Certain Table Settings using Function MOD. Chapter 2 shows that UMOD contains operation MODIF 2 that relates to the payroll modifier P. Mod you created in T510J. MODIF 2 = can relate up to 99 different P. Mod numbers in T510J. You can create up to 99 different amounts for your Saturday working wage type in T510J, and with MODIF 2, assign them to different groups of employees. 3. To copy UMOD, click Copy. 4. In To rule, rename it /MOD. 5. Click Continue.
3 1
4 5
1998 SAP Labs, Inc.
315
6. Create variants of this rule for each of your employee subgroupings for PCR, based on the Grouping Employees with Different Payment Structures guidelines in chapter 2. If necessary, using these guidelines, configure operation OUTWP to make additional decisions on your employee groupings. 7. Amend operation MODIF2=nn, for each employee grouping, so that nn corresponds to the appropriate P. Mod number and value in T510J.
General Processing of Time Data USA 6
This option also appears under the line Constants depen dant on wage types. 1. Place your cursor on General processing of time data USA and click choose. 1
316
1998 SAP Labs, Inc.
2. This action takes you to schema UT00 (see chapter 2 for details). This subschema calls rule UMOD with function MOD.
3. Choose Edit Replace to replace the entry UMOD with your renamed /MOD. 4. In Search, enter UMOD. 5. In Replace using, enter /013. 6. Click Continue.
6
4 5
1998 SAP Labs, Inc.
317
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 pay scale groups, or groups and levels for fixed payments. 1. Click Execute next to Constants dependent on the pay scale.
318
1998 SAP Labs, Inc.
2. Enter the Country grouping. 3. Enter the Pay scale type. 4. Enter the Pay scale area. These items should have already been configured. (To configure these items, choose Personnel Administration Payroll Data Basic Pay.) 5. Click Enter. 6. Create entries for the pay scale groups or the levels you would like valuated.
5 2 3 4
Create Person-Related Valuation Bases (linked to Basic pay)

The first Create person-related valuation bases line represents one of three options when configuring wage type valuation in the IMG. This option enables you to choose one or more basic pay wage types, and assign their amount to a technical wage type (for example, /001), which is then used to calculate an hourly rate for overtime or other calculations. 1. Click Execute next to the first Create person-related valuation bases line.
1998 SAP Labs, Inc.
319
2. This action takes you to a screen with a list of four options.
Maintain Basic Pay for Valuation Basis

1. In the above screen, place your cursor on Maintain basic pay for valuation bases, and click Choose. 2. Select the Country grouping and click Continue. A screen appears with the wage types configured for basic pay infotype 0008. 3. Select a wage type. 4. Click Details. You will then see the processing class 01 value for the wage type. Processing class 01 determines the assignment of this wage type to a valuation base.
4 3
320
1998 SAP Labs, Inc.
5. Click on possible entries to see the available valuation bases.
6. Choose the technical wage type ( /001, /002, etc.) that your wage type will valuate. 7. Click Enter.
6
If you need to select values other than 13, 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 and the other for addition. The addition option takes you to rule X010 (see Wage Type Valuation Flow earlier this chapter for a full explanation of how this works). Rule X010 processes the /00 1 and /00 2 technical wage types selected in the previous step with processing class 01.
1998 SAP Labs, Inc.
321
1. Place your cursor on Form valuation bases (addition), and click Choose.
1
2. To copy rule X010, click Copy. 3. In To rule, rename it /010. 4. Click Continue. 5. If necessary, amend the rule and its links to the processing class 01 values.
3 4 2
6. If you are working in your 6 Recording client, you will see the screen to the right.
322
1998 SAP Labs, Inc.
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 detailed description of rules X010 and X013). You will see from these descriptions that rule X013 has different variants for hourly employees (variant ESG for PCR 1) and salaried employees (variant ESG for PCR 29). Rule X013 calculates hourly rates, and because hourly staff already have hourly rates, the variant for hourly staff is configured to pass data on without further processing (ADDWT *). Your configuration in this view relates only to salaried employees. Operation RTE=TSDIVP states that the amount in technical wage type /0 01 should be divided by the total working time in working hours to get an hourly rate. The total working time (TSDIVP) is taken from the field Working Hours per Payroll Period in infotype 0008. To find out the other ways that operation RTE calculates the hourly rate, please see the operation Help. Complete the following steps: 1. Place your cursor on Form valuation bases (division) and click Choose. 2. Select the Country grouping and click Continue.
3. To copy rule X013, click Copy. 4. In To rule, enter /013. 5. Click Continue.
3
4 5
1998 SAP Labs, Inc.
323
You will see the screen to the right.
6. Create variants of this rule for each of your employee sub-groupings for PCR 29. 7. If RTE=TSDIVP is the correct hourly calculation for each EESG for PCR 29, no further action is necessary. 8. If different calculations are needed for different EESGs for PCR, change RTE= as appropriate for each rule variant.
General Processing of Time Data USA

This line is the third option under Create person-related valuation bases. This choice takes you to subschema UT00. 1. Place your cursor on General processing of time data USA and click Choose.
324
1998 SAP Labs, Inc.
2 2. This action takes you to subschema UT00 (see chapter 2 for details).
3. This subschema calls rule X013 with function PIT.
4. Choose Edit Replace to replace the entry X013 with your renamed / 013. 5. In Search, enter X013. 6. In Replace using, enter /013. 7. Click Continue.
7
5 6
1998 SAP Labs, Inc.
325
9. / 013 has replaced X013.
Assign Valuation Bases

The line Assign valuation bases is the last option when configuring wage type valuation in the IMG. By this point, you have successfully configured your different valuation bases. You must now assign those valuation 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 Assign valuation bases. 2. Select the Country grouping, and click Continue.
326
1998 SAP Labs, Inc.
3. Select a wage type. 4. Click Details.

4
The Change View Valuation Bases: Details window appears. The configuration for the fields on this screen is described below.
1998 SAP Labs, Inc.
327
Current Wage Type The Current wage type box shows the valuation for the currently selected time wage type, displayed at the top 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 are available: - nn A numeric entry relates to the secondary wage type from which this wage type takes its value. For example, 01 is technical wage type / 001, and 02 is technical wage type /0 02. If an entry appears, the current wage type will multiply the Number of hours and the Rate calculated in rule X013 (the result of operation DIVID ARR) to get the Amount. - K This option signifies that the wage type will take its valuation from the appropriate line in T510J, as described in the entries under the Constants Dependant on Wage Types line earlier this section. - TS This valuation basis means that the wage type takes its valuation from the appropriate line in Constants Dependant on the Pay Scale and takes into account the pay scale group and level. - TG This option means that the wage type takes its valuation from the appropriate line in Constants Dependant on the Pay Scale and takes into account the pay scale group, but not the level. - T This option signifies that the wage type takes its valuation from the appropriate line in Constants Dependant on the Pay Scale and takes into account the pay type, area, and wage type, but not the pay scale group or level. StatemnWT This is the wage type where the result of the chosen valuation is placed in the payroll output table. A blank space in this field means that the valuation is placed in the displayed wage type in the payroll output table. %rate Once the current wage type has been valuated, a percentage can be applied to the valuated amount. If the valuated amount should be paid in full, enter 100; if the current wage type should only pay half of the 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 the valuated amounts by the appropriate percentages for the same total result. This second option gives you more flexibility to record payment splits and valuate derived wage types.
328
1998 SAP Labs, Inc.
Wage Type Valuation Valuating Time Wage Types with Average Amounts over a Given Period
1st Derived Wage Type

In the 1st derived wage type box, the displayed wage type can have up to two derived wage types that are valuated by the hours (Number) of the current wage type. If the current wage type already has an Amount or a Rate, nothing will be triggered in its derived wage types or its statement wage type. Usually, wage types that have derived wage types have hours generated in Time Management or hours entered in infotype 2010. These hours (Number) are applied to the valuation basis (Rate) of their derived wage type to get an Amount. A derived wage type can be configured differently from the current wage type, with different processing and evaluation classes so that different combinations of tax settings, valuation settings, etc., can be configured 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 from primary wage types into secondary wage types, and average the totals over different periods of time. The resulting average rates are used to valuate time wage types. Averages are used to calculate vacation, short and long term disability entitlements, etc., where the entitlement depends on the earnings or percentage of days worked in the previous payroll period or several previous payroll periods. Overtime payments may also be calculated in this way. The 3.0F delivered system for the U.S. and Canada does not contain complete averages configuration. The screenshots and descriptions explain how to configure basic averages processing from scratch. In general, to configure basic averages processing you need primary wage types to be included in evaluation bases and evaluated by averages processing (see the steps below).
1998 SAP Labs, Inc.
329
Primary Wage Types to be Included in Evaluation Bases

1. In the IMG, choose Time Wage Type Valuation Averages Form bases for calculating averages. 2. Click Execute next to Form bases for calculating averages. 3. Select the Country code, and click Continue.
2 1
4. Select each primary wage type whose Rate, Number, or Amount should be used to calculate average Rates. 5. Click Details.
330
1998 SAP Labs, Inc.
5. In the next screen, select whether its Rate, Number of hours, and Amount should be cumulated in / 201 Average bases and the percentage for each. / 201 is the only /2nn wage type available for selection in the delivered U.S. version.
6
Primary (Time) Wage Types to be Evaluated by Averages Processing

1. Choose Payroll: USA Basic Settings Environment for Maintaining Wage Types Logical Views Check assignment to wage type group. Before time wage types can be evaluated by averages processing, make sure that they are assigned to the delivered wage type group 0510, wage type generation. 2. Click Execute next to Check assignment to wage type group.
2 1
1998 SAP Labs, Inc.
331
3. Choose Time Wage Type Valuation Averages Assign valuation of averages to primary wage type. 4. Click Execute next to Assign valuation of averages to primary wage type. 5. Select the Country grouping, and click Continue.
6. On this screen, choose the time wage types that should have their hourly Rate calculated as an average over a period of time. 7. Click Details.
332
1998 SAP Labs, Inc.
8. Choose the appropriate processing class 15 value for your time wage type.
9. The three delivered values are 1, 2, and A. These PC15 values are processed by rule X016, which makes the following decision (VWTCL 15): For PC15 value 1, rule X016 goes to T511A and processes calculation rule 01 (MEANV 01). For PC15 value 2, rule X016 goes to T511A and processes calculation rule 02 (MEANV 02). PC15 value A relates to frozen averages that are outside of the scope of this document.
9
1998 SAP Labs, Inc.
333
10. Choose Time Wage Type Valuation Averages Bases for valuation of averages. 11. Click Execute next to Bases for valuation of averages.
11
10
12. This IMG screen should show the averages calculations rules that are set up in T511A. However, the U.S. delivered version (3.0F) does not yet have a standard entry in this view.
334
1998 SAP Labs, Inc.
13. To see what is set up for country version 01 (Germany), in the IMG, choose Time Wage Type Valuation Averages Create cumulation rules for bases for calculating averages. 14. Click Execute next to Create cumulation rules for bases for calculating averages.
14 13
15. Place your cursor on HR: Averages, Start on second level. 16. Click Choose.
15
16
17. For Country grouping, select 01. 18. Click Continue.
17 18
1998 SAP Labs, Inc.
335
19. For Country grouping, reselect 01. 20. Click Enter.

19
20
21. Click Average type. You will then see the screen to the right, which is the starting point to describe averages processing.
21
T511A: Averages Calculation Rules
336
1998 SAP Labs, Inc.
The screen above shows the different average calculation rules configured for country 01 in T511A. The following 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 operation MEANV 01 in rule X016. Therefore, time wage types that should be valuated by this calculation rule are given processing class 15 value 1. Rel. test Cal. rule 01 goes to rule X017 to process a relevancy test, which determines which previous payroll periods are relevant for averages calculations. Rule X017 is configured to make all previous periods relevant. 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 to accumulate the Numbers, Rates, or Amounts used in averages calculations. However, if an employee is absent for part or all of a previous period, their earnings or hours of work may not be relevant to the averages calculation. Cumulation This column refers to a cumulation type called by the calculation rule. Calc. rule 01 calls cumulation type 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 to rule X018 for final processing. Rule X018 calculates the average Rate, using the values accumulated in the table MV (cumulation table for averages processing). These values come from the /2nn wage types selected by the cumulation type. Max.No.Per This column stands for the maximum number of previous payroll periods that can be used to calculate the average Number, Rate, or Amount. Calc. rule 01 is configured to return to a maximum of three payroll periods. No.rel. per This column stands for the minimum number of previous payroll periods that can be used to calculate the average Number, Rate, or Amount. Calc. rule 01 is configured to return to a minimum of three payroll periods. Wage type A wage type entered in this column can be configured with a predefined average value, which can be chosen by users when they enter data in infotype 2010. This value is useful for employees who, for example, are new and have not worked long enough for average processing to calculate an average value.
1998 SAP Labs, Inc.
337
T511B: Cumulation Types

Select Calc. Rule 01 and click Cumulation Type for Average, which is found near the menu bar to see the following screen:
This screen shows Cumulation type 01, which is called by Calc. Rule 01. In this example, Cum ulation Typ e 01 is accumulating values collected in wage types /2 04 and /2 07. For /2 04, the wage type Amount accumulates 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 Rate calculations in X018. The Adjustment field determines how retroactive pay increases are handled by averages processing. This entry relates to an adjustment rule. Cumulation Typ e 01 calls Adjustment rule 01 for /20 4 and /20 7. Notice that each /2nn wage type is related to a different adjustment rule. To see the adjustment rules screen, click Modification 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 combinations of Numbers, Rates, and Amounts from / 204 and /2 07 to be included in averages calculations. If a pay increase is activated in the system, and that increase is effective from the current pay period, the average calculations 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 your averages processing to consider the increased amounts, not the amounts that have accumulated so far for those periods.
338
1998 SAP Labs, Inc.
Different adjustment rules can be configured and attached to /2 nn wage types in cumulation types, so that individual /2nn wage types can be adjusted in different ways to consider retroactive pay increases. The fields in the Adjustm ent Rules for Bases for Calculating Average Values screen have the following functionality: 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 this adjustment 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 current pay 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 of increase 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 the previous 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 the following options: ID: Vbasis If you chose option 4 above, enter the / 0nn wage type you want your retroactive increase to your /2nn Number, 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 wage type to be selected as a once-only payment in infotype 2010 to apply a percentage increase. These employee-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 this field, 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 in table T510C. To see how this functionality works, click Features of standard pay increase to see the following screen.
1998 SAP Labs, Inc.
339
The settings will be applied to the Rates or Numbers of the /2 nn wage types that have option 1 chosen in the 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 the employees being processed. The same / 2nn wage type can have its average bases increased by different factors, according to the different percentage increases configured for different groups of employees in T510C. Percent 1 Enter the percentage increase to be applied to the valuation bases for employees who receive a pay increase 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 to receive the same pay. In this case, enter the reduction factor to be applied.
340
1998 SAP Labs, Inc.
Calculating Daily and Weekly Overtime Overview
Chapter 4: Calculating Daily and Weekly Overtime

Contents
Overview ..............................................................................................................................................................................................................41 The Time Evaluation Program ...........................................................................................................................................................................42 Schema TM04 (Negative Time Processing) ......................................................................................................................................................42 The USA Fair Labor Standards Act (FLSA).......................................................................................................................................................42 Federal Law verses State Law ......................................................................................................................................................................43 Exempt and Nonexempt Employees .............................................................................................................................................................43 Exempt Employees................................................................................................................................................................................43 Nonexempt Employees .........................................................................................................................................................................43 Regular Rate of Pay ......................................................................................................................................................................................43 Daily Balance Table TES and Monthly Balance Table SALDO........................................................................................................................44 Calculating Weekly Overtime (TW30 or TW20).................................................................................................................................................45 Subschema TW30Weekly Overtime for Different Workweeks ..................................................................................................................46 Employees with Workweeks that Have Start Times......................................................................................................................................46 Rule TW31.............................................................................................................................................................................................46 Rule TW32.............................................................................................................................................................................................48 Rule TW06.............................................................................................................................................................................................48 Rule TW04.............................................................................................................................................................................................49 Rule TW33...........................................................................................................................................................................................410 Employees with Workweeks that Do Not Have Start Times........................................................................................................................411 Rule TW34...........................................................................................................................................................................................411 Rule TW35...........................................................................................................................................................................................411 Rule TW04...........................................................................................................................................................................................412 Rule TW36...........................................................................................................................................................................................412 Subschema TW20: Weekly Overtime for One Workweek...........................................................................................................................412 Rule TW01...........................................................................................................................................................................................413 Rule TW02...........................................................................................................................................................................................413 Rule TW04...........................................................................................................................................................................................414 Rule TW03...........................................................................................................................................................................................414 Calculating Daily Overtime (Subschema TW15) ............................................................................................................................................414 Rule TO01 ...................................................................................................................................................................................................415 Rule TO02 ...................................................................................................................................................................................................416 Calculating Overtime Based on Consecutive Attendance Days (TW10) .....................................................................................................417 Rule TW00 ..................................................................................................................................................................................................417 Rule TO00 ...................................................................................................................................................................................................418
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 Evaluation program and the schemas and rules specifically designed to generate overtime hours for application to time wage types.
1998 SAP Labs, Inc.
41
Calculating Daily and Weekly Overtime The Time Evaluation Program
The Time Evaluation Program

The delivered Time Evaluation program is RPTIME00, which evaluates basic employee time data, like the Payroll 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 RPTIME00 are 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 the main top-level schemas appropriate for the U.S.: TM00 to evaluate PDC time recording, where start and end times are directly entered into the system or 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 employees evaluated with negative time processing.
Schema TM04 (Negative Time Processing)

Chapter 7 highlights the main processing steps that affect overtime configuration in TM04. The following screenshot and the remainder of this chapter describe in detail step 4, which involves calculating overtime hours and flagging overtime time pairs. TM04-lines 000410000430 Excess hours can be flagged as overtime based on the number of days worked per week, or the number of hours worked per day or per week.
The USA Fair Labor Standards Act (FLSA)

The delivered schema TM04 contains subsche mas 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 section provides an overview of the FLSA legislation.
42
1998 SAP Labs, Inc.
Calculating Daily and Weekly Overtime The USA Fair Labor Standards Act (FLSA)
Federal Law verses State Law

The Federal wage-hour law (FLSA) requires most employers to pay at least the federal minimum wage and an overtime premium to certain employees. Many states also impose their own minimum wage and overtime requirements. If the state law is more beneficial to the employee, then the employer must comply with the state law.
Exempt and Nonexempt Employees

Employees may be exempt (or nonexempt) from FLSA legislation. The category they belong to depends on the 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 usually paid 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 for hours 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 does not stipulate that overtime rates should be paid when someone works more than eight hours a day. However, some state laws, and union contracts require that overtime is paid when these conditions are met. Schema TM04 contains subschemas and rules that deal with these variables.
Regular Rate of Pay

Nonexempt employees must be paid at least one-and-a-half times their regular rate of pay for physically working over 40 hours during a workweek. The definition for physically worked does not include sick pay, vacation pay, jury duty pay, etc., unless it is the employers policy to do so. As an exception, state or local government employees can be given compensatory time off instead of overtime pay.
1998 SAP Labs, Inc.
43
Calculating Daily and Weekly Overtime Daily 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 salary compensates For employees paid on a piecework or commission basis, usually the total earnings for the week divided 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 pay for 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 or services, 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 can be 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 are stored in time types, and the rules described in this chapter use the following utility time types to temporarily store hours or times: 0903 0904 0905 0906 0900 0040 Hours (that can count towards overtime) stored for this week Hours (that can count towards overtime) stored for next week Sequence of attendance days Start time of the workweek Daily overtime after X hours (threshold) Overtime hours
44
1998 SAP Labs, Inc.
Calculating Daily and Weekly Overtime Calculating 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 the time 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 monthly balance 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, ADDDB0903 updates the daily balance of time type 0903). In the above example, if the new daily balance overrides the previous entry in TES, the operation will have 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 time processing, 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 changes to the delivered rules. (For example, if your employees are paid overtime after working nine 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 they are configured for ESG for PCR*. If you have less than nine sets of overtime regulations in your company, you may use the same rule, with different variants for ESG for PCR (linked to employee subgroup in master data), to process various sets of employees in different ways.
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, with different start days or start times. In this case, different workweeks can be defined in T559A and defaulted to different groups of employees 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 TW20 in the Copy function line in TM04.
1998 SAP Labs, Inc.
45
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 Wee k.
Subschema TW30Weekly Overtime for Different Workweeks

The screenshot below shows subschema TW30. TW30 uses IF and ELSE functions to select different rules for different groups of employees as follows: 1. IF and WW if the employee has a workweek selected in infotype 0007. 2. IF and WWTI if the employees workweek has a start time.
1 2
3. Rules TW31, TW32, and TW33 are 3 processed. 4 4. ELSE if the employee has a 5 workweek selected in infotype 0007, but their workweek does not have a start time. 5. Rules TW34, TW35, and TW36 are processed. The main reason for these two different types of processing is the need to create splits in the time pairs where an employee begins a shift during one workweek and ends it during another. At the beginning of the day, the system automatically splits the time pairs when an employees new workweek begins (for example, at midnight). However, if the new workweek begins during the day (for example, Monday at 2:00 p.m.), additional processing is required to create new time pairs for the hours worked before and after 2:00 p.m. If an employees workweek does not have a start time, the system assumes that the new workweek begins at midnight on the first day.
Employees with Workweeks that Have Start Times

The following sequence of subschemas and rules is called by TW30 to process weekly overtime for employees 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 their workweek has a start time, their hours will be processed by rules TW31, TW32, and TW33.
46
1998 SAP Labs, Inc.
Function ACTIO in TW30 calls rule TW31, as shown below:
Line 000010
Operation Descriptions 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 overrides the previous daily balance (ADDDB0903Z). The monthly balance of the number of hours for the following week (HRS=M0904) is added to the daily balance of hours for the following week, which overrides the previous daily balance (ADDDB0904Z).
000020 000030 000040
A decision (D) is made whether this is the first day of the workweek (VARSTFDYWW). If this is not the first day of the workweek (N), a decision (D) is made whether this is the last day of the workweek (VARSTLDYWW). If this is not the first day of the workweek (N) and not the last day of the workweek (N), 48 hours 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 the current 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 the start and end of workweeks. If this is not the first day of the workweek (N) but the last day of the workweek (Y), 24 hours are 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 will be included in the current week; it temporarily moves the start time of the next week forward by 24 hours. If this is the first day of the workweek (Y), the start time of the workweek recorded in infotype 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 of each new workweek.
000050
000060
1998 SAP Labs, Inc.
47
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 internal table TIP without further processing (COLOP*). If start and end times exist, the data passes to rule TW06 for further processing (GCY TW06).
Rule TW06
Line 000010 000020 000030 000040
Operation Descriptions TW06 first makes a decision on the processing type of the time pair (OUTTPVTYPE). If the processing type is anything other than S (Planned Work Time), the data is transferred back to internal table 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 time pair (OUTTPPTYPE). (S *) If the processing type is S (Planned Work Time) and the pair type is not 0 or 2, the start time of todays shift (HRS=PBEG) is compared to the start time of the workweek (HRS?D0906). Time type 0906 was initialized in rule TW31. (S * *) If the processing type is S (Planned Work Time), todays hours (HRS=PNUM) are added to the daily balance for time type 0904 [hours for the following week (ADDDB0904)], then transferred back to TIP (COLOP). (S * < ) If the start time of todays shift is before the start time of the workweek (S * <), the end
000050
000060
48
1998 SAP Labs, Inc.
Line
Operation Descriptions time of todays shift (HRS=PEND) is compared to the start time of the current workweek (HRS?D0906). (S * < *) If the start time of todays shift is before the start time of the workweek, and the end time of todays shift is before the start of the workweek, the data passes to rule TW04 for further processing (Z GCY TW04). (S * < > ) If the start time of todays shift is before the start time of the workweek and the end time of todays shift is after the start of the workweek, the difference between the start of this workweek and the end of todays shift (HRS=R, the result of the previous decision in line 000060) 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 to TW04 for further processing (GCY TW04). If the pair type is 0 or 2 (non-recorded time or recorde d absence), the data is transferred back to internal table TIP without further processing (COLOP*). However, the comment on the last line states that if recorded absences can be counted toward overtime, they should have the hours added to time type 0903.
000070
000080
000090 and 000100
Rule TW04
TW04 now receives data for time pairs with processing type S (Planned Work), for all hours except nonrecorded time and recorded absence. Separate time pairs have also been created by TW06 for hours that cross the start time of the workweek. Line 000010 Operation Descriptions TW04 now compares the hours in the daily balance table for time type 0903 [Hours in the Current Week (HRS=D0903)] with the weekly overtime threshold stored in table entry OVERT in T511K under country grouping 10 [USA (HRS?COVERT)]. Any excess hours from the previous operation are transferred to internal table TIP as time type 0040 [Overtime Hours (COLOP 0040)]. Their time pair processing type is changed from S (Planned Work) to M [Overtime (FILLPVM)]. If the hours in the current week are less than the threshold stored in T511K (<), todays hours are added to the daily balance in 0903 (HRS+PNUM), and the result is again compared to the weekly overtime threshold stored in T511K (HRS?COVERT). The new hours total after line 000030 is added to the daily balance table for 0903 (overwriting the previous balance) and transferred to internal table TIP (ADDDB0903ZCOLOP).
000020
000030
000040
1998 SAP Labs, Inc.
49
Line 000050
Operation Descriptions If the T511K threshold is exceeded as a result of todays planned hours, a partial time pair is generated for the hours in excess of this threshold in T511K (HRS=COVERTHRS-D0903 GENTPB 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 Types from 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 the rollover 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, these rolling updates are performed differently, according to whether this is the first day of the workweek (D VARSTFDYWW). 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 of hours 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 todays daily balance for the current and the following week. These balances are then 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 for the hours for the following week (D0904), and the total is added to the daily balance for the hours for the current week (ADDDB0903Z). This process takes todays daily balance of hours and states that these are now the current, or new, weeks hours, not the following weeks hours.
410
1998 SAP Labs, Inc.
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 Times

The following sequence of subschemas and rules is called by TW30 to process overtime on a weekly basis for 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 their workweek 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 first day 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 this is 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 type is anything other than S (Planned Work), the data is transferred back to internal table 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 time pair (OUTTPPTYPE). If the pair type is 0 or 2 (Non-Recorded Time or Recorded Absence), the data is transferred back to internal table TIP without further processing (COLOP*). However, the comment on the last line states that if
1998 SAP Labs, Inc.
411
recorded absences can be counted toward overtime, they should have the hours added to time type 0903. If the processing type is S (Planned Work), and the pair types are not 0 or 2 (*), the data is transferred to rule TW04 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 except non-recorded time and recorded absence. Please see the screenshot and description of TW04 on page 10 for details 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 weeks hours (HRS=D0903), and subtracts from it the monthly balance for this weeks hours (HRS-M0903). The new total is todays balance for this weeks hours, which is added 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 to calculate 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 pairs with processing type M Rule TW03 resets the daily balance table TES after processing is complete
412
1998 SAP Labs, Inc.
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 company workweek 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 weeks hours is updated in table TES (ADDDB0903Z) with the monthly balance for this weeks hours (HRS=M0903). If this is the first day of the workweek, the daily balance for this weeks hours is set to 0,00 hours (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 internal table 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 time pair (OUTTPPTYPE). If the pair type is 0 or 2, (Non-Recorded Time or Recorded Absence), the data is transferred back to internal table TIP without further processing (COLOP*). However, the comment on the last line states that if recorded absences can be counted toward overtime, they should have the hours added to time type 0903. If the processing type is S (Planned Work), and the pair type is not 0 or 2 (*), the data is transferred to rule TW04 for further processing (Z GCY TW04).
1998 SAP Labs, Inc.
413
Calculating Daily and Weekly Overtime Calculating Daily Overtime (Subschema TW15)
Rule TW04
TW04 has now been passed data for time pairs with processing class S (Planned Work), for all hours except non-recorded time and recorded absence. Please see the screenshot and description of TW04 on page 9 for details 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 daily balance for this weeks hours (HRS=D0903), and subtracts from it the monthly balance for this weeks hours (HRS-M0903). The new total is todays balance for this weeks hours, which is added to the daily balance 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 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 on a Daily Basis.
Subschema TW15 first calls rule TO01, shown on the following page.
414
1998 SAP Labs, Inc.
Rule TO01
TO01 sets the limits after which overtime becomes payable.
Line 000010 000020
Operation Descriptions A decision (D) is made on the day type being worked by the employee (VARSTDAYTY). 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 TES for planned hours worked (HRS=S HRS>8,00 ADDDB0900). For day type 0 (work, paid), the rule decides whether this is a free day in the employees work schedule (D VARSTFREE). 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 for overtime. Line 000050 adds 8,00 hours to time type 0900 (Daily Overtime After X Hours) in TES for planned hours worked. This line is deactivated by the * in column T.
000030 000040 and 000050
Essentially, in delivered rule TO01, overtime is not automatically paid after eight hours. To make overtime payable after eight hours, delete the * in column T to activate line 000050 and add 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 this limit to planned hours (HRS=8,00 ADDDB0900Z). This setting means that the hours worked over eight hours on a free day qualify for overtime. 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. For day type 2 (off, unpaid), 99,00 hours are added to time type 0900 (HRS=99,00 ADDDB0900Z). This means that overtime will not be paid for the hours worked on an unpaid day off.
000070 000080
1998 SAP Labs, Inc.
415
Rule TO02
After the processing of TO01, subschema TW15 calls rule TO02.
Line 000010 000020 000030 000040
Operation Descriptions A decision (D) is made on the processing type of the time pair being processed (OUTTPVTYPE). (*) Time pairs with processing types other than S (Planned Hours) are passed on without further processing (COLOP*). (S) For time pairs with processing type S, a decision is made (D) on the time pair type (OUTTPPTYPE). (S *) For all time types with processing type S, and with time pair types other than 0 (NonRecorded Time), and 2 (Recorded Absence), the rule compares the daily balance for hours for the following week (HRS=D0904) with the daily balance stored in the daily overtime after-xhours time type (HRS?D0900). (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 (Planned Work) to M [Overtime (FILLPVM)]. (S * <) If the hours in D0904 are less than the hours in D0900, todays hours are added to the hours in D0904 and again compared to the hours in D0900 (D HRS+PNUM HRS?D0900). (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 (ADDDB0904Z COLOP). (S * < >) If the hours in D0904 are now greater than the hours in D0900, a partial time pair is generated for the excess hours (HRS=D0900 HRS-D0904 GENTPB S), and its processing type is changed from S (Planned Work) to M [Overtime (FILLPVM)]. The excess hours are also transferred to internal table TIP as time type 0040 [Overtime Hours (COLOP 0040)]. For time types with processing type S, and with time pair type 0 (Non-Recorded Time), the data passes on without further processing (COLOP*).
000050
000060 000070
000080
000090
416
1998 SAP Labs, Inc.
Calculating Daily and Weekly Overtime Calculating Overtime Based on Consecutive Attendance Days (TW10)
Line 000100
Operation Descriptions For time types with processing type S, and with time pair type 2 (Recorded Absence), the data passes on without further processing (COLOP*). However, the comment on the last line states that if recorded absences can be counted toward overtime, they should have the hours added to 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 attendance days. TW10 is delivered deactivated. 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 Days Worked.
In subschema TW10, function IF calls rule TW00.
Rule TW00
Line 000010 000020
Operation Descriptions A decision (D) is made on whether the employee is present today (VARSTPRSNT). If the employee is absent (N), the IF statement is called false (SCOND=F), and the daily balance in time type 0905 (Sequence of Attendance Days) is set to zero (HRS=0,00 ADDDB0905Z), with no further processing in subschema TW10. If the employee is present (Y), a decision (D) is made on whether this is the start of the
000030
1998 SAP Labs, Inc.
417
Calculating Daily and Weekly Overtime Calculating Overtime Based on Consecutive Attendance Days (TW10)
Line 000040
Operation Descriptions workweek (VARSTWDY 7). The first day of the week is set for day number 7 (Sunday). If the employee is present, and this is not the first day of the workweek, the previous days balance in 0905 is made available, and 1,00 day is added to it (HRS=L0905 HRS+1,00), and the daily balance in 0905 is updated by the new total (ADDDB0905Z). The new balance is then compared to 6,00 [the consecutive days threshold, after which overtime becomes payable (HRS?6,00)]. If the result of the previous line is not greater than 6,00, the IF statement is false (SCOND=F IF) and no further processing is carried out in TW10. 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. If the employee is present, and this is the first day of the workweek (Y Y), then the IF statement is false (SCOND=F IF) and the daily balance for 0905 is set to 1,00, for the first day of the week (HRS=1,00 ADDDB0905Z). No further processing is carried out in TW10.
000050 000060 000070
Rule TO00
If the employee is present, this is not the first day of the workweek, and he or she has exceeded six consecutive 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 time pairs with processing type P (Planned Hours) and other than 0 (Non-Recorded Time) and 2 (Recorded Absence) have their processing type changed to M [Overtime (FILLPVM)] and are ready to be selected by T510S, as described in chapter 7, Step 5: Generate Time Wage Types from Time Pairs. The excess hours are also transferred to internal table TIP as time type 0040 [Overtime Hours (COLOP 0040)].
418
1998 SAP Labs, Inc.
Compensating Overtime with Remuneration or Vacation Overview
Chapter 5: Compensating Overtime with Remuneration or Vacation

Contents
Overview ..............................................................................................................................................................................................................51 Choosing a Compensation Type .......................................................................................................................................................................52 Configuring Processing Class 17 for Overtime Wage Types..........................................................................................................................52 Data Flow: Rules TC20, TC21, TC22............................................................................................................................................................53 Data Flow: TC10, TC11, TC12......................................................................................................................................................................53 Configuring Overtime Compensation in Rules TC20, TC21, and TC22..........................................................................................................53 Rule TC20 .....................................................................................................................................................................................................54 Rule TC21 .....................................................................................................................................................................................................55 Rule TC22 .....................................................................................................................................................................................................56 Configuring Overtime Compensation in Rules TC10, TC11, TC12.................................................................................................................57 Rule TC10 .....................................................................................................................................................................................................57 Rule TC11 .....................................................................................................................................................................................................58 Rule TC12 .....................................................................................................................................................................................................59
Overview
Examine the screenshot of lines 000440000610 in schema TM04 below. This screenshot highlights the one of 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 wage types), as discussed in chapter 7. In this step, remuneration or vacation combinations can be generated for wage types that contain hours generated as overtim e. This chapter also describes rule TC10, which works like TC20 and, if required, can also be processed by schema TM04.
1998 SAP Labs, Inc.
51
Compensating Overtime with Remuneration or Vacation Choosing a Compensation Type
Choosing a Compensation Type

Chapter 1 described the ways that overtime is entered in the system. Overtime hours are entered using infotypes 2005 (Overtime) and 2007 (Attendance Quotas). The user can choose one of the following compensation types: Compensation type left blank Compensation type 1 Compensation type 2 Compensation type 3 The compensation type will depend on the wage type chosen. Compensate with remuneration only. Compensate with remuneration and vacation. Compensate with vacation only.
Configuring Processing Class 17 for Overtime Wage Types

Some companies compensate overtime by providing additional vacation hours, or a combination of vacation and extra payments. Each of these options can be configured into an overtime wage type, so that this wage type automatically behaves as expected when additional hours are worked. This configuration is set up by assigning an appropriate value to wage type processing class 17 (PC17) in T512W. PC17 must be set up for all overtime wage types. To configure PC17, choose IMG Personnel Administration and Payroll Accounting Time Management Time Evaluation Time Accounting Without Clock Times Time Wage Type Selection and Overtime Com pensation Compensate Overtime. Depending on the PC17 value, the wage type is processed by rules TC20, TC21, and TC22, or by rules TC10, TC11, and TC12. The main differences between rules TC2022 and TC1012 are: Rules TC2022 These rules process wage types with PC17 values AE, which allow you to configure additional remuneration and/or additional leave compensation for additional hours worked. The amount of vacation compensation is either on a one-to-one basis, or is determined by the percentages of the derived wage types, based on the chosen PC17 value. Rules TC1012 These rules process wage types with PC17 values 09, and V, which allow you to configure additional remuneration and/or additional leave compensation for additional hours worked. However, the amount of additional leave compensation is determined by fixed factors (1:1.25, 1:1.5, etc), based on the chosen PC17 value.
52
1998 SAP Labs, Inc.
Compensating Overtime with Remuneration or Vacation Configuring Overtime Compensation in Rules TC20, TC21, and TC22
Data Flow: Rules TC20, TC21, TC22

TC20 This rule looks for wage types with PC17 values AF. - 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 an overtime 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 19 and V. - If the wage type has values 15 and V, TC10 will process it. - If the wage type has PC17 values 69, TC10 passes it to TC11 for processing. TC11 This rule looks at wage types with PC17 values 69 and checks if the user has input an overtime compensation type against them in infotypes 2005 or 2007. - If the user has selected compensation type 12, 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 69.
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 wage types valuation basis), it multiplies N x R to get the Amo unt to be paid.
1998 SAP Labs, Inc.
53
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 on to 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 to get 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 number will be the Number of hours to be applied to the overtime Rate in wage type valuation, to get the Amount to be paid. Remuneration will be paid by one, or both, of the derived wage types, and not by the original wage type. For PC17 value C (compensate overtime with vacation, with a factor from the derived wage type percentages): - 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).
54
1998 SAP Labs, Inc.
Rule TC21
Rule TC21 makes a decision (D) on the overtime compensation type (OUTOTCLTYP) selected by the user for 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 specifications are 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 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 valuation to get the Amount to be paid. For wage types where overtime compensation type 2 was selected (compensate overtime with remuneration and vacation): - 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 number will be the Number of hours to be applied to the overtime Rate in wage type valuation to get the Amount to be paid. Remuneration will be paid by one, or both, of the derived wage types, and not by the original wage type. For wage types where overtime compensation type 3 was selected (compensate overtime with vacation 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 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)].
1998 SAP Labs, Inc.
55
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 valuation to 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 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 number will be the Number of hours for application to the overtime Rate in wage type valuation, to get the Amount to be paid. Remuneration will be paid by one, or both, of the derived wage types, and not by the original wage type. For PC17 value F (compensate overtime with vacation, with a factor from the derived wage type percentages): - 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)].
56
1998 SAP Labs, Inc.
Compensating Overtime with Remuneration or Vacation Configuring 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 19, and V, as follows:
Rule TC10
Rule TC10 processes wage types with processing class 17 values 09, and V, as follows: It first makes a decision on WT processing class 17 value (VWTCL 17). For values other than 19 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 number will be the Number of hours to be applied to the overtime Rate in wage type valuation to get the Amount to be paid. Remuneration will be paid by one, or both, of the derived wage types, and not by 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 (ADDDB0410), and time quota 02 [Time Off Entitlement (UPDTQA02)].
1998 SAP Labs, Inc.
57
For values 3, 4, 5: The operations are the same as value 2, except that the vacation compensation ratios are 1,25; 1,50; and 2,00, respectively.
For values 69: 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 valuation to get an Amount to be paid.
Rule TC11
Rule TC11 makes a decision on the overtime compensation type (OUTOTCLTYP) selected by the user for the 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 type valuation to get the Amount to be paid. For wage types where overtime compensation type 2 was selected (compensate overtime with remuneration and vacation): - ADDDB0043 and ADDDB0410 add the number of hours to time types 0043 (OvertimeBasic/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 number will be the Number of hours to be applied to the overtime Rate in wage type valuation to get the Amount to be paid. Remuneration will be paid by one or both of the derived wage types, and not by the original wage type.
58
1998 SAP Labs, Inc.
For wage types where overtime compensation type 3 was selected (compensate overtime with vacation 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 (ADDDB0410), and time quota 02 [Time Off Entitlement (UPDTQA02)]. 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,00 respectively.
1998 SAP Labs, Inc.
59
Overtime in Schema TM00 (Positive Time Processing) Overview
Chapter 6: Overtime in Schema TM00 (Positive Time Processing)

Contents
Overview ..............................................................................................................................................................................................................61 Schema TM00Positive Time Recording.........................................................................................................................................................61 Subschema TO00 .........................................................................................................................................................................................62 Subschema TC20..........................................................................................................................................................................................62
Overview
The purpose of this chapter is to provide a high-level summary of some of the subschemas and rules that can be used to process overtime in schema TM00. A complete summary of all of the available overtime configuration options is outside the scope of this document.
Schema TM00Positive Time Recording

TM00 calls the following rules:
Rule MODT TO20 Purpose Determines table modifiers using MODIF W (T510S), MODIF T (T555Z), and MODIF A (T554C). Determines overtime from employees absence and attendance times on a quo ta basis. Forms overtime pairs for hours in excess of planned work time for the day. Overtime approval must exist, 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. Checks OVPOS field in T550A for general overtime approval for each daily work schedule. If overtime is approved for EEs daily work schedule, it calls TO16. Selects all time pairs outside of planned work time, to calculate overtime. Can either be used with TO15 above, so that only approved overtime is paid, or can be used without TO15, so that overtime is paid without approval. Calls TO11 for final calculation of overtime.
TO15 TO16
TM00 calls subschema TO00 (Rounding Overtime Hours), which is used where approved overtime hours should not be paid in full but should be rounded up or down to a predetermined amount.
1998 SAP Labs, Inc.
61
Overtime in Schema TM00 (Positive Time Processing) Schema TM00Positive Time Recording
Subschema TO00
This subschema calls the following rules: Rules TO30 TO50 TO50 Functions This rule is an alternative to rule TO20. Time pairs that fulfill the conditions for overtime are not converted to overtime at this point, but are assigned processing type U. Time pairs with processing type U are rounded off with the rounding factor ZMRND from T511K, using operation RNDOT, to a set number of hours. This rule is called using function GOT, which checks for overtime approval in the appropriate quota type, (specified in parameter 2). If overtime is approved, it is generated from time pairs with processing type U.
Subschema TC20
This subschema calls the following rule: Rules TC20 Functions Looks at WT processing class 17 values A, B, C, D, E, and F, to decide if an employee should be paid, or given time off for overtime hours. Updates time types, and time off quota, using T556A. Calls rule TC21 for further processing if applicable.
62
1998 SAP Labs, Inc.
Main Steps in Overtime Processing, Steps 18 Overview
Chapter 7: Main Steps in Overtime Processing, Steps 18

Contents
Overview ..............................................................................................................................................................................................................71 Steps 18: The Time Evaluation Program ........................................................................................................................................................71 Schema TM04 ...............................................................................................................................................................................................72 Step 1: Function MOD sets Table Modifiers..................................................................................................................................................74 Step 2: Hours Collection................................................................................................................................................................................75 Step 3: Assign Hours to Time Pairs in T555Y ...............................................................................................................................................75 Assigning Collected Hours to Time Pairs in T555Y...............................................................................................................................78 Step 4: Calculate Overtime Hours and Flag Overtime Pairs .........................................................................................................................79 Step 5: Generate Time Wage Types from Time Pairs ................................................................................................................................710 Time Wage Type Selection Rule Table (T510S).................................................................................................................................713 Function GWT .....................................................................................................................................................................................715 Step 6: Further Processing of Overtime Wage Types.................................................................................................................................715 Step 7: Check Overtime Compensation Account ........................................................................................................................................716 Step 8: Export Results to Payroll Input File PCL2.......................................................................................................................................717
Overview
Chapter 7 provides a high-level, chronological overview, of the main processing steps in the Time Evaluation program RPTIME00, schema TM04, and the Payroll Calculation program RPCALCU0, which affect overtime payments. Chapter 3 described how wage type valuation calculates an hourly Rate, and applies it to a Numb er of hours in time wage types, to get the Am ount to be paid. Chapter 4 showed you how different rules in Time Management schema TM04 configure different overtime calculations, which then formulate the Number of overtime hours for generation in time wage types. Chapters 7 and 8 describe how these processes are brought together in RPTIME00 and RPCALCU0. This chapter focuses on steps 18, which are processed in RPTIME00, and chapter 8 provides details on steps 916, which are processed in RPCALCU0.
Steps 18: 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), which can 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.
1998 SAP Labs, Inc.
71
Main Steps in Overtime Processing, Steps 18 Steps 18: The Time Evaluation Program
The program generally runs overnight, and is started by scheduling a batch job. The results of RPTIME00 are stored in the payroll input files PREL, PCL1, and PCL2 and are ready for pickup during the next run of RPCALCX0. RPTIME00 is an international program, so there are no country-specific versions. The following are the main top-level schemas appropriate to the U.S.: TM00 to evaluate PDC time recording, where start and end times are directly entered into the system or 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 customers top-level schema is a copy of TM04.
This chapter sets out the main daily processing performed by RPTIME00, schema TM04.
Schema TM04
The screenshots on the following pages show how schema TM04 performs eight of the main steps in overtime processing.
72
1998 SAP Labs, Inc.
Schema TM04
1. Function MOD sets table modifers (line 000080).
2. The next step is hours collection (line 000180000250).
3. Function TYPES assigns hours to time pairs in T555Y (line 000320).
4. Overtime hours and flag overtime time pairs are calculated (line 000410000430). 5. Time wage types from time pairs are generated (lines 000440000490). 6. Overtime wage types are further processed (line 000500000520).
1998 SAP Labs, Inc.
73
7. Overtime compensation account is checked (line 000610).
8. Function EXPRT exports results to payroll input files PREL, PCL1, and PCL2 (line 000760).
The above steps are described in detail in the following pages.
Step 1: Function MOD sets Table Modifiers

1. In line 000080, function MOD calls the ESG for PCR variants for rule TMON, which set the modifiers for the following tables: MODIF W Selects the time wage type selection group in T510S. MODIF T Selects the time type 1 determination group in T555Y and T555Z. MODIF A Selects the employee grouping for absence valuation in T554C. You will see the effects of these table modifiers in steps 3 and step 5 later in this chapter.
74
1998 SAP Labs, Inc.
Step 2: Hours Collection

In lines 000180000250 the processing is divided into two stages: First stage: - Function IF parameter POS states that if actual times are being recorded, function P2000 should load the planned hours in the daily work schedule, without the start and end times. - Function ELSE states that if actual times are not being recorded, function P2000 should load the planned hours in the daily work schedule with the start and end times. Second stage: - Function ENDIF ends the IF function. - Functions P2002, P2003, and P2001 load the attendances, the substitutions, and the absences for the day.
Step 3: Assign Hours to Time Pairs in T555Y

1. In this step, line 000320, function TYPES collects the hours from step 2 and assigns them processing types and time pair types in T555Y.
1
1998 SAP Labs, Inc.
75
2. To access the configuration for T555Y (schema TM04), in the IMG, choose: Time Management Time Evaluation Time Accounting Without Clock Times Time Data Processing Assign time types and processing types. 3. Click Execute next to Assign time types and processing types.
3 2
4. This path divides into four additional options. The four choices 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 is assigned to a personnel subarea grouping for time recording, which is used as part of the selection criteria in T555Y.
Define class processing type /time type for absence This option assigns classes for Time Evaluation to absence types. This configuration is outside the scope 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.
76
1998 SAP Labs, Inc.
The delivered processing type and time type class definitions are: 01 02 03 04 05 Leave types or general working hours Periods of illness Time off for overtime Other absences 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 to the appropriate time pairs. Each time pair in T555Y contains a time type, which has been configured and assigned in the views above, and a processing type. The time type accumulates the collected hours into time balances. The processing type for each time type is configurable in T555Y, and the following processing types are used in the delivered table T555Y: Planned working hours Overtime hours Absence hours Attendance hours Processing type S Processing type M Processing type A Processing type P
In the delivered system, step 4 (overtime calculation subschemas), and step 5 (generate time wage types from time pairs in T510S), process the following time pair processing types: Planned working hours Overtime hours Processing type S Processing type M
Remember that steps 4 and step 5 can be configured to process any processing type configured in T555Y.
1998 SAP Labs, Inc.
77
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 the appropriate 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, and 3). In the screenshot above, only employees with pers subarea group 01 will have their hours processed. 2. Then, in column 2 (Group), T555Y restricts the available time pairs based on the time type determination 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 01 will 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 assigned to the absence or attendance type used to enter the hours. If the hours have defaulted from the work schedule 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 (function P2001). Pair Type 3 This type relates to attendance hours that have been entered into the system in infotype 2002 (function P2002).
78
1998 SAP Labs, Inc.
By the end of the processing in T555Y, the collected hours will have been assigned to the appropriate time pair, which will contain a time type and a processing type. The time type accumulates the collected hours into time balances. The processing type, in step 4 (overtime calculation subschemas), and step 5 (generate time wage types from time pairs based on the conditions in T510S) identify which hours should be generated in time wage types. In release 3.0F, the delivered system generates only those time wage types that have the following processing types: Planned working hours Overtime hours Processing type S Processing type M
The time types in each line, and the processing types assigned to them, can be configured in T555Y 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 for absences. PSG 01 and MODIF T grouping 02 relate to negative paid employees. The processing 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 select whether a time wage type should be generated. This field, therefore, plays a major role in deciding whether certain hours should, or should not be paid for different staff. The time pair processing type is also used for decision making in the rules in TM04 step 4.
Step 4: Calculate Overtime Hours and Flag Overtime Pairs

In step 3, we saw that T555Y assigns time pairs and processing types to collected hours. In the final line of T555Y, notice that pair types 1 and 3 (Attendances) generate processing type M for overtime, if the attendance type used to enter the hours had processing and time type class 05 (Overtime). Step 4 (lines 000410 000430) occurs if the user decides that an employee was entitled to overtime, and then directly entered the hours using an overtime attendance type.
If we want the system to check to see if an employee has exceeded overtime hours thresholds, we need to configure the appropriate subschema.
1998 SAP Labs, Inc.
79
The subschemas are: TW10 TW15 TW30 and TW20 Overtime after 6 consecutive working days Overtime after 8 hours per day Overtime after 40 hours per week
Please see chapter 4 for a full description of how these subschemas work. One of the results of the processing in these schemas is that hours that qualify for overtime are assigned processing type M for overtime. The system then moves to step 5 for the next overtime processing stage.
Step 5: Generate Time Wage Types from Time Pairs

In the delivered system, when TM04 reaches step 5 (lines 000440000490), all of the attendance hours collected in step 2 for employees not using positive time recording (PDC) have been assigned time pairs that have processing type S for planned hours or processing type M for overtime hours. Employees using PDC are processed by TM00, which is outside the scope of this document. In step 5, the system generates time wage types from these time pairs, based on the rules configured in T510S (Time Wage Type Selection Rule table). Time wage types generated from time pairs with processing type S are entered into internal table DZL, with processing type S. Time wage types generated from time pairs with processing type M will be entered into internal table ZML with processing type M.
710
1998 SAP Labs, Inc.
1. To access this step, in the IMG, choose Time Evaluation Time Accounting Without Clock Times Time Wage Type Selection and Overtime Compensation. 2. This menu path subdivides into eight options. Several of these lines are described below.
1
Define valuation classes for period work schedules With this option you can assign valuation classes to period work schedules. Different valuation classes can then be attached to the time wage type generation rules in T510S, so that a time wage type can have different 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. The settings in DAYMO enable you attach different settings to the time wage type rules in T510S, based on which 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 a public 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 public holiday, 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 a public 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, in T510S, 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 different groups of employees can have different T510S rules based on the day of the week being processed. The
1998 SAP Labs, Inc.
711
best way to use function DAYMO and MODIF D together, is to have the DAYMO settings as set out above, 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 the wage type generation rules are configured for this wage type in T510S: 1. Click Execute next to Set rules for wage type generation. 2. Select a Country grouping and click Continue. 3. Choose a wage type. 4. Click Details to see the screen that begins the next section.
4 3
712
1998 SAP Labs, Inc.
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 been set for it for groups of employees, sets of hours, and days of the week. If all of the conditions have been met, the wage type is generated. The different wage type generation rules for a given wage type can be quickly 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 in TM04 step 1. The same wage type can therefore have different conditions applied to it for different groups of employees. Day grouping This setting indicates the value set in function DAYMO and MODIF D in function MOD. The same wage type can therefore have different conditions attached to it for different groups of employees on different days of the week. Subsequent number This is used if you have different conditions within the same time wage type selection group, and the same day grouping. You then assign a sequential number to the same groupings. This number would be used where, for example, the same wage type should be generated for more than one set of hours in the same day. Valid processing types Time pairs with the processing types listed here will have this time wage type generated.
1998 SAP Labs, Inc.
713
Fixed Val. In this field you can enter a fixed number of hours to be paid if an employees time pair meets all other conditions, 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 hours worked, 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.), PH Pre. 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 the previous and subsequent days, (hence b123456789 all have X), and as long as the current day has a holiday 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 the processing type (such as M for overtime) already contains X number of hours for the day being processed.
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 generated for 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.
714
1998 SAP Labs, Inc.
Relevant processing types In this field, specify which processing types are to be taken into account in the requirement of a minimum or a maximum number of hours, in other words, which time pairs are to be counted for those hours.
Interval If this field is selected, the minimum or maximum number of hours entered must have been reached before 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 the rules configured in T510S, (Time Wage Type Selection Rule Table). Time wage types generated from time pairs with processing type S (Planned Hours) are entered in the internal table DZL with processing type S. Time wage types generated from time pairs with processing type M (Overtime Hours) are entered into internal table ZML, with processing type M.
Step 6: Further Processing of Overtime Wage Types

At the end of step 5, time wage types are generated, with a number of planned or overtime hours assigned to them. In step 6 (lines 000500000520), the addition processing is applied to the generated overtime wage types. Addition processing proceeds as follows: 1. Subschema TW00 is commented out in the delivered system, but it can be reactivated, if necessary. This subschema is configured to generate a higher bonus if an employee works more than 10 hours of overtime in a given week. It checks the overtime hours generated in MM10, and if 1 they exceed 10 hours, it generates 2 MM20 for the additional hours. 2. Rule TC20 checks to see if the generated wage types have an entry in processing class 17, which determines if the overtime hours should be paid, compensated with vacation, or both. Rule TC20 is explained in detail in chapter 5, Compensating Overtime with Renumeration or Vacation.
1998 SAP Labs, Inc.
715
Step 7: Check Overtime Compensation Account

In step 7 (line 000610), the overtime compensation account is checked. 1. Function ACTIO calls rule TR91. At the end of the current payroll period, TR91 checks to see if all of the hours accumulated in time type 0410 (Time Off for Overtime) have been used up. The rule takes 1 the accumulated hours for the present payroll period in time type 0410 (Time Off from Overtime), (HRS=X0410), and adds the hours from the daily balance table TES for 0410 (HRS+D0410) and compares 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), COLER40 generates 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 then remunerates the unused hours.
716
1998 SAP Labs, Inc.
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 the Time Evaluation results in the following payroll input files: PREL PCL1 PCL2, cluster B2.
The data is now ready for pickup and further processing in the next payroll run.
1998 SAP Labs, Inc.
717
Main Steps in Overtime Processing, Steps 916 Overview
Chapter 8: Main Steps in Overtime Processing, Steps 916

Contents
Overview ..............................................................................................................................................................................................................81 Steps 916: The Payroll Calculation Program..................................................................................................................................................81 Step 9: Schema U000Subschema UODP Imports Data From PCL2 Cluster B2 ......................................................................................82 Subschema UT00..................................................................................................................................................................................83 Step 10: Rules X010 and X013 Commence Wage Type Valuation ..............................................................................................................84 Step 11: Function MOD Sets Table Modifiers ...............................................................................................................................................84 Step 12: Import Cluster B2 Data for PDC Employees and Process TC00 ....................................................................................................85 Subschema TC00..................................................................................................................................................................................85 Overtime Functionality Comparison: TM04 (RPTIME00) Compared to TC00 (RPCALCU0) ................................................................87 Step 13: Weekly Overtime Analysis ..............................................................................................................................................................87 Step 14: Process Infotype 2010 Data in X930. .............................................................................................................................................89 Step 15: U.S. FLSA Regular Rate of Pay Valuation....................................................................................................................................810 Function IF UTRR................................................................................................................................................................................811 Subschema UTR0 ...............................................................................................................................................................................812 Rule UTR0...........................................................................................................................................................................................813 Determining the Relevant Amounts and Number of Hours with Processing Class 85 ........................................................................814 Step 16: The Final Step in Wage Type Valuation, Rule X015.....................................................................................................................814
Overview
Chapter 7 explained steps 18 of overtime processingthe steps that occur in the Time Evaluation program RPTIME00, schema TM04. This chapter continues with steps 916, which take place in the Payroll Calculation program.
Steps 916: The Payroll Calculation Program

At the end of step 8 in the previous chapter, the results of RPTIME00 were stored in files PREL, PCL1, and PCL2. 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 916 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 many different payroll periods as the customer requires. If RPTIME00 is run every day, the payroll program has several days worth of data waiting for pickup in cluster B2.
1998 SAP Labs, Inc.
81
Main Steps in Overtime Processing, Steps 916 Steps 916: The Payroll Calculation Program
Step 9: Schema U000Subschema UODP Imports Data From PCL2 Cluster B2

The following screenshot shows schema U000 for RPCALCU0: Schema U000 imports and processes the RPTIME data in the following fashion: 1. Subschema UODP (line 000030) imports the following data from PCL2 with function IMPRT: The previous payroll results from cluster RU (for the U.S.). The results of RPTIME00 from cluster B.
3 1 2
2. Double-click on UODP to see the functions it contains, such as IMPRT. 3. Subschema UT00 (line 000090) processes time data for RPCALC00, including the imported RPTIME00 data.
The following screenshot of subschema UT00 highlights processing steps 1016 for time wage types.
82
1998 SAP Labs, Inc.
Subschema UT00
Subschema UT00 completes the following steps: 10. Rules X010 and X013 begin wage type valuation (lines 000100 000110). 11. Function MOD sets table modifiers (line 000120). 12. Import cluster B2 data for PDC employees and process TC00 (lines 000150000210). 13. Weekly overtime analysis (line 000220). 14. Process infotype 2010 data in X930 line 000280). 10 15. FLSA, regular rate of pay valuation (line 000320000350). 16. Rule X015, the final step in wage type valuation (line 000370).
12 11
13
14
15
16
Steps 1016 above complete the processing of time wage types, such as overtime payments. These steps are described in detail in the remainder of this chapter.
1998 SAP Labs, Inc.
83
Step 10: Rules X010 and X013 Commence Wage Type Valuation
In step 10 (lines 000100000110), the Payroll Calculation program calls rules X010 and X013, which calculate an hourly Rate for wage types that have valuation basis nn. See chapter 3, Wage Type Valuation for a full description of how these rules work.
Step 11: Function MOD Sets Table Modifiers

In step 11 (line 000120), function MOD calls the ESG for PCR variants for rule UMOD, which sets the modifiers for the following tables: MODIF A Selects the employee grouping for absence valuation in T554C. MODIF 2 Selects the payroll modifier for constant valuations in T510J. MODIF B Selects the payroll modifier for limits in deductions in T51D1. This is net payroll and is outside the scope of this document. You will see the effects of MODIF 2 in step 16 (rule X015, final wage type valuation).
84
1998 SAP Labs, Inc.
Step 12: Import Cluster B2 Data for PDC Employees and Process TC00
In step 12 (lines 000150000210), UT00 uses an IF and ELSE statement to call subschema TC00 in the following fashion: 1. The IF statement means that IF PDC is active for an employee, (for example, if an employee has a Time Management status of 2 in infotype 0007), cluster B2 of table PCL2 should be made available for processing in subschema TC00. 2. PRINT means that the time wage types in table ZL should be printed on a new page (NP) in the program log. 3. The series DAYPR TC00 PDC initiates the daily processing of time data in subschema TC00, taking into account the data from cluster B2.
1 2 3 4
4. ELSE states that if PDC is not active for an employee, (for example, if an employee does not have a Time Management status of 2 in infotype 0007), the daily processing of time data (DAYPR) in subschema 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, which processes daily time data within the Payroll program. At this point, it is not essential for a customer to implement RPTIME00 in their system. If they only have basic requirements for time recording and time evaluation, then the Payroll Calculation program alone may have sufficient functionality for their needs. Please see chapter 4 for a summary of the additional functionality supplied with RPTIME00. 1. Double-click on TC00 in line 000180 of subschema UT00.
1998 SAP Labs, Inc.
85
Notice that subschema TC00 duplicates much of the functionality of schema TM04, which completed steps 18 of the overtime processing. Subschema TC00 functions as follows: 2. Function MOD calls rule TMOD, which sets table modifiers in T510S and T555Z. 3. Function TIMTP assigns a processing type and a time type to time pairs with T555Z. T555Z processes hours in a similar way to T555Y (discussed in step 3), and assigns processing types and time types to time pairs. Processing types S and M flag planned and overtime hours for further processing by T510S. Time pairs formed in RPTIME00 will retain the same processing types and time types. 4. Function DAYMO sets the day groupings for T510S. 5. Function GWT takes the hours from the time pairs that meet the conditions set in T510S and generates time wage types. 6. Function POVT calls rule TC00 to check if the user has selected an overtime compensation type for the generated time wage types. Chapter 5 discusses the options that are available to compensate overtime by vacation and by remuneration. In TM04, this vacation and remuneration is processed in rules TC20, TC21, and TC22, and TC10, TC11, and TC12. However, because it is part of RPCALU0, and not RPTIME00, rule TC00 cannot update overtime time types and time quotas like TM04 would. Rule TC00 is therefore configured to update wage type MM70 (Claim to Time Off for Overtime). MM70 is not one of the U.S.-delivered wage types.
3 4 5 6
86
1998 SAP Labs, Inc.
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 the time the payroll was run. Subschema TC00 evaluates time data where only the exceptions to the work schedule have been 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. Subschema TC00 only processes RPTIME00 results for PDC employees, (who would be processed by schema 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 various rules in schema TM04, which can be used for all employees except those whose clock-in and clock-out times 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 the system to: Generate overtime on a daily basis, a weekly basis, and so on, with different conditions for different groups 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 RPCALCU0
TC00 automatically generates overtime for all attendances recorded in infotypes 2002 and 2005 that are outside 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 type assigned to the time pair, which is assigned to the attendance in T555Z.
Step 13: Weekly Overtime Analysis

At the end of step 12, the results of RPTIME00 are imported to RPCALCU0, and subschema UT00 has performed daily time data processing in TC00 for all employees not included in RPTIME00 and clock-in and clock-out employees who have been processed by schema TM00 in RPTIME00.
1998 SAP Labs, Inc.
87
1. In Step 13 (line 000220), subschema XT01 analyzes the overtime wage types by period. 2. Double-click on XT01.
1 2
Subschema XT01 has been deactivated in the delivered system by the * in the execute function column (E). A screen showing subschema XT01 appears.
Schema XT01 goes through the following processes: Func. IMPRT INSZL SORT PRINT PZL Par1 01 01 ZL NP X940 ZL GEN NOAB M Par2 ZL M Par3 Par4 Operation Descriptions Time wage types (ZL) are imported from the previous payroll period and placed into table ZH (the current period) The overtime wage types are extracted from the ZH table (processing type M). The ZL table is sorted alphabetically. A new page (NP) is created in the log for all of the current period and last period time wage types. The ZL table is processed in rule X940 for the overtime wage types (processing type M). Rule X940 only processes wage type MM01 and converts wage type MM01 to MM02 if more than 10 overtime hours have been worked in a week. The wage types are deleted from the previous period that was added to ZL by function INSZL.
DELZ
00
88
1998 SAP Labs, Inc.
Func. PRINT EXPRT
Par1 NP
Par2 ZL ZL
Par3
Par4
Operation Descriptions A new page is created in the log for all of the current period overtime wage types. The current period overtime wage types are exported back to table 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 time wage type processing. In step 14 (line 000280), the program looks at any data entered into an employee record in infotype 2010 and processes the data in rule X930.
The screenshot to the right shows an example of infotype 2010.
Valuation Basis *
Valuation Basis X
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
1998 SAP Labs, Inc.
89
An overtime compensation type A premium An external document, such as an invoice
The screenshot to the right shows rule X930. Notice that the rule first makes a decision on the valuation basis entered by the user in infotype 2010.
Line 000010 000020 to 000060
Operation Descriptions A decision (D) is made on the valuation basis entered for the wage type in infotype 2010 (VALBS?0). 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 without further 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 with the 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 on the entries in the second part of infotype 2010. This area of processing is outside the scope of this document, but please read the documentation for these rules for a description of how they work.
Step 15: U.S. FLSA Regular Rate of Pay Valuation

Chapter 4 summarizes the U.S. Fair Labor Standards Act (FLSA), which stipulates that certain employees should be paid overtime for excess hours worked per week. In addition, some state laws legislate that overtime is paid for excess hours worked per day. Chapter 4 described the rules in schema TM04 in RPTIME00, which are used to calculate the excess hours per day or per week and should count towards overtime. The FLSA legislation also lends the second part to the overtime equation, called the Regular Rate of Pay, which helps determine the Rate at which excess hours should be paid.
810
1998 SAP Labs, Inc.
Chapter 3 described the different ways in which an hourly Rate can be calculated, using wage type valuation. Step 15 (lines 000320000350) contains a different type of wage type valuation that is designed to work 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 the salary is intended to compensate. For employees paid on a piecework or commission basis, their rate of pay is the total earnings for the week, 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 pay for 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 or services, (for example, meals and lodging). Retroactive pay or back pay awards On-call pay Cost of living adjustments
Function IF UTRR
Step 15 (lines 000320000350) comprises the following functions: 1. IF calls rule UTRR. 2. Double-click on UTRR.
1998 SAP Labs, Inc.
811
Rule UTRR appears. The lines of this rule are described below.
Line 000010 000020 000030 000040 000050
Operation Descriptions A decision (D) is made on the employee subgrouping for the PCR value (OUTWPABART). A second IF condition is set. SCOND=F IF means that if the ESG for PCR value is not 1, the condition is false. A decision (D) is made on the setting in the Working Week field in infotype 0007 (OUTWPWWEEK). If the ESG for PCR value is 1, but the Working Wee k field in infotype 0007 is less than two characters, the condition is not fulfilled (1 *). 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 is processed in the next function.
Subschema UTR0
1. In subschema UT00 (step 15) in line 000330, the copy function calls subschema UTR0, which processes hourly paid employees (ESG for PCR value 1) who have a workweek entered in infotype 0007. 1 2. Double-click on schema UTR0.
812
1998 SAP Labs, Inc.
3. In schema UTR0, the line ZLIT UTRO GEN NOAB * puts the wage types from the ZL table into the payroll input table according to rule UTR0, which processes these wage types as described in the following section. 4. Double-click on rule UTR0.
4 3
Rule UTR0
1. Rule UTR0 makes a decision (D) on the value of processing class 85 for the wage type being processed (VWTCL 85). 2. If the wage type has a PC85 value of anything other than 15, it is passed on without further processing in rule UTR0 (ADDWT *). 3. For wage types with PC85 values 15, SETIN X= WWADDWT * sets variable splits based on the workweek selected in infotype 0007, and attaches that split to the wage type. Processing continues in subschema UTR0 in the following fashion: 4. PRINT NP V0 creates a new page in the log for the variable splits. 5. X015 then valuates every wage type (GEN, NOAB) selected by the decision rule UTRR, so the FLSA qualifying wage types will now have a Number of hours (from Time Management) and an Amount (calculated in X015). However, the Amount will not necessarily have been calculated by X015 using the correct Rate for the FLSA qualifying wage types.
1 2 3
4 5 6 7
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
1998 SAP Labs, Inc.
813
processing class 85. RGRT looks for wage types that have processing class 85 values and processes these 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 the relevant 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, their valuation 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, their valuation 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, their valuation 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, their valuation basis is nn). Value 5 does not contribute to the regular rate.
Step 16: The Final Step in Wage Type Valuation, Rule X015
In step 16 (line 000370), rule X015 performs the final step in the processing and calculates the overtime Amount to be paid for all wage types, except the FLSA qualifying wage types that were valuated in step 14. Rule X015 is described in detail in chapter 3, Wage Type Valuation.
814
1998 SAP Labs, Inc.
Glossary Error! No text of specified style in document.
Glossary
Modifiers 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-end Accrual MODIFD = Wage Type Processing with Regard to Month-end Accruals MODIFW = T510S Wage Type Generation
The modifiers allow you to set a specific range of table entries for different groups of employees. Operation PIT Building block for rules that is used to process wage types. Processing Input Table Based on designated rules, PIT accesses a personnel calculation rule that processes contents of input table IT. PORT Transfers data from the previous payroll; based on specified rules, PORT initiates a cycle which processes the wage types of the old results table. Stored in T512W, this item is used in rules to determine which version of the rule should be selected for a particular wage type. Process time wage type table ZL. The time evaluation drive, it is used to evaluate employee time data which has been recorded using time infotypes or at time recording systems. The elements of a wage type. Controls how wage types are processed during payroll processing (rules consist of operations). A series of sequential processing steps for payroll and time evaluation. Main schema
Processing Class
PZL RPTIME00
Rte, Num, Amt Rule Schemas
1998 SAP Labs, Inc.
Glossary Error! No text of specified style in document.
U000 U.S. Payroll accounting schema for RPCALCUO K000 Canadian payroll accounting schema for RPCALCUO TM00 Main schema for Time Management TM01 Time evaluation schema for exceptions to the work schedule. TM04 Time evaluation schema without clock times. Subschema Contains processing steps needed by payroll. Subschemas are called from a main schema using function copy. An allocation of times based on payment aspects. A wage type that needs to be valuated because it carries only a unit (i.e., hours, days, etc.) Technical Wage types 100X (i.e. /001) and is used to store hourly rates that will be used against time wage types that need to be paid. Assigned to absences to determine how they will be processed in payroll. Represents deductions, earnings, or tax codes.
Time types Time Wage Type Valuation Basis
Valuation Rule Class Wage types
1998 SAP Labs, Inc.
Index Error! No text of specified style in document.
Index
A Absence hours 78 processing type A 77 Absence types assigning classes 76 assigning processing types 76 Absence valuation group having different 213 MODIF A 210, 74, 84 Absences 75, 77, 79, 87 evaluating using TM04 72 recorded 49, 412, 413 Absenses recorded 417 Accessing different rule variants 211 Help to view source text 25 rules using IMG or PE02 25 rules using MOD 28 rules using PIT and PORT 27 schemas using IMG or PE01 25 ACTIO47, 410, 411, 412, 414, 716 ADDB0903Z 411 ADDDB updating daily balance table TES 45 ADDDB004154, 55, 56, 57, 5 9 ADDDB0042 54, 55, 56, 58 ADDDB004354, 55, 56, 57, 5 8 ADDDB041054, 55, 56, 57, 5 8, 59 ADDDB0900 415 ADDDB0900Z 415 ADDDB0903Z45, 47, 410, 411, 412, 413, 414 ADDDB0903ZCOLOP 49 ADDDB0904 48, 49 ADDDB0904Z47, 410, 411, 4 16 ADDDB0905Z 417, 418 ADDDB0906Z 47 Addition processing 715 ADDNA 39 ADDNA * 310 ADDWT 38 ADDWT *34, 35, 36, 37, 38, 310, 323, 810, 813 ADDWT /001 35 ADDZLM* 54, 55, 56, 57, 58 ADDZLMMM00 716 ADDZML1 54, 55, 56, 57, 58 ADDZML2 54, 55, 56, 57, 58 Adjust average bases to pay scale3 39 Adjustment field 339 Adjustment rules cumulation types 339 fields 339 for averages bases 338 Amending schemas and rules 215 AMT = BETRGAMT?0 810 AMT?0 38 AMT=M 311 Asences recorded 42 Assigning collected hours to time pairs 78 hours to time pairs 75 valuation bases to overtime wage types 326 Attendance days, consecutive calculating using TW10 417 Attendance hours 78, 710 Processing type P 77 Attendance quotas infotype 2007 11 Attendance types configuring to time pairs 12 defining classes 77 Attendances evaluating using TM04 72 infotype 2002 12 schema TC00 87 Attributes button viewing program class and country grouping 25 Automatic overtime generation 11 Average rates valuating time wage types 329 Averages calculation adjustment rules 338 fields and funcitionalities 336 no hours in number field of MV3 11 rule X018 processes final 310 rules 334 table MV 310, 311 Averages configuration valuating time wage types 329 Averages processing configuring from scratch 329 configuring wage types for 33 evaluating primary wage types3 31 first step, rule X016 39 including primary wage types3 29 rule X015 branches to X016 38 rules X016, X017, and X018 33 B B2 81, 83, 85 importing data for PDC employees and process TC008 5 Back pay 44, 811 Basic pay infotype 0008 214 maintaining for valuation bases3 20 Basic pay wage types 33, 319 C Calc. rule 337 Calculating overtime according to consecutive attendance days 417 daily 414 hours 79 on daily or weekly basis 41 Clock-in, clock-out11, 42, 71, 8 7 Cluster B 42 COLER40 716 Collected hours assigning to time pairs 78 COLOP 48, 410, 416, 418 COLOP*48, 49, 411, 413, 4 16, 417 Compensating overtime choosing compensation types 52 vacation with derived wage type percentages 54, 56 with remuneration54, 55, 56, 58 with remuneration and vacation5 1, 54, 55, 56, 57, 58 with vacation 55, 57, 59 Compensation infotypes 2005 and 2007 11 Compensation types 53 choosing 52 overtime 55, 58 Cond.exit 714 Conditions
1998 SAP Labs, Inc.
Day 714 Time 714 Configuring customer requirements 215 overtime calculations46, 414, 417 overtime compensation 53, 57 processing class 17 for overtime wage types 52 schemas and rules 215 wage type valuation 312 Configuring wage type valuation3 19, 326 Constant valuation constants dependant on pay scale 318 creating bases 312 dependant on wage types 313 determining per wage type 313 general processing of time data3 16 modifier for 315 Constant wage type valuation 210 Constants dependant on pay scale3 18 Constants dependant on wage types 313 determine constant valuation per wage type 313 general processing of time data3 16 modifier for constant evaluation3 15 Contract field configuring in IMG 214 Copy function calling subschemas 23 Copying schemas and rules 215 Cost of living adjustments 44, 811 Country grouping 313 Create constant valuation bases 312 constants dependant on pay scale 318 constants dependant on wage types 313 Create person-related valuation bases 319 form valuation bases 321, 323 general processing of time data3 24 Create wage type catalogue 712 Cumulation field averages calculation 337 Cumulation types 337 adjustment rules 339
for averages 338 Customer configuration requirements 215 tracking schemas and rules216, 218 Customer rules 213 Customer time wage types 712 D D0904 410 Daily balance table TES44, 45, 4 15, 55 operation ADDDB 45 rule TC10 57, 58 rule TC11 58 rule TC12 59 rule TC20 54 rule TC21 55 rule TC22 56 rule TO01 415 rule TW01 413 rule TW03 414 rule TW33 410 rule TW34 411 rule TW36 412 subschema TW20 412 time type 0410 716 Daily overtime after X hours time type 0900 44, 415 Data flow rules TC10, TC11, TC12 53 rules TC20, TC21, TC22 53 Day grouping 713 Day types 415 DAYMO 711, 713, 86 DAYPR 85 Define groupings 711 Define processing types 712 DELZ 88 Derived wage types329, 52, 54, 55, 56, 57, 58 Descriptions, schemas and rules changing or ammending 218 Determine constant valuation per wage type 313 Disability entitlements using averages configuration 329 Display data 26 DIVID ANR 311 DIVID ARR 34, 328 Documentation button explaining schemas or rules 25 Documentation, schemas and rules changing or ammending 218 new 218 RPDSYS00 program 25
E EE pay scale group 339 remuneration 11 subgroup grouping 340 ELIMI 35 ELSE function 46, 411 schema TM04 75 schema UT00 85 subschema TC00 85 Employee groupings using rule variants 212 Employee groupings 212 Employee Subgroup Grouping for Personnel Calculation Rules (ESG for PCR) 28 Employee Subgroups relating to table settings 28 Employees groupings operation OUTWP 213 Employees with workweeks having start times 46 without start times 411 EMPLR 214 ENDIF 75 Entering overtime automatic generation 11 manual data entry 11 ESG for PCR value 1 29, 812 employee table links 210 exception to rule X013 33 hourly paid staff 212 rule X013 36 ESG for PCR value 2 29 employee table links 211 rule X013 36 ESG for PCR value 3 210 employee table links 211 ESG for PCR variants configuring 215 Evaluation bases See Valuation bases Exempt employees 43 Exporting results to PCL2 717 EXPRT 74, 717, 89 F F. process 337 Fair Labor Standards Act (FLSA)4 2, 87 exempt and nonexempt employees 43 federal law verses state law 43 qualifying wage types 813, 814 regular rate of pay 43, 83, 810 FILLF N 39
1998 SAP Labs, Inc.
FILLPVM 49, 410, 416, 418 First-derived wage type 39 fields for valuation 329 rule TC10 57 rule TC11 58 rule TC20 54 rule TC21 55 rule TC22 56 Fixed Val. 714 Flextime 42 timetypes 71 FLSA See Fair Labor Standards Act Form valuation bases addition 321 division 323 Functions of schemas 26 G GCY48, 49, 412, 413, 54, 55, 58, 59, 810 GEN 27, 28, 88, 813, 814 General processing of time data USA 316, 324 GENTPB 410, 416 GENTPE 49 Grouping employees using operation OUTWP212, 2 13 using rule variants 212 with different payment structures 212 GWT 715, 86 H Help clicking for operation descriptions 35 consulting on MODIF 211 using to view source text 25 Hourly paid staff ESG for PCR value 1 212 regular rate of pay 811 subdividing 213 subschema UTR0 812 Hourly rate processing with configured rule variant 212 using rules X010 and X013 to fill PIT 34 Hours assigning to time pairs 75, 78 Hours collection schema TM04 73, 75 Hours reduced 340 Hours stored for next week time type 0904 44
Hours stored for this week time type 0903 44 HRS*%012 54, 55, 56 HRS*1,00 57, 59 HRS?0,00 716 HRS?6,00 418 HRS?COVERT 49 HRS?D0900 416 HRS?D0906 48, 49 HRS+1,00 418 HRS+D0410 716 HRS+PNUM 49, 416 HRS=0,00 411, 413, 415, 417 HRS=1,00 418 HRS=48,00 47 HRS=8,00 415 HRS=99,00 415 HRS=COVERTHRS-D0903 410 HRS=D0900 416 HRS=D0903 49, 410, 412, 414 HRS=D0904 410, 416 HRS=IWWEEKHRS+24 47 HRS=L0905 418 HRS=M0903 47, 411, 413 HRS=M0904 47 HRS=PBEG 48 HRS=PEND 49 HRS=PNUM 48 HRS=R 49 HRS=S 415 HRS=X0410 716 HRS>8,00 415 HRS-D0904 416 HRS-M0903 410, 412, 414 HRS-M0904 410, 411 I ID: Vbasis 339 IF function 75 rule TW00 417, 418 rule TW31 46 rule UTRR 811, 812 schema TM04 75 schema UT00 85 subschema TC00 85 subschema TW10 417 subschema TW30 46 IMPRT 26, 82, 88 Ind:AMT 339 Ind:NUM 339 Ind:RTE 339 Infotype 0001 Organizational Assignment 214 using the Contract field 214 Infotype 0005 Leave Entitlement 42
Time Evaluation 71 Infotype 0007 46, 411 pair type 1 78 Planned Work Time 214 rule TW31 46, 47 rule UTR0 813 rule UTRR 812 schema UT00 85 subschema TW30 45 subschema UTR0 812 Infotype 0008 Basic Pay 214 basic pay configurations 320 total working time 323 Infotype 2001 pair type 2 78 subschema TC00 87 Infotype 2002 entering overtime manually 12 pair type 3 78 subschema TC00 87 Infotype 2005 choosing compensation types 52 choosing remuneration or compensation 11 entering overtime manually 11 rule TC11 53, 58 rule TC21 53, 55 subschema TC00 87 Infotype 2007 choosing compensation types 52 choosing remuneration or compensation 11 entering overtime manually 11 rule TC11 53, 58 rule TC21 53, 55 Infotype 2010 89 as factor in rate 39 averages processing 337 entering overtime manually 11 rule X930 89, 810 subschema UT00 83 Infotype 2011 time recording terminals 78 INSZL 88 Interval field 715 IWWEEKADDDB0906Z 47 L Leave compensation Leave entitlement infotype 0005 M M0903 410 52 42
1998 SAP Labs, Inc.
Maintain basic pay for valuation basis 320 Manual data entry 11 infotype 2002 12 infotype 2005 11 infotype 2007 11 infotype 2010 11 Master data configuration 212, 215 Max. 714 Max.No.Per 337 MEANV 01 310, 333, 337 MEANV 02 310, 333 MEANV REL 310 Min. 714 Minimum wage 43 MM00, wage type 314, 716 MM01, wage type 88 MM02, wage type 88 MM10, wage type 715 MM20, wage type 715 MM70, wage type 86 MOD function accessing rules 28 calling rule UMOD 28 in schema UT00 317 relating employee subgroups to table settings 28 setting table modifiers73, 74, 84 subschema TC00 86 subschema UT00 83 MODIF 2 84 payroll modifier in T510J 210 MODIF A 74, 84 absence valuation group 210 MODIF B 84 payroll modifier in T51D1 210 MODIF D 711, 713 MODIF function different uses 211 MODIF T 74, 78, 79 MODIF W 74, 713 Modifier for constant evaluation315 Monthly balance table SALDO44, 45 rule TW34 411 MULTI NRA 38, 310, 311 N Naming conventions customer-configured schemas and rules 218 schemas and rules 215 Negative time processing42, 45, 72 schema TM04 42
Negative time recording pair type 1 78 NEXTR 39 No.periods 339 No.rel. per 337 NOAB 27, 88, 813, 814 Non-cash payments 44, 811 Non-discretionary bonuses 44, 811 Nonexempt employees 43 NP 85, 88, 813 NUM?0 38, 810 NUM?0.00 311 NUM= ANZHLADDWT * 810 Number of hours determing with PC 85 814 O On-call pay 44, 811 Operation descriptions rule TO01 415 rule TO02 416 rule TW00 417 rule TW06 48 rule TW31 47 rule X010 35 rule X013 36, 37 rule X015 38 Operation OUTWP getting rules to make decisions2 14 grouping employees 212, 213 other field decisions 215 OPIND 810 Organizational Assignment infotype 0001 214 OUTOTCLTYP 55, 58 OUTTPEXTIM 48 OUTTPPTYPE 48, 413, 416 OUTTPVTYPE48, 411, 413, 4 16 OUTWP See Operation OUTWP OUTWPABART 812 OUTWPEMPLR 214 OUTWPWWEEK 812 OVERT 49 Overtime attendance types 79 calculating consecutive attendance days 417 calculating daily 41 calculating daily 414 calculating on a weekly basis41, 45 compensating with remuneration and vacation 51
compensation account checked7 4 compensation account,checking of 716 configuring compensation in rules TC10, TC11, TC12 57 configuring compensation in rules TC20, TC21, TC22 53 generating, modifying rules 87 processing, Payroll Calculation program 81 requirements, state and federal43 weekly analysis 83, 87 Overtime compensation types55, 5 8 type 1 55, 58 type 2 55, 58 type 3 55, 59 Overtime hours calculating 79 processing type M 77, 79 time type 0040 44 Overtime time pairs flagging 79 schema TM04 73 subschema TW20 412 Overtime time types rule TC00 86 Overtime wage types 32 configuring processing class 175 2 depending on attendance in T555Z 87 further processing of 715 schema TM04 73 subschema XT01 88, 89 P P. Mod 314, 315, 316 P2000 75, 78 P2001 75 P2002 75 P2003 75 Pay increase 340 Pay scale 328 Payment structures grouping employees 212 Payroll Calculation program21, 4 2, 81 RPCALCU0 22, 71 subschema TC00 85 wage type valuation rules 33 Payroll input file exporting results to PCL2 717 PCL2 42 Payroll input table
1998 SAP Labs, Inc.
subschema UTR0 813 Payroll Input Table filling with hourly rate using rules X010 and X013 34 Payroll modifier having different in T510J and T51D1 213 in T510J, MODIF 2 210, 84 in T51D1, MODIF B 210 table T51D1, MODIF B 84 Payroll output table 328 Payroll periods adjustment rules 338 averages calculation 337 averages processing 337 PCL1 717, 81 PCL2 717, 81, 82, 85 exporting results to 717 PDC 85 PDC employees 83, 87 importing cluster B2 data 85 PDC time recording 42 evaluating with TM00 72 PE01 See Transaction PE01 PE02 See Transaction PE02 Percent 1 340 Percent 2 340 Percentage applied to valuated amount 328 increases, adjusting average bases 340 Period work schedules assigning valuation classes 711 PIT See Process Input Table Planned work time infotype 0007 214 processing type S 48, 77, 79 PORT See Process Old Results Table PORT function set up charts 28 POS 75 Positive time 11 Positive time recording (PDC) 710 POVT 86 PREL 717, 81 PRINT 26, 85, 88, 89, 813 Process data 26 Process Input Table (PIT) 24 accessing rules 27 processing data 26 set up charts 28 Process Old Results Table (PORT)2 7 accessing rules 27 Processing class 1711, 52, 53, 5 4, 57
configuring for overtime wage types 52 rule TC20 715 rules TC1012 52, 53 rules TC2022 52, 53 value 1 57 value 2 57 value A 54 value B 54 value C 54 value V 58 values 19 and V 57 values 3, 4, 5 58 values 69 58, 59 values D, E, and F 54, 55, 56 Processing class 85 813, 814 determining number of hours 814 determining relevant amounts8 14 regular rate of pay 814 Processing type M 710 Processing type A table T555Y 77 Processing type M12, 77, 79, 7 10 changed from S 49, 410, 416 rule TO00 418 rule TO02 416 subschema TC00 86 subschema TW20 412 subschema XT01 88 table T555Y 77, 79 table ZML 715 Processing type P rule TO00 418 table T555Y 77 Processing type S 710 planned work time 48 rule TO02 416, 417 rule TW02 413 rule TW04 49 rule TW06 48 rule TW35 411 subschema TC00 86 table DZL 715 table T555Y 77, 79 Processing types 79, 86 assigned by absences types 76 assigned by attendance types 77 assigned to time pairs 86 assigning to time pairs 77 defining additional 712 relevant 715 table T555Y 77 valid 713
PTIP PZL Q Quota type 01 R
48, 411 88
11
Rate of pay See Regular rate of pay Read data 26 Reduction in hours same pay 340 Regular rate of pay 43, 810 configuring in processing class 85 813 definition 811 payment examples 811 processing class 85 values 814 Rel. test 337 Relating employee subgroups to table settings 28 Relevancy tests averages calculation 337 Relevant amounts determining with PC 85 814 Relevant cumulation rule in T511A 311 Relevant processing types 715 Remuneration11, 39, 51, 52, 5 4, 57, 58, 86 infotypes 2005 and 2007 11 overtime compensation51, 54, 55 Retroactive pay 338, 44, 811 increases, four options 339 or back pay awards 44 RGRT 813 RPCALCK0 Payroll Calculation program, Canada 22 RPCALCU0 71, 81, 82, 87 in schema TC00 87 Payroll Calculation program, U.S. 22 RPCALCX0 72 RPCALU0 86 RPDSYS00 program 214 fields OUTWP makes decisions on 215 schemas and rules documentation 25 RPTIME0042, 44, 71, 81, 82, 85, 86, 87 schema TM04 in 87 subschema TC00 87 Time Evaluation program 42 RTE 323
1998 SAP Labs, Inc.
RTE?0 38 RTE=TSDIVP 34, 323, 324 RU 82 Rule TC00 86, 87 Rule TC10 51, 53, 57 configuring compensation 52 PC17 values 1-9 and V 53 Rule TC11 53, 58 configuring compensation 52 PC17 values 6-9 53 Rule TC12 53, 59 configuring compensation 52 PC17 values 6-9 53 Rule TC20 51, 54 configuring compensation 52 configuring overtime compensation 53 PC17 values A-F 53 processing class 17 715 Rule TC21 53, 54, 55, 62 configuring compensation 52 configuring overtime compensation 53 PC17 values D, E, and F 53 Rule TC22 55, 56 configuring compensation 52 configuring overtime compensation 53 PC17 values D, E, and F 53 Rule TMOD 86 Rule TO00 418 Rule TO01 414, 415, 416 operation descriptions 415 Rule TO02 416 operation descriptions 416 Rule TR91 716 Rule TW00 417, 418 called by subschema TW10 417 operation descriptions 417 Rule TW01 413 subschema TW20 412 Rule TW02 413 behaves like rule TW35 413 subschema TW20 412 Rule TW03 414 behaves like rule TW36 414 subschema TW20 412 Rule TW0449, 410, 412, 413, 414 Rule TW06 48, 49 operation descriptions 48 Rule TW31 46, 47, 48, 410 operation descriptions 47 Rule TW32 46, 48 Rule TW33 46, 410 Rule TW34 46, 411
Rule TW35 46, 411 behaves like rule TW02 413 Rule TW36 46, 411, 412 behaves like rule TW03 414 Rule UMOD 315, 317, 318, 84 called by function MOD 28 variant $MOD 28 Rule UTR0 813 Rule UTRR 811, 812, 813 Rule variants accessing 211 configuring 28 grouping employees 212 maintaining 28 processing an amount 212 processing an hourly rate 212 rule X013 36 rule X015 37, 39 Rule X010 35, 37 commence wage type valuation8 4 filling PIT with hourly rate 34 form valuation bases, addition3 21 operation descriptions 35 subschema UT00 83 summary, valuation flow 33 Rule X013 36, 37 commence wage type valuation8 4 filling PIT with hourly rate 34 form valuation bases, division3 23 operation descriptions 36, 37 subschema UT00 83 summary, valuation flow 33 variant for ESG for PCR 1 36 variant for ESG for PCR 2 36 Rule X015 37, 84, 813, 814 operation descriptions 38 summary, valuation flow 33 variant for ESG for PCR 1 37 variant for ESG for PCR 2-9 39 wage type valuation, final step8 3, 814 Rule X016 38, 39, 333 averages calculation 337 averages processing 33 Rule X017 310 averages calculation 337 averages processing 33 processed by calculation rule 310 Rule X018 310 averages processing 33, 337 cumulation types 338
processing final averages calculation 310 Rule X115 39 Rule X930 89, 810 processing infotype 2010 89 Rule X935 810 Rule X940 88 Rules accessing using IMG or PE02 25 changing descriptions 218 configuring 215 configuring variants 28 copying and ammending 215 documentation, RPDSYS00 25 documenting new or ammended2 18 maintaining variants 28 naming conventions 216 tracking customer rules 216 upgrading 215 wage type valuation 32 S Salaried employees assigning rule variant values 212 regular rate of pay 811 semi-monthly paid 212 weekly paid 212 SALDOSee Monthly balance table SALDO Schema TM04 71 Schema TC00 See Subschema TC00 Schema TM00 710 evaluating PDC time recording4 2 in RPTIME00 87 Time Evaluation program 72 Schema TM04 51, 711, 81, 86 compared to rule TC00 86, 87 configuring tips 45 evaluating attendances and absences 42 in RPTIME00 87 negative time processing 42 screenshot 73 subschema TW10 417 subschemas TW30 and TW20 45 Time Evaluation program 72 using subschema TW15 414 Schema U000 22 UODP importing data from B28 2 Schema UT00 317 general processing of time data3 24
1998 SAP Labs, Inc.
screenshot 28 Schema XT01 See Subschema XT01 Schemas 22 accessing using IMG or PE01 25 changing descriptions 218 configuring 215 copying and amending 215 documentation, RPDSYS00 25 documenting new or ammended2 18 functions 26 naming conventions 216 tracking customer schemas 216 upgrading 215 SCOND=F 417, 418 SCOND=T 418 Second-derived wage type 39 rule TC10 57 rule TC11 58 rule TC20 54 rule TC21 55 rule TC22 56 valuation fields 329 Sequence of attendance days time type 0905 44 Set valid entries in tables 26 SETIN 813 Shift premiums 44, 811 SORT 88 Source Text button viewing schema or rule 25 Start time of the workweek time type 0906 44 Start times workweeks having 46 Subdividing hourly paid staff 213 Subschema TC00 85, 86, 87 called by Payroll Calculation program 85 called by schema UT00 85 compared to TM04 87 in RPCALCU0 87 RPTIME00 87 Subschema TW00 715 Subschema TW10 417 calling rule TW00 417 configuring overtime hours 710 consecutive attendance days 417 processing rule TO00 418 rule TW00 417, 418 Subschema TW15 calculating daily overtime 414 calling rule TO02 416 configuring overtime hours 710 Subschema TW20
configuring overtime hours 710 rule TW01 412 rule TW02 412 rule TW03 412, 414 weekly overtime for one workweek 45, 412 Subschema TW30 calling rule TW34 411 calling rule TW35 411 calling rule TW36 412 configuring overtime hours 710 different workweek definitions4 5, 46 IF and ELSE functions 46 PTIP calls rule TW32 48 rule TW33 410 workweeks without start times4 11 Subschema UODP importing data from B2 82 Subschema UT0083, 85, 814. See also Schema UT00 processing time date for RPCALC00 82 time data processing in TC00 87 Subschema UTR0 812, 813 Subschema XT01 88 Subschemas 22 Subsequent number 713 Symb. 714 T Table DZL 710, 715 Table FEHLER 716 Table modifers setting, MOD 73 Table modifiers T510S and T555Z 86 Table MV310, 311, 338. See also Averages calculation averages processing 337 cumulation types 338 Table settings relating to employee subgroups2 8 Table T510C 339 adjust average bases to pay scale 339 Table T510J 210, 32, 328 country-specific view of 313 having different payroll modifier 213 Table T510S 79, 710 attaching time wage type rules7 11 MODIF W 74
rule TO00 418 rule TW04 410 subschema TC00 86 time wage type selection rules7 13 Table T511A 333 averages calculation rules 337 processing calculation rules from 310 Table T511B cumulation types 338 Table T511C adjustment rules for averages bases 338 Table T511K 49 rule TW04 49, 410 subschema TW20 412 Table T512W rule TC10 57 rule TC11 58 rule TC20 54 rule TC21 55 rule TC22 56 Table T51D1 210 having different payroll modifier 213 Table T554C 210 having different absence valuation group 213 MODIF A 74 Table T555E 716 Table T555Y 12 assigning hours to time pairs in7 5 MODIF T 74 processing types 77 rule TW32 48 schema TM04 73 Table T555Z MODIF T 74 subschema TC00 86, 87 time pairs, TC00 87 Table T559A different workweeks 45 Table TIP 49 rule TO00 418 rule TO02 416 rule TW02 413 rule TW04 49, 410 rule TW06 48, 49 rule TW32 48 rule TW35 411 Table ZH 88 Table ZL 716, 88, 89 rule TC10 57, 58 rule TC11 58
1998 SAP Labs, Inc.
rule TC20 54 rule TC21 55 rule TC22 56 schema UT00 85 subschema UTR0 813 Table ZML 710, 715 Technical wage types311, 319, 3 23, 328 choosing to valuate 321 wage type valuation 33 TES See Daily balance table TES Time balances 79 Time daily balances 42 Time data 42 Time Evaluation program 41 final major step 717 RPTIME00 42, 71, 81 steps 1-8 71 Time Management derived wage types 329 Time pairs12, 42, 46, 61, 62, 77, 78, 79, 710, 713, 715, 86, 87 assigning processing type 77 creating splits 46 formed in RPTIME00 86 generating time wage types710, 86 in table T555Y 75, 78 overtime, subschema TW20 412 pair type 1 78 pair type 2 78 pair type 3 78 partial 49 planned 87 processing type and time type assigned to 86 rule TO00 418 rule TO02 416, 417 rule TW02 413 rule TW04 49, 412, 414 rule TW06 48 rule TW35 411 table T555Z 87 Time Pairs 410 Time quota 02 54 rule TC10 57 rule TC11 58 rule TC12 59 rule TC20 54 rule TC21 55 rule TC22 56 Time quotas rule TC00 86 Time recording 76 Time specifications 54, 57, 59
Time type 0040 44 rule TO00 418 rule TO02 416 rule TW04 49, 410 Time type 0041 rule TC10 57 rule TC12 59 rule TC20 54 rule TC21 55 rule TC22 56 Time type 0042 rule TC10 58 rule TC11 58 rule TC20 54 rule TC21 55 rule TC22 56 Time type 0043 rule TC10 57 rule TC11 58 rule TC20 54 rule TC21 55 rule TC22 56 Time type 0410 716 rule TC10 57 rule TC11 58 rule TC12 59 rule TC20 54 rule TC21 55 rule TC22 56 rule TR91 716 Time type 0900 44, 415 rule TO01 415 Time type 0903 44, 45 rule TW04 49 rule TW06 49 rule TW33 410 rule TW35 412 Time type 0904 44 rule TO02 417 rule TW06 48, 49 rule TW33 410 Time type 0905 44 rule TW00 417 Time type 0906 44 rule TW06 48 rule TW31 47 Time types 79, 86 assigned to time pairs 86 defining 76 hours stored in 44 in Time Evaluation program 71 list of 44 rule TO02 416, 417 storing daily balances 42 with processing type S 416
Time wage types312, 326, 331, 332, 337, 41, 71, 77, 710, 715, 81, 82, 86 assigning valuation bases 326 calculating Amount to be paid 71 choosing processing class 333 creating customer 712 displaying valuation 328 evaluated by averages processing 331 function GWT 715 generated by time pairs 86 generating from time pairs79, 7 10 generation rules 712 processing of in UT00 83 rule TC10 58 rule TC11 58 rule TC20 54 rule TC21 55 rule TC22 56 schema TM04 73 selection rule table, T510S 713 subschema XT01 88 table T555Y 79 valuating average amounts 329 valuation bases 32 viewing generation rules 713 Time Wage Types 418 TIMTP 86 Tm WT Sel. Rule Group 713 TMON 74, 78, 711 Transaction PE01 accessing schemas 25, 216 Transaction PE02 accessing rules 25, 216 TSDIVP 323 TW30 710 TYPES 73, 75 U Uncon.exit 714 UPDTQA0 56 UPDTQA02 54, 55, 56, 57, 58 Upgrading schemas and rules 215 UTR1 814 UTRO 813 V V0 813 Vacation 11, 43, 52, 86, 87 compensation 42, 51, 52 compensation ratios 58, 59 compensation, time types 71 using averages configuration 329 VAKEYALZNR 39
1998 SAP Labs, Inc.
VALBS?0 810 VALBS0 39, 39 VALBS1 39 VALBS2 39 Valid processing types 713 Valuating time wage types with average amounts 329 Valuation bases 37 assigning 326 averages processing 331 configuring time wage types 32 constants dependant on pay scale 318 create constant 312 create person-related 319 field selections 328 form by addition 321 form by division 323 general processing of time data3 24 including primary wage types3 30 infotype 2010 810 maintaining basic pay for 320 Valuation basis See Valuation bases Valuation classes assigning to work schedules 711 Valuation rules 210 Variants See Rule Variants VARSTDAYTY 415 VARSTFDYWW 47, 410, 411 VARSTFREE 415 VARSTLDYWW 47 VARSTPRSNT 417 VARSTWDY 413, 418 VWTCL 35, 36, 37 VWTCL 15 310, 333 VWTCL 17 54, 57 VWTCL 18 39
VWTCL 85 W
813
Wage type MM00 314, 716 MM01 88 MM02 88 MM10 715 MM20 715 MM70 86 Wage type field averages processing 337 Wage type valuation 31 configuring in IMG 312 constants dependant on wage types 313 create constant valuation bases3 12 equation 32 final step, rule X015 83, 814 flow, summary 33 flowchart 34 regular rate of pay 811 rule TC10 58 rule TC11 58 rule TC20 54 rule TC21 55 rule TC22 56 rule X010 33 rule X013 33 rule X015 33 rules and technical wage types 33 subschema UT00 83 using rules 32 Wage typesSee also Basic pay wage type; Derived wage type; Overtime wage type; Technical wage type; Time wage type called by function GEN 28
configuring for averages processing 33 copying 314 current 328, 329 giving new value and P. Mod314 primary 329 processing class 85 values 814 valuating for remuneration or compensation 11 Weekly overtime analysis 83 WGTYP 39 Work schedules, period assigning valuation classes 711 Workweek definitions beginning day 413 different 45, 46 employees with start times 46 employees without start times4 11 only one 45, 412 WPBP 26 WTy for Percentage 339 WW 46 WWTI 46 X X= WWADDWT * X015 X940 Z ZERO= N ZERO=A ZL ZLIT 35 34 88 813 813 813 88
1998 SAP Labs, Inc.

Schema

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Schema

Uploaded by

Copyright:

Available Formats

Understanding Overtime Schemas and Rules in Payroll and Time Evaluation

SAP Labs, Inc. R/3 Simplification Group

Understanding Overtime Schemas and Rules in Payroll and Time Evaluation

1998 SAP Labs, Inc.

Understanding Overtime Schemas and Rules in Payroll and Time Evaluation

1998 SAP Labs, Inc.

1998 SAP Labs, Inc.

1998 SAP Labs, Inc.

Introduction to Overtime Overview

Release 3.0F, U.S. Country-Specific

Who Should Use This Guide

1998 SAP Labs, Inc.

Introduction to Overtime Some Commonly Asked Questions

Some Commonly Asked Questions

On What is an R/3 Overtime Payment Based?

How is the Hourly Rate Calculated?

How is the Hours Threshold Determined?

How Can I Configure Overtime According to the FLSA Regulations?

1998 SAP Labs, Inc.

Introduction to Overtime Some Commonly Asked Questions

What If There Are Different Workweek Definitions?

1998 SAP Labs, Inc.

Generating Overtime in the System Overview

Chapter 1: Generating Overtime in the System

Automatic Overtime Generation

Manual Data Entry

1998 SAP Labs, Inc.

Generating Overtime in the System Manual Data Entry

1998 SAP Labs, Inc.

Schemas and RulesThe Basics Overview

Chapter 2: Schemas and RulesThe Basics

The Payroll Calculation Program

1998 SAP Labs, Inc.

Schemas and RulesThe Basics Schemas

When running RPCALCU0, the following selection screen appears:

1998 SAP Labs, Inc.

Schemas and RulesThe Basics Schemas

1998 SAP Labs, Inc.

Schemas and RulesThe Basics Schemas

1998 SAP Labs, Inc.

Schemas and RulesThe Basics Accessing Schemas and Rules

Accessing Schemas and Rules

Accessing Help When Looking at the Source Text

Schemas and Rules Documentation (RPDSYS00)

1998 SAP Labs, Inc.

Schemas and RulesThe Basics Schema Functions

These functions are discussed in detail in the next sections.

1998 SAP Labs, Inc.

Schemas and RulesThe Basics Schema Functions

Accessing Rules Using Functions PIT and PORT

1998 SAP Labs, Inc.

Schemas and RulesThe Basics Schema Functions

1998 SAP Labs, Inc.

Schemas and RulesThe Basics Schema Functions

1998 SAP Labs, Inc.

Schemas and RulesThe Basics Schema Functions

1998 SAP Labs, Inc.

Schemas and RulesThe Basics Schema Functions

Accessing Different Rule Variants

1998 SAP Labs, Inc.

4. Once you are in a variant, click

to scroll between variants.

Grouping Using Rule Variants