SAP India
HR400 Payroll Configuration
HR400
Payroll Configuration

SAP AG 1999
n R/3
n Release 4.6B
n June 2000
n 50036639
SAP AG
HR400 (4.6B) Payroll Configuration
0-7
SAP India
Copyright
Copyright 2000 SAP AG. All rights reserved.
Neither this training manual nor any part thereof may
be copied or reproduced in any form or by any means,
or translated into another language, without the prior
consent of SAP AG. The information contained in this
document is subject to change and supplement without prior
notice.
All rights reserved.
 SAP AG 1999
SAP AG
HR400 (4.6B) Payroll Configuration
0-7
SAP India
Trademarks:
n Microsoft ®, Windows ®, NT ®, PowerPoint ®, WinWord ®, Excel ®, Project ®, SQL-Server ®,
Multimedia Viewer ®, Video for Windows ®, Internet Explorer ®, NetShow ®, and HTML Help
® are registered trademarks of Microsoft Corporation.
n Lotus ScreenCam ® is a registered trademark of Lotus Development Corporation.
n Vivo ® and VivoActive ® are registered trademarks of RealNetworks, Inc.
n ARIS Toolset ® is a registered Trademark of IDS Prof. Scheer GmbH, Saarbrücken
n Adobe ® and Acrobat ® are registered trademarks of Adobe Systems Inc.
n TouchSend Index ® is a registered trademark of TouchSend Corporation.
n Visio ® is a registered trademark of Visio Corporation.
n IBM ®, OS/2 ®, DB2/6000 ® and AIX ® are a registered trademark of IBM Corporation.
n Indeo ® is a registered trademark of Intel Corporation.
n Netscape Navigator ®, and Netscape Communicator ® are registered trademarks of Netscape
Communications, Inc.
n OSF/Motif ® is a registered trademark of Open Software Foundation.
n ORACLE ® is a registered trademark of ORACLE Corporation, California, USA.
n INFORMIX ®-OnLine for SAP is a registered trademark of Informix Software Incorporated.
n UNIX ® and X/Open ® are registered trademarks of SCO Santa Cruz Operation.
n ADABAS ® is a registered trademark of Software AG
n The following are trademarks or registered trademarks of SAP AG; ABAP/4, InterSAP, RIVA, R/2,
R/3, R/3 Retail, SAP (Word), SAPaccess, SAPfile, SAPfind, SAPmail, SAPoffice, SAPscript,
SAPtime, SAPtronic, SAP-EDI, SAP EarlyWatch, SAP ArchiveLink, SAP Business Workflow,
and ALE/WEB. The SAP logo and all other SAP products, services, logos, or brand names
included herein are also trademarks or registered trademarks of SAP AG.
n Other products, services, logos, or brand names included herein are trademarks or registered
trademarks of their respective owners.
SAP AG
HR400 (4.6B) Payroll Configuration
0-7
SAP India
Human Resources 4.6 (1)
Level 2
HR505
3 days
Organizational
Management
Level 3
HR510
Personnel
Development
HR305
3 days
Configuration of
Master Data
HR315
3 days
Recruitment
HR050
5 days
Human Resources
HR306
AC270
3 days
Travel Management
Travel Expenses
see
HR2
HR540
3 days
Compensation
Management
HR325
3 days
Benefits
Administration
HR580
Reporting in
HR
HR250
3 days
Configuration of Time
Recording
3 days
3 days
Employee Self Service
3 days
HR515
3 days
Training and Event
Management
HR310/311
5 days
Time Evaluation
HR307
2 days
Configuration of HR
System Controls
HR350
5 days
Programming in HR
HR530
3 days
Technical Topics in
Human Resources
CA500
2 days
CATS The Cross
Application Time Sheet
 SAP AG 1999
SAP AG
HR400 (4.6B) Payroll Configuration
0-7
SAP India
Human Resources 4.6 (2)
Level 2
Level 3
HR305
Configuration of
Master Data
3 days
HR390
2 days
Introduction
to Payroll
HR400
5 days
Payroll Configuration
HR050
5 days
Human Resources
HR4xx
3 days
Country-Specific
Payroll
HR7xx
2 days
Payroll Reporting
(Country-Specific)
 SAP AG 1999
SAP AG
HR400 (4.6B) Payroll Configuration
0-7
SAP India
Course Prerequisites
l HR050 - Human Resources
l HR305 - Configuration of Master Data
l HR306 - Configuration of Time Recording
l HR390 - Introduction to Payroll

SAP AG
SAP AG 1999
HR400 (4.6B) Payroll Configuration
0-7
SAP India
Target Group
l Audience
n
Project team members responsible for Customizing
and supporting payroll.
l Duration: 5 days


SAP AG 1999
SAP AG
Notes to the user
n The training materials are not teach-yourself programs . They complement the course
instructor's explanations . Your material includes space for noting down this additional
information.
n There may not be enough time to do all the exercises during the course. The exercises are intended
to be additional examples that are dealt with during the course. Participants can also use them to
deepen their knowledge after the course.
SAP AG
HR400 (4.6B) Payroll Configuration
0-7
Course Overview
Contents:
l Course goal
l Course objectives
l Course content
l Course overview diagram
l Main business scenario
 SAP AG 1999
© SAP AG
HR400
1-1
Course Goal
This course will prepare you to:
l Modify HR Payroll to the specific
requirements of your enterprise.
 SAP AG 1999
© SAP AG
HR400
1-2
Course Objectives
At the conclusion of this course, you will be able to:
l Use the IMG to make changes in the schema and
personnel calculation rules so that you can modify
wage type valuation, the processing of absences
and averages, time wage type generation, factoring
and the formation of cumulation wage types to meet
your company’s requirements.
 SAP AG 1999
© SAP AG
HR400
1-3
Course Contents
Preface
Unit 1
Course Overview
Unit 7 Time Wage Type Selection
Unit 2
Payroll Basics
Unit 8 Averages
Unit 3
Personnel Calculation
Rules
Unit 9 Factoring
Unit 4
Starting Payroll
Unit 5
Wage Type Valuation
Unit 6
Absence Valuation
Unit 10 Cumulation Wage Types
Unit 11 Retroactive Accounting
Appendix
Exercises
Solutions
 SAP AG 1999
© SAP AG
HR400
1-4
Course Overview Diagram
Payroll Basics
Time Wage Type Selection
Personnel Calculation Rules
Averages
Starting Payroll
Factoring
Wage Type Valuation
Cumulation Wage Types
Absence Valuation
Retroactive Accounting
 SAP AG 1999
© SAP AG
HR400
1-5
Main Business Scenario
l Your company, the Caliber ‘A’ Bicycle Company,
is implementing HR Payroll.
l As a member of the project team, you have
to map the specific payroll requirements of
your company in the HR system.
 SAP AG 1999
© SAP AG
HR400
1-6
Payroll Basics
Contents:
l Payroll Steps
l Wage Types in Payroll
l The SAP Payroll Concept
l Payroll Schema X000
l Main Schema and Subschemas
l Functions and What They Do
l The Schema Editor
l Functions and Personnel Calculation Rules
 SAP AG 1999
© SAP AG
HR400
2-1
Payroll Basics: Unit Objectives
At the conclusion of this unit, you will be able to:
l Identify wage types as an essential part of
payroll
l Describe the SAP payroll concept and its
advantages
l Define payroll control using the process
schema and functions
l Explain why some functions require personnel
calculation rules to process wage types
l Use the schema editor
 SAP AG 1999
© SAP AG
HR400
2-2
Course Overview Diagram
Payroll Basics
Time Wage Type Selection
Personnel Calculation Rules
Averages
Starting Payroll
Factoring
Wage Type Valuation
Cumulation Wage Types
Absence Valuation
Retroactive Accounting
 SAP AG 1999
© SAP AG
HR400
2-3
Remuneration Structure
Periodic remuneration
Basic remuneration
(fixed parts)
Basic pay
Bonuses
Time compensation
(variable parts)
Bonuses for overtime, night work,
Sunday and public holiday work based
on planned working time and overtime
Time compensation
(variable parts)
Pnnnn
Wage type
Pnnnn
Amount
Wage
type
P0014
Recurring
Amount
P0008 Basic
PayNumber/Unit
Wage typeNumber/Unit
Wage type
Amount
Number/Unit
Amount
Number/Unit
Pnnnn
P2010
Wage
Employee
type
AmountInfo.
Remuneration
Wage typeNumber/Unit
Number/Unit
(Amount)
Automatic
generation
during the
payroll run
 SAP AG 1999
n The elements of an employee’s periodic remuneration are either entered by the relevant department
or are created by the payroll program using specific prerequisites as a basis.
© SAP AG
HR400
2-4
Wage Type Information
Assignment
to employee
groupings
Assignment
to Cost
Accounting
Name
What information
do wage types
contain?
Assignment
to absences
Assignment
to a particular
part of the
payroll period
Characteristics
determining payroll
processing
Value fields:
Number, rate,
amount
 SAP AG 1999
n Wage types form an essential part of payroll. A wage type consists of several fields containing
various information.
© SAP AG
HR400
2-5
Wage Type Elements
Work
center
basic
pay
Amount
per
unit
RATE
WPBP-Split
RTE
01
15.00
01
20.00
Number
Amount
NUMBER
AMOUNT
NUM
AMT
Examples:
- Hourly wage
3
60.00
- Time wage type:
- Salary
01
4,500.00
Partial period 01
02
5,000.00
Partial period 02
 SAP AG 1999
n Each wage type is assigned to a work center/basic pay period. If, for example, an employee's pay
changes within a payroll period, then the period is split into partial periods, and the wage types are
assigned to these partial periods.
n Furthermore, each wage type contains three value fields :
n The RTE field specifies, for example, the hourly rate used for hourly wage types.
n With time wage types, the NUM field initially specifies three hours overtime, for example. To
determine the time wage type amount, the system multiplies the number by the rate, and stores the
result in the AMT field. The rate for time wage types is calculated according to the conditions
defined in Customizing.
n With basic pay wage types, such as salary, the amount is stored in the AMT field.
© SAP AG
HR400
2-6
Validity Period of Wage Type Characteristics
Example
Subject to tax
Tax-free
1997
1998
1999
 SAP AG 1999
n Each wage type contains a sequence of time-dependent characteristics that determine how the wage
type is treated during the payroll run. The characteristics that are stored enable you to control how
wage types are processed during payroll.
n If wage type characteristics change, it does not suffice to simply change the corresponding table
entries. Instead, the validity periods of existing entries must be delimited, and new entries created
with the characteristics required in the future.
n If you change the wage type characteristics of a previous payroll period, you must correct all
subsequent payroll results. As the system does not automatically recognize such changes, you must
force retroactive accounting runs for the relevant employees and payroll periods.
© SAP AG
HR400
2-7
Wage Type Coding
1. Primary wage types
2. Secondary wage types
- Dialog wage types
- Time wage types
- Others: Absences
- Valuation bases
/0..
- Gross cumulation
/1..
- Average bases
/2..
- Factoring / CO
/8..
- Outgoing wage types in
retroactive acc. period
/A..
- Incoming wage types
from previous period
/Z..
- Others:
- Result wage types: Tax
- Result wage types: SI
/3..
/4..
 SAP AG 1999
n Primary wage types are either entered into the system directly by the user (for example, dialog
wage types for basic pay) or generated by the system based on time data (for example, time wage
types for overtime).
n During the payroll run, the payroll program creates secondary wage types. For example, all
amounts to be paid are cumulated into the secondary wage type Total Gross (/101) during the run.
SAP delivers secondary wage types identified by a name starting with /.
n You can create customer wage types in the above name range. Note that many secondary wage
types have a fixed meaning and that you must therefore not change the name.
n You can create customer wage types by copying and modifying non-technical wage types.
© SAP AG
HR400
2-8
Payroll Processes
1.
1.
Read basic data
2.
2.
Read payroll accounts from the payroll
period last accounted
3.
3.
Time data processing
- Read time data
- Generate time wage types
- Valuate time wage types
4.
4.
Import additional payments/deductions
5.
5.
Factoring
- Reduce basic pay
- Determine wage types for FI/CO
6.
6.
Statutory payments/deductions
7.
7.
Net payments/deductions
8.
8.
Determine payment amount
 SAP AG 1999
n The customer largely defines the first phase of processing.
n The second phase involving statutory payments and deductions rarely requires customer
adjustments.
© SAP AG
HR400
2-9
The SAP Payroll Concept
Payroll driver
Schema
Function
Personnel calculation rule
Operations
Function module
Operation module
SAP
Customizing
tables
Customer (IMG)
 SAP AG 1999
n A customer-defined schema and the functions included in that schema affect flow control in the
payroll driver. A function calls the function module assigned to it in the payroll driver. Certain
functions also call personnel calculation rules containing operations that are linked to operation
modules in the payroll driver.
n During the payroll run, function and operation modules access entries stored in Customizing tables.
© SAP AG
HR400
2-10
International Payroll Schema X000
Payroll schema:
INTERNATIONAL Gross wage calculation
and transfer
XIN0
Initialization of payroll
XBD0
Edit basic data
XLR0
Import last payroll results
XT00
Process time data for Payroll
XAP9
Import additional payments/deductions
XAL9
Partial period factoring and storage
XNA9
Cumulate net amount/form payment amount
XRR0
Retroactive accounting
XNN0
Net payments/deductions and transfers
XEND
Final processing
 SAP AG 1999
n To run the payroll program, you require a payroll driver and a payroll schema. The payroll schema
defines the processes carried out by the payroll driver and ensures that the program gathers all the
data required to run payroll for an employee in a specified period.
© SAP AG
HR400
2-11
Main Schema and Subschemas
COM
Payroll Schema:
COM
INTERNATIONAL
Gross wage calculation
COM
and transfer
COPY
XIN0
Initialization of payroll
COPY
XBD0
Edit basic data
COPY
XLR0
Import last payroll results
COPY
XT 00
Process time data for Payroll
COPY
XAP9
Import additional payments/deductions
COPY
XAL9
Partial period factoring and storage
COPY
XNA9
Cumulate net amount/form payment amount
COPY
XRR0
Retroactive accounting
COPY
XNN0
Net payments/deductions and transfers
COPY
XEND
Final processing
Functions
COM
BLOCK
ENAME
WPBP
GON
BLOCK
Basic data INTERNATIONAL
BEG
END
Edit basic data
Determine name of EE
Read work center/basic pay data
Continue with complete data
Edit basic data
 SAP AG 1999
n A main schema consists of a sequence of subschemas that are included in the main schema using
the COPY function. The main schema is generated and subsequently executed by the payroll
driver.
n Subschemas can be edited separately in Customizing, yet they are not executable unless
incorporated into a main schema.
n A schema consists of a sequence of functions . Functions retrieve and process the data required for
each processing step.
© SAP AG
HR400
2-12
Function Types and Examples
Functions that import infotype data:
WPBP
Work center and basic pay data
RAB
Absences
P0015
Additional payments
P2010
EE remuneration information
Functions that process data according to the entries
in Customizing tables:
PAB
Absence valuation
Functions that edit wage types using personnel
calculation rules:
PIT
Process input table
 SAP AG 1999
n You can display documentation on a function by pressing F1.
n Functions within a schema are processed sequentially.
n Data processing for employee wage types takes place in internal payroll tables. To process such
data, certain functions access an assigned personnel calculation rule that can be adjusted if
necessary.
© SAP AG
HR400
2-13
Maintaining Schemas
Schema
Create
Source text
Attributes
Documentation
Display
Change
 SAP AG 1999
n The schema editor (transaction PE01) enables you to display and maintain schemas.
n When displaying a source text, you can choose between tables and structural graphics.
n The personnel calculation schema editor enables you to carry out the following activities:
•
Display and print schema directory
•
Compare source text from schemas
•
Copy schemas
•
Change schema ele ments
•
Create schemas
•
Check the syntax of source text in schemas
•
Generate modified or new source text
•
Transport schemas to another client
•
Navigate within and between schema elements
•
Navigate between schemas
•
Access personnel calculation rules
© SAP AG
HR400
2-14
Schema Attributes
Attributes
Program class
C Payroll
T Time Management
Country grouping
*, 01, 02, ... 99
û
Executable schema
Person responsible
û
Changes by person responsible only
Administrative data
Created on
Last changed by
Version
_
_
_
on _
at _
 SAP AG 1999
n Attributes store administrative data on schemas.
n The program class determines how the schema is used (C = Payroll, T = Time Management).
n The HR country grouping defines the country versions for which the schema is valid.
n If you flag Changes by person responsible only, the schema elements (source text, attributes,
documentation) can only be changed by the person responsible for them.
n You do not require special authorization to generate a schema.
n A person other than the person responsible can execute a schema. Each function checks the
authorizations set up in HR.
© SAP AG
HR400
2-15
The Schema Editor
1
Fct
Par1 Par2 Par3 Par4
1 Command line
D Text
2 Line number
000010
000020
000030
000040
000050
3 Function
4 Parameters 1 - 4
5 Execute function
2
3
4
5
6
6 Text
 SAP AG 1999
n In areas 1 and 2 of the editor, you can use the standard SAP commands.
n Area 3 of the editor specifies the schema's functions. The four parameters in area 4 provide more
exact definitions of the functions.
n Placing an asterisk in area 5 deactivates the relevant function.
n You can enter a description of each function in area 6.
© SAP AG
HR400
2-16
Displaying Schemas as Structural Graphics
X000
+
XIN0
-
XBD0
Initialization of payroll
Edit basic data
Basic data
International
COM
-
Edit basic data
ENAME
WPBP
P0052
GON
 SAP AG 1999
n To expand the sub-tree, click the plus sign, and to collapse the sub-tree, click the minus sign.
n If the function and parameter fields are not displayed in color, this indicates that the function has
been deactivated.
n Where a function calls a personnel calculation rule, you can call the personnel calculation rule by
double-clicking the name of the rule (in the first parameter field).
n Schemas can be viewed in structural graphics, but cannot be edited in this view.
© SAP AG
HR400
2-17
Functions and Personnel Calculation Rules
COM
Payroll schema:
INTERNATIONAL
COM
Gross wage calculation
COM
and transfer
Parameters
COPY
XIN0
Initialization of payroll
COPY
XBD0
Edit basic data
COPY
XLR0
Import last payroll result
COPY
XT 00
Gross remuneration (Time Management)
…
...
BLOCK
COM
IMPRT
PRINT
PORT
ACTIO
BLOCK
BEG
L
NP
ORT
X006 P06 NOAB
X402
END
Import last payroll result
Last payroll results
Import last result
Print ORT after import
Transfer relevant data to LRT
Processing /A67
Import last payroll result
Personnel calculation rule X006
Operation
Operation
Operation
 SAP AG 1999
n A schema consists of a sequence of functions . Functions retrieve and process the data required for
each processing step.
n Certain functions call a personnel calculation rule . The relevant calculation rule processes the data
retrieved by functions. A personnel calculation rule consists of separate operations and always
processes logical units.
n Personnel calculation rules therefore fine-tune processes carried out by functions.
© SAP AG
HR400
2-18
Payroll Basics: Summary
l You are now familiar with the main processing
steps in Payroll.
l You have learned that the payroll program is
controlled by functions in a process schema.
l You know that wage types are an essential
part of payroll and that personnel calculation
rules assist in processing wage types.
 SAP AG 1999
© SAP AG
HR400
2-19
Exercise Data Sheet
Key to Icons in the Exercises and Solutions
Exercises
Solutions
Objectives
Business Scenario
Hints and Tips
Warning or Caution
Data used in Exercises
Type of Data
Data in Training System
Data in EDES
System
Payroll Area
X1 – X9 (Groups 01 – 09)
X0
Y0 – Y9 (Groups 10 – 19)
Wage Types:
Salary
10nn (nn = Group number)
Bad Weather Bonus
20nn
Overtime up to 2 hours 3nn1
Overtime after 2 hours
3nn2
Overtime Sunday
3nn3
Overtime Public
Holiday
3nn4
Bonus 25%
3nn5
Bonus 50%
3nn6
Bonus 75%
Bonus 100%
3nn7
3nn8
Vacation Bonus
40nn
Bonus
50nn
Instructor’s Bonus
60nn
© SAP AG
HR400
2-20
Exercises
Unit: Payroll Basics
Topic: Hiring an Employee
• Hiring an employee.
1.
Your employee enters the company on January 01 of the current year.
Carry out the personnel action 'Hiring HR400' using the following data for the
respective infotypes. You can skip infotypes for which no data is given.
Personnel number:
Personnel area:
Employee grouping
Employee subgroup:
22nn
(nn = group number.)
CABB
1
X0
Infotype Organizational Assignment:
Payroll area:
X1 to X9 for groups 01 - 09,
Y0 to Y9 for groups 10 - 19
Position:
Default
(Note: Cancel the position assignment)
Infotype Address:
any data
Infotype Working time:
Work schedule rule:
FLEX
Time Management status: 0
Infotype Basic pay:
Pay scale type:
Pay scale area:
Pay scale group:
Wage type:
01
01
E03
M020 (salary valuated indirectly)
In addition, create infotypes Bank details, Contract elements, and Absence quota
(Type 09, validity period, current calendar).
2.
Release payroll for the period 01, run payroll for your new employee and look at the
results table.
© SAP AG
HR400
2-21
Unit: Payroll Basics
Topics: Schema Editor, Main Schema, Subschemas
• Creating customer main and subschemas.
To adjust payroll to meet your company's requirements, you must
modify the payroll schema. To do this, you copy and rename the original
payroll schema, and make the changes required.
Make a copy of subschema XT00, and rename it ZTnn. Then make a copy of the international
payroll schema X000, and rename it Z0 nn (nn = group number).
© SAP AG
HR400
2-22
Solutions
Unit: Payroll Basics
Topic: Hiring an Employee
1.
Carry out the personnel action ‘Hiring HR400’:
Human Resources à Personnel Management à Administration à HR Master
Data → PA40 - Personnel Actions
2.
Run payroll for your new employee:
Human Resources à Payroll à International à Payroll à Release Payroll
Human Resources à Payroll à International à Payroll à Start Payroll
© SAP AG
HR400
2-23
Unit: Payroll Basics
Topics: Schema Editor, Main Schema, Subschemas
Copy subschema XT00 and schema X000:
Human Resources à Payroll à International à Tools à Maintenance Tools à Schema
à Copy
From schema
To schema
XT00
ZTnn
and
From schema
To schema
© SAP AG
X000
Z000.
HR400
2-24
Personnel Calculation Rules
Contents:
l Employee Subgroup Groupings for
Personnel Calculation Rules
l Rule Access Variants
l Maintaining Personnel Calculation Rules
 SAP AG 1999
© SAP AG
HR400
3-1
Personnel Calculation Rules: Unit Objectives
At the conclusion of this unit, you will be able to:
l Explain why personnel calculation rules must
process certain employee groupings differently.
l Describe how internal tables interact during
payroll.
l Use various methods of accessing personnel
calculation rules from the schema.
l Maintain personnel calculation rules using
structural graphics.
 SAP AG 1999
© SAP AG
HR400
3-2
Course Overview Diagram
Payroll Basics
Time Wage Type Selection
Personnel Calculation Rules
Averages
Starting Payroll
Factoring
Wage Type Valuation
Cumulation Wage Types
Absence Valuation
Retroactive Accounting
 SAP AG 1999
© SAP AG
HR400
3-3
Employee Subgroup Groupings
EE subgroup
groupings
for personnel
calc.rule
Personnel calculation rule Xnnn
Rule: Xnnn EE subgroup grpg: 1 Wage type: ****
Hourly wage
earners
Operations
1
Rule: Xnnn EE subgroup grpg: 2 Wage type: ****
2
Operations
Period wage
earner
Rule: Xnnn EE subgroup grpg: 3 Wage type: ****
3
Operations
Salaried
employee
 SAP AG 1999
n Personnel calculation rules for wage types are usually configured to perform various processes. For
example, wage types for hourly wage earners are processed differently than wage types for monthly
wage earners or salaried employees.
n To facilitate differential processing, each employee subgroup must be assigned to a grouping for a
personnel calculation rule. Each grouping is defined by SAP and, in this case, can have its own area
depending on the personnel calculation rule.
© SAP AG
HR400
3-4
Personnel Calculation Rules: Example 1
Personnel calculation rule Xnnn
Rule: Xnnn EE subgroup grpg: 1 Wage type: ****
Hourly wage + bonuses per hour
= hourly rate for overtime
Calculation of hourly rate
Rule: Xnnn EE subgroup grpg: 2 Wage type: ****
(Wage + bonuses) per period
/ working hours per payroll period
= hourly rate for overtime
 SAP AG 1999
n The hourly rate for overtime is subject to different methods of calculation (valuation basis)
depending on whether the employee is a period wage earner, a salaried employee or an hourly wage
earner.
n For employees with periodic remuneration, the hourly rate is calculated by dividing the
remuneration elements by the number of working hours per period specified in the Basic Pay
infotype.
© SAP AG
HR400
3-5
Personnel Calculation Rules: Example 2
Personnel calculation rule Xnnn
Factor 1
Rule: Xnnn ES Grpg: *
Wage type: nnn1
Factor = (Planned working time - unpaid absence)
Period Working Time
Calculation of reduction factor
for absences
Rule: Xnnn ES grouping: * Wage type: nnn2
Factor = (Planned working time - unpaid absence - paid absence)
Period Working Time
Factor 2
 SAP AG 1999
n Reduction factors are stored in diverse wage types and are used in payroll to calculate the reduction
in pay for absences. A personnel calculation rule can contain several calculation formulas
depending on the definition and use of the rule. Each formula is accessed exactly for the relevant
wage type.
n The factors stored in the wage types are used to reduce periodic remuneration for unpaid absences,
for example.
© SAP AG
HR400
3-6
Interaction Between the Most Important Internal
Payroll Tables with Function PIT
Payroll rule
INPUT
TABLE
OPERATIONS
OUTPUT
TABLE
- Wage types
-
RESULT
TABLE
 SAP AG 1999
n Internal table IT contains the wage types required for the relevant processing step.
n The results of a processing step are either stored in internal table OT or RT.
n Upon completion of a processing step, the wage types are transferred from internal table OT to
internal table IT.
n Internal tables IT and OT are filled temporarily and only exist during the payroll run, whereas
internal table RT is stored on the database.
© SAP AG
HR400
3-7
Rule Access Using Groupings
Table IT
Schema X000
…
3
M020
3,000
PIT
...
Xnnn
GEN
____
Personnel calculation rule Xnnn
Rule: Xnnn EE subgroup grpg: 1 Wage type: ****
Operations
Rule: Xnnn EE subgroup grpg: 2 Wage type: ****
Operations
Rule: Xnnn EE subgroup grpg: 3 Wage type: ****
Operations
 SAP AG 1999
n Function PIT (Process Input Table ) processes each wage type stored in internal table IT
generically by accessing the personnel calculation rule defined in the first parameter through the
employee subgroup grouping for personnel calculation rules.
n Example:
The rule access is used in subschema XT00 to access personnel calculation rule X015.
© SAP AG
HR400
3-8
Generic Rule Access
Table IT
Schema X000
…
3
M020
3,000
PIT
...
Xnnn
GEN
NOAB
Personnel calculation rule Xnnn
Rule: Xnnn ES grouping: *
Wage type: ****
Operations
 SAP AG 1999
n Function PIT (Process Input Table ) generically accesses the personnel calculation rule defined in
the first parameter for each wage type stored in internal table IT When doing so, the employee
subgroup grouping for personnel calculation rules in the wage type is not taken into account.
n Example:
The rule access is used in subschema XEND to access personnel calculation rule X070.
© SAP AG
HR400
3-9
Rule Access Using Processing Classes
Table IT
Schema X000
…
3
M020
3,000
PIT
...
Xnnn
P01
____
M020
Personnel calculation rule Xnnn
Rule: Xnnn EE subgroup grpg: 2 Wage type: ****
Operations
Processing class
specification
01
Rule: Xnnn EE subgroup grpg: 3 Wage type: ****
Processing class 01?
0
Operations
1
Operations
02
2
Operations
03
0
1
2
3
5
...
...
...
 SAP AG 1999
n Function PIT (Process Input Table ) processes each wage type stored in internal table IT by
reading the processing class defined in the second parameter and determining the specification of
the processing class.
n Example:
The rule access is used in subschema XT00 to access personnel calculation rule X013.
© SAP AG
HR400
3-10
Rule Access Using Wage Types
Table IT
Schema X000
…
*
*
nnn1
nnn2
PIT
...
Xnnn
____
NOAB
Personnel calculation rule Xnnn
Rule: Xnnn ES Grpg: * Wage type: nnn1
Operations
Rule: Xnnn ES grouping: * Wage type: nnn2
Operations
Rule: Xnnn ES grouping : * Wage type: nnn3
Operations
 SAP AG 1999
n Function PIT (Process Input Table ) processes each wage type stored in internal table IT by
accessing the personnel calculation rule defined in the first parameter. When doing so, the
employee subgroup grouping for personnel calculation rules in the wage type is not taken into
account. If there is no processing for the wage type in the personnel calculation rule, the wage type
is written to table OT without being changed.
n Example:
In subschema XAL9, the personnel calculation rule XPPF is accessed in this way.
© SAP AG
HR400
3-11
Rule Access Variants
Function
PIT
Parameter 1
Rule
Parameter 2
NOAB
GEN
Pnn
NOAB
NOAB
Parameter 3
 SAP AG 1999
n This overview show the six rule access variants. The four most common variants are marked.
n Further functions used to edit wage types stored in internal tables are PLRT, PORT, PDT, PRT,
and PZL. The personnel calculation rules are accessed using the same parameters as function PIT.
n In parameter 2, you enter the type of rule access. The wage types to be processed can be specified
using processing classes (Pnn). The rule can be accessed generically (GEN); that is, all the wage
types in the table are processed in the payroll rule. If parameter 2 is empty, the personnel
calculation rule is accessed for the wage type being processed.
n If you have not differentiated for employee subgroup groupings in a customer personnel calculation
rule, you must call the rule using NOAB in parameter 3.
© SAP AG
HR400
3-12
Maintaining Personnel Calculation Rules
Rule
Create
Source text
ES grouping
Wage/time type
Attributes
Documentation
Display
Change
 SAP AG 1999
n The personnel calculation rule editor enables you to display and maintain personnel calculation
rules. You can access the editor under the Tools in the Payroll menu (transaction PE02).
n Personnel calculation rules are processed according to the employee subgroup grouping and the
wage type.
© SAP AG
HR400
3-13
Rule Attributes
Attributes
Program class
C Payroll
T Time Management
Country grouping
*, 01, 02, ... 99
Person responsible
û
Changes by person responsible only
Administrative data
Created on
Last changed by
Version
_
_
_
on _
at _
 SAP AG 1999
n Personnel calculation rules are assigned by their attributes to a program class; that is, they are used
either in Payroll or Time Management.
n The responsibility for maintenance can be assigned to an employee. In this case, all other
employees are only able to display the rule.
n The administrative data tells you when the personnel calculation rule was created, the date and time
when the last change was made, and the name of the person who made the last change.
© SAP AG
HR400
3-14
Displaying Rules as Structural Graphics
X006
Import relevant wage types to LRT
E
Employee subgroup
grouping for personnel
calculation rule
*
E
****
E
WT
VWTCL 06
E
Processing class
*
ERROR
Cancel processing
0
E
Specification
of processing
class
1
ADDWTL *
E
2
LRTST Y
ADDWTL *
 SAP AG 1999
n Structural graphics display the source text as lines and nodes linked in a hierarchical structure. You
can display and change source text in this mode.
n The source text elements and decision operations are color-coded. Decision operations are
displayed in a color different to the one used for the other operations.
© SAP AG
HR400
3-15
Personnel Calculation Rules: Summary
l Personnel calculation rules enable you to
process wage types according to employee
groupings and wage types.
l There are different ways of accessing
personnel calculation rules within a schema
to select the required processing.
 SAP AG 1999
© SAP AG
HR400
3-16
Exercises
Unit: Personnel Calculation Rules
Topic: Functions for Processing Internal Payroll Tables
• Practicing various methods of accessing customer personnel
calculation rules.
To adjust payroll to meet your company's requirements, you will usually
require customer-specific personnel calculation rules to edit wage types
in diverse payroll tables.
Note: This exercise does not require you to carry out any activities in the
system. Write the name of the access on this page.
1.
You want to process table IT using personnel calculation rule Z001. You should access
the rule by means of the employee subgroup grouping for personnel calculation rules,
and not by means of the wage type.
___________
2.
___________
___________
___________
___________
___________
___________
You want to process table RT using personnel calculation rule ZEND. You should
access the rule without using the wage type or the employee subgroup grouping for
personnel calculation rules.
___________
5.
___________
You want to process table IT using personnel calculation rule Z010. You should access
the rule by means of the employee subgroup grouping for personnel calculation rules,
and the specification in processing class 99.
___________
4.
___________
You want to process table ORT using personnel calculation rule ZORT. You should
access the rule by means of the wage type, and not by means of the employee subgroup
grouping for personnel calculation rules.
___________
3.
___________
___________
___________
___________
You only want to process wage type 4711 in table IT in the same way for all employees
using personnel calculation rule Z123.
___________
© SAP AG
___________
___________
HR400
___________
3-17
Unit: Personnel Calculation Rules
Topic: Creating Personnel Calculation Rules
• Creating customer personnel calculation rules, and accessing the rules
from the schema.
To adjust payroll to meet your company's requirements, you will usually
require customer personnel calculation rules to edit wage types in
diverse payroll tables. To access these rules, you must adjust the schema
accordingly.
1.
Make a copy of personnel calculation rule XMOD, and rename your copy ZM nn. In
subschema ZTnn, go to function MOD and change parameter 1 so that personnel
calculation rule ZM nn is accessed.
2.
Change your international payroll schema Z0 nn so that it copies the modified
subschema ZTnn instead of the standard schema XT00.
Check the schema. If it contains no errors, save it .
© SAP AG
HR400
3-18
Solutions
Unit: Personnel Calculation Rules
Topic: Functions for Processing Internal Payroll Tables
Access:
PIT
Access:
PORT ZORT ___
Access:
PIT
Z010
Access:
PRT
ZEND GEN
NOAB
Access:
PIT
Z123
NOAB
© SAP AG
Z001
GEN
NOAB
P99
___
HR400
3-19
Unit: Personnel Calculation Rules
Topic: Creating Personnel Calculation Rules
1.
To copy personnel calculation rule XMOD, and change subschema ZTnn, go to:
Human Resources à Payroll à International à Tools à Maintenance Tools à
Calculation Rule à Copy
from rule
to rule
2.
XMOD
ZMnn.
Change payroll schema Z0nn:
Human Resources à Payroll à International à Tools à Maintenance Tools à
Schema. In your payroll schema Z0nn, change the line in which the partial schema
XT00 is copied to ZTnn.
© SAP AG
HR400
3-20
Starting Payroll
Contents:
l Initializing Payroll
l Checking the Personnel Control Record
l Importing Basic Data
l Work Center and Basic Pay Data
l WPBP Splits
l Data Completeness
 SAP AG 1999
© SAP AG
HR400
4-1
Starting Payroll: Unit Objectives
At the conclusion of this unit, you will be able to:
l Set the parameters for initializing the payroll
run in your live schema.
l Define the work center and basic pay data
set up at the start of payroll.
 SAP AG 1999
© SAP AG
HR400
4-2
Course Overview Diagram
Payroll Basics
Time Wage Type Selection
Personnel Calculation Rules
Averages
Starting Payroll
Factoring
Wage Type Valuation
Cumulation Wage Types
Absence Valuation
Retroactive Accounting
 SAP AG 1999
© SAP AG
HR400
4-3
Initializing Payroll
Abrechnungsschema:
Payroll
schema:
Initialisierung Abrechnung
Initialization
of payroll
XIN0
XIN0
COM
BLOCK
PGM
UPD
OPT
OPT
CHECK
BLOCK
INTERNATIONALE
und
INTERNATIONALBruttolohnfindung
Gross wage calculation
Überweisung
and transfer
BEG
ABR
YES
INFT
TIME
ABR
ABR ABR* *
END
*
Initialization INTERNATIONAL
Initialisierung
INTERNATIONAL
Initialisierungofder
Initialization
Payroll
Abrechnung
Programmtyp
Program
type for
Abrechnung
payroll
Datenbankupdates
Update
database (YES/NO)
durchführen (YES/NO)
nur verwendete
Read
used infotypes
Infotypen
only lesen
alle Zeitinfotypen
Import
all time infotypes
lesen
Prüfungagainst
Check
gegen PA03
PA03
Initialisierungofder
Initialization
Payroll
Abrechnung
 SAP AG 1999
n At the start of the payroll run, subschema XIN0 provides the payroll driver with the data required to
run the payroll program.
n Function PGM provides the payroll driver with data on the type of program the schema uses. The
different schemas allow the payroll driver to execute the functions of diverse programs run at
various times during processing. To execute the payroll program, the function must be set to
parameter ABR.
n Function UPD controls whether the payroll results are updated on the database or only available
during the payroll run. If the payroll driver has been set to test run, function UPD will not update
the database even when set to YES.
n Function OPT set to the parameter INFT ensures that only the infotypes required in the functions
within the schema are imported. The parameter TIME enables all time infotypes to be imported.
This function is designed to enhance performance.
© SAP AG
HR400
4-4
Checking the Personnel Control Record
Abrechnungsschema:
XIN0
.
. XIN0
CHECK
ABR
.
Initialization INTERNATIONAL
Check against PA03
Control record
Released for payroll
Released for correction
Exit payroll
Check payroll results
Payroll period
Run
10.1998
01
 SAP AG 1999
n Function CHECK set to parameter ABR ensures that:
•
Payroll is only run for the employees in a payroll area that has been released for payroll.
•
Payroll is not run for any employees with payroll results relating to the future.
n In a live payroll schema, function CHECK ABR must be activated. The function is deactivated by
setting the program to test run.
© SAP AG
HR400
4-5
Importing Basic Data
INTERNATIONAL Gross wage calculation
and transfer
COM
BLOCK
ENAME
WPBP
GON
BLOCK
BEG
END
XIN0
Initialization of payroll
XBD0
Edit basic data
XLR0
Import last payroll results
XT 00
Gross remuneration (Time Management)
XAP9
Import additional payments/deductions
XAL9
Partial period factoring and storage
XNA9
Cumulate net amount/form payment amount
XRR0
Retroactive Accounting
XNN0
Net payments/deductions and transfer
XEND
Final processing
Basic data INTERNATIONAL
Edit basic data
Determine name of EE
Read work center/basic pay data
Continue if data complete
Edit basic data
 SAP AG 1999
n Schema XBD0 is a subschema used to read the basic data that is essential to payroll.
© SAP AG
HR400
4-6
Reading Work Center / Basic Pay Data
IT 0000
IT 0001
IT 0007
IT 0008
IT 0027
Personnel
Actions
Org.
Assignment
Planned
Working
Time
Basic Pay
Cost
Distribution
WPBP
Table WPBP
Table IT
01 01.JUL.1999 31.JUL.1999
Action
Hiring
Personnel area
1000
Work schedule rule NORM
M020
01
3,000.-
...
...
 SAP AG 1999
n Function WPBP fills internal table WPBP with the master data, work center data and basic pay data
valid for the payroll period.
n Function WPBP also fills internal table IT with the basic pay wage types.
n This data usually remains the same for the entire payroll period.
© SAP AG
HR400
4-7
WPBP Splits
IT 0000
IT 0007
IT 0008
Personnel Actions
Planned Working Time
Basic Pay
01.JUL.1991 - 15.JUL.1999
16.JUL.1999 - 31.DEC.9999
01.JUL.1999 - 20.JUL.1999
21.JUL.1999 - 31.DEC.9999
01.JUL.1999 -15.JUL.1999
16.JUL.1999 - 31.DEC.9999
WPBP
Table WPBP
01 01.JUL.1999
Table IT
15.JUL.1999
Action
Hiring
Personnel area
1000
Work schedule rule NORM
02 16.JUL.1999
Action
03 21.JUL.1999
...
...
20.JUL.1999
M020
01
3,000.-
M020
02
3,500.-
M020
03
3,500.-
Change in pay
31.JUL.2000
Work schedule rule FLEX
 SAP AG 1999
n Various partial periods can contain different data. Where this is the case, the different entries are
assigned a split indicator in internal tables WPBP and IT.
n In this example, a new employee's basic pay and planned working time have been changed during
the payroll period. The system creates an entry in table WPBP for each partial period of the payroll
period.
n Similarly, table IT contains three entries for the same wage type except that the second and third
partial periods each specify the same amount.
© SAP AG
HR400
4-8
Data Completeness
GON
Is all the data
complete?
Payroll
 SAP AG 1999
n Function GON checks whether all the master data has been imported. Further processing of the
personnel calculation schema only occurs if certain data is available. Checking procedures vary
from country to country. However, there must always be a work center (IT 0007).
© SAP AG
HR400
4-9
Starting Payroll: Summary
l In a live schema, you must activate
the checking procedure for the personnel
control record.
l Work center and basic pay data for the
payroll period are stored in tables IT and
WPBP according to partial periods.
 SAP AG 1999
© SAP AG
HR400
4-10
Exercises
Unit: Starting Payroll
Topic: WPBP Splits
• Recognizing WPBP splits in the payroll results.
You have already hired and run payroll for your employee.
1.
Release your payroll area for correction.
2.
Midway through the payroll period, your employee receives a bonus in basic pay. In the
Basic Pay infotype, create a new record specifying wage type 50nn, and a bonus
amount of 300.00.
Release the payroll for payroll period 01, run payroll for your employee using payroll
schema Z0nn (nn = group number), and view the results in the results table. Exit the
payroll run.
Create a selection variant for the payroll driver to ensure that
the your schema Z0nn is used when you run payroll in the
following exercises.
© SAP AG
HR400
4-11
Solutions
Unit: Starting Payroll
Topic: WPBP Splits
1.
To release the payroll area for correction, choose:
Human Resources à Payroll à International à Payroll à Corrections
2.
To assign a bonus and run payroll again for your employee, choose:
Human Resources à Personnel Management à Administration à Maintain
Master Data
Human Resources à Payroll à International à
Release Payroll
Human Resources à Payroll à International à
Start Payroll
Human Resources à Payroll à International à
Payroll à Exit Payroll
Create selection variant for RPCALCX0:
Human Resources à Payroll à International à Payroll à Start payroll à Goto à
Variants à Save As Variant
© SAP AG
HR400
4-12
Wage Type Valuation
Contents:
l Wage Type-Dependent Constants
l Pay Scale-Dependent Constants
l Modifiers for Table Access
l Person-Related Valuation Bases
l Personnel Calculation Rules X010 and X013
l Assigning Valuation Bases
l Derived Wage Types
l Valuating Wage Types in the Schema
 SAP AG 1999
© SAP AG
HR400
5-1
Wage Type Valuation: Unit Objectives
At the conclusion of this unit, you will be able to:
l Valuate time wage types with fixed amounts
and, if necessary, according to organizational
units
l Valuate time wage types according to the
provisions in your collective agreement
l Valuate time wage types using a value derived
from the employee’s basic pay data
 SAP AG 1999
© SAP AG
HR400
5-2
Course Overview Diagram
Payroll Basics
Time Wage Type Selection
Personnel Calculation Rules
Averages
Starting Payroll
Factoring
Wage Type Valuation
Cumulation Wage Types
Absence Valuation
Retroactive Accounting
 SAP AG 1999
© SAP AG
HR400
5-3
Valuating Time Wage Types
e
Tim et
e
sh
 SAP AG 1999
n Overtime that is not recorded automatically, but entered on a time sheet, can be processed for
payroll in two ways:
1. The employee's working times are added up and entered as employee remuneration information
with certain wage types.
2. The exact days and hours of the employee's working times are recorded. This can occur
manually in the Overtime infotype (2005). The system then selects the correct time wage types
to be used in the payroll run.
n The system processes PDC (plant data collection/time evaluation data) automatically.
n In both cases, the wage types initially contain the number of hours overtime the employee has
worked. This figure is specified in the number field (NUM) to be multiplied by a payable amount.
Example:
The amount (AMT) of a time wage type is calculated by multiplying the number (NUM) of time
units by the valuation basis (RTE):
RTE * NUM = AMT
17.70 * 10 hrs = 177.00
The valuation basis is defined in Customizing.
© SAP AG
HR400
5-4
Valuation: Constant Remuneration (1)
l The Caliber ‘A’ Bicycle Company pays a constant
hourly rate that is the same for all employees.
 SAP AG 1999
© SAP AG
HR400
5-5
Wage Type-Dependent Constants (1)
Bad weather bonus
WType
…
4000
4000
5000
...
Start date
End date
Amount
01.JAN.1997
01.JAN.1999
01.JAN.1998
31.DEC.1998
31.DEC.9999
31.DEC.9999
10.00
12.00
20.00
 SAP AG 1999
n In payroll, a wage type can be valuated using a constant amount. The amount does not depend on
the employee's organizational assignment or on any other characteristics.
n Each wage type can have several entries denoting various validity periods.
© SAP AG
HR400
5-6
Valuation: Constant Remuneration (2)
l The Caliber ‘A’ Bicycle Company pays an
hourly bonus that is based on the employee’s
assignment to a pay scale level.
 SAP AG 1999
© SAP AG
HR400
5-7
Pay Scale-Dependent Constants
Collective
Agreement
- Hourly earners
- Monthly earners
- Salaried staff
Night work bonus
Entries per: - Pay scale type
- Pay scale area
EE SG Pay scale PS
Grpg group
level
…
3
3
...
GR04
GR04
01
02
WType
4010
4010
Start date
End date
01.JAN.1998 31.DEC.2000
01.JAN.1998 31.DEC.2000
Amount
10.00
12.00
 SAP AG 1999
n If wage types are subject to constant valuation depending on their pay scale level assignment, you
must define the values for each pay scale level assignment and wage type.
n Note the various employee subgroup groupings for collective agreement provisions specified when
the employee subgroups are defined.
© SAP AG
HR400
5-8
Valuation: Constant Remuneration (3)
l The Caliber ‘A’ Bicycle Company pays an hourly
bonus that varies depending on the
personnel area.

SAP AG 1999
© SAP AG
HR400
5-9
Modifiers for Table Access
Personnel area 1000
Key
01
Payroll
Personnel area 1100
Amount
01 4000
10.00
01 5000
20.00
..
02 4000
15.00
02 5000
22.00
..
02
 SAP AG 1999
n Elements of remuneration, such as bonuses, usually vary depending on the organizational unit.
n Example :
You want bonus wage type 4000 to be remunerated differently for employees in personnel area
1000 than for employees in personnel area 1100. To do this, the system uses a modifier as the first
key specified in the table. The default SAP value for modifiers is 01. The modifier for personnel
area 1100 is created in Customizing by copying modifier 01, renaming it 02, and entering the
relevant amount. During the payroll run, the system sets the modifier to the required value
according to the personnel area assigned to each personnel number.
© SAP AG
HR400
5-10
Personnel Calculation Rule XMOD
Employee grouping for payroll
XMOD
E
3
Using ES grouping 3 wage/
wage/time type
type ****
**** as
as an example
E
****
E
OUTWPPLANT
E
E
Personnel area
1000
MODIF A = 01
Table Absence valuation
MODIF 1 = 01
Table Wage type selection rule
MODIF 2 = 01
Table Constant wage type valuation
1100
MODIF A = 02
MODIF 1 = 02
MODIF 2 = 02
 SAP AG 1999
n In the payroll run, function MOD centrally assigns the modifiers described on the previous page
using personnel calculation rule XMOD.
n Decision operation OUTWP uses various parameters to define an employee's organizational
characteristics such as the company code and personnel area. Operation MODIF sets the modifiers
for table access. The parameters used for operation MODIF represent various tables.
© SAP AG
HR400
5-11
Wage Type-Dependent Constants (2)
Personnel area 1000
Dirty work bonus
Personnel area 1100
PayMo
WType
Start date
End date
Amount
…
01
02
...
4000
4000
01.01.1998
01.01.1998
31.12.2000
31.12.2000
10.00
15.00
 SAP AG 1999
n This represents a complete view of the table Wage type -dependent constants . If, as described in
the first scenario, the values are all the same, you can use the model SAP entries in the standard
system which have the payroll modifier (MODIF 2) set to value 01.
© SAP AG
HR400
5-12
Valuating Wage Types in the Schema (1)
XT00
.
.
.
.
MOD
XMOD
.
P2010 X930
.
.
PIT
X015
.
.
General processing of time data INTERN.
GEN
GEN
GEN
Determine payroll modifiers
NOAB
Edit employee remuneration information
Valuation of time wage types
 SAP AG 1999
n In subschema XT00, personnel calculation rule XMOD queries employee work center data and sets
modifiers that access the table for wage type-dependent constants.
n Function P2010 imports the bonuses for dirty work entered as employee remuneration information.
The wage types are then stored in internal table IT with the number of hours specified in the NUM
field. The RTE field remains empty.
n Valuation is performed in personnel calculation rule X015, which checks whether internal table IT
contains time wage types. If time wage types are found in table IT, the system performs the
valuation set up in Customizing.
© SAP AG
HR400
5-13
Valuation: Person-Related Remuneration (1)
l The Caliber ‘A’ Bicycle Company pays
overtime according to an employee’s
personal hourly rate.

SAP AG 1999
© SAP AG
HR400
5-14
Person-Related Valuation Bases
The valuation basis is
calculated using a basic
pay wage type:
6,000
500
Standard salary
Standard bonus
Voluntary bonus
yes
yes
no
2,700
300
6,000
Total pay
3,000
34.09
Divided by working hours per period (IT0008)
176 Hours
88 Hours
34.09
 SAP AG 1999
n The basis that is used to valuate person-related valuation bases is not a fixed constant, but an
employee-specific value calculated according to the employee's remuneration.
n The system flags the wage types used to calculate person-related valuation bases.
© SAP AG
HR400
5-15
Processing in Rule X010
Input
Processing in X010
Output
Table IT
3 M020
2,700
3 M230
300
Table OT
Amounts totaled
in wage types /0nn
3 M020
2,700
3 M230
300
3 /001
3,000
 SAP AG 1999
n Personnel calculation rule X010 queries processing class 01 for the basic pay wage types in internal
table IT. The specification of processing class 01 determines in which valuation basis the wage type
is cumulated.
© SAP AG
HR400
5-16
Processing in Rule X013
Input
Processing in X013
Output
Table IT
Table OT
3 M020
3 M230
3 /001
2,700
300
3,000
Divided by working
hours per payroll
3 M020
2,700
3 M230
300
3 /001
34.09
period
 SAP AG 1999
n The valuation bases for employees who are not paid by the hour are divided by the flat-rate number
of hours in a period. This results in an hourly rate that is stored in the rate field (RTE) for wage
types /001 and /002.
© SAP AG
HR400
5-17
Personnel Calculation Rule X010
Determination of valuation bases ADDITION
X010
E
3
Using ES grouping 3 wage/
wage/time type
type ****
**** as
as an example
E
****
E
Processing class 01
VWTCL 01
E
*
Cancel processing
ERROR
E
0
Transfer wage type to output table OT
ADDWT *
E
 SAP AG 1999
1
ADDWT *
Transfer wage type to output table OT
ELIMI Z
Eliminate time period ID
ZERO=N
Set NUM field = 0
ADDWT /001
Transfer wage type as /001 to table OT
n ADDWT
Add wage type to subsequent wage type
•
Task: The wage type being processed is transferred to internal table OT.
•
Input: Wage types that are in the header of the input table (work area) during processing.
•
Processing: The values of the wage type in the current work area are added to the subsequent
wage type. You can also rename the wage type.
n ELIMI
Eliminate period indicators
•
This operation removes the time unit indicator (split indicator) for the wage type in the current
work area. This prepares the way for combining the values stored in wage types that up to this
point were distinct.
n ZERO
Initializes the current work areas
© SAP AG
HR400
5-18
Personnel Calculation Rule X013
Division of valuation bases
X013
E
3
Using ES grouping 3 wage/
wage/time type
type ****
**** as
as an example
E
****
E
VWTCL 01
E
Processing class 01
*
ADDWT *
E
Transfer wage type to output table OT
5
RTE=TSDIVP
Transfer working hours per period to RTE
DIVID ARR
Divide AMT/RTE, transfer result to RTE
ZERO=A
Set AMT field = 0
ADDWT *
Transfer wage type to output table OT
 SAP AG 1999
n RTE
Calculations in the current rate field (RTE)
•
Task: Change value or query RTE field.
•
Input: Wage types that are in the header of the input table (work area) during processing.
•
Processing: Depending on the operator specified, this operation can be an action or a decision
operation. In this case, the work hours per period from the Basic Pay infotype are stored in the
Rate field.
n DIVID
Divide
•
Task: This operation divides two fields in the current entry and places the result in another
field.
•
Processing: This operation processes the following fields of the current entry in table OT:
NUM (number field), RTE (amount/unit = rate field), and AMT (amount field). Each of these
fields can be divided by any other, and the result can also be stored in any of the fields.
© SAP AG
HR400
5-19
Creating Person-Related Valuation Bases
WType
M010
Standard salary
Processing class
1
Assignment to valuation bases
Specification
1
Wage type included in /001
 SAP AG 1999
n All wage types entered in the Basic Pay (0008) infotype must be assigned to processing class 1.
The specification of this processing class determines the valuation bases used for the wage types
(secondary wage types /0..).
© SAP AG
HR400
5-20
Assigning Valuation Bases (1)
WT
M110
Current wage type
Valuation basis
Overtime hours
01
StatementWT
Start
End
% rate
100.00
Input options:
K = Wage-dependent constant
TS = Pay scale-dependent constant
TG = Pay-scale dependent constant without PS level
T = Pay scale-dependent constant without level and group
01 = /001
02 = /002 etc.
' ‘ = No valuation
 SAP AG 1999
n Example:
Wage type M110 was entered as employee remuneration information specifying 5 hours. Line a)
shows the wage type in table IT after the employee remuneration information was imported, and
line b) shows the wage type after valuation using the valuation basis specified in Customizing:
RTE
NUM
AMT
------------------------------------------------------------------------------------------------------a) Before valuation
M110
5
b) After valuation
M110
14.10
5
70.50
© SAP AG
HR400
5-21
Valuation: Person-Related Remuneration (2)
l The Caliber ‘A’ Bicycle Company pays
overtime according to the employee’s
personal hourly rate and bonus.
 SAP AG 1999
© SAP AG
HR400
5-22
Assigning Valuation Bases (2)
WT
M110
Overtime hours
Start
End
Current wage type
Valuation basis
01
StatementWT
% rate
100.00
1st derived wage type
Valuation basis
01
StatementWT M111
% rate
25.00
StatementWT
% rate
2nd derived wage type
Valuation basis
 SAP AG 1999
n The first and second derived wage types enable you to define bonus wage types for which
remuneration is calculated when an employee's current wage type is valuated in payroll.
n You can determine whether remuneration is calculated for the current wage type by specifying a
valuation basis in the appropriate line.
Example:
RTE
NUM
AMT
----------------------------------------------------------------------------------------------a) Before valuation
M110
5
b) After valuation
M110
14.10
5
70.50
M111
3.52
5
17.60
© SAP AG
HR400
5-23
Valuating Wage Types in the Schema (2)
XT00
.
.
PIT
PIT
MOD
.
P2010
.
.
PIT
.
.
General processing of time data INTERN.
X010
X013
XMOD
P01
P01
GEN
X930
GEN
X015
GEN
Create valuation bases (addition)
Create valuation bases (division)
Determine payroll modifiers
NOAB
Edit employee remuneration information
Valuation of time wage types
 SAP AG 1999
n Subschema XT00 (General processing of time data) calls personnel calculation rule X010, which
queries processing class 01 for basic pay wage types in internal table IT. The specification in
processing class 01 determines whether the wage type is transferred to secondary wage types that
are used to create the valuation bases.
n Subschema XT00 then calls personnel calculation rule X013. The values for employees not paid by
the hour are divided by the flat-rate number of hours in a period. This results in an amount per
working hour that is entered as the valuation basis in the rate field (RTE) for wage types /001 and
/002.
© SAP AG
HR400
5-24
Types of Valuation Bases
1) Valuation bases that are entered in a table as:
- constants dependent on wage types, or
- constants dependent on a collective agreement
2) Valuation bases calculated for specific persons
using basic pay data
 SAP AG 1999
n Valuation bases can also be determined using the average values for remuneration elements from
previous payroll periods. These valuation bases will be covered later in the course.
© SAP AG
HR400
5-25
Wage Type Valuation: Summary (1)
l Time wage types used in payroll initially specify the
number of hours of overtime
in the NUM field. The amount per time unit
needed to calculate remuneration is included
in payroll through the valuation basis.
l A time wage type can be valuated using the
same amount for all employees or amounts
that vary according to organizational
characteristics.
 SAP AG 1999
© SAP AG
HR400
5-26
Wage Type Valuation: Summary (2)
l A time wage type can be valuated according
to the employee’s assignment to a pay scale
level.
l A time wage type can also be valuated using
the hourly rate calculated for each individual
employee.
 SAP AG 1999
© SAP AG
HR400
5-27
Exercises
Unit: Wage Type Valuation
Topic: Creating Constant Valuation Bases
• Adjusting personnel calculation rule XMOD to meet customer
requirements.
• Creating a constant valuation basis for a wage type.
You company pays time wage types with amounts that vary depending
on the employee's organizational assignment. These time wage types
include a bad weather bonus of 1.25 per hour. If the weather is bad, the
wage type is entered as employee remuneration information.
1.
In personnel calculation rule ZMnn (nn = group number), set MODIF 2 to value xx for
the table Constant Wage Type Valuation for employee subgroup grouping 3. Call up
the table Constant Wage Type Valuation, and make an entry under the payroll modifier
xx (xx = 50 + group number) for wage type 20nn Bad weather bonus in the amount of
1.25 (starting January 1st of the current year).
2.
Assign employee remuneration information to your employee for payroll period 02
using wage type 20nn for 10 hours. Run the payroll for the payroll period.
Ensure that the date of the remuneration information is within the payroll period. To
run payroll, use your selection variant.
© SAP AG
HR400
5-28
Unit: Wage Type Valuation
Topic: Creating Person-Related Valuation Bases
• Copy model wage types to customer wage types.
• Check processing class 1 for customer-specific wage types.
Your company pays time wage types that are valuated using the
employee's hourly rate. To calculate the hourly rate, you must encode all
the wage types to be included in the calculation in processing class 1.
1.
Make a copy of wage type M020, and rename it 10nn Salary (nn = group number)
using the wage typ e copying function in the Implementation Guide (transaction PU30).
2.
Encode wage type 10nn in the IMG so that it is included in valuation bases /001 and
/002.
3.
Enable correction entry in your payroll area and change your employee's basic pay
from wage type M020 to wage type 10nn (change without delimitation), and run the
payroll for payroll period 02. Check that the valuation bases have been created.
© SAP AG
HR400
5-29
Unit: Wage Type Valuation
Topic: Assigning Valuation Bases/Derived Wage Types
• Valuating time wage types using an employee's hourly rate.
• Creating derived wage types for bonuses.
Your company pays various bonuses for overtime. For the first two
hours overtime in a day, the employee receives a 25% bonus. For each
additional hour, the employee receive s a 50% bonus. Overtime on
Sundays is remunerated by a 75% bonus, and overtime on public
holidays by a 100% bonus. Basic overtime is also subject to
remuneration.
1.
You require time wage types for overtime remuneration. These wage types are to be
entered as employee remuneration information, and an entry is only made in the fields
Number/unit (which represents the number of hours in this instance).
The wage types must be valuated with the employee's hourly rate, which is contained in
the valuation basis /001. You require the following wage types, and you want to specify
the bonus in the statement wage types:
- 3nn1 Up to 2 hours overtime
derived:3nn5 25% bonus
- 3nn2 Starting 3 hours overtime
derived:3nn6 50% bonus
- 3nn3 Overtime on Sundays
derived:3nn7 75% bonus
- 3nn4 Overtime on public holidays
3nn8 100% bonus
Copy wage type M110 eight times using the wage type copying function
2.
Encode the valuation bases for the wage types 3nn1 to 3nn4.
3.
Check your wage types by assigning employee remuneration information (pay attention
to the date) to your employee in payroll period 02, and specifying 10 hours for each of
the wage types 3nn1, 3nn2, 3nn3, and 3nn4. Run the payroll for period 02. Then exit
the payroll run.
© SAP AG
HR400
5-30
Solutions
Unit: Wage Type Valuation
Topic: Creating Constant Valuation Bases
1.
In the rule ZMnn, set MODIF 2 to the value xx, and make an entry in the table
”Constant Wage Type Valuation”.
IMG à Payroll International à Time Wage Type Valuation à Valuation Bases
à Constant Valuation Bases à Define Wage Type-Dependent Constants
In the dialog box, choose the activity Set modifier for constant valuation.
Note: The IMG enables you to edit personnel calculation rule XMOD. Note that you do
not have to perform the activity Enter modified personnel calculation rule in schema
since you have already created rule ZM nn, and included the rule in schema Z0nn (nn =
group number).
Choose the activity Determine Constant Valuation Per Wage Type
Make the following entries in the table:
Modifier:
xx
Wage type: 20nn
Start date:
January 1st of the current year
End date:
December 31st , 9999
Value:
1.25
2.
To enter 10 hours for wage type 20nn and run the payroll, go to:
Human Resources à Personnel Management à Administration à Maintain
Master Data
Choose the infotype Employee Remuneration Information, and create a record
specifying wage type 20nn and 10 (hours) in the field Number/unit. Go to:
Human Resources à Payroll à International à Payroll à Release Payroll
Human Resources à Payroll à International à Payroll à Start Payroll
Human Resources à Payroll à International à Payroll à Corrections
© SAP AG
HR400
5-31
Unit: Wage Type Valuation
Topic: Creating Person-Related Valuation Bases
1.
To make a copy of wage type M020 and rename it 10nn using the wage type copying
function, go to
IMG à Personnel Management à Personnel Administration à Payroll Data à
Basic Pay à Wage Types à Create Wage Type Catalog
Choose Copy, flag the wage type M020, copy and rename it 10nn "Salary".
2.
To encode wage type 10nn in processing class 1, go to:
IMG à Payroll: International à Time Wage Type Evaluation à Valuation Bases
à Create Person-Related Valuation Bases à Maintain Basic Pay for Valuation
Bases
Flag the wage type and choose Details. Display the specifications for processing class
1, and choose specification 3. Do not forget to save the setting you have made.
3.
To change your employee's basic pay from wage type M020 to 10nn, go to:
Human resources à Payroll à International à
Payroll à Corrections
Human Resources à Personnel Management à Administration à Maintain
Master Data
To run the payroll for the payroll period and check whether the valuation bases have
been created, go to:
Human Resources à Payroll à International à
Payroll à Release Payroll
Human Resources à Payroll à International à Payroll à Start Payroll
Check whether wage types /001 and /002 have been included in table IT (after rule
X013 has been processed) of the payroll log.
© SAP AG
HR400
5-32
Unit: Wage Type Valuation
Topic: Assigning Valuation Bases/Derived Wage Types
1.
To copy time wage types to remunerate overtime, go to:
IMG à Personnel Management à Personnel Administration à Payroll Data à
Employee Remuneration Data à Wage Types à Create Wage Type Catalog
Choose Copy, and enter the original wage type M110 and the Customizing wage type
3nn1.
Choose Make copies of wage type, and enter the following information:
- Wage type starts at
- Number of wage types
- Increase for each step
2.
3nn1
8
1
To encode the valuation bases of wage types 3nn1 - 3nn4, go to:
IMG à Payroll: International à Time Wage Type Valuation à Valuation Bases à
Assign Valuation Bases.
Valuate your wage types with the valuation basis 01 to 100% and make the following
entries for the first derived wage type.
WT
Val. Bases
Statement WT
Percent.
3nn1
3nn2
3nn3
3nn4
01
01
01
01
3nn5
3nn6
3nn7
3nn8
25
50
75
100
© SAP AG
HR400
5-33
3.
To set up and run the payroll program for employee remuneration information, go to:
Human Resources à Payroll à International à Payroll à
Corrections
Human Resources à Personnel Management à Administration à Maintain
Master Data à Time Mgmt Trans. Data à Create
Choose the infotype Employee remuneration information and for each entry create a
record specifying wage types 3nn1 to 3nn4 and 10 (hours) in the field Number/unit.
Human Resources à Payroll à International à Payroll à Start Payroll
Human Resources à Payroll à International à Payroll à Exit Payroll
© SAP AG
HR400
5-34
Wage Type Valuation
Contents:
l Wage Type-Dependent Constants
l Pay Scale-Dependent Constants
l Modifiers for Table Access
l Person-Related Valuation Bases
l Personnel Calculation Rules X010 and X013
l Assigning Valuation Bases
l Derived Wage Types
l Valuating Wage Types in the Schema
 SAP AG 1999
© SAP AG
HR400
5-1
Wage Type Valuation: Unit Objectives
At the conclusion of this unit, you will be able to:
l Valuate time wage types with fixed amounts
and, if necessary, according to organizational
units
l Valuate time wage types according to the
provisions in your collective agreement
l Valuate time wage types using a value derived
from the employee’s basic pay data
 SAP AG 1999
© SAP AG
HR400
5-2
Course Overview Diagram
Payroll Basics
Time Wage Type Selection
Personnel Calculation Rules
Averages
Starting Payroll
Factoring
Wage Type Valuation
Cumulation Wage Types
Absence Valuation
Retroactive Accounting
 SAP AG 1999
© SAP AG
HR400
5-3
Valuating Time Wage Types
e
Tim et
e
sh
 SAP AG 1999
n Overtime that is not recorded automatically, but entered on a time sheet, can be processed for
payroll in two ways:
1. The employee's working times are added up and entered as employee remuneration information
with certain wage types.
2. The exact days and hours of the employee's working times are recorded. This can occur
manually in the Overtime infotype (2005). The system then selects the correct time wage types
to be used in the payroll run.
n The system processes PDC (plant data collection/time evaluation data) automatically.
n In both cases, the wage types initially contain the number of hours overtime the employee has
worked. This figure is specified in the number field (NUM) to be multiplied by a payable amount.
Example:
The amount (AMT) of a time wage type is calculated by multiplying the number (NUM) of time
units by the valuation basis (RTE):
RTE * NUM = AMT
17.70 * 10 hrs = 177.00
The valuation basis is defined in Customizing.
© SAP AG
HR400
5-4
Valuation: Constant Remuneration (1)
l The Caliber ‘A’ Bicycle Company pays a constant
hourly rate that is the same for all employees.
 SAP AG 1999
© SAP AG
HR400
5-5
Wage Type-Dependent Constants (1)
Bad weather bonus
WType
…
4000
4000
5000
...
Start date
End date
Amount
01.JAN.1997
01.JAN.1999
01.JAN.1998
31.DEC.1998
31.DEC.9999
31.DEC.9999
10.00
12.00
20.00
 SAP AG 1999
n In payroll, a wage type can be valuated using a constant amount. The amount does not depend on
the employee's organizational assignment or on any other characteristics.
n Each wage type can have several entries denoting various validity periods.
© SAP AG
HR400
5-6
Valuation: Constant Remuneration (2)
l The Caliber ‘A’ Bicycle Company pays an
hourly bonus that is based on the employee’s
assignment to a pay scale level.
 SAP AG 1999
© SAP AG
HR400
5-7
Pay Scale-Dependent Constants
Collective
Agreement
- Hourly earners
- Monthly earners
- Salaried staff
Night work bonus
Entries per: - Pay scale type
- Pay scale area
EE SG Pay scale PS
Grpg group
level
…
3
3
...
GR04
GR04
01
02
WType
4010
4010
Start date
End date
01.JAN.1998 31.DEC.2000
01.JAN.1998 31.DEC.2000
Amount
10.00
12.00
 SAP AG 1999
n If wage types are subject to constant valuation depending on their pay scale level assignment, you
must define the values for each pay scale level assignment and wage type.
n Note the various employee subgroup groupings for collective agreement provisions specified when
the employee subgroups are defined.
© SAP AG
HR400
5-8
Valuation: Constant Remuneration (3)
l The Caliber ‘A’ Bicycle Company pays an hourly
bonus that varies depending on the
personnel area.

SAP AG 1999
© SAP AG
HR400
5-9
Modifiers for Table Access
Personnel area 1000
Key
01
Payroll
Personnel area 1100
Amount
01 4000
10.00
01 5000
20.00
..
02 4000
15.00
02 5000
22.00
..
02
 SAP AG 1999
n Elements of remuneration, such as bonuses, usually vary depending on the organizational unit.
n Example :
You want bonus wage type 4000 to be remunerated differently for employees in personnel area
1000 than for employees in personnel area 1100. To do this, the system uses a modifier as the first
key specified in the table. The default SAP value for modifiers is 01. The modifier for personnel
area 1100 is created in Customizing by copying modifier 01, renaming it 02, and entering the
relevant amount. During the payroll run, the system sets the modifier to the required value
according to the personnel area assigned to each personnel number.
© SAP AG
HR400
5-10
Personnel Calculation Rule XMOD
Employee grouping for payroll
XMOD
E
3
Using ES grouping 3 wage/
wage/time type
type ****
**** as
as an example
E
****
E
OUTWPPLANT
E
E
Personnel area
1000
MODIF A = 01
Table Absence valuation
MODIF 1 = 01
Table Wage type selection rule
MODIF 2 = 01
Table Constant wage type valuation
1100
MODIF A = 02
MODIF 1 = 02
MODIF 2 = 02
 SAP AG 1999
n In the payroll run, function MOD centrally assigns the modifiers described on the previous page
using personnel calculation rule XMOD.
n Decision operation OUTWP uses various parameters to define an employee's organizational
characteristics such as the company code and personnel area. Operation MODIF sets the modifiers
for table access. The parameters used for operation MODIF represent various tables.
© SAP AG
HR400
5-11
Wage Type-Dependent Constants (2)
Personnel area 1000
Dirty work bonus
Personnel area 1100
PayMo
WType
Start date
End date
Amount
…
01
02
...
4000
4000
01.01.1998
01.01.1998
31.12.2000
31.12.2000
10.00
15.00
 SAP AG 1999
n This represents a complete view of the table Wage type -dependent constants . If, as described in
the first scenario, the values are all the same, you can use the model SAP entries in the standard
system which have the payroll modifier (MODIF 2) set to value 01.
© SAP AG
HR400
5-12
Valuating Wage Types in the Schema (1)
XT00
.
.
.
.
MOD
XMOD
.
P2010 X930
.
.
PIT
X015
.
.
General processing of time data INTERN.
GEN
GEN
GEN
Determine payroll modifiers
NOAB
Edit employee remuneration information
Valuation of time wage types
 SAP AG 1999
n In subschema XT00, personnel calculation rule XMOD queries employee work center data and sets
modifiers that access the table for wage type-dependent constants.
n Function P2010 imports the bonuses for dirty work entered as employee remuneration information.
The wage types are then stored in internal table IT with the number of hours specified in the NUM
field. The RTE field remains empty.
n Valuation is performed in personnel calculation rule X015, which checks whether internal table IT
contains time wage types. If time wage types are found in table IT, the system performs the
valuation set up in Customizing.
© SAP AG
HR400
5-13
Valuation: Person-Related Remuneration (1)
l The Caliber ‘A’ Bicycle Company pays
overtime according to an employee’s
personal hourly rate.

SAP AG 1999
© SAP AG
HR400
5-14
Person-Related Valuation Bases
The valuation basis is
calculated using a basic
pay wage type:
6,000
500
Standard salary
Standard bonus
Voluntary bonus
yes
yes
no
2,700
300
6,000
Total pay
3,000
34.09
Divided by working hours per period (IT0008)
176 Hours
88 Hours
34.09
 SAP AG 1999
n The basis that is used to valuate person-related valuation bases is not a fixed constant, but an
employee-specific value calculated according to the employee's remuneration.
n The system flags the wage types used to calculate person-related valuation bases.
© SAP AG
HR400
5-15
Processing in Rule X010
Input
Processing in X010
Output
Table IT
3 M020
2,700
3 M230
300
Table OT
Amounts totaled
in wage types /0nn
3 M020
2,700
3 M230
300
3 /001
3,000
 SAP AG 1999
n Personnel calculation rule X010 queries processing class 01 for the basic pay wage types in internal
table IT. The specification of processing class 01 determines in which valuation basis the wage type
is cumulated.
© SAP AG
HR400
5-16
Processing in Rule X013
Input
Processing in X013
Output
Table IT
Table OT
3 M020
3 M230
3 /001
2,700
300
3,000
Divided by working
hours per payroll
3 M020
2,700
3 M230
300
3 /001
34.09
period
 SAP AG 1999
n The valuation bases for employees who are not paid by the hour are divided by the flat-rate number
of hours in a period. This results in an hourly rate that is stored in the rate field (RTE) for wage
types /001 and /002.
© SAP AG
HR400
5-17
Personnel Calculation Rule X010
Determination of valuation bases ADDITION
X010
E
3
Using ES grouping 3 wage/
wage/time type
type ****
**** as
as an example
E
****
E
Processing class 01
VWTCL 01
E
*
Cancel processing
ERROR
E
0
Transfer wage type to output table OT
ADDWT *
E
 SAP AG 1999
1
ADDWT *
Transfer wage type to output table OT
ELIMI Z
Eliminate time period ID
ZERO=N
Set NUM field = 0
ADDWT /001
Transfer wage type as /001 to table OT
n ADDWT
Add wage type to subsequent wage type
•
Task: The wage type being processed is transferred to internal table OT.
•
Input: Wage types that are in the header of the input table (work area) during processing.
•
Processing: The values of the wage type in the current work area are added to the subsequent
wage type. You can also rename the wage type.
n ELIMI
Eliminate period indicators
•
This operation removes the time unit indicator (split indicator) for the wage type in the current
work area. This prepares the way for combining the values stored in wage types that up to this
point were distinct.
n ZERO
Initializes the current work areas
© SAP AG
HR400
5-18
Personnel Calculation Rule X013
Division of valuation bases
X013
E
3
Using ES grouping 3 wage/
wage/time type
type ****
**** as
as an example
E
****
E
VWTCL 01
E
Processing class 01
*
ADDWT *
E
Transfer wage type to output table OT
5
RTE=TSDIVP
Transfer working hours per period to RTE
DIVID ARR
Divide AMT/RTE, transfer result to RTE
ZERO=A
Set AMT field = 0
ADDWT *
Transfer wage type to output table OT
 SAP AG 1999
n RTE
Calculations in the current rate field (RTE)
•
Task: Change value or query RTE field.
•
Input: Wage types that are in the header of the input table (work area) during processing.
•
Processing: Depending on the operator specified, this operation can be an action or a decision
operation. In this case, the work hours per period from the Basic Pay infotype are stored in the
Rate field.
n DIVID
Divide
•
Task: This operation divides two fields in the current entry and places the result in another
field.
•
Processing: This operation processes the following fields of the current entry in table OT:
NUM (number field), RTE (amount/unit = rate field), and AMT (amount field). Each of these
fields can be divided by any other, and the result can also be stored in any of the fields.
© SAP AG
HR400
5-19
Creating Person-Related Valuation Bases
WType
M010
Standard salary
Processing class
1
Assignment to valuation bases
Specification
1
Wage type included in /001
 SAP AG 1999
n All wage types entered in the Basic Pay (0008) infotype must be assigned to processing class 1.
The specification of this processing class determines the valuation bases used for the wage types
(secondary wage types /0..).
© SAP AG
HR400
5-20
Assigning Valuation Bases (1)
WT
M110
Current wage type
Valuation basis
Overtime hours
01
StatementWT
Start
End
% rate
100.00
Input options:
K = Wage-dependent constant
TS = Pay scale-dependent constant
TG = Pay-scale dependent constant without PS level
T = Pay scale-dependent constant without level and group
01 = /001
02 = /002 etc.
' ‘ = No valuation
 SAP AG 1999
n Example:
Wage type M110 was entered as employee remuneration information specifying 5 hours. Line a)
shows the wage type in table IT after the employee remuneration information was imported, and
line b) shows the wage type after valuation using the valuation basis specified in Customizing:
RTE
NUM
AMT
------------------------------------------------------------------------------------------------------a) Before valuation
M110
5
b) After valuation
M110
14.10
5
70.50
© SAP AG
HR400
5-21
Valuation: Person-Related Remuneration (2)
l The Caliber ‘A’ Bicycle Company pays
overtime according to the employee’s
personal hourly rate and bonus.
 SAP AG 1999
© SAP AG
HR400
5-22
Assigning Valuation Bases (2)
WT
M110
Overtime hours
Start
End
Current wage type
Valuation basis
01
StatementWT
% rate
100.00
1st derived wage type
Valuation basis
01
StatementWT M111
% rate
25.00
StatementWT
% rate
2nd derived wage type
Valuation basis
 SAP AG 1999
n The first and second derived wage types enable you to define bonus wage types for which
remuneration is calculated when an employee's current wage type is valuated in payroll.
n You can determine whether remuneration is calculated for the current wage type by specifying a
valuation basis in the appropriate line.
Example:
RTE
NUM
AMT
----------------------------------------------------------------------------------------------a) Before valuation
M110
5
b) After valuation
M110
14.10
5
70.50
M111
3.52
5
17.60
© SAP AG
HR400
5-23
Valuating Wage Types in the Schema (2)
XT00
.
.
PIT
PIT
MOD
.
P2010
.
.
PIT
.
.
General processing of time data INTERN.
X010
X013
XMOD
P01
P01
GEN
X930
GEN
X015
GEN
Create valuation bases (addition)
Create valuation bases (division)
Determine payroll modifiers
NOAB
Edit employee remuneration information
Valuation of time wage types
 SAP AG 1999
n Subschema XT00 (General processing of time data) calls personnel calculation rule X010, which
queries processing class 01 for basic pay wage types in internal table IT. The specification in
processing class 01 determines whether the wage type is transferred to secondary wage types that
are used to create the valuation bases.
n Subschema XT00 then calls personnel calculation rule X013. The values for employees not paid by
the hour are divided by the flat-rate number of hours in a period. This results in an amount per
working hour that is entered as the valuation basis in the rate field (RTE) for wage types /001 and
/002.
© SAP AG
HR400
5-24
Types of Valuation Bases
1) Valuation bases that are entered in a table as:
- constants dependent on wage types, or
- constants dependent on a collective agreement
2) Valuation bases calculated for specific persons
using basic pay data
 SAP AG 1999
n Valuation bases can also be determined using the average values for remuneration elements from
previous payroll periods. These valuation bases will be covered later in the course.
© SAP AG
HR400
5-25
Wage Type Valuation: Summary (1)
l Time wage types used in payroll initially specify the
number of hours of overtime
in the NUM field. The amount per time unit
needed to calculate remuneration is included
in payroll through the valuation basis.
l A time wage type can be valuated using the
same amount for all employees or amounts
that vary according to organizational
characteristics.
 SAP AG 1999
© SAP AG
HR400
5-26
Wage Type Valuation: Summary (2)
l A time wage type can be valuated according
to the employee’s assignment to a pay scale
level.
l A time wage type can also be valuated using
the hourly rate calculated for each individual
employee.
 SAP AG 1999
© SAP AG
HR400
5-27
Exercises
Unit: Wage Type Valuation
Topic: Creating Constant Valuation Bases
• Adjusting personnel calculation rule XMOD to meet customer
requirements.
• Creating a constant valuation basis for a wage type.
You company pays time wage types with amounts that vary depending
on the employee's organizational assignment. These time wage types
include a bad weather bonus of 1.25 per hour. If the weather is bad, the
wage type is entered as employee remuneration information.
1.
In personnel calculation rule ZMnn (nn = group number), set MODIF 2 to value xx for
the table Constant Wage Type Valuation for employee subgroup grouping 3. Call up
the table Constant Wage Type Valuation, and make an entry under the payroll modifier
xx (xx = 50 + group number) for wage type 20nn Bad weather bonus in the amount of
1.25 (starting January 1st of the current year).
2.
Assign employee remuneration information to your employee for payroll period 02
using wage type 20nn for 10 hours. Run the payroll for the payroll period.
Ensure that the date of the remuneration information is within the payroll period. To
run payroll, use your selection variant.
© SAP AG
HR400
5-28
Unit: Wage Type Valuation
Topic: Creating Person-Related Valuation Bases
• Copy model wage types to customer wage types.
• Check processing class 1 for customer-specific wage types.
Your company pays time wage types that are valuated using the
employee's hourly rate. To calculate the hourly rate, you must encode all
the wage types to be included in the calculation in processing class 1.
1.
Make a copy of wage type M020, and rename it 10nn Salary (nn = group number)
using the wage typ e copying function in the Implementation Guide (transaction PU30).
2.
Encode wage type 10nn in the IMG so that it is included in valuation bases /001 and
/002.
3.
Enable correction entry in your payroll area and change your employee's basic pay
from wage type M020 to wage type 10nn (change without delimitation), and run the
payroll for payroll period 02. Check that the valuation bases have been created.
© SAP AG
HR400
5-29
Unit: Wage Type Valuation
Topic: Assigning Valuation Bases/Derived Wage Types
• Valuating time wage types using an employee's hourly rate.
• Creating derived wage types for bonuses.
Your company pays various bonuses for overtime. For the first two
hours overtime in a day, the employee receives a 25% bonus. For each
additional hour, the employee receive s a 50% bonus. Overtime on
Sundays is remunerated by a 75% bonus, and overtime on public
holidays by a 100% bonus. Basic overtime is also subject to
remuneration.
1.
You require time wage types for overtime remuneration. These wage types are to be
entered as employee remuneration information, and an entry is only made in the fields
Number/unit (which represents the number of hours in this instance).
The wage types must be valuated with the employee's hourly rate, which is contained in
the valuation basis /001. You require the following wage types, and you want to specify
the bonus in the statement wage types:
- 3nn1 Up to 2 hours overtime
derived:3nn5 25% bonus
- 3nn2 Starting 3 hours overtime
derived:3nn6 50% bonus
- 3nn3 Overtime on Sundays
derived:3nn7 75% bonus
- 3nn4 Overtime on public holidays
3nn8 100% bonus
Copy wage type M110 eight times using the wage type copying function
2.
Encode the valuation bases for the wage types 3nn1 to 3nn4.
3.
Check your wage types by assigning employee remuneration information (pay attention
to the date) to your employee in payroll period 02, and specifying 10 hours for each of
the wage types 3nn1, 3nn2, 3nn3, and 3nn4. Run the payroll for period 02. Then exit
the payroll run.
© SAP AG
HR400
5-30
Solutions
Unit: Wage Type Valuation
Topic: Creating Constant Valuation Bases
1.
In the rule ZMnn, set MODIF 2 to the value xx, and make an entry in the table
”Constant Wage Type Valuation”.
IMG à Payroll International à Time Wage Type Valuation à Valuation Bases
à Constant Valuation Bases à Define Wage Type-Dependent Constants
In the dialog box, choose the activity Set modifier for constant valuation.
Note: The IMG enables you to edit personnel calculation rule XMOD. Note that you do
not have to perform the activity Enter modified personnel calculation rule in schema
since you have already created rule ZM nn, and included the rule in schema Z0nn (nn =
group number).
Choose the activity Determine Constant Valuation Per Wage Type
Make the following entries in the table:
Modifier:
xx
Wage type: 20nn
Start date:
January 1st of the current year
End date:
December 31st , 9999
Value:
1.25
2.
To enter 10 hours for wage type 20nn and run the payroll, go to:
Human Resources à Personnel Management à Administration à Maintain
Master Data
Choose the infotype Employee Remuneration Information, and create a record
specifying wage type 20nn and 10 (hours) in the field Number/unit. Go to:
Human Resources à Payroll à International à Payroll à Release Payroll
Human Resources à Payroll à International à Payroll à Start Payroll
Human Resources à Payroll à International à Payroll à Corrections
© SAP AG
HR400
5-31
Unit: Wage Type Valuation
Topic: Creating Person-Related Valuation Bases
1.
To make a copy of wage type M020 and rename it 10nn using the wage type copying
function, go to
IMG à Personnel Management à Personnel Administration à Payroll Data à
Basic Pay à Wage Types à Create Wage Type Catalog
Choose Copy, flag the wage type M020, copy and rename it 10nn "Salary".
2.
To encode wage type 10nn in processing class 1, go to:
IMG à Payroll: International à Time Wage Type Evaluation à Valuation Bases
à Create Person-Related Valuation Bases à Maintain Basic Pay for Valuation
Bases
Flag the wage type and choose Details. Display the specifications for processing class
1, and choose specification 3. Do not forget to save the setting you have made.
3.
To change your employee's basic pay from wage type M020 to 10nn, go to:
Human resources à Payroll à International à
Payroll à Corrections
Human Resources à Personnel Management à Administration à Maintain
Master Data
To run the payroll for the payroll period and check whether the valuation bases have
been created, go to:
Human Resources à Payroll à International à
Payroll à Release Payroll
Human Resources à Payroll à International à Payroll à Start Payroll
Check whether wage types /001 and /002 have been included in table IT (after rule
X013 has been processed) of the payroll log.
© SAP AG
HR400
5-32
Unit: Wage Type Valuation
Topic: Assigning Valuation Bases/Derived Wage Types
1.
To copy time wage types to remunerate overtime, go to:
IMG à Personnel Management à Personnel Administration à Payroll Data à
Employee Remuneration Data à Wage Types à Create Wage Type Catalog
Choose Copy, and enter the original wage type M110 and the Customizing wage type
3nn1.
Choose Make copies of wage type, and enter the following information:
- Wage type starts at
- Number of wage types
- Increase for each step
2.
3nn1
8
1
To encode the valuation bases of wage types 3nn1 - 3nn4, go to:
IMG à Payroll: International à Time Wage Type Valuation à Valuation Bases à
Assign Valuation Bases.
Valuate your wage types with the valuation basis 01 to 100% and make the following
entries for the first derived wage type.
WT
Val. Bases
Statement WT
Percent.
3nn1
3nn2
3nn3
3nn4
01
01
01
01
3nn5
3nn6
3nn7
3nn8
25
50
75
100
© SAP AG
HR400
5-33
3.
To set up and run the payroll program for employee remuneration information, go to:
Human Resources à Payroll à International à Payroll à
Corrections
Human Resources à Personnel Management à Administration à Maintain
Master Data à Time Mgmt Trans. Data à Create
Choose the infotype Employee remuneration information and for each entry create a
record specifying wage types 3nn1 to 3nn4 and 10 (hours) in the field Number/unit.
Human Resources à Payroll à International à Payroll à Start Payroll
Human Resources à Payroll à International à Payroll à Exit Payroll
© SAP AG
HR400
5-34
Absence Valuation
Contents:
l Absence Valuation Types
l Valuation Using Constant Values
l Time of Absence Valuation
l Defining and Creating Counting Classes
l Assigning Absences to a Valuation
l Grouping for Absence Valuation
l Defining and Using Day Rules
l Valuating Absences According to the ‘As If’ Principle
l Processing Absences in the Schema
 SAP AG 1999
© SAP AG
HR400
6-1
Absence Valuation: Unit Objectives
At the conclusion of this unit, you will be able to:
l Describe the various methods of valuating
absences.
l Explain what is meant by valuation and
counting classes.
l Valuate vacation bonus as a constant
in payroll according to organizational
differences and time constraints.
 SAP AG 1999
© SAP AG
HR400
6-2
Course Overview Diagram
Payroll Basics
Time Wage Type Selection
Personnel Calculation Rules
Averages
Starting Payroll
Factoring
Wage Type Valuation
Cumulation Wage Types
Absence Valuation
Retroactive Accounting
 SAP AG 1999
© SAP AG
HR400
6-3
Absences
 SAP AG 1999
n The system can process an employee's absences in several ways.
n Examples:
•
An employee is sick for a long period of time.
•
An employee takes vacation.
•
An employee goes on maternity leave.
•
An employee takes unpaid leave.
© SAP AG
HR400
6-4
Absence Valuation Types
l Valuation using an average
amount or a fixed amount
l ‘As If’ principle
 SAP AG 1999
n There are various methods for valuating absences. Each method can be used separately or
combined with other methods.
1. Valuating absences using averages or constants.
Example:
You want to calculate a vacation bonus using the average remuneration for overtime hours
worked by your employees.
2. Valuating absences as if the employee had worked (‘as if’ principle).
Example:
You want employees who are unable to work to receive their basic pay as well as the bonus
they would have received had they been at work.
n If employees take unpaid leave, their remuneration is reduced accordingly. Reductions in pay as a
result of unpaid or partially paid absences (factoring) will be covered later in the course.
© SAP AG
HR400
6-5
Absence Valuation: Vacation Bonus (1)
l The Caliber ‘A’ Bicycle Company pays a constant
vacation bonus for each day.
l In the near future the company will pay a vacation
bonus made up of average values that is
paid for each day.
 SAP AG 1999
© SAP AG
HR400
6-6
Valuating Absences by Constants/Averages
View: Absence Valuation: Averages/Constants
AbsValGrpg
Valuation rule
01
01
WType
M400
__
__
Percent.
100
___
___
Time
B
_
_
Paid leave
Time unit
AT
__
__
From
To
BP split
X
__
__
Day rule
__
__
__
Time units
Absence hours
Absence days
Calendar days
Accounting hours
Accounting days
363.00
51.00
71.00
363.00
51.00
AH
AT
KT
RH
RT
 SAP AG 1999
n Scenario:
1. Your employees are to receive a fixed vacation bonus for each day's leave. In this case, the
system valuates the relevant wage type using a constant amount.
2. For each absence day of leave, your employees are to receive a vacation bonus based on the
average amount of overtime they have worked over the last three months. In this case, the
relevant wage type must be valuated using average bases.
n
You want to pay vacation bonus for each leave day. There are several ways in which you can
remunerate leave per day:
1. Calendar days.
2. Absence days, that is, each day that counts as a workday on the work schedule.
3. Accounting days, that is, leave days processed according to the entries specified in the table
Attendance/Absence Counting .
n If you flag the field Basic Pay Split, changes made to an employee's basic pay for a payroll period
are taken into account.
© SAP AG
HR400
6-7
Time of Absence Valuation
Jan 20
Absence
Payroll period
Jan 01
Feb 05
Feb 01
Jan 98
March 01
Feb 98
Time B
Time E
Time I
Time Z
Store data per day
 SAP AG 1999
n If an employee’s absence spans several payroll periods, valuation can occur either in the payroll
period in which the absence begins, the payroll period in which the absence ends, or on a pro rata
basis in each payroll period affected.
n Time Z writes the wage type to internal time wage type table ZL.
© SAP AG
HR400
6-8
Defining and Creating Counting Classes
View: Absence Valuation: Create Counting Classes
AbsValGrpg
Valuation rule
Counting class
01
__
__
01
01
Paid leave
Leave
X
% rate
100
Start
End
Day rule
View: Define Counting Classes
01
Leave
02
Illness
xAP01
xAU01
xAP02
xAU02
 SAP AG 1999
n Counting classes are used to collect data on various absence types (for example, leave and
sickness). You have the option of subdividing each counting class into paid (AP = absences paid)
and unpaid absences (AU = absences unpaid).
n This data on paid and unpaid absences is used to reduce pay or to generate statistical information.
1. To reduce remuneration for unpaid absences, in the standard system, all counting classes that
group unpaid absences are processed together. Therefore, a prerequisite for the reduction in
remuneration is that the unpaid absences are grouped together in at least one counting class. If
several counting classes are to be created for unpaid absences, you must explicitly specify the
counting classes that are to be taken into consideration in factoring .
2. To generate statistics and for cost accounting, you can group together absence times in the
counting classes to fill wage types and evaluate the cumulated values for cost accounting or
statistical purposes. You can access the counting classes using operation NUM. Paid counting
classes are queried in operations with the ID xAPnn, and unpaid counting classes are queried
with the ID xAUnn, where x = K for the value in calendar days, A in workdays, and S in hours.
© SAP AG
HR400
6-9
Assigning Absences to a Valuation (1)
View: Absence: Payment Data
PSGrp
Abs./attendance type
01
01
01
01
0100
0110
0120
0200
From
Leave
Leave 1/2 day
Seniority leave
Sickness
To
VRule
01
01
01
02
Cat.
-
Absence Valuation Rule
01
Leave
02
Sickness
 SAP AG 1999
n You want to valuate absences for paid leave differently from absences for paid sickness, and you
want all leave types to be processed using the same valuation method. To do this, you group all
absence types that are valuated identically by assigning them to an absence valuation rule.
n Absence valuation rules determine how an employee's absences are processed in the payroll run.
n The field Category is used in specific Austrian evaluations and for the German public sector to
determine the continued pay and sick pay supplement periods.
© SAP AG
HR400
6-10
Assigning Absences to a Valuation (2)
View: Absence:Valuation Using Constants/Averages
PSGrp
Abs./Attendance type
01
01
01
01
0100
0110
0120
0200
From
To
Leave
Leave 1/2 day
Seniority leave
Sickness
VRule
01
01
01
02
Cat.
-
View: Valuate Absences
Employee grouping
for absence valuation
AbsValGrpg
Rule
Valuation class
01
01
02
02
01
02
01
02
Leave
Sickness
Leave
Sickness
 SAP AG 1999
n To valuate absences, you must divide your employees into groups. This enables you to apply
different absence valuation rule s to each grouping.
© SAP AG
HR400
6-11
Valuation Rules and Counting Classes
1.
Create absence valuation rules
01 Leave
02 Paid illness
...
11 Unpaid illness
3.
3.
2.
2.
Cumulate absences for valuation
0100 Leave
0110 Half leave day
01
0120 Age-based leave
.. .
0200 Illness
02
...
0620 Unpaid leave
11
Create counting classes for absence valuation
a) Define counting classes
01 Leave
02 Illness
b) Create counting classes for absence valuation
Valuation rule 01
xAP01
Counting class 01 Paid leave
100%
Valuation rule 11
xAU01

Counting class 01 Paid leave
100%
SAP AG 1999
n In this example, paid leave is grouped together using the absence valuation rule 01 in counting class
01 Leave in the „bucket“ of paid absences (AP).
n Unpaid leave is grouped together using absence valuation rule 11 in counting class 01 Leave in the
„bucket“ of unpaid absences (AU).
© SAP AG
HR400
6-12
Grouping for Absence Valuation
Employee grouping for payroll
XMOD
E
3
Using ES grouping 3 wage/time
wage/time type
type ****
**** as
as an example
E
****
E
OUTWPPLANT
E
E
Personnel area
1000
MODIF A = 01
Table Absence valuation
MODIF 1 = 01
Table Time wage type selection rule
MODIF 2 = 01
Table Constant wage type valuation
1100
MODIF A = 02
MODIF 1 = 02
 SAP AG 1999
MODIF 2 = 02
n In this step, you group together employees whose absences are to be valuated identically in absence
valuation. In this way, you determine which table entries the system references for which employee
subgroup groupings during absence valuation.
n Decision operation OUTWP uses work center elements to determine the modifiers.
n Operation MODIF set to parameter A determines the employee groupings for accessing the table
Absence Valuation during payroll.
© SAP AG
HR400
6-13
Absence Valuation: Vacation Bonus (2)
l The Caliber ‘A’ Bicycle company decides
not to pay the constant vacation bonus
for an absence taken on a public holiday.
Therefore absences that coincide with a
public holiday should be grouped together in a
separate counting class.
 SAP AG 1999
© SAP AG
HR400
6-14
Defining Day Rules
View: Define Day Rules
Day rule
Sequential no.
WD
00
Conditions set for holiday class
Prev. day
Current day
X
X
X
X
X
X
Holiday class BLANK - no public holiday
Holiday class 1 - public holiday
….
Conditions set for day type
Day type BLANK - work acc. to PWS
Day type 1 - day off
….
Conditions set
for weekday
Monday
Tuesday
….
X
X
Conditions set
for planned hours
Plnd hrs > 0
Plnd hrs = 0
….
X
X
X
 SAP AG 1999
n Day rules allow you to form counting classes or wage types based on the following conditions set
for the day of an absence:
•
Public holiday class or day type of the day to be evaluated or the previous day?
•
Which weekday?
•
Does the employee's personal work schedule for the current or previous day show planned
hours?
n You can specify several different conditions for a day rule, and assign them sequential numbers.
During processing, the system runs through the numbers in consecutive order until it finds an
appropriate condition.
n The name range reserved for customers is A - Z.
© SAP AG
HR400
6-15
Using Day Rules
View: Absence Valuation: Averages/Constants
AbsValGrpg
Valuation rule
01
01
WType
M400
Percent.
100
Time
B
Paid leave
Time unit
AT
From
To
BP split
X
Day rule
WD
View: Absence Valuation: Create Counting Classes
AbsValGrpg
Valuation rule
01
01
Counting class
01
11
Paid
X
Paid leave
% rate
100
100
From
To
Day rule
WD
DO
 SAP AG 1999
n WD - Workday: To ensure that the counting class is only formed on workdays, two conditions must
be fulfilled and stored in a rule without a sequential number:
a) The day is assigned day type BLANK.
b) There are planned hours specified for the employee for this day, that is:
- A valid daily work schedule with planned hours greater than 0, or
- A time substitution.
n Making entries for just one of these conditions is not sufficient to determine a workday. If a day is
assigned the day type BLANK, the decision as to whether or not the employee must work is made
on the basis of the planned hours in the work schedule (are there planned hours specified for the
employee on the day in question or is the daily work schedule OFF?). Therefore, the planned hours
in the daily work schedule and the day type must both be queried.
n DO - Day OFF: Days off can be characterized by two different conditions that you represent by
assigning the sequential numbers 01 and 02 to day rule DO:
c) Sequential number 01: The day is assigned day type 1.
d) Sequential number 02: There are no planned hours specified for the employee on the relevant
day.
© SAP AG
HR400
6-16
Absence Valuation: ‘As If’ Principle
l Absences taken by employees
who are remunerated based on
their working times are to be paid
as if the employee had worked.
 SAP AG 1999
© SAP AG
HR400
6-17
Valuating Absences Using the ‘As If’ Principle
View: Absence Valuation: ‘As If’ Principle
PSGrp
Valuation rule
01
01
01
02
Time wage type selection
Leave
Sickness
x
Employee grouping
for absence valuation
Wage type generation
20
20
10
10
10
10
 SAP AG 1999
n Absence valuation using the ‘as if’ principle means paying employees exactly as if they had
worked. This includes bonuses that form part of the employee's planned working time. Overtime is
not taken into account when absences are valuated using the ‘as if’ principle.
n Example:
An employee grouping is paid according to time worked. One employee should have worked 160
hours in the month. Instead, he or she worked 120 hours and was unable to work the other 40 hours.
•
Wage types must be generated for these 40 hours so that the employee can be paid for the
absences.
•
As a result of the collective agreement, legal requirements or enterprise-specific regulations,
the employee is also to receive bonuses for work on Sundays, night work, and so on, just as if
he or she had worked as normal.
© SAP AG
HR400
6-18
Processing Absences in the Schema
XT00
.
.
.
MOD
XMOD
RAB
.
DAYPR TC00
.
PAB
.
.
.
General processing of time data INTERN.
GEN
Determine payroll modifiers
Import absences
Day processing of time data
Edit absence data
 SAP AG 1999
n Function MOD calls personnel calculation rule XMOD which queries employee work center data
and sets modifiers for table access during payroll.
n The entries are sorted and grouped in table views using one or more key fields.
© SAP AG
HR400
6-19
Absence Valuation: Summary (1)
l Time wage types for absences can be
valuated at different times during the absence
using average or fixed amounts. They can
also be sorted according to organizational
criteria and valuation rules (for example, leave).
l In factoring and Cost Accounting, absences are
cumulated into counting classes (for example,
sickness). Paid and unpaid absences can
be processed separately in each counting
class.
 SAP AG 1999
© SAP AG
HR400
6-20
Absence Valuation: Summary (2)
l Absences can be valuated using
the ‘as if’ principle, which is used to
remunerate employees exactly as if
they had worked.
 SAP AG 1999
© SAP AG
HR400
6-21
Exercises
Unit: Absence Valuation
Topic: Valuating Absences
• Adjusting personnel calculation rule XMOD to meet customer
requirements.
• Including a constant, daily vacation allowance in the payroll run.
Your company pays a vacation allowance for each day of leave. The
amount of the vacation allowance varies depending on the employee's
organizational assignment.
Your company pays a constant vacation allowance of 20.00 per payroll day. You want to
include the vacation allowance in the payroll run using the absence Leave.
1.
Determine the absence valuation grouping for your employee by setting modifier
MODIF A to value yy (yy = 70 + group number) in personnel calculation rule ZMnn
(nn = group number) for the table ”Valuation of Absences”.
2.
To ensure that the vacation allowance is valuated as a constant, assign a constant
valuation basis to the wage type 40nn ”Vacation allowance”. Enter the valuation
indicator K against your wage type. Create an entry for the wage type 40nn ”Vacation
allowance” in the table ”Constant wage type valuation” under the payroll modifier xx
(xx = 50+group number) using the amount 20.00.
3.
To ensure that wage type 40nn is included in your payroll runs, your table "Valuation
of absences" must contain an entry for your absence valuation grouping.
Use the entry for the absence valuation grouping 01 and the valuation rule 01 as a copy
template and create an entry for your absence valuation grouping yy and the valuation
rule 01 Leave (yy = 70 + group number).Use counting class 01 and ensure that the
absence is paid in full. Effect payment of the vacation allowance in the payroll period
that leave begins.
4.
Record leave for your employee between payroll periods 03 and 04 (the course
instructor will provide the exact dates).
Release and run the payroll for period 03.
5.
Effect payment of the vacation allowance in the payroll period that leave ends (E).
Change the entry for absence grouping yy, and run the payroll for period 04. What must
you take into account as you do this?
6.
Effect payment of the vacation allowance in the relevant payroll period (I). Change the
entry of absence grouping yy, and run the payroll for periods 03 and 04.
When there are no more errors, exit the payroll run.
Check the payroll log for each scenario.
© SAP AG
HR400
6-22
Solutions
Unit: Absence Valuation
Topic: Valuating Absences
1.
To set up the absence valuation grouping in personnel calculation rule ZMnn, to:
IMG à Payroll: International à Absences à Define Grouping for Absence
Valuation
Note: The IMG automatically calls personnel calculation rule XMOD. Note that you
previously copied personnel calculation rule ZMnn, and included it in schema Z0 nn
(nn = group number).
2.
To valuate wage type 40nn as a constant, go to:
IMG à Payroll: International à Time Wage Type Valuation à Valuation Bases
à Constant Valuation Bases à Assign Valuation Bases
Change the following entry:
Wage type:
40nn
Start date:
January 1st current year
End date:
31st December 1999
Valuation basis: K
IMG à Payroll: International à Time Wage Type Valuation à Valuation Bases
à Constant Valuation Bases à Define Wage Type-Dependent Constants à
Determine Constant Valuation Per Wage Type
Create the following entry:
Mod:
xx
Wage type:
40nn
Start date:
January 1st current year
End date:
31st December 1999
Value:
20
© SAP AG
HR400
6-23
3.
To enter absence valuation grouping yy and valuation rule 01 Leave, go to:
IMG à Payroll: International à Absences à Valuation of Absences à Create
Counting Classes for Absence Valuation à Set Up Counting Classes for Absence
Valuation
Create the following entry:
AbsValGrp:
xx
Valuation rule: 01
Count.class:
01
Paid:
yes
Percentage:
100
IMG à Payroll: International à Absences à Valuation of Absences à Valuate
Absences by Constants/Averages
Enter the following data for the valuation of averages:
Wage type:
40nn
Time:
B
Percent:
100
Time unit:
RT
4.
Record and run payroll for cross-period leave:
Human Resources à Personnel Management à Administration à Maintain
Master Data à Time Mgmt Trans Data à Absences à Create
Human Resources à Payroll à International à Payroll à Release Payroll
Human Resources à Payroll à International à Payroll à Start Payroll
5.
To change the data stored for absence grouping yy, and run the payroll, go to:
IMG à Payroll: International à Absences à Valuation of Absences à Create
Counting Classes for Absence Valuation à Absence Valuation: Expert View
Time: E
Solution: After running the payroll for period 03, you changed an entry in a table view.
This change does not automatically trigger a retroactive accounting run for the relevant
employee. You must therefore run the payroll for period 04 with forced retroactive
accounting for period 03.
6.
To change the data stored for absence grouping yy, and run the payroll, go to:
IMG à Payroll: International à Absences à Valuation of Absences à Create
Counting Classes for Absence Valuation à Absence Valuation: Expert View
Time: I
Human Resources à Payroll à International à Payroll à Start Payroll
Human Resources à Payroll à International à Payroll à Exit Payroll
© SAP AG
HR400
6-24
Time Wage Type Selection
Contents:
l Time Wage Type Selection
l Time Pairs in Table TIP
l Structure of a Time Wage Type Selection Rule
l Grouping for Time Wage Type Selection Rule
l Day Grouping for Time Wage Type Selection
l Valuation Classes for Period Work Schedule
l Examples of Time Wage Type Selections
l Function GWT
l Time Wage Type Selection in the Schema
 SAP AG 1999
© SAP AG
HR400
7-1
Time Wage Type Selection: Unit Objectives
At the end of this unit, you will be able to:
l Explain the time wage type selection
concept.
l Assign groupings for the time wage type
selection rule based on organizational
differences.
l Create time wage type selection rules.
l Modify the schema to meet company
requirements.
 SAP AG 1999
© SAP AG
HR400
7-2
Course Overview Diagram
Payroll Basics
Time Wage Type Selection
Personnel Calculation Rules
Averages
Starting Payroll
Factoring
Wage Type Valuation
Cumulation Wage Types
Absence Valuation
Retroactive Accounting
 SAP AG 1999
© SAP AG
HR400
7-3
Time Wage Type Selection (1)
When does
overtime start?
How many hours
overtime are
paid at what rate?
Weekend
work?
arl Walden
Time sheet C
.m.
0 a.m. - 7:00 p
:0
7
y
a
d
rs
u
Th
0 p.m.
7:30 a.m. - 6:0
Friday
p.m.
0 a.m. - 5:00
:0
0
1
y
a
rd
tu
a
S
.m.
a.m. - 1:00 p
0
:0
0
1
y
a
Sund
 SAP AG 1999
n If an employee's working times are recorded manually on a time sheet and you want to maintain
this data as wage types in the Employee Remuneration Information infotype (2010), the person
responsible must be familiar with all the relevant details and take these into account. For example:
•
When does planned working time end, that is, when does overtime start for the employee?
•
Which bonus is used to remunerate overtime?
•
Does the employee's work schedule include weekend work, or is work at weekends the
exception (do the bonuses vary)?
•
Is there a public holiday on the workday itself, the day before or the day after?
n The HR component allows you to check an employee's working times by defining certain
conditions. Once the conditions have been fulfilled, the system can generate the required wage
types and include these in the payroll run.
© SAP AG
HR400
7-4
Time Wage Type Selection and
Overtime Compensation
Initialization
Prepare time data
Time wage type
type
selection group
group
Tolerance and error
checks
Function
Function
DAYMO
Time classification
Time WT selection and
overtime
vertime compensation
Time wage types
selection
Admin. of time accounts
Overtime
compensation
Final processing
 SAP AG 1999
n Time wage type selection takes place in subschema TC00.
© SAP AG
HR400
7-5
Time Pairs
Calculate employee’s working time
Work schedule
Time recording terminal
+
Early
Normal
Night
Processing type
Planned time
Actual time
S
M
Time pairs
8:00 a.m.
5:00 p.m.
7:00 p.m.
 SAP AG 1999
n The R/3 System displays an employee's working times in the form of time pairs (start/end times). In
this example, the time recording terminal shows that the employee worked from 8:00 a.m. to 7:00
p.m. The time pair 08:00 a.m. to 05:00 p.m. is derived from the employee's work schedule. The pair
represents the employee's planned working time and is assigned processing type S (planned work).
The time pair 8:00 a.m. to 5:00 p.m. represents the time span the employee works outside his or her
planned working time, and has processing type M (overtime).
n Time pairs are stored in internal table TIP (Time Pairs).
© SAP AG
HR400
7-6
Time Wage Type Selection (2)
TIP
Start
End
Proc. type
08.0000
17.0000
17.0000
19.0000
S
M
Number
9.0000
2.0000
Rules for selecting
time wage types
(V_T510S)
Function
Time wage type selection
GWT S DZL
GWT M ZML
Planned working pairs
l
l
Hourly wage
Bonuses
Overtime pairs
l
DZL
DZL
ZML
ZML
Overtime
wage types
 SAP AG 1999
n When daily processing is effected, the entries in internal table TIP are generated as time wage
types.
n To do this, you must first define rules that assign time wage types to the entries in table TIP
according to the processing type of the rele vant entry (for example, S or M).
© SAP AG
HR400
7-7
Time Wage Type Selection: Rule Structure (1)
ition
n
i
f
i
f
e
D
De
FField
n Valid processing types
Time pair type?
(planned or overtime pair)
n Conditions on day
What days?
l Weekday
l Workday, weekend
l Public holiday
n Conditions on time
l What time intervals?
l What limits?
l Determine the value limits?
n Control
l Override using fixed values?
l Leave rule?
 SAP AG 1999
n Valid processing types:
These fields determine the processing types that entries in internal table TIP must have in order to
generate the relevant wage type.
n Conditions on day:
These fields check weekdays, public holidays, the day type and the daily work schedule class.
n Conditions on time:
These fields check time intervals as well as minimum and maximum hours.
n Control:
This field allows you to specify a fixed value.
n For the relevant entry to be selected, all the conditions must be fulfilled simultaneously.
n For time wage type selection rules requiring start and end times to be observed, all the TIP entries
to be valuated for the relevant day must denote clock times. If there are TIP entries without clock
times, the time wage types that specify a time interval are not selected for that day.
© SAP AG
HR400
7-8
Time Wage Type Selection: Rule Structure (2)
Conditions time
n Time interval:
enn??
W
Whhe
20:00
-
30:00
n Value limits for number of hours:
Explicit Symb.
t?
Star
Minimum hours:
EEnndd??
Maximum hours:
vaall??
iinntteerrv
e
e
m
m
i
TTi
Relevant
processing types:
Planned hrs.
acc. to DWS
S
S
M
Interval:
 SAP AG 1999
n Clock time interval:
The system only processes time pairs that fall within the time interval specified.
n Maximum/minimum hours:
The employee must work a minimum/maximum number of hours. This entry can be explicit or
denote planned hours based on the daily work schedule.
n The system determines limits using the relevant processing types. If you flag the field Interval, the
system only processes the hours of the time pair that apply to the relevant time interval.
n An entry in the fixed value field always overrides the hours specified by the time pair.
© SAP AG
HR400
7-9
Time Wage Type Selection Rule Group
Function MOD, personnel calc. rule TMOD
Hourly wage earners
MODIF W = 01
l
l
l
Hourly wage
Bonuses
Overtime
Salaried employees
Salaried employees
MODIF W = 02
l
l
Bonuses
Overtime
MODIF W = 03
l
l
Bonuses
Overtime as of
10 overtime hours
 SAP AG 1999
n You can use the time wage type selection rule group to set specific regulations for time wage type
selection according to an employee's organizational assignment.
n You use function MOD in personnel calculation rule TMOD to determine which time wage type
selection rule group the time evaluation driver should use to access the entries for an employee in
the Time Wage Type Selection table.
© SAP AG
HR400
7-10
Grouping for Time Wage Type Selection Rule
Determining table modifiers
TMOD
E
3
Using ES grouping 3 wage/time
wage/time type
type ****
**** as
as an example
E
****
E
OUTWPPLANT
E
E
Personnel area
1000
MODIF T = 01
Table Time type determination
MODIF W = 01
Table Time wage type selection rule
1100
MODIF T = 01
Table Time type determination
MODIF W = 02
Table Time wage type selection rule
 SAP AG 1999
n In this step, you group together employees who are to be processed identically for time wage type
selection. In this way, you determine which table entries the system references for which employee
subgroup groupings during wage type generation. Operation MODIF W determines the employee
groupings for accessing the Time Wage Type Selection table during payroll.
n Decision operation OUTWP uses work center elements to determine the modifiers.
© SAP AG
HR400
7-11
Time Wage Type Selection: Function DAYMO
Set day grouping for time wage type selection
Conditions on day
Not a public holiday Not a public holiday Public holiday
Monday - Saturday Sunday
Monday - Saturday
DAYMO
Public holiday
Sunday
PAR 1
PAR 2
PAR 3
PAR 4
01
02
02
02
Day grouping
 SAP AG 1999
n Function DAYMO is used to determine which rules are referenced for time wage type selection for
the relevant day. The function must be contained in the schema otherwise no rules are selected for
time wage type selection.
n If the four day categories are not sufficient for your purposes, it is also possible to set the day
grouping in a personnel calculation rule using operation MODIF D=xx.
© SAP AG
HR400
7-12
The Rule Group Principle Using Time Wage
Type Selection
R
Ruullee g
grroouup
Not a pub. hol.
Mo - Sa
Time wage type
selection group
TIP
Day
grouping
Sequential number of
rules for time wage
type selection
01 01
001 Normal hours
Wage type MI10
01 01
050 Overtime 25%
Rule not fulfilled
01 01
055 Overtime 50%
Rule not fulfilled
01 01
070 Night bonus 35%
Wage type MQ30
01 01
075 Night bonus 35%
Rule not fulfilled
01 02
070 Night bonus 35%
01 02
080 Sunday bonus
 SAP AG 1999
n By assigning a wage type to groupings (time wage type selection rule group and day grouping), you
can preselect the relevant wage types.
n The sequential number should be chosen in increments of 10 so that you can add numbers later.
© SAP AG
HR400
7-13
Valuation Classes for the Period Work Schedule
Normal work
Mo
.
.
.
Fr
3-week shift
Time wage type selection
1
Valuation class
3
Mo
.
.
.
Fr
Creates various bonus
wage types for the same
amount of overtime
Overtime bonus
Overtime shift
 SAP AG 1999
n Valuation classes enable you to structure time wage type selection rules according to the period
work schedule. For example, employees who work on a rotating shift can receive hig her bonuses
than employees who work on a normal shift.
© SAP AG
HR400
7-14
Example: Time Wage Type Selection Rule (1)
Grouping…
Valid processing type
M___
Conditions on day
Control
Fixed value
Valuation class
0123456789
x
Conditions on time
Start
00:00
End
47:59
Min. Symb. Max. Symb.
Relevant proc. types
Interv.
M Overtime
Wage type for 2 hours
overtime during shift
16.00
18.00
 SAP AG 1999
n You want overtime for shift work to be remunerated at a higher rate than overtime for normal work.
To do this, the system queries the valuation class of the period work schedule.
© SAP AG
HR400
7-15
Example: Time Wage Type Selection Rule (2)
Grouping…
Valid processing types
M___
Conditions on day
Weekdays
01234567
xx
Control
Fixed value
2
Valuation class
0123456789
x
Conditions on time
Start
20:00
End
30:00
Min. Symb. Max. Symb.
Relevant proc. types
Interv.
M Overtime
Wage type for 2
hours overtime
22.00 22.20
 SAP AG 1999
n In the fixed value field, you can specify how many hours (number) should be valuated with a wage
type if an employee's time pair meets all other conditions but overlaps with the time interval.
n If an employee's overtime exceeds the fixed value, a subsequent rule must be defined in which the
fixed value is configured as minimum hours.
© SAP AG
HR400
7-16
Example: Time Wage Type Selection Rule (3)
Grouping…
Valid processing types
SM__
.
.
.
Control
Fixed value
Conditions on time
Start
20:00
End
30:00
S Plnd. Wrk.
Min. Symb. Max. Symb.
2,00
Relevant proc. types
SM
Interv. X
M Overtime
Wage type for hours from
10:00 p.m. to midnight
14.00
20.00 22.00 24.00
 SAP AG 1999
n Only the hours that fall within the time interval of 08:00 p.m. to 06:00 a.m. the following day are
taken into account. The hours from 02:00 p.m. to 08:00 p.m. are not taken into account. The
minimum requirement of two hour's work (minimum hours = 2 hours) is calculated from 08:00 p.m.
onwards, because the field Count in specified interval only has been activated. A wage type is
generated for the time between 10:00 p.m. to midnight.
© SAP AG
HR400
7-17
Example: Time Wage Type Selection Rule (4)
Grouping …
Valid processing types
SM__
Control
Fixed val.
.
.
.
Leave rule
Exit time wage type
selection
Conditions on time
Start
20:00
End
30:00
Min. Symb. Max. Symb.
2.00
Relevant proc. types
SM
Interv.
S Planned work M Overtime
Wage type for hours from
08:00 p.m. to midnight
14.00
20.00 22.00 24.00
 SAP AG 1999
n The employee has already fulfilled the minimum requirement of two hour's work (minimum hours
= 2) by 04:00 p.m. in the planned working time as the system does not only count the hours in the
time interval specified. A wage type is generated for the time between 08:00 p.m. and midnight.
n Leaving the time wage type valuation rule : When selecting time wage types, the system checks
all the rules stored for all TIP entries and selects the relevant wage type, if the requirements are
met. By activating this field, you cause the system to leave processing of the current rule , as soon as
the wage type was selected for a TIP entry. The next rule continues time wage type selection.
n Exiting time wage type selection: By activating this field, you cause the system to exit time wage
type selection, as soon as the wage type was selected for a TIP entry. The subsequent rules are no
longer included in time wage type selection.
© SAP AG
HR400
7-18
Function GWT: Select Time Wage Types
Select wage types for planned work and overtime
1. Wage type for planned work:
Function GWT with parameter S
V_554C_E
DZL
TIP
Start
End
08.0000 10.0000
10.0000 13.0000
14.0000 16.0000
Proc.Type
AB
Number
S
S
S
01
2.0000
3.0000
2.0000
02
GWT S DZL
V_T510s
WT
MI10
MI10
IFTYP Number
A
4.0000
S
3.0000
2. Wage type for overtime:
Function GWT with parameter M
ZML
TIP
Start
End
18.0000 22.0000
Proc.Type
M
AB
Number
4.0000
GWT M ZML
V_T510s
WT
Key
MM10
MM20
IFTYP Number
M
2.0000
M
2.0000
 SAP AG 1999
n The function GWT generates time wage types for TIP entries according to the rules in the view
Time Wage Type Selection (V_T510S).
•
Time wage type selection for planned work:
TIP entries with processing type S are processed in time wage type selection for planned time.
For each time wage type selection rule for wage types for planned working time, the system
checks which TIP entries observe the rule. If the rule is observed, the relevant wage type is
entered in the internal table DZL.
•
Time wage type selection for overtime:
All TIP entries with processing type M are processed in time wage type selection for overtime.
For each time wage type selection rule for overtime wage types, the system checks which TIP
entries observe the rule. If the rule is observed, the relevant wage type is entered in the internal
table ZML.
n Function GWT is used in time evaluation to select time wage types for all absences which are
valuated on the basis of the ‘As If’ principle (the field Wage type generation in the view Absence
Valuation Rule (V_554C_E) must be activated). This is done for absences whose processing type
has been changed to S or absences which are evaluated using function GWT A. All other absences
are valuated in the gross part of payroll.
n There is detailed information on absence valuation in the section on Absences in the payroll section
of the Implementation Guide (IMG).
© SAP AG
HR400
7-19
Time Wage Type Selection in Schemas
XT00
.
IF
IMPRT
PRINT
DAYPR
ELSE
DAYPR
ENDIF
General processing of time data INTERN.
PDC
B2
NP
ZL
TC00 PDC
TC00
TC00
.
MOD
TMOD GEN
.
DAYMO 01
02 02 02
GWT
S
DZL
GWT
M
ZML
.
PRINT NP
DZL
Is PDC active in period?
Import cluster B2
Print table of time wage types
Day processing of time data
PDC not active in period
Day processing of time data
Endif PDC
Processing time data/Wage type selection
Set modifiers
Set day modifier
Time wage type selection for planned work
Time wage type selection for overtime
Daily results: Wage types
 SAP AG 1999
n If time recording has been activated for the personnel number for which payroll is being run, this
indicates that time wage types already exist in cluster B2 of table ZL. This cluster is then imported,
and the system processes any days that have not yet been processed for the payroll period. The
wage types that still have to be generated are formed according to the work schedule, which
triggers retroactive accounting in the subsequent payroll period.
n Function DAYPR calls subschema TC00, which processes time wage type selection for planned
work and overtime on a daily basis.
© SAP AG
HR400
7-20
Time Wage Type Selection: Summary (1)
l In time wage type selection, time pairs
form wage types.
l Time wage type selection occurs using
rules that are stored in the Time Wage
Type Selection Rule table. The rules
enable you to control time wage type
selection according to employees, days
and times.
 SAP AG 1999
© SAP AG
HR400
7-21
Time Wage Type Selection: Summary (2)
l Time wage type selection can be processed
according to two groupings that are set up in
the Time Wage Type Selection Rule table:
The time wage type selection rule group
processes time wage type selection according
to the employee’s organizational assignment.
The day grouping processes time wage type
selection depending on certain factors applicable
to the day that is being evaluated.
 SAP AG 1999
© SAP AG
HR400
7-22
Exercises
Unit: Time Wage Type Selection
Topic: Generating Wage Types
• Adjusting personnel calculation rule TMOD to meet customer
requirements.
• Adjusting subschema TC00 to meet customer requirements.
• Defining time wage type generation rules.
Up to now, your company has paid overtime as employee remuneration
information. However, your employees are now able to record overtime
in the system themselves. You want to include the time pairs recorded
for overtime as time wage types in the payroll run. In the table Time
Wage Type Selection Rule, you want to create different rules for each of
the payroll areas in your company.
Time wage types 3nn1 to 3nn4, which were entered in the system as
employee remuneration information, must now be generated by the
system on the basis of overtime time pairs. For this reason, the table
Time Wage Type Selection Rule must include rules that are grouped
together in a time wage type selection rule group for each payroll
area. In this exercise, you should create the time wage type selection
rules for the payroll area to which you assigned your employee at
the time of hiring.
1.
First you must define the groupings. In the IMG, make a copy of personnel calculation
rule TMOD, and rename it ZTnn (nn = group number).
Then adjust personnel calculation rule ZTnn by querying the payroll area in the
decision operation. Change MODIF W to the value ww (ww = 10 + group number) for
your payroll area, and to the value 01 for the other payroll areas.
2.
Since personnel calculation rule TMOD is accessed from subschema TC00, an
adjustment is also required here.
Make a copy of subschema TC00, rename it ZCnn (nn = group number), change the
line that includes function MOD, and the line that accesses rule TMOD.
3.
Since subschema TC00 is called up from schema XT00, an adjustment is also required
here. Change the relevant line in schema ZTnn (nn = group number) accordingly.
© SAP AG
HR400
7-23
4.
Enter the generation rules for the following wage types:
- 3nn1
Up to 2 hours overtime
- 3nn2
3 or more hours overtime
- 3nn3
Overtime on Sundays
- 3nn4
Overtime on public holidays
Note:
According to the collective agreement for the company used in the course, public
holidays last from 00:00 midnight to 06:00 a.m. on the following day. The system
should also generate the public holiday bonus if the overtime time pair starts after
midnight, that is, on the following day.
5.
Test the generation rules you have created by entering overtime for your employee on
the following days in payroll period 05:
- On a working day
05:00 p.m. – 08:00 p.m.
- On a Sunday
10:00 a.m. – 01:00 p.m.
- On a public holiday
10:00 a.m. – 01:00 p.m.
- On the next working day
05:00 p.m. – 08:00 p.m.
Release the payroll for period 05, start the payroll run, and check the results.
© SAP AG
HR400
7-24
Solutions
Unit: Time Wage Type Selection
Topic: Wage Type Generation
1.
To define the groupings for the table Time Wage Type Selection Rule go to:
IMG à Payroll: International à Day Processing of Time Data à Day Processing
Functions à Define Groupings
Rule ZTnn, employee subgroup grouping 3:
OUTWPPAYSB
Payroll area?
**
All other
MODIF T = 02
TOUTWPPAYSB
MODIF W = 01
TOUTWPPAYSB
yy
Payroll area yy
MODIF T = 02
TOUTWPPAYSB
MODIF W = ww
TOUTWPPAYSB
© SAP AG
HR400
7-25
2.
To adjust schema TC00, go to:
Human resources à Payroll à International à Tools à Maintenance Tools à
Schema à Copy
from schema TC00
to schema
ZCnn
In subschema ZCnn, change the line that accesses rule TMOD as follows:
MOD
ZTnn
GEN
3.
To adjust subschema XT00 go to:
Human resources à Payroll à International à Tools à Maintenance Tools à
Schema à Change
In subschema ZTnn, change the line that accesses day processing of time data as
follows:
DAYPR
ZCnn
4.
To create generation rules for your wage types, go to:
IMG à Payroll: International à Day Processing of Time Data à Day Processing
Functions à Time Wage Type Selection Rule à Define Generation Rules
Make the following entries for your time wage type selection rule group ww in the
table:
ww
ww
ww
ww
ww
ww
ww
01
01
01
01
01
02
02
010
020
030
040
050
010
020
3nn1
3nn1
3nn2
3nn2
3nn4
3nn3
3nn4
01.01.YY
01.01.YY
01.01.YY
01.01.YY
01.01.YY
01.01.YY
01.01.YY
31.12.9999
31.12.9999
31.12.9999
31.12.9999
31.12.9999
31.12.9999
31.12.9999
Entry details are provided on the following pages
© SAP AG
HR400
7-26
Time wage type selection rule group:
Day grouping:
Sequential number:
Wage type:
ww
01
010
3nn1
Valid processing classes:
M
Week days:
1234567
xxxxxx
b123456789
x
b123456789
x
b123456789
xxxxxxxxxx
0123456789
xxxxxxxxxx
0123456789
xxxxxxxxxx
b123456789
xx
Public holiday class, previous day:
Public holiday class, current day:
Public holiday class next day:
Valuation class:
Daily work schedule class:
Day type
Start:
End:
Minimum:
Maximum:
2,00
Relevant processing types:
M
© SAP AG
HR400
7-27
Time wage type selection rule group:
Day grouping:
Sequential number:
Wage type:
ww
01
020
3nn1
Valid processing classes:
M
Week days:
1234567
xxxxxx
b123456789
xxxxxxxxx
b123456789
x
b123456789
xxxxxxxxxx
0123456789
xxxxxxxxxx
0123456789
xxxxxxxxxx
b123456789
xx
Public holiday class, previous day:
Public holiday class, current day:
Public holiday class next day:
Valuation class:
Daily work schedule class:
Day type
Start:
End:
Minimum:
Maximum:
06:00
24:00
Relevant processing types:
M
© SAP AG
2.00
HR400
7-28
Time wage type selection rule group:
Day grouping:
Sequential number:
Wage type:
ww
01
030
3nn2
Valid processing classes:
M
Week days:
1234567
xxxxxx
b123456789
x
b123456789
x
b123456789
xxxxxxxxxx
0123456789
xxxxxxxxxx
0123456789
xxxxxxxxxx
b123456789
xx
Public holiday class, previous day:
Public holiday class, current day:
Public holiday class next day:
Valuation class:
Daily work schedule class:
Day type
Start:
End:
Minimum:
Maximum:
2,00
Relevant processing types:
© SAP AG
M
HR400
7-29
Time wage type selectio n rule group:
Day grouping:
Sequential number:
Wage type:
ww
01
040
3nn2
Valid processing classes:
M
Week days:
1234567
xxxxxx
b123456789
xxxxxxxxx
b123456789
x
b123456789
xxxxxxxxxx
0123456789
xxxxxxxxxx
0123456789
xxxxxxxxxx
b123456789
xx
Public holiday class, previous day:
Public holiday class, current day:
Public holiday class next day:
Valuation class:
Daily work schedule class:
Day type
Start:
End:
Minimum:
Maximum:
06:00
24:00
2,00
Relevant processing types:
M
© SAP AG
HR400
7-30
Time wage type selection rule group:
Day grouping:
Sequential number:
Wage type:
ww
01
050
3nn4
Valid processing classes:
M
Week days:
1234567
xxxxxxx
b123456789
xxxxxxxxx
b123456789
x
b123456789
xxxxxxxxxx
0123456789
xxxxxxxxxx
0123456789
xxxxxxxxxx
b123456789
xx
Public holiday class, previous day:
Public holiday class, current day:
Public holiday class next day:
Valuation class:
Daily work schedule class:
Day type
Start:
End:
© SAP AG
06:00
HR400
7-31
Time wage type selection rule group:
Day grouping:
Sequential number:
Wage type:
ww
02
010
3nn3
Valid processing classes:
M
Week days:
1234567
x
b123456789
xxxxxxxxxx
b123456789
x
b123456789
xxxxxxxxxx
0123456789
xxxxxxxxxx
0123456789
xxxxxxxxxx
b123456789
xx
Public holiday class, previous day:
Public holiday class, current day:
Public holiday class next day:
Valuation class:
Daily work schedule class:
Day type
Start:
End:
© SAP AG
30:00
HR400
7-32
Time wage type selection rule group:
Day grouping:
Sequential number:
Wage type:
ww
02
020
3nn4
Valid processing classes:
M
Week days:
1234567
xxxxxxx
b123456789
xxxxxxxxxx
b123456789
xxxxxxxxx
b123456789
xxxxxxxxxx
0123456789
xxxxxxxxxx
0123456789
xxxxxxxxxx
b123456789
xx
Public holiday class, previous day:
Public holiday class, current day:
Public holiday class, next day:
Valuation class
Daily work schedule class:
Day type
Start:
End:
© SAP AG
30:00
HR400
7-33
5.
To test the generation rules, go to:
Human resources à Personnel Management à Administration à Maintain
Master Data à Time Mgmt Trans. Data à Overtime à Create
Choose the infotype Overtime, enter the overtime for the relevant dates and times, and
run payroll.
Human Resources à Payroll à International à Payroll à Release Payroll
Human Resources à Payroll à International à Payroll à Start Payroll
Human Resources à Payroll à International à Payroll à Exit Payroll
© SAP AG
HR400
7-34
Averages
Contents:
l
l
l
l
l
l
l
l
l
l
Valuating Time Wage Types
Elements of Average Processing
Creating Average Bases
Triggering the Valuation of Averages
Relevancy Rule for Average Calculation
Cumulation Rules for Average Bases
Calculating the Average Amount
Final Processing Rules and Comparison Rules
Adjustment Rules for Average Bases
Processing Averages in the Schema
 SAP AG 1999
© SAP AG
HR400
8-1
Averages: Unit Objectives
At the conclusion of this unit, you will be able to:
l Explain how to calculate average values for
wage types used in previous payroll periods
and how to valuate a wage type in the current
period using these average values.
l Check the relevancy of previous payroll periods.
l Adjust average values to an increase in an
employee's remuneration.
 SAP AG 1999
© SAP AG
HR400
8-2
Course Overview Diagram
Payroll Basics
Time Wage Type Selection
Personnel Calculation Rules
Averages
Starting Payroll
Factoring
Wage Type Valuation
Cumulation Wage Types
Absence Valuation
Retroactive Accounting
 SAP AG 1999
© SAP AG
HR400
8-3
Valuating Time Wage Types
Processing
INPUT TABLE
WT
RTE NUM AMT
X
WT
Transfer
X
X
OUTPUT TABLE
RTE
NUM AMT
X
Transfer
X
X
Multiply
X
X
X
X
Specify valuation
basis?
X
X
X
yes
no
Valuate using the
valuation basis
Valuate according to principle
of averages
 SAP AG 1999
n In personnel calculation rule X015, the system checks to see if the IT table contains time wage
types that have not yet been valuated. To do so, the system checks the contents of the value fields
AMT (amount), NUM (number) and RTE (rate).
n If the RTE or AMT field contains an amount, the wage type is transferred to the internal table OT.
n If the AMT field is empty, the NUM field contains a number and the RTE field a rate, then the
NUM field is multiplied by the RTE field. The result is stored in the amount field, and the wage
type transferred to table OT.
n If only the NUM field contains an entry because only a number (for example, hours) was entered,
and if the AMT and the RTE fields are both empty, the system queries whether a valuation basis
has been specified for the wage type. If this is the case, the wage type is valuated using the
valuation basis specified.
n If no valuation basis is specified, valuation takes place according to the principle of averages if a
average valuation is assigned to the wage type. If this is not the case, the wage type is not valuated
using a monetary value.
© SAP AG
HR400
8-4
Remuneration Using Averages
How can you create and
remunerate average values
using variable remuneration
for several payroll periods?
Sales
HR department
 SAP AG 1999
n If an employee is sick or is on leave, certain remuneration elements are reduced for the employee in
question (for example, commission, bonuses for piecework, overtime). Hence, the employer often
pays the average values of variable remuneration.
n You can also use the average calculation procedure in HR Payroll for different purposes. For
example, you can calculate average values for fixed payments.
© SAP AG
HR400
8-5
Elements of Average Processing
l Retrieving average bases
l Determining the previous periods required
l Performing a relevancy test for each period
l Cumulating the average bases from the relevant
previous periods
l Including changes in pay
l Calculating averages
 SAP AG 1999
n Collective agreements often contain rules that state that in the case of absences, an average
remuneration calculated from previous months must be paid. To valuate absences according to the
principle of averages, the following questions must first be answered:
n How many periods are used to create an average?
n Can a period be irrelevant to the creation of averages? (For example, if an employee takes unpaid
leave throughout the whole payroll period.)
n In such cases, what is the maximum number of periods that should be used to create averages?
n What triggers a payment based on an average value (for example, an absence)?
n What is the formula used to calculate the average value?
n What value is used for new employees in the first payroll period, if there are no previous values
available for calculating the average value?
n Should an average value be adjusted if remuneration changes (for example, after a standard pay
increase)?
n Which wage types are included in an average value?
© SAP AG
HR400
8-6
Creating Averages
Payroll periods
Average calculation bases
n -3
Variable remuneration A
Variable remuneration B
Basis A
n-2
Variable remuneration A
Variable remuneration B
Basis A
n -1
Variable remuneration A
Variable remuneration B
Basis A
Current period n
Remuneration with
average value
l Cumulation of basis for calculating
averages
l Calculation of average value by division
 SAP AG 1999
n Remuneration elements included in averages are grouped into average bases for the relevant payroll
period and stored together with the payroll results.
n In a payroll period, in which a wage type should be remunerated with an average value, the average
bases for the relevant previous periods are first of all cumulated. The average value is then
calculated (for example, by dividing the total by the number of previous periods). The resulting
value is then included in the employee's remuneration.
© SAP AG
HR400
8-7
Creating Bases for Calculating Average Values
Assigning Primary Wage Types to Bases for Calculating Average Values
CoGrp WT
99
Av.basis
M110 /201
Valid to
Valid from RTE
31.12.9999 01.01.1999 4
%
NUM
%
100
4
100
AMT %
Assigning Partial Period Parameters to Bases for Calculating Average Values
Part.per. Par. Av.basis
Valid from Valid to
TA
01.01.1999 31.12.9999
/205
Percent
100
 SAP AG 1999
n In this step, you specify which primary wage types and which partial period parameters should be
included in which average basis. The secondary wage types /201 to /232 are available as average
bases.
n Create various average bases, for example, all overtime remuneration, all overtime bonuses, all
work on public holidays, and so on.
n Specify which primary wage type should be included in which average basis. Specify which wage
type field (RTE, NUM, AMT) should be used with which percentage.
n You can include the following partial period parameters in the average bases. As the value of the
Number field is always read from partial period parameters, only specify the percentage here. For a
thorough presentation of the partial period parameters, see the unit on Factoring.
© SAP AG
HR400
8-8
Averages: Calculating Vacation Bonus
l The Caliber 'A' Bicycle Company pays a constant
vacation bonus for each day. This should be calculated
as the average of the overtime pay

SAP AG 1999
© SAP AG
HR400
8-9
Triggering the Valuation of Averages
Leave with Average Valuation of Wage Type M400 Vacation Bonus
Processing class
PRCL
15
Specification n
Is the average calculation
rule assigned?
yes
yes
New average calc. procedure
Function AVERA
Old average calc.procedure
PC rule X016 Operation MEANV
 SAP AG 1999
n If a valuation basis is not been specified, but a specification has been assigned to processing class
15, the wage type is valuated according to the old principle of averages. In this case, the system
accesses personnel calculation rule X016 (Special processing for the valuation of time wage types).
(For an explanation of the old average calculation procedure please see the appendix.)
n If you assign an average calculation rule to a wage type in the view V_T51AV_P, it is valuated
with the monetary value calculated by the new average calculation procedure.
n If processing class 15 is filled with a specification and is also assigned an average calculation rule
for a wage type, the wage type is valuated using the new average calculation procedure (if you use
the standard schema).
© SAP AG
HR400
8-10
Assigning Average Valuation to a Primary Wage Type
Assigning Wage Types to Average Calculation Rules
WType Text
Valid from Valid to
7520
01.01.1999 31.12.2005
Average
Av.rule
Av. rule text
Averages 1
 SAP AG 1999
n In this step, you must maintain all primary wage types that are to be valuated using an average.
These wage types are created in payroll either after they were generated from the attendances and
absences , or after you have entered them online, for example, in the infotypes 0015 or 2010.
n Specify which wage type should be evaluated according to which average calculation rule.
© SAP AG
HR400
8-11
Calculation Rules for Averages
Creating Calculation Rules for Averages
Av.rule
Text
Valid from
Valid to
ZAV1
ZAV2
Averages 1 . .
01.01.1999
31.12.2005
A = The value is frozen for the length of the absence
1 = The value is frozen for the calendar year (Jan.01-Dec.31)
4 = The value is frozen for one year (April 01-March 03)
Rel.R.
Cum.R. FProc. Comp.R.
Rel.R. TU
max .P. TU current freeze
ZREL
ZCU1
3
6
ZEND
ZCOM
1
1
4
WT
A
1 = Calendar month
3 = Calendar weeks (in acc. with feature LDAYW)
5 = Rolling month
 SAP AG 1999
n Create the calculation rules using the previously defined relevancy rules, cumulation rules, final
processing rules and comparison rules.
n Specify from how many previous periods the relevant average periods should be selected, and if the
current period should be included. Select a time unit for the relevant average periods.
n Specify if the calculated average value should be frozen. The rate is then stored in the AVERAGE
table in the payroll results. For example : In the case of an absence covering several payroll periods,
the calculated average value should be used throughout, or an average value that was calculated in
the first payroll period of the year should be used in all the payroll periods in the year.
n If you want to use a relevancy test to determine the relevant period, you must enter the maximum
number of relevant periods and the time unit you require.
n If it should be possible to pay the employee a definite amount instead of the calculated value, enter
the wage type you wish to use for this purpose.
n You can specify which weekday should be the last day in a calendar week with the help of feature
LDAYW. If you want to change the feature, please consider that this will also affect Time
Management!
© SAP AG
HR400
8-12
Relevancy Rule for Average Calculation
Checking the legal person
Checking for re-hiring
Creating the Relevancy Rule for Average Calculation
Rel.rule
LegPers. Rehiring
Part.rel.
RelAvPer.
ZREL
N
N
1
N
Funct.mod.
Behaviour for partially relevant periods
Behaviour for relevancy of the averages period
 SAP AG 1999
n Here, you specify whether an average period should be relevant or should not be relevant for the
calculation of averages under the conditions specified. You can use any four-digit sequence of
characters starting with the letter Z or a number between 0 and 9 as a name range.
n If you do not use a relevancy rule, the system uses all the average periods for average calculation.
n Define processing of the relevancy test when the legal person changes: Check (Y) or no check (N).
n Define processing of the relevancy test when the employee is rehired: Check (Y) or no check (N).
n Define processing of the relevancy test for partially relevant periods: No check (N), only take the
results that do not overlap into consideration (C) or take all the results into consideration (A).
n Define processing of the period's relevancy: Average period is relevant if a result (1) or if all results
(A) are relevant.
n If you perform a relevancy test with a function module, you specify it's name. The module provided
depends on the country version.
© SAP AG
HR400
8-13
Excluding the Relevancy of Off-Cycle Reasons
Excluding the Relevancy of Off-Cycle Reasons
Rel.rule
Relevancy rule text
OC-reason
Description
ZREL
Rel.test for incentive wages
0001
Holiday bonus
 SAP AG 1999
n If you do not use Off-Cycle Payroll, you do not need to make these settings.
n Otherwise, you specify which Off-Cycle payroll runs should no longer be taken into consideration.
© SAP AG
HR400
8-14
Cumulation Rules for Average Bases
Field to be cumulated
Cumulation type (+ or -)
Multiplication with the adjustment
factor from the adjustment rule
Average basis to be
cumulated
Cumulation Rules for Average Bases
Cum.rule
Av.basis
Valid from
Valid to
RTE + AR
ZCU1
ZCU1
/201
/202
01.01.1999
01.01.1999
31.12.2005
31.12.2005
NUM + AR
AMT + AR
4
4
4
4
Factor.
+ ZADJ
+ ZADJ
Processing for periods to be partially cumulated
F = Factoring according to calendar days
S = Use WPBP split (Error when none exist)
N = Use total value
 SAP AG 1999
n In the cumulation rules, specify which average value calculation basis wage types /2nn should be
used. When doing so, you determine which field (RTE, NUM, AMT) should be used to cumulate
the wage types and if the cumulation should be positive (+) or negative (-). If you do not make any
entries, the relevant field is not cumulated.
n If you have created adjustment rules and these should be used when cumulating, enter the
adjustment rule required for every field.
© SAP AG
HR400
8-15
Modifying Average Formulas
Modifying Average Formula (Personnel Calculation Rule)
Calculating the average after cumulation
X018
E
*
E
Cumulation table MV
****
Rule
NUM
NUM?0.00
ZAV1
20
E
ZAV2
NUM=M
E
*
RTE
AMT
500
AMT=M
DIVID ANR
=
Work area
NUM
RTE
AMT
for wage type
20
25
500
 SAP AG 1999
n An average calculation must result in the Rate (RTE) field containing a valuation basis. The
formula used to calculate this value is included in personnel calculation rule X018.
n The internal table MV contains the cumulations for averages.
n Standard rule X018 uses the formula amount/number to calculate hourly rates.
© SAP AG
HR400
8-16
Final Processing Rules and Comparison Rules
Final Processing Rules for Averages
F.process.
Calc.rule
Short description
ZEND
Z018
Divide amount by the standard workdays
Comp. WT is greater than average value
Use comp. WT
Creating Comparison Rule for Average Calculation
Comp.rule
WT
Field
Comparison
ZCOM
4711
AMT
>

> = Comp.wage type is greater than av.value:
Use comparison wage type
< = Comp.wage type is smaller than av.value:
Use average value
SAP AG 1999
n Create the final processing rules that you require. You can reselect certain periods for final
processing from the relevant average periods and store a delivered or modified final processing
rule.
n Define the comparison rules for calculated average values. If you do not want to compare the
calculated average value, you do not need to make any settings.
n The calculated value can be compared with a value specified here, for example, the standard pay.
Specify under which conditions which value should be used. The system then uses the calculated
value or the comparison value accordingly as the average value.
© SAP AG
HR400
8-17
Adjustment Rules
Positive/negative adjustment
No.of periods to be adjusted
and the time unit for the
average periods
Adjustment type
Creating Adjustment Rule
Adj.rule
Description
Adj.type +/- Comp.WT
No.periods TmeUnit WgeType
ZADJ
3 months
4
3
P
/001
Comparison wage type
for determining the
factor for adjustment type 4
01
Wage type for individual
adjustment of the average
bases
 SAP AG 1999
n If you need to adjust the average bases to retroactively increased payments for the employee, you
must create an adjustment rule that you can then use in the cumulation rules. For each rule, specify
which adjustment type (multiplication factor) should be used to adjust the average bases or if the
adjustment should be made for individual employees using a wage type. In Release 4.6B, you can
only use adjustment type 4. In the Comparison wage type field, enter the required 0nn wage type.
n Decide whether the adjustment should only take place in the case of a positive multiplication factor
(P) or also for a negative factor (B).
n Determine the number of periods to be adjusted retroactively and the time unit for the average
periods.
n If you want to retroactively adjust the average bases in your own way, specify a wage type here. In
this way, you override the adjustment rule. In the payroll period in which the change of average
bases becomes effective, use this wage type to assign an individual percentage to your employee,
usually an increase percentage. To do so, enter the percentage, where, for example, '105'
corresponds to an increase of 5% and '95' corresponds to a reduction of 5%, in the amount field for
the wage type in the master data.
© SAP AG
HR400
8-18
Processing Averages in the Schema
XT00
.
MOD
RAB
.
DAYPR
.
PAB
.
P2010
.
PIT
AVERA
.
General processing of time data INTERN.
XMOD
GEN
Determine payroll modifiers
Import absences
TC00
Day processing of time data
Edit absence data
X930
GEN
X015
GEN
NOAB
Edit employee remuneration information
Valuation of time wage type
Calculation of averages
 SAP AG 1999
n Once time data and employee remuneration information have been processed, time wage types are
entered in internal table IT. Personnel calculation rule X015 then determines which wage types
only have a value in the NUM field. If a valuation basis has been specified for a relevant wage type,
it is used in personnel calculation rule X115 to valuate the wage type.
n If processing class 15 has been maintained for the relevant wage type, personnel calculation rules
X016, X017 and X018 are used to calculate the averages.
n The AVERA function selects the wage types that are to be evaluated in accordance with the new
average calculation procedure (from 4.6A).
© SAP AG
HR400
8-19
Averages: Summary (1)
l Time wage types can be evaluated using the average
values of wage types if an average value
was assigned in Customizing. The average values
can be calculated from wage types from periods already
included in a payroll run and/or from the current period.
 SAP AG 1999
© SAP AG
HR400
8-20
Averages: Summary (2)
l To calculate average values, you must specify
how the relevant wage types are to be included
in the valuation bases. The number of payroll periods
required already included in a payroll run is entered in
the calculation rule. You can run a relevancy
check for each period. The cumulation rule determines
the type of cumulation used to calculate the
average bases for the relevant periods.
Changes in pay can be stored in the adjustment rule.
l The average values calculated can be frozen.
 SAP AG 1999
© SAP AG
HR400
8-21
Averages-Exercises:
New Averages
Unit: Averages
Topic: Creating Average Calculation Bases
• Creating average calculation bases from overtime remuneration.
Your company decides to change vacation bonus provisions. Instead of a
fixed amount per leave day, the average of all remuneration paid for
overtime over the past four payroll periods will be paid for each leave
day.
To create the average calculation bases, you must flag the following time wage types:
-
3nn1
3nn2
3nn3
3nn4
Up to 2 hours overtime
3 or more hours overtime
Overtime on Sundays
Overtime on public holidays
and the derived bonus wage types 3nn5 - 3nn8 as relevant for the calculation of averages.
The contents of the AMT (amount) field for wage types 3nn1 to 3nn4 must be added to the
average basis /201.
The total amount for the bonus wage types 3nn5 to 3nn8 must be added to the average basis
/202.
This ensures that /201 contains all overtime remuneration, and that /202 contains the bonuses
for the calculation of averages.
Run payroll for period 05, together with a forced retroactive accounting run for the previous
periods. Check that the wage types have been created. Exit the payroll run.
The validity period of the Customizing entries for the average
calculation procedure runs from January 01 of the relevant calendar
year until December 12, 9999
© SAP AG
HR400
8-22
Unit: Averages
Topic: Average Calculation Rules
•
Creating cumulation rules for average bases
•
Adjusting personnel calculation rule X018 to meet customer
requirements.
•
Creating a final processing rule
•
Creating an average calculation rule
• Assigning an average calculation rule to a wage type
Until now, your company has constantly valuated wage type 40nn with
20.00 per leave day. From payroll period 06 onwards, employees will be
paid the average of all the overtime remuneration paid over the past three
payroll periods for each leave day.
1.
Valuation of wage type 40nn Vacation bonus, which was previously constant at 20,
must now be delimited. Delimit the existing entry for the wage type to the start date of
payroll period 06, and remove the indicator for constant valuation from the new record.
2.
Payment must be made in the period for which payroll is being run, that is, absence
valuation for wage type 40nn must be set to ‘I’.
3.
Create a cumulation rule for both the cumulation of overtime remuneration in wage
type /201 and for the cumulation of the bonuses in /202. The contents of the AMT field
should be cumulated positively.
Call your cumulation rule ZC## (## = group number), for example, ZC01 for group 1.
4.
Adjust the average formula. Copy personnel calculation rule X018 to Z8## and store an
average calculation formula that divides the average of the total cumulated average
calculation formulas by the standard number of workdays in three payroll periods.
5.
Create your final processing rule ZE## with your personnel calculation rule Z8##.
6.
Now, set up your calculation rule for averages, ZA##.
7.
For your wage type 40nn, store the assignment to your average calculation rule.
8.
Enter a few days leave for your employee in payroll period 06, release and then start
payroll for the period.
© SAP AG
HR400
8-23
Unit: Averages
Topic: Adjusting Average Calculation Bases
• Adjusting the average calculation bases when there is a change in
remuneration.
The new vacation bonus provision in your company specifies that an
employee's vacation bonus must be adjusted to increases in his/her pay.
The bases for calculating average values must therefore be adjusted by
the relevant factor in the three previous payroll periods. The factor is
determined by the difference in valuation basis /001 before and after the
increase in pay.
1.
Increase your employee's basic pay from the start of payroll period 06 by increasing
direct bonus wage type 50nn (nn = group number) to 500.00.
2.
Now, create the adjustment rule ZJ## for your calculation rule ZA## (## = group
number).
3.
Finally, modify your cumulation rule ZC##, by entering your adjustment rule in the
AMT field.
4.
Repeat the payroll run for payroll period 06.
© SAP AG
HR400
8-24
Unit: Averages
Topic: Frozen Averages
• Freezing the average value for an absence covering several payroll
periods
The new vacation bonus provisions in your company specify that an
employee's vacation bonus must be constant for all leave days. To also
guarantee that this is the case for absences covering several payroll
periods, the calculated average value in the period, in which the absence
starts, must be frozen for the duration of the absence.
1.
Modify your calculation rule ZA## (## = group number).
2.
Finally, enter additional leave for your employee starting in payroll period 05 and
ending in period 06. Repeat the payroll run for payroll period 06 and check the log.
Finally, exit the payroll run.
© SAP AG
HR400
8-25
Exercises: Old Averages
Unit: Averages
Topic: Creating Average Calculation Bases
• Creating average calculation bases from overtime remuneration.
Your company decides to change vacation bonus provisions. Instead of a
fixed amount per leave day, the average of all overtime remuneration
paid over the past four payroll periods will be paid for each leave day.
To create the average calculation bases, you must flag the following time wage types:
-
3nn1
3nn2
3nn3
3nn4
Up to 2 hours overtime
3 or more hours overtime
Overtime on Sundays
Overtime on public holidays
and the derived bonus wage types 3nn5 - 3nn8 as relevant for the calculation of averages.
The contents of the AMT (amount) field for wage types 3nn1 to 3nn4 must be added to the
average basis /201.
The amount of the bonus wage types 3nn5 to 3nn8 must be completely added to the average
basis /202.
This ensures that /201 contains all overtime remuneration, and /202 contains the bonuses for
the calculation of averages.
Run payroll for period 05, together with a forced retroactive accounting run for the previous
periods. Check that the wage types have been created. Exit the payroll run.
© SAP AG
HR400
8-26
Unit: Averages
Topic: Average Calculation Rules
• Adding further specifications to a processing class
• Coding wage types for valuation with an average value.
• Adjusting personnel calculation rule X016 to meet customer
requirements.
• Creating average calculation rules and cumulation rules.
• Checking the relevancy of previous periods for the calculation of
averages.
• Adjusting personnel calculation rule X018 to meet customer
requirements.
Until now, your company has constantly valuated wage type 40nn with
20.00 per leave day. As of payroll period 06, employees will be paid the
average of all overtime remuneration paid over the past four payroll
periods for each leave day.
1.
You must now delimit valuation of wage type 40nn Vacation Bonus, which was
previously constant at 20. Delimit the existing entry for the wage type with the start
date of payroll period 06, and remove the indicator for constant valuation from the new
record.
2.
Payment must be made in the period for which payroll is being run, in other words,
absence valuation for wage type 40nn must be set to ‘I’.
3.
To valuate a wage type using an average value, you must code the wage type in
processing class 15 with the specification that corresponds to the relevant average
calculation rule. To enter your own average calculation rules in the system, you must
first of all create a new specification for each calculation rule in processing class 15.
Add the specification of processing class 15 planned for your group. Note: For
technical reasons, specifications of processing class 15 are used that are outside the
customer name range (Z):
Group 01 = I
Group 02 = J
Group 03 = K
Group 04 = L
Group 05 = M
Group 06 = N
© SAP AG
Group 07 = O
Group 08 = P
Group 09 = Q
Group 10 = R
Group 11 = S
Group 12 = T
Group 13 = U
Group 14 = V
Group 15 = W
Group 16 = X
Group 17 = Y
Group 18 = Z
HR400
8-27
4.
Code wage type 40nn in processing class 15 with the specification for your group.
You have made all the necessary preparations in the area of wage
types for the new averages rule. Now, you must make sure that the
system accesses the average calculation rule in your schema when
valuating wage types.
You have already created your own specification for processing
class 15, and coded wage type 40nn accordingly. Personnel
calculation rule X016 queries processing class 15, and the
specification tells the system which average calculation rule should
be used.
5.
Copy personnel calculation rule X016 to the name Z6nn (nn = group no.) and modify it
by adding a line for your specification of the processing class when processing class 15
is queried. You must assign average calculation rule zz to operation MEANV.
(zz = 10 + Group number)
The modified subschema ZTnn accesses the valuation of time
wage types in the line PIT X015 GEN. Rule X015 calls
continuation rule X016. However, you previously created a
modified version of rule X016 and named it Z6 nn. Therefore, you
now also require a modified version of rule X015 that is accessed
from the modified subschema ZTnn.
6.
Copy personnel calculation rule X015 to Z5nn (nn = group number), and change access
of rule X016 accordingly.
7.
Change modified subschema ZTnn in the line that accesses time wage valuation.
8.
To prepare for creation of the average calculation rules, copy personnel calculation rule
X018 to Z8nn (nn = group number).
In personnel calculation rule Z6nn, you already created a link
between your specification in processing class 15 and average value
calculation rule zz. Now you must create the average calculation
rule zz as well as cumulation rule zz, and set up final processing in
rule Z8nn.
9.
Create the average calculation rule zz. Set the number of relevant previous periods and
the maximum number of previous periods to 4. In the Cumulation rule field, enter the
same value as for the averages rule.
10.
Define cumulation rule zz by taking all the overtime remuneration (/201) into account.
Note: Once you have completed the exercise, you can modify the cumulation rule and
also include the bonuses (201 + /202) for cumulation. Test this scenario as well.
11.
Create an average calculation formula in rule Z8nn that divides the total of all
cumulated overtime remuneration by the average number of workdays in four payroll
periods.
12.
Enter a few days leave for your employee in payroll period 06, release and then start
payroll for the period.
© SAP AG
HR400
8-28
Unit: Averages
Topic: Adjusting Average Calculation Bases
• Adjusting the average calculation bases when there is a change in
remuneration.
The new vacation bonus provisions in your company specify that an
employee's vacation bonus must be adjusted to increases in his/her pay.
The average calculation bases of the last three previous periods must
therefore be adjusted by the relevant factor. The factor is determined by
the difference in valuation basis /001 before and after the increase in
pay.
1.
Increase your employee's basic pay from the start of payroll period 06 by increasing the
direct bonus wage type 50nn (nn = group number) to 500.00.
2.
Create adjustment rule zz for your calculation rule zz. You must enter a relevant
modification indicator in the AMT (amount) field for the adjustment type. Also specify
the number of previous periods to be taken into account. With regard to your employee,
at least three periods must be taken into account for the increase factor to be effective.
3.
Repeat the payroll run for payroll period 06. Finally, exit the payroll run.
© SAP AG
HR400
8-29
Solutions: New Averages
Unit: Averages
Topic: Creating Average Calculation Bases
Identifying time wage types and the bonus wage types derived from them as relevant to the
calculation of averages.
IMG à Payroll: International à Time Wage Type Valuation à Averages New à Create
Bases for Calculating Average Values
Choose the action Calculating Average Bases from Wage Types.
For the overtime wage types 3nn1 – 3nn4, flag the Amount field and enter 100 in the
Percentage field.
Then, select the bonus wage types 3nn5 – 3nn8, in order to copy them. In the Basis for
calculating average field for the entries to be copied, enter /202. Also flag the Amount field
and enter 100 in the Percentage field for these wage types.
Finally delete the entries for the bonus wage types 3nn5 – 3nn8 with the valuation basis /201!
Perform payroll for period 05:
Human Resources à Payroll à International à Payroll à Start Payroll
Exit payroll:
Human Resources à Payroll à International à Payroll à Exit Payroll
© SAP AG
HR400
8-30
Unit: Averages
Topic: Average Calculation Rules
1.
Delimiting valuation of wage type 40nn, and deleting the identifier for constant
valuation from the new record:
IMG à Payroll: International à Time Wage Type Valuation à Valuation Bases à
Assigning Valuation Bases
Choose Delimit, and then enter the start date of payroll period 06. Edit the delimited
entry by deleting K for the valuation basis.
2.
Setting the valuation of absences for wage type 40nn to ‘I’:
IMG à Payroll: International à Absences à Valuation of Absences à Create
Counting Classes for Absence Valuation à Absence Valuation: Expert View
Change your entry as follows:
Abs.val.grp:
yy
Valuation rule: 01
Time:
I
3.
Creating cumulation rule ZC##:
IMG à Payroll: International à Time Wage Type Valuation à Averages New à
Create Calculation Rule for Averages
Choose the action Cumulation Rules for Bases for Calculating Average Values.
Create the following rule:
Cum.rule
Av. basis
ZC##
ZC##
© SAP AG
RTE
+
NUM
AMT
+
/201
!
+
/202
!
+
HR400
+
8-31
4.
Modifying average formulas
IMG à Payroll: International à Time Wage Type Valuation à Averages New à
Create Calculation Rule for Averages
Choose the action Modify average formula (personnel calculation rule).
Copy rule X018 to Z8## and change your rule in the fo llowing way:
pauschalierte Anzahl
NUM=
AMT=M
DIVID ANR
5.
Create final processing rule ZE##:
IMG à Payroll: International à Time Wage Type Valuation à Averages New à
Create Calculation Rule for Averages
Choose the action Final processing rules for averages.
Create the following rule :
6.
Final processing
Formula
ZE##
Z8##
Create calculation rule for averages ZA##:
IMG à Payroll: International à Time Wage Type Valuation à Averages New à
Create Calculation Rule for Averages
Choose the action Create calculation rules for averages.
Create the following rule:
Av.rule
Cum. rule
Fin.processing
Rel. av.per.
Time unit
ZA##
ZC##
ZE##
3
1
© SAP AG
HR400
8-32
7.
Assign average calculation rule wage type 40nn:
IMG à Payroll: International à Time Wage Type Valuation à New Averages à
Assign the Valuation of Averages to a Primary Wage Type
Create the following entry:
8.
WT
Av.rule
40nn
ZA##
Check averages processing:
Human Resources à Payroll à International à Payroll à Release Payroll
Human Resources à Payroll à International à Payroll à Start Payroll
© SAP AG
HR400
8-33
Unit: Averages
Topic: Adjusting Average Calculation Bases
1.
Increase basic pay by direct bonus wage type 50nn (nn = group number):
Human Resources à Personnel Management à Administration à Maintain
Master Data
2.
Create adjustment rule ZJ##:
IMG à Payroll: International à Time Wage Type Valuation à Averages New à
Create Calculation Rule for Averages
Choose the action Create adjustment rules.
Create the following rule:
3.
Adj.rule
Adj.type
+/-
Com.wage type
Modif.per.
Time unit
ZJ##
4
P
/001
3
1
Change cumulation rule ZC##:
IMG à Payroll: International à Time Wage Type Valuation à Averages New à
Create Calculation Rule for Averages
Choose the action Cumulation Rules for Bases for Calculating Average Values.
Change your rule:
4.
Cum.rule
Av. basis
....
AMT
+
Adjustment rule
ZC##
ZC##
/201
/202
....
....
!
!
+
+
ZJ##
ZJ##
Repeat the payroll run for payroll period 06:
Human Resources à Payroll à International à Payroll à Start Payroll
© SAP AG
HR400
8-34
Unit: Averages
Topic: Frozen Averages
1.
Modify calculation rule for averages ZA##:
IMG à Payroll: International à Time Wage Type Valuation à Averages New à
Create Calculation Rule for Averages
Choose the action Create calculation rules for averages.
Change your rule:
2.
Av.rule
Cum. rule
Fin.processing
Rel. av.per.
Time unit
freeze
ZA##
ZC##
ZE##
3
1
A
Repeat the payroll run for payroll period 06 and exit:
Human Resources à Payroll à International à Payroll à Start Payroll
Human Resources à Payroll à International à Payroll à Exit payroll
© SAP AG
HR400
8-35
Solutions: Old Averages
Unit: Averages
Topic: Creating Average Calculation Bases
Identifying time wage types and the bonus wage types derived from them as relevant to the
calculation of averages.
IMG à Payroll: International à Time Wage Type Valuation à Averages à Create Bases
for Calculating Average Values
Set flags in the following lines for wage types 3nn1 – 3nn4:
AMT
/201
x
x
Select AMT for the bonus wage types x
/202
x
Human Resources à Payroll à International à Payroll à Start Payroll
© SAP AG
HR400
8-36
Unit: Averages
Topic: Average Calculation Rules
1.
Delimiting valuation of wage type 40nn, and deleting the identifier for constant
valuation from the new record:
IMG à Payroll: International à Time Wage Type Valuation à Valuation Bases à
Assigning Valuation Bases
Choose Delimit, and then enter the start date of payroll period 06. Edit the delimited
entry by deleting K for the valuation basis.
2.
To valuation of absences must be set to the time ‘I’ for wage type 40nn:
IMG à Payroll: International à Absences à Valuation of Absences à Create
Counting Classes for Absence Valuation à Absence Valuation: Expert View
Change your entry as follows:
Abs.val.grp:
yy
Valuation rule: 01
Time:
I
3.
Create a specification in processing class 15:
IMG à Payroll: International à Basic Settings à Environment of Wage Type
Maintenance à Processing Classes and Evaluation Classes à Maintain Processing
Classes and Their Specifications
Select processing class 15 and use navigation to choose the specifications.
Then, add your new entry.
4.
Code wage type 40nn with a specification in processing class 15:
IMG à Payroll: International à Time Wage Type Valuation à Averages à Assign
the Valuation of Averages to a Primary Wage Type
5.
Copy and modify rule X016:
IMG à Payroll: International à Time Wage Type Valuation à Averages à Adjust
Calculation of Averages Within the Payroll Run à Copy ‘special processing for time
wage type valuation’ rule
from rule
to rule
© SAP AG
X016
Z6nn
HR400
8-37
6.
Copy rule X015, and change the access of rule X016:
IMG à Payroll: International à Time Wage Type Valuation à Averages à Adjust
Calculation of Averages Within the Payroll Run à Copy ‘valuation of wage types
rule’
from rule
to rule
X015
Z5nn
In rule Z5nn, change the line that accesses rule X016:
from GCY X016*
to
GCY Z6nn*
7.
Change modified subschema ZTnn in the line that accesses the valuation of time wage
types:
IMG à Payroll: International à Time Wage Type Valuation à Averages à
Adjust Calculation of Averages Within the Payroll Run à Enter Modified Personnel
Calculation Rule in Schema
The IMG offers you schema XT00 for processing. To edit your schema, choose
Schema à Different schema, and enter ZTnn.
Change the line specifying PIT X015 GEN to PIT Z5nn GEN.
8.
Copy personnel calculation rule X018:
IMG à Payroll: International à Time Wage Type Valuation à Averages à
Create Final Processing Rule
Copy from rule X018
to rule
Z8nn
9.
Create average calculation rule xx:
IMG à Payroll: International à Time Wage Type Valuation à Averages à
Create Calculation Rule for Averages
Create the following rule:
Rule
Rel.test
Cumulation
F.process.
Max.no.per
No.rel.per
zz
X017
zz
Z8nn
4
4
© SAP AG
HR400
8-38
10.
Define cumulation rule xx:
IMG à Payroll: International à Time Wage Type Valuation à Averages à
Create Cumulation Rules for Bases for Calculating Averages
Create the following rule:
Cumulation
WT
zz
/201
CumNUM
CumRTE
CumAMT
Adjust.
+
You can also create the following cumulation rule:
zz
11.
/202
+
Create a final processing rule:
IMG à Payroll: International à Time Wage Type Valuation à Averages à
Create Final Processing Rule
Change rule Z8nn:
pauschalierte Anzahl
NUM=
AMT=M
DIVID ANR
12.
Check averages processing:
Human Resources à Payroll à International à Payroll à Release Payroll
Human Resources à Payroll à International à Payroll à Start Payroll
© SAP AG
HR400
8-39
Unit: Averages
Topic: Adjusting Average Calculation Bases
1.
Increase basic pay by direct bonus wage type 50nn (nn = group number):
Human Resources à Personnel Management à Administration à Maintain
Master Data
2.
Create adjustment rule zz for calculation rule zz:
IMG à Payroll: International à Time Wage Type Valuation à Averages à
Create Cumulation Rules for Bases for Calculating Averages
Change cumulation rule zz by entering adjustment rule zz in the field Adjustment.
Then, use navigation to access the adjustment rules for the average calculation bases
and create the following rule:
Adjustment
zz
3.
...
IndAMT
VBasisID
4
01
...
No.period
3
Repeat the payroll run for payroll period 06:
Human Resources à Payroll à International à Payroll à Start Payroll
Human Resources à Payroll à International à Payroll à Exit Payroll
© SAP AG
HR400
8-40
Factoring
Contents:
l
l
l
l
l
l
l
l
l
l
l
The Factoring Concept
Partial Period Factors
Personal Work Schedule
Partial Period Parameters
Factoring Methods
Personnel Calculation Rules for Factoring
Assigning Partial Period Factors
Valuating Elements of Remuneration
Creating Wage Types for Cost Accounting
Creating Hourly Rates for Cost Accounting
Factoring in the Schema
 SAP AG 1999
© SAP AG
HR400
9-1
Factoring: Unit Objectives
At the conclusion of this unit, you will be able to:
l Describe the factoring concept and diverse
factoring methods.
l Create personnel calculation rules to
calculate partial period factors, and assign
the factors to the wage types to be factored.
l Explain how to create wage types for Cost
Accounting.
 SAP AG 1999
© SAP AG
HR400
9-2
Course Overview Diagram
Payroll Basics
Time Wage Type Selection
Personnel Calculation Rules
Averages
Starting Payroll
Factoring
Wage Type Valuation
Cumulation Wage Types
Absence Valuation
Retroactive Accounting
 SAP AG 1999
© SAP AG
HR400
9-3
The Factoring Concept
l Reduction in pay
n Joining or leaving company during payroll period
n Unpaid absences
n Paid absences
n Inactive work relationship
l Calculation of pay for exact periods
n Changes to basic pay
n Change in organizational assignment
n Change in personal work schedule
l Calculation of cost accounting wage types
for exact periods
 SAP AG 1999
n Within SAP Payroll, factoring describes the pro rata calculation of remuneration for an exact
period. Periodic remuneration consists of primary wage types assigned to an employee as basic pay,
recurring payments, or additional payments. Factoring only covers the events that occur in the
current period.
n During the payroll run, the system evaluates changes relevant to factoring in the following
infotypes:
•
Personnel Actions (0000)
•
Organizational Assignment (0001)
•
Planned Working Time (0007)
•
Basic Pay (0008)
•
Recurring Payments/Deductions (0014)
•
Additional Payments (0015)
•
Absences (2001)
If a situation arises during the payroll run that triggers factoring, the current factor is calculated and
then multiplied by the wage type assigned.
© SAP AG
HR400
9-4
Factoring: Periodic Remuneration
l In the Caliber ‘A’ Bicycle Company,
an employee’s remuneration changes
in the middle of the payroll period.
 SAP AG 1999
© SAP AG
HR400
9-5
Partial Period Factors
Change in basic pay midway
through the payroll period
Table IT before factoring
M020
M020
01
02
Partial period factor
Partial period 01 = ~ 0.5
Partial period 02 = ~ 0.5
3,000
3,500
Multiplied by partial period factor
Table IT after factoring
M020
M020
01
02
1,500
1,750
 SAP AG 1999
n In payroll, a factor is required to calculate partial period amounts.
n The partial period factor is a value between 0 and 1. As soon as changes are made to master data
that trigger factoring, the factor is multiplied by the employee's primary wage types for exact
periods if the primary wage types must be reduced, or if their constituents for exact periods must be
calculated separately.
n The calculation of partial period factors is always based on times that result, for example, from the
employee's personal work schedule or absences.
© SAP AG
HR400
9-6
Personal Work Schedule
Date
DWS
grpg
Daily
WS
Day type
PHol
class
31.12.1998
01.01.1999
02.01.1999
03.01.1999
04.01.1999
05.01.1999
06.01.1999
07.01.1999
08.01.1999
09.01.1999
10.01.1999
11.01.1999
01
01
01
01
01
01
01
01
01
01
01
01
FLEX
FLEX
FLEX
OFF
OFF
FLEX
FLEX
FLEX
FLEX
FLEX
OFF
OFF
0
1
0
0
0
0
0
0
0
0
0
0
0
1
0
0
0
0
0
0
0
0
0
0
01
01
01
01
01
01
FLEX
FLEX
FLEX
FLEX
OFF
OFF
0
0
0
0
0
0
0
0
0
0
0
0
Variant
B
B
DWS
class
Period
WS
Hours
Active
5
5
5
0
0
5
5
5
5
5
0
0
FLEX
FLEX
FLEX
FLEX
FLEX
FLEX
FLEX
FLEX
FLEX
FLEX
FLEX
FLEX
8,00
8,00
5,00
0,00
0,00
8,00
8,00
8,00
8,00
5,00
0,00
0,00
X
X
X
X
X
X
X
X
X
X
X
5
5
5
5
0
0
FLEX
FLEX
FLEX
FLEX
FLEX
FLEX
8,00
8,00
8,00
5,00
0,00
0,00
X
X
X
X
X
X
......
27.01.1999
28.01.1999
29.01.1999
30.01.1999
31.01.1999
01.02.1999
0
1
2
3
=
=
=
=
Work/paid
Day off/paid
Day off/unpaid
Special day
B
0 = No public holiday
1 = Public holiday
2 = Half-day pub. hol.
0
= Day off
1 - 9 = Can be defined
freely
 SAP AG 1999
n At the start of subschema XT00, function GENPS generates the personal work schedule for the
personnel number for which payroll is being run. For time data evaluation, each employee is
assigned to a general work schedule (infotype 0007) which defines planned working time on the
basis of the relevant employee's work center assignment. If the employee is assigned to different
work schedules during a payroll period due to a change of work center or substitution (infotype
2003), his or her planned working time will comprise several general work schedules.
n The above diagram is an excerpt of table PWS for one personnel number with a monthly payroll
period. The table specifies the last day of the previous payroll period and the first day of the
subsequent payroll period as the system requires this data if, for example, the relevant day is a
public holiday.
© SAP AG
HR400
9-7
Displaying Partial Period Parameters (1)
Total working
time projected
for period
T
No From To KSoll ASoll
SSoll
01
02
78.80 31.00
82.60 31.00
G
15.00 11.00
16.00 11.00
31.00 22.00 161.40
KDiv I ADiv I SDiv I
31.00
01
02
G
SDivP
161.40
161.40
30.00
30.00
22.00
22.00
156.48
156.48
22.00
161.40
30.00
22.00
156.48
KAX** AAX**
SAX**
0.00
2.00
0.00
1.00
0.00
8.00
4.00
1.00
4.00
1.00
32.00
8.00
1.00
0.00
1.00
0.00
8.00
0.00
2.00
1.00
8.00
5.00
5.00
40.00
1.00
1.00
8.00
Unpaid
absences
T = Partial period
G = Whole period
 SAP AG 1999
KDivP ADivP
22.00
22.00
No From To KAU** AAU** SAU** KAP** AAP** SAP**
T
Payroll
constants
Paid
absences
Public holidays
K = Calendar days
A = Workdays
S = Hours
n At the start of subschema XT00, function PARTT accesses data from the personal work schedule
(table PSP) to determine the partial period factors for the payroll period. If required, substitutions
can also be taken into account.
n The total working time for the partial periods is calculated by applying the relevant partial period of
the valid work schedule to the other partial periods of the payroll period.
n You maintain constants ADIVP and KDIVP in accordance with the time unit of the payroll period
in the view Payroll Constants for Time Unit.
n Planned working time according to the employee's personal work schedule (PSP) for a specific
basic pay period. KSOLL: Planned work measured in calendar days. ASOLL: Planned work
measured in workdays. SSOLL: Planned work measured in working hours.
n Unpaid absences (for a specific basic pay period) possibly weighted. KAUxx: Unpaid absence
measured in calendar days. AAUxx: Unpaid absence measured in workdays. SAUxx: Unpaid
absence measured in working hours. Either xx = nn stands for the unpaid absence counting class, or
xx = ** stands for the sum of all unpaid absences (for all counting classes).
n Total working time for the payroll period in accordance with the employee's work schedule for a
specific basic pay period. KDIVI: Total working time measured in calendar days. ADIVI: Total
working time measured in workdays. SDIVI: Total working time measured in working hours.
© SAP AG
HR400
9-8
Displaying Partial Period Parameters (2)
Total working
time projected
for the period
T
No From To KSoll ASoll
SSoll
01
02
39.40 31.00
82.60 31.00
G
15.00 11.00
16.00 11.00
31.00 22.00 122.00
KDiv I ADiv I SDiv I
31.00
01
02
G
SDivP
80.70
161.40
30.00
30.00
22.00
22.00
78.24
156.48
22.00
122.00
30.00
22.00
156.48
KAX** AAX**
SAX**
0.00
2.00
0.00
1.00
0.00
8.00
4.00
1.00
4.00
1.00
32.00
8.00
1.00
0.00
1.00
0.00
8.00
0.00
2.00
1.00
8.00
5.00
5.00
40.00
1.00
1.00
8.00
Unpaid
absences
T = Partial period
G = Whole period
 SAP AG 1999
KDivP ADivP
22.00
22.00
No From To KAU** AAU** SAU** KAP** AAP** SAP**
T
Payroll
constants
Paid
absences
Public holidays
K = Calendar days
A = Workdays
S = Working hours
n In this example, the employee is a part-time worker in the first half of the payroll period with an
employment percentage of 50%.
n In the second half of the payroll period, the employee is a full-time worker with a 100%
employment percentage.
n The total working time SDIVI of both partial periods is calculated by applying the respective
partial period of the valid work schedule to the rest of the payroll period.
n GSSOLL contains the employee's planned hours from the first to the last day of the payroll period,
and equals GSDIVI in this example. If, for example, the employee joins the company on the fifth
day of the payroll period, GSSOLL will contain a smaller value than GSDIVI because the planned
hours are only counted from the day the employee joins the company.
© SAP AG
HR400
9-9
Factoring: Reduction in Pay
l In the Caliber ‘A’ Bicycle Company,
an employee leaves the company two days
before the end of the payroll period.

SAP AG 1999
© SAP AG
HR400
9-10
Formula for the Deduction Method
Factor
=
1
Absence
---------------------------------------General period working time
General period working time - absence
------------------------------------------------------General period working time
=
Problem:
-
Many absences during monthly payroll
Long month
-0.097
167.7 - 184
--------------167.7
Claims on employee
167.7 - 144
--------------167.7
Pay despite absence for whole period
Short month
0.14
 SAP AG 1999
n The deduction method multiplies the employee's hourly/daily rate by the number of unpaid times,
and deducts the result from the employee's pay. The number of working hours specified per period
is used as the divisor.
n If payroll is run for monthly periods, the general divisor determines that each calculation unit (hour
or day) has the same value irrespective of whether the period is a long or short month.
n The deduction method is not suitable to use in the following situations:
n In the long months, such as July, a large number of absences could result in negative remuneration,
that is, money would be claimed from the employee.
n If payroll is run for the employee on a monthly basis (monthly or half-monthly) and the employee
has many unpaid absences. In short months, such as February, the employee could be absent for the
entire month and still receive remuneration.
n If partial remuneration must be calculated for exact periods. The employee would receive an
amount that is different from the amount of remuneration effected for the period, because the
number of hours or days does not correspond to the average.
© SAP AG
HR400
9-11
Formula for the Payment Method
Factor
=
1
* (Planned working time - Absence)
------------------------------------------------------------General period working time
=
Planned working time - Absence
---------------------------------------------General period working time
Problem:
Few absences during monthly payroll
Long month
-1.049
184 - 8
---------167.7
Pay too high despite absence
160 - 8
---------167.7
Large reduction for few absences
Short month
0.906
 SAP AG 1999
n In the payment method, the employee is remunerated for the period actually worked or for paid
absences. The hourly or daily rate for the payroll period is calculated based on the amount of
remuneration agreed and multiplied by the number of hours or days to be paid. The number of
working hours specified per period is used as the divisor.
n If payroll is run for monthly periods, the general divisor determines that each calculation unit (hour
or day) has the same value irrespective of whether the period is a short or long month.
n It is not suitable to use the payment method in the following situations:
n In long months , such as July, few absences could result in a factor that is greater than one; that is,
the employee would be paid too much.
n In short months, such as February, the employee could work almost the entire period and still earn
considerably less.
n If partial periods are calculated for exact periods, the employee would receive an amount that is
different from the amount of remuneration effected for the period, because the number of hours or
days does not correspond to the average.
n In practice, a hybrid of both the payment and deduction methods is often used: The deduction
method is used for up to 10 absence days, and the payment method for more than 10 absence days.
However, this procedure also causes problems, because changing from the deduction to the
payment method gives rise to great differences in the valuation of remuneration. This can lead to
unwanted situations.
© SAP AG
HR400
9-12
Formula for the PWS Method
Factor
=
1
* (PWS planned working time - Absence)
--------------------------------------------------------------------Period working time according to PWS
=
PWS planned working time - Absence
-----------------------------------------------------Period working time according to PWS
Problem:
Reduction factors of varying size
Long month
0.957
184 - 8
---------184
Short month
0.950
The hourly rate is lower in long
months than in short months
160 - 8
---------160
 SAP AG 1999
n In the PWS method, the individual, actual planned working time according to the employee's
personal work schedule (PWS) is used as the divisor.
n The PWS method is particularly suitable for reductions if planned working time is specified exactly
and all deviations from planned working time are entered in the system.
n Deviations that frequently occur from planned working time are the result of changes to the
following infotypes:
•
Absences (2001)
•
Substitutions (2003)
•
Planned Working Time (0007)
n The PWS method is also suitable for calculating partial payments for exact periods.
© SAP AG
HR400
9-13
Secondary Wage Types for Period Factors
Table IT
NUM
Function
GEN/8
RTE
3
3
.
.
.
3
/801 01
/802 01
100,000
100,000
/816 01
100,000
3
3
.
.
.
3
/801 02
/802 02
100,000
100,000
/816 02
100,000
AMT
 SAP AG 1999
n Function GEN/8 generates secondary wage types /801 to /816. Factoring values are assigned to
these secondary wage types during calculation.
n By accessing GEN/8, the system determines the following:
•
Secondary wage types /801 to /8nn are generated and written to the input table (IT) for each
WPBP split period.
•
The factor is set at 1 in each secondary wage type /8nn generated and then multiplied by the
constant GENAU 100,000.00 to increase the accuracy of the calculations. The result is written
to the Rate (RTE) field.
n In the standard system, 16 secondary wage types are generated for the partial period factors. You
can use 9 of these secondary wage types for your own partial period factors. Secondary wage types
/810 to /816 have a meaning within the system.
© SAP AG
HR400
9-14
Personnel Calculation Rules for Factoring
XPPF
XPP0 + XPP1
XPPF
Determine partial period factors
yes
EXIT
Inactive work relationship the entire period?
no
XPP0
-
Unpaid absence?
Change in basic pay?
Employee joined in payroll period?
Employee left in payroll period?
no
XPP1
Calculate partial period factors
 SAP AG 1999
n Personnel calculation rule XPPF is accessed in subschema XAL0 according to wage types /801 to
/816 to calculate partial period factors.
n Depending on the check results from operation PPPAR, personnel calculation rule XPPF accesses
personnel calculation rules XPP0 and XPP1 for wage types /801 and /802.
n Personnel calculation rule XPPF calculates the following factors for Cost Accounting:
•
/810
Difference between the working time for the current period and the average working
time
•
/814
Share of paid public holidays on which there is no work
•
/815
Share of work on public holidays and paid absences
•
/816
Share of unpaid absences
© SAP AG
HR400
9-15
Determining Partial Period Factor /801
Determine partial period factors
XPP1
E
*
E
/801
Partial period factor in wage type /801
RTE=TSSOLL
Planned work in hours
RTE-TSAU**
Minus unpaid absences
RTE*KGENAU
Multiplied by factor
RTE/TSDIVI
Divided by total working time
ADDWT *
PWS method:
PWS planned working time - Unpaid absences
Monthly working time according to PWS
 SAP AG 1999
n Wage type /801 contains a partial period factor that is determined using the PWS method.
n Personnel calculation rule XPP1 is accessed in subschema XAL9 from personnel calculation rule
XPPF for each wage type.
© SAP AG
HR400
9-16
Determining Partial Period Factor /802
Determine partial period factors
XPP0
E
*
E
/802
E
Partial period factor in wage type /802
RTE=GASOLL
Planned workdays
RTE-GAAU**
Minus unpaid absences
RTE-GAAP**
Minus paid absences
RTE?0
RTE = 0?
E
E
*
RTE=0
Set RTE = 0
ADDWT *
Put wage type in OT
>
RTE*KGENAU Multiplied by 100,000
RTE/TADIVI
 SAP AG 1999
Division
ADDWT *
n The partial period factor in wage type /802 is calculated using the following formula:
n Planned working time - Unpaid absences - Paid absences
Planned working time
n You can use partial period factor /802 to only remunerate the constituent parts of an employee's pay
(for example, transportation allowance) on the days in the payroll period the employee actually
worked.
© SAP AG
HR400
9-17
Assigning Partial Period Factors
WType
M020
Monthly salary
Processing class
10
Identify wage type for factoring
Specification
1
Reduction with factor /801
 SAP AG 1999
n The reduction factor for primary wage types is assigned to processing class 10.
© SAP AG
HR400
9-18
Valuating Payroll Elements
Valuate payroll elements using partial period factors
XVAL
E
3
Using ES grouping 3 wage/time
wage/time type
type ****
**** as
as an example
E
****
E
VWTCL 10
E
Processing class 10
*
ERROR
E
Cancel processing
0
ADDWT *
E
 SAP AG 1999
Put wage type in OT
1
ELIMI *
RESET RA
RTE= /801
Eliminate time period indicator
Set time period indicator
Transfer partial period factor
RESET *
MULTI RAA
Set time period indicator
Multiply R*A=A
AMT/KGENAU
ZERO= R
Divide by 100,000
Set RTE to zero
ADDWT *
Put wage type in OT
n Personnel calc ulation rule XVAL multiplies the amount of the wage type to be factored by the
partial period factor. If the wage type to be factored has specification 1 in processing class 10, for
example, the system uses the factor in the RTE field of wage type /801 for the multiplication. The
result of the multiplication is stored in the AMT field of the factored wage type.
n ELIMI
The entries in the work tables (IT, OT, RT,…) are assigned to various validity periods in basic data
(such as work center, taxation, cost distribution) by means of split indicators. This allows the
system to create exact time references for wages/salary earned and to calculate and distribute costs.
If it is no longer necessary to distinguish between partial periods for one of the feature classes in the
wage type currently being processed, you can remove the corresponding split indicator using the
operation ELIMI. You can specify up to 3 split indicators as parameters, or enter * for all of them.
n RESET
This operation resets the time period indicators (split indicators).
n Examples:
*
All indicators
R Employee subgroup grouping for personnel calculation rule
A Work center indicator (WPBP)
© SAP AG
HR400
9-19
Creating Wage Types for Cost Accounting
WType
M020
Monthly salary
Processing class
31
Allocate monthly lump sums to CO
Specification
1
Calculate paid public holidays
 SAP AG 1999
n To create the amount paid as continued pay for paid absences (leave, sickness, public holidays), all
of the basic pay wage types must have a specification in processing class 31.
n Processing class 31 can have the following specifications:
0
Wage type does not lead to cost center debits/credits
1
Calculate paid public holidays
2
Calculate total paid non-work
3
Calculate paid non-work and unpaid absence time
n Personnel calculation rule XCM0 is accessed by subschema XAL9 to distribute remuneration
elements to secondary wage types for Cost Accounting. The payments made to an employee are
divided into productive and unproductive parts for exact periods. Depending on the specification,
the amount field (AMT) is filled with the following wage types:
n /840
/844
/845
/846
© SAP AG
Difference between working hours in current month and average value
Paid public holidays
Total paid non-work
Total unpaid absences.
HR400
9-20
Creating Hourly Rates for Cost Accounting
Supply Cost Accounting (CO) with number of hours
XCH0
E
*
E
****
NUM=TSDIVI
Total working time in partial period
NUM-TSDIVP
General working time in partial period
ADDWTI/840
Put wage type in IT
NUM=TSAX**
Paid public holidays in partial period
ADDWTI/844
Put wage type in IT
NUM=TSAX**
Paid public holidays in partial period
NUM+TSAP**
Paid absences in partial period
ADDWTI/845
Put wage type in IT
NUM=TSAU**
Unpaid absences in partial period
ADDWTI/846
Put wage type in IT
 SAP AG 1999
n In personnel calculation rule XCH0, the number (NUM) field of the wage types /840, /844, /845
and /846 is filled with hours. The amount (AMT) fields in personnel calculation rule XCM0 already
contain values.
n Subschema XAL0 accesses personnel calculation rule XCH0 a single time using function ACTIO.
Operation ADDWTInnnn inserts wage types with the designation nnnn into the input table. As the
wage types specified in the personnel calculation rule already exist in table IT, only the NUM field
changes for the existing wage types.
© SAP AG
HR400
9-21
Factoring in Schemas
XT00
.
GENPS
GENPS
.
PARTT
.
P2003
.
PAB
XAL9
GEN/8
PIT
PIT
PIT
ACTIO
.
General processing of time data INTERN.
**
*
Generate personal work schedule PWS
Generate PWS with shift substitutions
Partial period parameter
S**
Import shift substitutions into PWS
Edit absence data
16
XPPF
XCM0
XVAL
XCH0
NOAB
P31
P10
A
Factoring and storage INTERN.
Create wage types /801 - /816 in IT
Determine partial period factors
Monthly lump sums for Cost Accounting
Valuate remuneration elements
Hourly rates for Cost Accounting
 SAP AG 1999
n At the start of subschema XT00, function GENPS generates the personal work schedule for the
personnel number for which payroll is being run. Substitutions (infotype 2003) that are relevant for
the work schedule may either be taken into account when setting up table PWS or added at a later
time.
n In the procedure shown, shift substitutions are not taken into account when setting up partial period
parameters and factors as function P2003 imports them into table PWS at a later time.
n Table PARTT is complete once the absence data (PAB) has been edited
n In personnel calculation rule XVAL, the amount specified for the wage type to be factored is
multiplied by the partial period factor (wage type /8nn).
© SAP AG
HR400
9-22
Factoring: Summary (1)
l Factoring is used to calculate remuneration
for exact periods. For example, it is required
to reduce remuneration for unpaid absences,
to account for changes in organizational
assignment, and in Cost Accounting. In
Payroll, partial period parameters
are created based on the employee’s work
schedule, absences and public holidays. These
parameters are used in personnel calculation
rules to calculate partial period factors.
 SAP AG 1999
© SAP AG
HR400
9-23
Factoring: Summary (2)
l The partial period factors are stored in
wage types /8nn during the payroll run.
In processing class 10, the wage types
to be factored are assigned a specification
determining which factor (/8nn) they are
to be multiplied by.
l Cost Accounting receives data on the
productive and unproductive elements
of an employee’s remuneration.
 SAP AG 1999
© SAP AG
HR400
9-24
Exercises
Unit: Factoring
Topic: Determining and Assigning Reduction Factors
•
Determining partial period factors according to the all-or-nothing
method
•
Assigning partial period factors to a wage type that is to be reduced
If the employee works on at least half the planned working days in the
payroll period, your company will pay the full instructor's bonus. If the
employee worked on less than half the planned working days, no
instructor's bonus will be paid.
You will require a partial period factor that is determined in the time unit
‘workday’ using the formula planned working time - unpaid absences
- paid absences. The reduction factor must be stored in wage type /803.
1.
Using the IMG, make a copy of personnel calculation rule XPPF, and rename it ZPnn
(nn = group number). In rule ZPnn, create a processing link to wage type /803.
2.
Make a copy of subschema XAL9, rename it ZAnn, and adjust subschema ZAnn and
your payroll schema Z0nn accordingly.
3.
Assign a reduction factor to the wage type Instructor's bonus 60nn.
4.
Assign an instructor's bonus of 100.00 to your employee's basic pay starting in payroll
period 07. Finally, enter a period of leave in period 07.
5.
Simulate the payroll run for period 07, and check that the personnel calculation rule
ZPnn is correct.
© SAP AG
HR400
9-25
Solutions
Unit: Factoring
Topic: Determining and Assigning Reduction Factors
1.
Copy personnel calculation rule XPPF to ZPnn and create a processing link for wage type
/803:
IMG à Payroll: International à Partial Period Calculation à Create Reduction
Factors à Determine Partial Period Factors -Rule XPPF
Make a copy of rule XPPF, and rename it ZPnn. In the Wage type field, enter /803 and
choose Change. Change rule ZPnn.
/803
Partial period factor 3
RTE=GASOLL
Set
RTE-GAAU**
Subtraction
RTE-GAAP**
Subtraction
RTE?
*
© SAP AG
Value
Compare
RTE=0
Set
ADDWT *
Outputtabelle
HR400
9-26
>
2.
RTE=1
Set
RTE*KGENAU
Multiplication
ADDWT *
Outputtabelle
Make a copy of subschema XAL9, change access to personnel calculation rule XPPF,
and include your copy of the subschema in payroll schema Z0nn:
Human resources à Payroll à International à Tools à Maintenance tools à
Schema à Copy
from schema XAL9
to schema
ZAnn
Change schema Zann
from PIT XPPF
___
to
PIT ZPnn
___
NOAB
NOAB.
Human resources à Payroll à International à Tools à Maintenance tools à
Schema à Change
Change schema Z0nn
from COPY XAL9
to
COPY ZAnn.
3.
Assign a reduction factor to wage type 60nn:
IMG à Payroll: International à Partial Period Calculation à Assign Reduction
Factors
Set processing class 10 to specification 3.
4.
Assign wage type 60nn to the employee's basic pay, and maintain paid and/or unpaid
absences:
Human Resources à Personnel Management à Administration à Maintain
Master Data
Choose the Basic Pay infotype, and create a record specifying wage type 60nn. Then
choose the Absences infotype , and maintain a paid and/or an unpaid absence.
5.
Simulate the payroll run for the period, and check personnel calculation rule ZPnn:
Human resources à Payroll à International à Payroll à Simulation
© SAP AG
HR400
9-27
Cumulation Wage Types
Contents:
l
l
l
l
l
Cumulating and Storing Time Wage Types
Cumulating and Storing Basic Pay Wage Types
Cumulation Wage Types from External Transfers
Updating Cumulation Wage Types
Creating Cumulation WTs in Schemas
 SAP AG 1999
© SAP AG
HR400
10-1
Cumulation Wage Types: Unit Objectives
At the conclusion of this unit, you will be able to:
l Code time and basic pay wage types for
cumulation and storage in the
results table.
l Code the cumulation and storage of wage
types from external transfers.
l Determine which wage types are cumulated
in the annual results table.
 SAP AG 1999
© SAP AG
HR400
10-2
Course Overview Diagram
Payroll Basics
Time Wage Type Selection
Personnel Calculation Rules
Averages
Starting Payroll
Factoring
Wage Type Valuation
Cumulation Wage Types
Absence Valuation
Retroactive Accounting
 SAP AG 1999
© SAP AG
HR400
10-3
Cumulating and Storing Time Wage Types
Table OT
Table IT
/001
M020
M110
M111
.
/001
/101
/201
M020
.
17.05
17.05
4.26
10
10
3,000
170.50
42.60
17.05
213.10
213.10
3,000
Cumulation of amounts into
cumulation wage types /1nn
and average bases /2nn
Table RT
Storage of time wage types
in the results table and
accumulation of overtime
into wage type /852
.
/852
.
M110
M111
.
10
17.05
4.26
10
10
170.50
42.60
 SAP AG 1999
n At the end of subschema XT00, the wage types in the IT are processed in personnel calculation rule
X020. The time wage types that no longer need to be processed, as they were already valuated
using a valuation basis or using an average value, are now stored in the RT results tables and the
amounts are added to the gross cumulation wage types /1nn and average bases /2nn. The overtime
hours can be cumulated in wage type /852 .
n At this point in time, the basic pay wage types have not been through factoring in the payroll
schema. For this reason, they cannot yet be stored in the results table.
© SAP AG
HR400
10-4
Cumulation WTs from Time-Based Payments
WT
M110
Overtime hours
Processing class
3
Cumulation and storage of time wage types
Specification
5
RT storage, cumulation, accumulation of OT
Cumulation
1
Total gross amount
10
Net payments/deduct.
X
 SAP AG 1999
n In processing class 3, you specify how each time wage type should be stored in the results table.
You have the following options:
•
The wage type is not stored in the results table but is transferred
•
The wage type is stored in the results table without being cumulated
•
The wage type is cumulated and stored in the results table
•
The wage type is cumulated and stored in the results table, the hours for this wage type are also
cumulated as overtime hours.
n At this point, wage types from the Basic Pay infotype (0008) must also be identified. They should
not be transferred at this point, as the system needs them at a later stage in the payroll run.
© SAP AG
HR400
10-5
Cumulating and Storing Basic Pay Wage Types
Table OT
Table IT
/001
/101
/201
M020
.
/101
17.05
213.10
213.10
3,000
3,213.10
.
.
Cumulation of amounts in
cumulation wage types /1nn
Table RT
Storage of wage types
from the infotypes 0008,
0014 and 0015 in the
results table
/001
.
/852
.
M020
M110
M111
.
17.05
10
17.05
4.26
10
10
3,000
170.50
42.60
 SAP AG 1999
n At the end of subschema XAL9, the wage types in the IT are processed in personnel calculation
rule X023. The wage types that no longer require processing are now stored in the RT results table,
the amount fields are added to the gross cumulation wage types /1nn.
© SAP AG
HR400
10-6
Cumulation Wage Types Based on Master Data
WT
M020
Monthly salary
Processing class
20
Storage and cumulation
Specification
3
RT storage, cumulation
Cumulation
1
Total gross amount
10
Net payments/deduct.
X
 SAP AG 1999
n In processing class 20, you specify how each master data wage type should be stored in the results
table. You have the following options:
•
The wage type is not stored in the results table but is transferred unchanged
•
The wage type is excluded
•
The wage type is stored in the results table and is included in the cumulation wage types
•
The wage type is stored in the results table without being cumulated
© SAP AG
HR400
10-7
Cumulation Wage Types from External Transfers
WT
M500
Union contributions
Processing class
25
Processing after end of payments/deductions
Specification
1
Summarized RT storage
Cumulation
10
Net payments/deduct.
X
 SAP AG 1999
n In processing class 25, you specify how every wage type entered via the External Bank Transfers
infotype (0011) should be processed in the personnel calculation rule X045. These wage types
cannot be cumulated in gross cumulation wage types, as they are processed in the net part of the
payroll run. You have the following options:
•
Transfer unchanged
•
Summarized RT storage with transfer ID.
n It is not possible to cumulate in wage type /110.
© SAP AG
HR400
10-8
Updating Cumulation Wage Types
Table RT
/001
/101
/852
.
M020
M110
M111
.
17.05
3,213.10
10
17.05
4.26
10
10
3,000
170.50
42.60
Cumulation of selected
wage types from the results
table in the cumulation
results table
Table CRT
/101
/852
.
M020
M110
M111
.
6,213.10
10
10
10
6,000
170.50
42.60
 SAP AG 1999
n For many wage types, you may want an overview of the annual values already cumulated (for
example, for printing annual values from certain wage types on the payroll form). For this purpose,
these wage types are transferred to the annual results table CRT.
n This takes place at the end of the payroll run with the help of the ADDCU function and processing
class 30.
© SAP AG
HR400
10-9
Creating Annual Values
WT
M020
Monthly salary
Processing class
30
Update of cumulation wage types
Specification
3
Cumulate number in current year
 SAP AG 1999
n In processing class 30, you specify which wage types are cumulated in the annual results table CRT
using the ADDCU function.
© SAP AG
HR400
10-10
Creating Cumulation WTs in Schemas
XT00
.
PIT
.
PIT
General processing of time data INTERN.
X015
GEN
Valuation of time wage types
X020
P03
Cumulation and RT storage
XAL9
.
ACTIO XCH0
.
PIT
X023
XNN0
.
P0011 X055
PIT
X045
.
XEND
.
ADDCU
.
Factoring and storage INTERN.
A
P20
Hourly rates for Cost Accounting
NOAB
Gross input and storage
Net payments/deducts.and transfers INTERN.
GEN
P25
NOAB
Read external transfers infotype 0011
Import payments/deductions to RT
Final processing INTERN.
P30
Update cumulation wage types CRT
 SAP AG 1999
© SAP AG
HR400
10-11
Cumulation Wage Types: Summary (1)
l In processing class 3, you use coding to define in
which cumulation wage types each time wage
type is included and how it is stored in the results table.
l In processing class 20, you use coding to determine in
which cumulation wage types each basic
pay wage type is included and how it is
stored in the results table.
 SAP AG 1999
© SAP AG
HR400
10-12
Cumulation Wage Types: Summary (2)
l In processing class 25, you use coding to determine
how each wage type from external transfers is
stored in the results table.
l In processing class 30, you determine how each wage
type in the results table is cumulated in the annual
results table.
 SAP AG 1999
© SAP AG
HR400
10-13
Retroactive Accounting
Contents:
l Calculating Retroactive Accounting Differences
l Simple Retroactive Accounting
l Multiple Retroactive Accounting
 SAP AG 1999
© SAP AG
HR400
11-1
Retroactive Accounting: Unit Objectives
At the conclusion of this unit, you will be able to:
l Identify the wage types with difference
amounts in retroactive accounting.
l Describe the processing steps in the
schema for retroactive accounting.
 SAP AG 1999
© SAP AG
HR400
11-2
Course Overview Diagram
Payroll Basics
Time Wage Type Selection
Personnel Calculation Rules
Averages
Starting Payroll
Factoring
Wage Type Valuation
Cumulation Wage Types
Absence Valuation
Retroactive Accounting
 SAP AG 1999
© SAP AG
HR400
11-3
Calculating Retroactive Accounting Differences
1) Cumulation of net amount:
/550
3,000
Statutory net pay
2) Payment amount before transfer:
/560
3,000
Payment amount (new)
3) Creation of differences:
/560
/560
/551
/553
3,750
3,000
750
750
Payment amount (new)
Payment amount (from ORT)
Total net retro. acc. difference
Retro. acc. difference to last payr.
4) Wage types in the results table:
/559
/560
/551
/553
3,750
3,000
750
750
Bank transfer
Payment amount (old)
Total net retro. acc. difference
Retro. acc. difference to last payr.
 SAP AG 1999
n Wage type /550 is created in the net cumulation part of the payroll schema. The amount for wage
type /550 is then added to wage type /560.
n Wage types /551 and /553 are created in the case of retroactive accounting. The difference between
wage type /560 from the old payroll result (table ORT) and the newly calculated payment amount is
stored in wage type /551 for the payroll period calculated retroactively.
n Wage type /553 is created as the difference between the payment amount for the period currently
being accounted and the previous result for the same period. Where multiple retroactive accounting
takes place for a period, the wage type contains the difference between the amounts paid for
previous and current retroactive accounting. Wage types /551 and /553 are both stored with a
reversed sign +/-.
n Note that wage type /560 in the results table for the retroactive accounting run contains the amount
specified in the original payroll result.
© SAP AG
HR400
11-4
Simple Retroactive Accounting
l In payroll period 02, an employee at the
Caliber 'A' Bicycle Company receives
additional remuneration for payroll period 01
retroactively.
 SAP AG 1999
© SAP AG
HR400
11-5
Example: First Retroactive Accounting Run
Period 01 in period 01
/550
/559
/560
3,000
3,000
3,000
Statutory net amount
Bank transfer
Payment amount
Period 01 in period 02
Period 02 in period 02
/550
/551
3,750
750 -
/550
4,500
/552
750
/553
/559
/560
750 3,000
3,000
/559
/560
5,250
5,250
Statutory net amount
Total net retro. acc. difference
Total net subseq. clearance
Retro. acc. difference to last payr.
Bank transfer
Payment amount
 SAP AG 1999
n In this example, the employee's basic pay is increased from 3,000 to 4,500 in the middle of payroll
periode 01. The statutory net amount for the period calculated retroactively is the total of the
statutory net amount for both partial periods of this payroll period.
n Due to subsequent clearing, the statutory net amount of period 01 in period 02 as well as the
amount paid are higher than specified in the original payroll run. Wage type /551 contains the
difference between the old and the newly calculated payment amount with reversed +/- sign.
n In the current period, the amount in wage type /551 is then transferred to wage type /552.
© SAP AG
HR400
11-6
Multiple Retroactive Accounting
l In the Caliber 'A' Bicycle Company, an employee receives
another basic pay raise in payroll period 03 that is
backdated to payroll period 01.
l This increase in basic pay comes into force in the first
payroll period as well as at a later date in the payroll
period.
 SAP AG 1999
© SAP AG
HR400
11-7
Example: Second Retroactive Accounting Run
Period 01 in period 01
/550 3,000
/559 3,000
/560 3,000
Period 01 in period 02
/550 3,750
/551 750 /553
/559
/560
750 3,000
3,000
Period 01 in period 03
/550 4,075
/551 1,075 /553
/559
/560
325 3,000
3,000
Statutory net amount
Bank transfer
Payment amount
Period 02 in period 02
/550 4,500
Statutory net amount
Total net retro. acc. difference
/552
750
Total net subseq. clearance
Retro. acc. difference to last payr.
/559 5,250
Bank transfer
/560 5,250
Payment amount
Period 02 in period 03
/550 5,800
/551 1,300 /552
750
/553 1,300 /559 5,250
/560 5,250
Period 03 in period 03
/550 5,800
/552
1,625
/559
/560
7,425
7,425
 SAP AG 1999
n In this example, the employee's basic pay is increased from 4,500 to 5,800 in period 03 at the start
of the last third of payroll period 01.
n Due to subsequent clearing, the statutory net amount for period 01 in period 03 and the amount paid
are again higher than in the original payroll run. Wage type /551 contains the difference between
the original and the newly calculated amount. Wage type /553 contains the difference between the
newly calculated payment amount and that from the previous retroactive accounting run.
n The statutory net amount for period 02 in period 03 is higher than in the original payroll results.
Wage type /552 contains the subsequent clearing amount from the first retroactive accounting run
for period 01.
n The amount from for wage type /553 from both retroactively accounted periods is transferred to
wage type /552 in the current period.
© SAP AG
HR400
11-8
Retroactive Accounting in the Schema
XRR0
IF
PDT
ELSE
ACTIO
LPBEG
IMPRT
PORT
PIT
BTFIL
LPEND
IF
PIT
ELSE
PIT
PIT
ENDIF
ENDIF
X041
O
GEN
NOAB
RC
O
GEN
NOAB
X048
X042
X047
International retroactive accounting
Original payroll?
Provide differences received
Retroactive accounting
Reset BTEX
Loop over old results
Import last payroll run
Create differences and transfer
wage types that cannot be revised
Cumulate new payment amount
Transfer BT from last payroll results
LPCR
X043
X047
X043
End of loop
Did the program run through the loop?
New amount to data medium
No
Cumulation of new payment amount
Write new amount to data medium
Re: Did program run through loop?
End of retroactive accounting
 SAP AG 1999
n This subschema is used to calculate any differences that may have been created if payroll takes
place in a period for which retroactive accounting has been performed so that remuneration is no
longer consistent with the original payroll run. The differences calculated are then taken into
account in the same subschema in the original payroll run for the current period.
n The subschema primarily comprises the following steps:
•
Query whether original or retroactive run
•
Original payroll run: Provide differences received
•
Retroactive run: Read last payroll result (original payroll run or old retroactive accounting run)
•
Print the values read (internal table ORT)
•
Create differences and transfer non-revisable wage types
•
Derive new payment amount
•
Store new payment amount in difference table (internal table DT)
•
Transfer bank transfer(s) (from internal table BT) from last payroll result
© SAP AG
HR400
11-9
Retroactive Accounting: Summary
l In retroactive accounting, the last payroll
result is imported into the period for
which retroactive accounting takes place.
The system creates differences that are
stored in table DT and transfers the wage
types that no longer can be revised.
l The differences are read and processed
in the original payroll run.
 SAP AG 1999
© SAP AG
HR400
11-10
Appendix
l This section contains supplementary material
to be used for reference
l This material is not part of the standard course
l Therefore, the instructor might not cover this
during the course presentation
 SAP AG 1999
© SAP AG
HR400
12-1
Appendix
Contents:
l
l
l
l
l
l
l
l
l
l
l
l

Checklist of Payroll Prerequisites
The Payroll Control Record
The Employee's Payroll Status
The Payroll Log
Schema and Rule Editor
Utilities
Processing Classes
Old Averages
Calculating Overtime
Archiving
Off Cycle Payroll
Process Model
SAP AG 1999
© SAP AG
HR400
12-2
Checklist of Payroll Prerequisites
Master and
Time Data
Prerequisites
Activities
l Dialog and time wage types
l Copy model wage types in the wage
l Work schedules
l Infotypes 0000, 0001, 0007, 0008,
0009 and country dependent
infotypes (example: tax)
type catalog to customer wage types
in the customer name range
(numbers)
l Configure and generate work schedules
in Customizing
l Enter personal data in the system using
personnel actions
l Payroll processes further
Infotypes: 0014, 0015, 2001, 2010,
2003, 2005 . . .
Administration
Subs.
Activities
l Payroll areas and periods
l Configure and generate in Customizing
l Payroll control record
l Create in Customizing
l Bank details and details of house
l Mostly configured using FI
banks
l Mostly configured using FI, combine
l Cost centers
...
with organizational units
l Employee remuneration statements
...
l Standard form provided
...
 SAP AG 1999
n Before employee data can be entered and processed in the system, some necessary prerequisites
must be set up first. SAP provides numerous sample entries that you can modify to meet the
requirements of your enterprise.
n The above list gives an overview of the most important elements.
© SAP AG
HR400
12-3
Payroll Control Record (1)
International Payroll
Incorrect pers. nr.
Payroll areas
Tools
XX monthly
System
Help
...
Payroll calendar
Payroll status
Payroll
Payroll control
control record
record
Payroll results
Released for payroll
...
Released for correction
Exit payroll
Check payroll results
Coordination of the
various
phases in payroll
 SAP AG 1999
n You must create a control record in Customizing for each payroll area before it can be used.
n The personnel control record performs the following functions in payroll:
n Defines the payroll past for retroactive accounting recognition.
n Locks master data and time data so no changes can be made during the payroll process. The lock is
valid for the payroll past and the payroll present. Changes affecting future payroll runs are still
possible
n Defines the earliest possible retroactive accounting date for each payroll area
n The control record is maintained either in the Payroll menu under Tools -> Control Record, or in
the Payroll menu option, from which you may only choose the steps permitted at this point in the
payroll process.
n If you choose Change Control Record in the Tools menu, the 'Incorrect pers. nos.' pushbutton is
displayed. This displays a list of rejected personnel numbers. The list is displayed automatically if
you attempt to end a payroll run in which payroll is not complete for all personnel numbers.
© SAP AG
HR400
12-4
Payroll Control Record (2)
Payroll areas
Period of last
payroll run
XX monthly
Payroll status
Payroll period
01 1998
Run
01
Earliest retro acctg period
01. 01. 1998
-
01 1997
31. 01. 1998
01. 01. 1997
Current payroll
run saved
Retroactive accounting
for payroll is only
possible up to the start
date of this period.
Last change to control record
by Miller
Status
on February 01, 1998
at 01:01:30
Change information
Control record newly created
 SAP AG 1999
n You must pay particular attention when creating the payroll control record in your live system. The
payroll period used to create the payroll control records must be 1 period before the period in which
you want to go live.
n Example:
You want to use the SAP Payroll system to go live in period 05, 1998. You must enter period 4 as
the period in the payroll control record.
© SAP AG
HR400
12-5
Employee Payroll Status (Set by the System)
Up to which day payroll took
place for the employee
There is
only ever
one valid
record
Change Payroll Status (Infotype
Infotype 0003)
0003)
HR Master Data Edit
Goto
Utilities
System Help
Valid
Special run
Payroll / retroactive accounting
Accounted to
Earliest MD change
Retr.Act.Subs.Period
Payroll Correction
In case a personnel number
was rejected by payroll
or data was changed in
the correction phase
Date up to which
payroll recognizes
if and when a
payroll run
must be repeated
to take changes
in master data
into consideration
Start date
of retro. accounting
 SAP AG 1999
n Each employee has an individual payroll status. The necessary data is stored in the Payroll Status
infotype (0003). This infotype is created automatically as part of the Hiring action and each payroll
period is maintained automatically. You will rarely need to make changes to master data in this
infotype. Occasionally, however, you may need to enter employee-specific information relating to
Payroll or Time Management. It is therefore possible to change a few particular fields in the
Payroll Status infotype manually.
n The payroll driver enters the end date of the la st completed payroll period in the "Accounted to"
field.
n If master data is changed, the system enters the appropriate date in the "Earliest MD change" field.
This date is deleted after each completed payroll run.
n The payroll driver flags the "Payroll Correction" field if a personnel number has been rejected, or
you have entered data during the correction phase of the payroll run. The employee is entered in the
correction run with this indicator and if payroll is subsequently completed successfully, the
indicator is removed. If changes are made in Customizing, the "Payroll Correction" indicator is not
set.
© SAP AG
HR400
12-6
EE Payroll Status (Information Changed
Manually)
Defines the latest date when changes can be
made in the payroll past
Change Payroll Status (Infotype 0003)
HR Master Data
Edit
Goto
Utilities
System Help
Valid
Payroll / retroactive accounting
Earl.pers.RA date
Run payroll up to
Day until which
payroll can be
performed for an
EE even after
leaving
Do not account after
Pers. no. locked
Employee can be
locked
for payroll
Payroll is run for this
employee until this date
 SAP AG 1999
n Earliest personnel retroactive accounting date: This field is only used if you want to set a
retroactive accounting limit for an employee that is different from the date set in the payroll area.
n Do not account after: You can enter a date after which payroll will no longer be performed for an
employee. This date must not lie within an active period.
n Run payroll to: If an employee has left the company and continues to be paid after the leaving date,
this date is stored in this field. If you are dealing with payments in the payroll past, you do not have
to enter a date in this field. This is because such payments are triggered automatically during
retroactive accounting.
n Personnel number locked: If this field is flagged, an employee can be locked for payroll. This
personnel number will not be selected for payroll.
© SAP AG
HR400
12-7
The Payroll Log
Payroll Log
General data
data
Payroll period
Selection
Gen.data
Gen.data
(not
(not based
based on
on
payroll)
payroll)
Hierarchy levels
General program control
Logging
Process
Process course
course for
for
successful
successful
personnel
personnel numbers
numbers
Successful personnel numbers
00000006 Barbara Eden
00000007 James Bond
06/1998 (01.06.1998 - 30.06.1998)
Messages
Messages
Personnel numbers rejected
00000008 John Ross Ewing
Process
Process course
course for
for
rejected
rejected
personnel numbers
Messages
Statistics
Display statistical information
on
on the
the payroll run
 SAP AG 1999
n The report tree provides information on the payroll run (general data, messages and statistics) as
well as details on the processing steps for the personnel numbers selected.
n The log tree has five fixed hierarchy levels. Each fixed hierarchy level contains variable hierarchy
levels derived from the schema.
© SAP AG
HR400
12-8
Variable Hierarchy Levels
COM
BLOCK
ENAME
WPBP
GON
BLOCK
BLOCK
BLOCK
BEG
END
BEG
BEG
Log
Basic data INTERNATIONAL
Edit basic data
Determine name of EE
Read work center/basic pay data
Continue with complete data
Edit basic data
< Next block >
< Sub-block >
Schema
06/1998 (01.06.1998 - 30.06.1998)
Edit basic data
Determine name of EE
Read work center/basic pay data
Continue with complete data
< Next block >
< Sub-block >
 SAP AG 1999
n Variable hierarchy levels are used to structure data from the payroll run.
n Variable hierarchy levels are identified by the BLOCK function at the start (BEG) and end (END)
of the schema.
© SAP AG
HR400
12-9
Detail Display of a Function
WPBP: Import work center/basic pay
Input
P0000
P0001
P0007
P0008
Processing
Data retrieval
Indirect valuation
Output
WPBP
IT
 SAP AG 1999
n The detail display for a function enables you to view input data, processing steps, and output data in
the log.
© SAP AG
HR400
12-10
Navigating in the List
l "Expand" displays detailed
WPBP: Import work center/basic pay
information
Input
l "Compress" displays an
P0000
Type
Start
01.06.1998
overview
End
30.06.1998
Action
01
Reason
21
n Normal (important fields)
P0001
Infotype
Start
0001
01.06.1998
l Change table display
End
30.06.1998
n All (all fields)
P0007
P0008
Processing
Data retrieval
Indirect valuation
Output
WPBP
IT
 SAP AG 1999
n You can save your personal settings for the log tree and the list as a variant.
© SAP AG
HR400
12-11
Messages and Error Messages
……...
Personnel numbers rejected
000008
John Ross Ewing
06/1998 (01.06.1998-30.06.1998)
Gross part: Processing time data
GENPS
Processing
Period work schedule FLEX for 06 1998 not yet generated
 SAP AG 1999
n If an error occurs while a personnel number is being processed, the log automatically expands at the
relevant position, and displays an error message.
© SAP AG
HR400
12-12
Key to the Results Table
Employee subgroup grouping
WPBP Split indicators
Assign alternative payment
Assign cost accounting
A WT
3
3
3
3
AP C1 C2 C3 AB KoRe BT Aw vT vN
/001
/001
M020
M020
01
02
01
02
Assign transfer
Assign
absences
Country-specific split
 SAP AG 1999
n The country-specific splits indicate partial periods for social security and taxation purposes.
n The object ID for a variable assignment (vT) and its number (vN) can be set using operation
SETIN.
© SAP AG
HR400
12-13
The Schema Editor
1
Fct
Par1 Par2 Par3 Par4
D
1 Command line
Text
2 Line number
000010
000020
000030
000040
000050
3 Function
4 Parameters 1 - 4
5 Execute function
2
3
4
5
6
6 Text
 SAP AG 1999
n The editor command lines contain commands generally used within the R/3 System
•
A number
Attatch; position on specified line number
•
CHECK
Syntaxcheck
•
F schema
Fetch; that is, import a different schema such as F XT00
•
FIND string
Search for specified string
•
I
Insert; add a new page
•
Print
Print schema
•
R string1 string2
Replace; string 1 is replaced by string 2
•
U
Update; save schema
n F1 Help
You can display online documentation with immediate relevance to the part of the system in which
you are working, for example, by positioning the cursor on function names or the names of
personnel calculation rules, and pressing F1.
© SAP AG
HR400
12-14
Line Commands in the Schema Editor
R
R4
Repeat
Repeat line
Repeat line 4x
D
DD
Delete
Delete line
Delete block (Select first/last lines!)
C
CC
Copy
Copy line
Copy block (Select first/last lines!)
M
MM
Move
Move line
Move block (Select first/last lines!)
A
B
After
Before
Positioning for C/M line commands
 SAP AG 1999
n Further line commands:
•
RESET
Deletes the line command.
•
*
The line selected appears as the first line of the editor.
•
I
Inserts a blank line directly under the line selected.
•
In
Inserts the number of lines specified (n) directly under the line selected.
•
X
Copies data stored in X buffer under the line.
•
XX...XX
Marks the block of lines selected in the X buffer. Enter XX in the first and last
line of the block that you want to include in the buffer.
© SAP AG
HR400
12-15
The Rule Editor
Payroll rule xxxx ES grouping 1 W/TType ****
1
VarKey
NL
T
1 Command line
Operations
2 Line number
000010
000020
000030
000040
000050
3 Variable key
4 Next line
5 Rule type
2
3
4
5
6
6 Operations
 SAP AG 1999
n A personnel calculation rule can consist of several subareas, each of which is characterized by an
employee subgroup grouping for personnel calculation rules, a wage type, and a time type. An
index function provides an overview, and enables you to switch from one section to another as well
as delete individual subareas.
n The rule line contains 6 operations . The continuation indicator enables you to extend the
processing rule to several lines if required.
n The rule type determines the type of processing that is performed. D is used for decision
operations, P to call up subroutines, and Z to access a different personnel calculation rule.
n The variable key enables you to build up a decision tree, that can then be used to control wage
type processing from an organizational point of view, for example.
© SAP AG
HR400
12-16
Maintain Processing Classes and Specifications
Navigation
Processing Classes
---> Processing class specifications
1
3
Assignment to valuation bases
Cumulation and storage of time wage types
(X010)
Mark wage types for factoring
(XVAL)
Valuation according to principle of averages
(X016)
(X020)
.
10
.
15
.
 SAP AG 1999
n In the standard system, the processing classes are stored in the areas from 01 to 89. Processing
classes 90 to 99 are for customer-specific entries. You can create your own processing classes and
specifications, or create new specifications for existing processing classes.
n SAP recommends that you only create new processing classes in the aforementioned customer
areas, as entries that are maintained in the standard system could be overwritten when the release is
next updated.
© SAP AG
HR400
12-17
Maintain Processing Class Specifications
Navigation
Processing Classes
---> Processing class specifications
Processing class
15
Valuation according to principle of averages
1
Valuation of averages over 3 months
2
Valuation of averages over 6 months
A
Valuation of averages with frozen values over 3 months
 SAP AG 1999
n To create a new entry, you can either flag an existing entry, copy and rename that entry, or choose
"New entries".
© SAP AG
HR400
12-18
Using Wage Types in Payroll (1)
Program:
Output:
RPDLGA20
Tables
Tree structure
Continuous list
A
B
C
D
E
F
Areas belonging to modifier value xx
Meaning of processing classes and their values
Meaning of evaluation classes and their values
Meaning of cumulation wage types
Meaning of average bases
Use of valuation bases
B
01
01
01
01
01
Meaning of processing classes and their values
Assignment to valuation bases
1 Wage type is included in valuation basis /001 /001
2 Wage type is included in valuation basis /001 /002
3 Wage type is included in valuation basis /001 /001 and /002
9 Division of valuation bases /001 and /002
 SAP AG 1999
n This program enables you to obtain an overview of how all your primary and secondary wage types
are coded. This can be useful for comparing the coding of different wage types or for gaining an
overview of the status of your wage types in the system.
n To run the program, you must enter the country grouping and specify a validity period. By entering
certain wage types, you can limit the evaluation to the wage types that you require. The results can
be displayed in tables, in a tree structure, or in a continuous list.
n If you flag the optional field Display logical views , you can link from results that are displayed in
tables or in a tree structure to the logical views used to maintain processing classes, evaluation
classes and cumulation wage types. If a logical view is maintained in the Implementation Guide
(IMG), the program also enables you to access and execute the relevant IMG activity directly.
n To display the results in a table (see diagram above), you can navigate to the relevant table entry by
double-clicking the left-hand button of your mouse. To navigate in the tree structure, you can press
the left-hand mouse button once, or expand and collapse the relevant folder icon.
© SAP AG
HR400
12-19
Using Wage Types in Payroll (2)
B
01
01
01
01
01
Meaning of processing classes and their values
Assignment to valuation bases
---> X010
1 Wage type is included in valuation basis /001 /001
2 Wage type is included in valuation basis /001 /002
3 Wage type is included in valuation basis /001
9 Division of valuation bases /001 and /002
---> X013
B Meaning of processing classes and their values
01 1 Wage type is included in valuation basis /001 /001
01
01
01
01
01
01
1
1
1
1
1
1
M000 Hourly rate
M010 Monthly wage
M020 Monthly salary
M070 Pension payment
M200 Shift bonus
M220 Bonus by percentage
 SAP AG 1999
n Generating the tree structure and the continuous list can be time-consuming, as the system must
assign all the data to a particular branch before the tree can be displayed. It is faster to display your
results in tables as the system generates the relevant data sequentially as you branch to the next
level.
n To obtain a where-used list, you should display your results in a tree structure or a continuous list.
n If, for example, you simply want to know how individual processing classes are used in wage types,
you are recommended to display your results in a table.
© SAP AG
HR400
12-20
Displaying Schemas and Rules
Program:
RPDASC00
Schema:
Trigger PC rules:
ES grouping:
X000
X010
3
XT00 017 PIT X010 P01
Create valuation bases (Addition)
X0103****
DVWTCL 01
X0103*****
ERROR
X0103****0
ADDWT *
X0103****1
ADDWT * ELIMI Z ZERO= N
X0103****2
ADDWT * ELIMI Z ZERO= N
X0103****3
ADDWT * ELIMI Z ZERO= N
XT00 018 PIT X013 P01
Create valuation bases (Addition)
XT00 019 MOD XMOD GEN
Specify payroll modifiers
......
ADDWT /001
ADDWT /002
ADDWT /001ADDWT /002
 SAP AG 1999
n Report RPDASC00 enables you to create lists of schemas and subschemas. You can also explode
personnel calculation rules (according to the employee subgroup grouping for personnel calculation
rules) in the list. This is particularly useful for documenting and gaining an overview of personnel
calculation rules you have changed.
© SAP AG
HR400
12-21
Using HR Documentation Maintenance
HR Documentation Maintenance
Documentation class
Operation (Payroll)
Documentation object
Country
Object name
HR Documentation Object Name
HR Documentation class
OPEX
Country grouping
Also available as
amodal window
Object name
Description of logical information object
ADDNA *
Collect number and amount in
...
ADDWT
Add wage type to subsequent wage type
...
 SAP AG 1999
n The transaction PDSY (HR documentation maintenance) gives you access to the documentation on
all schemas, functions, personnel calculations and operations. If necessary, you can also create
client-specific documentation.
n You can get a list of these objects by specifying the documentation class you require and by using
the Possible Entries key for the field Object Name. You can also display this list as an amodal
window, for example, to have a list of all operations available when creating personnel calculation
rules.
n Relevant documentation classes for Time Management:
SCHE
- Personnel calculation schemas
CYCL
- Personnel calculation rules
FUNC
- Functions in payroll
OPEC
- Operations in payroll
549X
- Features
PRCL
- Processing class
PROMO
- Process model
n In schema and personnel calculation rule maintenance, HR documentation maintenance is called for
a specific context using F1 Help.
© SAP AG
HR400
12-22
Payroll and Processing Classes
M020 Monthly salary
Processing classes and specifications
1.
1.
Read basic data
2.
2.
Read payroll accounts for the last
period for which payroll was run
3.
3.
01 1
Assignment to valuation bases
02
03 0
Cumulation and storage of time wage types
04
Time data processing
- Determine valuation bases
- Read time data
- Generate time wage types
- Valuate time wage types
- Store time wage types in RT
05
06 0
Import from old payroll account
07
08
4.
4.
Import further payments and deductions
5.
5.
Factoring
- Reduce basic pay
- Determine wage types for FI/CO
09
10 1
Identify wage type for factoring
.
.
...
...
 SAP AG 1999
n Processing classes control the processing of wage types at various stages of payroll. The personnel
calculation rule called in the schema checks the value (specification) set in Customizin g, and
performs the processing required for the relevant value.
n For example, processing class 06 transfers wage types from the results in the imported previous
period to the current payroll period. The specification 0 in this class denotes that the wage type is
not transferred to the current payroll period.
n In total, there are 99 processing classes. The classes 90-99 can be used for customer-specific
processing. The processing classes 01-89 belong to SAP, although they are not all used.
n A wage type must have a specification in a processing class if the wage type goes through the
payroll processing step in which the relevant processing class is queried.
© SAP AG
HR400
12-23
Overview of Schemas and Processing Classes
Subschema
XIN0
XBD0
XLR0
XT00
Initialization of payroll
Edit basic data
Import last payr.result
Gross remuneration
XAP9 Import further
payments/deductions
XAL9 Factoring and PIT
Storage
XNA9 Net cumulation
XRR0 Retroactive accounting
XNN0 Net payments/deductions
and bank transfer
XEND Final processing
Function Rule
WPBP
PORT
PIT
PIT
P2010
PIT
PIT
P0014
P0015
XPPF
PIT
PIT
ACTIO
PIT
X006
X010
X013
X930
X015
X016
X020
X011
X011
06
01
01
X030
P0011
X055
X045
Notes
Basic pay
Infotype 0008
/001 - /0nn
/001 - /0nn
Valuation bases
05
EE remun.info (IT 2010)
Time WT valuation
Average valuation
Gross import and RT storage
Recurring payments/
Add.Payments (IT 15)
Partial period factors
Monthly lump sums for CO
Valuation of remun.elements
Hourly rates for CO
Gross import and
RT storage
Net cumulation
25
30
Ext.bank transfers (IT 11)
Import pymnts/deds to RT
Update cumulation in CRT
15
03
47
47
XCM0 31
XVAL 10
XCH0
X023 20
PIT
ADDCU
PRCL Wage types
/801 - /816
/840
/840
 SAP AG 1999
© SAP AG
HR400
12-24
Processing class 06
Payroll subschema XLR0
Processing class 06
PORT X006 P06 NOAB
Import last payroll account
Maintain all results wage types with regard to importing wage
types from the last payroll account
 SAP AG 1999
n Wage types from the last payroll result that are relevant to the current payroll run are placed in
internal table LRT (Last Result Table) to be used later.
© SAP AG
HR400
12-25
Processing class 01
Payroll subschema XT00
Processing class 01
PIT X010 P01 Create valuation
bases
PIT X013 P01
Maintain basic pay for creating
valuation bases
 SAP AG 1999
n Use this processing class to code all the wage types that you need for the valuation of other wage
types. The valuation bases are stored in secondary wage types /0nn.
© SAP AG
HR400
12-26
Processing class 03
Payroll subschema XT00
Processing class 03
PIT X020 P03
Cumulation
and storage of
time wage types
Maintain basic pay data and time wage types for storage
once time wage type processing is complete
 SAP AG 1999
n After valuation, time wage types can be cumulated into gross cumulation wage types and average
bases, and stored in the results table.
n Wage types from the infotype Basic Pay must also be coded in this processing class. They should
be passed on once time wage type processing is complete as they are usually required for factoring.
© SAP AG
HR400
12-27
Processing class 47
Payroll subschema XAP0
Processing class 47
P0014 X011 GEN NOAB
P0015 X011 GEN NOAB
Special processing infotypes 0014 and 0015
Check wage types in infotypes 0014 and 0015 with regard
to special processing in personnel calculation rule X011
 SAP AG 1999
n Under certain circumstances, you may need to effect special processing for certain recurring
payments/deductions wage types and additional payments wage types.
n Example:
Union dues are calculated in accordance with the amount of gross income.
© SAP AG
HR400
12-28
Processing class 10
Payroll subschema XAL0
Processing class 10
PIT XVAL P10
Factoring
Maintain unstored wage types for partial period payroll
 SAP AG 1999
n All of the wage types that are not stored after time wage type processing must be coded for partial
period factoring.
© SAP AG
HR400
12-29
Processing class 31
Payroll subschema XAL0
Processing class 31
PIT XCM0 P31
Create monthly lump sums
for Cost Accounting
Maintain gross wage types for cost distribution
 SAP AG 1999
n All the wage types that are not stored after time wage type processing must be encoded with regard
to their influence on the calculation of monthly lump sums for Cost Accounting.
n From the employee's point of view, paid absences have no effect on his or her basic pay wage
types. Cost Accounting, however, makes a distinction between remuneration effected for
attendance and remuneration effected for absence. For this reason, cost accounting wage types are
created during payroll. This processing class enables you to determine the wage type amounts that
are included in the cost accounting wage types.
© SAP AG
HR400
12-30
Processing class 20
Payroll subschema XAL0
Processing class 20
PIT X023 P20 NOAB
Cumulation and storage
Maintain remaining gross wage types for cumulation
and storage after gross calculation of pay
 SAP AG 1999
n Processing class 20 enables you to determine if and how wage types are stored in the results table
after the gross calculation of pay, and in which cumulation and averages wage types they are
cumulated.
© SAP AG
HR400
12-31
Processing class 25
Payroll subschema XNN0
Processing class 25
PIT X045 P25
Import
net payments/
deductions in
the RT
Maintain wage types for external bank transfers to be
processed by net payroll
 SAP AG 1999
n Processing class 25 determines how to store wage types that are entered through the infotype
External Bank Transfers. These wage types cannot be cumulated in gross cumulation wage types,
as they are processed in the net part of the payroll run.
© SAP AG
HR400
12-32
Processing class 30
Payroll subschema XEND
Processing class 30
PRT X080 P30 NOAB
Update of cumulation wage
types in CRT
Maintain all wage types for wage type cumulation in CRT
 SAP AG 1999
n Wage types can be cumulated for several periods in the Cumulated Results Table. In processing
class 30, you code wage types that are to be evaluated as an annual valuation, or that are to be listed
on the remuneration statement.
© SAP AG
HR400
12-33
Processing class 15
Payroll subschema XT00
Processing class 15
PIT X015 GEN
Time wage type
valuation
Maintain (time) wage types valuated using an average value
with regard to the calculation rule for averages you want to use
 SAP AG 1999
n In this processing class, you code the wage types that must be valuated using averages based on
values from previous periods. The specification of this processing class determines the calculation
rule for averages that is used to calculate the average value.
n Use in personnel calculation rules X015 - X018.
© SAP AG
HR400
12-34
Creating Bases for Calculating Average Values
(Old)
WT
MM10
Overtime 25%
Start
End
Averages
RTE
Rate
NUM Number
x
AMT Amount
100,00 100,00 100,00 100,00 100,00
%
x
/201
Average basis 01
x
/202
Average basis 02
/203
Average basis 03
/204
Average basis 04
 SAP AG 1999
n When creating the bases for calculating average values, you must determine if and how each
primary wage type is used to calculate averages.
n The various bases for calculating average values created here can be used for diverse valuations
when calculating average values in cumulation rules.
n In this scenario, basic remuneration for overtime is cumulated in wage type /201, and also in wage
type /202.
© SAP AG
HR400
12-35
Valuating Averages Using a Primary Wage Type
WT
M400
Vacation bonus
Processing class
15
Valuation according to principle of averages
Specification
1
Valuation of averages over 3 months
 SAP AG 1999
n All primary wage types to be valuated using an average must be maintained in processing class 15.
The system queries the specification in personnel calculation rule X016.
n In the standard system, wage types are not valuated according to the principle of averages.
© SAP AG
HR400
12-36
Defining Calculation Rules for Averages
Special processing rules for the valuation of time wage types
X016
E
*
E
****
E
VWTCL 15
E
Processing class
*
ADDWT *
E
E
Add in table OT
1
MEANV 01
Access average calculation rule
MULTI NRA
Multiplication
ADDNA *
Combine number and amount
2
Calculation rule
MEANV 02
MULTI NRA
01
...
02
...
ADDNA *
 SAP AG 1999
n To process averages, it is important that you determine the calculation rule. This occurs in
personnel calculation rule X016 where decision operation VWTCL 15 queries processing class 15.
Wage types to be valuated according to the principle of averages have a specification in processing
class 15. For each specification you enter, the system calls operation MEANV nn, where nn is the
average value calculation rule.
© SAP AG
HR400
12-37
Calculation Rules for Averages
The calculation rule is identified as follows:
Relevancy test
Cumulation rule for
average basis
Personnel calculation
rule for final processing
Maximum number of previous
periods to be included
Number of relevant
previous periods required
Possible
wage type
01
X017
01
X018
06
03
 SAP AG 1999
n The following values must be entered for each calculation rule:
1. The personnel calculation rule in which your relevancy test is stored.
2. A cumulation rule: You can either create a cumulation rule or use an existing rule.
3. The personnel calculation rule in which your final processing rule is stored; that is, the rule in
which the average is actually calculated.
4. The maximum number of periods that can be used to determine the relevant periods.
5. The number of relevant periods used to cumulate the average bases.
6. A wage type that allows exceptions for individual employees (for example, manual changes to
the average value or an average value for new employees).
© SAP AG
HR400
12-38
Creating Cumulation Rules (1)
View: Calculation Rules for Averages
Calc.rule
Rel.test
Cumul.
F.process. Max.no.per
No.rel.per
01
X017
03
X018
3
3
02
X017
09
X018
6
6
WT
View: Cumulation Rules for Average Bases
Cumulation
WT Start
End
CumNUM CumRTE CumAMT Adjust.
03
/201
+
+
09
/206
+
+
 SAP AG 1999
n The Cumulation field in the view Calculation Rules for Averages references the Cumulation field
in the view Cumulation Rules for Average Bases.
n Secondary wage types /201 - /232 can be used for the cumulation rules.
© SAP AG
HR400
12-39
Creating Cumulation Rules (2)
The cumulationrule is identified by:
Wage type
Sign indicating
cumulationin NUM
Sign indicating
cumulationin AMT
Sign indicating
cumulation in RTE
Adjustment rule
01

/201
+
+
SAP AG 1999
n A list is displayed of wage types (/201 - /232) used with the cumulation rules that were entered as
average types. The field used for the calculation is flagged accordingly.
+
Cumulation with positive sign
Cumulation with negative sign
" " No cumulation
n To adjust a wage type due to pay increase, the entry in the last field references the modification
indicator for the average bases.
© SAP AG
HR400
12-40
Creating Relevancy Test
Relevancy test for the valuation of averages
X017
E
*
E
****
MEANV REL
MEANV REL
=
MEANV 00,...99 =
Period is relevant
Calculation rule for averages
 SAP AG 1999
n This step enables you to determine the periods that are used for averages processing.
n As a general rule, periods that occur immediately before the current payroll period are always used
for the formation of averages. Sometimes a period cannot be used because, for example, the
employee was absent for its duration rendering it unrepresentative for a calculation rule for
averages. The system sets the status of each period as being relevant or irrelevant.
n Each period is processed as follows:
The system imports the payroll results for the previous period and calls personnel calculation rule
X017. In this rule, you can include wage types from the imported payroll result in the relevancy
test. You do this with operations AMT, RTE and NUM (for example, AMT=O….,). MEANV REL
specifies that the period is relevant to the calculation of averages otherwise it is irrelevant; that is, it
is not included in the subsequent cumulation of the average bases.
© SAP AG
HR400
12-41
Creating a Final Processing Rule
Calculating the average after cumulation
X018
E
*
E
Table MV
****
Rule
NUM
NUM?0.00
1
20
E
2
NUM=M
E
*
RTE
AMT
500
AMT=M
DIVID ANR
=
Work area
NUM
RTE
AMT
for wage type
20
25
500
 SAP AG 1999
n An average calculation must result in the Rate (RTE) field containing a valuation basis. The
formula used to calculate this value is included in personnel calculation rule X018.
n The internal table MV contains the cumulations for averages.
n Standard rule X018 uses the formula amount/number to calculate hourly rates.
© SAP AG
HR400
12-42
Technical Procedure of Average Processing
1)
Average already calculated?
(X016)
yes
RTE
no
2)
Import previous period
Is period relevant?
(X017)
no
yes
Cumulation acc. to cumulation rule
3)
Maximum number of periods fulfilled?
no
yes
4)
Calculation of average(X018)
 SAP AG 1999
n 1. Has an average value already been calculated for the employee in the current payroll period and
for the relevant calculation rule for averages? If so, the average value is stored in the RTE field.
n 2. Each previous period that needs to be processed is imported starting with the current period -1.
A relevancy test is then performed in personnel calculation rule X017. If the period is relevant,
cumulation takes place in accordance with a cumulation rule that determines which average
bases are cumulated and how.
n 3. The system determines whether the maximum number of periods to be used for the calculation
rule for averages has been reached.
n 4. Final processing takes place in personnel calculation rule X018. It consists of calculating the
average value and making the appropriate entry in the RTE field of the wage type requiring
valuation.
© SAP AG
HR400
12-43
Creating Adjustment Rules (1)
View: Cumulation Rules for Average Bases
Cumulation
WT Start
End
CumNUM CumRTE CumAMT Adjust.
03
/201
+
+
02
09
/206
+
+
03
View: Adjustment Rules for Average Bases
Adjustment Ind:NUM
Ind:RTE
IndAMT
02
4
03
1
VBasis
01
WT
No.period
3
3
 SAP AG 1999
n The view Adjustment Rules for Average Bases contains rules that can be used to increase average
values if pay increases. For each field (NUM, RTE and AMT) of the average calculation basis, you
can specify by which adjustment factor the relevant field should be multiplied.
© SAP AG
HR400
12-44
Creating Adjustment Rules (2)
The adjustment rule is identified by:
Mod. ind. for NUM
Mod. ind. for RTE
Mod. ind. for AMT
Val. basis /0nn
% rate
No. of
periods
01
01
3
 SAP AG 1999
n To adjust a wage type due to pay increase, the entry in the last field references the modification
indicator for the average bases.
© SAP AG
HR400
12-45
Creating Adjustment Rules (3)
Modification indicators
NUM
1
RTE
AMT
2
2
3
3
4
4
1
1
 SAP AG 1999
n Increase factor 2 is calculated as follows:
Basic standard pay for the employee in the rel. period
Basic standard pay for the employee in the rel. pre vious period.
This factor not only takes account of changes to the pay scale, but also of reassignments to different
wage groups.
n Increase factor 3 is calculated as follows:
Basic standard pay for the employee in the rel. period
Basic standard pay for the employee in the rel. previous period.
The difference to increase factor 2 is that basic standard pay in the period in question is determined
by the pay scale features of the previous period. Reassignments to different wage groups are not
taken into account.
n In increase factor 4, an identifier for a valuation basis must also be specified in the field NN. The
increase factor is then calculated as follows:
RTE field of /0nn in the rel. period
RTE field of /0nn from the rel. previous period.
In this case, pay scale and individual bonuses are taken into consideration.
n Increase factor 1 is determined using the table Adjust Average Bases According to Pay Scale .
© SAP AG
HR400
12-46
Creating Adjustment Rules (4)
View: Adjustment Rules for Average Bases
Adjustment Ind:NUM
Ind:RTE
IndAMT
02
09
4
VBasis
WT
01
No.period
3
1
3
View: Adjust Average Bases to Pay Scale
PStype
PSarea
GrpPSRule
Start
Percent1
Percent2
01
01
1
01.04.1998
105,000
95,000
01
01
2
01.04.1998
106,000
0,000
01
01
3
01.04.1998
106,000
0,000
 SAP AG 1999
n Modification indicator 1 references the table Adjust Average Bases to Pay Scale .
n Percentage 1 specifies a standard pay increase if working time does not change. A reduction in
working time with full pay is specified in percentage 2.
n If the NUM or AMT fields specify modification indicator 1, the increase factor corresponds to
percentage 1.
n If modification indicator 1 is entered in the RTE field, the increase factor is calculated as follows:
Percentage 1 is divided by percentage 2, if percentage 2 <> 0, or
percentage 1, if percentage 2 = 0.
© SAP AG
HR400
12-47
Views Used to Calculate Averages
1. Calculation rules
Rule
CumRule
CumRule
2. Cumulation rules
Rule
AdjRule
AdjRule
3. Adjustment Rules
AdjRule
IndNUM
IndRTE
IndAMT
4. Adjusting the average
calculation bases to the
pay scale
PStype
PSarea
PS ID
PRZN1
PRZN2
 SAP AG 1999
n If you flag the relevant rule in the view Calculation Rules for Averages, you can use the
navigation field to access subsequent rules.
n If you calculate averages without taking individual pay increases into account, you only require
entries in the first two views.
n If you must take individual increases in an employee's basic pay into account, an entry is required
in view 3.
n If you have to take pay scale increases in basic pay into account, additional entries are required in
view 4.
© SAP AG
HR400
12-48
Frozen Averages
Special processing rules for the valuation of time wage types
X016
VWTCL 15
Processing class
…..
E
A
ABEVL?
E
0
E
Absence periods
1
E
2
E
3
MEANV 10
MEANV 10
RTE=L /02A
RTE=L /02A
MULTI NRA
MULTI NRA
MULTI NRA
MULTI NRA
ADDNA *
ADDNA *
ADDNA *
ADDNA *
ZERO= NA
ZERO= NA
ELIMI *
ELIMI *
ADDNAE/02A
ADDNAE/02A
 SAP AG 1999
n If you assign specification A to a wage type in processing class 15, personnel calculation rule X016
calls decision operation ABEVL?. This operation determines whether an employee's absence is
longer than the current period and returns the values 0, 1, 2 and 3.
0
The absence starts and ends in the current payroll period; normal calculatio n of averages.
1
The absence starts in the current period and ends in the subsequent period:
The average value is calculated in the current period and frozen in the subsequent period.
Operation ADDNAE/02A stores the amount specified in the rate (RTE) field in wage type
/02A, and saves it to internal table RT. Storing the rate, that is, the average value, in this
wage type freezes it and enables valuation of the same absence in the subsequent period.
2
The absence starts in the previous period, spans the current period, and ends in the
subsequent period. In this case, the system uses the frozen average value from the previous
payroll period to valuate the absence in the current period. The average value is then frozen
again for valuation in the subsequent period.
3
The absence starts in the previous period and ends in the current period. In this case, the
absence is valuated using the frozen average value from the previous period.
© SAP AG
HR400
12-49
Calculating Overtime
Processing overtime wage types
TC00
E
*
E
****
E
OUTOTCLTYP
E
Clearing key in variable key
*
ADDZL *
E
Add in table ZL
2
ADDZL MM70
Add in table ZL
ADDZLM1
M = Overtime, create 1st and 2nd
derived wage type
ADDZLM2
E
3
HRS *%012
Multiplication
ADDZLMM70
 SAP AG 1999
n The value of the overtime compensation type in the infotype Overtime (2005) determines how
employees are compensated for overtime. The standard specifications are as follows:
•
1: Remuneration
•
2: Basic pay for free time, bonuses paid
•
3: Compensation
n In the specification for compensation, operation HRS multiplies the number of hours field by the
percentage specified for the current, first and second derived wage type in the table Wage Type
Valuation.
n Processing class 17 determines overtime compensation for wage types included in payroll through
cluster B2.
n Personnel calculation rule TC10 references processing class 17 of the overtime wage types and the
overtime compensation type assigned to the overtime quota. This occurs to decide whether the
wage type, or derived wage types, should be stored in table ZL (remuneration of overtime and
bonuses), or whether a time-off quota should be set up (compensation by time in lieu).
© SAP AG
HR400
12-50
Overview of Archiving in HR
R/3 DB
Archiving objects
Archive
files
PA_CALC
PA_TIME
PA_TRAVEL
Archiving in HR
ArchiveLink
 SAP AG 1999
n Data to be archived in the R/3 database can only be archived using archiving objects that are
available in the system, which describe the structure and composition of the data. For payroll
results, this object is PA_CALC.
n Essentially, the archiving procedure can be broken down into two steps:
•
The creation of archiving files: When archiving takes place, the archiving data is first written
sequentially to a newly created file. These archive files can, for example, be transferred to an
archiving system using an ArchiveLink.
•
Initializing the delete program: On the basis of the created archive files, the deletion program
removes data from the data base.
n The archived data can be displayed, without being restored, with the report RPCLSTxx
(xx = Cluster-ID).
n If you want to archive data, you must first create an archiving group.
© SAP AG
HR400
12-51
Contents of an Archiving Group
l Country for which the payroll results were created
l Selection of archiving objects
l Archiving date
l Retroactive accounting limit
l Country-specific parameters for payroll
l Selected personnel numbers, for example
- All employees who have left the company
- All employees in one personnel area
 SAP AG 1999
n The archiving group is a special structure for archiving. It allows you to summarize archiving
objects from Payroll, Time Management and Travel Management, if these components are
integrated.
n To create an archiving group, you have to specify its characteristics. To enable you to do this, the
system asks you questions step by step.
n The Archiving date is the date up until which payroll data, based on personnel numbers, is to be
archived. The retroactive accounting limit is the date that determines how far back the assigned
personnel numbers can be accounted.
n To create an archiving group, you can take one of the following approaches:
a) You specify the archiving date. The system proposes a retroactive accounting limit that comes
as soon as possible after the archiving date, and ensures that country-specific requirements are
taken into consideration.
b) You specify a retroactive accounting limit. The system proposes an archiving date immediately
before the specified retroactive accounting limit, and ensures that country-specific requirements
are taken into consideration.
n At the end of this step, each archiving group receives a number that is supplied by the number
range. You must therefore create a number range for the number range object HRARCHIVE.
© SAP AG
HR400
12-52
The Archiving Process
l 1. Phase 1: Creating an Archiving Group
l 2. Phase 2: Assigning Personnel Numbers
l 3. Phase 3: HR Preparation for Archiving
n Test Run
n Release
n Execute
n Reverse
n Exit
l 4. Phase 4: Archiving
n Execute
n Exit
 SAP AG 1999
n When you create an archiving group, the system checks your entries to ensure that there are no
inconsistencies as a result of missing data.
n You then assign the relevant personnel numbers to an archiving group.
n Although it is not compulsory, you are nonetheless advised to carry out a test run before releasing
the archiving. The release status locks access to the payroll data for the assigned personnel
numbers. It is subsequently not possible to carry out retroactive payroll for these personnel
numbers, as they are locked for the payroll driver.
n After carrying out HR preparation for archiving, the payroll data is no longer accessible for payroll,
although it is still available in the database. Consequently, retroactive payroll runs are no longer
possible for archived periods. It is, however, possible to undo the HR preparation for archiving,
either for all the personnel numbers in an archiving group, or for individual personnel numbers.
You can then, if needs be, carry out necessary retroactive accounting runs.
n In the final step, the archive administration transaction (SARA) is called. Here, you create an
archiving job. This means the archive data, which is assigned to an archiving group, is transferred
by archiving object to an archive file and then deleted from the database.
© SAP AG
HR400
12-53
Off-Cycle Payroll
l Bonus payments
l Correction payroll runs
l Regular payroll
l Payments in advance
l Payment of an absence
 SAP AG 1999
n The Off-Cycle Payroll function enables you to carry out various payroll activities that are not
covered by the regular payroll run. The payroll control record is not affected by Off-Cycle Payroll.
The types of Off-Cycle Payroll that you can carry out depends on the settings in Customizing for
Payroll.
n If an employee is to receive a bonus payment, run Off-Cycle Payroll to trigger payment for the
employee.
n If you want to make a payment for an absence to an employee in future payroll periods, you run
payroll on a daily basis for the period in which the absence takes place.
n If master or time data was changed for an employee, you can use retroactive accounting to start a
correction run and trigger the payment.
n If an employee was hired shortly before the payroll date and his or her papers could not be
processed in time, you can run regular payroll, even if this is no longer possible for the payroll
area, or you can run payroll for this employee before running payroll for the whole payroll area the
next time.
n If an employee leaves the enterprise, or is absent for several periods and wants to receive the money
owed to him immediately, you can carry out payroll in advance for several periods with a payment
in advance. The personnel number is selected for payroll again when the period, for which payroll
has been run, has elapsed.
© SAP AG
HR400
12-54
The Process of Off-Cycle Payroll
Absence
Payment
Payment
of
of an
an absence
absence
Enter
absence
Off-Cycle Payroll
Specify the date, and the reason for the
payroll run.
Reason
0001 Holiday bonus
Date
06.12.1999
Run payroll
Payments in
advance
advance with
with
reg.payments
reg.payments
Payments
Payments in
in
advance
advance with
with
spec.payments
spec.payments
Payroll period
Payroll
Select
period
Special payments
payments
Payment
Payment
method
method
Change
payment
method
Run
Run
payroll
payroll
Enter
wage type
Other
Other payments
payments
 SAP AG 1999
n The Off-Cycle reason that you specify determines the subsequent payroll process.
n In the case of payment of an absence , the system proposes the absences that have already been
entered in the Absences infotype (2001), which were entered for off-cycle payroll runs in Payroll
Customizing. As an alternative, you can enter an absence directly from the program in the
Absences infotype (2001). The start and end date are the same for this type of absence. The system
writes the reason for Off-Cycle Payroll, the payment date, the payroll type and payroll
identifier in the Absences infotype (2001).
n In the case of advance payment, the system offers you the periods for which you can perform
payroll. You made this setting in Payroll Customizing. If you are paying several periods in advance,
the system carries out a regular payroll run for the last period that is to be paid. All other periods
that occur before this are dealt with by retroactive accounting. Consequently, for several periods
there is only one original result , and only one payment is made. The payroll control record is not
even taken into consideration in this payroll run. The employee is not selected for regular payroll
until the last period.
n In the case of a bonus payment, you must enter a wage type that is permitted for infotype 0267.
© SAP AG
HR400
12-55
Supplementing Payment Methods
Infotype 0009 for regular payroll runs
Subtype
Payment method
Payee
Bank
Bank
Bank account
0
Check
1
Transfer
Bank of America 1234567890
1
Transfer
Bank of America 0987654321
Default value
% rate
Michael Bond
100 USD
20,00
Supplementing
Payment Methods
Supplement
Supplement Payment
Payment Method
Method for
for Off-Cycle
Off-Cycle Payroll
Payroll
Subtype
Payment method
5
Check
6
Transfer
Check
date
date
Payroll
Payroll type
type
Payee
Payee
Bank
Bank account
account
Default value
% rate
rate
Michael Bond
Bank of America 9999999999
Payroll
Payroll
identif.
identif.
Off-Cycle
Off-Cycle
reason
reason
50,00
Off-Cycle
Off-Cycle
payroll run
run
 SAP AG 1999
n You can change the payment method during Off-Cycle Payroll. A record is created for the current
payment in the Bank Details infotype (0009). This record includes the reason for the Off-Cycle
Payroll, the payment date, the payroll type and the identifier. The record is only valid for the
current payroll run.
n As a default, payment by check is proposed. You can split the payment, and assign main and
secondary bank details.
n For Off-Cycle Payroll, the system proposes, when requested, the following subtypes of infotype
0009:
•
Subtype '5' for main bank details
•
Subtype '6' for secondary bank details
© SAP AG
HR400
12-56
Absence Valuation in Off-Cycle Payroll
Leave
Leave
(10.6.
(10.6. -- 20.6.)
20.6.)
Payment
Payment in
in advance
advance
of absence
absence
Regular payroll
Valuation acc
Valuation
acc.. to constants/averages
Valuation acc.
acc. to constants/averages
constants/averages
WT
Percent
Time unit
WT
MD01
100
KT
MD01
MD02
100
KT
MD02
Percent
Percent
100
Time unit
KT
KT
Counting classes
Counting
Counting class
class
01
Payt
Percent
Percent
100
 SAP AG 1999
n There are two procedures for paying absences in advance.
1. In a regular payroll run. In a regular payroll run, payroll is started for an employee after regular
payroll is already complete for the relevant payroll area.
2. In a payroll run that only deals with employee absences that should be paid in advance. In this
case, you set up special absence valuation rules for Off-Cycle Payroll. Generally, this applies to
absences such as leave and other types of time in lieu entitlements.
n The process of absence valuation in Off-Cycle Payroll:
1. The off-cycle run is carried out. Absences that are valuated in the course of the run are given a
special indicator at the start of Off-Cycle Payroll. You can display this indicator in the infotype
record for the relevant absence.
2. Payroll is run for the period of the absence that overlaps with the respective payroll
periods in a regular payroll run. The RAB function checks whether the absence(s) have the
off-cycle indicator flagged. If so, payroll can determine the differences betweeen the new
payroll run for the absence and the results in the off-cycle run. You can cumulate the
differences in specific wage types and counting classes.
n To valuate absences in Off-Cycle Payroll, two absence valuation rules must be set up for a group of
absences.
© SAP AG
HR400
12-57
Setting Up Reasons for Off-Cycle Payroll
View Reasons for Off-Cycle Payroll
OC-reason Description
OC Category
Payroll type
9000
9001
02
05
A
A
01
02
03
04
05
06
07
Sales bonus
Leave bonus
Regular
Bonus
Correction
Manual check
Absence payment
Payment in advance of periods
On-demand payroll for next period
A
B
C
__
Bonus payment
Correction run
Manual check
Regular
 SAP AG 1999
n In Off-Cycle Payroll, the administrator first has to select the off-cycle reason.
n In this step, you define the reasons that are available to the administrator. You also assign a
category to each reason.
n The category defines the type of payroll involved, and whether Off-Cycle Payroll is dealing, for
example, with a bonus or absence calculation, with a payment-in-advance, or with something else.
It is possible that similar reasons have the same category. For example, the reason 'sales bonus'
specifies the meaning of the payroll run in more detail.
n If you create your own reasons, note that these must begin with 9, Y or Z.
© SAP AG
HR400
12-58
Setting Up Off-Cycle Absence Valuations
View Reasons for Off-Cycle Payroll
OC-reason Description
PSGrp
Absence type
9000
9001
01
01
0100 Leave
0110 Leave 1/2 day
Leave bonus
Leave bonus
View: Valuate Absences
AbsValGrpg
Valuation rule
Off-cycle indicator
Wage type
4000
Percent
100
01
01
O
Paid leave
Start
End
Valuation in Off-Cycle Payroll
Time unit
AT
Day rule
WD
 SAP AG 1999
n In the first step, you specify which employee absence times can be valuated in an off-cycle payroll
run. To do so, you assign an off-cycle reason to each of the relevant absence types. At the start of
the off-cycle payroll run, the system then proposes to the administrator all of the employee's
absences, for which off-cycle reasons have been assigned to absence types in Customizing.
n In the next step, you specify the following absence valuation rules:
•
For the valuation of absences in the off-cycle payroll run
•
For the valuation of absences in the regular payroll run if an off-cycle payroll run has already
taken place.
To enable you to set up the Absence Valuation table, there is an additional key field: the
indicator for absence valuation in Off-Cycle Payroll. Depending on this indicator, you can
access various views of this table.
n Absence valuation:
•
Indicator O (Valuation in the off-cycle payroll run): Here, you can only specify
constants/averages.
•
Indicator R (Valuation in the regular payroll run with OC indicator): Here, you can display all
methods of absence valuation ('as if' principle, counting classes, and so on).
© SAP AG
HR400
12-59
Creating Process Models
Read Markers
Markers/Transfer to
to Process Model for Payroll Runs
Regular payroll runs
x Bonus runs
Correction payroll runs
Non-Authorized Manual Checks
Model-ID
SAPXXOC
Personnel number
to
Print Form
Program
Variante
RPCEDTU0
SAP_OC
Execute posting run
Program
Variant
Pre-program DME
RPCIPE00
SAP_OC
Program
Variant
RPCDTCU0
SAP_OC
Check processing
Program
Variant
H99_RFF_FRAME
SAP_OC
 SAP AG 1999
n Subsequent activities are necessary for all off-cycle payroll runs. The reports to be executed must
be grouped together in process models.
n The sequence of processing steps is defined in process models. A process model has the following
advantages:
•
It clearly illustrates how individual processing steps are linked together
•
It makes it possible to execute programs on a parallel basis
•
It makes it possible to easily repeat processes
•
It clearly illustrates the status of the process and the personnel numbers
•
It makes it easy to navigate to the job log and the program log
n If you use both the Off-Cycle Payroll function and the check replacement function, you require two
different process models, as the pre-program DME is already integrated in the check replacement
procedure. Unlike this, running pre-program DME for off-cycle payroll runs is a subsequent
activity and must be started in the process model.
n SAP provides several process models as a sample and template.
© SAP AG
HR400
12-60