sap payroll

SAP India

SAP AG HR400 (4.6B) Payroll Configuration 0-7

SAP AG 1999

HR400Payroll Configuration

HR400HR400

Payroll ConfigurationPayroll Configuration

n R/3

n Release 4.6B

n June 2000

n 50036639

SAP India


SAP AG 1999

Copyright 2000 SAP AG. All rights reserved.

Neither this training manual nor any part thereof maybe copied or reproduced in any form or by any means,or translated into another language, without the priorconsent of SAP AG. The information contained in thisdocument is subject to change and supplement without priornotice.

All rights reserved.

Copyright

SAP India


Trademarks:

n Microsoft ®, Windows ®, NT ®, PowerPoint ®, WinWord ®, Excel ®, Project ®, SQL-Server ®, Multimedia Viewer ®, Video for Windows ®, Internet Explorer ®, NetShow ®, and HTML Help ® are registered trademarks of Microsoft Corporation.

n Lotus ScreenCam ® is a registered trademark of Lotus Development Corporation.

n Vivo ® and VivoActive ® are registered trademarks of RealNetworks, Inc.

n ARIS Toolset ® is a registered Trademark of IDS Prof. Scheer GmbH, Saarbrücken

n Adobe ® and Acrobat ® are registered trademarks of Adobe Systems Inc.

n TouchSend Index ® is a registered trademark of TouchSend Corporation.

n Visio ® is a registered trademark of Visio Corporation.

n IBM ®, OS/2 ®, DB2/6000 ® and AIX ® are a registered trademark of IBM Corporation.

n Indeo ® is a registered trademark of Intel Corporation.

n Netscape Navigator ®, and Netscape Communicator ® are registered trademarks of Netscape Communications, Inc.

n OSF/Motif ® is a registered trademark of Open Software Foundation.

n ORACLE ® is a registered trademark of ORACLE Corporation, California, USA.

n INFORMIX ®-OnLine for SAP is a registered trademark of Informix Software Incorporated.

n UNIX ® and X/Open ® are registered trademarks of SCO Santa Cruz Operation.

n ADABAS ® is a registered trademark of Software AG

n The following are trademarks or registered trademarks of SAP AG; ABAP/4, InterSAP, RIVA, R/2, R/3, R/3 Retail, SAP (Word), SAPaccess, SAPfile, SAPfind, SAPmail, SAPoffice, SAPscript, SAPtime, SAPtronic, SAP-EDI, SAP EarlyWatch, SAP ArchiveLink, SAP Business Workflow, and ALE/WEB. The SAP logo and all other SAP products, services, logos, or brand names included herein are also trademarks or registered trademarks of SAP AG.

n Other products, services, logos, or brand names included herein are trademarks or registered trademarks of their respective owners.

SAP India


SAP AG 1999

Human Resources 4.6 (1)

Level 3Level 2

Human Resources

HR050 5 days

Employee Self ServiceHR250 3 days

OrganizationalManagement

HR505 3 days

Travel ManagementTravel Expenses

AC270 3 days

CompensationManagement

HR540 3 days

Reporting inHR

HR580 3 days

Training and EventManagement

HR515 3 days

Time EvaluationHR310/311 5 days

Configuration ofMaster Data

HR305 3 days

Configuration of TimeRecording

HR306 3 days

BenefitsAdministration

HR325 3 days

RecruitmentHR315 3 days

seeHR2

Configuration of HRSystem Controls

HR307 2 days

Programming in HR

HR350 5 days

Technical Topics inHuman Resources

HR530 3 days

CATS The CrossApplication Time Sheet

CA500 2 days

PersonnelDevelopment

HR510 3 days

SAP India


SAP AG 1999

Human Resources 4.6 (2)

Human Resources

HR050 5 days

Payroll Reporting(Country-Specific)

HR7xx 2 days

Level 2 Level 3

Payroll Configuration

HR400 5 days

Country-SpecificPayroll

HR4xx 3 days

Configuration ofMaster Data

HR305 3 days

Introductionto Payroll

HR390 2 days

SAP India


SAP AG 1999

Course Prerequisites

l HR050 - Human Resources

l HR305 - Configuration of Master Data

l HR306 - Configuration of Time Recording

l HR390 - Introduction to Payroll

SAP India


SAP AG 1999

Target Group

SAP AG

l Audiencen Project team members responsible for Customizing

and supporting payroll.

l Duration: 5 days

Notes to the user

n The training materials are not teach-yourself programs . They complement the course instructor's explanations . Your material includes space for noting down this additional information.

n There may not be enough time to do all the exercises during the course. The exercises are intended to be additional examples that are dealt with during the course. Participants can also use them to deepen their knowledge after the course.

© SAP AG HR400 1-1

SAP AG 1999

Course Overview

l Course goal

l Course objectives

l Course content

l Course overview diagram

l Main business scenario

Contents:

© SAP AG HR400 1-2

SAP AG 1999

Course Goal

This course will prepare you to:

l Modify HR Payroll to the specificrequirements of your enterprise.

© SAP AG HR400 1-3

SAP AG 1999

Course Objectives

At the conclusion of this course, you will be able to:

l Use the IMG to make changes in the schema and personnel calculation rules so that you can modify wage type valuation, the processing of absencesand averages, time wage type generation, factoring and the formation of cumulation wage types to meet your company’s requirements.

© SAP AG HR400 1-4

SAP AG 1999

Course Contents

Unit 7 Time Wage Type Selection

Unit 8 Averages

Unit 9 Factoring

Unit 10 Cumulation Wage Types

Unit 11 Retroactive Accounting

Unit 1 Course Overview

Unit 2 Payroll Basics

Unit 3 Personnel Calculation Rules

Unit 4 Starting Payroll

Unit 5 Wage Type Valuation

Unit 6 Absence Valuation

Appendix

Exercises

Solutions

Preface

© SAP AG HR400 1-5

SAP AG 1999

Course Overview Diagram

Payroll Basics

Starting Payroll

Personnel Calculation Rules

Wage Type Valuation

Time Wage Type Selection

Averages

Cumulation Wage Types

Factoring

Retroactive AccountingAbsence Valuation

© SAP AG HR400 1-6

SAP AG 1999

Main Business Scenario

l Your company, the Caliber ‘A’ Bicycle Company, is implementing HR Payroll.

l As a member of the project team, you have to map the specific payroll requirements of your company in the HR system.

© SAP AG HR400 2-1

SAP AG 1999

Payroll Basics

l Payroll Steps

l Wage Types in Payroll

l The SAP Payroll Concept

l Payroll Schema X000

l Main Schema and Subschemas

l Functions and What They Do

l The Schema Editor

l Functions and Personnel Calculation Rules

Contents:

© SAP AG HR400 2-2

SAP AG 1999

Payroll Basics: Unit Objectives

l Identify wage types as an essential part of payroll

l Describe the SAP payroll concept and its advantages

l Define payroll control using the process schema and functions

l Explain why some functions require personnelcalculation rules to process wage types

l Use the schema editor

At the conclusion of this unit, you will be able to:

© SAP AG HR400 2-3

SAP AG 1999


Payroll Basics

Starting Payroll


Wage Type Valuation


Averages


Factoring


© SAP AG HR400 2-4

SAP AG 1999

Remuneration Structure

Periodic remuneration

PnnnnWage type Amount Number/Unit


P0014 Recurring

Wage type Amount Number/Unit

P0008 Basic Pay

Wage type Amount Number/Unit


P2010 EmployeeRemuneration Info.Wage type Number/Unit (Amount)

Basic pay

Bonuses

Time compensation(variable parts)

Bonuses for overtime, night work,Sunday and public holiday work basedon planned working time and overtime

Time compensation(variable parts)

Automaticgenerationduring thepayroll run

Basic remuneration(fixed parts)

n The elements of an employee’s periodic remuneration are either entered by the relevant department or are created by the payroll program using specific prerequisites as a basis.

© SAP AG HR400 2-5

SAP AG 1999

Wage Type Information

What informationdo wage types

contain?

Assignment to employeegroupings

Name

Assignmentto Cost

Accounting

Assignmentto a particular

part of the payroll period

Value fields:Number, rate,

amount

Characteristics determining payroll

processing

Assignmentto absences

n Wage types form an essential part of payroll. A wage type consists of several fields containing various information.

© SAP AG HR400 2-6

SAP AG 1999

Wage Type Elements

Examples:

- Hourly wage

- Time wage type:

- Salary

Partial period 01

Partial period 02

WPBP-Split

01

Workcenter basicpay

01

01

02

RTE

15.00

AmountperunitRATE

20.00

NUM

Number

NUMBER

3

AMT

Amount

AMOUNT

60.00

4,500.00

5,000.00

n Each wage type is assigned to a work center/basic pay period. If, for example, an employee's pay changes within a payroll period, then the period is split into partial periods, and the wage types are assigned to these partial periods.

n Furthermore, each wage type contains three value fields :

n The RTE field specifies, for example, the hourly rate used for hourly wage types.

n With time wage types, the NUM field initially specifies three hours overtime, for example. To determine the time wage type amount, the system multiplies the number by the rate, and stores the result in the AMT field. The rate for time wage types is calculated according to the conditions defined in Customizing.

n With basic pay wage types, such as salary, the amount is stored in the AMT field.

© SAP AG HR400 2-7

SAP AG 1999

Validity Period of Wage Type Characteristics

Example

1997

Tax-free Subject to tax

19991998

n Each wage type contains a sequence of time-dependent characteristics that determine how the wage type is treated during the payroll run. The characteristics that are stored enable you to control how wage types are processed during payroll.

n If wage type characteristics change, it does not suffice to simply change the corresponding table entries. Instead, the validity periods of existing entries must be delimited, and new entries created with the characteristics required in the future.

n If you change the wage type characteristics of a previous payroll period, you must correct all subsequent payroll results. As the system does not automatically recognize such changes, you must force retroactive accounting runs for the relevant employees and payroll periods.

© SAP AG HR400 2-8

SAP AG 1999

Wage Type Coding

Secondary wage types

- Valuation bases /0..

- Gross cumulation /1..

- Average bases /2..

- Factoring / CO /8..

- Outgoing wage types inretroactive acc. period /A..

- Incoming wage typesfrom previous period /Z..

- Others:- Result wage types: Tax /3..- Result wage types: SI /4..

- Dialog wage types

- Time wage types

- Others: Absences

2.Primary wage types1.

n Primary wage types are either entered into the system directly by the user (for example, dialog wage types for basic pay) or generated by the system based on time data (for example, time wage types for overtime).

n During the payroll run, the payroll program creates secondary wage types. For example, all amounts to be paid are cumulated into the secondary wage type Total Gross (/101) during the run. SAP delivers secondary wage types identified by a name starting with /.

n You can create customer wage types in the above name range. Note that many secondary wage types have a fixed meaning and that you must therefore not change the name.

n You can create customer wage types by copying and modifying non-technical wage types.

© SAP AG HR400 2-9

SAP AG 1999

Payroll Processes

Read basic data1.1.

Read payroll accounts from the payroll period last accounted

2.2.

Time data processing- Read time data- Generate time wage types- Valuate time wage types

3.3.

Import additional payments/deductions4.4.

Factoring- Reduce basic pay - Determine wage types for FI/CO

5.5.

Statutory payments/deductions6.6.

Net payments/deductions7.7.

Determine payment amount8.8.

n The customer largely defines the first phase of processing.

n The second phase involving statutory payments and deductions rarely requires customer adjustments.

© SAP AG HR400 2-10

SAP AG 1999

The SAP Payroll Concept

Payroll driver Schema

SAP Customer (IMG)

Customizingtables

Personnel calculation rule

Function

Operations

Function module

Operation module

n A customer-defined schema and the functions included in that schema affect flow control in the payroll driver. A function calls the function module assigned to it in the payroll driver. Certain functions also call personnel calculation rules containing operations that are linked to operation modules in the payroll driver.

n During the payroll run, function and operation modules access entries stored in Customizing tables.

© SAP AG HR400 2-11

SAP AG 1999

XIN0

XBD0

XLR0

XT00

XAP9

XAL9

XNA9

XRR0

XNN0

XEND

International Payroll Schema X000

Payroll schema:

Initialization of payroll

Edit basic data

Import last payroll results

Process time data for Payroll

Import additional payments/deductions

Partial period factoring and storage

Cumulate net amount/form payment amount

Retroactive accounting

Net payments/deductions and transfers

Final processing

INTERNATIONAL Gross wage calculationand transfer

n To run the payroll program, you require a payroll driver and a payroll schema. The payroll schema defines the processes carried out by the payroll driver and ensures that the program gathers all the data required to run payroll for an employee in a specified period.

© SAP AG HR400 2-12

SAP AG 1999

COMBLOCKENAME WPBPGONBLOCK

BEG

END

Basic data INTERNATIONAL Edit basic data Determine name of EERead work center/basic pay dataContinue with complete dataEdit basic data Functions

COM

COM

COM

COPY XIN0

COPY XBD0

COPY XLR0

COPY XT 00

COPY XAP9

COPY XAL9

COPY XNA9

COPY XRR0

COPY XNN0

COPY XEND

Payroll Schema: INTERNATIONAL

Gross wage calculation

and transfer


Edit basic data


Process time data for Payroll




Retroactive accounting

Net payments/deductions and transfers

Final processing

Main Schema and Subschemas

n A main schema consists of a sequence of subschemas that are included in the main schema using the COPY function. The main schema is generated and subsequently executed by the payroll driver.

n Subschemas can be edited separately in Customizing, yet they are not executable unless incorporated into a main schema.

n A schema consists of a sequence of functions . Functions retrieve and process the data required for each processing step.

© SAP AG HR400 2-13

SAP AG 1999

Function Types and Examples

Functions that import infotype data:WPBP Work center and basic pay dataRAB AbsencesP0015 Additional paymentsP2010 EE remuneration information

Functions that process data according to the entries in Customizing tables:PAB Absence valuation

Functions that edit wage types using personnel calculation rules:PIT Process input table

n You can display documentation on a function by pressing F1.

n Functions within a schema are processed sequentially.

n Data processing for employee wage types takes place in internal payroll tables. To process such data, certain functions access an assigned personnel calculation rule that can be adjusted if necessary.

© SAP AG HR400 2-14

SAP AG 1999

Create

Display Change

Maintaining Schemas

Schema

Source text

Attributes

Documentation

n The schema editor (transaction PE01) enables you to display and maintain schemas.

n When displaying a source text, you can choose between tables and structural graphics.

n The personnel calculation schema editor enables you to carry out the following activities:

• Display and print schema directory

• Compare source text from schemas

• Copy schemas

• Change schema elements

• Create schemas

• Check the syntax of source text in schemas

• Generate modified or new source text

• Transport schemas to another client

• Navigate within and between schema elements

• Navigate between schemas

• Access personnel calculation rules

© SAP AG HR400 2-15

SAP AG 1999

Administrative data

Attributes

Program class C PayrollT Time Management

û

Country grouping *, 01, 02, ... 99

Executable schema

û

Person responsible

Changes by person responsible only

Created onLast changed byVersion

___

on _ at _

Schema Attributes

n Attributes store administrative data on schemas.

n The program class determines how the schema is used (C = Payroll, T = Time Management).

n The HR country grouping defines the country versions for which the schema is valid.

n If you flag Changes by person responsible only, the schema elements (source text, attributes, documentation) can only be changed by the person responsible for them.

n You do not require special authorization to generate a schema.

n A person other than the person responsible can execute a schema. Each function checks the authorizations set up in HR.

© SAP AG HR400 2-16

SAP AG 1999

The Schema Editor

000010000020000030000040000050

111

222 333 444 555 666

Fct Par1 Par2 Par3 Par4 D Text111 Command line

222 Line number

333 Function

444 Parameters 1 - 4

555 Execute function

666 Text

n In areas 1 and 2 of the editor, you can use the standard SAP commands.

n Area 3 of the editor specifies the schema's functions. The four parameters in area 4 provide more exact definitions of the functions.

n Placing an asterisk in area 5 deactivates the relevant function.

n You can enter a description of each function in area 6.

© SAP AG HR400 2-17

SAP AG 1999

Displaying Schemas as Structural Graphics


Basic dataInternational

XIN0

XBD0

+

-

Edit basic data

Edit basic data

COM

X000

-

ENAME

WPBP

P0052

GON

n To expand the sub-tree, click the plus sign, and to collapse the sub-tree, click the minus sign.

n If the function and parameter fields are not displayed in color, this indicates that the function has been deactivated.

n Where a function calls a personnel calculation rule, you can call the personnel calculation rule by double-clicking the name of the rule (in the first parameter field).

n Schemas can be viewed in structural graphics, but cannot be edited in this view.

© SAP AG HR400 2-18

SAP AG 1999

Functions and Personnel Calculation Rules

BLOCKCOM IMPRTPRINTPORTACTIOBLOCK

Import last payroll result Last payroll results Import last result Print ORT after import Transfer relevant data to LRT Processing /A67 Import last payroll result

ORTP06 NOAB

Personnel calculation rule X006

Operation Operation Operation

BEG

LNPX006X402END

ParametersCOM

COM

COM

COPY XIN0

COPY XBD0

COPY XLR0

COPY XT 00

…

...

Payroll schema: INTERNATIONAL

Gross wage calculation

and transfer


Edit basic data

Import last payroll result

Gross remuneration (Time Management)

n A schema consists of a sequence of functions . Functions retrieve and process the data required for each processing step.

n Certain functions call a personnel calculation rule . The relevant calculation rule processes the data retrieved by functions. A personnel calculation rule consists of separate operations and always processes logical units.

n Personnel calculation rules therefore fine-tune processes carried out by functions.

© SAP AG HR400 2-19

SAP AG 1999

Payroll Basics: Summary

l You are now familiar with the main processingsteps in Payroll.

l You have learned that the payroll program is controlled by functions in a process schema.

l You know that wage types are an essential part of payroll and that personnel calculationrules assist in processing wage types.

© SAP AG HR400 2-20

Exercise Data Sheet Key to Icons in the Exercises and Solutions

Exercises

Solutions

Objectives

Business Scenario

Hints and Tips

Warning or Caution

Data used in Exercises

Type of Data Data in Training System Data in EDES System

Payroll Area X1 – X9 (Groups 01 – 09) X0

Y0 – Y9 (Groups 10 – 19)

Wage Types:

Salary 10nn (nn = Group number)

Bad Weather Bonus 20nn Overtime up to 2 hours 3nn1

Overtime after 2 hours 3nn2

Overtime Sunday 3nn3

Overtime Public Holiday

3nn4

Bonus 25% 3nn5

Bonus 50% 3nn6

Bonus 75% 3nn7 Bonus 100% 3nn8

Vacation Bonus 40nn

Bonus 50nn

Instructor’s Bonus 60nn

© SAP AG HR400 2-21

Exercises

Unit: Payroll Basics

Topic: Hiring an Employee

• Hiring an employee.

1. Your employee enters the company on January 01 of the current year. Carry out the personnel action 'Hiring HR400' using the following data for the respective infotypes. You can skip infotypes for which no data is given.

Personnel number: 22nn (nn = group number.) Personnel area: CABB Employee grouping 1 Employee subgroup: X0

Infotype Organizational Assignment: Payroll area: X1 to X9 for groups 01 - 09, Y0 to Y9 for groups 10 - 19 Position: Default (Note: Cancel the position assignment)

Infotype Address: any data Infotype Working time: Work schedule rule: FLEX Time Management status: 0

Infotype Basic pay: Pay scale type: 01 Pay scale area: 01 Pay scale group: E03 Wage type: M020 (salary valuated indirectly)

In addition, create infotypes Bank details, Contract elements, and Absence quota (Type 09, validity period, current calendar).

2. Release payroll for the period 01, run payroll for your new employee and look at the results table.

© SAP AG HR400 2-22


Topics: Schema Editor, Main Schema, Subschemas

• Creating customer main and subschemas.

To adjust payroll to meet your company's requirements, you must modify the payroll schema. To do this, you copy and rename the original payroll schema, and make the changes required.

Make a copy of subschema XT00, and rename it ZTnn. Then make a copy of the international payroll schema X000, and rename it Z0nn (nn = group number).

© SAP AG HR400 2-23

Solutions


Topic: Hiring an Employee

1. Carry out the personnel action ‘Hiring HR400’: Human Resources à Personnel Management à Administration à HR Master Data → PA40 - Personnel Actions

2. Run payroll for your new employee: Human Resources à Payroll à International à Payroll à Release Payroll Human Resources à Payroll à International à Payroll à Start Payroll

© SAP AG HR400 2-24


Topics: Schema Editor, Main Schema, Subschemas

Copy subschema XT00 and schema X000: Human Resources à Payroll à International à Tools à Maintenance Tools à Schema à Copy

From schema XT00 To schema ZTnn

and

From schema X000 To schema Z000.

© SAP AG HR400 3-1

SAP AG 1999


l Employee Subgroup Groupings forPersonnel Calculation Rules

l Rule Access Variants

l Maintaining Personnel Calculation Rules

Contents:

© SAP AG HR400 3-2

SAP AG 1999

Personnel Calculation Rules: Unit Objectives


l Explain why personnel calculation rules mustprocess certain employee groupings differently.

l Describe how internal tables interact duringpayroll.

l Use various methods of accessing personnelcalculation rules from the schema.

l Maintain personnel calculation rules usingstructural graphics.

© SAP AG HR400 3-3

SAP AG 1999


Payroll Basics

Starting Payroll

Wage Type Valuation


Averages


Factoring

Absence Valuation Retroactive Accounting


© SAP AG HR400 3-4

SAP AG 1999

Employee Subgroup Groupings

Hourly wageearners

Salariedemployee

Period wage earner

Personnel calculation rule Xnnn

Rule: Xnnn EE subgroup grpg: 1 Wage type: ****



Operations

Operations

Operations

1

2

3

EE subgroupgroupingsfor personnelcalc.rule

n Personnel calculation rules for wage types are usually configured to perform various processes. For example, wage types for hourly wage earners are processed differently than wage types for monthly wage earners or salaried employees.

n To facilitate differential processing, each employee subgroup must be assigned to a grouping for a personnel calculation rule. Each grouping is defined by SAP and, in this case, can have its own area depending on the personnel calculation rule.

© SAP AG HR400 3-5

SAP AG 1999

Personnel Calculation Rules: Example 1



Hourly wage + bonuses per hour

= hourly rate for overtime


(Wage + bonuses) per period/ working hours per payroll period

= hourly rate for overtime

Calculation of hourly rate

n The hourly rate for overtime is subject to different methods of calculation (valuation basis) depending on whether the employee is a period wage earner, a salaried employee or an hourly wage earner.

n For employees with periodic remuneration, the hourly rate is calculated by dividing the remuneration elements by the number of working hours per period specified in the Basic Pay infotype.

© SAP AG HR400 3-6

SAP AG 1999

Personnel Calculation Rules: Example 2


Rule: Xnnn ES Grpg: * Wage type: nnn1

Factor = (Planned working time - unpaid absence)Period Working Time

Calculation of reduction factorfor absences

Rule: Xnnn ES grouping: * Wage type: nnn2

Factor = (Planned working time - unpaid absence - paid absence)Period Working Time

Factor 1

Factor 2

n Reduction factors are stored in diverse wage types and are used in payroll to calculate the reduction in pay for absences. A personnel calculation rule can contain several calculation formulas depending on the definition and use of the rule. Each formula is accessed exactly for the relevant wage type.

n The factors stored in the wage types are used to reduce periodic remuneration for unpaid absences, for example.

© SAP AG HR400 3-7

SAP AG 1999

Interaction Between the Most Important InternalPayroll Tables with Function PIT

Payroll rule

OPERATIONSINPUTTABLE- Wage types ----

RESULTTABLE

OUTPUTTABLE

n Internal table IT contains the wage types required for the relevant processing step.

n The results of a processing step are either stored in internal table OT or RT.

n Upon completion of a processing step, the wage types are transferred from internal table OT to internal table IT.

n Internal tables IT and OT are filled temporarily and only exist during the payroll run, whereas internal table RT is stored on the database.

© SAP AG HR400 3-8

SAP AG 1999

Rule Access Using Groupings


Rule: Xnnn EE subgroup grpg: 1 Wage type: ****Operations



Schema X000

3 M020 3,000

Table IT

…

PIT...

Xnnn GEN ____

n Function PIT (Process Input Table ) processes each wage type stored in internal table IT generically by accessing the personnel calculation rule defined in the first parameter through the employee subgroup grouping for personnel calculation rules.

n Example: The rule access is used in subschema XT00 to access personnel calculation rule X015.

© SAP AG HR400 3-9

SAP AG 1999

Generic Rule Access


Rule: Xnnn ES grouping: * Wage type: ****

Operations

Schema X000

3 M020 3,000

Table IT

…

PIT...

Xnnn GEN NOAB

n Function PIT (Process Input Table ) generically accesses the personnel calculation rule defined in the first parameter for each wage type stored in internal table IT When doing so, the employee subgroup grouping for personnel calculation rules in the wage type is not taken into account.

n Example: The rule access is used in subschema XEND to access personnel calculation rule X070.

© SAP AG HR400 3-10

SAP AG 1999

Rule Access Using Processing Classes

Schema X000

3 M020 3,000

Table IT

…

PIT...

Xnnn P01 ____



Rule: Xnnn EE subgroup grpg: 3 Wage type: ****Processing class 01?

0

1

2

Operations

Operations

Operations

Processing classspecification

01

02

03

M020

01235.........

n Function PIT (Process Input Table ) processes each wage type stored in internal table IT by reading the processing class defined in the second parameter and determining the specification of the processing class.

n Example: The rule access is used in subschema XT00 to access personnel calculation rule X013.

© SAP AG HR400 3-11

SAP AG 1999

Rule Access Using Wage Types

Schema X000

* nnn1* nnn2

Table IT

…

PIT...

Xnnn ____ NOAB


Rule: Xnnn ES Grpg: * Wage type: nnn1Operations

Rule: Xnnn ES grouping: * Wage type: nnn2Operations

Rule: Xnnn ES grouping : * Wage type: nnn3Operations

n Function PIT (Process Input Table ) processes each wage type stored in internal table IT by accessing the personnel calculation rule defined in the first parameter. When doing so, the employee subgroup grouping for personnel calculation rules in the wage type is not taken into account. If there is no processing for the wage type in the personnel calculation rule, the wage type is written to table OT without being changed.

n Example: In subschema XAL9, the personnel calculation rule XPPF is accessed in this way.

© SAP AG HR400 3-12

SAP AG 1999

Rule Access Variants

Parameter 3

Parameter 2

Parameter 1

Function

GEN Pnn

Rule

PIT

NOAB NOAB NOAB

n This overview show the six rule access variants. The four most common variants are marked.

n Further functions used to edit wage types stored in internal tables are PLRT, PORT, PDT, PRT, and PZL. The personnel calculation rules are accessed using the same parameters as function PIT.

n In parameter 2, you enter the type of rule access. The wage types to be processed can be specified using processing classes (Pnn). The rule can be accessed generically (GEN); that is, all the wage types in the table are processed in the payroll rule. If parameter 2 is empty, the personnel calculation rule is accessed for the wage type being processed.

n If you have not differentiated for employee subgroup groupings in a customer personnel calculation rule, you must call the rule using NOAB in parameter 3.

© SAP AG HR400 3-13

SAP AG 1999

Maintaining Personnel Calculation Rules

Create

Display Change

Rule

Source text

Attributes

Documentation

ES grouping

Wage/time type

n The personnel calculation rule editor enables you to display and maintain personnel calculation rules. You can access the editor under the Tools in the Payroll menu (transaction PE02).

n Personnel calculation rules are processed according to the employee subgroup grouping and the wage type.

© SAP AG HR400 3-14

SAP AG 1999

Rule Attributes

Administrative data

Attributes

Program class C PayrollT Time Management

Country grouping *, 01, 02, ... 99

û

Person responsible

Changes by person responsible only

Created onLast changed byVersion

___

on _ at _

n Personnel calculation rules are assigned by their attributes to a program class; that is, they are used either in Payroll or Time Management.

n The responsibility for maintenance can be assigned to an employee. In this case, all other employees are only able to display the rule.

n The administrative data tells you when the personnel calculation rule was created, the date and time when the last change was made, and the name of the person who made the last change.

© SAP AG HR400 3-15

SAP AG 1999

Displaying Rules as Structural Graphics

E VWTCL 06

E *

ERROR

0

E 1

ADDWTL *

E 2

LRTST Y

ADDWTL *

Import relevant wage types to LRTX006

*E

E ****

Employee subgroup grouping for personnel

calculation rule

Specificationof processing

class

WT

Processing class

Cancel processing

n Structural graphics display the source text as lines and nodes linked in a hierarchical structure. You can display and change source text in this mode.

n The source text elements and decision operations are color-coded. Decision operations are displayed in a color different to the one used for the other operations.

© SAP AG HR400 3-16

SAP AG 1999

Personnel Calculation Rules: Summary

l Personnel calculation rules enable you toprocess wage types according to employeegroupings and wage types.

l There are different ways of accessingpersonnel calculation rules within a schemato select the required processing.

© SAP AG HR400 3-17

Exercises

Unit: Personnel Calculation Rules

Topic: Functions for Processing Internal Payroll Tables

• Practicing various methods of accessing customer personnel calculation rules.

To adjust payroll to meet your company's requirements, you will usually require customer-specific personnel calculation rules to edit wage types in diverse payroll tables. Note: This exercise does not require you to carry out any activities in the system. Write the name of the access on this page.

1. You want to process table IT using personnel calculation rule Z001. You should access the rule by means of the employee subgroup grouping for personnel calculation rules, and not by means of the wage type.

___________ ___________ ___________ ___________

2. You want to process table ORT using personnel calculation rule ZORT. You should access the rule by means of the wage type, and not by means of the employee subgroup grouping for personnel calculation rules.

___________ ___________ ___________ ___________

3. You want to process table IT using personnel calculation rule Z010. You should access the rule by means of the employee subgroup grouping for personnel calculation rules, and the specification in processing class 99.

___________ ___________ ___________ ___________

4. You want to process table RT using personnel calculation rule ZEND. You should access the rule without using the wage type or the employee subgroup grouping for personnel calculation rules.

___________ ___________ ___________ ___________

5. You only want to process wage type 4711 in table IT in the same way for all employees using personnel calculation rule Z123.

___________ ___________ ___________ ___________

© SAP AG HR400 3-18


Topic: Creating Personnel Calculation Rules

• Creating customer personnel calculation rules, and accessing the rules from the schema.

To adjust payroll to meet your company's requirements, you will usually require customer personnel calculation rules to edit wage types in diverse payroll tables. To access these rules, you must adjust the schema accordingly.

1. Make a copy of personnel calculation rule XMOD, and rename your copy ZMnn. In subschema ZTnn, go to function MOD and change parameter 1 so that personnel calculation rule ZMnn is accessed.

2. Change your international payroll schema Z0nn so that it copies the modified subschema ZTnn instead of the standard schema XT00. Check the schema. If it contains no errors, save it .

© SAP AG HR400 3-19

Solutions


Topic: Functions for Processing Internal Payroll Tables

Access: PIT Z001 GEN

Access: PORT ZORT ___ NOAB

Access: PIT Z010 P99

Access: PRT ZEND GEN NOAB

Access: PIT Z123 ___ NOAB

© SAP AG HR400 3-20


Topic: Creating Personnel Calculation Rules

1. To copy personnel calculation rule XMOD, and change subschema ZTnn, go to: Human Resources à Payroll à International à Tools à Maintenance Tools à Calculation Rule à Copy

from rule XMOD to rule ZMnn.

2. Change payroll schema Z0nn: Human Resources à Payroll à International à Tools à Maintenance Tools à Schema. In your payroll schema Z0nn, change the line in which the partial schema XT00 is copied to ZTnn.

© SAP AG HR400 4-1

SAP AG 1999

Starting Payroll

l Initializing Payroll

l Checking the Personnel Control Record

l Importing Basic Data

l Work Center and Basic Pay Data

l WPBP Splits

l Data Completeness

Contents:

© SAP AG HR400 4-2

SAP AG 1999

Starting Payroll: Unit Objectives


l Set the parameters for initializing the payrollrun in your live schema.

l Define the work center and basic pay data set up at the start of payroll.

© SAP AG HR400 4-3

SAP AG 1999

Payroll Basics

Starting Payroll


Wage Type Valuation


Averages


Factoring



© SAP AG HR400 4-4

SAP AG 1999

COMBLOCKPGMUPDOPTOPTCHECKBLOCK

Initialisierung INTERNATIONAL Initialisierung der Abrechnung Programmtyp Abrechnung Datenbankupdates durchführen (YES/NO)nur verwendete Infotypen lesenalle Zeitinfotypen lesenPrüfung gegen PA03Initialisierung der Abrechnung

BEGABRYESINFTTIME ABR ABR *END

*

Abrechnungsschema: INTERNATIONALE Bruttolohnfindung undÜberweisung

Initialisierung AbrechnungXIN0

COMBLOCKPGMUPDOPTOPTCHECKBLOCK

Initialization INTERNATIONAL Initialization of Payroll Program type for payroll Update database (YES/NO)Read used infotypes onlyImport all time infotypesCheck against PA03Initialization of Payroll

BEGABRYESINFTTIMEABR *END

XIN0

Payroll schema: INTERNATIONAL Gross wage calculationand transferInitialization of payroll

Initializing Payroll

n At the start of the payroll run, subschema XIN0 provides the payroll driver with the data required to run the payroll program.

n Function PGM provides the payroll driver with data on the type of program the schema uses. The different schemas allow the payroll driver to execute the functions of diverse programs run at various times during processing. To execute the payroll program, the function must be set to parameter ABR.

n Function UPD controls whether the payroll results are updated on the database or only available during the payroll run. If the payroll driver has been set to test run, function UPD will not update the database even when set to YES.

n Function OPT set to the parameter INFT ensures that only the infotypes required in the functions within the schema are imported. The parameter TIME enables all time infotypes to be imported. This function is designed to enhance performance.

© SAP AG HR400 4-5

SAP AG 1999

Checking the Personnel Control Record

Abrechnungsschema:

XIN0

Control record

Released for payroll

Released for correction

Exit payroll

Check payroll results

Payroll period 10.1998Run 01

XIN0..CHECK ABR.

Initialization INTERNATIONAL

Check against PA03

n Function CHECK set to parameter ABR ensures that:

• Payroll is only run for the employees in a payroll area that has been released for payroll.

• Payroll is not run for any employees with payroll results relating to the future.

n In a live payroll schema, function CHECK ABR must be activated. The function is deactivated by setting the program to test run.

© SAP AG HR400 4-6

SAP AG 1999

Importing Basic Data

COMBLOCKENAMEWPBPGONBLOCK

Basic data INTERNATIONALEdit basic dataDetermine name of EERead work center/basic pay dataContinue if data completeEdit basic data

BEG

END

INTERNATIONAL Gross wage calculationand transfer


Edit basic data


Gross remuneration (Time Management)




Retroactive Accounting

Net payments/deductions and transfer

Final processing

XIN0

XBD0

XLR0

XT 00

XAP9

XAL9

XNA9

XRR0

XNN0

XEND

n Schema XBD0 is a subschema used to read the basic data that is essential to payroll.

© SAP AG HR400 4-7

SAP AG 1999

Reading Work Center / Basic Pay Data

IT 0000

PersonnelActions

IT 0001

Org.Assignment

IT 0007

PlannedWorkingTime

IT 0008

Basic Pay

IT 0027

CostDistribution

WPBP

M020 01 3,000.-

...

...

01 01.JUL.1999 31.JUL.1999

Table ITTable WPBP

ActionPersonnel areaWork schedule rule

Hiring1000NORM

n Function WPBP fills internal table WPBP with the master data, work center data and basic pay data valid for the payroll period.

n Function WPBP also fills internal table IT with the basic pay wage types.

n This data usually remains the same for the entire payroll period.

© SAP AG HR400 4-8

SAP AG 1999

WPBP Splits

WPBP

IT 0000

Personnel Actions01.JUL.1991 - 15.JUL.199916.JUL.1999 - 31.DEC.9999

IT 0007

Planned Working Time01.JUL.1999 - 20.JUL.199921.JUL.1999 - 31.DEC.9999

IT 0008

Basic Pay01.JUL.1999 -15.JUL.199916.JUL.1999 - 31.DEC.9999

M020 01 3,000.-

M020 02 3,500.-

M020 03 3,500.-

...

...

01 01.JUL.1999 15.JUL.1999

Table ITTable WPBP

ActionPersonnel areaWork schedule rule

Hiring1000NORM

02 16.JUL.1999 20.JUL.1999Action Change in pay

03 21.JUL.1999 31.JUL.2000Work schedule rule FLEX

n Various partial periods can contain different data. Where this is the case, the different entries are assigned a split indicator in internal tables WPBP and IT.

n In this example, a new employee's basic pay and planned working time have been changed during the payroll period. The system creates an entry in table WPBP for each partial period of the payroll period.

n Similarly, table IT contains three entries for the same wage type except that the second and third partial periods each specify the same amount.

© SAP AG HR400 4-9

SAP AG 1999

Data Completeness

GON Is all the datacomplete?

Payroll

n Function GON checks whether all the master data has been imported. Further processing of the personnel calculation schema only occurs if certain data is available. Checking procedures vary from country to country. However, there must always be a work center (IT 0007).

© SAP AG HR400 4-10

SAP AG 1999

Starting Payroll: Summary

l In a live schema, you must activate the checking procedure for the personnelcontrol record.

lWork center and basic pay data for thepayroll period are stored in tables IT andWPBP according to partial periods.

© SAP AG HR400 4-11

Exercises

Unit: Starting Payroll

Topic: WPBP Splits

• Recognizing WPBP splits in the payroll results.

You have already hired and run payroll for your employee.

1. Release your payroll area for correction.

2. Midway through the payroll period, your employee receives a bonus in basic pay. In the Basic Pay infotype, create a new record specifying wage type 50nn, and a bonus amount of 300.00.

Release the payroll for payroll period 01, run payroll for your employee using payroll schema Z0nn (nn = group number), and view the results in the results table. Exit the payroll run.

Create a selection variant for the payroll driver to ensure that the your schema Z0nn is used when you run payroll in the following exercises.

© SAP AG HR400 4-12

Solutions

Unit: Starting Payroll

Topic: WPBP Splits

1. To release the payroll area for correction, choose: Human Resources à Payroll à International à Payroll à Corrections

2. To assign a bonus and run payroll again for your employee, choose: Human Resources à Personnel Management à Administration à Maintain Master Data

Human Resources à Payroll à International à Release Payroll Human Resources à Payroll à International à Start Payroll Human Resources à Payroll à International à Payroll à Exit Payroll

Create selection variant for RPCALCX0: Human Resources à Payroll à International à Payroll à Start payroll à Goto à Variants à Save As Variant

© SAP AG HR400 5-1

SAP AG 1999

Wage Type Valuation

l Wage Type-Dependent Constants

l Pay Scale-Dependent Constants

l Modifiers for Table Access

l Person-Related Valuation Bases

l Personnel Calculation Rules X010 and X013

l Assigning Valuation Bases

l Derived Wage Types

l Valuating Wage Types in the Schema

Contents:

© SAP AG HR400 5-2

SAP AG 1999

Wage Type Valuation: Unit Objectives


l Valuate time wage types with fixed amounts and, if necessary, according to organizational units

l Valuate time wage types according to theprovisions in your collective agreement

l Valuate time wage types using a value derivedfrom the employee’s basic pay data

© SAP AG HR400 5-3

SAP AG 1999

Payroll Basics

Starting Payroll


Wage Type Valuation


Averages


Factoring



© SAP AG HR400 5-4

SAP AG 1999

Valuating Time Wage Types

Time

sheet

n Overtime that is not recorded automatically, but entered on a time sheet, can be processed for payroll in two ways:

1. The employee's working times are added up and entered as employee remuneration information with certain wage types.

2. The exact days and hours of the employee's working times are recorded. This can occur manually in the Overtime infotype (2005). The system then selects the correct time wage types to be used in the payroll run.

n The system processes PDC (plant data collection/time evaluation data) automatically.

n In both cases, the wage types initially contain the number of hours overtime the employee has worked. This figure is specified in the number field (NUM) to be multiplied by a payable amount. Example: The amount (AMT) of a time wage type is calculated by multiplying the number (NUM) of time units by the valuation basis (RTE): RTE * NUM = AMT 17.70 * 10 hrs = 177.00 The valuation basis is defined in Customizing.

© SAP AG HR400 5-5

SAP AG 1999

Valuation: Constant Remuneration (1)

l The Caliber ‘A’ Bicycle Company pays a constanthourly rate that is the same for all employees.

© SAP AG HR400 5-6

SAP AG 1999

Wage Type-Dependent Constants (1)

Bad weather bonus

WType

01.JAN.199701.JAN.199901.JAN.1998

Start date End date Amount

…400040005000...

31.DEC.199831.DEC.999931.DEC.9999

10.0012.0020.00

n In payroll, a wage type can be valuated using a constant amount. The amount does not depend on the employee's organizational assignment or on any other characteristics.

n Each wage type can have several entries denoting various validity periods.

© SAP AG HR400 5-7

SAP AG 1999


l The Caliber ‘A’ Bicycle Company pays an hourly bonus that is based on the employee’s assignment to a pay scale level.

© SAP AG HR400 5-8

SAP AG 1999

Pay Scale-Dependent Constants

Night work bonus

CollectiveAgreement- Hourly earners

- Monthly earners

- Salaried staff

EE SGGrpg

01.JAN.199801.JAN.1998

Start date

GR04GR04

31.DEC.200031.DEC.2000

10.0012.00

Pay scalegroup

PSlevel

WType End date Amount

…33...

0102

40104010

Entries per: - Pay scale type- Pay scale area

n If wage types are subject to constant valuation depending on their pay scale level assignment, you must define the values for each pay scale level assignment and wage type.

n Note the various employee subgroup groupings for collective agreement provisions specified when the employee subgroups are defined.

© SAP AG HR400 5-9

SAP AG 1999


l The Caliber ‘A’ Bicycle Company pays an hourlybonus that varies depending on thepersonnel area.

© SAP AG HR400 5-10

SAP AG 1999

Modifiers for Table Access

Personnel area 1000

Personnel area 1100

01 4000

01 5000

..

02 4000

02 5000

..

Key Amount

10.00

20.00

15.00

22.00

Payroll

01

02

n Elements of remuneration, such as bonuses, usually vary depending on the organizational unit.

n Example : You want bonus wage type 4000 to be remunerated differently for employees in personnel area 1000 than for employees in personnel area 1100. To do this, the system uses a modifier as the first key specified in the table. The default SAP value for modifiers is 01. The modifier for personnel area 1100 is created in Customizing by copying modifier 01, renaming it 02, and entering the relevant amount. During the payroll run, the system sets the modifier to the required value according to the personnel area assigned to each personnel number.

© SAP AG HR400 5-11

SAP AG 1999

Personnel Calculation Rule XMOD

E OUTWPPLANT

E 1000

MODIF A = 01

Employee grouping for payrollXMOD

E ****

MODIF 1 = 01

MODIF 2 = 01

MODIF A = 02

MODIF 1 = 02

MODIF 2 = 02

E 1100

3E UsingUsing ES ES grouping grouping 3 wage/ 3 wage/time type **** astime type **** as an an example example

Personnel area

Table Absence valuation

Table Wage type selection rule

Table Constant wage type valuation

n In the payroll run, function MOD centrally assigns the modifiers described on the previous page using personnel calculation rule XMOD.

n Decision operation OUTWP uses various parameters to define an employee's organizational characteristics such as the company code and personnel area. Operation MODIF sets the modifiers for table access. The parameters used for operation MODIF represent various tables.

© SAP AG HR400 5-12

SAP AG 1999


Dirty work bonus Personnel area 1000 Personnel area 1100

PayMo

01.01.199801.01.1998


…0102...

31.12.200031.12.2000

10.0015.00

WType

40004000

n This represents a complete view of the table Wage type -dependent constants . If, as described in the first scenario, the values are all the same, you can use the model SAP entries in the standard system which have the payroll modifier (MODIF 2) set to value 01.

© SAP AG HR400 5-13

SAP AG 1999

Valuating Wage Types in the Schema (1)

XT00....MOD XMOD GEN.P2010 X930 GEN NOAB..PIT X015 GEN..

General processing of time data INTERN.

Determine payroll modifiers

Edit employee remuneration information

Valuation of time wage types

n In subschema XT00, personnel calculation rule XMOD queries employee work center data and sets modifiers that access the table for wage type-dependent constants.

n Function P2010 imports the bonuses for dirty work entered as employee remuneration information. The wage types are then stored in internal table IT with the number of hours specified in the NUM field. The RTE field remains empty.

n Valuation is performed in personnel calculation rule X015, which checks whether internal table IT contains time wage types. If time wage types are found in table IT, the system performs the valuation set up in Customizing.

© SAP AG HR400 5-14

SAP AG 1999

Valuation: Person-Related Remuneration (1)

l The Caliber ‘A’ Bicycle Company paysovertime according to an employee’spersonal hourly rate.

© SAP AG HR400 5-15

SAP AG 1999

Person-Related Valuation Bases

6,000 3,000Total pay

34.09 34.09

Standard salaryStandard bonusVoluntary bonus

6,000

500

yesyesno

2,700300

Divided by working hours per period (IT0008)176 Hours 88 Hours

The valuation basis is calculated using a basic pay wage type:

n The basis that is used to valuate person-related valuation bases is not a fixed constant, but an employee-specific value calculated according to the employee's remuneration.

n The system flags the wage types used to calculate person-related valuation bases.

© SAP AG HR400 5-16

SAP AG 1999

Processing in Rule X010

Table IT

3 M020

3 M230

2,700

300

Table OT

3 M020

3 M230

3 /001

2,700

300

3,000

Input Processing in X010 Output

Amounts totaled

in wage types /0nn

n Personnel calculation rule X010 queries processing class 01 for the basic pay wage types in internal table IT. The specification of processing class 01 determines in which valuation basis the wage type is cumulated.

© SAP AG HR400 5-17

SAP AG 1999


Table IT

3 M020

3 M230

3 /001

2,700

300

3,000

Table OT

3 M020

3 M230

3 /001

2,700

300

34.09


Divided by working

hours per payroll

period

n The valuation bases for employees who are not paid by the hour are divided by the flat-rate number of hours in a period. This results in an hourly rate that is stored in the rate field (RTE) for wage types /001 and /002.

© SAP AG HR400 5-18

SAP AG 1999

Personnel Calculation Rule X010

E VWTCL 01

E *

ERROR

Determination of valuation bases ADDITIONX010

E ****

ADDWT *

E 0


ADDWT *

E 1

ELIMI Z

ZERO=N

ADDWT /001

Processing class 01

Cancel processing

Transfer wage type to output table OT


Eliminate time period ID

Set NUM field = 0

Transfer wage type as /001 to table OT

n ADDWT

Add wage type to subsequent wage type

• Task: The wage type being processed is transferred to internal table OT.

• Input: Wage types that are in the header of the input table (work area) during processing.

• Processing: The values of the wage type in the current work area are added to the subsequent wage type. You can also rename the wage type.

n ELIMI

Eliminate period indicators

• This operation removes the time unit indicator (split indicator) for the wage type in the current work area. This prepares the way for combining the values stored in wage types that up to this point were distinct.

n ZERO

Initializes the current work areas

© SAP AG HR400 5-19

SAP AG 1999


E VWTCL 01

E *

ADDWT *

Division of valuation basesX013

E ****

RTE=TSDIVP

DIVID ARR

E 5


ZERO=A

ADDWT *

Processing class 01


Transfer working hours per period to RTE

Divide AMT/RTE, transfer result to RTE

Set AMT field = 0


n RTE

Calculations in the current rate field (RTE)

• Task: Change value or query RTE field.


• Processing: Depending on the operator specified, this operation can be an action or a decision operation. In this case, the work hours per period from the Basic Pay infotype are stored in the Rate field.

n DIVID

Divide

• Task: This operation divides two fields in the current entry and places the result in another field.

• Processing: This operation processes the following fields of the current entry in table OT: NUM (number field), RTE (amount/unit = rate field), and AMT (amount field). Each of these fields can be divided by any other, and the result can also be stored in any of the fields.

© SAP AG HR400 5-20

SAP AG 1999

Creating Person-Related Valuation Bases

WType

Processing class

Specification

M010 Standard salary

1 Assignment to valuation bases

1 Wage type included in /001

n All wage types entered in the Basic Pay (0008) infotype must be assigned to processing class 1. The specification of this processing class determines the valuation bases used for the wage types (secondary wage types /0..).

© SAP AG HR400 5-21

SAP AG 1999

Assigning Valuation Bases (1)

WT M110 Overtime hours Start End

Current wage typeValuation basis 01 % rate 100.00StatementWTStatementWT

Input options:K = Wage-dependent constant TS = Pay scale-dependent constantTG = Pay-scale dependent constant without PS levelT = Pay scale-dependent constant without level and group01 = /00102 = /002 etc. ' ‘ = No valuation

n Example: Wage type M110 was entered as employee remuneration information specifying 5 hours. Line a) shows the wage type in table IT after the employee remuneration information was imported, and line b) shows the wage type after valuation using the valuation basis specified in Customizing:

RTE NUM AMT ------------------------------------------------------------------------------------------------------- a) Before valuation M110 5 b) After valuation M110 14.10 5 70.50

© SAP AG HR400 5-22

SAP AG 1999

l The Caliber ‘A’ Bicycle Company paysovertime according to the employee’spersonal hourly rate and bonus.


© SAP AG HR400 5-23

SAP AG 1999



Current wage typeValuation basis 01 % rateStatementWTStatementWT

1st derived wage typeValuation basis 01 % rateStatementWTStatementWT M111

100.00

25.00

2nd derived wage typeValuation basis % rate StatementWTStatementWT

n The first and second derived wage types enable you to define bonus wage types for which remuneration is calculated when an employee's current wage type is valuated in payroll.

n You can determine whether remuneration is calculated for the current wage type by specifying a valuation basis in the appropriate line.

Example: RTE NUM AMT ----------------------------------------------------------------------------------------------- a) Before valuation M110 5 b) After valuation M110 14.10 5 70.50 M111 3.52 5 17.60

© SAP AG HR400 5-24

SAP AG 1999


XT00..PIT X010 P01PIT X013 P01MOD XMOD GEN.P2010 X930 GEN NOAB..PIT X015 GEN..


Create valuation bases (addition)Create valuation bases (division)Determine payroll modifiers



n Subschema XT00 (General processing of time data) calls personnel calculation rule X010, which queries processing class 01 for basic pay wage types in internal table IT. The specification in processing class 01 determines whether the wage type is transferred to secondary wage types that are used to create the valuation bases.

n Subschema XT00 then calls personnel calculation rule X013. The values for employees not paid by the hour are divided by the flat-rate number of hours in a period. This results in an amount per working hour that is entered as the valuation basis in the rate field (RTE) for wage types /001 and /002.

© SAP AG HR400 5-25

SAP AG 1999

Types of Valuation Bases

1) Valuation bases that are entered in a table as:

- constants dependent on wage types, or

- constants dependent on a collective agreement

2) Valuation bases calculated for specific persons using basic pay data

n Valuation bases can also be determined using the average values for remuneration elements from previous payroll periods. These valuation bases will be covered later in the course.

© SAP AG HR400 5-26

SAP AG 1999

Wage Type Valuation: Summary (1)

l Time wage types used in payroll initially specify the number of hours of overtimein the NUM field. The amount per time unit needed to calculate remuneration is included in payroll through the valuation basis.

l A time wage type can be valuated using the same amount for all employees or amounts that vary according to organizational characteristics.

© SAP AG HR400 5-27

SAP AG 1999


l A time wage type can be valuated according to the employee’s assignment to a pay scalelevel.

l A time wage type can also be valuated usingthe hourly rate calculated for each individual employee.

© SAP AG HR400 5-28

Exercises

Unit: Wage Type Valuation

Topic: Creating Constant Valuation Bases

• Adjusting personnel calculation rule XMOD to meet customer requirements.

• Creating a constant valuation basis for a wage type.

You company pays time wage types with amounts that vary depending on the employee's organizational assignment. These time wage types include a bad weather bonus of 1.25 per hour. If the weather is bad, the wage type is entered as employee remuneration information.

1. In personnel calculation rule ZMnn (nn = group number), set MODIF 2 to value xx for the table Constant Wage Type Valuation for employee subgroup grouping 3. Call up the table Constant Wage Type Valuation, and make an entry under the payroll modifier xx (xx = 50 + group number) for wage type 20nn Bad weather bonus in the amount of 1.25 (starting January 1st of the current year).

2. Assign employee remuneration information to your employee for payroll period 02 using wage type 20nn for 10 hours. Run the payroll for the payroll period. Ensure that the date of the remuneration information is within the payroll period. To run payroll, use your selection variant.

© SAP AG HR400 5-29


Topic: Creating Person-Related Valuation Bases

• Copy model wage types to customer wage types.

• Check processing class 1 for customer-specific wage types.

Your company pays time wage types that are valuated using the employee's hourly rate. To calculate the hourly rate, you must encode all the wage types to be included in the calculation in processing class 1.

1. Make a copy of wage type M020, and rename it 10nn Salary (nn = group number) using the wage type copying function in the Implementation Guide (transaction PU30).

2. Encode wage type 10nn in the IMG so that it is included in valuation bases /001 and /002.

3. Enable correction entry in your payroll area and change your employee's basic pay from wage type M020 to wage type 10nn (change without delimitation), and run the payroll for payroll period 02. Check that the valuation bases have been created.

© SAP AG HR400 5-30


Topic: Assigning Valuation Bases/Derived Wage Types

• Valuating time wage types using an employee's hourly rate.

• Creating derived wage types for bonuses.

Your company pays various bonuses for overtime. For the first two hours overtime in a day, the employee receives a 25% bonus. For each additional hour, the employee receives a 50% bonus. Overtime on Sundays is remunerated by a 75% bonus, and overtime on public holidays by a 100% bonus. Basic overtime is also subject to remuneration.

1. You require time wage types for overtime remuneration. These wage types are to be entered as employee remuneration information, and an entry is only made in the fields Number/unit (which represents the number of hours in this instance). The wage types must be valuated with the employee's hourly rate, which is contained in the valuation basis /001. You require the following wage types, and you want to specify the bonus in the statement wage types:

- 3nn1 Up to 2 hours overtime derived:3nn5 25% bonus

- 3nn2 Starting 3 hours overtime derived:3nn6 50% bonus

- 3nn3 Overtime on Sundays derived:3nn7 75% bonus

- 3nn4 Overtime on public holidays 3nn8 100% bonus

Copy wage type M110 eight times using the wage type copying function

2. Encode the valuation bases for the wage types 3nn1 to 3nn4.

3. Check your wage types by assigning employee remuneration information (pay attention to the date) to your employee in payroll period 02, and specifying 10 hours for each of the wage types 3nn1, 3nn2, 3nn3, and 3nn4. Run the payroll for period 02. Then exit the payroll run.

© SAP AG HR400 5-31

Solutions



1. In the rule ZMnn, set MODIF 2 to the value xx, and make an entry in the table ”Constant Wage Type Valuation”. IMG à Payroll International à Time Wage Type Valuation à Valuation Bases à Constant Valuation Bases à Define Wage Type-Dependent Constants

In the dialog box, choose the activity Set modifier for constant valuation.

Note: The IMG enables you to edit personnel calculation rule XMOD. Note that you do not have to perform the activity Enter modified personnel calculation rule in schema since you have already created rule ZMnn, and included the rule in schema Z0nn (nn = group number). Choose the activity Determine Constant Valuation Per Wage Type Make the following entries in the table: Modifier: xx Wage type: 20nn Start date: January 1st of the current year End date: December 31st, 9999 Value: 1.25

2. To enter 10 hours for wage type 20nn and run the payroll, go to:

Human Resources à Personnel Management à Administration à Maintain Master Data Choose the infotype Employee Remuneration Information, and create a record specifying wage type 20nn and 10 (hours) in the field Number/unit. Go to:

Human Resources à Payroll à International à Payroll à Release Payroll Human Resources à Payroll à International à Payroll à Start Payroll Human Resources à Payroll à International à Payroll à Corrections

© SAP AG HR400 5-32



1. To make a copy of wage type M020 and rename it 10nn using the wage type copying function, go to

IMG à Personnel Management à Personnel Administration à Payroll Data à Basic Pay à Wage Types à Create Wage Type Catalog

Choose Copy, flag the wage type M020, copy and rename it 10nn "Salary".

2. To encode wage type 10nn in processing class 1, go to:

IMG à Payroll: International à Time Wage Type Evaluation à Valuation Bases à Create Person-Related Valuation Bases à Maintain Basic Pay for Valuation Bases

Flag the wage type and choose Details. Display the specifications for processing class 1, and choose specification 3. Do not forget to save the setting you have made.

3. To change your employee's basic pay from wage type M020 to 10nn, go to:

Human resources à Payroll à International à Payroll à Corrections Human Resources à Personnel Management à Administration à Maintain Master Data

To run the payroll for the payroll period and check whether the valuation bases have been created, go to:

Human Resources à Payroll à International à Payroll à Release Payroll Human Resources à Payroll à International à Payroll à Start Payroll

Check whether wage types /001 and /002 have been included in table IT (after rule X013 has been processed) of the payroll log.

© SAP AG HR400 5-33



1. To copy time wage types to remunerate overtime, go to:

IMG à Personnel Management à Personnel Administration à Payroll Data à Employee Remuneration Data à Wage Types à Create Wage Type Catalog

Choose Copy, and enter the original wage type M110 and the Customizing wage type 3nn1.

Choose Make copies of wage type, and enter the following information:

- Wage type starts at 3nn1 - Number of wage types 8 - Increase for each step 1

2. To encode the valuation bases of wage types 3nn1 - 3nn4, go to:

IMG à Payroll: International à Time Wage Type Valuation à Valuation Bases à Assign Valuation Bases.

Valuate your wage types with the valuation basis 01 to 100% and make the following entries for the first derived wage type.

WT Val. Bases Statement WT Percent.

3nn1 01 3nn5 25 3nn2 01 3nn6 50 3nn3 01 3nn7 75 3nn4 01 3nn8 100

© SAP AG HR400 5-34

3. To set up and run the payroll program for employee remuneration information, go to: Human Resources à Payroll à International à Payroll à Corrections

Human Resources à Personnel Management à Administration à Maintain Master Data à Time Mgmt Trans. Data à Create

Choose the infotype Employee remuneration information and for each entry create a record specifying wage types 3nn1 to 3nn4 and 10 (hours) in the field Number/unit.

Human Resources à Payroll à International à Payroll à Start Payroll Human Resources à Payroll à International à Payroll à Exit Payroll

© SAP AG HR400 5-1

SAP AG 1999

Wage Type Valuation

l Wage Type-Dependent Constants

l Pay Scale-Dependent Constants

l Modifiers for Table Access

l Person-Related Valuation Bases

l Personnel Calculation Rules X010 and X013

l Assigning Valuation Bases

l Derived Wage Types

l Valuating Wage Types in the Schema

Contents:

© SAP AG HR400 5-2

SAP AG 1999

Wage Type Valuation: Unit Objectives


l Valuate time wage types with fixed amounts and, if necessary, according to organizational units

l Valuate time wage types according to theprovisions in your collective agreement

l Valuate time wage types using a value derivedfrom the employee’s basic pay data

© SAP AG HR400 5-3

SAP AG 1999

Payroll Basics

Starting Payroll


Wage Type Valuation


Averages


Factoring



© SAP AG HR400 5-4

SAP AG 1999


Time

sheet

n Overtime that is not recorded automatically, but entered on a time sheet, can be processed for payroll in two ways:

1. The employee's working times are added up and entered as employee remuneration information with certain wage types.

2. The exact days and hours of the employee's working times are recorded. This can occur manually in the Overtime infotype (2005). The system then selects the correct time wage types to be used in the payroll run.

n The system processes PDC (plant data collection/time evaluation data) automatically.

n In both cases, the wage types initially contain the number of hours overtime the employee has worked. This figure is specified in the number field (NUM) to be multiplied by a payable amount. Example: The amount (AMT) of a time wage type is calculated by multiplying the number (NUM) of time units by the valuation basis (RTE): RTE * NUM = AMT 17.70 * 10 hrs = 177.00 The valuation basis is defined in Customizing.

© SAP AG HR400 5-5

SAP AG 1999


l The Caliber ‘A’ Bicycle Company pays a constanthourly rate that is the same for all employees.

© SAP AG HR400 5-6

SAP AG 1999


Bad weather bonus

WType

01.JAN.199701.JAN.199901.JAN.1998


…400040005000...

31.DEC.199831.DEC.999931.DEC.9999

10.0012.0020.00

n In payroll, a wage type can be valuated using a constant amount. The amount does not depend on the employee's organizational assignment or on any other characteristics.

n Each wage type can have several entries denoting various validity periods.

© SAP AG HR400 5-7

SAP AG 1999


l The Caliber ‘A’ Bicycle Company pays an hourly bonus that is based on the employee’s assignment to a pay scale level.

© SAP AG HR400 5-8

SAP AG 1999

Pay Scale-Dependent Constants

Night work bonus

CollectiveAgreement- Hourly earners

- Monthly earners

- Salaried staff

EE SGGrpg

01.JAN.199801.JAN.1998

Start date

GR04GR04

31.DEC.200031.DEC.2000

10.0012.00

Pay scalegroup

PSlevel

WType End date Amount

…33...

0102

40104010

Entries per: - Pay scale type- Pay scale area

n If wage types are subject to constant valuation depending on their pay scale level assignment, you must define the values for each pay scale level assignment and wage type.

n Note the various employee subgroup groupings for collective agreement provisions specified when the employee subgroups are defined.

© SAP AG HR400 5-9

SAP AG 1999


l The Caliber ‘A’ Bicycle Company pays an hourlybonus that varies depending on thepersonnel area.

© SAP AG HR400 5-10

SAP AG 1999

Modifiers for Table Access

Personnel area 1000

Personnel area 1100

01 4000

01 5000

..

02 4000

02 5000

..

Key Amount

10.00

20.00

15.00

22.00

Payroll

01

02

n Elements of remuneration, such as bonuses, usually vary depending on the organizational unit.

n Example : You want bonus wage type 4000 to be remunerated differently for employees in personnel area 1000 than for employees in personnel area 1100. To do this, the system uses a modifier as the first key specified in the table. The default SAP value for modifiers is 01. The modifier for personnel area 1100 is created in Customizing by copying modifier 01, renaming it 02, and entering the relevant amount. During the payroll run, the system sets the modifier to the required value according to the personnel area assigned to each personnel number.

© SAP AG HR400 5-11

SAP AG 1999

Personnel Calculation Rule XMOD

E OUTWPPLANT

E 1000

MODIF A = 01


E ****

MODIF 1 = 01

MODIF 2 = 01

MODIF A = 02

MODIF 1 = 02

MODIF 2 = 02

E 1100


Personnel area


Table Wage type selection rule


n In the payroll run, function MOD centrally assigns the modifiers described on the previous page using personnel calculation rule XMOD.

n Decision operation OUTWP uses various parameters to define an employee's organizational characteristics such as the company code and personnel area. Operation MODIF sets the modifiers for table access. The parameters used for operation MODIF represent various tables.

© SAP AG HR400 5-12

SAP AG 1999


Dirty work bonus Personnel area 1000 Personnel area 1100

PayMo

01.01.199801.01.1998


…0102...

31.12.200031.12.2000

10.0015.00

WType

40004000

n This represents a complete view of the table Wage type -dependent constants . If, as described in the first scenario, the values are all the same, you can use the model SAP entries in the standard system which have the payroll modifier (MODIF 2) set to value 01.

© SAP AG HR400 5-13

SAP AG 1999


XT00....MOD XMOD GEN.P2010 X930 GEN NOAB..PIT X015 GEN..


Determine payroll modifiers



n In subschema XT00, personnel calculation rule XMOD queries employee work center data and sets modifiers that access the table for wage type-dependent constants.

n Function P2010 imports the bonuses for dirty work entered as employee remuneration information. The wage types are then stored in internal table IT with the number of hours specified in the NUM field. The RTE field remains empty.

n Valuation is performed in personnel calculation rule X015, which checks whether internal table IT contains time wage types. If time wage types are found in table IT, the system performs the valuation set up in Customizing.

© SAP AG HR400 5-14

SAP AG 1999


l The Caliber ‘A’ Bicycle Company paysovertime according to an employee’spersonal hourly rate.

© SAP AG HR400 5-15

SAP AG 1999

Person-Related Valuation Bases

6,000 3,000Total pay

34.09 34.09

Standard salaryStandard bonusVoluntary bonus

6,000

500

yesyesno

2,700300

Divided by working hours per period (IT0008)176 Hours 88 Hours

The valuation basis is calculated using a basic pay wage type:

n The basis that is used to valuate person-related valuation bases is not a fixed constant, but an employee-specific value calculated according to the employee's remuneration.

n The system flags the wage types used to calculate person-related valuation bases.

© SAP AG HR400 5-16

SAP AG 1999


Table IT

3 M020

3 M230

2,700

300

Table OT

3 M020

3 M230

3 /001

2,700

300

3,000


Amounts totaled

in wage types /0nn

n Personnel calculation rule X010 queries processing class 01 for the basic pay wage types in internal table IT. The specification of processing class 01 determines in which valuation basis the wage type is cumulated.

© SAP AG HR400 5-17

SAP AG 1999


Table IT

3 M020

3 M230

3 /001

2,700

300

3,000

Table OT

3 M020

3 M230

3 /001

2,700

300

34.09


Divided by working

hours per payroll

period

n The valuation bases for employees who are not paid by the hour are divided by the flat-rate number of hours in a period. This results in an hourly rate that is stored in the rate field (RTE) for wage types /001 and /002.

© SAP AG HR400 5-18

SAP AG 1999


E VWTCL 01

E *

ERROR

Determination of valuation bases ADDITIONX010

E ****

ADDWT *

E 0


ADDWT *

E 1

ELIMI Z

ZERO=N

ADDWT /001

Processing class 01

Cancel processing



Eliminate time period ID

Set NUM field = 0

Transfer wage type as /001 to table OT

n ADDWT


• Task: The wage type being processed is transferred to internal table OT.


• Processing: The values of the wage type in the current work area are added to the subsequent wage type. You can also rename the wage type.

n ELIMI

Eliminate period indicators

• This operation removes the time unit indicator (split indicator) for the wage type in the current work area. This prepares the way for combining the values stored in wage types that up to this point were distinct.

n ZERO

Initializes the current work areas

© SAP AG HR400 5-19

SAP AG 1999


E VWTCL 01

E *

ADDWT *

Division of valuation basesX013

E ****

RTE=TSDIVP

DIVID ARR

E 5


ZERO=A

ADDWT *

Processing class 01


Transfer working hours per period to RTE

Divide AMT/RTE, transfer result to RTE

Set AMT field = 0


n RTE

Calculations in the current rate field (RTE)

• Task: Change value or query RTE field.


• Processing: Depending on the operator specified, this operation can be an action or a decision operation. In this case, the work hours per period from the Basic Pay infotype are stored in the Rate field.

n DIVID

Divide

• Task: This operation divides two fields in the current entry and places the result in another field.

• Processing: This operation processes the following fields of the current entry in table OT: NUM (number field), RTE (amount/unit = rate field), and AMT (amount field). Each of these fields can be divided by any other, and the result can also be stored in any of the fields.

© SAP AG HR400 5-20

SAP AG 1999

Creating Person-Related Valuation Bases

WType

Processing class

Specification

M010 Standard salary

1 Assignment to valuation bases

1 Wage type included in /001

n All wage types entered in the Basic Pay (0008) infotype must be assigned to processing class 1. The specification of this processing class determines the valuation bases used for the wage types (secondary wage types /0..).

© SAP AG HR400 5-21

SAP AG 1999



Current wage typeValuation basis 01 % rate 100.00StatementWTStatementWT

Input options:K = Wage-dependent constant TS = Pay scale-dependent constantTG = Pay-scale dependent constant without PS levelT = Pay scale-dependent constant without level and group01 = /00102 = /002 etc. ' ‘ = No valuation

n Example: Wage type M110 was entered as employee remuneration information specifying 5 hours. Line a) shows the wage type in table IT after the employee remuneration information was imported, and line b) shows the wage type after valuation using the valuation basis specified in Customizing:

RTE NUM AMT ------------------------------------------------------------------------------------------------------- a) Before valuation M110 5 b) After valuation M110 14.10 5 70.50

© SAP AG HR400 5-22

SAP AG 1999

l The Caliber ‘A’ Bicycle Company paysovertime according to the employee’spersonal hourly rate and bonus.


© SAP AG HR400 5-23

SAP AG 1999



Current wage typeValuation basis 01 % rateStatementWTStatementWT

1st derived wage typeValuation basis 01 % rateStatementWTStatementWT M111

100.00

25.00

2nd derived wage typeValuation basis % rate StatementWTStatementWT

n The first and second derived wage types enable you to define bonus wage types for which remuneration is calculated when an employee's current wage type is valuated in payroll.

n You can determine whether remuneration is calculated for the current wage type by specifying a valuation basis in the appropriate line.

Example: RTE NUM AMT ----------------------------------------------------------------------------------------------- a) Before valuation M110 5 b) After valuation M110 14.10 5 70.50 M111 3.52 5 17.60

© SAP AG HR400 5-24

SAP AG 1999


XT00..PIT X010 P01PIT X013 P01MOD XMOD GEN.P2010 X930 GEN NOAB..PIT X015 GEN..


Create valuation bases (addition)Create valuation bases (division)Determine payroll modifiers



n Subschema XT00 (General processing of time data) calls personnel calculation rule X010, which queries processing class 01 for basic pay wage types in internal table IT. The specification in processing class 01 determines whether the wage type is transferred to secondary wage types that are used to create the valuation bases.

n Subschema XT00 then calls personnel calculation rule X013. The values for employees not paid by the hour are divided by the flat-rate number of hours in a period. This results in an amount per working hour that is entered as the valuation basis in the rate field (RTE) for wage types /001 and /002.

© SAP AG HR400 5-25

SAP AG 1999

Types of Valuation Bases

1) Valuation bases that are entered in a table as:

- constants dependent on wage types, or

- constants dependent on a collective agreement

2) Valuation bases calculated for specific persons using basic pay data

n Valuation bases can also be determined using the average values for remuneration elements from previous payroll periods. These valuation bases will be covered later in the course.

© SAP AG HR400 5-26

SAP AG 1999


l Time wage types used in payroll initially specify the number of hours of overtimein the NUM field. The amount per time unit needed to calculate remuneration is included in payroll through the valuation basis.

l A time wage type can be valuated using the same amount for all employees or amounts that vary according to organizational characteristics.

© SAP AG HR400 5-27

SAP AG 1999


l A time wage type can be valuated according to the employee’s assignment to a pay scalelevel.

l A time wage type can also be valuated usingthe hourly rate calculated for each individual employee.

© SAP AG HR400 5-28

Exercises




• Creating a constant valuation basis for a wage type.

You company pays time wage types with amounts that vary depending on the employee's organizational assignment. These time wage types include a bad weather bonus of 1.25 per hour. If the weather is bad, the wage type is entered as employee remuneration information.

1. In personnel calculation rule ZMnn (nn = group number), set MODIF 2 to value xx for the table Constant Wage Type Valuation for employee subgroup grouping 3. Call up the table Constant Wage Type Valuation, and make an entry under the payroll modifier xx (xx = 50 + group number) for wage type 20nn Bad weather bonus in the amount of 1.25 (starting January 1st of the current year).

2. Assign employee remuneration information to your employee for payroll period 02 using wage type 20nn for 10 hours. Run the payroll for the payroll period. Ensure that the date of the remuneration information is within the payroll period. To run payroll, use your selection variant.

© SAP AG HR400 5-29



• Copy model wage types to customer wage types.

• Check processing class 1 for customer-specific wage types.

Your company pays time wage types that are valuated using the employee's hourly rate. To calculate the hourly rate, you must encode all the wage types to be included in the calculation in processing class 1.

1. Make a copy of wage type M020, and rename it 10nn Salary (nn = group number) using the wage type copying function in the Implementation Guide (transaction PU30).

2. Encode wage type 10nn in the IMG so that it is included in valuation bases /001 and /002.

3. Enable correction entry in your payroll area and change your employee's basic pay from wage type M020 to wage type 10nn (change without delimitation), and run the payroll for payroll period 02. Check that the valuation bases have been created.

© SAP AG HR400 5-30



• Valuating time wage types using an employee's hourly rate.

• Creating derived wage types for bonuses.

Your company pays various bonuses for overtime. For the first two hours overtime in a day, the employee receives a 25% bonus. For each additional hour, the employee receives a 50% bonus. Overtime on Sundays is remunerated by a 75% bonus, and overtime on public holidays by a 100% bonus. Basic overtime is also subject to remuneration.

1. You require time wage types for overtime remuneration. These wage types are to be entered as employee remuneration information, and an entry is only made in the fields Number/unit (which represents the number of hours in this instance). The wage types must be valuated with the employee's hourly rate, which is contained in the valuation basis /001. You require the following wage types, and you want to specify the bonus in the statement wage types:

- 3nn1 Up to 2 hours overtime derived:3nn5 25% bonus

- 3nn2 Starting 3 hours overtime derived:3nn6 50% bonus

- 3nn3 Overtime on Sundays derived:3nn7 75% bonus

- 3nn4 Overtime on public holidays 3nn8 100% bonus

Copy wage type M110 eight times using the wage type copying function

2. Encode the valuation bases for the wage types 3nn1 to 3nn4.

3. Check your wage types by assigning employee remuneration information (pay attention to the date) to your employee in payroll period 02, and specifying 10 hours for each of the wage types 3nn1, 3nn2, 3nn3, and 3nn4. Run the payroll for period 02. Then exit the payroll run.

© SAP AG HR400 5-31

Solutions



1. In the rule ZMnn, set MODIF 2 to the value xx, and make an entry in the table ”Constant Wage Type Valuation”. IMG à Payroll International à Time Wage Type Valuation à Valuation Bases à Constant Valuation Bases à Define Wage Type-Dependent Constants

In the dialog box, choose the activity Set modifier for constant valuation.

Note: The IMG enables you to edit personnel calculation rule XMOD. Note that you do not have to perform the activity Enter modified personnel calculation rule in schema since you have already created rule ZMnn, and included the rule in schema Z0nn (nn = group number). Choose the activity Determine Constant Valuation Per Wage Type Make the following entries in the table: Modifier: xx Wage type: 20nn Start date: January 1st of the current year End date: December 31st, 9999 Value: 1.25

2. To enter 10 hours for wage type 20nn and run the payroll, go to:

Human Resources à Personnel Management à Administration à Maintain Master Data Choose the infotype Employee Remuneration Information, and create a record specifying wage type 20nn and 10 (hours) in the field Number/unit. Go to:

Human Resources à Payroll à International à Payroll à Release Payroll Human Resources à Payroll à International à Payroll à Start Payroll Human Resources à Payroll à International à Payroll à Corrections

© SAP AG HR400 5-32



1. To make a copy of wage type M020 and rename it 10nn using the wage type copying function, go to

IMG à Personnel Management à Personnel Administration à Payroll Data à Basic Pay à Wage Types à Create Wage Type Catalog

Choose Copy, flag the wage type M020, copy and rename it 10nn "Salary".

2. To encode wage type 10nn in processing class 1, go to:

IMG à Payroll: International à Time Wage Type Evaluation à Valuation Bases à Create Person-Related Valuation Bases à Maintain Basic Pay for Valuation Bases

Flag the wage type and choose Details. Display the specifications for processing class 1, and choose specification 3. Do not forget to save the setting you have made.

3. To change your employee's basic pay from wage type M020 to 10nn, go to:

Human resources à Payroll à International à Payroll à Corrections Human Resources à Personnel Management à Administration à Maintain Master Data

To run the payroll for the payroll period and check whether the valuation bases have been created, go to:


Check whether wage types /001 and /002 have been included in table IT (after rule X013 has been processed) of the payroll log.

© SAP AG HR400 5-33



1. To copy time wage types to remunerate overtime, go to:

IMG à Personnel Management à Personnel Administration à Payroll Data à Employee Remuneration Data à Wage Types à Create Wage Type Catalog

Choose Copy, and enter the original wage type M110 and the Customizing wage type 3nn1.

Choose Make copies of wage type, and enter the following information:

- Wage type starts at 3nn1 - Number of wage types 8 - Increase for each step 1

2. To encode the valuation bases of wage types 3nn1 - 3nn4, go to:

IMG à Payroll: International à Time Wage Type Valuation à Valuation Bases à Assign Valuation Bases.

Valuate your wage types with the valuation basis 01 to 100% and make the following entries for the first derived wage type.

WT Val. Bases Statement WT Percent.

3nn1 01 3nn5 25 3nn2 01 3nn6 50 3nn3 01 3nn7 75 3nn4 01 3nn8 100

© SAP AG HR400 5-34

3. To set up and run the payroll program for employee remuneration information, go to: Human Resources à Payroll à International à Payroll à Corrections

Human Resources à Personnel Management à Administration à Maintain Master Data à Time Mgmt Trans. Data à Create

Choose the infotype Employee remuneration information and for each entry create a record specifying wage types 3nn1 to 3nn4 and 10 (hours) in the field Number/unit.


© SAP AG HR400 6-1

SAP AG 1999

Absence Valuation

l Absence Valuation Types

l Valuation Using Constant Values

l Time of Absence Valuation

l Defining and Creating Counting Classes

l Assigning Absences to a Valuation

l Grouping for Absence Valuation

l Defining and Using Day Rules

l Valuating Absences According to the ‘As If’ Principle

l Processing Absences in the Schema

Contents:

© SAP AG HR400 6-2

SAP AG 1999

Absence Valuation: Unit Objectives


l Describe the various methods of valuatingabsences.

l Explain what is meant by valuation and counting classes.

l Valuate vacation bonus as a constant in payroll according to organizational differences and time constraints.

© SAP AG HR400 6-3

SAP AG 1999


Payroll Basics

Starting Payroll


Wage Type Valuation


Averages


Factoring


© SAP AG HR400 6-4

SAP AG 1999

Absences

n The system can process an employee's absences in several ways.

n Examples:

• An employee is sick for a long period of time.

• An employee takes vacation.

• An employee goes on maternity leave.

• An employee takes unpaid leave.

© SAP AG HR400 6-5

SAP AG 1999

Absence Valuation Types

l Valuation using an averageamount or a fixed amount

l ‘As If’ principle

n There are various methods for valuating absences. Each method can be used separately or combined with other methods.

1. Valuating absences using averages or constants. Example: You want to calculate a vacation bonus using the average remuneration for overtime hours worked by your employees.

2. Valuating absences as if the employee had worked (‘as if’ principle). Example: You want employees who are unable to work to receive their basic pay as well as the bonus they would have received had they been at work.

n If employees take unpaid leave, their remuneration is reduced accordingly. Reductions in pay as a result of unpaid or partially paid absences (factoring) will be covered later in the course.

© SAP AG HR400 6-6

SAP AG 1999

Absence Valuation: Vacation Bonus (1)

l The Caliber ‘A’ Bicycle Company pays a constant vacation bonus for each day.

l In the near future the company will pay a vacation bonus made up of average values that ispaid for each day.

© SAP AG HR400 6-7

SAP AG 1999

Valuating Absences by Constants/Averages

View: Absence Valuation: Averages/Constants

AbsValGrpg Valuation rule

0101 Paid leave From To

WTypeM400____

TimeB__

Percent.100______

Time unitAT____

BP splitX____

Day rule______

AHAHATATKTKTRHRHRTRT

Time units

Absence hoursAbsence daysCalendar daysAccounting hoursAccounting days

363.0051.0071.00

363.0051.00

n Scenario:

1. Your employees are to receive a fixed vacation bonus for each day's leave. In this case, the system valuates the relevant wage type using a constant amount.

2. For each absence day of leave, your employees are to receive a vacation bonus based on the average amount of overtime they have worked over the last three months. In this case, the relevant wage type must be valuated using average bases.

n You want to pay vacation bonus for each leave day. There are several ways in which you can remunerate leave per day:

1. Calendar days.

2. Absence days, that is, each day that counts as a workday on the work schedule.

3. Accounting days, that is, leave days processed according to the entries specified in the table Attendance/Absence Counting .

n If you flag the field Basic Pay Split, changes made to an employee's basic pay for a payroll period are taken into account.

© SAP AG HR400 6-8

SAP AG 1999

Time of Absence Valuation

Absence Jan 20 Feb 05

Payroll period Jan 01 Feb 01 March 01

Jan 98 Feb 98

Time B

Time E

Time I

Time Z Store data per day

n If an employee’s absence spans several payroll periods, valuation can occur either in the payroll period in which the absence begins, the payroll period in which the absence ends, or on a pro rata basis in each payroll period affected.

n Time Z writes the wage type to internal time wage type table ZL.

© SAP AG HR400 6-9

SAP AG 1999

Defining and Creating Counting Classes

View: Absence Valuation: Create Counting Classes


0101 Paid leave Start End

Counting class01____

LeaveX

% rate100

Day rule

View: Define Counting Classes

01 Leave

02 Illness

xAU01

xAU02

xAP01

xAP02

n Counting classes are used to collect data on various absence types (for example, leave and sickness). You have the option of subdividing each counting class into paid (AP = absences paid) and unpaid absences (AU = absences unpaid).

n This data on paid and unpaid absences is used to reduce pay or to generate statistical information.

1. To reduce remuneration for unpaid absences, in the standard system, all counting classes that group unpaid absences are processed together. Therefore, a prerequisite for the reduction in remuneration is that the unpaid absences are grouped together in at least one counting class. If several counting classes are to be created for unpaid absences, you must explicitly specify the counting classes that are to be taken into consideration in factoring .

2. To generate statistics and for cost accounting, you can group together absence times in the counting classes to fill wage types and evaluate the cumulated values for cost accounting or statistical purposes. You can access the counting classes using operation NUM. Paid counting classes are queried in operations with the ID xAPnn, and unpaid counting classes are queried with the ID xAUnn, where x = K for the value in calendar days, A in workdays, and S in hours.

© SAP AG HR400 6-10

SAP AG 1999

Assigning Absences to a Valuation (1)

View: Absence: Payment Data

PSGrp From To

01010101

Abs./attendance type VRule Cat.

0100 Leave 0110 Leave 1/2 day0120 Seniority leave 0200 Sickness

01010102

----

Absence Valuation Rule

01 Leave

02 Sickness

n You want to valuate absences for paid leave differently from absences for paid sickness, and you want all leave types to be processed using the same valuation method. To do this, you group all absence types that are valuated identically by assigning them to an absence valuation rule.

n Absence valuation rules determine how an employee's absences are processed in the payroll run.

n The field Category is used in specific Austrian evaluations and for the German public sector to determine the continued pay and sick pay supplement periods.

© SAP AG HR400 6-11

SAP AG 1999

Assigning Absences to a Valuation (2)

View: Absence:Valuation Using Constants/Averages

PSGrp From To

01010101

Abs./Attendance type VRule Cat.

0100 Leave 0110 Leave 1/2 day 0120 Seniority leave 0200 Sickness

01010102

----

View: Valuate AbsencesAbsValGrpg Rule Valuation class

01010202

01020102

LeaveSickness Leave Sickness

Employee groupingfor absence valuation

n To valuate absences, you must divide your employees into groups. This enables you to apply different absence valuation rules to each grouping.

© SAP AG HR400 6-12

SAP AG 1999

Valuation Rules and Counting Classes

1.1.1.Create absence valuation rules01 Leave02 Paid illness. . .11 Unpaid illness

2.2.2.Cumulate absences for valuation0100 Leave0110 Half leave day 010120 Age-based leave. . .0200 Illness 02. . .0620 Unpaid leave 11

3.3.3.Create counting classes for absence valuation

Valuation rule 01

Define counting classes01 Leave02 IllnessCreate counting classes for absence valuation

a)

b)

Valuation rule 11

xAP01 Counting class 01 Paid

Counting class 01 PaidxAU01

leave

leave

100%

100%

n In this example, paid leave is grouped together using the absence valuation rule 01 in counting class 01 Leave in the „bucket“ of paid absences (AP).

n Unpaid leave is grouped together using absence valuation rule 11 in counting class 01 Leave in the „bucket“ of unpaid absences (AU).

© SAP AG HR400 6-13

SAP AG 1999

Grouping for Absence Valuation

E OUTWPPLANT

E 1000

MODIF A = 01


E ****

MODIF 1 = 01

MODIF 2 = 01

MODIF A = 02

MODIF 1 = 02

MODIF 2 = 02

E 1100


Personnel area


Table Time wage type selection rule


n In this step, you group together employees whose absences are to be valuated identically in absence valuation. In this way, you determine which table entries the system references for which employee subgroup groupings during absence valuation.

n Decision operation OUTWP uses work center elements to determine the modifiers.

n Operation MODIF set to parameter A determines the employee groupings for accessing the table Absence Valuation during payroll.

© SAP AG HR400 6-14

SAP AG 1999

Absence Valuation: Vacation Bonus (2)

l The Caliber ‘A’ Bicycle company decidesnot to pay the constant vacation bonus for an absence taken on a public holiday. Therefore absences that coincide with a public holiday should be grouped together in a separate counting class.

© SAP AG HR400 6-15

SAP AG 1999

Defining Day Rules

View: Define Day Rules

Day ruleSequential no.

WD00

Conditions set for holiday class Prev. day Current day

XHoliday class BLANK - no public holidayHoliday class 1 - public holiday

XX

….

Conditions set for day type

XDay type BLANK - work acc. to PWS Day type 1 - day off

XX

….

Conditions setfor weekday

MondayTuesday….

XX

Conditions setfor planned hours

Plnd hrs > 0Plnd hrs = 0….

XX

X

n Day rules allow you to form counting classes or wage types based on the following conditions set for the day of an absence:

• Public holiday class or day type of the day to be evaluated or the previous day?

• Which weekday?

• Does the employee's personal work schedule for the current or previous day show planned hours?

n You can specify several different conditions for a day rule, and assign them sequential numbers. During processing, the system runs through the numbers in consecutive order until it finds an appropriate condition.

n The name range reserved for customers is A - Z.

© SAP AG HR400 6-16

SAP AG 1999

Using Day Rules

View: Absence Valuation: Averages/Constants



WTypeM400

TimeB

Percent.100

Time unitAT

BP splitX

Day ruleWD

View: Absence Valuation: Create Counting Classes



Counting class 0111

Paid X

% rate100100

Day ruleWDDO

n WD - Workday: To ensure that the counting class is only formed on workdays, two conditions must be fulfilled and stored in a rule without a sequential number:

a) The day is assigned day type BLANK.

b) There are planned hours specified for the employee for this day, that is:

A valid daily work schedule with planned hours greater than 0, or

A time substitution.

n Making entries for just one of these conditions is not sufficient to determine a workday. If a day is assigned the day type BLANK, the decision as to whether or not the employee must work is made on the basis of the planned hours in the work schedule (are there planned hours specified for the employee on the day in question or is the daily work schedule OFF?). Therefore, the planned hours in the daily work schedule and the day type must both be queried.

n DO - Day OFF: Days off can be characterized by two different conditions that you represent by assigning the sequential numbers 01 and 02 to day rule DO:

c) Sequential number 01: The day is assigned day type 1.

d) Sequential number 02: There are no planned hours specified for the employee on the relevant day.

© SAP AG HR400 6-17

SAP AG 1999

Absence Valuation: ‘As If’ Principle

l Absences taken by employees who are remunerated based on their working times are to be paid as if the employee had worked.

© SAP AG HR400 6-18

SAP AG 1999

Valuating Absences Using the ‘As If’ Principle

View: Absence Valuation: ‘As If’ Principle

PSGrp Time wage type selection

0101

Valuation rule

0102

Leave Sickness x

Employee groupingfor absence valuation Wage type generation

10101010

20202020

n Absence valuation using the ‘as if’ principle means paying employees exactly as if they had worked. This includes bonuses that form part of the employee's planned working time. Overtime is not taken into account when absences are valuated using the ‘as if’ principle.

n Example: An employee grouping is paid according to time worked. One employee should have worked 160 hours in the month. Instead, he or she worked 120 hours and was unable to work the other 40 hours.

• Wage types must be generated for these 40 hours so that the employee can be paid for the absences.

• As a result of the collective agreement, legal requirements or enterprise-specific regulations, the employee is also to receive bonuses for work on Sundays, night work, and so on, just as if he or she had worked as normal.

© SAP AG HR400 6-19

SAP AG 1999

Processing Absences in the Schema

XT00...MOD XMOD GENRAB.DAYPR TC00.PAB...


Determine payroll modifiersImport absences

Day processing of time data

Edit absence data

n Function MOD calls personnel calculation rule XMOD which queries employee work center data and sets modifiers for table access during payroll.

n The entries are sorted and grouped in table views using one or more key fields.

© SAP AG HR400 6-20

SAP AG 1999

Absence Valuation: Summary (1)

l Time wage types for absences can bevaluated at different times during the absenceusing average or fixed amounts. They canalso be sorted according to organizationalcriteria and valuation rules (for example, leave).

l In factoring and Cost Accounting, absences arecumulated into counting classes (for example,sickness). Paid and unpaid absences canbe processed separately in each countingclass.

© SAP AG HR400 6-21

SAP AG 1999

Absence Valuation: Summary (2)

l Absences can be valuated usingthe ‘as if’ principle, which is used toremunerate employees exactly as ifthey had worked.

© SAP AG HR400 6-22

Exercises

Unit: Absence Valuation

Topic: Valuating Absences


• Including a constant, daily vacation allowance in the payroll run.

Your company pays a vacation allowance for each day of leave. The amount of the vacation allowance varies depending on the employee's organizational assignment.

Your company pays a constant vacation allowance of 20.00 per payroll day. You want to include the vacation allowance in the payroll run using the absence Leave. 1. Determine the absence valuation grouping for your employee by setting modifier

MODIF A to value yy (yy = 70 + group number) in personnel calculation rule ZMnn (nn = group number) for the table ”Valuation of Absences”.

2. To ensure that the vacation allowance is valuated as a constant, assign a constant valuation basis to the wage type 40nn ”Vacation allowance”. Enter the valuation indicator K against your wage type. Create an entry for the wage type 40nn ”Vacation allowance” in the table ”Constant wage type valuation” under the payroll modifier xx (xx = 50+group number) using the amount 20.00.

3. To ensure that wage type 40nn is included in your payroll runs, your table "Valuation of absences" must contain an entry for your absence valuation grouping. Use the entry for the absence valuation grouping 01 and the valuation rule 01 as a copy template and create an entry for your absence valuation grouping yy and the valuation rule 01 Leave (yy = 70 + group number).Use counting class 01 and ensure that the absence is paid in full. Effect payment of the vacation allowance in the payroll period that leave begins.

4. Record leave for your employee between payroll periods 03 and 04 (the course instructor will provide the exact dates). Release and run the payroll for period 03.

5. Effect payment of the vacation allowance in the payroll period that leave ends (E). Change the entry for absence grouping yy, and run the payroll for period 04. What must you take into account as you do this?

6. Effect payment of the vacation allowance in the relevant payroll period (I). Change the entry of absence grouping yy, and run the payroll for periods 03 and 04. When there are no more errors, exit the payroll run. Check the payroll log for each scenario.

© SAP AG HR400 6-23

Solutions

Unit: Absence Valuation

Topic: Valuating Absences

1. To set up the absence valuation grouping in personnel calculation rule ZMnn, to:

IMG à Payroll: International à Absences à Define Grouping for Absence Valuation

Note: The IMG automatically calls personnel calculation rule XMOD. Note that you previously copied personnel calculation rule ZMnn, and included it in schema Z0nn (nn = group number).

2. To valuate wage type 40nn as a constant, go to:

IMG à Payroll: International à Time Wage Type Valuation à Valuation Bases à Constant Valuation Bases à Assign Valuation Bases

Change the following entry: Wage type: 40nn Start date: January 1st current year End date: 31st December 1999 Valuation basis: K

IMG à Payroll: International à Time Wage Type Valuation à Valuation Bases à Constant Valuation Bases à Define Wage Type-Dependent Constants à Determine Constant Valuation Per Wage Type

Create the following entry: Mod: xx Wage type: 40nn Start date: January 1st current year End date: 31st December 1999 Value: 20

© SAP AG HR400 6-24

3. To enter absence valuation grouping yy and valuation rule 01 Leave, go to:

IMG à Payroll: International à Absences à Valuation of Absences à Create Counting Classes for Absence Valuation à Set Up Counting Classes for Absence Valuation

Create the following entry: AbsValGrp: xx Valuation rule: 01 Count.class: 01 Paid: yes Percentage: 100

IMG à Payroll: International à Absences à Valuation of Absences à Valuate Absences by Constants/Averages

Enter the following data for the valuation of averages: Wage type: 40nn Time: B Percent: 100 Time unit: RT

4. Record and run payroll for cross-period leave:

Human Resources à Personnel Management à Administration à Maintain Master Data à Time Mgmt Trans Data à Absences à Create


5. To change the data stored for absence grouping yy, and run the payroll, go to:

IMG à Payroll: International à Absences à Valuation of Absences à Create Counting Classes for Absence Valuation à Absence Valuation: Expert View

Time: E

Solution: After running the payroll for period 03, you changed an entry in a table view. This change does not automatically trigger a retroactive accounting run for the relevant employee. You must therefore run the payroll for period 04 with forced retroactive accounting for period 03.

6. To change the data stored for absence grouping yy, and run the payroll, go to: IMG à Payroll: International à Absences à Valuation of Absences à Create Counting Classes for Absence Valuation à Absence Valuation: Expert View

Time: I


© SAP AG HR400 7-1

SAP AG 1999


l Time Wage Type Selection

l Time Pairs in Table TIP

l Structure of a Time Wage Type Selection Rule

l Grouping for Time Wage Type Selection Rule

l Day Grouping for Time Wage Type Selection

l Valuation Classes for Period Work Schedule

l Examples of Time Wage Type Selections

l Function GWT

l Time Wage Type Selection in the Schema

Contents:

© SAP AG HR400 7-2

SAP AG 1999

Time Wage Type Selection: Unit Objectives

At the end of this unit, you will be able to:

l Explain the time wage type selectionconcept.

l Assign groupings for the time wage typeselection rule based on organizationaldifferences.

l Create time wage type selection rules.

l Modify the schema to meet companyrequirements.

© SAP AG HR400 7-3

SAP AG 1999


Payroll Basics

Starting Payroll


Wage Type Valuation

Averages


Factoring



© SAP AG HR400 7-4

SAP AG 1999

Time Wage Type Selection (1)

Time sheet Carl Walden

Thursday 7:00 a.m. - 7:00 p.m.

Friday 7:30 a.m. - 6:00 p.m.

Saturday 10:00 a.m. - 5:00 p.m.

Sunday 10:00 a.m. - 1:00 p.m.

When does overtime start?

How many hoursovertime are

paid at what rate? Weekendwork?

n If an employee's working times are recorded manually on a time sheet and you want to maintain this data as wage types in the Employee Remuneration Information infotype (2010), the person responsible must be familiar with all the relevant details and take these into account. For example:

• When does planned working time end, that is, when does overtime start for the employee?

• Which bonus is used to remunerate overtime?

• Does the employee's work schedule include weekend work, or is work at weekends the exception (do the bonuses vary)?

• Is there a public holiday on the workday itself, the day before or the day after?

n The HR component allows you to check an employee's working times by defining certain conditions. Once the conditions have been fulfilled, the system can generate the required wage types and include these in the payroll run.

© SAP AG HR400 7-5

SAP AG 1999

Time WT selection andTime WT selection andoovertimevertime compensation compensation

Time Wage Type Selection andOvertime Compensation

Initialization

Prepare time data

Time classification

Admin. of time accounts

Final processing

Tolerance and error checks

FunctionFunctionDAYMODAYMO

Time wage typesTime wage typesselectionselection

Overtime Overtime compensationcompensation

Time wage type Time wage type selection groupselection group

n Time wage type selection takes place in subschema TC00.

© SAP AG HR400 7-6

SAP AG 1999

Time Pairs

Calculate employee’s working time

EarlyNormalNight

Work schedule Time recording terminal

+

Planned time Actual time

Processing type

8:00 a.m.

S M

5:00 p.m. 7:00 p.m.

Time pairs

n The R/3 System displays an employee's working times in the form of time pairs (start/end times). In this example, the time recording terminal shows that the employee worked from 8:00 a.m. to 7:00 p.m. The time pair 08:00 a.m. to 05:00 p.m. is derived from the employee's work schedule. The pair represents the employee's planned working time and is assigned processing type S (planned work). The time pair 8:00 a.m. to 5:00 p.m. represents the time span the employee works outside his or her planned working time, and has processing type M (overtime).

n Time pairs are stored in internal table TIP (Time Pairs).

© SAP AG HR400 7-7

SAP AG 1999

Time Wage Type Selection (2)

TIPStart End Proc. type Number

08.000017.0000

17.000019.0000

SM

9.00002.0000

DZLDZL

GWT M ZMLGWT S DZL

FunctionTime wage type selection

ZMLZML

Rules for selectingtime wage types(V_T510S)

l Hourly wagel Bonuses

l Overtimewage types

Planned working pairs Overtime pairs

n When daily processing is effected, the entries in internal table TIP are generated as time wage types.

n To do this, you must first define rules that assign time wage types to the entries in table TIP according to the processing type of the relevant entry (for example, S or M).

© SAP AG HR400 7-8

SAP AG 1999

Time Wage Type Selection: Rule Structure (1)

n Valid processing types

FieldField

Time pair type? (planned or overtime pair)

DefinitionDefinition

n Conditions on day What days?l Weekdayl Workday, weekendl Public holiday

n Conditions on time l What time intervals?l What limits?l Determine the value limits?

n Control l Override using fixed values?l Leave rule?

n Valid processing types: These fields determine the processing types that entries in internal table TIP must have in order to generate the relevant wage type.

n Conditions on day: These fields check weekdays, public holidays, the day type and the daily work schedule class.

n Conditions on time: These fields check time intervals as well as minimum and maximum hours.

n Control: This field allows you to specify a fixed value.

n For the relevant entry to be selected, all the conditions must be fulfilled simultaneously.

n For time wage type selection rules requiring start and end times to be observed, all the TIP entries to be valuated for the relevant day must denote clock times. If there are TIP entries without clock times, the time wage types that specify a time interval are not selected for that day.

© SAP AG HR400 7-9

SAP AG 1999

Time Wage Type Selection: Rule Structure (2)

Conditions time

20:00When?When?

n Time interval:

- 30:00

n Value limits for number of hours:

Minimum hours:

Maximum hours:

Explicit Symb.

Relevantprocessing types:

Interval:

Start?Start?

End?End?

S M

S

Planned hrs.acc. to DWS

Time interval?

Time interval?

n Clock time interval: The system only processes time pairs that fall within the time interval specified.

n Maximum/minimum hours: The employee must work a minimum/maximum number of hours. This entry can be explicit or denote planned hours based on the daily work schedule.

n The system determines limits using the relevant processing types. If you flag the field Interval, the system only processes the hours of the time pair that apply to the relevant time interval.

n An entry in the fixed value field always overrides the hours specified by the time pair.

© SAP AG HR400 7-10

SAP AG 1999

Time Wage Type Selection Rule Group

MODIF W = 02MODIF W = 01 MODIF W = 03

l Hourly wagel Bonusesl Overtime

l Bonusesl Overtime

l Bonusesl Overtime as of

10 overtime hours

Function MOD, personnel calc. rule TMOD

Hourly wage earners Salaried employees Salaried employees

n You can use the time wage type selection rule group to set specific regulations for time wage type selection according to an employee's organizational assignment.

n You use function MOD in personnel calculation rule TMOD to determine which time wage type selection rule group the time evaluation driver should use to access the entries for an employee in the Time Wage Type Selection table.

© SAP AG HR400 7-11

SAP AG 1999

Grouping for Time Wage Type Selection Rule

E OUTWPPLANT

E 1000

MODIF T = 01

Determining table modifiersTMOD

E ****

MODIF W = 01


Personnel area

Table Time type determination


E 1100

MODIF T = 01

MODIF W = 02

Table Time type determination


n In this step, you group together employees who are to be processed identically for time wage type selection. In this way, you determine which table entries the system references for which employee subgroup groupings during wage type generation. Operation MODIF W determines the employee groupings for accessing the Time Wage Type Selection table during payroll.

n Decision operation OUTWP uses work center elements to determine the modifiers.

© SAP AG HR400 7-12

SAP AG 1999

Time Wage Type Selection: Function DAYMO

Set day grouping for time wage type selection

PAR 1

DAYMO

Not a public holidayMonday - Saturday

Not a public holidaySunday

Public holidayMonday - Saturday

Public holidaySunday

Conditions on dayConditions on day

Day grouping

PAR 2 PAR 3 PAR 4

01 02 02 02

n Function DAYMO is used to determine which rules are referenced for time wage type selection for the relevant day. The function must be contained in the schema otherwise no rules are selected for time wage type selection.

n If the four day categories are not sufficient for your purposes, it is also possible to set the day grouping in a personnel calculation rule using operation MODIF D=xx.

© SAP AG HR400 7-13

SAP AG 1999

The Rule Group Principle Using Time WageType Selection

TIP Wage type MI10

Overtime 25%

Overtime 50%

Night bonus 35%

Rule not fulfilled

Rule not fulfilled

Wage type MQ30

Time wage typeselection group

Day grouping

Not a pub. hol.Mo - Sa

01 01

01 01

01 01

Night bonus 35%

Sequential number ofrules for time wage type selection

01 01 Night bonus 35% Rule not fulfilled

Sunday bonus

Rule groupRule group

01 01 Normal hours

01 02

01 02

050

055

070

075

001

070

080

n By assigning a wage type to groupings (time wage type selection rule group and day grouping), you can preselect the relevant wage types.

n The sequential number should be chosen in increments of 10 so that you can add numbers later.

© SAP AG HR400 7-14

SAP AG 1999

Valuation Classes for the Period Work Schedule

Normal workMo...Fr

3-week shiftMo...Fr

Overtime bonus Overtime shift

Time wage type selection

Creates various bonuswage types for the sameamount of overtime

1 3Valuation class

n Valuation classes enable you to structure time wage type selection rules according to the period work schedule. For example, employees who work on a rotating shift can receive higher bonuses than employees who work on a normal shift.

© SAP AG HR400 7-15

SAP AG 1999

Example: Time Wage Type Selection Rule (1)

Grouping…Valid processing typeM _ _ _Conditions on day

Start00:00

Control Fixed value

Valuation class0123456789

x

Conditions on time

End47:59

Min. Symb. Max. Symb. Relevant proc. typesInterv.

M Overtime

Wage type for 2 hours overtime during shift

16.00 18.00

n You want overtime for shift work to be remunerated at a higher rate than overtime for normal work. To do this, the system queries the valuation class of the period work schedule.

© SAP AG HR400 7-16

SAP AG 1999


Grouping…Valid processing typesM _ _ _Conditions on day

Start20:00

Control Fixed value

Valuation class0123456789x

Conditions on time

End30:00

Min. Symb. Max. Symb. Relevant proc. typesInterv.

M Overtime

Wage type for 2 hours overtime

22.00

2

Weekdays01234567

xx

22.20

n In the fixed value field, you can specify how many hours (number) should be valuated with a wage type if an employee's time pair meets all other conditions but overlaps with the time interval.

n If an employee's overtime exceeds the fixed value, a subsequent rule must be defined in which the fixed value is configured as minimum hours.

© SAP AG HR400 7-17

SAP AG 1999


Grouping…Valid processing typesS M _ _...

Start20:00

Control Fixed value

Conditions on time

End30:00

Min.2,00

Symb. Max. Symb. Relevant proc. typesS M Interv.

Wage type for hours from10:00 p.m. to midnight

X

M Overtime

14.00 24.0020.00 22.00

S Plnd. Wrk.

n Only the hours that fall within the time interval of 08:00 p.m. to 06:00 a.m. the following day are taken into account. The hours from 02:00 p.m. to 08:00 p.m. are not taken into account. The minimum requirement of two hour's work (minimum hours = 2 hours) is calculated from 08:00 p.m. onwards, because the field Count in specified interval only has been activated. A wage type is generated for the time between 10:00 p.m. to midnight.

© SAP AG HR400 7-18

SAP AG 1999


Grouping…Valid processing typesS M _ _...

Start20:00

ControlFixed val.

Conditions on time

End30:00

Min.2.00

Symb. Max. Symb. Relevant proc. typesS M Interv.

Wage type for hours from 08:00 p.m. to midnight

Leave rule

Exit time wage typeselection

M Overtime

14.00 24.0020.00 22.00

S Planned work

n The employee has already fulfilled the minimum requirement of two hour's work (minimum hours = 2) by 04:00 p.m. in the planned working time as the system does not only count the hours in the time interval specified. A wage type is generated for the time between 08:00 p.m. and midnight.

n Leaving the time wage type valuation rule : When selecting time wage types, the system checks all the rules stored for all TIP entries and selects the relevant wage type, if the requirements are met. By activating this field, you cause the system to leave processing of the current rule , as soon as the wage type was selected for a TIP entry. The next rule continues time wage type selection.

n Exiting time wage type selection: By activating this field, you cause the system to exit time wage type selection, as soon as the wage type was selected for a TIP entry. The subsequent rules are no longer included in time wage type selection.

© SAP AG HR400 7-19

SAP AG 1999

Function GWT: Select Time Wage Types

Select wage types for planned work and overtime

1. Wage type for planned work:Function GWT with parameter S

2. Wage type for overtime:Function GWT with parameter M

WT Key IFTYP NumberMM10 M 2.0000 MM20 M 2.0000

ZMLTIP

Start End Proc.Type AB Number18.0000 22.0000 M 4.0000

GWT M ZML

V_T510s

WT IFTYP NumberMI10 A 4.0000MI10 S 3.0000

DZL

Start End Proc.Type AB Number08.0000 10.0000 S 01 2.000010.0000 13.0000 S 3.000014.0000 16.0000 S 02 2.0000

TIP

GWT S DZL

V_554C_E

V_T510s

n The function GWT generates time wage types for TIP entries according to the rules in the view Time Wage Type Selection (V_T510S).

• Time wage type selection for planned work: TIP entries with processing type S are processed in time wage type selection for planned time. For each time wage type selection rule for wage types for planned working time, the system checks which TIP entries observe the rule. If the rule is observed, the relevant wage type is entered in the internal table DZL.

• Time wage type selection for overtime: All TIP entries with processing type M are processed in time wage type selection for overtime. For each time wage type selection rule for overtime wage types, the system checks which TIP entries observe the rule. If the rule is observed, the relevant wage type is entered in the internal table ZML.

n Function GWT is used in time evaluation to select time wage types for all absences which are valuated on the basis of the ‘As If’ principle (the field Wage type generation in the view Absence Valuation Rule (V_554C_E) must be activated). This is done for absences whose processing type has been changed to S or absences which are evaluated using function GWT A. All other absences are valuated in the gross part of payroll.

n There is detailed information on absence valuation in the section on Absences in the payroll section of the Implementation Guide (IMG).

© SAP AG HR400 7-20

SAP AG 1999

Time Wage Type Selection in Schemas

XT00.IF PDCIMPRT B2PRINT NP ZLDAYPR TC00 PDCELSEDAYPR TC00ENDIF


Is PDC active in period?Import cluster B2Print table of time wage typesDay processing of time dataPDC not active in periodDay processing of time dataEndif PDC

TC00.MOD TMOD GEN.DAYMO 01 02 02 02GWT S DZLGWT M ZML.PRINT NP DZL

Processing time data/Wage type selection

Set modifiers

Set day modifierTime wage type selection for planned workTime wage type selection for overtime

Daily results: Wage types

n If time recording has been activated for the personnel number for which payroll is being run, this indicates that time wage types already exist in cluster B2 of table ZL. This cluster is then imported, and the system processes any days that have not yet been processed for the payroll period. The wage types that still have to be generated are formed according to the work schedule, which triggers retroactive accounting in the subsequent payroll period.

n Function DAYPR calls subschema TC00, which processes time wage type selection for planned work and overtime on a daily basis.

© SAP AG HR400 7-21

SAP AG 1999

Time Wage Type Selection: Summary (1)

l In time wage type selection, time pairsform wage types.

l Time wage type selection occurs usingrules that are stored in the Time WageType Selection Rule table. The rules enable you to control time wage type selection according to employees, daysand times.

© SAP AG HR400 7-22

SAP AG 1999

Time Wage Type Selection: Summary (2)

l Time wage type selection can be processedaccording to two groupings that are set up in the Time Wage Type Selection Rule table: The time wage type selection rule groupprocesses time wage type selection accordingto the employee’s organizational assignment.The day grouping processes time wage type selection depending on certain factors applicableto the day that is being evaluated.

© SAP AG HR400 7-23

Exercises

Unit: Time Wage Type Selection

Topic: Generating Wage Types

• Adjusting personnel calculation rule TMOD to meet customer requirements.

• Adjusting subschema TC00 to meet customer requirements.

• Defining time wage type generation rules.

Up to now, your company has paid overtime as employee remuneration information. However, your employees are now able to record overtime in the system themselves. You want to include the time pairs recorded for overtime as time wage types in the payroll run. In the table Time Wage Type Selection Rule, you want to create different rules for each of the payroll areas in your company.

Time wage types 3nn1 to 3nn4, which were entered in the system as employee remuneration information, must now be generated by the system on the basis of overtime time pairs. For this reason, the table Time Wage Type Selection Rule must include rules that are grouped together in a time wage type selection rule group for each payroll area. In this exercise, you should create the time wage type selection rules for the payroll area to which you assigned your employee at the time of hiring.

1. First you must define the groupings. In the IMG, make a copy of personnel calculation rule TMOD, and rename it ZTnn (nn = group number). Then adjust personnel calculation rule ZTnn by querying the payroll area in the decision operation. Change MODIF W to the value ww (ww = 10 + group number) for your payroll area, and to the value 01 for the other payroll areas.

2. Since personnel calculation rule TMOD is accessed from subschema TC00, an adjustment is also required here. Make a copy of subschema TC00, rename it ZCnn (nn = group number), change the line that includes function MOD, and the line that accesses rule TMOD.

3. Since subschema TC00 is called up from schema XT00, an adjustment is also required here. Change the relevant line in schema ZTnn (nn = group number) accordingly.

© SAP AG HR400 7-24

4. Enter the generation rules for the following wage types:

- 3nn1 Up to 2 hours overtime

- 3nn2 3 or more hours overtime

- 3nn3 Overtime on Sundays

- 3nn4 Overtime on public holidays

Note: According to the collective agreement for the company used in the course, public holidays last from 00:00 midnight to 06:00 a.m. on the following day. The system should also generate the public holiday bonus if the overtime time pair starts after midnight, that is, on the following day.

5. Test the generation rules you have created by entering overtime for your employee on the following days in payroll period 05:

- On a working day 05:00 p.m. – 08:00 p.m.

- On a Sunday 10:00 a.m. – 01:00 p.m.

- On a public holiday 10:00 a.m. – 01:00 p.m.

- On the next working day 05:00 p.m. – 08:00 p.m.

Release the payroll for period 05, start the payroll run, and check the results.

© SAP AG HR400 7-25

Solutions

Unit: Time Wage Type Selection

Topic: Wage Type Generation

1. To define the groupings for the table Time Wage Type Selection Rule go to:

IMG à Payroll: International à Day Processing of Time Data à Day Processing Functions à Define Groupings

Rule ZTnn, employee subgroup grouping 3:

OUTWPPAYSB

**

MODIF T = 02 TOUTWPPAYSB MODIF W = 01 TOUTWPPAYSB

Payroll area?

All other

yy

MODIF T = 02 TOUTWPPAYSB MODIF W = ww TOUTWPPAYSB

Payroll area yy

© SAP AG HR400 7-26

2. To adjust schema TC00, go to:

Human resources à Payroll à International à Tools à Maintenance Tools à Schema à Copy

from schema TC00 to schema ZCnn

In subschema ZCnn, change the line that accesses rule TMOD as follows: MOD ZTnn GEN

3. To adjust subschema XT00 go to:

Human resources à Payroll à International à Tools à Maintenance Tools à Schema à Change

In subschema ZTnn, change the line that accesses day processing of time data as follows: DAYPR ZCnn

4. To create generation rules for your wage types, go to:

IMG à Payroll: International à Day Processing of Time Data à Day Processing Functions à Time Wage Type Selection Rule à Define Generation Rules

Make the following entries for your time wage type selection rule group ww in the table:

ww 01 010 3nn1 01.01.YY 31.12.9999 ww 01 020 3nn1 01.01.YY 31.12.9999 ww 01 030 3nn2 01.01.YY 31.12.9999 ww 01 040 3nn2 01.01.YY 31.12.9999 ww 01 050 3nn4 01.01.YY 31.12.9999 ww 02 010 3nn3 01.01.YY 31.12.9999 ww 02 020 3nn4 01.01.YY 31.12.9999

Entry details are provided on the following pages

© SAP AG HR400 7-27

Time wage type selection rule group: ww Day grouping: 01 Sequential number: 010 Wage type: 3nn1

Valid processing classes: M

Week days: 1234567 xxxxxx Public holiday class, previous day: b123456789 x Public holiday class, current day: b123456789 x Public holiday class next day: b123456789 xxxxxxxxxx Valuation class: 0123456789 xxxxxxxxxx Daily work schedule class: 0123456789 xxxxxxxxxx Day type b123456789 xx

Start: End: Minimum: Maximum: 2,00

Relevant processing types: M

© SAP AG HR400 7-28



Week days: 1234567 xxxxxx Public holiday class, previous day: b123456789 xxxxxxxxx Public holiday class, current day: b123456789 x Public holiday class next day: b123456789 xxxxxxxxxx Valuation class: 0123456789 xxxxxxxxxx Daily work schedule class: 0123456789 xxxxxxxxxx Day type b123456789 xx

Start: 06:00 End: 24:00 Minimum: Maximum: 2.00


© SAP AG HR400 7-29



Week days: 1234567 xxxxxx Public holiday class, previous day: b123456789 x Public holiday class, current day: b123456789 x Public holiday class next day: b123456789 xxxxxxxxxx Valuation class: 0123456789 xxxxxxxxxx Daily work schedule class: 0123456789 xxxxxxxxxx Day type b123456789 xx

Start: End: Minimum: 2,00 Maximum:


© SAP AG HR400 7-30



Week days: 1234567 xxxxxx Public holiday class, previous day: b123456789 xxxxxxxxx Public holiday class, current day: b123456789 x Public holiday class next day: b123456789 xxxxxxxxxx Valuation class: 0123456789 xxxxxxxxxx Daily work schedule class: 0123456789 xxxxxxxxxx Day type b123456789 xx Start: 06:00 End: 24:00 Minimum: 2,00 Maximum:


© SAP AG HR400 7-31



Week days: 1234567 xxxxxxx Public holiday class, previous day: b123456789 xxxxxxxxx Public holiday class, current day: b123456789 x Public holiday class next day: b123456789 xxxxxxxxxx Valuation class: 0123456789 xxxxxxxxxx Daily work schedule class: 0123456789 xxxxxxxxxx Day type b123456789 xx

Start: End: 06:00

© SAP AG HR400 7-32



Week days: 1234567 x Public holiday class, previous day: b123456789 xxxxxxxxxx Public holiday class, current day: b123456789 x Public holiday class next day: b123456789 xxxxxxxxxx Valuation class: 0123456789 xxxxxxxxxx Daily work schedule class: 0123456789 xxxxxxxxxx Day type b123456789 xx

Start: End: 30:00

© SAP AG HR400 7-33



Week days: 1234567 xxxxxxx Public holiday class, previous day: b123456789 xxxxxxxxxx Public holiday class, current day: b123456789 xxxxxxxxx Public holiday class, next day: b123456789 xxxxxxxxxx Valuation class 0123456789 xxxxxxxxxx Daily work schedule class: 0123456789 xxxxxxxxxx Day type b123456789 xx

Start: End: 30:00

© SAP AG HR400 7-34

5. To test the generation rules, go to:

Human resources à Personnel Management à Administration à Maintain Master Data à Time Mgmt Trans. Data à Overtime à Create

Choose the infotype Overtime, enter the overtime for the relevant dates and times, and run payroll.

Human Resources à Payroll à International à Payroll à Release Payroll

Human Resources à Payroll à International à Payroll à Start Payroll

Human Resources à Payroll à International à Payroll à Exit Payroll

© SAP AG HR400 8-1

SAP AG 1999

Averages

l Valuating Time Wage Typesl Elements of Average Processingl Creating Average Basesl Triggering the Valuation of Averagesl Relevancy Rule for Average Calculationl Cumulation Rules for Average Basesl Calculating the Average Amountl Final Processing Rules and Comparison Rulesl Adjustment Rules for Average Basesl Processing Averages in the Schema

Contents:

© SAP AG HR400 8-2

SAP AG 1999

Averages: Unit Objectives


l Explain how to calculate average values forwage types used in previous payroll periodsand how to valuate a wage type in the currentperiod using these average values.

l Check the relevancy of previous payroll periods.

l Adjust average values to an increase in anemployee's remuneration.

© SAP AG HR400 8-3

SAP AG 1999


Payroll Basics



Averages


FactoringStarting Payroll

Wage Type Valuation


© SAP AG HR400 8-4

SAP AG 1999


WT

Valuate using thevaluation basis

INPUT TABLE OUTPUT TABLEProcessing

RTE NUM AMT WT RTE NUM AMT

X

X

X

X

X

Transfer

Transfer

Multiply

Specify valuationbasis?

X

X

X XX

X XX

Valuate according to principle of averages

yes no

n In personnel calculation rule X015, the system checks to see if the IT table contains time wage types that have not yet been valuated. To do so, the system checks the contents of the value fields AMT (amount), NUM (number) and RTE (rate).

n If the RTE or AMT field contains an amount, the wage type is transferred to the internal table OT.

n If the AMT field is empty, the NUM field contains a number and the RTE field a rate, then the NUM field is multiplied by the RTE field. The result is stored in the amount field, and the wage type transferred to table OT.

n If only the NUM field contains an entry because only a number (for example, hours) was entered, and if the AMT and the RTE fields are both empty, the system queries whether a valuation basis has been specified for the wage type. If this is the case, the wage type is valuated using the valuation basis specified.

n If no valuation basis is specified, valuation takes place according to the principle of averages if a average valuation is assigned to the wage type. If this is not the case, the wage type is not valuated using a monetary value.

© SAP AG HR400 8-5

SAP AG 1999

Remuneration Using Averages

Sales

HR department

How can you create and remunerate average values using variable remuneration for several payroll periods?

n If an employee is sick or is on leave, certain remuneration elements are reduced for the employee in question (for example, commission, bonuses for piecework, overtime). Hence, the employer often pays the average values of variable remuneration.

n You can also use the average calculation procedure in HR Payroll for different purposes. For example, you can calculate average values for fixed payments.

© SAP AG HR400 8-6

SAP AG 1999

Elements of Average Processing

l Retrieving average bases

l Determining the previous periods required

l Performing a relevancy test for each period

l Cumulating the average bases from the relevantprevious periods

l Including changes in pay

l Calculating averages

n Collective agreements often contain rules that state that in the case of absences, an average remuneration calculated from previous months must be paid. To valuate absences according to the principle of averages, the following questions must first be answered:

n How many periods are used to create an average?

n Can a period be irrelevant to the creation of averages? (For example, if an employee takes unpaid leave throughout the whole payroll period.)

n In such cases, what is the maximum number of periods that should be used to create averages?

n What triggers a payment based on an average value (for example, an absence)?

n What is the formula used to calculate the average value?

n What value is used for new employees in the first payroll period, if there are no previous values available for calculating the average value?

n Should an average value be adjusted if remuneration changes (for example, after a standard pay increase)?

n Which wage types are included in an average value?

© SAP AG HR400 8-7

SAP AG 1999

Creating Averages

Payroll periods

n -3Variable remuneration AVariable remuneration B

n -1Variable remuneration AVariable remuneration B

n - 2Variable remuneration AVariable remuneration B

Average calculation bases

Basis A

Basis A

Basis A

Current period nRemuneration withaverage value

lCumulation of basis for calculatingaverages

lCalculation of average value by division

n Remuneration elements included in averages are grouped into average bases for the relevant payroll period and stored together with the payroll results.

n In a payroll period, in which a wage type should be remunerated with an average value, the average bases for the relevant previous periods are first of all cumulated. The average value is then calculated (for example, by dividing the total by the number of previous periods). The resulting value is then included in the employee's remuneration.

© SAP AG HR400 8-8

SAP AG 1999

Creating Bases for Calculating Average Values

Assigning Primary Wage Types to Bases for Calculating Average Values

CoGrp WT Av.basis Valid to Valid from RTE % NUM % AMT %

99 M110 /201 31.12.9999 01.01.1999 4 100 4 100

Assigning Partial Period Parameters to Bases for Calculating Average Values

Part.per. Par. Av.basis Valid from Valid to Percent

TA /205 01.01.1999 31.12.9999 100

n In this step, you specify which primary wage types and which partial period parameters should be included in which average basis. The secondary wage types /201 to /232 are available as average bases.

n Create various average bases, for example, all overtime remuneration, all overtime bonuses, all work on public holidays, and so on.

n Specify which primary wage type should be included in which average basis. Specify which wage type field (RTE, NUM, AMT) should be used with which percentage.

n You can include the following partial period parameters in the average bases. As the value of the Number field is always read from partial period parameters, only specify the percentage here. For a thorough presentation of the partial period parameters, see the unit on Factoring.

© SAP AG HR400 8-9

SAP AG 1999

Averages: Calculating Vacation Bonus

l The Caliber 'A' Bicycle Company pays a constantvacation bonus for each day. This should be calculatedas the average of the overtime pay

© SAP AG HR400 8-10

SAP AG 1999

Processing classPRCL 15Specification n

Is the average calculation rule assigned?

yes

Triggering the Valuation of Averages

Old average calc.procedurePC rule X016 Operation MEANV

New average calc. procedureFunction AVERA

yes

Leave with Average Valuation of Wage Type M400 Vacation Bonus

n If a valuation basis is not been specified, but a specification has been assigned to processing class 15, the wage type is valuated according to the old principle of averages. In this case, the system accesses personnel calculation rule X016 (Special processing for the valuation of time wage types). (For an explanation of the old average calculation procedure please see the appendix.)

n If you assign an average calculation rule to a wage type in the view V_T51AV_P, it is valuated with the monetary value calculated by the new average calculation procedure.

n If processing class 15 is filled with a specification and is also assigned an average calculation rule for a wage type, the wage type is valuated using the new average calculation procedure (if you use the standard schema).

© SAP AG HR400 8-11

SAP AG 1999

Assigning Average Valuation to a Primary Wage Type

Assigning Wage Types to Average Calculation Rules

WType Text Valid from Valid to

7520 Average 01.01.1999 31.12.2005

Av.rule Av. rule text

Averages 1

n In this step, you must maintain all primary wage types that are to be valuated using an average. These wage types are created in payroll either after they were generated from the attendances and absences , or after you have entered them online, for example, in the infotypes 0015 or 2010.

n Specify which wage type should be evaluated according to which average calculation rule.

© SAP AG HR400 8-12

SAP AG 1999

Calculation Rules for Averages

Creating Calculation Rules for AveragesAv.rule Text Valid from Valid to

ZAV1ZAV2

Averages 1 . . 01.01.1999 31.12.2005

Rel.R. Cum.R.

ZREL ZCU1

FProc.

ZEND

Comp.R.

ZCOM

Rel.R.

3

TU

1

max.P.

6

TU

1

current

4

freeze

A

WT

135

===

Calendar monthCalendar weeks (in acc. with feature LDAYW)Rolling month

A14

===

The value is frozen for the length of the absenceThe value is frozen for the calendar year (Jan.01-Dec.31)The value is frozen for one year (April 01-March 03)

n Create the calculation rules using the previously defined relevancy rules, cumulation rules, final processing rules and comparison rules.

n Specify from how many previous periods the relevant average periods should be selected, and if the current period should be included. Select a time unit for the relevant average periods.

n Specify if the calculated average value should be frozen. The rate is then stored in the AVERAGE table in the payroll results. For example : In the case of an absence covering several payroll periods, the calculated average value should be used throughout, or an average value that was calculated in the first payroll period of the year should be used in all the payroll periods in the year.

n If you want to use a relevancy test to determine the relevant period, you must enter the maximum number of relevant periods and the time unit you require.

n If it should be possible to pay the employee a definite amount instead of the calculated value, enter the wage type you wish to use for this purpose.

n You can specify which weekday should be the last day in a calendar week with the help of feature LDAYW. If you want to change the feature, please consider that this will also affect Time Management!

© SAP AG HR400 8-13

SAP AG 1999

Relevancy Rule for Average Calculation

Creating the Relevancy Rule for Average Calculation

Rel.rule

ZREL

LegPers.

N

Rehiring

N

Part.rel.

N

RelAvPer.

1

Funct.mod.

Checking the legal person Checking for re-hiring

Behaviour for partially relevant periods

Behaviour for relevancy of the averages period

n Here, you specify whether an average period should be relevant or should not be relevant for the calculation of averages under the conditions specified. You can use any four-digit sequence of characters starting with the letter Z or a number between 0 and 9 as a name range.

n If you do not use a relevancy rule, the system uses all the average periods for average calculation.

n Define processing of the relevancy test when the legal person changes: Check (Y) or no check (N).

n Define processing of the relevancy test when the employee is rehired: Check (Y) or no check (N).

n Define processing of the relevancy test for partially relevant periods: No check (N), only take the results that do not overlap into consideration (C) or take all the results into consideration (A).

n Define processing of the period's relevancy: Average period is relevant if a result (1) or if all results (A) are relevant.

n If you perform a relevancy test with a function module, you specify it's name. The module provided depends on the country version.

© SAP AG HR400 8-14

SAP AG 1999

Excluding the Relevancy of Off-Cycle Reasons

Excluding the Relevancy of Off-Cycle Reasons

Rel.rule

ZREL

Relevancy rule text

Rel.test for incentive wages

OC-reason

0001

Description

Holiday bonus

n If you do not use Off-Cycle Payroll, you do not need to make these settings.

n Otherwise, you specify which Off-Cycle payroll runs should no longer be taken into consideration.

© SAP AG HR400 8-15

SAP AG 1999

Cumulation Rules for Average Bases

Cumulation Rules for Average Bases

Cum.rule

ZCU1ZCU1

/201/202

Av.basis Valid from Valid to

01.01.199901.01.1999

31.12.200531.12.2005

RTE + AR NUM + AR AMT Factor.

44

44

++

ZADJZADJ

+ AR

Field to be cumulatedCumulation type (+ or -) Multiplication with the adjustment factor from the adjustment rule

Processing for periods to be partially cumulatedF = Factoring according to calendar daysS = Use WPBP split (Error when none exist)N = Use total value

Average basis to be cumulated

n In the cumulation rules, specify which average value calculation basis wage types /2nn should be used. When doing so, you determine which field (RTE, NUM, AMT) should be used to cumulate the wage types and if the cumulation should be positive (+) or negative (-). If you do not make any entries, the relevant field is not cumulated.

n If you have created adjustment rules and these should be used when cumulating, enter the adjustment rule required for every field.

© SAP AG HR400 8-16

SAP AG 1999

Modifying Average Formulas

Modifying Average Formula (Personnel Calculation Rule)

Calculating the average after cumulation

*

****

NUM?0.00

*

DIVID ANR

X018

E

E

=

E

E

Rule NUM RTE AMT

ZAV1

ZAV2

20 500

Work area

for wage type

AMT

500

NUM

20

RTE

25

AMT=M

NUM=M

Cumulation table MV

n An average calculation must result in the Rate (RTE) field containing a valuation basis. The formula used to calculate this value is included in personnel calculation rule X018.

n The internal table MV contains the cumulations for averages.

n Standard rule X018 uses the formula amount/number to calculate hourly rates.

© SAP AG HR400 8-17

SAP AG 1999

Final Processing Rules and Comparison Rules

Final Processing Rules for Averages

F.process.

ZEND

Calc.rule

Z018

Short description

Divide amount by the standard workdays

Creating Comparison Rule for Average Calculation

Comp.rule WT Field Comparison

ZCOM 4711 AMT >> = Comp.wage type is greater than av.value:

Use comparison wage type

Comp. WT is greater than average valueUse comp. WT

< = Comp.wage type is smaller than av.value:Use average value

n Create the final processing rules that you require. You can reselect certain periods for final processing from the relevant average periods and store a delivered or modified final processing rule.

n Define the comparison rules for calculated average values. If you do not want to compare the calculated average value, you do not need to make any settings.

n The calculated value can be compared with a value specified here, for example, the standard pay. Specify under which conditions which value should be used. The system then uses the calculated value or the comparison value accordingly as the average value.

© SAP AG HR400 8-18

SAP AG 1999

Adjustment Rules

Creating Adjustment Rule

Adj.rule

ZADJ

Description

3 months

Adj.type

/001

No.periods+/- Comp.WT TmeUnit WgeType

4 P 3 01

Comparison wage type for determining thefactor for adjustment type 4

Wage type for individualadjustment of the averagebases

Adjustment type

Positive/negative adjustment

No.of periods to be adjustedand the time unit for theaverage periods

n If you need to adjust the average bases to retroactively increased payments for the employee, you must create an adjustment rule that you can then use in the cumulation rules. For each rule, specify which adjustment type (multiplication factor) should be used to adjust the average bases or if the adjustment should be made for individual employees using a wage type. In Release 4.6B, you can only use adjustment type 4. In the Comparison wage type field, enter the required 0nn wage type.

n Decide whether the adjustment should only take place in the case of a positive multiplication factor (P) or also for a negative factor (B).

n Determine the number of periods to be adjusted retroactively and the time unit for the average periods.

n If you want to retroactively adjust the average bases in your own way, specify a wage type here. In this way, you override the adjustment rule. In the payroll period in which the change of average bases becomes effective, use this wage type to assign an individual percentage to your employee, usually an increase percentage. To do so, enter the percentage, where, for example, '105' corresponds to an increase of 5% and '95' corresponds to a reduction of 5%, in the amount field for the wage type in the master data.

© SAP AG HR400 8-19

SAP AG 1999

Processing Averages in the Schema

XT00.MOD XMOD GENRAB.DAYPR TC00.PAB.P2010 X930 GEN NOAB.PIT X015 GENAVERA.


Determine payroll modifiersImport absences

Day processing of time data

Edit absence data


Valuation of time wage typeCalculation of averages

n Once time data and employee remuneration information have been processed, time wage types are entered in internal table IT. Personnel calculation rule X015 then determines which wage types only have a value in the NUM field. If a valuation basis has been specified for a relevant wage type, it is used in personnel calculation rule X115 to valuate the wage type.

n If processing class 15 has been maintained for the relevant wage type, personnel calculation rules X016, X017 and X018 are used to calculate the averages.

n The AVERA function selects the wage types that are to be evaluated in accordance with the new average calculation procedure (from 4.6A).

© SAP AG HR400 8-20

SAP AG 1999

Averages: Summary (1)

l Time wage types can be evaluated using the average values of wage types if an average value was assigned in Customizing. The average valuescan be calculated from wage types from periods already included in a payroll run and/or from the current period.

© SAP AG HR400 8-21

SAP AG 1999

Averages: Summary (2)

l To calculate average values, you must specifyhow the relevant wage types are to be includedin the valuation bases. The number of payroll periods required already included in a payroll run is entered in the calculation rule. You can run a relevancy check for each period. The cumulation rule determinesthe type of cumulation used to calculate theaverage bases for the relevant periods. Changes in pay can be stored in the adjustment rule.

l The average values calculated can be frozen.

© SAP AG HR400 8-22

Averages-Exercises: New Averages

Unit: Averages

Topic: Creating Average Calculation Bases

• Creating average calculation bases from overtime remuneration.

Your company decides to change vacation bonus provisions. Instead of a fixed amount per leave day, the average of all remuneration paid for overtime over the past four payroll periods will be paid for each leave day.

To create the average calculation bases, you must flag the following time wage types:

- 3nn1 Up to 2 hours overtime - 3nn2 3 or more hours overtime - 3nn3 Overtime on Sundays - 3nn4 Overtime on public holidays

and the derived bonus wage types 3nn5 - 3nn8 as relevant for the calculation of averages.

The contents of the AMT (amount) field for wage types 3nn1 to 3nn4 must be added to the average basis /201.

The total amount for the bonus wage types 3nn5 to 3nn8 must be added to the average basis /202.

This ensures that /201 contains all overtime remuneration, and that /202 contains the bonuses for the calculation of averages.

Run payroll for period 05, together with a forced retroactive accounting run for the previous periods. Check that the wage types have been created. Exit the payroll run.

The validity period of the Customizing entries for the average calculation procedure runs from January 01 of the relevant calendar year until December 12, 9999

© SAP AG HR400 8-23

Unit: Averages

Topic: Average Calculation Rules

• Creating cumulation rules for average bases

• Adjusting personnel calculation rule X018 to meet customer requirements.

• Creating a final processing rule

• Creating an average calculation rule

• Assigning an average calculation rule to a wage type

Until now, your company has constantly valuated wage type 40nn with 20.00 per leave day. From payroll period 06 onwards, employees will be paid the average of all the overtime remuneration paid over the past three payroll periods for each leave day.

1. Valuation of wage type 40nn Vacation bonus, which was previously constant at 20, must now be delimited. Delimit the existing entry for the wage type to the start date of payroll period 06, and remove the indicator for constant valuation from the new record.

2. Payment must be made in the period for which payroll is being run, that is, absence valuation for wage type 40nn must be set to ‘I’.

3. Create a cumulation rule for both the cumulation of overtime remuneration in wage type /201 and for the cumulation of the bonuses in /202. The contents of the AMT field should be cumulated positively. Call your cumulation rule ZC## (## = group number), for example, ZC01 for group 1.

4. Adjust the average formula. Copy personnel calculation rule X018 to Z8## and store an average calculation formula that divides the average of the total cumulated average calculation formulas by the standard number of workdays in three payroll periods.

5. Create your final processing rule ZE## with your personnel calculation rule Z8##.

6. Now, set up your calculation rule for averages, ZA##.

7. For your wage type 40nn, store the assignment to your average calculation rule.

8. Enter a few days leave for your employee in payroll period 06, release and then start payroll for the period.

© SAP AG HR400 8-24

Unit: Averages

Topic: Adjusting Average Calculation Bases

• Adjusting the average calculation bases when there is a change in remuneration.

The new vacation bonus provision in your company specifies that an employee's vacation bonus must be adjusted to increases in his/her pay. The bases for calculating average values must therefore be adjusted by the relevant factor in the three previous payroll periods. The factor is determined by the difference in valuation basis /001 before and after the increase in pay.

1. Increase your employee's basic pay from the start of payroll period 06 by increasing direct bonus wage type 50nn (nn = group number) to 500.00.

2. Now, create the adjustment rule ZJ## for your calculation rule ZA## (## = group number).

3. Finally, modify your cumulation rule ZC##, by entering your adjustment rule in the AMT field.

4. Repeat the payroll run for payroll period 06.

© SAP AG HR400 8-25

Unit: Averages

Topic: Frozen Averages

• Freezing the average value for an absence covering several payroll periods

The new vacation bonus provisions in your company specify that an employee's vacation bonus must be constant for all leave days. To also guarantee that this is the case for absences covering several payroll periods, the calculated average value in the period, in which the absence starts, must be frozen for the duration of the absence.

1. Modify your calculation rule ZA## (## = group number).

2. Finally, enter additional leave for your employee starting in payroll period 05 and ending in period 06. Repeat the payroll run for payroll period 06 and check the log. Finally, exit the payroll run.

© SAP AG HR400 8-26

Exercises: Old Averages

Unit: Averages


• Creating average calculation bases from overtime remuneration.

Your company decides to change vacation bonus provisions. Instead of a fixed amount per leave day, the average of all overtime remuneration paid over the past four payroll periods will be paid for each leave day.

To create the average calculation bases, you must flag the following time wage types:

- 3nn1 Up to 2 hours overtime - 3nn2 3 or more hours overtime - 3nn3 Overtime on Sundays - 3nn4 Overtime on public holidays

and the derived bonus wage types 3nn5 - 3nn8 as relevant for the calculation of averages.

The contents of the AMT (amount) field for wage types 3nn1 to 3nn4 must be added to the average basis /201.

The amount of the bonus wage types 3nn5 to 3nn8 must be completely added to the average basis /202.

This ensures that /201 contains all overtime remuneration, and /202 contains the bonuses for the calculation of averages.

Run payroll for period 05, together with a forced retroactive accounting run for the previous periods. Check that the wage types have been created. Exit the payroll run.

© SAP AG HR400 8-27

Unit: Averages


• Adding further specifications to a processing class

• Coding wage types for valuation with an average value.


• Creating average calculation rules and cumulation rules.

• Checking the relevancy of previous periods for the calculation of averages.


Until now, your company has constantly valuated wage type 40nn with 20.00 per leave day. As of payroll period 06, employees will be paid the average of all overtime remuneration paid over the past four payroll periods for each leave day.

1. You must now delimit valuation of wage type 40nn Vacation Bonus, which was previously constant at 20. Delimit the existing entry for the wage type with the start date of payroll period 06, and remove the indicator for constant valuation from the new record.

2. Payment must be made in the period for which payroll is being run, in other words, absence valuation for wage type 40nn must be set to ‘I’.

3. To valuate a wage type using an average value, you must code the wage type in processing class 15 with the specification that corresponds to the relevant average calculation rule. To enter your own average calculation rules in the system, you must first of all create a new specification for each calculation rule in processing class 15. Add the specification of processing class 15 planned for your group. Note: For technical reasons, specifications of processing class 15 are used that are outside the customer name range (Z):

Group 01 = I Group 07 = O Group 13 = U Group 02 = J Group 08 = P Group 14 = V Group 03 = K Group 09 = Q Group 15 = W Group 04 = L Group 10 = R Group 16 = X Group 05 = M Group 11 = S Group 17 = Y Group 06 = N Group 12 = T Group 18 = Z

© SAP AG HR400 8-28

4. Code wage type 40nn in processing class 15 with the specification for your group.

You have made all the necessary preparations in the area of wage types for the new averages rule. Now, you must make sure that the system accesses the average calculation rule in your schema when valuating wage types. You have already created your own specification for processing class 15, and coded wage type 40nn accordingly. Personnel calculation rule X016 queries processing class 15, and the specification tells the system which average calculation rule should be used.

5. Copy personnel calculation rule X016 to the name Z6nn (nn = group no.) and modify it by adding a line for your specification of the processing class when processing class 15 is queried. You must assign average calculation rule zz to operation MEANV. (zz = 10 + Group number)

The modified subschema ZTnn accesses the valuation of time wage types in the line PIT X015 GEN. Rule X015 calls continuation rule X016. However, you previously created a modified version of rule X016 and named it Z6nn. Therefore, you now also require a modified version of rule X015 that is accessed from the modified subschema ZTnn.

6. Copy personnel calculation rule X015 to Z5nn (nn = group number), and change access of rule X016 accordingly.

7. Change modified subschema ZTnn in the line that accesses time wage valuation.

8. To prepare for creation of the average calculation rules, copy personnel calculation rule X018 to Z8nn (nn = group number).

In personnel calculation rule Z6nn, you already created a link between your specification in processing class 15 and average value calculation rule zz. Now you must create the average calculation rule zz as well as cumulation rule zz, and set up final processing in rule Z8nn.

9. Create the average calculation rule zz. Set the number of relevant previous periods and the maximum number of previous periods to 4. In the Cumulation rule field, enter the same value as for the averages rule.

10. Define cumulation rule zz by taking all the overtime remuneration (/201) into account.

Note: Once you have completed the exercise, you can modify the cumulation rule and also include the bonuses (201 + /202) for cumulation. Test this scenario as well.

11. Create an average calculation formula in rule Z8nn that divides the total of all cumulated overtime remuneration by the average number of workdays in four payroll periods.

12. Enter a few days leave for your employee in payroll period 06, release and then start payroll for the period.

© SAP AG HR400 8-29

Unit: Averages


• Adjusting the average calculation bases when there is a change in remuneration.

The new vacation bonus provisions in your company specify that an employee's vacation bonus must be adjusted to increases in his/her pay. The average calculation bases of the last three previous periods must therefore be adjusted by the relevant factor. The factor is determined by the difference in valuation basis /001 before and after the increase in pay.

1. Increase your employee's basic pay from the start of payroll period 06 by increasing the direct bonus wage type 50nn (nn = group number) to 500.00.

2. Create adjustment rule zz for your calculation rule zz. You must enter a relevant modification indicator in the AMT (amount) field for the adjustment type. Also specify the number of previous periods to be taken into account. With regard to your employee, at least three periods must be taken into account for the increase factor to be effective.

3. Repeat the payroll run for payroll period 06. Finally, exit the payroll run.

© SAP AG HR400 8-30

Solutions: New Averages

Unit: Averages


Identifying time wage types and the bonus wage types derived from them as relevant to the calculation of averages.

IMG à Payroll: International à Time Wage Type Valuation à Averages New à Create Bases for Calculating Average Values

Choose the action Calculating Average Bases from Wage Types.

For the overtime wage types 3nn1 – 3nn4, flag the Amount field and enter 100 in the Percentage field.

Then, select the bonus wage types 3nn5 – 3nn8, in order to copy them. In the Basis for calculating average field for the entries to be copied, enter /202. Also flag the Amount field and enter 100 in the Percentage field for these wage types.

Finally delete the entries for the bonus wage types 3nn5 – 3nn8 with the valuation basis /201!

Perform payroll for period 05:


Exit payroll:


© SAP AG HR400 8-31

Unit: Averages


1. Delimiting valuation of wage type 40nn, and deleting the identifier for constant valuation from the new record:

IMG à Payroll: International à Time Wage Type Valuation à Valuation Bases à Assigning Valuation Bases

Choose Delimit, and then enter the start date of payroll period 06. Edit the delimited entry by deleting K for the valuation basis.

2. Setting the valuation of absences for wage type 40nn to ‘I’:


Change your entry as follows: Abs.val.grp: yy Valuation rule: 01 Time: I

3. Creating cumulation rule ZC##:

IMG à Payroll: International à Time Wage Type Valuation à Averages New à Create Calculation Rule for Averages

Choose the action Cumulation Rules for Bases for Calculating Average Values. Create the following rule:

Cum.rule Av. basis RTE + NUM + AMT +

ZC## /201 ! +

ZC## /202 ! +

© SAP AG HR400 8-32

4. Modifying average formulas


Choose the action Modify average formula (personnel calculation rule). Copy rule X018 to Z8## and change your rule in the fo llowing way:

5. Create final processing rule ZE##:


Choose the action Final processing rules for averages. Create the following rule :

Final processing Formula

ZE## Z8##

6. Create calculation rule for averages ZA##:


Choose the action Create calculation rules for averages.

Create the following rule:

Av.rule Cum. rule Fin.processing Rel. av.per. Time unit

ZA## ZC## ZE## 3 1

NUM=pauschalierte Anzahl

AMT=M

DIVID ANR

© SAP AG HR400 8-33

7. Assign average calculation rule wage type 40nn:

IMG à Payroll: International à Time Wage Type Valuation à New Averages à Assign the Valuation of Averages to a Primary Wage Type

Create the following entry:

WT Av.rule

40nn ZA##

8. Check averages processing:



© SAP AG HR400 8-34

Unit: Averages


1. Increase basic pay by direct bonus wage type 50nn (nn = group number):

Human Resources à Personnel Management à Administration à Maintain Master Data

2. Create adjustment rule ZJ##:


Choose the action Create adjustment rules.


Adj.rule Adj.type +/- Com.wage type Modif.per. Time unit

ZJ## 4 P /001 3 1

3. Change cumulation rule ZC##:


Choose the action Cumulation Rules for Bases for Calculating Average Values. Change your rule:

Cum.rule Av. basis . . . . AMT + Adjustment rule

ZC## /201 . . . . ! + ZJ## ZC## /202 . . . . ! + ZJ##

4. Repeat the payroll run for payroll period 06:


© SAP AG HR400 8-35

Unit: Averages

Topic: Frozen Averages

1. Modify calculation rule for averages ZA##:


Choose the action Create calculation rules for averages.

Change your rule:

Av.rule Cum. rule Fin.processing Rel. av.per. Time unit freeze

ZA## ZC## ZE## 3 1 A

2. Repeat the payroll run for payroll period 06 and exit:


Human Resources à Payroll à International à Payroll à Exit payroll

© SAP AG HR400 8-36

Solutions: Old Averages

Unit: Averages


Identifying time wage types and the bonus wage types derived from them as relevant to the calculation of averages.

IMG à Payroll: International à Time Wage Type Valuation à Averages à Create Bases for Calculating Average Values

Set flags in the following lines for wage types 3nn1 – 3nn4:

AMT x /201 x

Select AMT for the bonus wage types x /202 x


© SAP AG HR400 8-37

Unit: Averages


1. Delimiting valuation of wage type 40nn, and deleting the identifier for constant valuation from the new record:

IMG à Payroll: International à Time Wage Type Valuation à Valuation Bases à Assigning Valuation Bases

Choose Delimit, and then enter the start date of payroll period 06. Edit the delimited entry by deleting K for the valuation basis.

2. To valuation of absences must be set to the time ‘I’ for wage type 40nn:


Change your entry as follows: Abs.val.grp: yy Valuation rule: 01 Time: I

3. Create a specification in processing class 15:

IMG à Payroll: International à Basic Settings à Environment of Wage Type Maintenance à Processing Classes and Evaluation Classes à Maintain Processing Classes and Their Specifications

Select processing class 15 and use navigation to choose the specifications. Then, add your new entry.

4. Code wage type 40nn with a specification in processing class 15:

IMG à Payroll: International à Time Wage Type Valuation à Averages à Assign the Valuation of Averages to a Primary Wage Type

5. Copy and modify rule X016:

IMG à Payroll: International à Time Wage Type Valuation à Averages à Adjust Calculation of Averages Within the Payroll Run à Copy ‘special processing for time wage type valuation’ rule

from rule X016 to rule Z6nn

© SAP AG HR400 8-38

6. Copy rule X015, and change the access of rule X016:

IMG à Payroll: International à Time Wage Type Valuation à Averages à Adjust Calculation of Averages Within the Payroll Run à Copy ‘valuation of wage types rule’

from rule X015 to rule Z5nn

In rule Z5nn, change the line that accesses rule X016: from GCY X016* to GCY Z6nn*

7. Change modified subschema ZTnn in the line that accesses the valuation of time wage types:

IMG à Payroll: International à Time Wage Type Valuation à Averages à Adjust Calculation of Averages Within the Payroll Run à Enter Modified Personnel Calculation Rule in Schema

The IMG offers you schema XT00 for processing. To edit your schema, choose Schema à Different schema, and enter ZTnn.

Change the line specifying PIT X015 GEN to PIT Z5nn GEN.

8. Copy personnel calculation rule X018:

IMG à Payroll: International à Time Wage Type Valuation à Averages à Create Final Processing Rule

Copy from rule X018 to rule Z8nn

9. Create average calculation rule xx:

IMG à Payroll: International à Time Wage Type Valuation à Averages à Create Calculation Rule for Averages


Rule Rel.test Cumulation F.process. Max.no.per No.rel.per

zz X017 zz Z8nn 4 4

© SAP AG HR400 8-39

10. Define cumulation rule xx:

IMG à Payroll: International à Time Wage Type Valuation à Averages à Create Cumulation Rules for Bases for Calculating Averages


Cumulation WT CumNUM CumRTE CumAMT Adjust.

zz /201 +

You can also create the following cumulation rule:

zz /202 +

11. Create a final processing rule:

IMG à Payroll: International à Time Wage Type Valuation à Averages à Create Final Processing Rule

Change rule Z8nn:

12. Check averages processing:



NUM=pauschalierte Anzahl

AMT=M

DIVID ANR

© SAP AG HR400 8-40

Unit: Averages


1. Increase basic pay by direct bonus wage type 50nn (nn = group number):


2. Create adjustment rule zz for calculation rule zz:

IMG à Payroll: International à Time Wage Type Valuation à Averages à Create Cumulation Rules for Bases for Calculating Averages

Change cumulation rule zz by entering adjustment rule zz in the field Adjustment. Then, use navigation to access the adjustment rules for the average calculation bases and create the following rule:

Adjustment . . . IndAMT VBasisID . . . No.period

zz 4 01 3

3. Repeat the payroll run for payroll period 06:



© SAP AG HR400 9-1

SAP AG 1999

Factoring

l The Factoring Conceptl Partial Period Factorsl Personal Work Schedulel Partial Period Parametersl Factoring Methodsl Personnel Calculation Rules for Factoringl Assigning Partial Period Factorsl Valuating Elements of Remunerationl Creating Wage Types for Cost Accountingl Creating Hourly Rates for Cost Accountingl Factoring in the Schema

Contents:

© SAP AG HR400 9-2

SAP AG 1999

Factoring: Unit Objectives


l Describe the factoring concept and diversefactoring methods.

l Create personnel calculation rules to calculate partial period factors, and assignthe factors to the wage types to be factored.

l Explain how to create wage types for Cost Accounting.

© SAP AG HR400 9-3

SAP AG 1999


Payroll Basics

Starting Payroll


Wage Type Valuation

Averages


Factoring



© SAP AG HR400 9-4

SAP AG 1999

The Factoring Concept

l Reduction in payn Joining or leaving company during payroll period

n Unpaid absences

n Paid absences

n Inactive work relationship

l Calculation of pay for exact periodsn Changes to basic pay

n Change in organizational assignment

n Change in personal work schedule

l Calculation of cost accounting wage typesfor exact periods

n Within SAP Payroll, factoring describes the pro rata calculation of remuneration for an exact period. Periodic remuneration consists of primary wage types assigned to an employee as basic pay, recurring payments, or additional payments. Factoring only covers the events that occur in the current period.

n During the payroll run, the system evaluates changes relevant to factoring in the following infotypes:

• Personnel Actions (0000)

• Organizational Assignment (0001)

• Planned Working Time (0007)

• Basic Pay (0008)

• Recurring Payments/Deductions (0014)

• Additional Payments (0015)

• Absences (2001)

If a situation arises during the payroll run that triggers factoring, the current factor is calculated and then multiplied by the wage type assigned.

© SAP AG HR400 9-5

SAP AG 1999

Factoring: Periodic Remuneration

l In the Caliber ‘A’ Bicycle Company,an employee’s remuneration changes in the middle of the payroll period.

© SAP AG HR400 9-6

SAP AG 1999

Partial Period Factors

M020M020

Table IT before factoring

0102

3,0003,500

Partial period factor

Partial period 01 = ~ 0.5Partial period 02 = ~ 0.5

M020M020

Table IT after factoring

0102

1,5001,750

Change in basic pay midwaythrough the payroll period

Multiplied by partial period factor

n In payroll, a factor is required to calculate partial period amounts.

n The partial period factor is a value between 0 and 1. As soon as changes are made to master data that trigger factoring, the factor is multiplied by the employee's primary wage types for exact periods if the primary wage types must be reduced, or if their constituents for exact periods must be calculated separately.

n The calculation of partial period factors is always based on times that result, for example, from the employee's personal work schedule or absences.

© SAP AG HR400 9-7

SAP AG 1999

Personal Work Schedule

Date DWS Daily Day type PHol Variant DWS Period Hours Active grpg WS class class WS

31.12.1998 01 FLEX 0 0 5 FLEX 8,00 01.01.1999 01 FLEX 1 1 5 FLEX 8,00 X 02.01.1999 01 FLEX 0 0 B 5 FLEX 5,00 X 03.01.1999 01 OFF 0 0 0 FLEX 0,00 X 04.01.1999 01 OFF 0 0 0 FLEX 0,00 X 05.01.1999 01 FLEX 0 0 5 FLEX 8,00 X 06.01.1999 01 FLEX 0 0 5 FLEX 8,00 X 07.01.1999 01 FLEX 0 0 5 FLEX 8,00 X 08.01.1999 01 FLEX 0 0 5 FLEX 8,00 X 09.01.1999 01 FLEX 0 0 B 5 FLEX 5,00 X 10.01.1999 01 OFF 0 0 0 FLEX 0,00 X 11.01.1999 01 OFF 0 0 0 FLEX 0,00 X

......

27.01.1999 01 FLEX 0 0 5 FLEX 8,00 X 28.01.1999 01 FLEX 0 0 5 FLEX 8,00 X 29.01.1999 01 FLEX 0 0 5 FLEX 8,00 X 30.01.1999 01 FLEX 0 0 B 5 FLEX 5,00 X 31.01.1999 01 OFF 0 0 0 FLEX 0,00 X 01.02.1999 01 OFF 0 0 0 FLEX 0,00 X

0 = No public holiday1 = Public holiday2 = Half-day pub. hol.

0 = Day off1 - 9 = Can be defined

freely

0 = Work/paid1 = Day off/paid2 = Day off/unpaid3 = Special day

n At the start of subschema XT00, function GENPS generates the personal work schedule for the personnel number for which payroll is being run. For time data evaluation, each employee is assigned to a general work schedule (infotype 0007) which defines planned working time on the basis of the relevant employee's work center assignment. If the employee is assigned to different work schedules during a payroll period due to a change of work center or substitution (infotype 2003), his or her planned working time will comprise several general work schedules.

n The above diagram is an excerpt of table PWS for one personnel number with a monthly payroll period. The table specifies the last day of the previous payroll period and the first day of the subsequent payroll period as the system requires this data if, for example, the relevant day is a public holiday.

© SAP AG HR400 9-8

SAP AG 1999

Displaying Partial Period Parameters (1)

No

0102

From To

15.0016.00

31.00

KSoll ASoll

11.0011.00

22.00

SSoll

78.8082.60

161.40

KDiv I

31.0031.00

31.00

ADiv I

22.0022.00

22.00

SDiv I

161.40161.40

161.40

KDivP

30.0030.00

30.00

ADivP

22.0022.00

22.00

SDivP

156.48156.48

156.48

T

G

No

0102

From To

0.002.00

2.00

KAU** AAU**

0.001.00

1.00

SAU**

0.008.00

8.00

KAP**

4.001.00

5.00

AAP**

4.001.00

5.00

SAP**

32.008.00

40.00

KAX**

1.000.00

1.00

AAX**

1.000.00

1.00

SAX**

8.000.00

8.00

T

G

T = Partial periodG = Whole period

K = Calendar daysA = WorkdaysS = Hours

Unpaidabsences

Paidabsences Public holidays

Total working time projectedfor period

Payrollconstants

n At the start of subschema XT00, function PARTT accesses data from the personal work schedule (table PSP) to determine the partial period factors for the payroll period. If required, substitutions can also be taken into account.

n The total working time for the partial periods is calculated by applying the relevant partial period of the valid work schedule to the other partial periods of the payroll period.

n You maintain constants ADIVP and KDIVP in accordance with the time unit of the payroll period in the view Payroll Constants for Time Unit.

n Planned working time according to the employee's personal work schedule (PSP) for a specific basic pay period. KSOLL: Planned work measured in calendar days. ASOLL: Planned work measured in workdays. SSOLL: Planned work measured in working hours.

n Unpaid absences (for a specific basic pay period) possibly weighted. KAUxx: Unpaid absence measured in calendar days. AAUxx: Unpaid absence measured in workdays. SAUxx: Unpaid absence measured in working hours. Either xx = nn stands for the unpaid absence counting class, or xx = ** stands for the sum of all unpaid absences (for all counting classes).

n Total working time for the payroll period in accordance with the employee's work schedule for a specific basic pay period. KDIVI: Total working time measured in calendar days. ADIVI: Total working time measured in workdays. SDIVI: Total working time measured in working hours.

© SAP AG HR400 9-9

SAP AG 1999

Displaying Partial Period Parameters (2)

No

0102

From To

15.0016.00

31.00

KSoll ASoll

11.0011.00

22.00

SSoll

39.4082.60

122.00

KDiv I

31.0031.00

31.00

ADiv I

22.0022.00

22.00

SDiv I

80.70161.40

122.00

KDivP

30.0030.00

30.00

ADivP

22.0022.00

22.00

SDivP

78.24156.48

156.48

T

G

Total working time projectedfor the period

Payrollconstants

No

0102

From To

0.002.00

2.00

KAU** AAU**

0.001.00

1.00

SAU**

0.008.00

8.00

KAP**

4.001.00

5.00

AAP**

4.001.00

5.00

SAP**

32.008.00

40.00

KAX**

1.000.00

1.00

AAX**

1.000.00

1.00

SAX**

8.000.00

8.00

T

G

Unpaid absences

Paidabsences Public holidays

T = Partial periodG = Whole period

K = Calendar daysA = WorkdaysS = Working hours

n In this example, the employee is a part-time worker in the first half of the payroll period with an employment percentage of 50%.

n In the second half of the payroll period, the employee is a full-time worker with a 100% employment percentage.

n The total working time SDIVI of both partial periods is calculated by applying the respective partial period of the valid work schedule to the rest of the payroll period.

n GSSOLL contains the employee's planned hours from the first to the last day of the payroll period, and equals GSDIVI in this example. If, for example, the employee joins the company on the fifth day of the payroll period, GSSOLL will contain a smaller value than GSDIVI because the planned hours are only counted from the day the employee joins the company.

© SAP AG HR400 9-10

SAP AG 1999

Factoring: Reduction in Pay

l In the Caliber ‘A’ Bicycle Company,an employee leaves the company two daysbefore the end of the payroll period.

© SAP AG HR400 9-11

SAP AG 1999

Formula for the Deduction Method

Factor = 1 -Absence ----------------------------------------General period working time

General period working time - absence-------------------------------------------------------General period working time

=

Problem: Many absences during monthly payroll

Long month

-0.097 ---------------167.7 - 184

167.7Claims on employee

Short month

0.14 ---------------167.7 - 144

167.7Pay despite absence for whole period

n The deduction method multiplies the employee's hourly/daily rate by the number of unpaid times, and deducts the result from the employee's pay. The number of working hours specified per period is used as the divisor.

n If payroll is run for monthly periods, the general divisor determines that each calculation unit (hour or day) has the same value irrespective of whether the period is a long or short month.

n The deduction method is not suitable to use in the following situations:

n In the long months, such as July, a large number of absences could result in negative remuneration, that is, money would be claimed from the employee.

n If payroll is run for the employee on a monthly basis (monthly or half-monthly) and the employee has many unpaid absences. In short months, such as February, the employee could be absent for the entire month and still receive remuneration.

n If partial remuneration must be calculated for exact periods. The employee would receive an amount that is different from the amount of remuneration effected for the period, because the number of hours or days does not correspond to the average.

© SAP AG HR400 9-12

SAP AG 1999

Formula for the Payment Method

Factor =1-------------------------------------------------------------

General period working time

Planned working time - Absence----------------------------------------------General period working time

=

Problem: Few absences during monthly payroll

Long month

-1.049 ----------184 - 8

167.7Pay too high despite absence

Short month

0.906 ----------160 - 8

167.7Large reduction for few absences

* (Planned working time - Absence)

n In the payment method, the employee is remunerated for the period actually worked or for paid absences. The hourly or daily rate for the payroll period is calculated based on the amount of remuneration agreed and multiplied by the number of hours or days to be paid. The number of working hours specified per period is used as the divisor.

n If payroll is run for monthly periods, the general divisor determines that each calculation unit (hour or day) has the same value irrespective of whether the period is a short or long month.

n It is not suitable to use the payment method in the following situations:

n In long months , such as July, few absences could result in a factor that is greater than one; that is, the employee would be paid too much.

n In short months, such as February, the employee could work almost the entire period and still earn considerably less.

n If partial periods are calculated for exact periods, the employee would receive an amount that is different from the amount of remuneration effected for the period, because the number of hours or days does not correspond to the average.

n In practice, a hybrid of both the payment and deduction methods is often used: The deduction method is used for up to 10 absence days, and the payment method for more than 10 absence days. However, this procedure also causes problems, because changing from the deduction to the payment method gives rise to great differences in the valuation of remuneration. This can lead to unwanted situations.

© SAP AG HR400 9-13

SAP AG 1999

Formula for the PWS Method

Factor =1---------------------------------------------------------------------

Period working time according to PWS

PWS planned working time - Absence------------------------------------------------------Period working time according to PWS

=

Problem: Reduction factors of varying size

Long month

0.957 ----------184 - 8

184 The hourly rate is lower in long months than in short monthsShort month

0.950 ----------160 - 8

160

* (PWS planned working time - Absence)

n In the PWS method, the individual, actual planned working time according to the employee's personal work schedule (PWS) is used as the divisor.

n The PWS method is particularly suitable for reductions if planned working time is specified exactly and all deviations from planned working time are entered in the system.

n Deviations that frequently occur from planned working time are the result of changes to the following infotypes:

• Absences (2001)

• Substitutions (2003)

• Planned Working Time (0007)

n The PWS method is also suitable for calculating partial payments for exact periods.

© SAP AG HR400 9-14

SAP AG 1999

Secondary Wage Types for Period Factors

33...3

33...3

Table IT

/801/802

/816

/801 /802

/816

0101

01

0202

02

NUM RTE

100,000100,000

100,000

100,000 100,000

100,000

AMT

FunctionGEN/8

n Function GEN/8 generates secondary wage types /801 to /816. Factoring values are assigned to these secondary wage types during calculation.

n By accessing GEN/8, the system determines the following:

• Secondary wage types /801 to /8nn are generated and written to the input table (IT) for each WPBP split period.

• The factor is set at 1 in each secondary wage type /8nn generated and then multiplied by the constant GENAU 100,000.00 to increase the accuracy of the calculations. The result is written to the Rate (RTE) field.

n In the standard system, 16 secondary wage types are generated for the partial period factors. You can use 9 of these secondary wage types for your own partial period factors. Secondary wage types /810 to /816 have a meaning within the system.

© SAP AG HR400 9-15

SAP AG 1999

XPP1

Calculate partial period factors

Personnel Calculation Rules for Factoring

no

XPPF XPP0 + XPP1 Determine partial period factors

XPP0

- Unpaid absence?- Change in basic pay?- Employee joined in payroll period?- Employee left in payroll period?

XPPF

Inactive work relationship the entire period?

no

yesEXIT

n Personnel calculation rule XPPF is accessed in subschema XAL0 according to wage types /801 to /816 to calculate partial period factors.

n Depending on the check results from operation PPPAR, personnel calculation rule XPPF accesses personnel calculation rules XPP0 and XPP1 for wage types /801 and /802.

n Personnel calculation rule XPPF calculates the following factors for Cost Accounting:

• /810 Difference between the working time for the current period and the average working time

• /814 Share of paid public holidays on which there is no work

• /815 Share of work on public holidays and paid absences

• /816 Share of unpaid absences

© SAP AG HR400 9-16

SAP AG 1999

Determining Partial Period Factor /801

RTE=TSSOLL

Determine partial period factorsXPP1

E /801

*E

Partial period factor in wage type /801

RTE-TSAU**

RTE*KGENAU

Planned work in hours

Minus unpaid absences

Multiplied by factor

Divided by total working time RTE/TSDIVI

ADDWT *

PWS planned working time - Unpaid absencesMonthly working time according to PWS

PWS method:

n Wage type /801 contains a partial period factor that is determined using the PWS method.

n Personnel calculation rule XPP1 is accessed in subschema XAL9 from personnel calculation rule XPPF for each wage type.

© SAP AG HR400 9-17

SAP AG 1999

RTE=GASOLL

RTE-GAAU**

RTE-GAAP**

Determining Partial Period Factor /802

E RTE?0

Determine partial period factorsXPP0

E /802

*E

*E

RTE=0

ADDWT *

>E

RTE*KGENAU

RTE/TADIVI

ADDWT *

Partial period factor in wage type /802

Planned workdays

Minus unpaid absences

Minus paid absences

RTE = 0?

Set RTE = 0

Put wage type in OT

Multiplied by 100,000

Division

n The partial period factor in wage type /802 is calculated using the following formula:

n Planned working time - Unpaid absences - Paid absences Planned working time

n You can use partial period factor /802 to only remunerate the constituent parts of an employee's pay (for example, transportation allowance) on the days in the payroll period the employee actually worked.

© SAP AG HR400 9-18

SAP AG 1999

Assigning Partial Period Factors

WType

Processing class

Specification

M020 Monthly salary

10 Identify wage type for factoring

1 Reduction with factor /801

n The reduction factor for primary wage types is assigned to processing class 10.

© SAP AG HR400 9-19

SAP AG 1999

Valuating Payroll Elements

E VWTCL 10

E 0

ADDWT *

Valuate payroll elements using partial period factorsXVAL

E ****

3E

*E

ERROR

E 1

UsingUsing ES ES grouping grouping 3 wage/ 3 wage/time type **** astime type **** as an an example example

ELIMI *RESET RARTE= /801

RESET *MULTI RAA

AMT/KGENAUZERO= R

ADDWT *

Processing class 10

Cancel processing

Put wage type in OT

Set time period indicatorTransfer partial period factor

Set time period indicatorMultiply R*A=A

Divide by 100,000Set RTE to zero

Put wage type in OT

Eliminate time period indicator

n Personnel calculation rule XVAL multiplies the amount of the wage type to be factored by the partial period factor. If the wage type to be factored has specification 1 in processing class 10, for example, the system uses the factor in the RTE field of wage type /801 for the multiplication. The result of the multiplication is stored in the AMT field of the factored wage type.

n ELIMI The entries in the work tables (IT, OT, RT,…) are assigned to various validity periods in basic data (such as work center, taxation, cost distribution) by means of split indicators. This allows the system to create exact time references for wages/salary earned and to calculate and distribute costs. If it is no longer necessary to distinguish between partial periods for one of the feature classes in the wage type currently being processed, you can remove the corresponding split indicator using the operation ELIMI. You can specify up to 3 split indicators as parameters, or enter * for all of them.

n RESET This operation resets the time period indicators (split indicators).

n Examples:

* All indicators

R Employee subgroup grouping for personnel calculation rule

A Work center indicator (WPBP)

© SAP AG HR400 9-20

SAP AG 1999

Creating Wage Types for Cost Accounting

WType

Processing class

Specification

M020 Monthly salary

31 Allocate monthly lump sums to CO

1 Calculate paid public holidays

n To create the amount paid as continued pay for paid absences (leave, sickness, public holidays), all of the basic pay wage types must have a specification in processing class 31.

n Processing class 31 can have the following specifications:

0 Wage type does not lead to cost center debits/credits

1 Calculate paid public holidays

2 Calculate total paid non-work

3 Calculate paid non-work and unpaid absence time

n Personnel calculation rule XCM0 is accessed by subschema XAL9 to distribute remuneration elements to secondary wage types for Cost Accounting. The payments made to an employee are divided into productive and unproductive parts for exact periods. Depending on the specification, the amount field (AMT) is filled with the following wage types:

n /840 Difference between working hours in current month and average value /844 Paid public holidays /845 Total paid non-work /846 Total unpaid absences.

© SAP AG HR400 9-21

SAP AG 1999

NUM=TSDIVI

NUM-TSDIVP

ADDWTI/840

NUM=TSAX**

ADDWTI/844

Creating Hourly Rates for Cost Accounting

Supply Cost Accounting (CO) with number of hoursXCH0

E ****

*E

NUM=TSAX**

NUM+TSAP**

ADDWTI/845

NUM=TSAU**

ADDWTI/846

General working time in partial period

Put wage type in IT

Paid public holidays in partial period

Put wage type in IT

Paid public holidays in partial period

Paid absences in partial period

Put wage type in IT

Total working time in partial period

Unpaid absences in partial period

Put wage type in IT

n In personnel calculation rule XCH0, the number (NUM) field of the wage types /840, /844, /845 and /846 is filled with hours. The amount (AMT) fields in personnel calculation rule XCM0 already contain values.

n Subschema XAL0 accesses personnel calculation rule XCH0 a single time using function ACTIO. Operation ADDWTInnnn inserts wage types with the designation nnnn into the input table. As the wage types specified in the personnel calculation rule already exist in table IT, only the NUM field changes for the existing wage types.

© SAP AG HR400 9-22

SAP AG 1999

Factoring in Schemas

XT00.GENPSGENPS ** *.PARTT.P2003 S**.PAB


Generate personal work schedule PWSGenerate PWS with shift substitutions

Partial period parameter

Import shift substitutions into PWS

Edit absence data

XAL9GEN/8 16PIT XPPF NOABPIT XCM0 P31 PIT XVAL P10ACTIO XCH0 A.

Factoring and storage INTERN.Create wage types /801 - /816 in ITDetermine partial period factorsMonthly lump sums for Cost AccountingValuate remuneration elementsHourly rates for Cost Accounting

n At the start of subschema XT00, function GENPS generates the personal work schedule for the personnel number for which payroll is being run. Substitutions (infotype 2003) that are relevant for the work schedule may either be taken into account when setting up table PWS or added at a later time.

n In the procedure shown, shift substitutions are not taken into account when setting up partial period parameters and factors as function P2003 imports them into table PWS at a later time.

n Table PARTT is complete once the absence data (PAB) has been edited

n In personnel calculation rule XVAL, the amount specified for the wage type to be factored is multiplied by the partial period factor (wage type /8nn).

© SAP AG HR400 9-23

SAP AG 1999

Factoring: Summary (1)

l Factoring is used to calculate remunerationfor exact periods. For example, it is requiredto reduce remuneration for unpaid absences,to account for changes in organizationalassignment, and in Cost Accounting. InPayroll, partial period parametersare created based on the employee’s work schedule, absences and public holidays. These parameters are used in personnel calculationrules to calculate partial period factors.

© SAP AG HR400 9-24

SAP AG 1999

Factoring: Summary (2)

l The partial period factors are stored inwage types /8nn during the payroll run.In processing class 10, the wage types to be factored are assigned a specification determining which factor (/8nn) they are to be multiplied by.

l Cost Accounting receives data on the productive and unproductive elements of an employee’s remuneration.

© SAP AG HR400 9-25

Exercises

Unit: Factoring

Topic: Determining and Assigning Reduction Factors

• Determining partial period factors according to the all-or-nothing method

• Assigning partial period factors to a wage type that is to be reduced

If the employee works on at least half the planned working days in the payroll period, your company will pay the full instructor's bonus. If the employee worked on less than half the planned working days, no instructor's bonus will be paid.

You will require a partial period factor that is determined in the time unit ‘workday’ using the formula planned working time - unpaid absences - paid absences. The reduction factor must be stored in wage type /803.

1. Using the IMG, make a copy of personnel calculation rule XPPF, and rename it ZPnn (nn = group number). In rule ZPnn, create a processing link to wage type /803.

2. Make a copy of subschema XAL9, rename it ZAnn, and adjust subschema ZAnn and your payroll schema Z0nn accordingly.

3. Assign a reduction factor to the wage type Instructor's bonus 60nn.

4. Assign an instructor's bonus of 100.00 to your employee's basic pay starting in payroll period 07. Finally, enter a period of leave in period 07.

5. Simulate the payroll run for period 07, and check that the personnel calculation rule ZPnn is correct.

© SAP AG HR400 9-26

Solutions

Unit: Factoring

Topic: Determining and Assigning Reduction Factors

1. Copy personnel calculation rule XPPF to ZPnn and create a processing link for wage type /803:

IMG à Payroll: International à Partial Period Calculation à Create Reduction Factors à Determine Partial Period Factors -Rule XPPF

Make a copy of rule XPPF, and rename it ZPnn. In the Wage type field, enter /803 and choose Change. Change rule ZPnn.

/803 Partial period factor 3

RTE=GASOLL

RTE-GAAU**

RTE-GAAP**

Set

Subtraction

Subtraction

RTE?Value Compare

RTE=0 Set

ADDWT * Outputtabelle

*

© SAP AG HR400 9-27

2. Make a copy of subschema XAL9, change access to personnel calculation rule XPPF, and include your copy of the subschema in payroll schema Z0nn:

Human resources à Payroll à International à Tools à Maintenance tools à Schema à Copy

from schema XAL9 to schema ZAnn

Change schema Zann from PIT XPPF ___ NOAB to PIT ZPnn ___ NOAB.

Human resources à Payroll à International à Tools à Maintenance tools à Schema à Change

Change schema Z0nn from COPY XAL9 to COPY ZAnn.

3. Assign a reduction factor to wage type 60nn:

IMG à Payroll: International à Partial Period Calculation à Assign Reduction Factors

Set processing class 10 to specification 3.

4. Assign wage type 60nn to the employee's basic pay, and maintain paid and/or unpaid absences:


Choose the Basic Pay infotype, and create a record specifying wage type 60nn. Then choose the Absences infotype , and maintain a paid and/or an unpaid absence.

5. Simulate the payroll run for the period, and check personnel calculation rule ZPnn:

Human resources à Payroll à International à Payroll à Simulation

RTE=1 Set

RTE*KGENAU Multiplication

ADDWT * Outputtabelle

>

© SAP AG HR400 10-1

SAP AG 1999


l Cumulating and Storing Time Wage Typesl Cumulating and Storing Basic Pay Wage Typesl Cumulation Wage Types from External Transfersl Updating Cumulation Wage Typesl Creating Cumulation WTs in Schemas

Contents:

© SAP AG HR400 10-2

SAP AG 1999

Cumulation Wage Types: Unit Objectives


l Code time and basic pay wage types for cumulation and storage in the results table.

l Code the cumulation and storage of wage types from external transfers.

l Determine which wage types are cumulated in the annual results table.

© SAP AG HR400 10-4

SAP AG 1999

Cumulating and Storing Time Wage Types

Table IT

/001M020M110M111.

17.05

17.054.26

1010

3,000170.50

42.60

Table OT

/001/101/201M020.

17.05213.10213.103,000

Cumulation of amounts into cumulation wage types /1nn and average bases /2nn

Table RT

./852.M110M111.

17.054.26

10

1010

170.5042.60

Storage of time wage types in the results table and accumulation of overtime into wage type /852

n At the end of subschema XT00, the wage types in the IT are processed in personnel calculation rule X020. The time wage types that no longer need to be processed, as they were already valuated using a valuation basis or using an average value, are now stored in the RT results tables and the amounts are added to the gross cumulation wage types /1nn and average bases /2nn. The overtime hours can be cumulated in wage type /852 .

n At this point in time, the basic pay wage types have not been through factoring in the payroll schema. For this reason, they cannot yet be stored in the results table.

© SAP AG HR400 10-5

SAP AG 1999

Cumulation WTs from Time-Based Payments

WT

Processing class

Specification

M110 Overtime hours

3 Cumulation and storage of time wage types

5 RT storage, cumulation, accumulation of OT

Cumulation

1 Total gross amount

10 Net payments/deduct.

X

n In processing class 3, you specify how each time wage type should be stored in the results table. You have the following options:

• The wage type is not stored in the results table but is transferred

• The wage type is stored in the results table without being cumulated

• The wage type is cumulated and stored in the results table

• The wage type is cumulated and stored in the results table, the hours for this wage type are also cumulated as overtime hours.

n At this point, wage types from the Basic Pay infotype (0008) must also be identified. They should not be transferred at this point, as the system needs them at a later stage in the payroll run.

© SAP AG HR400 10-6

SAP AG 1999

Cumulating and Storing Basic Pay Wage Types

Table IT

/001/101/201M020.

17.05213.10213.10

3,000

Table OT

/101

.

.

3,213.10

Cumulation of amounts incumulation wage types /1nn

Table RT

/001./852.M020M110M111.

17.05

17.054.26

10

1010

3,000170.50

42.60

Storage of wage types from the infotypes 0008,0014 and 0015 in theresults table

n At the end of subschema XAL9, the wage types in the IT are processed in personnel calculation rule X023. The wage types that no longer require processing are now stored in the RT results table, the amount fields are added to the gross cumulation wage types /1nn.

© SAP AG HR400 10-7

SAP AG 1999

Cumulation Wage Types Based on Master Data

WT

Processing class

Specification

M020 Monthly salary

20 Storage and cumulation

3 RT storage, cumulation

Cumulation

1 Total gross amount

10 Net payments/deduct.

X

n In processing class 20, you specify how each master data wage type should be stored in the results table. You have the following options:

• The wage type is not stored in the results table but is transferred unchanged

• The wage type is excluded

• The wage type is stored in the results table and is included in the cumulation wage types

• The wage type is stored in the results table without being cumulated

© SAP AG HR400 10-8

SAP AG 1999

Cumulation Wage Types from External Transfers

WT

Processing class

Specification

M500 Union contributions

25 Processing after end of payments/deductions

1 Summarized RT storage

Cumulation

10 Net payments/deduct. X

n In processing class 25, you specify how every wage type entered via the External Bank Transfers infotype (0011) should be processed in the personnel calculation rule X045. These wage types cannot be cumulated in gross cumulation wage types, as they are processed in the net part of the payroll run. You have the following options:

• Transfer unchanged

• Summarized RT storage with transfer ID.

n It is not possible to cumulate in wage type /110.

© SAP AG HR400 10-9

SAP AG 1999

Updating Cumulation Wage Types

Table RT

/001/101/852.M020M110M111.

17.05

17.054.26

10

1010

3,213.10

3,000170.5042.60

Table CRT

/101/852.M020M110M111.

10

1010

6,213.10

6,000170.5042.60

Cumulation of selectedwage types from the resultstable in the cumulationresults table

n For many wage types, you may want an overview of the annual values already cumulated (for example, for printing annual values from certain wage types on the payroll form). For this purpose, these wage types are transferred to the annual results table CRT.

n This takes place at the end of the payroll run with the help of the ADDCU function and processing class 30.

© SAP AG HR400 10-10

SAP AG 1999

Creating Annual Values

WT

Processing class

Specification

M020 Monthly salary

30 Update of cumulation wage types

3 Cumulate number in current year

n In processing class 30, you specify which wage types are cumulated in the annual results table CRT using the ADDCU function.

© SAP AG HR400 10-11

SAP AG 1999

Creating Cumulation WTs in Schemas

XT00.PIT X015 GEN. PIT X020 P03



Cumulation and RT storage

XAL9.ACTIO XCH0 A. PIT X023 P20 NOAB

Factoring and storage INTERN.

Hourly rates for Cost Accounting

Gross input and storage

XNN0.P0011 X055 GEN NOABPIT X045 P25.

Net payments/deducts.and transfers INTERN.

Read external transfers infotype 0011

Import payments/deductions to RT

XEND.ADDCU P30 .

Final processing INTERN.

Update cumulation wage types CRT

© SAP AG HR400 10-12

SAP AG 1999

Cumulation Wage Types: Summary (1)

l In processing class 3, you use coding to define in which cumulation wage types each time wage type is included and how it is stored in the results table.

l In processing class 20, you use coding to determine inwhich cumulation wage types each basicpay wage type is included and how it is stored in the results table.

© SAP AG HR400 10-13

SAP AG 1999

Cumulation Wage Types: Summary (2)

l In processing class 25, you use coding to determine how each wage type from external transfers isstored in the results table.

l In processing class 30, you determine how each wage type in the results table is cumulated in the annual results table.

© SAP AG HR400 11-1

SAP AG 1999

Retroactive Accounting

l Calculating Retroactive Accounting Differencesl Simple Retroactive Accountingl Multiple Retroactive Accounting

Contents:

© SAP AG HR400 11-2

SAP AG 1999

Retroactive Accounting: Unit Objectives


l Identify the wage types with differenceamounts in retroactive accounting.

l Describe the processing steps in theschema for retroactive accounting.

© SAP AG HR400 11-4

SAP AG 1999

Calculating Retroactive Accounting Differences

1)/550

Cumulation of net amount:3,000 Statutory net pay

2)/560Payment amount before transfer:

3,000 Payment amount (new)

3)/560/560/551/553

Creation of differences:3,7503,000

750750

Payment amount (new)Payment amount (from ORT)Total net retro. acc. differenceRetro. acc. difference to last payr.

4)/559/560/551/553

Wage types in the results table:3,7503,000

750750

Bank transferPayment amount (old)Total net retro. acc. differenceRetro. acc. difference to last payr.

n Wage type /550 is created in the net cumulation part of the payroll schema. The amount for wage type /550 is then added to wage type /560.

n Wage types /551 and /553 are created in the case of retroactive accounting. The difference between wage type /560 from the old payroll result (table ORT) and the newly calculated payment amount is stored in wage type /551 for the payroll period calculated retroactively.

n Wage type /553 is created as the difference between the payment amount for the period currently being accounted and the previous result for the same period. Where multiple retroactive accounting takes place for a period, the wage type contains the difference between the amounts paid for previous and current retroactive accounting. Wage types /551 and /553 are both stored with a reversed sign +/-.

n Note that wage type /560 in the results table for the retroactive accounting run contains the amount specified in the original payroll result.

© SAP AG HR400 11-5

SAP AG 1999

Simple Retroactive Accounting

l In payroll period 02, an employee at the Caliber 'A' Bicycle Company receivesadditional remuneration for payroll period 01retroactively.

© SAP AG HR400 11-6

SAP AG 1999

Example: First Retroactive Accounting Run

Period 01 in period 01

/550/559/560

3,0003,0003,000

Statutory net amountBank transferPayment amount


/550/551

/553/559/560

3,750750

7503,0003,000

Statutory net amountTotal net retro. acc. differenceTotal net subseq. clearanceRetro. acc. difference to last payr.Bank transferPayment amount

-

-


/550

/552

/559/560

4,500

750

5,2505,250

n In this example, the employee's basic pay is increased from 3,000 to 4,500 in the middle of payroll periode 01. The statutory net amount for the period calculated retroactively is the total of the statutory net amount for both partial periods of this payroll period.

n Due to subsequent clearing, the statutory net amount of period 01 in period 02 as well as the amount paid are higher than specified in the original payroll run. Wage type /551 contains the difference between the old and the newly calculated payment amount with reversed +/- sign.

n In the current period, the amount in wage type /551 is then transferred to wage type /552.

© SAP AG HR400 11-7

SAP AG 1999

Multiple Retroactive Accounting

l In the Caliber 'A' Bicycle Company, an employee receivesanother basic pay raise in payroll period 03 that is backdated to payroll period 01.

l This increase in basic pay comes into force in the first payroll period as well as at a later date in the payroll period.

© SAP AG HR400 11-8

SAP AG 1999

Example: Second Retroactive Accounting Run

Period 01 in period 01/550/559/560

3,0003,0003,000

Statutory net amountBank transferPayment amount

Period 01 in period 02/550/551

/553/559/560

3,750750 -

750 -3,0003,000

Statutory net amountTotal net retro. acc. differenceTotal net subseq. clearanceRetro. acc. difference to last payr.Bank transferPayment amount

Period 02 in period 02/550

/552

/559/560

4,500

750

5,2505,250

Period 01 in period 03/550/551

/553/559/560

4,0751,075 -

325 -3,0003,000

Period 02 in period 03/550/551 /552/553 /559/560

5,800 1,300 -

7501,300 -

5,2505,250

Period 03 in period 03/550

/552

/559/560

5,800

1,625

7,4257,425

n In this example, the employee's basic pay is increased from 4,500 to 5,800 in period 03 at the start of the last third of payroll period 01.

n Due to subsequent clearing, the statutory net amount for period 01 in period 03 and the amount paid are again higher than in the original payroll run. Wage type /551 contains the difference between the original and the newly calculated amount. Wage type /553 contains the difference between the newly calculated payment amount and that from the previous retroactive accounting run.

n The statutory net amount for period 02 in period 03 is higher than in the original payroll results. Wage type /552 contains the subsequent clearing amount from the first retroactive accounting run for period 01.

n The amount from for wage type /553 from both retroactively accounted periods is transferred to wage type /552 in the current period.

© SAP AG HR400 11-9

SAP AG 1999

Retroactive Accounting in the Schema

XRR0IF OPDT X041 GEN NOABELSEACTIO X048LPBEG RCIMPRT OPORT X042 GEN NOAB

PIT X047BTFILLPENDIF LPCRPIT X043ELSEPIT X047PIT X043ENDIFENDIF

International retroactive accounting Original payroll?Provide differences receivedRetroactive accountingReset BTEXLoop over old resultsImport last payroll runCreate differences and transferwage types that cannot be revisedCumulate new payment amountTransfer BT from last payroll results

End of loopDid the program run through the loop?New amount to data mediumNoCumulation of new payment amountWrite new amount to data mediumRe: Did program run through loop?End of retroactive accounting

n This subschema is used to calculate any differences that may have been created if payroll takes place in a period for which retroactive accounting has been performed so that remuneration is no longer consistent with the original payroll run. The differences calculated are then taken into account in the same subschema in the original payroll run for the current period.

n The subschema primarily comprises the following steps:

• Query whether original or retroactive run

• Original payroll run: Provide differences received

• Retroactive run: Read last payroll result (original payroll run or old retroactive accounting run)

• Print the values read (internal table ORT)

• Create differences and transfer non-revisable wage types

• Derive new payment amount

• Store new payment amount in difference table (internal table DT)

• Transfer bank transfer(s) (from internal table BT) from last payroll result

© SAP AG HR400 11-10

SAP AG 1999

Retroactive Accounting: Summary

l In retroactive accounting, the last payrollresult is imported into the period forwhich retroactive accounting takes place. The system creates differences that arestored in table DT and transfers the wage types that no longer can be revised.

l The differences are read and processed in the original payroll run.

© SAP AG HR400 12-1

SAP AG 1999

l This section contains supplementary materialto be used for reference

l This material is not part of the standard course

l Therefore, the instructor might not cover thisduring the course presentation

Appendix

© SAP AG HR400 12-2

SAP AG 1999

Appendix

l Checklist of Payroll Prerequisitesl The Payroll Control Recordl The Employee's Payroll Statusl The Payroll Logl Schema and Rule Editorl Utilitiesl Processing Classesl Old Averagesl Calculating Overtimel Archivingl Off Cycle Payrolll Process Model

Contents:

© SAP AG HR400 12-3

SAP AG 1999

Checklist of Payroll Prerequisites

Prerequisites

l Dialog and time wage types

l Work schedules

l Infotypes 0000, 0001, 0007, 0008,0009 and country dependentinfotypes (example: tax)

l Payroll processes further Infotypes: 0014, 0015, 2001, 2010,2003, 2005 . . .

l Payroll areas and periods

l Payroll control record

l Bank details and details of house banks

l Cost centers

l Employee remuneration statements...

l Copy model wage types in the wage type catalog to customer wage typesin the customer name range(numbers)

l Configure and generate work schedulesin Customizing

l Enter personal data in the system usingpersonnel actions

l Configure and generate in Customizing

l Create in Customizing

l Mostly configured using FI

l Mostly configured using FI, combine with organizational units

l Standard form provided...

Activities

Master and Time Data

Admini-stration

Subs.Activities

. . .

n Before employee data can be entered and processed in the system, some necessary prerequisites must be set up first. SAP provides numerous sample entries that you can modify to meet the requirements of your enterprise.

n The above list gives an overview of the most important elements.

© SAP AG HR400 12-4

SAP AG 1999

Payroll Control Record (1)

Released for payroll

Released for correction

Exit payroll

Check payroll results

Incorrect pers. nr.

Payroll areas

Payroll status

XX monthly

International Payroll International Payroll System HelpToolsTools

Payroll calendar

Coordination of the various phases in payroll

Payroll control recordPayroll control record

Payroll results

. . .

. . .

n You must create a control record in Customizing for each payroll area before it can be used.

n The personnel control record performs the following functions in payroll:

n Defines the payroll past for retroactive accounting recognition.

n Locks master data and time data so no changes can be made during the payroll process. The lock is valid for the payroll past and the payroll present. Changes affecting future payroll runs are still possible

n Defines the earliest possible retroactive accounting date for each payroll area

n The control record is maintained either in the Payroll menu under Tools -> Control Record, or in the Payroll menu option, from which you may only choose the steps permitted at this point in the payroll process.

n If you choose Change Control Record in the Tools menu, the 'Incorrect pers. nos.' pushbutton is displayed. This displays a list of rejected personnel numbers. The list is displayed automatically if you attempt to end a payroll run in which payroll is not complete for all personnel numbers.

© SAP AG HR400 12-5

SAP AG 1999

Payroll Control Record (2)

Payroll areas XX monthly

Payroll status

Payroll period 01 1998 01. 01. 1998 - 31. 01. 1998

Run 01

Earliest retro acctg period 01 1997 01. 01. 1997

Last change to control record

by Miller

Status Control record newly created

on February 01, 1998at 01:01:30

Period of lastpayroll run

Current payrollrun saved

Retroactive accounting for payroll is only possible up to the startdate of this period.

Change information

n You must pay particular attention when creating the payroll control record in your live system. The payroll period used to create the payroll control records must be 1 period before the period in which you want to go live.

n Example: You want to use the SAP Payroll system to go live in period 05, 1998. You must enter period 4 as the period in the payroll control record.

© SAP AG HR400 12-6

SAP AG 1999

Employee Payroll Status (Set by the System)

Change Payroll Status (Change Payroll Status (InfotypeInfotype 0003) 0003)SystemEdit Goto HelpHR Master Data Utilities

Valid

Accounted to

Payroll Correction

Special run

Earliest MD change

Retr.Act.Subs.Period

Payroll / retroactive accounting

There is only everone validrecord

In case a personnel number was rejected by payrollor data was changed inthe correction phase

Start dateof retro. accounting

Up to which day payroll took place for the employee

Date up to which payroll recognizesif and when a payroll runmust be repeatedto take changesin master datainto consideration

n Each employee has an individual payroll status. The necessary data is stored in the Payroll Status infotype (0003). This infotype is created automatically as part of the Hiring action and each payroll period is maintained automatically. You will rarely need to make changes to master data in this infotype. Occasionally, however, you may need to enter employee-specific information relating to Payroll or Time Management. It is therefore possible to change a few particular fields in the Payroll Status infotype manually.

n The payroll driver enters the end date of the la st completed payroll period in the "Accounted to" field.

n If master data is changed, the system enters the appropriate date in the "Earliest MD change" field. This date is deleted after each completed payroll run.

n The payroll driver flags the "Payroll Correction" field if a personnel number has been rejected, or you have entered data during the correction phase of the payroll run. The employee is entered in the correction run with this indicator and if payroll is subsequently completed successfully, the indicator is removed. If changes are made in Customizing, the "Payroll Correction" indicator is not set.

© SAP AG HR400 12-7

SAP AG 1999

EE Payroll Status (Information ChangedManually)

Change Payroll Status (Change Payroll Status (InfotypeInfotype 0003) 0003)SystemEdit Goto HelpHR Master Data Utilities

Valid

Earl.pers.RA date

Payroll / retroactive accounting

Run payroll up to

Do not account after

Pers. no. locked

Day until which payroll can be performed for an EE even afterleaving

Employee can be locked for payroll

Payroll is run for this employee until this date

Defines the latest date when changes can bemade in the payroll past

n Earliest personnel retroactive accounting date: This field is only used if you want to set a retroactive accounting limit for an employee that is different from the date set in the payroll area.

n Do not account after: You can enter a date after which payroll will no longer be performed for an employee. This date must not lie within an active period.

n Run payroll to: If an employee has left the company and continues to be paid after the leaving date, this date is stored in this field. If you are dealing with payments in the payroll past, you do not have to enter a date in this field. This is because such payments are triggered automatically during retroactive accounting.

n Personnel number locked: If this field is flagged, an employee can be locked for payroll. This personnel number will not be selected for payroll.

© SAP AG HR400 12-8

SAP AG 1999

The Payroll Log

Payroll LogGeneral dataGeneral data

Payroll periodSelectionGeneral program control

Successful personnel numbersSuccessful personnel numbers00000006 Barbara Eden00000007 James Bond

06/1998 (01.06.1998 - 30.06.1998)

Personnel numbers rejectedPersonnel numbers rejected00000008 John Ross Ewing

MessagesMessagesStatisticsStatistics

Process course forsuccessful

personnel numbers

Process course forsuccessful

personnel numbers

Gen.data(not based on

payroll)

Gen.data(not based on

payroll)

MessagesMessagesProcess course for

rejectedpersonnel numbers

Process course forrejected

personnel numbers

Display statistical informationon the payroll run

Display statistical informationon the payroll run

Logging

Hierarchy levels

n The report tree provides information on the payroll run (general data, messages and statistics) as well as details on the processing steps for the personnel numbers selected.

n The log tree has five fixed hierarchy levels. Each fixed hierarchy level contains variable hierarchy levels derived from the schema.

© SAP AG HR400 12-9

SAP AG 1999

Variable Hierarchy Levels

06/1998 (01.06.1998 - 30.06.1998)Edit basic data

Determine name of EERead work center/basic pay dataContinue with complete data

< Next block >< Sub-block >

Schema

Log

COMBLOCK BEGENAMEWPBPGONBLOCK ENDBLOCK BEGBLOCK BEG

Basic data INTERNATIONALEdit basic dataDetermine name of EERead work center/basic pay dataContinue with complete dataEdit basic data< Next block >< Sub-block >

n Variable hierarchy levels are used to structure data from the payroll run.

n Variable hierarchy levels are identified by the BLOCK function at the start (BEG) and end (END) of the schema.

© SAP AG HR400 12-10

SAP AG 1999

Detail Display of a Function

WPBP: Import work center/basic pay

Input

P0000P0001P0007P0008

Processing

Data retrievalIndirect valuation

Output

WPBPIT

n The detail display for a function enables you to view input data, processing steps, and output data in the log.

© SAP AG HR400 12-11

SAP AG 1999

Navigating in the List

l "Expand" displays detailedinformation

l "Compress" displays anoverview

l Change table display

n Normal (important fields)

n All (all fields)

WPBP: Import work center/basic pay

Input

P0000

P0001

Type Start End Action Reason01.06.1998 01 21

P0007

Infotype Start End0001 01.06.1998 30.06.1998

P0008

Processing

Data retrieval

Indirect valuation

Output

WPBP

IT

30.06.1998

n You can save your personal settings for the log tree and the list as a variant.

© SAP AG HR400 12-12

SAP AG 1999

Messages and Error Messages

Processing

000008 John Ross Ewing

Personnel numbers rejected

06/1998 (01.06.1998-30.06.1998)

Gross part: Processing time data

GENPS

Period work schedule FLEX for 06 1998 not yet generated

……...

n If an error occurs while a personnel number is being processed, the log automatically expands at the relevant position, and displays an error message.

© SAP AG HR400 12-13

SAP AG 1999

A AP C1 C2 C3 AB KoRe BT Aw vT vN

Key to the Results Table

WPBP Split indicators

Assign alternative payment

Assign cost accounting

Employee subgroup grouping

Country-specific splitAssign transfer

Assignabsences

WT3333

/001 /001 M020 M020

01020102

n The country-specific splits indicate partial periods for social security and taxation purposes.

n The object ID for a variable assignment (vT) and its number (vN) can be set using operation SETIN.

© SAP AG HR400 12-14

SAP AG 1999

The Schema Editor

000010000020000030000040000050

111

222 333 444 555 666

Fct Par1 Par2 Par3 Par4 D Text111 Command line

222 Line number

333 Function

444 Parameters 1 - 4

555 Execute function

666 Text

n The editor command lines contain commands generally used within the R/3 System

• A number Attatch; position on specified line number

• CHECK Syntaxcheck

• F schema Fetch; that is, import a different schema such as F XT00

• FIND string Search for specified string

• I Insert; add a new page

• Print Print schema

• R string1 string2 Replace; string 1 is replaced by string 2

• U Update; save schema

n F1 Help You can display online documentation with immediate relevance to the part of the system in which you are working, for example, by positioning the cursor on function names or the names of personnel calculation rules, and pressing F1.

© SAP AG HR400 12-15

SAP AG 1999

Line Commands in the Schema Editor

RR4

Repeat Repeat lineRepeat line 4x

DDD

Delete Delete line Delete block (Select first/last lines!)

CCC

Copy Copy line Copy block (Select first/last lines!)

MMM

Move Move lineMove block (Select first/last lines!)

AB

AfterBefore

Positioning for C/M line commands

n Further line commands:

• RESET Deletes the line command.

• * The line selected appears as the first line of the editor.

• I Inserts a blank line directly under the line selected.

• In Inserts the number of lines specified (n) directly under the line selected.

• X Copies data stored in X buffer under the line.

• XX...XX Marks the block of lines selected in the X buffer. Enter XX in the first and last line of the block that you want to include in the buffer.

© SAP AG HR400 12-16

SAP AG 1999

The Rule Editor

000010000020000030000040000050

111

222 333 444 555 666

VarKey NL Operations111 Command line

222 Line number

333 Variable key

444 Next line

555 Rule type

666 Operations

Payroll rule xxxx ES grouping 1 W/TType ****

T

n A personnel calculation rule can consist of several subareas, each of which is characterized by an employee subgroup grouping for personnel calculation rules, a wage type, and a time type. An index function provides an overview, and enables you to switch from one section to another as well as delete individual subareas.

n The rule line contains 6 operations . The continuation indicator enables you to extend the processing rule to several lines if required.

n The rule type determines the type of processing that is performed. D is used for decision operations, P to call up subroutines, and Z to access a different personnel calculation rule.

n The variable key enables you to build up a decision tree, that can then be used to control wage type processing from an organizational point of view, for example.

© SAP AG HR400 12-17

SAP AG 1999

Maintain Processing Classes and Specifications

Navigation

Processing Classes

---> Processing class specifications

1

3

.

10

.

15

.

Assignment to valuation basesCumulation and storage of time wage types

Mark wage types for factoring

Valuation according to principle of averages

(X010)

(X020)

(XVAL)

(X016)

n In the standard system, the processing classes are stored in the areas from 01 to 89. Processing classes 90 to 99 are for customer-specific entries. You can create your own processing classes and specifications, or create new specifications for existing processing classes.

n SAP recommends that you only create new processing classes in the aforementioned customer areas, as entries that are maintained in the standard system could be overwritten when the release is next updated.

© SAP AG HR400 12-18

SAP AG 1999

Maintain Processing Class Specifications

Navigation

Processing Classes

---> Processing class specifications

1

2

A

Valuation of averages over 3 months

Valuation of averages over 6 months

Valuation of averages with frozen values over 3 months

Processing class 15 Valuation according to principle of averages

n To create a new entry, you can either flag an existing entry, copy and rename that entry, or choose "New entries".

© SAP AG HR400 12-19

SAP AG 1999

Using Wage Types in Payroll (1)

ABCDEF

Assignment to valuation basesWage type is included in valuation basis /001 /001Wage type is included in valuation basis /001 /002Wage type is included in valuation basis /001 /001 and /002Division of valuation bases /001 and /002

Program:Output:

RPDLGA20TablesTree structureContinuous list

Areas belonging to modifier value xxMeaning of processing classes and their valuesMeaning of evaluation classes and their valuesMeaning of cumulation wage typesMeaning of average basesUse of valuation bases

B0101010101

1239

Meaning of processing classes and their values

n This program enables you to obtain an overview of how all your primary and secondary wage types are coded. This can be useful for comparing the coding of different wage types or for gaining an overview of the status of your wage types in the system.

n To run the program, you must enter the country grouping and specify a validity period. By entering certain wage types, you can limit the evaluation to the wage types that you require. The results can be displayed in tables, in a tree structure, or in a continuous list.

n If you flag the optional field Display logical views , you can link from results that are displayed in tables or in a tree structure to the logical views used to maintain processing classes, evaluation classes and cumulation wage types. If a logical view is maintained in the Implementation Guide (IMG), the program also enables you to access and execute the relevant IMG activity directly.

n To display the results in a table (see diagram above), you can navigate to the relevant table entry by double-clicking the left-hand button of your mouse. To navigate in the tree structure, you can press the left-hand mouse button once, or expand and collapse the relevant folder icon.

© SAP AG HR400 12-20

SAP AG 1999

Using Wage Types in Payroll (2)

Assignment to valuation basesWage type is included in valuation basis /001 /001Wage type is included in valuation basis /001 /002 Wage type is included in valuation basis /001 Division of valuation bases /001 and /002

B0101010101

1239

Meaning of processing classes and their values---> X010

---> X013

B01

Meaning of processing classes and their values1 Wage type is included in valuation basis /001 /001

010101010101

111111

M000 Hourly rate M010 Monthly wage M020 Monthly salary M070 Pension paymentM200 Shift bonus M220 Bonus by percentage

n Generating the tree structure and the continuous list can be time-consuming, as the system must assign all the data to a particular branch before the tree can be displayed. It is faster to display your results in tables as the system generates the relevant data sequentially as you branch to the next level.

n To obtain a where-used list, you should display your results in a tree structure or a continuous list.

n If, for example, you simply want to know how individual processing classes are used in wage types, you are recommended to display your results in a table.

© SAP AG HR400 12-21

SAP AG 1999

Displaying Schemas and Rules

Program: RPDASC00

Schema:Trigger PC rules:ES grouping:

X000

X0103

XT00 017 PIT X010 P01 Create valuation bases (Addition) X0103**** DVWTCL 01X0103***** ERRORX0103****0 ADDWT *X0103****1 ADDWT * ELIMI Z ZERO= N ADDWT /001 X0103****2 ADDWT * ELIMI Z ZERO= N ADDWT /002 X0103****3 ADDWT * ELIMI Z ZERO= N ADDWT /001ADDWT /002 XT00 018 PIT X013 P01 Create valuation bases (Addition) XT00 019 MOD XMOD GEN Specify payroll modifiers ......

n Report RPDASC00 enables you to create lists of schemas and subschemas. You can also explode personnel calculation rules (according to the employee subgroup grouping for personnel calculation rules) in the list. This is particularly useful for documenting and gaining an overview of personnel calculation rules you have changed.

© SAP AG HR400 12-22

SAP AG 1999

Using HR Documentation Maintenance

HR Documentation MaintenanceHR Documentation Maintenance

Documentation class

Country

Object name

Operation (Payroll)

Documentation object

HR Documentation Object NameHR Documentation Object NameHR Documentation class

Country grouping

Object name

ADDNA *

. . .

ADDWT

. . .

Description of logical information object

OPEX

Collect number and amount in


Also available asamodal window

n The transaction PDSY (HR documentation maintenance) gives you access to the documentation on all schemas, functions, personnel calculations and operations. If necessary, you can also create client-specific documentation.

n You can get a list of these objects by specifying the documentation class you require and by using the Possible Entries key for the field Object Name. You can also display this list as an amodal window, for example, to have a list of all operations available when creating personnel calculation rules.

n Relevant documentation classes for Time Management: SCHE - Personnel calculation schemas CYCL - Personnel calculation rules FUNC - Functions in payroll OPEC - Operations in payroll 549X - Features PRCL - Processing class PROMO - Process model

n In schema and personnel calculation rule maintenance, HR documentation maintenance is called for a specific context using F1 Help.

© SAP AG HR400 12-23

SAP AG 1999

Payroll and Processing Classes

Assignment to valuation bases

Cumulation and storage of time wage types

Import from old payroll account

Identify wage type for factoring

.

.

M020 Monthly salaryProcessing classes and specifications

Read basic data1.1.

Read payroll accounts for the lastperiod for which payroll was run

2.2.

Time data processing- Determine valuation bases- Read time data- Generate time wage types- Valuate time wage types- Store time wage types in RT

3.3.

Import further payments and deductions4.4.

Factoring- Reduce basic pay - Determine wage types for FI/CO

5.5.

......

01

02

03

04

05

06

07

08

09

10

1

0

0

1

n Processing classes control the processing of wage types at various stages of payroll. The personnel calculation rule called in the schema checks the value (specification) set in Customizing, and performs the processing required for the relevant value.

n For example, processing class 06 transfers wage types from the results in the imported previous period to the current payroll period. The specification 0 in this class denotes that the wage type is not transferred to the current payroll period.

n In total, there are 99 processing classes. The classes 90-99 can be used for customer-specific processing. The processing classes 01-89 belong to SAP, although they are not all used.

n A wage type must have a specification in a processing class if the wage type goes through the payroll processing step in which the relevant processing class is queried.

© SAP AG HR400 12-24

SAP AG 1999

Overview of Schemas and Processing Classes

Subschema Function Rule PRCL Wage types Notes

XIN0 Initialization of payroll XBD0 Edit basic data WPBP Basic pay Infotype 0008XLR0 Import last payr.result PORT X006 06XT00 Gross remuneration PIT X010 01 /001 - /0nn Valuation bases

PIT X013 01 /001 - /0nnP2010 X930 EE remun.info (IT 2010)PIT X015 Time WT valuation

X016 15 Average valuationPIT X020 03 Gross import and RT storage

XAP9 Import further P0014 X011 47 Recurring payments/payments/deductions P0015 X011 47 Add.Payments (IT 15)

XAL9 Factoring and PIT XPPF /801 - /816 Partial period factorsStorage PIT XCM0 31 /840 Monthly lump sums for CO

PIT XVAL 10 Valuation of remun.elementsACTIO XCH0 /840 Hourly rates for COPIT X023 20 Gross import and

RT storageXNA9 Net cumulation PIT X030 05 Net cumulationXRR0 Retroactive accountingXNN0 Net payments/deductions

and bank transfer P0011 X055 Ext.bank transfers (IT 11)X045 25 Import pymnts/deds to RT

XEND Final processing ADDCU 30 Update cumulation in CRT

© SAP AG HR400 12-25

SAP AG 1999

Processing class 06

Maintain all results wage types with regard to importing wage types from the last payroll account

Processing class 06

Payroll subschema XLR0

PORT X006 P06 NOABImport last payroll account

n Wage types from the last payroll result that are relevant to the current payroll run are placed in internal table LRT (Last Result Table) to be used later.

© SAP AG HR400 12-26

SAP AG 1999

Processing class 01

Maintain basic pay for creatingvaluation bases

Processing class 01

Payroll subschema XT00

PIT X010 P01 Create valuation bases

PIT X013 P01

n Use this processing class to code all the wage types that you need for the valuation of other wage types. The valuation bases are stored in secondary wage types /0nn.

© SAP AG HR400 12-27

SAP AG 1999

Processing class 03

Maintain basic pay data and time wage types for storageonce time wage type processing is complete

Processing class 03


PIT X020 P03 Cumulation and storage oftime wage types

n After valuation, time wage types can be cumulated into gross cumulation wage types and average bases, and stored in the results table.

n Wage types from the infotype Basic Pay must also be coded in this processing class. They should be passed on once time wage type processing is complete as they are usually required for factoring.

© SAP AG HR400 12-28

SAP AG 1999

Processing class 47

Check wage types in infotypes 0014 and 0015 with regardto special processing in personnel calculation rule X011

Processing class 47

Payroll subschema XAP0

P0014 X011 GEN NOABP0015 X011 GEN NOABSpecial processing infotypes 0014 and 0015

n Under certain circumstances, you may need to effect special processing for certain recurring payments/deductions wage types and additional payments wage types.

n Example: Union dues are calculated in accordance with the amount of gross income.

© SAP AG HR400 12-29

SAP AG 1999

Processing class 10

Maintain unstored wage types for partial period payroll

Processing class 10

Payroll subschema XAL0

PIT XVAL P10 Factoring

n All of the wage types that are not stored after time wage type processing must be coded for partial period factoring.

© SAP AG HR400 12-30

SAP AG 1999

Processing class 31

Maintain gross wage types for cost distribution

Processing class 31


PIT XCM0 P31Create monthly lump sumsfor Cost Accounting

n All the wage types that are not stored after time wage type processing must be encoded with regard to their influence on the calculation of monthly lump sums for Cost Accounting.

n From the employee's point of view, paid absences have no effect on his or her basic pay wage types. Cost Accounting, however, makes a distinction between remuneration effected for attendance and remuneration effected for absence. For this reason, cost accounting wage types are created during payroll. This processing class enables you to determine the wage type amounts that are included in the cost accounting wage types.

© SAP AG HR400 12-31

SAP AG 1999

Processing class 20

Maintain remaining gross wage types for cumulationand storage after gross calculation of pay

Processing class 20


PIT X023 P20 NOABCumulation and storage

n Processing class 20 enables you to determine if and how wage types are stored in the results table after the gross calculation of pay, and in which cumulation and averages wage types they are cumulated.

© SAP AG HR400 12-32

SAP AG 1999

Processing class 25

Maintain wage types for external bank transfers to beprocessed by net payroll

Processing class 25

Payroll subschema XNN0

PIT X045 P25 Importnet payments/deductions in the RT

n Processing class 25 determines how to store wage types that are entered through the infotype External Bank Transfers. These wage types cannot be cumulated in gross cumulation wage types, as they are processed in the net part of the payroll run.

© SAP AG HR400 12-33

SAP AG 1999

Processing class 30

Maintain all wage types for wage type cumulation in CRT

Processing class 30

Payroll subschema XEND

PRT X080 P30 NOABUpdate of cumulation wagetypes in CRT

n Wage types can be cumulated for several periods in the Cumulated Results Table. In processing class 30, you code wage types that are to be evaluated as an annual valuation, or that are to be listed on the remuneration statement.

© SAP AG HR400 12-34

SAP AG 1999

Processing class 15

Maintain (time) wage types valuated using an average valuewith regard to the calculation rule for averages you want to use

Processing class 15


PIT X015 GEN Time wage type valuation

n In this processing class, you code the wage types that must be valuated using averages based on values from previous periods. The specification of this processing class determines the calculation rule for averages that is used to calculate the average value.

n Use in personnel calculation rules X015 - X018.

© SAP AG HR400 12-35

SAP AG 1999

Creating Bases for Calculating Average Values(Old)

RTE

100,00

WT MM10 Overtime 25% Start End

Averages

100,00 100,00 100,00 100,00 %

NUM

AMT

Rate

Number

Amount

/201

/202

/203

Average basis 01

Average basis 02

Average basis 03

/204 Average basis 04

x

x

x

n When creating the bases for calculating average values, you must determine if and how each primary wage type is used to calculate averages.

n The various bases for calculating average values created here can be used for diverse valuations when calculating average values in cumulation rules.

n In this scenario, basic remuneration for overtime is cumulated in wage type /201, and also in wage type /202.

© SAP AG HR400 12-36

SAP AG 1999

Valuating Averages Using a Primary Wage Type

WT

Processing class

Specification

M400 Vacation bonus

15 Valuation according to principle of averages

1 Valuation of averages over 3 months

n All primary wage types to be valuated using an average must be maintained in processing class 15. The system queries the specification in personnel calculation rule X016.

n In the standard system, wage types are not valuated according to the principle of averages.

© SAP AG HR400 12-37

SAP AG 1999

Defining Calculation Rules for Averages

E VWTCL 15

E 1

MEANV 01

Special processing rules for the valuation of time wage typesX016

E ****

*E

Processing class

*E

ADDWT *

MULTI NRA

ADDNA *

E 2

MEANV 02

MULTI NRA

ADDNA *

Add in table OT

Access average calculation rule

Multiplication

Combine number and amount

Calculation rule

01 ...

02 ...

n To process averages, it is important that you determine the calculation rule. This occurs in personnel calculation rule X016 where decision operation VWTCL 15 queries processing class 15. Wage types to be valuated according to the principle of averages have a specification in processing class 15. For each specification you enter, the system calls operation MEANV nn, where nn is the average value calculation rule.

© SAP AG HR400 12-38

SAP AG 1999

Calculation Rules for Averages

Relevancy test

Cumulation rule foraverage basis

Personnel calculationrule for final processing

Maximum number of previousperiods to be included

Number of relevantprevious periods required

The calculation rule is identified as follows:

01 X017 01 X018 06 03

Possiblewage type

n The following values must be entered for each calculation rule:

1. The personnel calculation rule in which your relevancy test is stored.

2. A cumulation rule: You can either create a cumulation rule or use an existing rule.

3. The personnel calculation rule in which your final processing rule is stored; that is, the rule in which the average is actually calculated.

4. The maximum number of periods that can be used to determine the relevant periods.

5. The number of relevant periods used to cumulate the average bases.

6. A wage type that allows exceptions for individual employees (for example, manual changes to the average value or an average value for new employees).

© SAP AG HR400 12-39

SAP AG 1999

Creating Cumulation Rules (1)

View: Calculation Rules for Averages

Calc.rule Rel.test Cumul. F.process. Max.no.per No.rel.per WT

01

02

X017

X017

03

09

X018

X018

3

6

3

6

View: Cumulation Rules for Average Bases

Cumulation WT Start End CumNUM CumAMT Adjust.

03

09

/201

/206

CumRTE

+

+

+

+

n The Cumulation field in the view Calculation Rules for Averages references the Cumulation field in the view Cumulation Rules for Average Bases.

n Secondary wage types /201 - /232 can be used for the cumulation rules.

© SAP AG HR400 12-40

SAP AG 1999

Creating Cumulation Rules (2)

Wage type

Sign indicatingcumulation in NUM

Sign indicatingcumulation in AMT

Sign indicatingcumulation in RTE

Adjustment rule

The cumulation rule is identified by:

01 /201 + +

n A list is displayed of wage types (/201 - /232) used with the cumulation rules that were entered as average types. The field used for the calculation is flagged accordingly. + Cumulation with positive sign - Cumulation with negative sign " " No cumulation

n To adjust a wage type due to pay increase, the entry in the last field references the modification indicator for the average bases.

© SAP AG HR400 12-41

SAP AG 1999

Creating Relevancy Test

MEANV REL

Relevancy test for the valuation of averagesX017

E ****

*E

MEANV REL

MEANV 00,...99

Period is relevant

Calculation rule for averages

=

=

n This step enables you to determine the periods that are used for averages processing.

n As a general rule, periods that occur immediately before the current payroll period are always used for the formation of averages. Sometimes a period cannot be used because, for example, the employee was absent for its duration rendering it unrepresentative for a calculation rule for averages. The system sets the status of each period as being relevant or irrelevant.

n Each period is processed as follows: The system imports the payroll results for the previous period and calls personnel calculation rule X017. In this rule, you can include wage types from the imported payroll result in the relevancy test. You do this with operations AMT, RTE and NUM (for example, AMT=O….,). MEANV REL specifies that the period is relevant to the calculation of averages otherwise it is irrelevant; that is, it is not included in the subsequent cumulation of the average bases.

© SAP AG HR400 12-42

SAP AG 1999

Creating a Final Processing Rule

Calculating the average after cumulationX018

E ****

*E

E

AMT=M

DIVID ANR

=

NUM=M

NUM?0.00

*E

Work area

for wage type

AMT

500

NUM

20

RTE

25

Table MV

Rule NUM RTE AMT

1

2

20 500

n An average calculation must result in the Rate (RTE) field containing a valuation basis. The formula used to calculate this value is included in personnel calculation rule X018.

n The internal table MV contains the cumulations for averages.

n Standard rule X018 uses the formula amount/number to calculate hourly rates.

© SAP AG HR400 12-43

SAP AG 1999

Technical Procedure of Average Processing

Import previous period

Is period relevant? (X017)

Cumulation acc. to cumulation rule

Maximum number of periods fulfilled?

Calculation of average(X018)

1)

2)

3)

4)

yes

yes

yesRTE

no

no

Average already calculated? (X016)

no

n 1. Has an average value already been calculated for the employee in the current payroll period and for the relevant calculation rule for averages? If so, the average value is stored in the RTE field.

n 2. Each previous period that needs to be processed is imported starting with the current period -1. A relevancy test is then performed in personnel calculation rule X017. If the period is relevant, cumulation takes place in accordance with a cumulation rule that determines which average bases are cumulated and how.

n 3. The system determines whether the maximum number of periods to be used for the calculation rule for averages has been reached.

n 4. Final processing takes place in personnel calculation rule X018. It consists of calculating the average value and making the appropriate entry in the RTE field of the wage type requiring valuation.

© SAP AG HR400 12-44

SAP AG 1999

Creating Adjustment Rules (1)

View: Cumulation Rules for Average Bases

Cumulation WT Start End CumNUM CumAMT Adjust.

03

09

/201

/206

CumRTE

+

+

+

+

02

03

View: Adjustment Rules for Average Bases

Adjustment Ind:NUM

02

03

4

1

Ind:RTE IndAMT VBasis WT No.period

01 3

3

n The view Adjustment Rules for Average Bases contains rules that can be used to increase average values if pay increases. For each field (NUM, RTE and AMT) of the average calculation basis, you can specify by which adjustment factor the relevant field should be multiplied.

© SAP AG HR400 12-45

SAP AG 1999


Mod. ind. for NUM

Mod. ind. for RTE

Val. basis /0nn

The adjustment rule is identified by:

01

No. ofperiods

3

Mod. ind. for AMT

01

% rate

n To adjust a wage type due to pay increase, the entry in the last field references the modification indicator for the average bases.

© SAP AG HR400 12-46

SAP AG 1999


Modification indicators

NUM RTE AMT

2 2

3 3

4 4

1 1 1

n Increase factor 2 is calculated as follows: Basic standard pay for the employee in the rel. period Basic standard pay for the employee in the rel. pre vious period. This factor not only takes account of changes to the pay scale, but also of reassignments to different wage groups.

n Increase factor 3 is calculated as follows: Basic standard pay for the employee in the rel. period Basic standard pay for the employee in the rel. previous period. The difference to increase factor 2 is that basic standard pay in the period in question is determined by the pay scale features of the previous period. Reassignments to different wage groups are not taken into account.

n In increase factor 4, an identifier for a valuation basis must also be specified in the field NN. The increase factor is then calculated as follows: RTE field of /0nn in the rel. period RTE field of /0nn from the rel. previous period. In this case, pay scale and individual bonuses are taken into consideration.

n Increase factor 1 is determined using the table Adjust Average Bases According to Pay Scale .

© SAP AG HR400 12-47

SAP AG 1999


View: Adjustment Rules for Average Bases

Adjustment Ind:NUM

02

09

4

Ind:RTE IndAMT VBasis WT No.period

01 3

31

View: Adjust Average Bases to Pay Scale

PStype PSarea

01

01

01

01.04.1998

01.04.1998

01.04.1998

GrpPSRule Start Percent1 Percent2

01

01

01

1

2

3

105,000

106,000

106,000

95,000

0,000

0,000

n Modification indicator 1 references the table Adjust Average Bases to Pay Scale .

n Percentage 1 specifies a standard pay increase if working time does not change. A reduction in working time with full pay is specified in percentage 2.

n If the NUM or AMT fields specify modification indicator 1, the increase factor corresponds to percentage 1.

n If modification indicator 1 is entered in the RTE field, the increase factor is calculated as follows: Percentage 1 is divided by percentage 2, if percentage 2 <> 0, or percentage 1, if percentage 2 = 0.

© SAP AG HR400 12-48

SAP AG 1999

Views Used to Calculate Averages

AdjRuleAdjRuleRuleRule

AdjRuleAdjRule IndNUM IndRTE IndAMT

PStype PSarea PS ID PRZN1 PRZN2

Rule CumRuleCumRule

1. Calculation rules

2. Cumulation rules

3. Adjustment Rules

4. Adjusting the average calculation bases to the pay scale

n If you flag the relevant rule in the view Calculation Rules for Averages, you can use the navigation field to access subsequent rules.

n If you calculate averages without taking individual pay increases into account, you only require entries in the first two views.

n If you must take individual increases in an employee's basic pay into account, an entry is required in view 3.

n If you have to take pay scale increases in basic pay into account, additional entries are required in view 4.

© SAP AG HR400 12-49

SAP AG 1999

Frozen Averages

Special processing rules for the valuation of time wage typesX016

VWTCL 15

AE

Absence periods

…..Processing class

0E 1E 2E 3E

MEANV 10

MULTI NRA

ADDNA *

MEANV 10

MULTI NRA

ADDNA *

ZERO= NA

ELIMI *

ADDNAE/02A

RTE=L /02A

MULTI NRA

ADDNA *

ZERO= NA

ELIMI *

ADDNAE/02A

RTE=L /02A

MULTI NRA

ADDNA *

ABEVL?

n If you assign specification A to a wage type in processing class 15, personnel calculation rule X016 calls decision operation ABEVL?. This operation determines whether an employee's absence is longer than the current period and returns the values 0, 1, 2 and 3.

0 The absence starts and ends in the current payroll period; normal calculation of averages.

1 The absence starts in the current period and ends in the subsequent period: The average value is calculated in the current period and frozen in the subsequent period. Operation ADDNAE/02A stores the amount specified in the rate (RTE) field in wage type /02A, and saves it to internal table RT. Storing the rate, that is, the average value, in this wage type freezes it and enables valuation of the same absence in the subsequent period.

2 The absence starts in the previous period, spans the current period, and ends in the subsequent period. In this case, the system uses the frozen average value from the previous payroll period to valuate the absence in the current period. The average value is then frozen again for valuation in the subsequent period.

3 The absence starts in the previous period and ends in the current period. In this case, the absence is valuated using the frozen average value from the previous period.

© SAP AG HR400 12-50

SAP AG 1999

Calculating Overtime

E OUTOTCLTYP

E 2

ADDZL MM70

Processing overtime wage typesTC00

E ****

*E

*E

ADDZL *

Clearing key in variable key

Add in table ZL

Add in table ZL

Multiplication

M = Overtime, create 1st and 2ndderived wage type

ADDZLM1

ADDZLM2

E 3

HRS*%012

ADDZLMM70

n The value of the overtime compensation type in the infotype Overtime (2005) determines how employees are compensated for overtime. The standard specifications are as follows:

• 1: Remuneration

• 2: Basic pay for free time, bonuses paid

• 3: Compensation

n In the specification for compensation, operation HRS multiplies the number of hours field by the percentage specified for the current, first and second derived wage type in the table Wage Type Valuation.

n Processing class 17 determines overtime compensation for wage types included in payroll through cluster B2.

n Personnel calculation rule TC10 references processing class 17 of the overtime wage types and the overtime compensation type assigned to the overtime quota. This occurs to decide whether the wage type, or derived wage types, should be stored in table ZL (remuneration of overtime and bonuses), or whether a time-off quota should be set up (compensation by time in lieu).

© SAP AG HR400 12-51

SAP AG 1999

R/3R/3 DB DB

Overview of Archiving in HR

Archiving objects

PA_CALC

PA_TIME

PA_TRAVEL

Archiving in HR ArchiveLink

Archivefiles

n Data to be archived in the R/3 database can only be archived using archiving objects that are available in the system, which describe the structure and composition of the data. For payroll results, this object is PA_CALC.

n Essentially, the archiving procedure can be broken down into two steps:

• The creation of archiving files: When archiving takes place, the archiving data is first written sequentially to a newly created file. These archive files can, for example, be transferred to an archiving system using an ArchiveLink.

• Initializing the delete program: On the basis of the created archive files, the deletion program removes data from the data base.

n The archived data can be displayed, without being restored, with the report RPCLSTxx (xx = Cluster-ID).

n If you want to archive data, you must first create an archiving group.

© SAP AG HR400 12-52

SAP AG 1999

Contents of an Archiving Group

l Country for which the payroll results were created

l Selection of archiving objects

l Archiving date

l Retroactive accounting limit

l Country-specific parameters for payroll

l Selected personnel numbers, for example- All employees who have left the company- All employees in one personnel area

n The archiving group is a special structure for archiving. It allows you to summarize archiving objects from Payroll, Time Management and Travel Management, if these components are integrated.

n To create an archiving group, you have to specify its characteristics. To enable you to do this, the system asks you questions step by step.

n The Archiving date is the date up until which payroll data, based on personnel numbers, is to be archived. The retroactive accounting limit is the date that determines how far back the assigned personnel numbers can be accounted.

n To create an archiving group, you can take one of the following approaches:

a) You specify the archiving date. The system proposes a retroactive accounting limit that comes as soon as possible after the archiving date, and ensures that country-specific requirements are taken into consideration.

b) You specify a retroactive accounting limit. The system proposes an archiving date immediately before the specified retroactive accounting limit, and ensures that country-specific requirements are taken into consideration.

n At the end of this step, each archiving group receives a number that is supplied by the number range. You must therefore create a number range for the number range object HRARCHIVE.

© SAP AG HR400 12-53

SAP AG 1999

The Archiving Process

l 1. Phase 1: Creating an Archiving Group

l 2. Phase 2: Assigning Personnel Numbers

l 3. Phase 3: HR Preparation for Archivingn Test Run

n Release

n Execute

n Reverse

n Exit

l 4. Phase 4: Archiving

n Execute

n Exit

n When you create an archiving group, the system checks your entries to ensure that there are no inconsistencies as a result of missing data.

n You then assign the relevant personnel numbers to an archiving group.

n Although it is not compulsory, you are nonetheless advised to carry out a test run before releasing the archiving. The release status locks access to the payroll data for the assigned personnel numbers. It is subsequently not possible to carry out retroactive payroll for these personnel numbers, as they are locked for the payroll driver.

n After carrying out HR preparation for archiving, the payroll data is no longer accessible for payroll, although it is still available in the database. Consequently, retroactive payroll runs are no longer possible for archived periods. It is, however, possible to undo the HR preparation for archiving, either for all the personnel numbers in an archiving group, or for individual personnel numbers. You can then, if needs be, carry out necessary retroactive accounting runs.

n In the final step, the archive administration transaction (SARA) is called. Here, you create an archiving job. This means the archive data, which is assigned to an archiving group, is transferred by archiving object to an archive file and then deleted from the database.

© SAP AG HR400 12-54

SAP AG 1999

Off-Cycle Payroll

l Bonus payments

l Correction payroll runs

l Regular payroll

l Payments in advance

l Payment of an absence

n The Off-Cycle Payroll function enables you to carry out various payroll activities that are not covered by the regular payroll run. The payroll control record is not affected by Off-Cycle Payroll. The types of Off-Cycle Payroll that you can carry out depends on the settings in Customizing for Payroll.

n If an employee is to receive a bonus payment, run Off-Cycle Payroll to trigger payment for the employee.

n If you want to make a payment for an absence to an employee in future payroll periods, you run payroll on a daily basis for the period in which the absence takes place.

n If master or time data was changed for an employee, you can use retroactive accounting to start a correction run and trigger the payment.

n If an employee was hired shortly before the payroll date and his or her papers could not be processed in time, you can run regular payroll, even if this is no longer possible for the payroll area, or you can run payroll for this employee before running payroll for the whole payroll area the next time.

n If an employee leaves the enterprise, or is absent for several periods and wants to receive the money owed to him immediately, you can carry out payroll in advance for several periods with a payment in advance. The personnel number is selected for payroll again when the period, for which payroll has been run, has elapsed.

© SAP AG HR400 12-55

SAP AG 1999

The Process of Off-Cycle Payroll

Off-Cycle PayrollOff-Cycle Payroll

Specify the date, and the reason for the payroll run.

0001Reason

Date

Holiday bonus

06.12.1999

Payment of an absence

Payment of an absence

AbsenceAbsence

Enterabsence

Payments in advance withreg.payments

Payments in advance withreg.payments

Payroll periodPayroll period

Selectperiod

Payments inadvance with

spec.payments

Payments inadvance with

spec.payments

Special paymentsSpecial payments

Enterwage type

Other paymentsOther payments

Payment Payment methodmethod

Changepaymentmethod

Runpayroll

RunRunpayrollpayroll

Run payroll

n The Off-Cycle reason that you specify determines the subsequent payroll process.

n In the case of payment of an absence , the system proposes the absences that have already been entered in the Absences infotype (2001), which were entered for off-cycle payroll runs in Payroll Customizing. As an alternative, you can enter an absence directly from the program in the Absences infotype (2001). The start and end date are the same for this type of absence. The system writes the reason for Off-Cycle Payroll, the payment date, the payroll type and payroll identifier in the Absences infotype (2001).

n In the case of advance payment, the system offers you the periods for which you can perform payroll. You made this setting in Payroll Customizing. If you are paying several periods in advance, the system carries out a regular payroll run for the last period that is to be paid. All other periods that occur before this are dealt with by retroactive accounting. Consequently, for several periods there is only one original result , and only one payment is made. The payroll control record is not even taken into consideration in this payroll run. The employee is not selected for regular payroll until the last period.

n In the case of a bonus payment, you must enter a wage type that is permitted for infotype 0267.

© SAP AG HR400 12-56

SAP AG 1999

Supplementing Payment Methods

InfotypeInfotype 0009 for regular payroll runs 0009 for regular payroll runs

0

SubtypeSubtype Payment methodPayment method PayeePayee BankBank Bank accountBank account Default valueDefault value

1

1

Check

Transfer

Transfer

Michael Bond

Bank of America

Bank of America

1234567890

0987654321

% rate% rate

100 USD

20,00

Supplement Payment Method for Off-Cycle Payroll Supplement Payment Method for Off-Cycle Payroll

5

SubtypeSubtype Payment methodPayment method PayeePayee BankBank Bank accountBank account Default valueDefault value

6

Check

Transfer

Michael Bond

Bank of America 9999999999

% rate% rate

50,00

SupplementingPayment Methods

Checkdate

Checkdate Payroll typePayroll type Payroll

identif.Payrollidentif.

Off-Cyclereason

Off-Cyclereason

Off-Cyclepayroll runOff-CycleOff-Cycle

payroll runpayroll run

n You can change the payment method during Off-Cycle Payroll. A record is created for the current payment in the Bank Details infotype (0009). This record includes the reason for the Off-Cycle Payroll, the payment date, the payroll type and the identifier. The record is only valid for the current payroll run.

n As a default, payment by check is proposed. You can split the payment, and assign main and secondary bank details.

n For Off-Cycle Payroll, the system proposes, when requested, the following subtypes of infotype 0009:

• Subtype '5' for main bank details

• Subtype '6' for secondary bank details

© SAP AG HR400 12-57

SAP AG 1999

Absence Valuation in Off-Cycle Payroll

Leave(10.6. - 20.6.)

Leave(10.6. - 20.6.)

Payment in advance of absence

Payment in advance of absence Regular payrollRegular payroll

Counting classesCounting classes

01

Counting classCounting class PaytPayt PercentPercent

100

ValuationValuation acc acc. to constants/averages. to constants/averages

MD01

WTWT PercentPercent Time unitTime unit

MD02

100 KT

KT

ValuationValuation acc acc. to constants/averages. to constants/averages

MD01

WTWT PercentPercent Time unitTime unit

MD02

100 KT

KT100

n There are two procedures for paying absences in advance.

1. In a regular payroll run. In a regular payroll run, payroll is started for an employee after regular payroll is already complete for the relevant payroll area.

2. In a payroll run that only deals with employee absences that should be paid in advance. In this case, you set up special absence valuation rules for Off-Cycle Payroll. Generally, this applies to absences such as leave and other types of time in lieu entitlements.

n The process of absence valuation in Off-Cycle Payroll:

1. The off-cycle run is carried out. Absences that are valuated in the course of the run are given a special indicator at the start of Off-Cycle Payroll. You can display this indicator in the infotype record for the relevant absence.

2. Payroll is run for the period of the absence that overlaps with the respective payroll periods in a regular payroll run. The RAB function checks whether the absence(s) have the off-cycle indicator flagged. If so, payroll can determine the differences betweeen the new payroll run for the absence and the results in the off-cycle run. You can cumulate the differences in specific wage types and counting classes.

n To valuate absences in Off-Cycle Payroll, two absence valuation rules must be set up for a group of absences.

© SAP AG HR400 12-58

SAP AG 1999

Setting Up Reasons for Off-Cycle Payroll

View Reasons for Off-Cycle Payroll

OC-reason Description OC Category Payroll type

90009001

Sales bonusLeave bonus

0205

AA

01020304050607

RegularBonusCorrectionManual checkAbsence paymentPayment in advance of periodsOn-demand payroll for next period

ABC__

Bonus paymentCorrection runManual checkRegular

n In Off-Cycle Payroll, the administrator first has to select the off-cycle reason.

n In this step, you define the reasons that are available to the administrator. You also assign a category to each reason.

n The category defines the type of payroll involved, and whether Off-Cycle Payroll is dealing, for example, with a bonus or absence calculation, with a payment-in-advance, or with something else. It is possible that similar reasons have the same category. For example, the reason 'sales bonus' specifies the meaning of the payroll run in more detail.

n If you create your own reasons, note that these must begin with 9, Y or Z.

© SAP AG HR400 12-59

SAP AG 1999

Setting Up Off-Cycle Absence Valuations

View: Valuate AbsencesAbsValGrpg Valuation ruleOff-cycle indicator

0101O

Paid leave Start EndValuation in Off-Cycle Payroll

Wage type4000

Percent100

Time unitAT

Day ruleWD

View Reasons for Off-Cycle Payroll

OC-reason Description PSGrp Absence type

90009001

Leave bonus Leave bonus

0101

0100 Leave 0110 Leave 1/2 day

n In the first step, you specify which employee absence times can be valuated in an off-cycle payroll run. To do so, you assign an off-cycle reason to each of the relevant absence types. At the start of the off-cycle payroll run, the system then proposes to the administrator all of the employee's absences, for which off-cycle reasons have been assigned to absence types in Customizing.

n In the next step, you specify the following absence valuation rules:

• For the valuation of absences in the off-cycle payroll run

• For the valuation of absences in the regular payroll run if an off-cycle payroll run has already taken place. To enable you to set up the Absence Valuation table, there is an additional key field: the indicator for absence valuation in Off-Cycle Payroll. Depending on this indicator, you can access various views of this table.

n Absence valuation:

• Indicator O (Valuation in the off-cycle payroll run): Here, you can only specify constants/averages.

• Indicator R (Valuation in the regular payroll run with OC indicator): Here, you can display all methods of absence valuation ('as if' principle, counting classes, and so on).

© SAP AG HR400 12-60

SAP AG 1999

Creating Process Models

Read MarkersRead Markers/Transfer to /Transfer to Process Process Model Model for Payroll for Payroll RunsRuns

Regular payroll runsBonus runsxCorrection payroll runsNon-Authorized Manual Checks

Model-ID SAPXXOC

Personnel number to

Pre-program DMEProgramVariant

RPCDTCU0SAP_OC

Check processingProgramVariant

H99_RFF_FRAME SAP_OC

Execute posting runProgramVariant

RPCIPE00SAP_OC

Print FormProgramVariante

RPCEDTU0SAP_OC

n Subsequent activities are necessary for all off-cycle payroll runs. The reports to be executed must be grouped together in process models.

n The sequence of processing steps is defined in process models. A process model has the following advantages:

• It clearly illustrates how individual processing steps are linked together

• It makes it possible to execute programs on a parallel basis

• It makes it possible to easily repeat processes

• It clearly illustrates the status of the process and the personnel numbers

• It makes it easy to navigate to the job log and the program log

n If you use both the Off-Cycle Payroll function and the check replacement function, you require two different process models, as the pre-program DME is already integrated in the check replacement procedure. Unlike this, running pre-program DME for off-cycle payroll runs is a subsequent activity and must be started in the process model.

n SAP provides several process models as a sample and template.

sap payroll

Documents

days sap india sap ag

sap products

priorconsent of sap

sap word

sap archivelink

sap earlywatch

sap logo

n microsoft