WNA11

Advanced Payroll
Configuration:
Rule Writing in Payroll
 Copyright and Trademarks

§ No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of
SAP AG. The information contained herein may be changed without prior notice.
§ Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® are registered trademarks of Microsoft
Corporation.
§ IBM®, DB2®, OS/2®, DB2/6000®, Parallel Sysplex®, MVS/ESA®, RS/6000®, AIX®, S/390®, AS/400®, OS/390®, and OS/400® are
registered trademarks of IBM Corporation.
§ ORACLE® is a registered trademark of ORACLE Corporation.
§ INFORMIX®-OnLine for SAP and INFORMIX® Dynamic ServerTM are registered trademarks of Informix Software Incorporated.
§ UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks of the Open Group.
§ Citrix®, the Citrix logo, ICA®, Program Neighborhood®, MetaFrame®, WinFrame®, VideoFrame®, MultiWin® and other Citrix
product names referenced herein are trademarks of Citrix Systems, Inc.
§ HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts
Institute of Technology.
§ JAVA® is a registered trademark of Sun Microsystems, Inc.
§ JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and
implemented by Netscape.
§ SAP, SAP Logo, R/2, RIVA, R/3, SAP ArchiveLink, SAP Business Workflow, WebFlow, SAP EarlyWatch, BAPI, SAPPHIRE,
Management Cockpit, [Link] Logo and [Link] are trademarks or registered trademarks of SAP AG in Germany and
in several other countries all over the world. All other products mentioned are trademarks or registered trademarks of their
respective companies.

Disclaimer

THESE MATERIALS ARE PROVIDED BY SAP ON AN "AS IS" BASIS, AND SAP EXPRESSLY DISCLAIMS ANY AND ALL WARRANTIES,
EXPRESS OR APPLIED, INCLUDING WITHOUT LIMITATION WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE, WITH RESPECT TO THESE MATERIALS AND THE SERVICE, INFORMATION, TEXT, GRAPHICS, LINKS, OR ANY OTHER
MATERIALS AND PRODUCTS CONTAINED HEREIN. IN NO EVENT SHALL SAP BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL,
INCIDENTAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES OF ANY KIND WHATSOEVER, INCLUDING WITHOUT LIMITATION LOST REVENUES
OR LOST PROFITS, WHICH MAY RESULT FROM THE USE OF THESE MATERIALS OR INCLUDED SOFTWARE COMPONENTS.

ã SAP AG 2013 WNA11

 WNA11 APC: Rule Writing in Payroll
This workshop will cover the following topics:

n Optimizing standard processing of SAP payroll

n Editing payroll schemas and rules

n Creating custom personnel calculation rules

n Analyzing errors during payroll processing

n Reviewing payroll results

n Analyzing functions and operations

n Using debugger to review the payroll process

ã SAP AG 2013 WNA11

 WNA11 Course Outline

Ø Unit 1 Payroll Processing

Ø Unit 2 Maintaining Schemas and Rules
Ø Unit 3 Wage Type Configuration
Ø Unit 4 Customizing Payroll Processing
Ø Unit 5 Advanced Processing Options
Ø Unit 6 Appendices

ã SAP AG 2013 WNA11

 Course Prerequisites
n Courses:
u HR050 Business Processes in HCM
u HR305 Master Data Configuration

u HR306 Configuration of Time Recording

u HR400 Payroll Configuration

u HR410 or HR407 U.S./Canadian Payroll

ã SAP AG 2013 WNA11

 Main Business Scenario
n Your company uses SAP’s US payroll solution. However, you need
to customize the standard schema to incorporate unique company
pay practices and union requirements.

n In addition, you want to build some safeguards into the payroll

process to ensure that only those payroll records for which
complete data is available will be passed through to the various
programs of post-payroll processing.

n You would also like to determine when to use table customizing

versus creating new custom PCRs.

ã SAP AG 2013 WNA11

Payroll Processing

Contents:
•Processing Payroll via RPCALCU0
•PA03: The Control Record
•IT0003: Payroll Status Infotype
•Tables V_T582A, V_T588G and V_T591B
•Report RPUTRBK0
Payroll Processing

Release Payroll
Advance control record
Lock master data

Release for
Start Payroll Corrections
Run RPCALC_0
Unlock master data

Check Results
Lock master data
Lock payroll
CHECK
Exit Payroll ABR
Release master data
Lock control record

ã SAP AG 2013 WNA11

Payroll Processing: Running Payroll

Country-specific
payroll driver

ã SAP AG 2013 WNA11

Reviewing the Payroll Log

ã SAP AG 2013 WNA11

Managing the Control Record

ü Controls status
of Payroll Area

ü Monitors run
number

ü Defines payroll
present and past

ü Limits
retroactivity

ã SAP AG 2013 WNA11

Managing Payroll Status

ã SAP AG 2013 WNA11

Report RPUTRBK0

ã SAP AG 2013 WNA11

Unit 2: Payroll Overview

Exercise 1: Hiring Salaried Employee

1 Hiring first employee

A. Via PA40, Create the personnel number 11101## (## = your group
number) using the personnel action type Hire:

Entry date 01/01/YYYY

Personnel area 3300
Employee group 1
Employee subgroup U4 (salary worker)
Personnel Subarea 0001 Production
Payroll Area 4# (# = Payroll area assigned to Group)
Position None
Name Any
Birth Date Any
Social Security Number Any valid 9 digit number
Street Address Any
City Los Angeles
State CA
Zip Code 90210
Withholding Tax Authority FED
Withholding Status Single
Allowances Your choice
Pay Scale Group/Level GRD01/01
IT0378 Adj Reasons Cancel, Not necessary
Payment Method Check

ã SAP AG2013 WNA11 1-8

2. Running Payroll
A. Run payroll for your payroll area 4# and your employee 11101## for
period 01, YYYY. Review the payroll log for errors. Do not exit payroll
for period 1 yet!

ã SAP AG2013 WNA11 1-9

Unit 2: Payroll Overview

Solution 1: Hiring Salaried Employee

1 Hiring first employee

A. To hire a salaried employee, go to:
SAP Menu: Human Resources > Personnel Management >
Administration > HR Master Data > Personnel Actions
Enter the personnel number 11101##, the entry date 01/01/YYYY and
select the action type Hire. Execute. Enter the data from the exercises on
the appropriate infotypes, selecting Enter to review the defaults and saving
each infotype to progress through the hiring action. Make sure you assign
the employee to payroll area 4# (The payroll area assigned to your
group…see exercise data) on the Organizational Assignment infotype
(0001) and no position.
2 Running Payroll For Period 1, YYYY

A. To run payroll for your employee for period 01, YYYY, go to:

SAP Menu: Human Resources > Payroll > Americas > USA >
Payroll > Release Payroll

Release payroll for payroll area 4#.

Menu: Human Resources > Payroll > Americas > USA > Payroll >
Start Payroll

Enter payroll area 4# in the Payroll Period section and in the Selection
section of the payroll driver. Use the multiple selection and enter
personnel number 11101##. Select the Display log check box. Execute
the payroll run.
Review the payroll log. [Correct any errors in master data, if necessary,
and run payroll again.] Do not exit payroll for period 1.

ã SAP AG2013 WNA11 1 - 10

 Maintaining Schemas and Rules

Contents:
n Concept

n Structure

n Maintenance

ã SAP AG 2013 WNA11

 Maintaining Schemas and Rules: Unit Objectives

l Describe how schemas and rules are read by the payroll program
l Identify the different components of a schema
l Use the schema editor to copy and edit customized schemas
l Identify the tables that are updated when a new schema is
created
l Interpret the documentation of a function within a schema
l Document a new schema or personnel calculation rule
l Identify the different components of a personnel calculation rule
l Use the rule editor to copy, create and edit personnel calculation
rules

ã SAP AG 2013 WNA11

 The SAP Payroll Project
Conventional SAP payroll
payroll program accounting

... coding Payroll driver

ABAP/IV coding Flow control Payroll
RPCALC_0 Maintaining IMG
customizing

RPCALC_0

Schema
IMG

Function
module
Operation
module Rules

ã SAP AG 2013 WNA11

 Maintaining Schemas

ã SAP AG 2013 WNA11

 Schema Attributes

Choose
language

Country-specific or
Main or all countries
subschema

Limit change
access

ã SAP AG 2013 WNA11

 Maintaining Schemas
Maintain schema
PE01 1
Schema name
Decision tree 2
Command line
1
3
Line number
2
4
Function

5
Parameters 1-4

6
Deactivate function
7
Text
3 4 5 6 7

ã SAP AG 2013 WNA11

 Documenting Schema Changes

ã SAP AG 2013 WNA11

 Schema Comparisons

Modified
Schema
(T52C1)

Standard
Schema
(T52C0)

Differences

ã SAP AG 2013 WNA11

 Maintaining Personnel Calculation Rules

ã SAP AG 2013 WNA11

 Rule Attributes

ã SAP AG 2013 WNA11

 Table Editor

Sequence
1
number

1 2 2 Variable
5 key
Next line
3
indicator
3
4 Rule type

4 5 Operations

ã SAP AG 2013 WNA11

 Structural Graphics Rule Editor

Sequence
1
number

2 2 Variable
key
Next line
3
indicator
4 Rule type

5 Operations
5

ã SAP AG 2013 WNA11

 Rule Access

ã SAP AG 2013 WNA11

 Accessing Personnel Calculation Rules
n Called via functions
n Parameter values determine the access variants for the personnel
calculation rule
u Processing unique to Employee Subgroup Grouping for Personnel
Calculation Rule
u Processing of a selected group of wage types only

u Processing class determination of appropriate processing

ã SAP AG 2013 WNA11

 Rules: Access Variants
PIT
Function

Rule
Par1

GEN Pnn

Par2

NOAB NOAB NOAB

Par3

ã SAP AG 2013 WNA11

 Rules: Access Variants: Example PIT

GEN Pnn

Par2 Wage Type Access

Wage Types Generic Processing Class

nnn1 **** ****

NOAB

Par3 Employee Subgroup Grouping for PCR Access

Generic ESG for PCR

* 1, 2, 3

ã SAP AG 2013 WNA11

 Payroll Functions

PDSY

ã SAP AG 2013 WNA11

 Functions and Rules
n ACTIO Perform Rule n PDT Process Differences table
n MOD Set Modifiers n PIT Process Input Table
n P0009 Import Bank Details n PLRT Process Last Results Table
n P0014 Import Recurring n PORT Transfer of Data from
Payments/Deductions Previous Period
n P0015 Import Additional Payments n PRART Process Old Arrears Table
n P0221 Import Payroll Results n PRT Process Results Table
Adjustments n PTCRT Process Tax Cumulated
n P0267 Import Additional Payments Results Table
Off Cycle n PZL Process Time Wage Types
n P2010 Import Employee Table
remuneration Information n UMOD Set US Tax Modifiers
n PALP Process Alternative Payment
Table

ã SAP AG 2013 WNA11

 Creating a Personnel Calculation Rule
1) Create rule attributes
2) Decide upon appropriate rule access
3) Define access variables
4) Create decision tree, if necessary
5) Enter operations to perform processing
6) Consider input necessary and output expected to determine
possible schema locations in which rule can be entered
7) Enter rule into schema selecting appropriate function and rule
access
8) Create necessary data for testing
9) Run payroll to test the rule

ã SAP AG 2013 WNA11

 Maintaining Schemas and Rules: Unit Summary

l Schemas and personnel calculation rules are

the main areas in which customization of
payroll takes place
l When editing schemas and rules it is
important to document any changes
l Customized schemas can be compared to
system-delivered schemas to identify
changes

ã SAP AG 2013 WNA11

Unit 2: Maintaining Schemas and Rules

Exercise 1: Working with Schemas/Rules

1 Working with Schemas

A. Copy schema U000 to Z##U.
B. Copy subschema UT00 to Z##T.
C. Copy subschema UMO0 to Z##M
D. Incorporate subschemas Z##M and Z##T into schema Z##U.
E. Change the documentation for your new schema, Z##U, to reference the
changes you have made.
F. Compare schema U000 to your schema Z##U, noting any changes.
G. Create a variant for a payroll run and rerun payroll for your employee
11101## for period 01, YYYY, using your new schema. Review the log. If
there are no errors, exit period 1.

ã SAP AG 2013 WNA11 2 - 21

Unit 2: Maintaining Schemas and Rules

Solution 1: Working with Schemas/Rules

Menu: Human Resources > Payroll Accounting > Americas > USA > Tools >
Customizing Tools > Schema (Or, Transaction Code: PE01)
A. Select the Copy icon. Enter schema U000 in copy from and your new
schema Z##U in copy to. Choose Enter to copy the schema. Review the
structure by selecting Display.
B. Using the same method as above, make copies of subschema UMO0,
(renamed Z##M) and subschema UT00, (renamed Z##T).
C. To incorporate subschemas Z##M and Z##T into main schema Z##U,
return to the schema editor (Transaction Code PE01).

Enter schema Z##U and select the Change icon. To replicate the line
COPY UMO0, place an “r” in the sequence number field, and press
“enter”. Deactivate the original line which calls subschema UMO0. On
the active line, replace the value “UMO0” with your subschema Z##M.
Repeat the same process and replace UT00 with Z##T. Save your schema.
F. From the main schema editor screen, select the Documentation radio
button, then select the Change icon. Enter any text you like. Save.
G. To compare your schema to the original schema, enter your schema using
either change or display from the schema editor. Then, go to Menu:
Schema -> Compare. Enter schema U000 and select enter. Review the
comparison log. You may also want to compare schema UT00 to schema
Z##T.
H. To again run payroll for period 1 with your new Schema, go to: Menu:
Human Resources > Payroll Accounting > Americas > USA > Payroll
Accounting > Start Payroll

Enter your payroll area 4# in both the payroll period area and the selection
area of the driver screen. Select Display Log for both logs. Enter your
main schema Z##U in the Schema field.
Save your entries as a variant. Select the save icon, give your variant a
name and a description and choose Continue (enter).
Execute the payroll run. When you are finished reviewing the payroll,
exit the payroll run by going to: Menu: Payroll Accounting > Exit
payroll.

ã SAP AG 2013 WNA11 2 - 22

 Wage Type Configuration
Contents:
n Wage Type Configuration
n Configuration Reporting

ã SAP AG 2013 WNA11

 Wage Type Coding

Primary Wage Types

§ Dialog
§ Basic Pay
§ Additional Payments
§ Recurring Pay/Dedn
§ EE Remuneration Info
§ Time
§ Time Evaluation
§ Time WT Selection Rules
§ Absence
§ Absence Valuation
§ Time WT Selection Rules

ã SAP AG 2013 WNA11

 Wage Type Coding (United States)
Secondary Wage Types (US) Secondary Wage Types (US)
§ Valuation Bases /0_ _ § Taxable for Tips /E_ _
§ Cumulation /1_ _ § Reportable for Tips /F_ _
§ Average Bases /2_ _ § Garnishments /G_ _
§ Gross for Taxes /3_ _ § Non-effected
§ Tax Amount /4_ _ Deductions Tips /H_ _
§ Retro/Net Pay /5_ _ § Non-reduced Taxes /N_ _
§ Taxable Wages /6_ _ § Taxable, not Taxed /Q_ _
§ Reportable Wages /7_ _ § Regular Rate of Pay /R_ _
§ Factoring/CO /8_ _ § Taxable, not Taxed
§ Benefits /B_ _ for Tips /U_ _
§ Gross for Tips /C_ _ § Outflow /X_ _
§ Tax for Tips /D_ _ § Inflow /Z_ _
ã SAP AG 2013 WNA11
 Wage Type Coding (Canada)

Secondary Wage Types (CA) Secondary Wage Types (CA)

§ Valuation Bases /0_ _ § Benefits /B_ _
§ Cumulation, Tax § Garnishments /G_ _
Bases, Workers’ § Inflow for Tax Base /I_ _
Compensation /1_ _ § Loan Repayment /L_ _
§ Average Bases /2_ _ § Outflow for Tax
§ Tax Amount /3_ _ Base /O_ _
§ Tax Amount /4_ _ § Outflow /X_ _
§ Retro/Net Pay /5_ _ § Inflow /Z_ _
§ Employer Costs /7_ _
§ Factoring/CO /8_ _

ã SAP AG 2013 WNA11

 Model Wage Types
n SAP Delivered
u BAxx After Tax Benefits u M5xx LTI
Contributions u M7xx Voluntary Deductions
u BExx Employee Benefits u M8xx Time
Contributions/Pre-Tax
u MDxx Specialized Deductions
u BPxx Benefits Provider Payments
u MGxx Garnishments
u BRxx Employer Benefits
u MJxx Travel
Contributions
u MIxx US Time
u CMxx Compensation
u MLxx Incentive Wages
u Mxxx Basic
u MMxx Overtime
u M1xx Specialty Payments
u Txxx Tips
u M2xx Deductions/Donations
u M3xx Tuition Reimbursement
Relocation Expenses

ã SAP AG 2013 WNA11

 Wage Type Catalog

ã SAP AG 2013 WNA11

 Wage Type Configuration: Dialog Wage Types
n Characteristics V_T511
u Deductions or Earnings
u Amount or Number per Unit
u Indirect or Direct Valuation
n Permissibility V_T512Z
u Defining entry permissibility per infotype
n Eligibility
u Employee Subgroup Grouping for Primary Wage Type V_503_G
u Personnel Subarea Grouping for Primary Wage Type V_001P_K
n Groups V_511_B (See report RPDLGA00)
u Define access within the IMG
n Cumulation Classes V_512W_O
u Building /1_ _ wage types
n Processing Classes V_512W_O
u Define processing within the payroll run

ã SAP AG 2013 WNA11

 Wage Type Configuration: Processing Classes

ã SAP AG 2013 WNA11

 Wage Type Configuration: Cumulation Classes

U.S.

Canada

ã SAP AG 2013 WNA11

 Wage Type Configuration: Basic Pay
n Characteristics n Processing Classes
u Payment u 01 – Addition to Valuation Basis
u Indirect valuation
u 10 – Factoring (proration)

n Permissibility u 20 – Storage and cumulation

u Basic Pay (IT0008) u 30 – Annual/Period cumulation

n Eligibility u 68-71 – US taxation

u 52-53, 69-70 – CA taxation,
n Groups workers’ comp and payment
n Cumulation Classes processing
u 01 – Total Gross
u 02 (US) – 401K Wages
u 14 (US) – BSI Wages
u 01, 02, 20-22, 40, 52, 71 (CA) –
Taxable income

ã SAP AG 2013 WNA11

 Basic Pay Configuration

ã SAP AG 2013 WNA11

 Wage Type Configuration: Payments
n Characteristics n Processing Classes
u Payment
u 10 – Factoring (proration)
n Permissibility u 20 – Storage and cumulation
u Additional Payments (IT0015)
u 30 – Annual/Period cumulation
u Recurring Payments/Deductions
(IT0014) u 68-71 – US taxation
u One-Time Payments Off-Cycle u 52-53, 69-70 – CA taxation,
(IT0267) workers’ comp and payment
n Eligibility processing
n Groups u 76 – Special run inclusion

n Cumulation Classes
u 01 – Total Gross
u 02 (US) – 401K Wages
u 14 (US) – BSI Wages
u Various (CA) – Taxable income

ã SAP AG 2013 WNA11

 Wage Type Configuration: Deductions
n Characteristics n Processing Classes
u Deduction u 04 – Prorate and Cumulate (US)
u 05 – Storage and cumulation
n Permissibility u 06 – Carry forward
u Additional Payments (IT0015) u 10 – Factoring (proration)
u Recurring u 24 – Transfer control (claims)
Payments/Deductions (IT0014) u 41 – Storage and cumulation

n Eligibility u 50 – Deduction /Donation

processing
n Groups u 53 (CA) – Effect on absence

n Cumulation Classes u 70 (CA) – Tax cumulation

u 73 & 78 – 3rd party remittance
u 10 – EE deductions
u 76 – Special run inclusion
u 83 – Retrocalculation for
percentage deductions

ã SAP AG 2013 WNA11

 Wage Type Configuration: Payments and
Deductions

ã SAP AG 2013 WNA11

 Time Wage Type Selection
Import Time Data

Select Processing
Type

Time Wage Type

Selection

Cumulate Time Wage

Types

Valuate Time Wage

Types

ã SAP AG 2013 WNA11

 Time Wage Type Selection

ã SAP AG 2013 WNA11

 Wage Type Configuration: Time Wage Types
n Eligibility n Processing Classes
u 03 – Storage and cumulation
n Groups
u 17 – Overtime compensation
n Cumulation Classes type (Also used in RPTIME00)
u 01 – Total Gross u 30 – Annual/Period cumulation
u 02 (US) – 401K Wages u 68-71 (US) taxation
u 14 (US) – BSI Wages u 69-70 (CA) taxation
u Various (CA) – Taxable income u 86 (US) – Cumulate worked
hours
n Valuation
u Assign valuation bases
u May use derived wage types

ã SAP AG 2013 WNA11

 Absence Valuation (Wage Type Selection)
Import Absences

Absence Valuation

OR
“AS IF”
Time Wage Type
Selection

ã SAP AG 2013 WNA11

 Absence Valuation

ã SAP AG 2013 WNA11

 Internal tables PARTT and PARTA

SOLL DIVI DIVP (T510H) 0008

K Calendar Days A Work Days S Work Hours

These two tables can be accessed using operations RTE, NUM or AMT
The partial periods are available by using T and the whole periods using G
For example RTE=TSSOLL would fill the RTE field with the hours in “WHrs” for
each partial period. RTE=TSDIVI would fill the RTE field with the hours in
“WH1W” for each partial period.

ã SAP AG 2013 WNA11

 Internal table PARX with PARTA

Counting classes are stored on the PARX table by splits. These can be
used to create reduction factors if necessary. For example: RTE=TSAP02
would place the hours for absences assigned to counting class 02 in the
RTE field for each partial period.

ã SAP AG 2013 WNA11

 Wage Type Configuration: Absence Wage Types
n Eligibility n Processing Classes
u 03 – Storage and cumulation
n Groups
u 30 – Annual/Period cumulation
n Cumulation Classes u 68-71 (US) taxation
u 01 – Total Gross u 69-70 (CA) taxation
u 02 (US) – 401K Wages

u 14 (US) – BSI Wages

u Various (CA) – Taxable income

n Valuation
u Assign valuation bases
u May use derived wage types

ã SAP AG 2013 WNA11

 Configuration Reports: Wage Type Utilization

ã SAP AG 2013 WNA11

 Wage Type Tables
n Wage Type Valuation V_512W_O n Posting of Payroll Wage Types
V_T52EL
n Wage Type Characteristics V_T511
n Time Dependency of Wage Type
n Wage Type Text V_T512T
Posting V_T52EZ
n Wage Type Permissibility V_T512Z
n Assign Customizing Wage Type
n Absence Valuation V_T554C V_T52DZ
n Time Wage Type Selection n Wage Type Classes V_T52D7
V_T510S
n Customizing: Model Wage Types
n Assign to Wage Type Groups V_T52DZ
V_T52D7
n Cumulation (by calendar) V_T54C3
n Base Wage Type Valuation
n Time Constraints V_T591B
V_T539J

ã SAP AG 2013 WNA11

 Wage Type Configuration Tool (HRWTT00MAIN)

ã SAP AG 2013 WNA11

 Summary
n Wage types are the primary configuration elements of payroll
n Wage types may be split into two main categories, primary and
secondary (technical)
n Primary wage types are the responsibility of the customer for
maintenance and configuration
n Model wage types provide examples of configuration for primary
wage types
n Each type of primary wage types, dialog, time and absence, has
specific considerations for configuration
n Processing classes, cumulation classes and dialog characteristics
as well as other specialty table configuration characterize the wage
types for processing

ã SAP AG 2013 WNA11

Unit 3: Wage Types

Exercise 1: Creating New Pay scale Area with indirectly valuated wage
types.

1. Create a new pay scale area: 20+## (i.e. group 10 would be 30) and Text Los Angeles
G##.

2. Set up semi-monthly period parameters for your new pay scale area based on the
entries for pay scale type/are 01/11.

3. Create three new wage types from a copy of a wage type 1000:

Customer Wtype Wage Type Long Text Text

0##1 ## Hourly Rate ##HR
0##2 ## Hourly PS Group Bonus ##GB
0##3 ## Hourly Fixed Percent ##FP

4. Edit the characteristics of you three new wage types as follows. If an entry is not
specified, it should be blank:

Wage type 0##1 0##2 0##3

Amount Check Add to Total Check Add to Total Check Add to Total
Input Comb. +/- +/- -/-
Time leveling Blank Blank Blank
Number/Unit All Blank All Blank All Blank
Indirect Valuation TARIF/A TARIF/C SUMME/I
Rewritable Yes Yes Yes

5. Create a new pay scale structure for your new collective agreement groupings: Pay
scale type 01, pay scale area 20+##. Use pay scale type 01 pay scale area 11 as a
model and copy those entries to being. Be sure to add wage type 0##2 to the pay
scale structure reflecting TARIF C configuration with the following values.

Grpg PS Group Lv Wage Type Amount

1 H001 0##2 2.00
1 H002 0##2 3.00
1 H003 0##2 4.00

6. Map wage types 0##1 and 0##2 to be the base value for wage type 0##3 and include
wage type 0##1 in the ASAL calculation: Use the following values:

ã SAP AG 2013 WNA11 3 - 27

Mod. n Valuated No. Start Date End Date Base WT Percent
ANSAL ASAL 20+## 01/01/YYYY 12/31/9999 0##1 100
SUMME 0##3 1 01/01/YYYY 12/31/9999 0##1 10
SUMME 0##3 2 01/01/YYYY 12/31/9999 0##2 10
Note: Generally, all IT0008 wage types would be mapped to ASAL on this table, but
due to the line number restrictions, we are only adding in the first of our wage types.

7. Edit processing class 01 so that wage type 0##1 is added to valuation bases /001 and
/002, but wage types 0##2 and 0##3 are only added to /001. Do this from transaction
code SM30.

8. To hire a second employee, and test your configuration, go to PA40.

a. Hire employee 11102## (## = your group number) on 01/16/YYYY using the
personnel action type Hire and enter the following data:

Entry date 01/16/YYYY

Personnel area 3300
Employee group 1
Employee subgroup U1 (hourly worker)
Personnel Subarea 0001 Production
Payroll Area 4# (# = Payroll area assigned to Group)
Position Production Worker ##
For structure search, [Link] Training Group ->
Training National -> Training US -> Production
WNA11.
Name Any
Birth Date Any
SSN Any valid 9 digit number
Street Address Any
City Los Angeles
State CA
Zip Code 90210
Withholding Tax FED

ã SAP AG 2013 WNA11 3 - 28

 Withholding Status 2
Allowances Your choice
PS Type/Area 01 / 20+## (your new PS Area)
PS Group/Level H001/02
Wage types 0##1, 0##2, 0##3 (after entering all 3, press enter)
Go to Enrollment No
Payment Method Check

9. To test your configuration, run payroll for period 2 for your payroll area 4#. Exit the
period if the payroll provides the results you expected.

ã SAP AG 2013 WNA11 3 - 29

Unit 3: Wage Types

Exercise 2: Rule to Prorate Mentor Bonus for All Unpaid Absences and
Paid Personal Leave.

Complete this exercise for the class:

1. In your subschema Z##M, replace SAP rule UMOD with Z20M. This will be
used to set Modif A=50 for all employees in ESG for PCR 1.

2. Copy subschema UAL0 and rename it Z##A.

3. In Z##A replace rule XPPF with Z20F. This will be used to incorporate /803 into
the payroll process.

4. Enter your copy of subschema UAL0 (Z##A) in your copy of U000 (Z##U).

5. Assign the mentor bonus wage type (OMNB) to your employee on IT0014 as of
Feb 1, YYYY for $300.

6. Create a 2 day IT2001 record with absence type 0320 (personal leave) for both of
your employees during period 3/YYYY. Also create a 2 day IT2001 record for
absence type 0200 (Sick Leave) in period 3/YYYY.

7. Run payroll for period 3/YYYY and verify that while wage type 0MNB was
prorated because of the personal leave absence, it was not prorated for the sick
leave absence.

8. Exit Payroll.

Note: Please do not attempt the following steps for this exercise in class. These are
the procedure steps. During class, students will use rules set up by the instructor for
group number 20. The following steps are included as a user guide for future reference.

1. Copy Absence type 0200 to 03## and change the A/A type text to 03## and ##
Personal Leave.

2. Assign an absence valuation class 03 to absence type 03##:

3. Edit your copy of UMOD (Z##M) and verify that is has already been entered into
your copy of subschema UMO0. Change the entry for Modif A for ESG 1 to be:
Modif A=30+##.

ã SAP AG 2013 WNA11 3 - 30

4. Create an Absence Valuation rule which will count your new Absence type 03## as
paid, yet differentiate it from other kinds of paid absences. Use counting class 03.

5. Copy an existing valuation rule (AbsValGrpg 50, Valuation rule 20) as the model for
your new rule and change the counting class to 03. Use your new Modif A value for
the AbsValGrpg in you new rule.

6. Copy rule XPPF to Z##F and add wage type /803 as the factor to be used for the
mentor bonus. You will also need copies of rule XPP0 named Z##G and rule XPP1
named Z##H. You want paid absences with counting class 03 assigned as well as all
unpaid absences to be used to prorate the mentor bonus.

7. Create a copy of subschema UAL0 and enter your new copy of XPPF in it. Name the
new subschema Z##A.

8. Enter your copy of subschema UAL0 in your copy of U000.

9. Verify the processing class 10 value assigned to wage type 0MNB will use your new
rule for wage type /803.

10. Test your rule by assigning the mentor bonus wage type to your employee on infotype
0014 as of Feb 1, YYYY, and then create absence 03## for your employee during the
next payroll period.

11. Run payroll for period 3/YYYY and verify that while wage type 0MNB was prorated
because of the absence, yet, the regular hours for the absence were paid.

12. Exit Payroll.

ã SAP AG 2013 WNA11 3 - 31

Unit 3: Wage Types

Exercise 3: Copying/Modifying a Wage Type

A. Copy wage type 7020 401K Contribution to 70## Percent Deduction ##.
The wage type entries should start on January 01, YYYY.
B. Confirm that 70## is a deduction wage type with allowable entries via
percentage. The minimum number allowed should be 1% and the maximum
should be 10%. Modify the wage type attributes accordingly.

C. Confirm the values in the processing classes and cumulation classes. If

necessary change the specifications. In particular, consider that this is a
percentage deduction which must be considered for processing under
retroactive accounting. See the solutions for details.

D. If necessary, make the wage type permissible for infotype 0014 once per
period.

ã SAP AG 2013 WNA11 3 - 32

Unit 3: Wage Types

Solution 1: Creating New Pay scale Area with indirectly valuated wage
types.

1. To create a new pay scale area: IMG: Personnel Management -> Personnel
Administration -> Payroll Data -> Basic Pay -> Check Pay Scale Area.

Choose New Entries. Enter New Pay scale Area 20+## (i.e. group 10 would be 30)
and Text Los Angeles G##.

2. To set up semi-monthly period parameters for your new pay scale area: IMG:
Personnel Management -> Personnel Administration -> Payroll Data -> Basic
Pay -> Set up payroll period for collective agreement provision and then choose
Pay Scale > Period Parameter Assignment in the pop-up box.

a. Copy the entries for pay scale type/area 01/11 to your new pay scale area by
choosing the position button. Enter [Link] type 01, [Link] Area 11 then
continue (enter).
b. Select both entries for 01/11 and then Copy.
c. Change the pay scale area from 11 to 20+##, press Enter and then Save.

3. To create three new wage types from a copy of wage type 1000: IMG: Personnel
Management -> Personnel Administration -> Payroll Data -> Basic Pay -> Wage
Types-> Create wage type catalog. Leave the copy button selected and choose
continue (enter).

a. To clear all the wage types out of your view, click on the Select all button and
then choose the Delete row button. Note: All wage types will disappear from
your view, but are not actually deleted from anywhere.
b. Enter 1000 in the Original Wtype field and 0##1 in the Customer Wtype field.
c. Select the line and then choose the Copy wage type 1 button.
d. Note: Wage type 0##1 should default into the Wage type starts at field. Enter
3 in the Number of wage types field and 1 in the Increase each step field then
choose continue (enter).
e. Enter text for each new wage type:

Customer Wtype Wage Type Long Text Text

0##1 ## Hourly Rate ##HR
0##2 ## Hourly PS Group Bonus ##GB
0##3 ## Hourly Fixed Percent ##FP

f. Deselect the Test run box, and then choose Copy.

ã SAP AG 2013 WNA11 3 - 33

 g. Note: entries were not made on table T539J (Base Wage Type Valuation) and
T539A (Planned Remuneration Specifications, a.k.a.: Default Wage Types for
Basic Pay, IT0008). Take note of other tables where entries were made:
especially T512W and T511. Since all three of your new wage types are exact
copies of 1000, further edits will need to be made on these as well as other
tables to adjust the wage types for our course scenario.
h. To return to the IMG: Choose the Back button twice and then exit the wage
type maintenance pop up box.

4. To edit the characteristics of you three new wage types: IMG: Personnel
Management -> Personnel Administration -> Payroll Data -> Basic Pay -> Wage
Types-> Check Wage Type Catalog-> Check wage type characteristics.

a. Choose the position button, enter 0##1 in the Wage type field and the choose
Continue (enter).
b. Select all three of your wage types 0##1, 0##2 and 0##3 then choose Details.
c. Edit each wage type as follows: If an entry is not specified, make it blank.
Do not assign rounding or reduction to any wage type. Use the next entry
icon to move through each wage type to make changes and then save after
editing the third one.

Wage type 0##1 0##2 0##3

Amount Check Add to Total Check Add to Total Check Add to Total
Input Comb. +/- +/- -/-
Time leveling Blank Blank Blank
Number/Unit All Blank All Blank All Blank
Indirect Valuation TARIF/A TARIF/C SUMME/I
Rewritable Yes Yes Yes

5. To create a new pay scale structure for a collective agreement: IMG: Personnel
Management -> Personnel Administration -> Payroll Data -> Basic Pay ->
Revise Pay Scale Groups and Levels.

a. Enter Pay scale type 01, pay scale area 20+## and then continue (enter).
Choose New Entries. Note: In step b you will copy values from pay scale
type/area 01/11 for use in your new CAP.
b. To copy existing values from a similar pay scale type and area, open a second
session and go to transaction SM30, enter Table/View V_T510 and choose
Display. Enter pay scale type 01 pay scale area 11 and then enter.

ã SAP AG 2013 WNA11 3 - 34

 c. Press control + Y on your keyboard to activate a windows copy. Note: your
cursor should change to a + sign. To copy what is currently in your view
move the + sign to the upper left corner of the table into the Grpg field, click
and hold then drag the cursor to the end of the first line and then down the
entire view. Once this is highlighted, press control + C to copy the entries.
d. Return to the other session in the IMG view of V_T510 for your pay scale
type 01 and area 20+##. You should be in the new entries mode. Place your
cursor in the first Grpg field and press control + V to enter the copies you
made in step c and then Save.
e. Return to the other session and copy the next set of entries. Click once in the
blue area of the vertical scroll bar to page down to the rest of the entries for
pay scale type 01 pay scale level 11. Repeat the same procedure as above to
copy the rest of the entries to your new pay scale type/area 01/20+##. After
pasting your copies, choose Save.
f. To add wage type 0##2 to the pay scale structure, highlight each pay scale
group for ESG/CAP 1 (H001-H003) and only the level 1. Then choose Copy,
make the following entries and removing the level 1. After making all of
these entries, press Enter to confirm the copy and then choose Save:

Grpg PS Group Lv Wage Type Amount

1 H001 0##2 2.00
1 H002 0##2 3.00
1 H003 0##2 4.00

g. Return to the IMG.

6. To map wage types 0##1 and 0##2 to be the base value for wage type 0##3 and to
include wage type 0##1 in the ASAL calculation: IMG: Personnel Management ->
Personnel Administration -> Payroll Data -> Basic Pay -> Wage Types -> Define
valuation of base wage types.

a. Select New Entries, enter the all of the following, and then Save:

Mod. n Valuated No. Start Date End Date Base WT Percent

ANSAL ASAL 20+## 01/01/YYYY 12/31/9999 0##1 100
SUMME 0##3 1 01/01/YYYY 12/31/9999 0##1 10
SUMME 0##3 2 01/01/YYYY 12/31/9999 0##2 10
Note: Generally, all IT0008 wage types would be mapped to ASAL on this table, but
due to the line number restrictions, we are only adding in the first of our wage types.

7. To Edit processing class 01 so that wage type 0##1 is added to valuation bases /001
and /002, but wage types 0##2 and 0##3 are only added to /001: From the Easy
access menu enter SM30 in the command field.

ã SAP AG 2013 WNA11 3 - 35

 a. Enter V_512W_O in the Table/View field and then choose Maintain.
b. Press continue (enter) to get past any pop-up boxes.
c. Choose the position button, and enter wage type 0##1 in the wage type field
the press continue (enter).
d. Select all three of your wage types 0##1, 0##2 and 0##3 and then choose
Details.
e. Use the page forward button to move through each wage type to make the
following changes and then save after editing the third one.

Wage Type Processing Class 01 Value

0##1 3
0##2 1
0##3 1

8. To hire a second employee, and test your configuration, go to PA40.

a. Hire employee 11102## (## = your group number) on 01/16/YYYY using the
personnel action type Hire and enter the following data:

Entry date 01/16/YYYY

Personnel area 3300
Employee group 1
Employee subgroup U1 (hourly worker)
Personnel Subarea 0001 Production
Payroll Area 4# (# = Payroll area assigned to Group)
Position Production Worker ##
For structure search, [Link] Training Group ->
Training National -> Training US -> Production
WNA11.
Name Any
Birth Date Any
SSN Any valid 9 digit number
Street Address Any
City Los Angeles
State CA
Zip Code 90210
Withholding Tax FED

ã SAP AG 2013 WNA11 3 - 36

 Withholding Status 2
Allowances Your choice
PS Type/Area 01 / 20+## (your new PS Area)
PS Group/Level H001/02
Wage types 0##1, 0##2, 0##3 (after entering all 3, press enter)
Go to Enrollment No
Payment Method Check

9. To test your configuration, run payroll for period 2 for your payroll area 4#. Exit the
period if the payroll provides the results you expected.

a. Release payroll: SAP Menu: Human Resources > Payroll > Americas >
USA > Payroll > Release Payroll. Select Yes to Release payroll for payroll
area 4#, period 2, YYYY.
b. To run payroll: SAP Menu: Human Resources > Payroll > Americas >
USA > Payroll > Start Payroll. Click on Get Variant to choose your
variant created earlier and then execute.
c. Open the log to view results: Select your second employee, then choose
Find. Enter EXPRT in the find field and then choose find.
d. Open the folder EXPRT RU. Open the Input folder and then double-click on
the RT table. View contents to check if different amounts exist for /001 and
/002 wage types. Also check that wage types 0##1, 0##2 and 0##3 were
created properly. If everything is correct, exit payroll for period 2.
e. SAP Menu: Human Resources > Payroll > Americas > USA > Payroll >
Exit Payroll.

ã SAP AG 2013 WNA11 3 - 37

Unit 3: Wage Types

Solution 2: Rule to Prorate Mentor Bonus for All Unpaid Absences and
Paid Personal Leave.

Complete these exercise steps in class:

1. In your subschema Z##M, replace SAP rule UMOD with Z20M. This will be
used to set Modif A=50 for all employees in ESG for PCR 1 and Modif A=01 for
all employees in ESG for PCR 2. Transaction PE01:

a. Enter Z##M in the schema field and choose Change.

b. Use the find button at the top to locate rule UMOD.
c. Enter an R in front of the line for UMOD and then press enter to replicate
the line.
d. Deactivate the first line that calls UMOD by placing a * in the D column.
e. On the next line in Parameter 1, replace rule UMOD with Z20M and then
choose Save.

2. Copy subschema UAL0 and rename it Z##A. Transaction PE01:

a. Enter UAL0 in the schema field and choose Copy.

b. Enter Z##A in the To Schema field and choose Continue.

3. In Z##A replace rule XPPF with Z20F. This will be used to incorporate /803 into
the payroll process. Transaction PE01:

a. Enter Z##A in the schema field and choose Change.

b. Use the find button at the top to locate rule XPPF.
c. Enter an R in front of the line for XPPF and then press enter to replicate
the line.
d. Deactivate the first line that calls XPPF by placing a * in the D column.
e. On the next line in Parameter 1, replace rule XPPF with Z20F and then
choose Save.

4. Enter your copy of subschema UAL0 (Z##A) in your copy of U000 (Z##U).
Transaction PE01:

a. Enter Z##U in the schema field and choose Change.

b. Use the find button at the top to locate subschema UAL0.
c. Enter an R in front of the line and then press enter to replicate the line.
d. Deactivate the first line that calls UAL0 by placing a * in the D column.
e. On the next line, in Parameter 1, replace subschema UAL0 with your new
subschema Z##A, and then Save.

ã SAP AG 2013 WNA11 3 - 38

 5. Assign the mentor bonus wage type (OMNB) to both of your employees on
IT0014 as of Feb 1, YYYY for $300. From Easy Access: Transaction PA30.

a. Enter 11102## in the personnel no. field, 0014 in the Infotype field and
choose Create.
b. Enter 02/01/YYYY in the Start field, 0MNB in the wage type field, 300 in
the Amount field and choose Save.
c. Repeat for Employee 11101##

6. Create a 2 day IT2001 record with absence type 0320 (personal leave) for both of
your employees during period 3/YYYY. Also create a 2 day IT2001 record for
absence type 0200 (sick leave) in period 3/YYYY. From Easy Access:
Transaction PA30.

a. To create the first absence, enter 2001 in the Infotype field, 0320 in the
subtype field, the first Monday and Tuesday in February as the from and
to dates and then choose Create.
b. On the next screen verify the entries and choose Save.
c. To create the second absence, enter 2001 in the Infotype field, 0200 in the
subtype field, the first Wednesday and Thursday in February as the from
and to dates and then choose Create.
d. On the next screen verify the entries and choose Save.
e. Repeat these steps for your other employee.

7. Run payroll for period 3/YYYY and verify that wage type 0MNB was prorated
because of the personal leave absence but, it was not prorated for the sick leave
absence. (Note: only your hourly employee 11102## will prorate, if you look at
your salary employee 11101##, no proration should have taken place.)
a. Release payroll: SAP Menu: Human Resources > Payroll > Americas
> USA > Payroll > Release Payroll. Select Yes to Release payroll for
payroll area 4#, period 3, YYYY.
b. To run payroll: SAP Menu: Human Resources > Payroll > Americas >
USA > Payroll > Start Payroll. Click on Get Variant to choose your
variant created earlier and then execute.
c. Open the log to view results: Select your second employee, then choose
Find. Enter EXPRT in the find field and then choose find.
d. Open the folder EXPRT RU. Open the Input folder and then double-click
on the RT table. View contents to check if wage type 0MNB was
prorated. If everything is correct, exit payroll for period 3.
e. SAP Menu: Human Resources > Payroll > Americas > USA > Payroll
> Exit Payroll.

ã SAP AG 2013 WNA11 3 - 39

Note: Please do not attempt the following steps for this exercise in class. These are
the procedure steps. During class, students will use rules set up by the instructor for
group number 20. The following steps are included as a user guide for future reference.

1. To copy Absence type 0200 to 03##: IMG: Personnel Time Management ->
Time Data Recording and Administration -> Absences -> Absence Catalog ->
Define Absence Types.

a. Copy the entries for Absence type PS Grouping 10 and Absence type
0200 by choosing the position button. Enter PS Grouping 10, Att./abs.
type 0200 and then choose continue (enter).
b. Select the entry and choose Copy as.
c. Change the A/A type text to 03## and ## Personal Leave, the click on
enter and Save and return to the IMG.
d. Note: Since you made a copy, your new Absence type 03## will inherit
important characteristics from Absence type 0200. Some of the most
important are on table V_554S_O (entry screen and time constraint class),
V_554S_Q (counting rule and quota deduction) and V_554S_G
(assignment to an absence valuation class).

2. To assign an absence valuation class to absence type 03##: IMG: Payroll ->
Payroll: USA -> Absences -> Assign absences to valuation classes.

a. To position on the entry made from your copy, choose the position button,
enter PS Grouping 10, Att./abs. type 03## and then choose continue
(enter).
b. Enter 03 in the Val. R column and then Save.

3. To edit your copy of UMOD (Z##M) and enter it into your copy of subschema
UMO0: IMG: Payroll -> Payroll: USA -> Absences -> Determine grouping
for absence valuation Then double-click on Set modifiers for payroll
calculation in the pop-up box.

a. Note: UMOD will default in the Rule field. Replace it with Z##M and
then choose Change.
b. Position your cursor on the Modif A=01 entry for ESG 1 and wage type
**** and choose the change entry icon. Replace 01 with 30+## (i.e. group
10 will be 40). Then press enter and Save.
c. To quickly get to transaction PE01, use the Back icon twice to return to
the Choose activity pop-up box and double-click on Update schema
UT00. Note: you’ll do this is in order to reach PE01 where you will
switch from UT00 to your main schema Z##U in the next step.
d. Replace UT00 in the schema field with your Z##U and choose display.
Verify that your subschema Z##M and rule Z##M are included in your
copy of U000 (Z##U).

ã SAP AG 2013 WNA11 3 - 40

 e. Verify that you have deactivated the line COPY UMO0 and replaced it
with COPY Z##M.
f. Double click on your Z##M and verify that you have deactivated MOD
UMOD GEN and replaced it with MOD Z##M GEN.
g. Return to the IMG.

4. To create an Absence Valuation rule which will count your new Absence type
03## as paid, yet differentiate it from other kinds of paid absences: IMG:
Payroll -> Payroll: USA -> Absences -> Absence Valuation -> Evaluate
absences using 'as if' principle.

a. Choose New entries and enter AbsValGrpg 30+## and Valuation Rule 03.
Use validity dates 01/01/YYYY to 12/31/9999.
b. In the Form count. Classes section click on the insert row icon, and enter
CC for absences 03, select paid and enter 100 in the Percentage field.
c. Scroll down and in the Valuation using the “as if” principle section select
the box for Time WT selection and then Save. Return to the IMG.
d. Note: This rule will still generate the regular wage types for normal hours
for the employee for this kind of absence, but because the counting class
differs from other paid absences you will be able to include it in your copy
of rule XPPF to prorate the Mentor Bonus.

5. To copy an existing valuation rule to be used for other kinds of paid absences:
IMG: Payroll -> Payroll: USA -> Absences -> Absence Valuation ->
Evaluate absences using 'as if' principle.

a. Select the position button, enter AbsValGrpg 50, Valuation rule 20 and
choose Continue (enter).
b. Select this entry and choose Copy as.
c. Change the AbsValGrp to 30+## (your new value for Modif A), press
enter and then Save.

6. To copy rules XPPF, XPP0 and XPP1: open another session and on the SAP Easy
Access Menu screen, enter PE02 in the command field or choose it from your
favorites.
a. Enter XPPF in the rule field and then choose Copy. Enter Z##F it he To
rule field and then choose Continue (enter). Do the same for XPP0 and
name it Z##G then XPP1 and name it Z##H.
b. After you have made the three copies, enter Z##F in the rule field, choose
the change icon, and on the maintain calculation rule screen, place your
cursor on the single * at the top of the rule, choose Create and then sub-
level in the pop-up box.
c. Enter /803 in the open box. Then press Enter twice.

ã SAP AG 2013 WNA11 3 - 41

 d. To copy the lines of operations for wage type /801, click on the + sign
next to it, place you cursor on the first line of operations PPPAR R and
then choose Copy. Then place your cursor on your new entry for wage
type /803 and choose Paste.
e. To call your new rule Z##G from Z##F, open the folder for /803 by
clicking on Expand the subtree, then place your cursor on the operation
GCY XPP0 and choose Change. Insert your rule Z##G in place of XPP0
press Enter to close the line and then Save.
f. To edit your new rule Z##G, double-click on the operation GCY Z##G
you just entered and you will jump to the rule. NOTE: You will need to
click on Change <> Display to return to edit mode after the jump.
g. Close up the entire rule by clicking on the + sign next to the asterisk for
ESG/PCR and then place your cursor on the asterisk and choose Create
and Sub-level.
h. Enter /803 in the open box, press Enter twice then Save.
i. To copy the lines of operations for /801, Expand the subtree, place your
cursor on the first line of operations PPPAR U and choose Copy. Then
place your cursor on your new entry for wage type /803 and choose Paste.
j. To call your new rule Z##H from Z##G, open the folder for /803 by
clicking on Expand the subtree, then place your cursor on the operation
GCY XPP1 and choose Change. Insert your rule Z##H in place of rule
XPP1 and press Enter to close the line and then Save. Do this again until
all four calls of XPP1 have been replaced in your rule and also replace the
one call of XPPP and Save.
k. To edit rule Z##H and include a factor on counting class 03, double-click
on any line with the operation GCY Z##H you just entered and you will
jump to the rule. NOTE: You will need to click on Change <> Display to
return to edit mode after the jump.
l. Click on the wage type /801, choose Change and replace it with wage type
/803 then press Enter and Save.
m. To include a line or operations for factoring based on paid absences
assigned to counting class 03, place your cursor on the line of operations
RTE-TSAU** and choose Create. This should open a box immediately
under it where you should enter RTE-TSAP03, then press Enter and Save.
n. The following screen shots demonstrate how your three new rules should
look. These rules were created for group 20.

ã SAP AG 2013 WNA11 3 - 42

Screen Shot of Rule Z##F

ã SAP AG 2013 WNA11 3 - 43

Screen Shot for Rule Z##G

ã SAP AG 2013 WNA11 3 - 44

Screen Shot for Rule Z##H

ã SAP AG 2013 WNA11 3 - 45

 7. To make a copy of subschema UAL0 (where you will enter your new copy of
XPPF) in your schema: Return to the SAP Easy Access Menu, enter PE01 in the
command field or choose it from your favorites.

a. Enter UAL0 in the Schema field, choose Copy, enter Z##A in the To
schema field and then choose Continue (enter).
b. Your copy should now appear in the Schema field. Choose the Change
icon.
c. Enter an R in front of line 50 and then press enter to replicate the line.
d. Deactivate the first line that calls XPPF by placing a * in the D column.
e. On the other line in Parameter 1, replace rule XPPF with Z##F and then
Save.
f. Use the back icon to return to main PE01 screen and place you new
subschema in your schema Z##U.

8. To enter your copy of subschema UAL0 in your copy of U000: Transaction

PE01:

a. Enter Z##U in the schema field and choose Change.

b. Use the find button at the top to locate subschema UAL0.
c. Enter an R in front of the line and then press enter to replicate the line.
d. Deactivate the first line that calls UAL0 by placing a * in the D column.
e. On the next line in Parameter 1, replace subschema UAL0 with Z##A and
then Save.

9. To verify the processing class 10 value assigned to wage type 0MNB will use
your new rule for wage type /803, return to the SAP Easy Access Menu, enter
SM30 in the command field or choose it from your favorites.

a. Enter V_512W_O in the Table/View filed and then display. Verify you
want to work in country grouping 10 by choosing continue/enter.
b. Select the position button at the bottom, enter wage type 0MNB and
choose continue/enter.
c. Select wage type 0MNB and then choose Details. Confirm that
processing class 10 is set to a 3. This determines that the factor created for
wage type /803 in your copy of rule XPPF (Z##F) will be applied to this
wage type at rule XVAL.

10. To test your rule, assign the mentor bonus wage type to your employee on
infotype 0014 as of Feb 1, YYYY, and then create absence 03## for your
employee during the next payroll period. From Easy Access: Transaction PA30.

a. Enter 11102## in the personnel no. field, 0014 in the Infotype field and
choose Create.

ã SAP AG 2013 WNA11 3 - 46

 b. Enter 02/01/YYYY in the Start field, 0MNB in the wage type field, 300 in
the Amount field and Save.
c. To create an absence, enter 2001 in the Infotype field, 03## in the subtype
field, the first Monday and Tuesday in February as the from and to dates
and then choose Create.
d. On the next screen verify the entries and choose Save.

11. Run payroll for period 3/YYYY and verify that while wage type 0MNB was
prorated because of the absence, the regular hours for the absence were paid.

a. Release payroll: SAP Menu: Human Resources > Payroll > Americas
> USA > Payroll > Release Payroll. Select Yes to Release payroll for
payroll area 4#, period 3, YYYY.
b. To run payroll: SAP Menu: Human Resources > Payroll > Americas >
USA > Payroll > Start Payroll. Click on Get Variant to choose your
variant created earlier and then execute.
c. Open the log to view results: Select your second employee, then choose
Find. Enter EXPRT in the find field and then choose find.
d. Open the folder EXPRT RU. Open the Input folder and then double-click
on the RT table. View contents to check if wage type 0MNB was
prorated. If everything is correct, exit payroll for period 3.
e. SAP Menu: Human Resources > Payroll > Americas > USA > Payroll
> Exit Payroll.

ã SAP AG 2013 WNA11 3 - 47

Unit 3: Wage Types

Solution 3: Copying/Modifying a Wage Type

A. To copy wage type 7020, go to:

IMG: Payroll Accounting à Payroll: USA à Basic Settings à
Environment for Maintaining Wage Types à Create Wage Type Catalog
(Or use transaction OH11 from the Easy Access menu))

In the pop-up box, select Copy and then Enter.

Enter the wage type to be copied, 7020, in the OWType field and the wage
type you want to create, 70##, in the CWType field. At the bottom of the
screen, select the Entries from Validity date radio button and enter the date
01/01/YYYY. Select the line that includes the wage types, remove the test
run check and select Copy. Review the entries in the log.
To confirm that wage type 70## is a deduction wage type, you need to check
the wage type attributes (table V_T511). Access the table via the IMG (Or
SM30):
IMG: Payroll Accounting à Payroll: USA à Basic Settings à
Environment for Maintaining Wage Types à Check Wage Type
Attributes.

Confirm that the Deduction WT check box is selected. Verify the input
combination: Amount -, Number +. Verify Percent as the Time
unit/meas. and 1.00 as the minimum number/10.00 as the maximum
number.

B. To change the values in the processing and cumulation classes, you will
want to access table V_512W_O Wage Type Valuation directly. Only by
accessing the larger view of the table will you have access to all of the
processing classes at one time.

Transaction Code: SM30

Table/View: V_512W_O

ã SAP AG 2013 WNA11 3 - 48

 Select Maintain and enter country grouping 10. If prompted, select edit
everything in the next pop-up box.

Use the position button to find your wage type and go to the Detail screen.
You can use the drop down box or F1 help to give you an understanding of
what values we are setting for the processing classes. You should have the
following processing class values: Note: if a PC is not specifically
mentioned on this table, it should be blank.

Processing class Specification

1 Blank
3 0 Pass on unchanged
4 6 Transfer without modification
5 0 Store in RT without split indicator
6 0 Wage type will not be transferred
10 0 No reduction
15 Blank
17 Blank
18 Blank
20 1 Pass on unchanged
22 Blank
24 1 always effect transfer in full
25 Blank
30 T Cumulation according to T54C3
31 0 WT Does not lead to debits . . .
32 No longer relevant
35 Blank
41 3 RT storage and cumulation
45 - 72 Blank
73 1 - Reverse sign for TP Remit
74-77 Blank
78 1 - Deduction to be Remitted
79 - 99 Blank

For the cumulation classes, confirm that only cumulation class 10 is

selected.

ã SAP AG 2013 WNA11 3 - 49

 D. To make the wage type permissible on IT0014 (V_T512Z) once per period
go to: IMG: Personnel Management > Personnel Administration > Payroll
Data > Recurring Payments and Deductions > Wage Types > Checking
Wage Type Catalog > Check Entry Permissibility per Infotype. Confirm
that wage type 70## is on the table with the Once radio button selected.

ã SAP AG 2013 WNA11 3 - 50

 Customizing Payroll Processing

Contents:
l Important Operations of Payroll
l Link between Operations and Functions
l Review Internal Table Processing
l Building Customized Rules
l Customer Scenarios

ã SAP AG 2013 WNA11

 Customizing: Objectives
By the end of this unit, you will be able to:
l Identify and work with some of the most important operations in
payroll
l Create personnel calculation rules (PCRs)
l Create a customized processing class
l Design a rule to use your processing class

ã SAP AG 2013 WNA11

 Categories of Operations
ERROR GCY
ADDAR ADDNA NEXTR
ADDNT Update tables Technical Control
ADDWT MODIF PAYTP PCY
PRINT SCOND
WGTYP
DIVID
OUTWP
VAKEY NUM
Decision AMT Calculation
RTE MULTI
OUTZL
VWTCL ROUND

ELIMI FILLF
VALEN Field Control ZERO=
VAOFF RESET SETIN
ã SAP AG 2013 WNA11
 Decision Operations

Provide work center basic pay data

OUTWPPAYSB
Perform special processing if the
** .....
employee belongs to payroll area U1
U1 .....

OUTWPCOSTD
Does the employee have a cost center
* .....
on the Cost Distribution infotype?
X .....

Which wage type is being processed

WGTYP?
Perform special processing for wage
**** . . . . .
type 9000
9000 . . . . .

ã SAP AG 2013 WNA11

 Decision Operations: Processing Class

ã SAP AG 2013 WNA11

 Limiters for Decisions

VALEN Limit variable key length

VAOFF Access value in variable
8 spaces for
key
variable key

ã SAP AG 2013 WNA11

 Operations for Technical Control
n GCY_RULE_
u Get CYcle (Continue processing in new PCR . . .)
u Works with rule type Z

u Continue processing in specified rule, do not return to original rule

n PCY_RULE_
u Perform CYcle (Continue processing in new PCR. . .)
u Works with rule type P
u Perform processing in named rule, return to original rule to complete
processing

n PAYTP
u Internal rule jump
u Move to an alternate employee subgroup grouping for PCR

u Define a customer-specific grouping

ã SAP AG 2013 WNA11

 Customizing Scenario: Accuracy of Posting Data

Issue
n Your company does not always assign new employees to positions
n Some positions have missing or incorrect cost centers
n Payroll costs cannot be accurately posted without correct cost
centers
n Master cost centers must begin with 3

Solution
Write a personnel calculation rule that –
Confirms that all employees in company code 3000 either have a
Cost Distribution infotype or have a master cost center that begins
with 3.

ã SAP AG 2013 WNA11

 Calculation Operations: Setting Values

Operation RTE NUM AMT

Operators + - * / = S

Operands
Fixed Value Table Entry Wage Type
RTE=2.00 NUM=__ AMT=__
K Constants T511K C CRT
T Part Month Parameter M MV
Part Month PARTT L LRT
B ATAB (use TABLE) R RT

ã SAP AG 2013 WNA11

 Calculation Operations: Setting Values

Modify or set the Amount field

AMT O Y ZZZZZ

operation operator origin operand

indicator

ã SAP AG 2013 WNA11

 Payroll Operations: Update Results in Internal
Tables

Operation Table Updated

ADDAR ARRRS: Arrears Table

ADDNA Various tables

Number and amount cumulate
ADDNT DDNTK: Non-effected Deductions

ADDWT Various tables

Rate, number and amount cumulate
MODIF MODIF: Payroll Modifiers

ã SAP AG 2013 WNA11

 Payroll Operations: Update Tables

ADDWT Y ZZZZ

operation table wage type

indicator

Blank OT: Output Table

E RT: Results Table
I IT: Input Table
L LRT: Last Results Table
Z Time Wage Type Table

ã SAP AG 2013 WNA11

 Payroll Operations: ADDNA and ADDWT

ADDWT ADDNA

Cumulate all values Cumulate NUM & AMT

Input Table
WT RTE NUM AMT
9000 15 10 150
Rule 9999 10 5 50 Rule
ADDWT 9999 ADDNA 9999

Output Table Output Table

WT RTE NUM AMT WT RTE NUM AMT
9999 25 15 200 9999 10 15 200

ã SAP AG 2013 WNA11

 Customizing Scenario: Percentage Deduction
Issue
n Your company allows a percentage-based deduction with a set
limit of 1-10% of the employee’s gross pay per pay period.
n The deduction is entered as a recurring value.

Solution
Write a personnel calculation rule that –
n Valuates a deduction as a percentage of the employee’s total gross pay
for the payroll period.
n Works with a percentage that is specified on IT0014.

ã SAP AG 2013 WNA11

 Customizing Scenario: Combining wage types (1)

You want to test a custom rule (ZEL1) that would combine all /101 “Total
Gross” wage types distributed across splits into one total and store it in
wage type /191.
You also want to use a second rule to test the consequences of not
considering splits when combining wage types (ZEL2).

These rules should be placed in your copy of subschema UAL0 (Z##A)

after rule X023 when /101 is fully formed. Test one rule at a time in a
period where you have any kind of splits for your employee.

ã SAP AG 2013 WNA11

 Customizing Scenario: Combining wage types (2)

Insert both rules into your schema,

but keep one deactivated while you
test the other.
Both rules will only process wage
type /101 from the IT.

1. Record how /101 and /191 appear

on the IT table at the output of
each rule and note the differences.
2. Why do you have more than one
/191 after rule ZEL2?
3. Could an absence create a split
and keep wage types from being
combined?
4. When you are finished, deactivate
both rules in your subschema
Z##A.

ã SAP AG 2013 WNA11

 Structure of the Input Table

Structure name PC207

Short text Payroll Results: Results Table
Last changed SAP 11/11/1998 Original language DE German
Status Active Saved Development class PCAL

Field name Type name Dtyp Len Short text Dec Table Field Value tab IT Column
ABART ABRAR CHAR 1 ESG for PCR 0 T546A A/PCR
LGART LGART CHAR 4 Wage type 0 T512W Wage Type
APZNR APZNR RAW 1 PC205 assignment 0 AP/WC
CNTR1 CNTRN RAW 1 National assignment indicator 0 C1
CNTR2 CNTRN RAW 1 National assignment indicator 0 C2
CNTR3 CNTRN RAW 1 National assignment indicator 0 C3
ALZNR ALZNR RAW 1 Assignment for alternative pay 0 AB/Alt Pay
C1ZNR C1ZNO RAW 2 Pointer to cost accounting 0 KoRe/CA
BTZNR BTZNO RAW 1 Transfer assignment 0 BT
ABZNR ABZNO RAW 1 Absence assignment 0 Aw/Abs
V0TYP V0TYP CHAR 1 Variable assignment type 0 vT/Var
V0ZNR V0ZNR RAW 1 Variable assignment number 0 vn/Assign
ZEINH PT_ZEINH CHAR 3 Unit of time/measurement 0 T538A One/Unit
BETPE BETPE CURR 15 PA: Amount per Unit 2 T500C WAERS Amount/One/Rate
ANZHL PRANZ DEC 15 HR payroll: Number 2 Number
BETRG MAXBT CURR 15 HR Payroll: Amount 2 T500C WAERS Amount
RTE_CURR WAERS CUKY 5 Currency key 0 TCURC
AMT_CURR WAERS CUKY 5 Currency key 0 TCURC

ã SAP AG 2013 WNA11

 Split Indicators

Table Split Structure Text

Indicator
WPBP APZNR (PC205) Work center/basic pay
BT BTZNR (PC209) Bank transactions
ABC APZNR (PC206) Cumulate absence
classes
C1 C1ZNR (PC25X) Cost distribution from
various infotypes
V0 V0TYP (PC20C) Variable assignment
V0ZNR
ALP ALZNR (PC20E) Alternative payment
TAX CNTR1 (PC22T) Tax
CNTR2
CNTR3
TAXPR APZNR (PC22X) Authorities tax
prorates

ã SAP AG 2013 WNA11

 Payroll Operations: Split Indicators
n ELIMI AAA
u Eliminate split indicators
u Specify up to three indicators

n RESET AAA
u Reset indicators which were removed via ELIMI
u Specify up to three indicators

n WPBPC_nnnn
u Add WPBP indicator to a wage type that did not have one
u Distribute wage type across period splits

ã SAP AG 2013 WNA11

 Standard Rules to Import Data

76 à Include in special
payment run?
47 à Check for special
processing
10 à Factoring?

ã SAP AG 2013 WNA11

 Operations and Functions
Some operations can only be used when preceded by or used
in conjunction with specific functions

Operation MODIF Operation NUM=F

n Set Payroll Modifiers n Set value equal to distance
from date
n Can only be used with function
MOD n Can be used to compare
current date to fixed date
n Also valid for RTE or AMT
n Must be preceded by function
DATES

ã SAP AG 2013 WNA11

 Working With Dates

NUM=Faaesb
F Work with dates
aa Type of date
e Unit for calculation
s Calculate to which date
b Alternative date

ã SAP AG 2013 WNA11

 Customizing Scenario: Sick Leave Compensation
Issue
n For hourly employees, sick leave compensation varies based on length of
service.
n Hire date is stored on the Date Specification infotype (0041).
n The valuation percentage may be updated on a semi-annual basis.

Solution
Write a personnel calculation rule that –
n Modifies the rate of pay for sick leave for hourly employees using the
following percentages:
Length of Service Percent of Normal Pay
Less than 13 weeks 0%
Up to 1 year 60%
Up to 3 years 75%
Up to 5 years 90%
More than 5 years 100%

ã SAP AG 2013 WNA11

 Defining a Customer Processing Class

1. Define the processing class

2. Create specifications for the processing class
3. Create a calculation rule which uses operation VWTCL to
call the processing class and has variable key responses
for each valid specification
4. Add the appropriate operations for each processing class
specification to the rule
5. Insert the rule in the schema, where appropriate, using the
processing class code (P##) in Parameter 3 of the schema
statement

ã SAP AG 2013 WNA11

 Defining a Customer Cumulation Class

1. Copy a /1_ _ cumulation wage type to a wage type within

the customer range for cumulation, /190-/196
2. Assign wage types to the cumulation class that is now
active on V_512W_D

ã SAP AG 2013 WNA11

 Customizing Scenario: Incentive Wage Payments
Issue
n Your company provides an incentive wage (bonus payment) to hourly
employees but does not use the incentive wages portion of the R/3 system.
n The earned units for incentive wage are awarded on the Employee
Remuneration Information infotype once per pay period.
n The value (rate) of the incentive wage (unit) is calculated as 200% of the
Basic Pay value + 100% of the value of Overtime Worked divided by Total
Hours Worked.

Solution
Write a personnel calculation rule that –
n Valuates the incentive wage units according to the formula above.
n Recommendation: use a custom processing class and/or a custom
cumulation class.

ã SAP AG 2013 WNA11

 Customizing Scenario: Incentive Wage Payments
Issue
n Your company decides to extend the incentive wage program (bonus
payment) to salaried employees also. They still do not use the incentive
wages portion of the R/3 system.
n The earned units for incentive wage are awarded on the Employee
Remuneration Information infotype once per pay period.
n The value (rate) of the incentive wage (unit) is calculated as 200% of the
Basic Pay value divided by Total Hours Worked.

Solution
Write a personnel calculation rule that –
n Valuates the incentive wage units according to the formula above.
n Recommendation: Consider the order of processing for finalization of
gross payroll.

ã SAP AG 2013 WNA11

 Calculation of Total Gross Pay

xBD0 Import Basic Pay Data

xT00 Time Wage Type Processing

xAP0 Import Recurring and Additional

Payments

xAL0 Proration and Gross Cumulation

/101
ã SAP AG 2013 WNA11
 Customizing Scenario: Limit on Arrears
Issue
n Because of the cyclical nature of your business, employees often have
deductions that go into arrears. These values can become quite
significant.
n Your company wants to recover these amounts. However, the company
has decided to never take more than $250 per pay period to recover
amounts in arrears.
n This policy applies to all employees.

Solution
Write a personnel calculation rule that –
n Evaluates the amounts in arrears for each employee and limits the amount
to be processed in the current pay period to $250.
n Any remaining amounts in arrears should be returned to the arrears table
for processing in the next pay period.

ã SAP AG 2013 WNA11

 Option: Limit Arrears Recovery/New Wage Type
n While not required, an entry in table V_T51P1 can be used to
rename the arrears wage type. Use link 20 to do so.
n With this entry, wage type 8820 will be renamed 8888 before being
stored on the ARRRS table at function PREND, in subschema
UDNT, during the second run of deduction processing.

ã SAP AG 2013 WNA11

 Function PRART and Rule U013

This is a copy of SAP rule U013 (which is called

with function PRART in UDD0). In this version
of the rule during a regular run, a wage type
whose processing class 76 value is anything
other than a 1 or 2 will jump to rule Z20L.

This new rule Z##L could be used to perform

custom arrears processing. In our scenario we
want to limit the amount to be recovered to $250
and move the remaining balance back to arrears
for future processing.

In the standard U013, operation ADDWT is used

where Z20L is now called to simply move all
arrears wage types to the IT table. The system
would then attempt to recover the entire amount.

ã SAP AG 2013 WNA11

 Functions and Rules
n ACTIO Perform Rule n PDT Process Differences table
n MOD Set Modifiers n PIT Process Input Table
n P0009 Import Bank Details n PLRT Process Last Results Table
n P0014 Import Recurring n PORT Transfer of Data from
Payments/Deductions Previous Period
n P0015 Import Additional Payments n PRART Process Old Arrears Table
n P0221 Import Payroll Results n PRT Process Results Table
Adjustments n PTCRT Process Tax Cumulated
n P0267 Import Additional Payments Results Table
Off Cycle n PZL Process Time Wage Types
n P2010 Import Employee Table
remuneration Information
n PALP Process Alternative Payment
Table

ã SAP AG 2013 WNA11

 Functions IF and ELSE
n The functions in the personnel calculation schema located between the
functions IF and ELSE (or ENDIF) are only executed if a condition is met.
n This condition can be specified using a symbolic name or personnel
calculation rule. The functions IF, ELSE, and ENDIF form a function block.
n These blocks could include branching to different parts of a schema based
on dates. This can be accomplished more than one way and multiple
branches may occur in the same schema.

The following slides will depict possible options to use IF with

dates:
1. Hard Code a year in parameter 2 (General Branch)
2. Use a PCR: Best Practice - More options for different period
parameters/payroll areas.

ã SAP AG 2013 WNA11

 Using a hard coded date with function IF

The system documentation for

function IF describes how to use a
hard coded calendar year to branch.

ã SAP AG 2013 WNA11

 Customizing Scenario: Using IF/ELSE with a PCR
When a rule is called by function IF, operation SCOND is used to
determine if the condition queried by a PCR is True or False. When
the conditions specified are true than the IF path is followed. If
they are determined to be false, then the ELSE path is taken.
Since schemas and rules do not have validity dates, a PCR can be
used to include date specific changes in your schema while
maintaining history during retro calculations.

Write a PCR which, when called by function IF, will branch to the original
SAP subschema UMO0 and not your Z##M beginning the first day of the
next payroll period.
This will then branch to SAP rule UMOD and not your copy Z##M to
determine Modifiers for table access.
Either use date type RB on IT0041 to calculate the distance to the end of
the next payroll period OR use NUM=CURYY and NUM=CURPP.

ã SAP AG 2013 WNA11

 Customizing: Unit Summary
n Payroll operations perform the detailed processing of data
n Customized personnel calculation rules can be created to perform
processing beyond the delivered standards
n Customer-defined processing classes can be used to make
decisions within rules to process wage types in different ways
n Customer-defined cumulation classes may be used to hold
information on totals for use during payroll processing
n When creating a custom personnel calculation rule you must take
into consideration:
u Order of processing
u Cumulation and storage of wage types
u System limitations for length of keys
u Split indicators
u Variants for access of rules

ã SAP AG 2013 WNA11

 Exercises

Unit 4: Customizing
Rule 1: Check for Cost Center

· Building new rules

A customer has an on-going issue with cost centers not being entered for
their employees when they are hired. For employees in company code
3000, they need to determine if a cost center has either been on the Cost
Distribution infotype (IT0027) or assigned on the Organizational
Assignment infotype (IT0001).
All cost centers entered on IT0027 are valid. However, if no IT0027
exists, the rule must confirm that a valid master cost center exists on the
IT0001. For company code 3000, valid master cost centers must begin
with the number 3.

1 Check for valid cost center

A. Create personnel calculation rule Z##C. It should check for a valid cost center
for employees in Company Code 3000. All values are valid if they are on the
Cost Distribution infotype (0027). Master cost centers must start with a 3 to be
valid. Have the system produce an error if the cost center data is missing or
invalid.

B. Insert your new rule into your schema, making sure you copy any subschema
that you want to place it into.

C. Run payroll for period 04, YYYY, using the display log option.

D. Create a Cost Distribution infotype for employee 11101## for wage and salary
that is valid from Feb 16, YYYY. Run payroll for period 04, YYYY using
search helps W. Confirm that this employee has successfully processed in
payroll.
E. Exit payroll when complete.

ã SAP America 2013 WNA11 4 - 39

 Unit 4: Customizing
Rule 2: Percentage Deduction from /101

· Building new rules

The customer has a requirement to take a deduction based on a percentage

of total gross. The employee may choose to take this deduction for 1 to
10%, inclusive, of their total gross for the pay period.

1 Percentage based deduction

A. Using wage type 70##, which you created in a previous exercise, enter a 10
percent deduction for your salaried employee (11101##) on infotype 0014.
Enter this deduction on 03/01/YYYY.
B. Build a new rule named Z##P to value the deduction 70## as a percentage of
total gross.
C. Insert your new rule into your schema. You will need to choose which
subschema in which you should insert the rule. Remember to copy the
subschema before inserting the rule and to insert your new subschema into your
own main schema (Z##U). Name your new subschema Z##D.
D. Run payroll for period 05, YYYY and verify that your percentage deduction is
taken at the appropriate percentage. Also confirm that the amount of the
deduction has reduced net pay and appears in technical wage type /110 Total
deductions.
E. Your employee receives a pay increase on Mar 08, YYYY. His/Her new pay
scale level is 03. Create this new Basic Pay record.
F. Re-run payroll for Period 05, YYYY and review the results. Has the deduction
been taken as a true 10% of Total Gross? If not, edit processing class 10 to
rectify this situation. Make any corrections necessary to ensure that the
deduction is processed properly for the split pay period and re-run payroll to
confirm that your changes are correct.
G. When finished exit period 05.

ã SAP America 2013 WNA11 4 - 40

 Unit 4: Customizing
Rule 3: Prorate Absence Payment Based on Length of
Service
· Building new rules

A company has a requirement to modify the amount paid for sick leave
for hourly employees based on an employee’s length of service. The
company only wants to use one wage type for sick leave for hourly
employees, with the variable payment amount set during the processing
of payroll. The wage type should be valued at the following rates of the
employee’s regular hourly amount (as defined in /001):
Length of Service Rate
Less than 13 weeks 0%
13 weeks to 1 year 60%
1 year to 3 years 75%
3 years to 5 years 90%
more than 5 years 100%
The customer wants to reserve the right to change the percentage amounts
on an annual basis without having to access the personnel calculation rule
to make this change.

1. Sick leave by Length of Service

1-1. Change the infotype 0041 record for your hourly employee 11102##.
Enter or change the date type “01” with the date of 01/01/ZZZZ (3 years in
the past). Create an Absence record for your employee for a few days
between March 16-31, YYYY using absence type 0200 Illness.
1-2. Note: You will continue to use Z20M in place of UMOD to access
Absence Valuation Rules. This will set Modif A to 50 for employees in
ESG for PCR 1 and to 01 for employees in ESG for PCR 2 and 3. These
rules will select wage type 9002 Illness for absence type 0200 Illness. To
review this rule you can access table V_T554C via SM30.
1-3. Create personnel calculation rules named Z##S to modify the value of the
illness wage type 9002 to reflect the company’s length of service
requirements. Enter the rule in your schema.

Hints: Use function DATES, then create rule Z##S to determine the employee’s
length of service. Based on the length of service, modify the value in both the

ã SAP America 2013 WNA11 4 - 41

 rate and amount fields for the wage type. Consider wage type valuation and the
storage of time wage types when considering where to place the rule in the
schema.

2. Run payroll for period 06, YYYY for your payroll area. Was the correct Illness
amount calculated?

ã SAP America 2013 WNA11 4 - 42

 Unit 4: Customizing
Rules 4A and 4B: Incentive Wage Payment for Hourly
Employees
· Building new rules

Scenario: Your company offers an incentive wage to the hourly

employees. The number of units for the incentive wage is entered on
infotype 2010 Employee Remuneration Information. The value of each
unit of the bonus is derived using the following formula:
200% of Basic Pay value* + 100% of Paid Overtime amount divided by
total hours**

Shift differentials, location pay, pay for absences and bonuses are not
included in this calculation.
*Basic Pay value for hourly employees is the value of paid Regular
Hours for the period.
** For hourly employees, total hours worked is the total regular hour and
overtime hours worked, not including any absence hours.
Suggestion: Work with a customer-defined processing class and/or
cumulation class.

1. Calculating the value of the Incentive Wage

A. Edit your subschema schema Z##T to and replace subschema TC00 with
Z20C in two places. Each group will use the same subschema for day
processing with rule TMOD replaced by Z20T. All hourly ees (in ESG for
PCR 1) will be assigned to time wage type selection rule group 11.
Review the Time Wage Type Selection table to determine which time
wage types can be selected for your hourly employee for regular and
overtime.
B. Enter overtime on the Overtime infotype (2005) for several days between
April 1-15 YYYY, for your hourly EE 11102##.
C. Copy wage type 7120 Bonus to 71## Incentive Wage ## (where ## =
group number). Modify the wage type for entry as incentive wage units
on Employee Remuneration Information (IT2010). Ensure that it is
permissible to hourly employees. Confirm/Reset the cumulation and
processing classes, as necessary.

ã SAP America 2013 WNA11 4 - 43

 D. Assign 10 incentive wage units to your hourly employee 11102## on April
15, YYYY, on the Employee Remuneration Information infotype.
E. Create a rule or rules to calculate the incentive wage payment. Use the
following name ranges for any rules you create for this exercise: Z##I,
Z##J. Insert your new rule(s) into your schema. [Remember to copy any
subschemas to your own subschemas using Z and your group number as
the first three digits. If you need to create any additional wage types, use
the name range 72##.]
F. Run payroll for period 07, YYYY, to test your rule(s). Confirm that your
employee received the correct payment for the incentive wage.

ã SAP America 2013 WNA11 4 - 44

 Unit 4: Customizing
Optional: Rules 5A and 5B: Incentive Wage Payment for
Salaried Employees
· Building new rules
· Due to time constraints your instructor may simply demo this
variation on the last exercise.

Scenario: Your company decides to extend the incentive wage program

to the salaried employees. The number of units for the incentive wage is
entered on infotype 2010 Employee Remuneration Information. As
before, the value of each unit of the bonus is derived using the following
formula:
200% of Basic Pay value* divided by total hours**

There have been no changes to the details of the program for hourly
employees.
*Basic Pay value for salaried employees is the salary amount from Basic
Pay.
** For salaried employees, total hours worked is work hours per period as
defined on the Basic Pay infotype.
Suggestion: Work with a customer-defined processing class and/or
cumulation class.

1. Calculating the value of the Incentive Wage

A. Confirm that the 71## Incentive Wage ## wage type is available to your
salaried employees. Confirm/Reset the processing classes, as necessary.
B. Assign 5 incentive wage units to your salaried employee 11101## on April
30, YYYY, on the Employee Remuneration Information infotype.
C. Create a rule or rules to calculate the incentive wage payment. Use the
following name ranges for any rules you create for this exercise: Z##X,
Z##Y. Insert your new rule(s) into your schema. [Remember to copy any
subschemas to your own subschemas using Z and your group number as
the first three digits. If you need to create any additional wage types, use
the name range 72##.]
D. Run payroll for period 08, YYYY, to test your rule(s). Confirm that your
employee received the correct payment for the incentive wage.

ã SAP America 2013 WNA11 4 - 45

 Unit: Customizing
Rules 6A and 6B Limit on Arrears

· Building new rules

Because of the cyclical nature of your business, employees often have

deductions that go into arrears. The company has decided to limit the
amount that can be taken for deductions in arrears to $250.00 per pay
period for a series of, but not all, voluntary deductions. The company
wants to be able to distinguish the current amount taken for the
deductions from the limited arrearage amount. They would like you to
demonstrate this process for one wage type to prove that it is possible to
handle this request.

1. Limit on Arrears
A. Make a copy of wage type 8820 (originally copied from MD50, see
V_T52DZ) and name it 88##.
B. Confirm that wage type 88## will convert to wage type 8888 when it goes
into arrears.
C. To place a large amount in the ARRRS table and test your rule, create a
$2500 deduction for your salaried employee 11102## on the Additional
Payment infotype (0015) using wage type 88## which is valid during the
next payroll period.
D. Run payroll for period 09, YYYY. Review the amount of the deduction
that has gone into arrears and confirm that the amount has been transferred
to wage type 8888.
E. Write a rule that sets a limit of $250 for wage type 8888 and process the
next payroll period to test it. Any remaining amount must be carried
forward on the arrears table for processing in the next period.
You may wish to start by copying U013 to new rule Z##A (If you use this
as the start and decide to jump to another rule, use Z##L as the name of the
second rule).
F. Run payroll for period 10, YYYY. Confirm that the deduction recovered from
arrears was limited to $250.00 and the rest is carried forward on the ARRRS
table.
G. Be sure to review the processing of your rule in the log.

ã SAP America 2013 WNA11 4 - 46

 H. Optional: How would you adjust your rule to incorporate the following
considerations?
1. The limited amount is $200 for employees in payroll area 4#, but $250
for everyone else.
2. Historically at your company the limited amount has often changed.
You want to be proactive and plan for this contingency. How could you
set up your rule to most efficiently handle possible future changes to the
limit? For example: a decision is made to change the limited amount to
$150 on August 1 of the current year for employees in payroll area 4#
and $175 for everyone else.

ã SAP America 2013 WNA11 4 - 47

 Unit: Customizing
Rule 7 Using IF and ELSE with a PCR to process dates

· Access different places in the schema using dates

· Building new rules

Based on a particular date, your company desires to access the schema

differently than it has in the past. However, you want the schema to still
be accessed the way it was in the past during any retrocalculation runs.
You need to demonstrate how this can be accomplished using functions
IF/ELSE and a PCR with operation SCOND.

1. Create a PCR that (when called with function IF) will branch to different places
in the schema based on dates from IT0041.

A. Create rule Z##B. In it, include two decisions. First include a decision about
your payroll area. Second, include a date calculation using the difference
between date type RB on IT0041 and the end of the current period. You want
to use operation SCOND to determine when the difference between the dates
you are querying has occurred. Once the condition is found to be true, you
want to branch to SAP subschema UMO0 and no longer your copy of it
Z##M.

B. Place your new rule in your main Schema Z##U after subschema XLR0. Be
sure to include the appropriate functions IF, ELSE and ENDIF as well as
DATES.

C. Add a new entry on IT0041 for your employee 11101## with date type RB.
Enter the first day of the next pay period as the date.

D. Run payroll for the next pay period. As you do, force the retro back a few
periods to test if the rule branch takes effect starting with the current period.

E. Note: It is possible for your new rule to work properly but then actually
cause errors at other places in your schema. This new rule branches to
UMOD rather than you copy of it Z##M. As a result, this will place your
employees in different groupings and possibly conflict with earlier exercise

ã SAP America 2013 WNA11 4 - 48

 scenarios. In any event, you will be able to test your new rule to see if it
performed the branch.

ã SAP America 2013 WNA11 4 - 49

 Solutions

Unit 4: Customizing
Rule 1: Check for Cost Center

· Building new rules

A customer has an on-going issue with cost centers not being entered for
their employees when they are hired. For employees in company code
3000, they need to determine if a cost center has either been on the Cost
Distribution infotype (IT0027) or assigned on the Organizational
Assignment infotype (IT0001).
All cost centers entered on IT0027 are valid. However, if no IT0027
exists, the rule must confirm that a valid master cost center exists on the
IT0001. For company code 3000, valid master cost centers must begin
with the number 3.

1 Check for valid cost center

A. To create your new rule, go to: Menu: Human Resources > Payroll
Accounting > Americas > USA > Tools > Customizing Tools > Calculation
Rule (or transaction PE02). Enter the rule name Z##C and select Create.
Name the rule and choose program class C. Save the attributes, then return to
the rule editor screen.
On the rule editor screen, enter ESG * and wage type ****. Select Change. You
may build the rule using either the graphics editor or the table editor. The
detailed solutions for each rule are available in the appendix.

B. To insert your new rule into your schema, you will want to make a copy of
subschema UBD0 and rename your copy Z##B. Insert a new line in your copy
Z##B following function P0207 . Enter the values ACTIO Z##C to perform the
rule. You are placing the rule here because WPBP data, which includes
infotypes 0001 and 0027, has been loaded. You do not want to continue payroll
processing if the cost center is not valid.
Using the schema editor (transaction PE01), incorporate this new subschema
into your schema by replicating the line COPY UBD0. Then, deactivate the
original line and replace UBD0 with your subschema Z##B.

C. Run payroll for period 04, YYYY, using the display log option.

Menu: Human Resources > Payroll > Americas > USA > Start Payroll.
Get the selection variant you created earlier. Execute the payroll run.

ã SAP America 2013 WNA11 4 - 50

 D. You should receive an error for employee 11101##. Review the processing of
the rule for employee 11101## under Successful personnel numbers > 11101##
> 04/2000 > Basic data processing. Double-click on the line containing your
rule. Confirm that the correct decision operations where reached.
In the Incorrect personnel numbers section, review the error received for
employee 11101##.
E. Create a Cost Distribution infotype for employee 11101## for wage and salary
that is valid from Feb 16, YYYY. Run payroll for period 04, YYYY using
search helps W. Confirm that this employee has successfully processed in
payroll.
Hint: Via PA03: Change the status of your control record to “released for
corrections” in order to edit master data.

Menu: Human Resources > Personnel Management > Administration > HR

Master Data > Maintain

Enter personnel number 11101## and infotype number 0027 and start date Feb
16, YYYY. Select Create. On the infotype screen, enter distribution type 01
Wage/salary. In the table view section, enter company code 3000, cost center
3100 and percentage 100. Save the infotype.

Run payroll using the process described in the previous step of this exercise.
Prior to executing the program, select the Search Helps button, then select W
Payroll correction run. Review the log under Correct Personnel Numbers.

F. When finished, Via PA03, exit Payroll for period 04.

ã SAP America 2013 WNA11 4 - 51

 Unit 4: Customizing
Rule 2: Percentage Deduction from /101

· Building new rules

The customer has a requirement to take a deduction based on a percentage

of total gross. The employee may choose to take this deduction for 1 to
10%, inclusive, of their total gross for the pay period.

1 Percentage based deduction

A. To enter the infotype data, go to: Menu: Human Resources > Personnel
Management > Administration > HR Master Data > Maintain. Enter the
personnel number 11101## and enter infotype 0014. Enter 03/01/YYYY and select
Create. Choose wage type 70## and enter 10 in the Number field. Select Enter to
view the defaults and Save your entry.
B. To create your new rule, go to: Menu: Human Resources > Payroll > Americas >
USA > Tools > Customizing Tools > Calculation Rule (or transaction, PE02.
Enter the rule name Z##P and select Create. Name the rule and choose the program
class.
On the rule editor screen, enter ESG * and wage type 70##. Select Change. You
may build the rule using either the graphics editor or the table editor. Both solutions
are available in the appendix.

C. To insert your new rule into your schema, you will want to make a copy of
subschema UDD0 (suggested name of schema copy is Z##D). Insert a new line in
your version of UDD0 before the line PRART U013 GEN NOAB. Enter the values
PIT Z##P NOAB to call your rule by wage type and regardless of employee
subgroup grouping. You are placing the rule here because cumulation wage type
/101 has been fully created at this point.

Using the schema editor, incorporate the subschema into your schema by replicating
the line COPY UDD0, deactivating the original line and replacing UDD0 with your
subschema name.

D. Run payroll for period 05, YYYY and verify that your percentage deduction is
taken at the appropriate percentage. Review the payroll log section: Successful

ã SAP America 2013 WNA11 4 - 52

 personnel numbers > 11101## > 05/YYYY >Gross cumulation and tax processing >
Else > LPBEG > 1 run > Process deductions, benefits and storage > PIT Z##P
NOAB. Check the input, processing and output. Also confirm that the amount of the
deduction has reduced net pay and appears in technical wage type /110 Total
deductions in log section Final Processing USA > PRINT NP RT.

E. To edit IT0008 and create a WC split, go to: Menu: Human Resources >
Personnel Management > Administration > HR Master Data > Maintain. [Hint:
You will need to change the payroll area status to released for corrections before
entering this data]. Enter the personnel number and select the Basic Pay infotype.
Select Copy. Enter a validity date of Mar 08, YYYY, and select Pay Scale Level
03. Select Enter to view the defaults and Save your entry.

F. Re-run payroll for Period 05, YYYY and review the results as referenced above. If
the deduction is only be taken from one portion of the Total Gross, you may need to
edit processing class 10. Review the import of the Recurring Payments/Deductions
(infotype 0014) record by going to the log section: Successful personnel numbers >
11101## > 03/YYYY >Gross cumulation and tax processing > Else >Processing
further deductions/payments > P0014 U011 GEN NOAB.

Note: Rule U011 continues to rule U111 for processing. The operation VWTCL 10
queries the value in processing class 10 for the wage type being processed. Only
those wage types with processing class 10 values other than zero will reach the
operation WPBPC. This operation assigns basic pay split values to the wage type.
This allows the percentage deduction wage type to access each split value for /101
Total Gross in your custom rule so that a true 10% of gross is taken.

If needed, change the processing class 10 value for your wage type by going to:
SM30 and enter V_512W_O, then select maintain. Find your wage type 70## and
select Details. Enter any processing class 10 value between one and nine, inclusive.
Save your entry. Re-run payroll for period 05, YYYY, to confirm that the wage
type is now properly valuated.

G. When finished exit period 05.

ã SAP America 2013 WNA11 4 - 53

 Unit 4: Customizing
Rule 3: Prorate Absence Payment Based on Length of
Service
· Building new rules

A company has a requirement to modify the amount paid for sick leave
for hourly employees based on an employee’s length of service. The
company only wants to use one wage type for sick leave for hourly
employees, with the variable payment amount set during the processing
of payroll. The wage type should be valued at the following rates of the
employee’s regular hourly amount (as defined in /001):
Length of Service Rate
Less than 13 weeks 0%
13 weeks to 1 year 60%
1 year to 3 years 75%
3 years to 5 years 90%
More than 5 years 100%
The customer wants to reserve the right to change the percentage amounts
on an annual basis without having to access the personnel calculation rule
to make this change.

1. Sick leave by Length of Service

A. Edit the infotype 0041 record for your hourly employee 11102##, go to:
Menu: Human Resources > Personnel Management > Administration > HR
Master Data > Maintain. Enter date type 01 with the date of 01/01/YYYY (3
years in the past). Save the infotype record. (Later you can test variations of
your rule by changing this date to reflect lesser or greater lengths of service).
B. To give your employee an absence in payroll period 6, go to: Menu: Human
resources > Time Management > Administration > Maintain Time Data.
Create an absence record using absence type 0200 for some work days during
March 16-31.
C. Note: You will continue to use Z20M in place of UMOD to access Absence
Valuation Rules. This will set Modif A to 50 for employees in ESG for PCR 1
and to 01 for employees in ESG for PCR 2 and 3. These rules will select wage
type 9002 Illness for absence type 0200 Illness. To review this rule you can
access table V_T554C via SM30.

ã SAP America 2013 WNA11 4 - 54

 D. To create the personnel calculation rule Z##S, go to: Menu: Human
Resources > Payroll Accounting > America > USA > Tools > Customizing
Tools > Schemas (or transaction PE02).

Enter the rule name Z##S and select Create. Name the rule and choose the
program class. On the rule editor screen, enter ESG 1 and wage type 9002.
Select Change. You may build the rule using either the graphics editor or the
table editor. Both solutions are shown in the appendix.
Enter your rule in subschema Z##T, after the line PIT X015 GEN NOAB
using PIT Z##S _____ _____. This will call the rule by wage type and by
ESG for PCR. The order of processing in the schema should be:
PIT X015 GEN NOAB
DATES
PIT Z##S

2. To run payroll for your employee, go to: Menu: Human Resources > Payroll >
Americas > USA > Payroll Accounting > Release Payroll
Payroll Accounting > Start Payroll
In the log, review the processing in rule X015 and rule Z##S. The rate should be
reduced for wage type 9002 to the % of /001 as determined by the LOS with date
type 01 on IT0041 after the processing of rule Z##S. The amount should reflect
the calculation using this new value. The hours should not have been affected.

3. When finished, exit payroll for period 06. Menu: Human Resources > Payroll >
Americas > USA > Payroll Accounting > Exit Payroll

ã SAP America 2013 WNA11 4 - 55

 Unit 4: Customizing
Rules 4A and 4B: Incentive Wage Payment for Hourly
Employees
· Building new rules

Scenario: Your company offers an incentive wage to the hourly

employees. The number of units for the incentive wage is entered on
infotype 2010 Employee Remuneration Information. The value of each
unit of the bonus is derived using the following formula:
200% of Basic Pay value* divided by total hours**

There have been no changes to the details of the program for hourly
employees.
*Basic Pay value for salaried employees is the salary amount from Basic
Pay.
** For salaried employees, total hours worked is work hours per period as
defined on the Basic Pay infotype.
Suggestion: Work with a customer-defined processing class and/or
cumulation class.

1. Calculating value of incentive wage

A. Via transaction PE01, edit your subschema schema Z##T by replacing the
two calls of subschema TC00 with Z20C in both places. Note: For this
exercise, each group will use the same subschema for day processing
with rule TMOD replaced by Z20T. In rule Z20T, all hourly ees
(ESG for PCR 1) will be assigned to time wage type selection rule
group 11. After modifying your subschema, review the Time Wage Type
Selection table (V_T510S) to determine which time wage types can be
selected for your hourly employee for regular and overtime.

IMG: Payroll > Payroll: USA > Day Processing of Time Data > Day
Processing Functions > Wage Type Generation > Set Generation Rules

Review the entries for Time Wage Type selection Rule Group 11 (from
MODIF W) and Day Grouping of 01 for regular days or Day Grouping 02
for holidays and Sundays. The following wage types are selected for

ã SAP America 2013 WNA11 4 - 56

 hourly employees:

1200 Regular working time

1205 Overtime @ Base
1206 Overtime Prem @ 50%
1207 Overtime Prem @ 100%)
1270 Holiday Bonus

B. To enter overtime for your employee, go to: Menu: Human Resources >
Time Management > Administration > Time Data > Maintain. Create
several new overtime records (IT2005), one at a time, any days between
April 1-15, YYYY, for employee 11102##.
C. 1. To copy and modify the wage type, go to: Use transaction OH11 or the
IMG: Payroll Accounting > Payroll: USA > Basic Settings >
Environment for Maintaining Wage Types > Create Wage Type Catalog.
Select copy. Enter 7120 in the OWType field and 71## in the CWType
field (where ## = group number). Select the line to be copied; deselect the
Test run indicator and select the Copy button. Confirm that the correct
table entries have been created.
2. To check the attributes go to: Transaction SM30 and enter table
V_T511 or IMG: Payroll Accounting > Payroll: USA > Basic Settings >
Environment for Maintaining Wage Types > Check Wage Type Catalog
> Check Wage Type Attributes
Select wage type 71##. Go to details. Verify the input combination is set
to Amount -, Number +. Set the Time Unit/Measurement to Inc. wage.

3. To check Permissibility by Infotype: Transaction SM30 and enter table

V_T512Z or IMG: Personnel Management > Personnel
Administration > Payroll Data > Employee Remuneration Information >
Wage Types > Check Wage Type Catalog > Check Entry Permissibility
per Infotype
Enter wage type 71## with the frequency assignment of Once per period.

4. To check Permissibility for employee subgroup and personnel subarea

groupings Transaction SM30 and enter table V_511_B or IMG:
Personnel Management > Personnel Administration > Payroll Data >
Employee Remuneration Information > Wage Types > Define Wage
Type Permissibility for Each PS and ESG

Confirm that the value 1 permissible is assigned to at least Employee

Subgroup Groupings 1, 2 and 3.
5. To check other important characteristics, use transaction code: SM30,
enter V_512W_O.
Pay particular attention to processing class 10 (Will this distribute to
splits?).
Remove any valuation bases.
Assign or verify that cumulation classes 1, 2, 14 and 15 are selected.

ã SAP America 2013 WNA11 4 - 57

 D. To enter Employee Remuneration Information for your employee, go to:
Menu: Human Resources > Time Management > Administration >
Time Data > Maintain. Create a new employee remuneration record for
employee 11102## for 10 units of wage type 71## on April 15, YYYY.

E. To create your new rule or rules, go to: Menu: Human Resources >
Payroll > Americas > USA > Tools > Customizing Tools > Calculation
Rules or Transaction Code: PE02. Use the following name ranges for
any rules you create for this exercise: Z##I, Z##J.

One possible solution is listed in the appendix. This solution uses two
rules. Rule Z##I pulls the amounts and hours of the wage types relevant to
the incentive wage calculation into a new, holding wage type 7INC. Rule
Z##J processes the incentive wage wage type 71##, creating a rate by
manipulating values in 7INC. Customer processing class 99 is used to
manipulate the values in both rules. The elimination and resetting of split
indicators was critical in this processing. See the appendix for details.

F. To run payroll for period 07, YYYY to test your rules, go to: Menu:
Human Resources > Payroll Accounting > America > USA > Payroll.
Confirm that your employee received the correct incentive wage payment
by reviewing the processing of the rules in the log and the results table.

G. When finished, exit payroll for period 07 Menu: Human Resources >
Payroll > Americas > USA > Payroll Accounting > Exit Payroll.
.

ã SAP America 2013 WNA11 4 - 58

 Unit 4: Customizing
Optional: Rules 5A and 5B: Incentive Wage Payment for
Salaried Employees
· Building new rules
· Due to time constraints your instructor may simply demo this
variation on the previous exercise.

Scenario: Your company decides to extend the incentive wage program

to all employees. The number of units for the incentive wage is entered
on infotype 2010 Employee Remuneration Information. As before, the
value of each unit of the bonus is derived using the following formula:
200% of Basic Pay value* divided by total hours**
There have been no changes in the details of the incentive wage program
for hourly employees.

*Basic Pay Value for salaried employees is the salary amount from Basic Pay.
** For salaried employees, total hours worked is work hours per period as
defined on the Basic Pay infotype.

1. Calculating value of incentive wage

A. Confirm that your incentive wage wage type 71## is available to your
salaried employees. Also confirm the processing class values as
necessary.

IMG: Personnel Management > Personnel Administration > Payroll

Data > Employee Remuneration Information > Wage Types > Define
Wage Type Permissibility for Each PS and ESG

Confirm that the value 1 permissible is assigned to Employee Subgroup

Groupings 1, 2 and 3.
Transaction code: SM30. View : V_512W_O.
Pay particular attention to processing classes 3 and 20.

B. To enter Employee Remuneration Information for your employee, go to:

Menu: Human Resources > Time Management > Administration >

ã SAP America 2013 WNA11 4 - 59

 Time Data > Maintain. Create a new employee remuneration record for
employee 11101## for 5 units of wage type 71## on April 30, YYYY.

C. To create your new rule or rules, go to: Menu: Human Resources >
Payroll > Americas > USA > Tools > Customizing Tools > Calculation
Rules or Transaction Code: PE02. Use the following name ranges for
any rules you create for this exercise: Z##X, Z##Y.

One possible solution is listed in the appendix. This solution uses two
rules. Rule Z##X pulls the amounts and hours of the wage types relevant
to the incentive wage calculation into a new, holding wage type 7INC.
Rule Z##Y processes the incentive wage wage type 71##, creating a rate
by manipulating values in 7INC. Customer processing class 99 is used to
manipulate the values in both rules. The elimination and resetting of split
indicators was critical in this processing. See the appendix for details.

D. To run payroll for period 08, YYYY to test your rules, go to: Menu:
Human Resources > Payroll Accounting > America > USA > Payroll.
Confirm that your employee received the correct incentive wage payment
by reviewing the processing of the rules in the log and the results table.

ã SAP America 2013 WNA11 4 - 60

 Unit: Customizing
Topic: Rules 6A and 6B Limit on Arrears

· Building new rules

Because of the cyclical nature of your business, employees often have

deductions that go into arrears. The company has decided to limit the
amount that can be taken for deductions in arrears to $250.00 per pay
period for a series of, but not all, voluntary deductions. The company
wants to be able to distinguish the current amount taken for the
deductions from the limited arrearage amount. They would like you to
demonstrate this process for one wage type to prove that it is possible to
handle this request.

1. Limit on Arrears
A. To copy wage type 8820, go to: IMG: Payroll > Payroll: USA >Basic
Settings > Environment for Maintaining Wage Types > Create Wage
Type Catalog: Or use transaction OH11.
Enter 8820 in the original wage type field and 88## in the customer wage
type field. Give the wage type a suitable text. Select your new wage type
and Deselect the test run box and choose Copy.
B. To confirm that wage type 88## to convert to wage type 8888 when it goes
into arrears: IMG: Payroll > Payroll: USA > Deductions > Limits on
Deductions > Rename Wage Types for Arrears Processing

Confirm that wage type 88## is linked to wage type 8888 with indicator
20. The validity dates should match the dates of your copy from 8820.
C. To create a large deduction and place an amount in the ARRRS table: Go
to transaction PA30:
Enter 11102## in the personnel no. field, enter 15 in the infotype field
and choose Create. The last day of the next payroll period will default as
the date of origin, you can use that date.
Enter 88## in the wage type field and 3000 in the amount field. Then
choose Save.
D. Run payroll for period 09, YYYY in order to take the deduction and create
a large amount on the ARRRS table. Menu: Human Resources > Payroll
Accounting > America > USA > Payroll.

ã SAP America 2013 WNA11 4 - 61

 In the payroll log, review the amount of the deduction that has gone into
arrears and confirm that the amount now shows in wage type 8888.
Log: Successful personnel numbers > 11102## > Current Period> Final
Processing > PRINT ARRS.
E. Copy rule U013 to Z##A. Use this new rule to call a second rule, Z##L
which you will create to limit the recovery amount of wage type 8888 to
$250 and moves the remaining balance forward for the next payroll run.
An example of two rules which can be used together to set such a limit for
arrears is in the appendix. The first rule uses processing class 76 to
determine when the limit should occur and the second rule applies the limit
and moves the balance remaining forward on the arrears table for
processing in the next period.
F. Run payroll for period 10, YYYY and confirm that the deduction
recovered from arrears was limited to $250.00 with the remainder kept on
the arrears table to be processed (with the limit) in future periods.
Log: Successful personnel numbers > 11102## > Current Period> Final
Processing > PRINT ARRS and PRINT RT
G. As always, review the detailed processing of your rule.
H. Optional: Adjust your rule to incorporate the following considerations:
1. The limited amount is $200 for employees in payroll area 4#, but $250 for
everyone else.
Solution: You could incorporate operation WPBP into your rule to query
the payroll area and then specify different limits for different ones.
2. Historically at your company, the limited amount has often changed. You
want to be proactive and plan for this contingency. How could you set up
your rule to most efficiently handle possible future changes to the limit?
For example: a decision is made to change the limited amount to $150 on
August 1 of the current year for employees in payroll area 4# and $175 for
everyone else.
Solution: You could set up constants on V_T511K which hold the
different limit values and can easily be delimited by dates in the future.
You would need at least two constants, one for the limit amount for your
payroll area and one for everyone else. If you want to attempt this name
you constants Z##4# for your payroll area and Z##EV for everyone else.

ã SAP America 2013 WNA11 4 - 62

 Unit: Customizing
Rule 7 Using IF and ELSE with a PCR to process dates

· Access different places in the schema using dates

· Building new rules

Based on a particular date, your company desires to access the schema

differently than it has in the past. However, you want the schema to still
be accessed the way it was in the past during any retrocalculation runs.
You need to demonstrate how this can be accomplished using functions
IF/ELSE and a PCR with operation SCOND.

1. Create a PCR that (when call with function IF) will branch to different places in the
schema based on dates from IT0041.

A. Create rule Z##B. In it, include two decisions. First include a decision about your
payroll area. Second, include a date calculation using the difference between date
type RB on IT0041 and the end of the current period. You want to use operation
SCOND to determine when the difference between the dates you are querying has
occurred. Once the condition is found to be true, you want to branch to SAP
subschema UMO0 and no longer your copy of it Z##M.

To create your new rule, go to: Transaction Code: PE02

Name your new rule Z##B. One possible solution is listed in the appendix.

B. Place your new rule in your main Schema Z##U after subschema XLR0. Be sure
to include the appropriate functions IF, ELSE and ENDIF as well as DATES.

To place your new rule in your main schema, go to: Transaction code: PE01

After the line COPY XLR0, add the functions DATES, IF (with your new rule
Z##B in parmater 2), ELSE and ENDIF. IF should COPY subschema UMO0 and
ELSE should COPY Z##M. See the appendix for details if necessary.

C. Add a new entry on IT0041 for your employee 11101## with date type RB. Enter
the first day of the next pay period as the date.

ã SAP America 2013 WNA11 4 - 63

 To add a new entry on IT0041 for your employee, go to: Transaction code:
PA30

Enter 11101## in the personnel no. field, enter 41 in the infotype field and
choose Change. Enter an additional date type, RB and assign the first day of the
next payroll period (should be 06/01/YYYY) as the date, then Save.

D. Run payroll for the next pay period. As you do, force the retro back a few periods
to test if the rule branch takes effect starting with the current period.

To run payroll for period 11, YYYY go to, Menu: Human Resources > Payroll
Accounting > America > USA > Payroll.

Be sure to force the retro back a few periods to test if the rule created the branch
for the correct pay periods. If it worked correctly you should branch to
subschema UMO0 in the current period, but Z##M for any prior periods. Check
the log for the current pay period as well as a previous one to verify this took
place.

E. Note: It is possible for your new rule to work properly but then actually cause
errors at other places in your schema. This new rule branches to UMOD rather
than you copy of it Z##M. As a result, this will place your employees in
different groupings and possibly conflict with earlier exercise scenarios. In any
event, you will be able to test your new rule to see if it performed the branch.

ã SAP America 2013 WNA11 4 - 64

 Advanced Processing Options

Contents:
l Working with transaction PE04
l Working with debugger to analyze processing

ã SAP AG 2013 WNA11

 Advanced Processing Options : Objectives
By the end of this unit, you will be able to:
l Read the technical setup of a function

l Examine how a function is used/called in a schema

l Work with debugger to isolate certain processing steps in the

payroll program which may be difficult to do in the log

ã SAP AG 2013 WNA11

 Function and Operation Definition

ã SAP AG 2013 WNA11

 Reading Functions and Operations

ã SAP AG 2013 WNA11

 Reading Functions and Operations

ã SAP AG 2013 WNA11

 Definition of Operations

ã SAP AG 2013 WNA11

 Definition of Operations

ã SAP AG 2013 WNA11

 Steps for Creating a Function
1. Name your new function

2. Document your new function

3. Select valid countries

4. Set valid parameters

5. Enter valid values for the parameters

6. Save and add to development class

7. Activate

8. Add form routine to customer-include

RPCBURZ0

ã SAP AG 2013 WNA11

 Debugging
n Breakpoints
u Hard breakpoint in functions, operations
u Soft breakpoints set directly when using Debugger

n Watchpoints
u Trace a wage type during the process of a schema
u Observe the impact of processing classes

u Observe different values in a processing class

ã SAP AG 2013 WNA11

 Debugging Payroll

/h activates
debugger

ã SAP AG 2013 WNA11

 Setting Breakpoints

Breakpoint >
Breakpoint at >
Subroutine

ã SAP AG 2013 WNA11

 Debugging: Stop at Breakpoint

ã SAP AG 2013 WNA11

 Creating Watchpoints

ã SAP AG 2013 WNA11

 Tracking Watchpoints

ã SAP AG 2013 WNA11

 Views in Debugging

ã SAP AG 2013 WNA11

 Views in Debugging

ã SAP AG 2013 WNA11

 Function and Operation BREAK
The picture can't be display ed.

ã SAP AG 2013 WNA11

 Processing Operation Break

ã SAP AG 2013 WNA11

 Advanced Processing Options : Unit Summary
n Custom functions can be created for use in a schema. For
the function to be active, you must include the form routine
in the customer-include program that is used with
RPCALCU0
n It is important to document and test a new function
n Payroll processing can be run using debugger and setting
break points. This allows you to see the actual data as it
processes --
u in the schema
u in a rule

u in the payroll program

n Run debugger when you want to change field values

during processing or confirm the fill of a specific field.

ã SAP AG 2013 WNA11

 Running Payroll with Debugging

Note: With the payroll driver the classic debugger is usually the best option to use: To be sure
your user id is set up to use it, go to transaction SE38. From the top menu choose Utilities ->
Settings. Choose the Debugging tab, select the radio button for Classic Debugging and choose
Transfer.

1. To run payroll with debugging: Run a simulation payroll for your salaried employee
11101## during a period in which they had wage type 70## assigned on IT0014. This
should be any period after and including 05.

On the payroll driver screen, enter a /h in the command field and choose enter. Note:
You should receive a message at the bottom of the screen that debugging switched on.
After noting the message, execute payroll.

2. Set a Breakpoint: From the top menu choose Breakpoints ->Breakpoint at ->
Subroutine and enter FUPIT in the Subroutine/Method/Module field and click on
Continue (Enter).

3. From the icon bar choose the Run (to Cursor) icon or the F8 key. This will take you to
the first place in the program where function PIT occurs.

4. You’ll notice a stop sign next to the place in the program where it first found function
PIT. To see the PCR being used by this call of function PIT double-click on the words in
this line next to the stop sign: “as-parm1”.

5. In the Field Names section near the bottom of your screen, you see the field is brought
in with the name of the rule (U010) that is being processed at this point.

6. To view what is on the IT table at this point, choose the Table button and in the Internal
Table field enter IT and then choose enter. Note: You could also enter any other internal
table that would have been created by this point…for example the LRT. If you enter the
RT or OT you will have no entries at rule U010 as no wage types have been moved to
either of these internal tables at this point in the schema.

7. Clear your breakpoint: To clear your breakpoint, double-click on the stop sign icon.

8. Create a Watchpoint: To go to the Watchpoints screen, click on the Watchpoints

button. To create a Watchpoint, choose the Create Watchpoint icon and make the
following entries:

a. Program: RPCALCU0
b. Field Name: it-lgart
c. Relational Operator: = (equals)
d. Comp. Field/value: /101
e. And choose the green check or enter
f. Click on Run to Cursor
ã SAP America 2013 WNA11 5 - 20
 g. Click on the Fields button, the field as-parm1 should still be displayed in the
Field names. Add another field entry: Enter it-lgart as a field and then choose
enter. Wage type /101 should appear in the field.
h. What is the name of the rule where the program stopped? It should be Z##P. If is
not click on Run to the Cursor until rule Z##P is displayed.

9. Create another Watchpoint: To to the Watchpoints screen, click on the Watchpoints

button. Choose the Create Watchpoint icon and make the following entries:

a. Program: RPCALCU0
b. Field Name: it-lgart
c. Relational Operator: = (equals)
d. Comp. Field/value: 70##
e. And choose the green check or enter
f. Accept the OR default for the Logical operator between watchpoints
g. Return to the Fields screen
h. Click on Run to Cursor

10. Change some of the field contents. On the Fields screen:

a. Wage type 70## should now be displayed in the it-lgart field

b. Click on the Table button and enter the IT table to view the contents. Verify that
both /101 and 70## are on the table.
c. Return to the Fields screen and enter these additional fields: it-anzhl and it-betrg
and then choose enter
d. Overwrite the 10 in the anzhl field with 20 and then Click on the Change fld
contents icon. Note: This will lead to a 20% deduction instead of the 10%
entered on IT0014.
e. Click on Run to Cursor until you see 450- in the it-betrg field of wage type 70##.

11. Delete your Watchpoints: To delete both of your watchpoints, Click on the Watchpoint
button and choose the Delete Watchpoint icon for both watchpoints.

12. Click on Run to Cursor to finish the payroll run and view the results in the log. Go to
Final Processing USA and double-click on the line PRINT RT. Verify that wage type
70## now has 20 in the number field and 450- as the amount.

ã SAP America 2013 WNA11 5 - 21

WNA11 Appendix A

Solutions
 Solution: Check for Cost Center

ã SAP AG 2013 WNA11

 Solution: Check for Cost Center

ã SAP AG 2013 WNA11

 Solution: Check for Cost Center in Schema

In Schema Z##U (U000)

In Subschema Z##B (UBD0)

ã SAP AG 2013 WNA11

 Solution: Check for Cost Center, Log View

No cost distribution
or master cost
center

Valid master cost

center

ã SAP AG 2013 WNA11

 Solution: Percentage Deduction

ã SAP AG 2013 WNA11

 Solution: Percentage Deduction in Schema

In Schema Z##U (U000)

In Z##D (UDD0)

ã SAP AG 2013 WNA11

 Solution: Length of Service Valuation of Absence

ã SAP AG 2013 WNA11

 Solution: Length of Service Valuation of Absence

ã SAP AG 2013 WNA11

 Solution: Length of Service Valuation of Absence

ã SAP AG 2013 WNA11

 Solution: Length of Service/Absences

V_T511K

ã SAP AG 2013 WNA11

 Solutions 4A: Hourly Incentive Wage Calculation

Wage type Proc. class

99
1200 Regular Working 1
Time
1205 Overtime Base 2

1206, 1207, 1210, 1211 3

Overtime Premiums
71## Incentive Wage 0
Payment (Copy of 7120)
7INC Calculation Base 9

ã SAP AG 2013 WNA11

 Solutions 4A: Incentive Wage Calculation

ã SAP AG 2013 WNA11

 Solutions 4B: Hourly Incentive Wage Calculation

Only the incentive wage

payment is processed

ã SAP AG 2013 WNA11

 Solutions: Incentive Wage Calculation

n Entry of two incentive wage

rules after X015 wage type
valuation
n Inserted prior to X020
cumulation and storage

ã SAP AG 2013 WNA11

 Solutions 5A: Salary Incentive Wage Calculation
Needed for possible wage
types on IT without
ESG for PCR

Wage type Proc’g

class 99
1002 Salary 4

71## Incentive Wage 0

Payment (Copy of 7120)
7INC Calculation Base 9

ã SAP AG 2013 WNA11

 Solutions 5B: Salary Incentive Wage Calculation

If both ESG/PCR 2 and 3 are Salaried EEs,

then the rule would need to include both.
Our Salary EE is in ESG/PCR 2

ã SAP AG 2013 WNA11

 Solutions: Incentive Wage for Salaried Employees

n In Subschema Z##A (UAL0)

n Entry of two incentive wage
rules after XVAL proration
n Inserted prior to X023
cumulation and storage
(completion of total gross)

ã SAP AG 2013 WNA11

 Solutions 6: Limit Arrears Recovery
n While not required, an entry in table V_T51P1 can be used to
rename the arrears wage type. Use link 20 to do so. This would
allow for multiple deductions to be placed in the same “bucket” for
repayment.

n With this entry, wage type 8820 will be renamed 8888 before being
stored on the ARRRS table at function PREND, in subschema
UDNT, during the second run of deduction processing.

ã SAP AG 2013 WNA11

 Solutions: 6A Limit Arrears Recovery

This is a copy of SAP rule U013 (which is called

with function PRART in UDD0). In this version
of the rule during a regular run, a wage type
whose processing class 76 value is anything
other than a 1 or 2 will jump to rule Z20L.

This new rule Z##L could be used to perform

custom arrears processing. In our scenario we
want to limit the amount to be recovered to $250
and move the remaining balance back to arrears
for future processing.

In the standard U013, operation ADDWT is used

where Z20L is now called to simply move all
arrears wage types to the IT table. The system
would then attempt to recover the entire amount.

ã SAP AG 2013 WNA11

 Solutions: 6B Limit Arrears Recovery

Called by function PRART, this rule will

query the wage types on the AOA table
(previous period ARRRS).
All wage types except for 8888, will be
placed on the IT table as a deduction
for the full amount in arrears.
Wage type 8888 will be reduced by
$250 with the remainder placed in the
ARRRS table. The $250 deduction is
then placed on the IT and added to
technical wage type /190 for reporting.
When the amount for wage type 8888
is greater than 250-, then the total
amount will be transferred to the IT and
nothing goes to ARRRS.

ã SAP AG 2013 WNA11

 Copy of subschema UDD0 with new rule

Rule Z##A can replace U013 to allow for special processing of wage
type 8888.
In rule U013, Processing Class 76 is intended by SAP to be used by
customers for their specific deduction processing needs.
Rules U011 (with P0014) and U015 (with P0015) similarly use
processing class 76 as well.

ã SAP AG 2013 WNA11

 Optional Exercise Using Constants for ARRRS
This rule has special processing for wage type 8888.
All other wage types on the AOA table will be added to the
OT and the system will try to collect everything it can.
But, for wage type 8888, rule Z21L will determine if the
amount in arrears is greater than $150. If so, only $150 will
be taken and the remainder placed in new ARRRS.
Since table V_T511K cannot hold a negative number, the
arrears amount must first be multiplied by 1- to make it
positive. Then it can be compared to constant Z20ME for
payroll area 4U. If the arrears value is “greater than” the
constant, it would mean more money is in arrears than the
limit and therefore should be capped.
After the limit check, the arrears AMT is again multiplied by
1- to restore it’s original value as a negative number. The
positive value from constant Z20ME is then added to it
which will reduce it.
The reduced remainder is placed back on ARRRS and
added to /190. The AMT is now set to constant Z20ME,
multiplied by 1- and ADDWT places it on the OT as a
deduction.
ã SAP AG 2013 WNA11
 Table V_T511K for Arrears Cap

Z20ME represents a different limit for arrears deductions than Z20EV.

This values can be incorporated into arrears processing rules to set
different limits for different employee groups.
Since you cannot enter a negative value in V_T511K, multiply the AMT
from AOA by 1-. This makes it a positive number. Then compare it to
what is on V_T511K. But you will need to multiply it again by 1- at
some point. Just be aware of when you are working with it as a
positive number and when it is negative or the math will be incorrect.

ã SAP AG 2013 WNA11

 Solutions 71: Rule Z##B: Date Branch in Schema

Rule 7, Option 1:
IT0041 Date Type RB

ã SAP AG 2013 WNA11

 Solutions 71: Rule Z##B: Date Branch in Schema

Example IT0041 with date type RB used in rule

Z##B to branch based on dates

ã SAP AG 2013 WNA11

 Solutions 72: Rule Z##B: Date Branch in Schema
Rule 7, Option 2:
Use a Year and Payroll Period

ã SAP AG 2013 WNA11

 Solutions: Rule Z##B: Placing Rule in Schema*

Hint: If you created option 1 for your rule, use the DATES function
preceding your rule.
For the purpose of testing, place this rule in your main schema Z##U
after subschema XLR0.
*However, you can place a rule like this anywhere in your schema
when you wish to branch.

ã SAP AG 2013 WNA11

 Solutions 7.3: Rule /22B: Date Branch in Schema

Rule 7, Option 3:
Use a constant on V_T511K with a
value of 1 as a trigger.

ã SAP AG 2013 WNA11

 WNA11 Appendix B
Supplement to Unit 3:
Important tables for Wage Type Configuration

© SAP AG 2013 WNA11 Appendix B -1

V_T511 “Wage Type Characteristics” Table
(Note: TARIF points the wage type to V_T510. The input combo +/-is typical
for TARIF.)

© SAP AG 2013 WNA11 Appendix B - 2

 By using the F1 key on the field for input combination you can see the
possible entries. Note: The F4 key is not very helpful here.

© SAP AG 2013 WNA11 Appendix B - 3

V_T510 “Pay Scale Groups”
The Grpg field is the Employee Subgroup Grouping for CAP
For Dialog Wage Types on IT0008, IT0014 or IT0015 the table is accessed
using the Indirect Valuation Module TARIF, variants A,B,C or D
For Time Wage Types, Rule X015 can access this table for a wage type with
the Valuation Bases TS, TG or T
In this example “Dialog” Wage Type MM20 would be assigned TARIF C
But, if it were a “Time” Wage Type it would have the valuation basis TG

© SAP AG 2013 WNA11 Appendix B - 4

V_T511 “Wage Type Characteristics” Table
(Note: PRZNT or SUMME point a wage type to V_T539J for a base value.
Input combo -/+ is typical for PRZNT. For SUMME -/- is often used.

© SAP AG 2013 WNA11 Appendix B - 5

V_T539J “Base Wage Type Valuation” Table
For Dialog Wage Types on IT0008, IT0014 or IT0015 the table is accessed
using the Indirect Valuation Modules PRZNT or SUMME variants I or D
This table is also used to calculate ASAL, BSAL and CSAL

© SAP AG 2013 WNA11 Appendix B - 6

V_512W_O
Time Wage Type with a Derived Wage Type both using valuation basis 01
(the employees hourly rate in /001).
Wage type adds to /101 Total Gross since Cumulations class 01 chosen

© SAP AG 2013 WNA11 Appendix B - 7

V_512W_O

Time Wage Type with a valuation basis of a K. It will be valuated from an

entry in V_T510J.

© SAP AG 2013 WNA11 Appendix B - 8

V_T510J
The field PMod “Payroll Modifier” is the Modif 2 value from rule XMOD.
Using Operation OUTWP, XMOD can assign employees to different
groupings for this table.
Therefore you can use the same wage type, but get a different rate for
different kinds of employees.

© SAP AG 2013 WNA11 Appendix B - 9

V_T554C
Function PAB accesses this table. Rule XMOD, Modif A is the AbsValGrpg
“Absence Valuation Grouping”.

© SAP AG 2013 WNA11 Appendix B - 10

V_T510S Function GWT accesses this table.
TMOD, Modif W is the “Time WT sel. rule grp”
If all conditions met, Wage Type will be selected for a MAX of 2 Hours

© SAP AG 2013 WNA11 Appendix B - 11

V_T510S Function GWT accesses this table.
TMOD, Modif W is the “Time WT sel. rule grp”
If all conditions met, Wage Type will be selected After a MIN of 2 Hours

© SAP AG 2013 WNA11 Appendix B - 12

V_T510S Function GWT accesses this table with TMOD, Modif W
If all other conditions met, Wage Type selected only for hours worked
between 22 – 30 (10PM – 6AM the next morning).
This example also includes restrictions on the employees Period Work
Schedule “Val. Class” and Daily Work Schedule Class “DWS class”.

© SAP AG 2013 WNA11 Appendix B - 13