You are on page 1of 38

PAYROLL AREA AND PAYROLL PERIOD: -

SPRO – IMG – PRESONNEL MANAGEMENT – PERSONAL ADMINISTRATION –


ORGANISATIONAL DATA – ORGANISATIONAL ASSIGNMENT – CREATE PAYROLL
AREA – NEW ENTRIES (ENTER: PAYROLL AREA , PAYROLL AREA TEXT, PAYROLL
FOR PA – SELECT THIS ONLY IF YOU WANT TO RUN THE PAYROLL) – SAVE

SELECT 2ND OPTION – CREATE PAYROLL AREA – CLICK ON POSITIONS – FIND


PAYROLL AREA IN POSITION – PERIOD PAR (ENTER 01 – IT MEANS MONTHLY) –
DATE MODIFIER(ENTER 01 – IT MEANS STANDARD MODIFIER IT RUNS ON A
PARTICULAR DATE) – RUN P(CHECK IT) – SAVE.

PayrollAre Payroll Area Period Period Payroll Date


a Text Parameter Parameter Text Relevant Modifier
10 Monthly 01 Monthly  01
11 Semi-monthly 02 Semi-Monthly  01
12 Weekly 03 Weekly  01
13 Bi-weekly 04 Bi-Weekly  01
99 Non-payroll
Relevant

DEFINE PERIOD PARAMETER :

IMG Path Payroll  Payroll: Great Britain  Basic Settings  Payroll


Organization  Define Period Parameters
Transaction SPRO
Code

DEFINE DATE MODIFIER:

In your enterprise, payroll is run monthly. You want the payment date for pensioners to be
the first day of the month, for industrial workers the 15th, and for salaried employees the
25th. You specify the following date modifiers:

Date modifier Description


01 Payment date on 1st day of the month
02 Payment date on 15th day of the month
03 Payment date on 25th day of the month
IMG Path Payroll  Payroll: Great Britain  Basic Settings  Payroll
Organization  Define Date Modifier
Transaction SPRO
Code

FEATURE ABKRS – IT IS A FEATURE FOR DEFAULT PAYROLL AREA:


ABKRS is used to default payroll area on IT0001 on an employee.

You use a few logic condition such as personnel area, personnel sub area, company code,
employee group, etc., to determine down to the employee level what payroll area he/she
belongs to.

That then get transported to the payroll area field on IT0001. The payroll area field on
IT0001 is what payroll extract runs of when handling your payroll process.

TCODE – PE03

IN TC CLASS – IN OTHERWISE – SELECT MOLGA – CREATE – SELECT 08 – CREATE


– SELECT FIELD DECISION OPERATION – SELECT ESG(PERSK – IT IS FIELD NAME
FOR ESG) – SELECT PERSK – CREATE – SELECT ESG(FROM SYSTEM) – SELECT ESG
SALARIED – CREATE – SELECT RETURN VALUE - ENTER – ENTER VALUE(ESG
FROM SYSTEM) – SELECT PAYROLL AREA WE CREATED FROM SYSTEM – ENTER –
SAVE.

TO ACTIVATE FEATURE – GO TO ACTIVATE BUTTON – PRESS ENTER(THE STATUS


WILL CHANGE FROM SAVED TO ACTIVATE).

NOTE : - YOU MIGHT GET ERROR – FIELD VALUE NODES MUST HAVE
DEPENDENT NODES THEN GO TO INFO IN OTHERWISE – SELECT THE INFO – GO
TO DELETE – DELETE IT – SAVE.

CONTROL RECORD : -

In this step, you set up the system controls for the payroll control record. This control record
has the following functions in payroll:

 It determines the current payroll period for the exact date.


 It defines the payroll past for the retroactive accounting recognition.

 It locks the master data and the time data to prevent changes from being made
during the payroll run.

This lock is valid for the payroll past and the payroll present. Changes which affect
the future can still be made.

 It determines the earliest retroactive accounting period.

Transaction Code : PA03

SPRO – IMG – PRESONNEL MANAGEMENT – PERSONAL ADMINISTRATION –


ORGANISATIONAL DATA – ORGANISATIONAL ASSIGNMENT – CREATE CONTROL
RECORD – IN PAYROLL AREA (SELECT FROM SYSTEM) – CREATE -

Personnel Control Record


Control Record Payroll period Ru Earliest Retroactive Accounting
Type n Period
0 200 01/01/2006 –
01 Payroll 1 6 01/31/2006 0 01 2006 01/01/2006
0 200 01/01/2006 –
01 Payroll 1 6 01/15/2006 0 01 2006 01/01/2006
0 200 01/01/2006 –
01 Payroll 2 6 01/07/2006 0 02 2006 01/01/2006
0 200 01/01/2006
01 Payroll 2 6 – 01/14/2006 0 02 2006 01/01/2006

Payday rule: This field specifies how the payment date should be calculated for each payroll
period.

Example: In your system, you use monthly payroll periods and want to define the 25th of the month
as the payment day. Then you need to make the following entries:

Payment day rule: 4


Number of days: 25

That means that the payment day in every payroll period is not based on the length of the month.

In your system, you use weekly payroll periods and want the payment day to come four days after
the end of the payroll period. You make the following entries:

Payment day rule: 3


Number of days: 4
Generate Payroll Periods
Procedure
1. Access the activity using one of the following navigation options:
IMG Path Payroll  Payroll: Great Britain  Basic Settings  Payroll
Organization  Generate payroll periods
Transaction SPRO
Code
2. On the ‘Choose Activity’ screen, select “Generate payroll periods” and choose the ‘Choose’
button. Insert value ‘01’ in the ‘Work Area’ and choose ‘Enter’. You will see the values in the table
below.
3. Payroll periods for all payroll areas have been generated from period 01.2000 to the last payroll
period of 2010. The values used in the generation process are as follows:
Period Date Start Final Start Payday Number Determine Carry
Modifier Modifier Date Year of Rule of Days Period out
Tax Number table
Year change
01.01.200
01 01 2 2010 0101 3 
01.01.200
02 01 2 2010 0101 3 
12.23.200
03 01 1 2010 0101 3 6 
12.23.200
04 01 1 2010 0101 3 6 

Retroactive Accounting – Refers to the last payroll process date.

- SAVE.
-
ESG GROUPING FOR PCR(Personnel Calculation Rule):

In this step, you can define the groupings for the personnel calculation rules and
collective agreement provisions for all your employee groups and subgroups.

The employee subgroup grouping for the personnel calculation rule is required in
Payroll Accounting. The collective agreement provisions grouping is required for
indirect valuation of wage types in the Basic Pay infotype (0008).

Indirect Valuation - If we maintain values in V_t539a ,then the values will be


defaulted in basic pay infotype and it is indicated with "I".I f there are any manual
entries then the "I " will disappear. S0 entering values in t539a is an indirect
evaluation.

Collective Agreement Provisions are for Employee Union...The Employee Unions will
come up with a set of requirements for different employee groups and we need to
segregate an employee based on the provisions his particular association with a
union requires.
So you create a seperate grouping for different employees whose requirements vary
based on the agreement and then assign employees to these groupings.

SPRO – IMG – PERSONNEL MANAGEMENT – PERSONAL


ADMINISTRATION - PAYROLL DATA – BASIC PAY – DEFINE ESG FOR
PERSONNEL CALCULATION RULE & COLLECTIVE AGREEMENT PROVISION
– COUNTRY GROUPING(ENTER 08) – PRESS ENTER – ESG FOR PCR – 3
(MEANS SALARIED) – SAVE.

Employee subgroup grouping for the personnel calculation rule:

 1 = hourly wage

 2 = periodic payment (eg.monthly wage)

 3 = salary/pension

 4 = pay (German civil service)

 5 = social insurance (German civil service)

Employee subgroup grouping for the collective agreement provisions:

 1 = industrial workers/hourly wage

 2 = industrial workers/monthly wage

 3 = salaried employee

 4 = AT

PAYSCALE TYPE

SPRO – IMG – PERSONNEL MANAGEMENT – PERSONAL


ADMINISTRATION - PAYROLL DATA – BASIC PAY – CHECK PAYSCALE TYPE –
NEW ENTRIES – PAYSCALE TYPE(ENTER ANY NUMBER) – PAYSCALE TYPE
TEXT(ENTER) – SAVE.

PAYSCALE AREA

SPRO – IMG – PERSONNEL MANAGEMENT – PERSONAL


ADMINISTRATION - PAYROLL DATA – BASIC PAY – CHECK PAYSCALE AREA
– NEW ENTRIES – PAYSCALE AREA(ENTER ANY NUMBER) – PAYSCALE
AREA TEXT(ENTER) – SAVE.

ASSIGNMENT OF PAYSCALE STRUCTURE TO ENTERPRISE STRUCTURE

SPRO – IMG – PERSONNEL MANAGEMENT – PERSONAL


ADMINISTRATION - PAYROLL DATA – BASIC PAY – CHECK ASSIGNMENT OF
PAYSCALE STRUCTURE TO ENTERPRISE STRUCTURE – (SELECT PAYSCALE
AREA AND PAYSCALE TYPE FROM THE SYSTEM) – SAVE.

FEATURE TARIF - – IT IS A FEATURE FOR DEFAULT PAYSCALE DATA :

SPRO – IMG – PERSONNEL MANAGEMENT – PERSONAL


ADMINISTRATION - PAYROLL DATA – BASIC PAY - DETERMINE DEFAULT
FOR PAYSCALE DATA – SELECT TARIF – GO TO CREATE – SELECT FIELD FOR
DECISION OPERATION – SELECT PERSK – GO TO CREATE – SELECT ESG
FROM SYSTEM – ENTER – CREATE – SELECT RETURN VALUE – ENTER –
THEN SELECT PA & PSA – SAVE – ACTIVATE(STATUS CHANGES FROM SAVE
TO ACTIVATE).

CREATION OF WAGE TYPE:

In this step, you create your own wage types for the infotype
Basic Pay (0008) by copying the model wage types in the
standard system.

These copies are the wage types you will use in further
processing. You can also modify the copies to suit your
requirements.
Wage types

In a broad sense, a wage type simply holds a piece of data – a rate,


number, and/or amount. But more specifically, a wage type has dozens
of attributes that control how it is manipulated and processed. In the end
though, it ends up as an object in the payroll results database that stores
a rate, number, and/or amount. The most typical use of a wage type is to
store the amounts of earnings, deductions and taxes in an employee’s
paycheck. A person’s base pay is stored in a wage type, the amount of
their United Way deduction is stored in a wage type, and their taxable
wages & taxes are stored in wage types.

Wage types, as the primary data element for employee paychecks, are
also mapped to FI/CO accounts to record the debits and credits resulting
from the paycheck and reported on the W-2 and other tax forms. Wage
types can also be used to store statistical data – such as the number of
hours worked in a pay period, the average weekly wages for the past six
months, or the amount of wages eligible for a profit sharing calculation.

Wage type attributes are stored in several tables, but the central table is
T512W. Much more time will be spent on various aspects of T512W.
There are three categories of wage types – model, technical, and user.
Model wage types are delivered by SAP for customers to use as
guidelines for creating their own wage types. They always start with a
letter and SAP may add, delete or update them in system upgrades.
Technical wage types always start with the ‘/’ symbol, and are delivered
by SAP. They are intended for very specific standard processing in
payroll, and while you can modify them, SAP may also update them
during upgrades. So if you ever (I mean EVER) change a technical wage
type, check it after each upgrade to make sure it still has the attributes
you want. And never delete a technical wage type.

SPRO – IMG - PERSONNEL MANAGEMENT – PERSONAL


ADMINISTRATION – PAYROLL DATA – BASIC PAY – WAGE TYPES – CREATE
WAGETYPE CATALOG – SELECT COPY – CLICK ON WAGETYPE GROUP
BUTTON ON LEFT TOP – SELECT THE INFOTYPE – ENTER – SELECT THE
WAGE TYPE FROM THE ORIGIN COLUMN – CLICK ON CWT BUTTON –
ENTER THE WAGE TYPE NUMBER OF YOUR CHOICE – ENTER – WRITE
WAGETYPE LONG TEXT AND TEXT – UNCHECK TEST RUN – CLICK ON
COPY BUTTON ON TOP – GO BACK – SELECT COMPLETENESS CHECK –
SELECT TEST RUN – ENTER.

NOTE – WE CAN SEE OUR WAGE TYPE IN TCODE – OH11

SPRO – IMG - PERSONNEL MANAGEMENT – PERSONAL


ADMINISTRATION – PAYROLL DATA – BASIC PAY – WAGE TYPES – – CHECK
WAGE TYPE GROUP ‘ BASIC PAY ‘ – NEW ENTRIES - - ENTER WAGE
TYPE(WHICH YOU CREATED) – SAVE.

NOTE – THE ABOVE PROCEDURE STORES THE WAGE TYPE WHICH YOU
CREATED IN THE INFOTYE WHICH YOU SELECTED AT THE TIME OF
CREATING WAGE TYPE.

SPRO – IMG - PERSONNEL MANAGEMENT – PERSONAL


ADMINISTRATION – PAYROLL DATA – BASIC PAY – WAGE TYPES – CHECK
WAGE TYPE CATALOG – CHECK WAGE TYPE TEXT – CHANGE THE START
DATE – SAVE.

SPRO – IMG - PERSONNEL MANAGEMENT – PERSONAL


ADMINISTRATION – PAYROLL DATA – BASIC PAY – WAGE TYPES – –
CHECK ENTRY PERMISSIBILITY PER INFOTYPE (THIS STEP ALLOWS YOU
TO DEFINE THE VALIDITY PERIOD OF YOUR WAGE TYPE) – NEW ENTRIES
– WAGE TYPE – START DATE – END DATE – SAVE.

WAGE TYPE PERMISSIBILITY :

In this section, you can define which wage types may be entered for your groupings.

Example

You want to allow the "bonus" wage type only for employee subgroup grouping "9".
These employee groups and subgroups were defined in the previous but one step.
Set this indicator in column "9" of the "Admissibility for employee subgroup grouping"
block for your groupings.

You want to allow the "share of turnover" wage type only for personnel subarea
grouping "9". These personnel subareas were defined in the previous step. Set this
indicator in column "9" of the "Admissibility for personnel subarea grouping" block for
your groupings.

SPRO – IMG - PERSONNEL MANAGEMENT – PERSONAL


ADMINISTRATION – PAYROLL DATA – BASIC PAY – WAGE TYPES – DEFINE
WAGE TYPE PERMISSIBILITY FOR EACH PSA & ESG – SELECT THE WAGE
TYPE – CLICK ON DETAILS BUTTON – ESG AND PSG GROUPING SHOULD
HAVE NO 1 – SAVE.

WAGE TYPE CHARACTERISTICS :

SPRO – IMG - PERSONNEL MANAGEMENT – PERSONAL


ADMINISTRATION – PAYROLL DATA – BASIC PAY – WAGE TYPES – CHECK
WAGE TYPE CATALOG – CHECK WAGE TYPE CHARACTERISTICS

Amount - Minimum and maximum values – you can specify minimum and maximum
values for a wage type. This is useful to stop input errors at source. Having
meaningful values set here can prevent errors at the input stage rather than having
to find them in your payroll exception reports or even at a later stage. The difficulty
most customers find that it is very hard to decide on what values to use for each
instance. It is recommended to configure meaningful values for most of the wage
types that are input manually. You might only prevent a few incorrect inputs of data,
but it may well save your organisation a lot of money. Add to total - Tick this indicator
if you would like the value for this wage type to be included in the basic pay total for
the employee. Input combination - This controls what values are allowed at data
entry – i.e. whether you have to enter an amount or you can enter either an amount
or a number with units etc. There are 5 options for both amount and number and
these are controlled separately for both. The help is very useful in these fields and
won't be repeated here. Time Levelling and Time Sheet Basic hours - Defines
whether the wage type is a wage type for basic hours or a bonus wage type. The
indicator is used for time levelling. Number / Unit Time Unit / Measurement - This
allows you to stipulate the hours, months, years, shares etc If you have stipulated
that the user is to enter units on the input combination, then you should choose one
of the entries from the drop down. Minumum and Maximum Number - This is the
threshold value for minimum and maximum amount which can be entered for a
wage type in the Basic pay infotype (0008). If you create or change a wage type in the
Basic pay infotype (0008), the system checks the minimum value of a wage type
against the created or changed value. If the value entered in the infotype exceeds the
defined minimum value for the wage type, the system issues the relevant
information message. Indirect Valuation Indirect Evaluation Module -You can use the
indirect evaluation module to output various default values for wage types on
different infotypes. The most commonly used ones are as follows: TARIF - this
method valuates according to the "collective agreement group and level"
specifications you enter in the IMG. Wage types with TARIF will use the settings on
the wage type and the values held in table T510 to populate the relevant value into
the relevant infotype. There are 4 different module variants for TARIF – A, B, C and D.
See the SAP help for more assistance. PRZNT - this is used where you have a wage
type being a constant percentage of another wage type and wish this to be shown on
the infotype. The wage type in question and the wage type that the percentage is
based upon (base WT), are all held in table T539J. ANSAL - this is used in table T539J
for the wage types which you would like to be accumulated and shown as Annual
Salary on screen 2010 on infotype 0008 – Basic Pay. SUMME - very similar to the
'PRZNT' module except that the value of the wage type to be valuated indirectly is
always the entire basic pay. There are different module variants, which can be viewed
in more detail in the SAP help. CONST - Module for constant valuation of wage types
according to table T510K (V_T510K view).

1.1.1 Input combination amount


1.1.2 Definition
Define whether the amount and/or number/unit must be maintained for this wage type.

The following entry combinations are possible:

Amount Number/unit Meaning


'X' 'X' Either amount or number/unit

'-' '-' Neither amount nor number/unit

'+' '-' Amount essential, no number/unit

'-' '+' No amount, number/unit essential

'*' '*' At least amount or number/unit

'+' '.' Amount essential, number/unit optional

'.' '+' Amount optional, number/unit essential

'+' '+' Amount essential, number/unit essential

'.' '.' Amount optional, no number/unit

TARIF -
Valuation according to the "collective agreement group and level" specifications you enter in
the IMG step:

 Module variant 'A'

Country grouping derived from the employee's personnel area


Pay scale type from infotype 0008/0052
Pay scale area from infotype 0008/0052
Pay scale indicator derived from the employee subgroup
Pay scale group from infotype 0008/0052
Pay scale level from infotype 0008/0052
Wage type = SPACE

 Module variant 'B'

like module variant 'A' except:


Wage type = wage type to be valuated indirectly

 Module variant 'C'

like module variant 'A' except:


Pay scale level = SPACE
Wage type = wage type to be valuated indirectly

 Module variant 'D'

like modul variant 'A' except:


Pay scale group = SPACE
Pay scale level = SPACE
Wage type = wage type to be valuated indirectly

 TAROD (only for Public Sector, Germany)

Module variants: A, B

 VERGL (only for Public Sector, Germany, Austria)

Module variants: A, B, C, H, I, J

DIFFR (only for public service employees in Germany)


 Module variants 'A', 'B', 'C'

The difference is derived from the valuation with module VERGL and the valuation with module TARIF.

Valuation according to the "basic wage type" specifications in the IMG.

PRZNT -
Country grouping assigned to the employee master (derived from the personnel area)
MODUL = 'PRZNT'
Valuated wage type = indirectly valuated wage type

 Module variant 'B'

The basic pay is determined from the total of all basic wage type amounts entered in infotype 0008
according to the specifications in the "basic wage type valuation" step irrespective of which infotype is
being valuated. Wage types in the Wage Maintenance infotype (0052) are then valuated using the wage
types in the Basic Pay infotype (0008).
The value of the wage type to be valuated indirectly is calculated by multiplying the basic pay by the
percentage specified for the wage type to be valuated.

 Module variant 'D'

The basic pay is determined from the total of all basic wage type amounts specified in the infotype
currently being valuated according to the specifications in the "basic wage type valuation" step. The
wage types in the Wage Maintenance infotype (0052) are then valuated using the wage types in the
Basic Pay infotype (0008).
The value of the wage type to be valuated indirectly is calculated by multiplying the basic pay by the
percentage specified for the wage type to be valuated.

 Module variant 'I'

The basic pay is determined from the total of all basic wage type amounts weighted with GWCHT
according to the specifications in the "basic wage type valuation" step. All these basic wage types are
valuated indirectly even if these wage types are valuated directly in the infotype.
The value of the wage type to be valuated indirectly is calculated by multiplying the basic pay by the
percentage specified for the wage type to be valuated.

 Module variant 'J'


Like module variant 'I' except that basic wage types are not reduced.

SUMME
 Module variants 'B', 'D', 'I','J'

The 'SUMME' module corresponds to the 'PRZNT' module except that the value of the wage type to be
valuated indirectly is always the entire basic pay.

 Module variant 'M'

Corresponds to the module variant 'D'. The basis wage types are valuated as unreduced.

 Module variant 'O'

Corresponds to the module variant 'I'. The basic wage types are not weighted in payroll.

UNITS

 Module variants 'B', 'D', 'I', 'J'

The 'UNITS' module corresponds to the 'PRZNT' module with the exception that the value of the wage
type to be valuated indirectly is calculated by multiplying the basic pay by the number entered for the
wage type to be valuated.

CONST
Module for constant valuation of wage types according to table T510K (V_T510K view).

In this module variant, the entry from table T510K is assigned to the wage type.

M In this module variant, the entry from table T510K is multiplied with the Number field (Number) of the infotype.
The wage type must be set up in the wage type table (T511) accordingly. In other words, a unit must be allowed,
and the minimum number should, if possible, be 1. If no value is entered, the system uses 0 as the default.

P In this module type, the entry from table T510K is valuated as a percentage using the infotype's Number field
(Number). The wage type must be set up in the wage type table (T511) accordingly. In other words, a unit must
be allowed, and the minimum number should, if possible, be 1. If no value is entered, the system uses 0 as the
default.

ARBPL -

Valuation according to the specifications which you must make in the "Determine indirect valuation for
positions/work centers" section of the IMG.

OTYPE = module variant value


PLANS = position from the Organizational Assignment infotype (0001).
The total of the wage type values specified in the "Determine indirect valuation for positions/work centers" section
is the value used for the wage type to be valuated. If the wage type amount is zero, this wage type is valuated
indirectly before the total is formed.

ORTSZ - Family-related, cost-of-living, and social bonuses

The module variants of the ORTSZ indirect valuation module determine the components included in the
valuation. The Family Bonuses infotype (0595) contains information on whether a claim exists for each
component. For more information on the meaning of the individual components, refer to the documentation on
indirect valuation of family-related, cost-of-living, and social bonuses.

1. Module variant 1 (component for single persons): Only the component for single persons: LD.

2. Module variant 2 (component for spouse): If a claim exists for the whole of the spousal component,
the amount VH is read. If a claim exists for half of the spousal component, the amount VH is read and
divided by 2.

3. Module variant 3 (component for children): For each child or counted child, the total number of
children increases by 1. There is a child componentKI and an increase amount K1 for each child. The
increase amount is K1 for the first child, and KE for each subsequent child. An exception to this is used
for a count child (non-marital). No increase amount is paid in such a case. If the first child is also a
count child (non-marital), and the second child simply a count child, then increase amount K1 is used
for the second child.

4. Module variant 4 (component for spouse): If a claim exists for the whole or half of the spousal
component, either amount VH or amount V1 is read.

5. Module variant 5 (component for children): This rule is the same as module variant 3, except that
componentK3 is used instead of component KI from the birth of the third child inclusively.

6. Module variant 6 (component for children): Determination of the social bonus according to BMTG
including allowable bonuses.

7. Module variant 7 (TVöD: vested payment for children): Determination of the component for
children for cost-of-living bonus based on pay scale information before the data was transferred to the
TVöD (Collective Agreement for Public Sector). This information, if it exists, is taken from the Basic Pay
(0008) infotype history. If sufficient history does not exist, the old pay scale information is taken from the
backup table PDPBSTVOED_UEB that was written when the data was transferred. If no entry exists in
this table either, then the valuation is made as for module variant 3.

8. Module variant 8 (TVöD: component for spouse without discount): This module variant
calculates the spousal component without discount if the checkbox "No part-time reduction" is set for the
spouse in the infotype 0595. If the checkbox is not set, the amount is set to 0. The pay scale information
is determined analog to module variant 7. This is necessary to avoid the part-time reduction of the
spousal component when using an individual interim level.

Reduction method for indirect valuation -


The following reduction methods are planned:

 1

No reduction

 2

Reduction according to the capacity utilization level specified in the Basic Pay infotype (0008)

 3
Reduction according to
The regular weekly working time specified in table T508A

the pay-scale weekly working time specified in T510I

 4

Reduction according to
Weekly working hours specified in the Planned Working Time infotype (0007)

pay-scale weekly working hours specified in table T510I

 5

Reduction according to
Regular weekly working hours in T508A - PS working hours in T510I

pay-scale weekly working hours in T510I

 6

Reduction according to
Weekly working hours in the Planned Working Time infotype (0007) - PS wkly work. hours in T510I

pay-scale weekly working time in T510I

 Y

Use this option only if the view for the German public sector is active. Reduction is carried out according
to the numerator/denominator combination of basic pay. The Additional Information on Basic Pay
infotype (IT0304) is NOT taken into account in indirect valuation of wage types.

 Z

Use this option only if the view for German public sector is active. The reduction is carried out according
to the numerator/denominator combination of basic pay. The Additional Information on Basic Pay
infotype (0304) is taken into account in indirect valuation of wage types.

Rounding type
The following values are permitted:

'A': amount rounded down

'B': amount rounded up/down

'C': amount rounded up

Rounding divisor
Accepted values for the rounding divisor are 0 - 999999.
Examples
Rounding to 20 PENCE : divisor = 20 pence

Rounding to 1 POUND : divisor = 100 pence

Overwrite indicator for indirectly valuated wage type


This option specifies whether or not the Amount, Number or Unit wage type fields may be overwritten during
indirect valuation in master data maintenance.

 If you set the indicator, the fields are in input mode and can be overwritten.

 If you do not set the indicator, the fields are not in input mode.

The indicator must always be set for direct valuation.

SPRO – IMG - PERSONNEL MANAGEMENT – PERSONAL ADMINISTRATION –


PAYROLL DATA – BASIC PAY – WAGE TYPES – CHECK WAGE TYPE CATALOG –
CHECK WAGE TYPE CHARACTERISTICS – SELECT WAGE TYPE – SELECT DETAIL
BUTTON – MAKE THE NECESSARY CHANGES – SAVE.

CREATE WAGE TYPE MODEL:

In this step, you can set up default wage types based on your internal company
structure for the Basic Pay infotype (0008) using the feature Planned remuneration
specification (LGMST) defined in the previous step.

Example

You want the system to propose the wage type "standard pay" for salaried
employees and industrial workers in all personnel areas. So you assigned the key
"----1DU" to these two employee subgroups in the previous step. In this step, you
determine the default wage type "standard pay" for this key.

SPRO – IMG - PERSONNEL MANAGEMENT – PERSONAL


ADMINISTRATION – PAYROLL DATA – BASIC PAY – WAGE TYPES – –
REVISE DEFAULT WAGE TYPE – NEW ENTRIES – WAGE TYPE MODEL (FOR
YOUR CHOICE) – START DATE – END DATE – SEQUENCE (NUMBER OF
YOUR CHOICE) – MODE(EITHER O OR F) – SELECT WAGE TYPE FROM
SYSTEM – SAVE.

Note - Indicator Meaning


F The wage type is assigned for basic pay and cannot
be overwritten (fixed value).
O The wage type can be entered and/or
overwritten.
BLANK No wage type entries may be made.

GO TO IMG – DEFINE VALUATION OF BASE WAGE TYPES – NEW ENTRIES


– MOD – VALUATE – N – START DATE – END DATE – BASE – WAGE TYPE –
PERCENTAGE – SAVE.

FEATURE LGMST :

LGMST is a feature used to default values for planned payment specification from
T539A.It is used for payroll wage types.Eg: IT0008, we can default the no of wage
types depending on comp code, pers area etc etc...

In short we can default how many wagetypes & which wage types needed in the
particular IT.

GO TO IMG – ENTERPRISE STRUCTURE FOR WAGE TYPE MODEL – SELECT


MOLGA - CREATE – SELECT COUNTRY GROUPING 08 – SELECT 08 –
CREATE - SELECT FIELD FOR DECISION OPERATION – SELECT EG OR ESG –
ENTER – SELECT EG OR ESG – CREATE – ENTER EG OR ESG WHICH YOU
HAVE CREATED – SAVE - ACTIVATE.

Bank Details
Create Bank Connection Types
Use
In the SAP Best Practices the standard delivered bank connection types have not been modified.

Procedure
1. Access the activity using one of the following navigation options:
IMG Path Personnel Management  Personnel Administration  Personal Data
 Bank Details  Create bank connection types
Transaction SPRO
Code
2. On the Change View “Subtype Characteristics”: Overview screen, choose the New entries button
and enter the following values:
SubType Bank Connection Type Text Time Constraint
0 Main Bank 1

1 Other Bank 3

2 Travel Expenses 2

5 Main Bank for Off-Cycle 3

6 Other Bank for Off-Cycle 3

3. Choose Save.
Define Payment Methods
Use
In the SAP Best Practices the standard delivered entries for Payment Methods are used. It is
recommended that no modifications be made in this area in order to avoid unnecessary configuration
in further steps.

Procedure
1. Access the activity using one of the following navigation options:
IMG Path Personnel Management  Personnel Administration  Personal Data
 Bank Details  Define payment method
Transaction Spro
Code
2. On the Customizing: Maintain Payment Program screen choose the Pmnt methods in company
codes button.
3. On the Change View “Maintainence of Company Code Data for a Payment Method”: Overview
screen, choose the New entries button and enter the following values:
Pay Method Payment Method Text
C Check

P Bank transfer (ACH PPD)

T Transfer (Direct Deposit)

4. Choose Save.

Off-Cycle Payroll covers the various payroll functions that are not covered by the regular
Payroll Process. Off-Cycle Payroll includes the processing of special payments, entering
information for manually created checks, reversing payroll results and reprinting checks, all
of which may take place outside the regular payroll cycle.

1. You can run offcycle by using tcode ---> PUOC_10 – (10 is nothing but u.s.a country code
so you should enter the country code of your sap hr project) (Offcycle workbench)
2. can i make payments for future dates? ---> YES you can make future payments

3.where should i give the bonus amount?


---> Offcycle derives the amount from offcycle workbench if you manually enter the wage
type or can be derived from infotype 0267 (Additional offcycle payment)
If you are running for a single pernr then u can use offcycle workbench. But if you are
intending for multiple Pernr's use payroll driver.
Note: the default payment method thru offcycle is cheque and thru payroll driver is bank
transfer.
You can directly run a offcycle thru t-code PUOC_10. mention the payment date and the
particular wage type for which you are intending to pay the EE.

4. how can i see the results?


--->Go to t-code PC_PAYRESULT and you can see results generated for offcycle payroll run.
You can easily identify offcycle result as it is different from regular payroll.

5. how will it effect the clusters like RT?


--->In RT you will find payments only for off cycle. In clusters you will see BT table which
holds info about the payment
in there you will see that Payroll type and Payment date for which you have done the off
cycle run.

6. how will it effect regular payroll?


--> Itz a different component that regular payroll so it doesn’t effect regular payroll at all. But
you need to do off cycle postings separately.

7. how the results will be posted? what is the procedure to post?


---> We do the postings same as in regular payroll, but in off cycle posting we have to use
correct payroll type and payment date in postings and identifier ( to differentiate the off
cycle run done on the same day with same date ) if we use any.

Enterprise Structure for Wage Type Model


Procedure
1. Access the activity using one of the following navigation options:
IMG Path Personnel Management  Personnel Administration  Payroll Data 
Basic Pay  Wage Types  Enterprise Structure for Wage Type Model
Transaction SPRO
Code
Feature ‘LGMST’ determines which default wage types are assigned in basic pay infotype 0008. In
the SAP Best Practices these defaults are based on Employee Group/Subgroup:
 LGMST:
D MOLGA
10 D PERSG
10 1 D PERSK
10 1 U0 &LGMST=5/HOURLY,
10 1 ** &LGMST=5/SALARY,
10 2 &LGMST=5/PENSION,
10 4 D PERSK
10 4 U0 &LGMST=5/HOURLY,
10 4 ** &LGMST=5/SALARY,
10 7 D PERSK
10 7 U0 &LGMST=5/HOURLY,
10 7 ** &LGMST=5/SALARY,
10 * &LGMST=5/SALARY,

Revise Default Wage Types


Procedure
1. Access the activity using one of the following navigation options:
IMG Path Personnel Management  Personnel Administration  Payroll Data 
Basic Pay  Wage Types  Revise Default Wage Types
Transaction SPRO
Code
2. The following table illustrates the models and the corresponding Wage Types that are to be
defaulted on the Basic Pay infotype (IT0008).
WT Model Start date End date Seq. F/O WT Description
HOURLY 01/01/1900 12/31/9999 1 F 1001 Base Rate / Hourly Wage
PENSION 01/01/1900 12/31/9999 1 F 1004 Pension / Retiree Pay
SALARY 01/01/1900 12/31/9999 1 F 1003 Pay Period Salary

1.1.3 Define Valuation of Base Wage Types


Procedure
1. Access the activity using one of the following navigation options:
IMG Path Personnel Management  Personnel Administration  Payroll Data 
Basic Pay  Wage Types  Define Valuation of base wage types
Transaction SPRO
Code
2. In the SAP Best Practices only module ‘ANSAL’ has been used. This is used to define the Basic
Pay wage types that are to make up the Annual Salary, Benefit Salary and Compensation. If
additional wage types are created that are to be included in an annual salary or base
calculation additions will be required in this area. Although in the SAP Best Practices only
modules ‘ANSAL’ and ‘PRZNT’, additional modules can be used for base wage type valuation.
For additional information on modules refer to the SAP R/3 documentation on base wage
type valuation.
Model WT WT Text Seq Start date End date WT Percent
ANSAL /102 401(k) Wages 1 01/01/1800 12/31/9999 1001 100.00
ANSAL /102 401(k) Wages 2 01/01/1800 12/31/9999 1002 100.00
ANSAL /102 401(k) Wages 3 01/01/1800 12/31/9999 1003 100.00
ANSAL /BS1 Spending Acct. Annual Wt 1 01/01/1800 12/31/9999 1001 100.00
ANSAL /BS1 Spending Acct. Annual Wt 2 01/01/1800 12/31/9999 1002 100.00
ANSAL /BS1 Spending Acct. Annual Wt 3 01/01/1800 12/31/9999 1003 100.00
ANSAL ASAL Annual salary 1 01/01/1800 12/31/9999 1001 100.00
ANSAL ASAL Annual salary 2 01/01/1800 12/31/9999 1002 100.00
ANSAL ASAL Annual salary 3 01/01/1800 12/31/9999 1003 100.00
ANSAL ASAL Annual salary 4 01/01/1800 12/31/9999 1004 100.00
Model WT WT Text Seq Start date End date WT Percent
ANSAL BSAL Benefit-based salary 1 01/01/1800 12/31/9999 1001 100.00
ANSAL BSAL Benefit-based salary 2 01/01/1800 12/31/9999 1002 100.00
ANSAL BSAL Benefit-based salary 3 01/01/1800 12/31/9999 1003 100.00
ANSAL BSAL Benefit-based salary 4 01/01/1800 12/31/9999 1004 100.00
ANSAL CSAL Planned remuneration 1 01/01/1800 12/31/9999 1001 100.00
ANSAL CSAL Planned remuneration 2 01/01/1800 12/31/9999 1002 100.00
ANSAL CSAL Planned remuneration 3 01/01/1800 12/31/9999 1003 100.00
ANSAL NSAL Annual salary (proposed) 1 01/01/1800 12/31/9999 ASAL 100.00
ANSAL NSAL Annual salary (proposed) 2 01/01/1800 12/31/9999 CHNG 100.00
PRZNT BSAL Benefit-based salary 1 01/01/1800 12/31/9999 1003 150.00

1.1.4 Annual Salary Definition


Annual salary is derived based on the number of pay frequencies within the year. In the SAP Best
Practices for HCM USA feature ‘PFREQ’ has not been modified.
 PFREQ:
D MOLGA
10 &PFREQ=52, NEXTR
10 1 &PFREQ=26, NEXTR
10 2 &PFREQ=24, NEXTR
10 3 &PFREQ=13, NEXTR
10 4 &PFREQ=12, NEXTR
10 5 &PFREQ=04, NEXTR
10 6 &PFREQ=01,

1.2 Recurring Payments and Deductions


1.2.1 Reasons for Change
Procedure
1. Access the activity using one of the following navigation options:
IMG Path Personnel Management  Personnel Administration  Payroll Data 
Recurring Payments and Deductions  Define reasons for change
Transaction SPRO
Code
In the SAP Best Practices for HCM USA the following Reason Codes are delivered for Recurring
Earnings/Deductions infotype (IT0014):
Reason Description
01 Pay Scale Increase
02 Tax Directive

1.2.2 Wage Types for Recurring Payments and Deductions


Procedure
1. Access the activity using one of the following navigation options:
IMG Path Personnel Management  Personnel Administration  Payroll Data 
Recurring Payments and Deductions  Wage Types  Check wage
type group ‘Recurring Payments and Deductions’
Transaction SPRO
Code
2. Wage types for the Recurring Earnings and Deductions infotype 0014 are provided to support
ongoing earnings and deductions in the SAP Best Practices The following wage types are
delivered in the SAP Best Practices for Recurring Earnings/Deductions:
Wage Type Wage Type Text Wage Type Wage Type Text
1120 Uniform Allowance 2012 Cafeteria Deduction
1121 Equipment Allowance 2015 Bond Purchase - Deduction
1122 Car Allowance 2035 Computer Loan - Deduction
1500 1099R Non-taxable Wages 2040 401K Loan Deduction
1501 1099R Taxable Wages 2045 Education Loan - Deduction
2000 Charitable Donation – Amt 2855 ClmClr Dedn RepayPlan Tx0
2004 Misc. Dedn. Arrears dedn. 2858 ClmClr Dedn RepayPlan Tx1
2010 Parking Deduction 2861 ClmClr Dedn RepayPlan Tx2
2011 Miscellaneous Deduction

For detailed information regarding all wage types that correspond to the payroll-related
configuration in Personnel Administration, please refer to the Wage Type Documentation
spreadsheet.

1.2.3 Payment Models OK


Procedure
1. Access the activity using one of the following navigation options:
IMG Path Personnel Management  Personnel Administration  Payroll Data 
Recurring Payments and Deductions  Payment Models  Define
Payment Models
Transaction SPRO
Code
2. Payment models have been defined for every combination of date modifier, period
parameter and pay period. The defaults for payment/deduction schedules are controlled via
feature ‘MODDE’ in combination with table entries. In the SAP Best Practices for HCM USA,
the feature has been updated to assign the group based on the delivered payroll areas.
 MODDE:
D ABKRS
10 &MODDE=FE10, “Monthly “BEST PRACTICES USA
11 &MODDE=FE11, “Semi-Monthly “BEST PRACTICES USA
12 &MODDE=FE12, “Weekly“BEST PRACTICES USA
13 &MODDE=FE13, “Bi-Weekly“BEST PRACTICES USA
1. The defaults for the payments models are then assigned for specific wage types for each
employee group. Generally, most deduction amounts are processed in each pay period
therefore; the assignment of a payment/deduction schedule is not necessary. In the SAP Best
Practices for HCM USA, default payment frequency models are assigned to the Charitable
Donation deduction. Additional wage types can be assigned here if there is a requirement at the
customer site
Group Wage Type Wage Type Text Payment Model Name
FE10 2000 Charitable Donation UM02 Every period – Annual input value
FE11 2000 Charitable Donation US00 Last pay period of month
FE12 2000 Charitable Donation UW02 Last pay period of month
FE13 2000 Charitable Donation UB02 Last pay period of month
For additional information on Payment models, refer to the Payroll Configuration Guide
(K05_BB_ConfigGuide_EN_US.doc on the documentation DVD under
\\BBLibrary\Documentation).

1.3 Additional Payments


1.3.1 Reasons for Change
Procedure
1. Access the activity using one of the following navigation options:
IMG Path Personnel Management  Personnel Administration  Payroll Data 
Additional Payments  Define reason for change
Transaction SPRO
Code
2. In the SAP Best Practices for HCM U.S., the following reason codes are delivered for
Additional Payments infotype (IT0015):
Reason Description
01 Pay Scale Increase
02 Tax Directive
U1 Change in amount

1.3.2 Wage Types for Additional Payments


Procedure
1. Access the activity using one of the following navigation options:
IMG Path Personnel Management  Personnel Administration  Payroll Data 
Additional Payments  Wage Types  Check wage type group
‘Additional Payments’
Transaction SPRO
Code
2. Wage types for the Additional Payments infotype 0015 are provided to support one time
payments and deductions in the SAP Best Practices for HCM U.S. All wage types have been
assigned availability of only once for a specific time and gaps are permitted. The following
wage types are delivered in the SAP Best Practices for HCM USA for Additional Payments and
Deductions:
Wage Type Wage Type Text Wage Type Wage Type Text
1100 Tip income 2007 Miscellaneous Arrears Recovery
1105 Gross up regular method 2008 Credit arrears $ purge
1107 Gross up supplemental method 2010 Parking Deduction
1108 Gross up result-supp method 2011 Miscellaneous Deduction
1109 Non-tax income 2012 Cafeteria Deduction
1110 Bonus 2015 Bond Purchase - Deduction
1112 Commission 2016 Bond Purchase - Balance
1113 Severance pay 2035 Computer Loan - Deduction
1120 Uniform allowance 2036 Computer Loan - Balance
1121 Equipment allowance 2040 401K Loan Deduction
1122 Car allowance 2045 Education Loan - Deduction
1123 Tuition reimbursement – taxable 2046 Education Loan - Balance
1124 Tuition reimbursement - non-tax 2057 PPD: Deduction - Benefits
1125 Relocation expenses 2058 PPD: Reimburse - Benefits
Wage Type Wage Type Text Wage Type Wage Type Text
1500 1099R Non-Taxable wages 2061 PPD: Payment - Benefits
1501 1099R Taxable Wages 2856 Claim Clearing Bal Tx0
1510 1099R Total Distribution 2859 Claim Clearing Bal Tx1
2000 Charitable Donation – Amt 2862 Claim Clearing Bal Tx2
2002 Charitable - Balance 2915 Cash Non-Taxable
2004 Miscellaneous Dedn arrears dedn 2916 Claim of right
2005 Miscellaneous Dedn arrears bal 6055 Non Cash taxable

For detailed information regarding all wage types that correspond to the payroll-related
configuration in Personnel Administration, please refer to the Wage Type Documentation
spreadsheet.

1.4 Off Cycle Payments


1.4.1 Wage Types for Off Cycle Payments
Procedure
1. Access the activity using one of the following navigation options:
IMG Path Personnel Management  Personnel Administration  Payroll Data 
Additional Payments: Off-Cycle  Wage Types  Check wage type
group ‘One Time Payments Off-Cycle’
Transaction SPRO
Code
2. Wage types for the Additional Payments infotype 0267 are provided to support one-time
special payments such as Bonuses in the SAP Best Practices for HCM U.S. The following wage
types are delivered in the SAP Best Practices for HCM USA for Off Cycle Payments:
Wage Type Wage Type Text Wage Type Wage Type Text
1105 Gross up regular method 2803 Claim Repayment Txblty 1
1107 Gross up suppl method 2804 Claim Forgiveness Txblty 2
1111 Bonus - special pay run 2805 Claim Payment Txblty 2
1112 Commission 2850 CC Dedn Recovery Txblty 0
1113 Severance pay 2851 CC Dedn Recovery Txblty 1
2800 Claim Forgiveness Txblty 0 2852 CC Dedn Recovery Txblty L
2801 Claim Payment Txblty 0 2853 CC Dedn Recovery Txblty G

2802 Claim Forgiveness Txblty 1

For detailed information regarding all wage types that correspond to the payroll-related
configuration in Personnel Administration, please refer to the Wage Type Documentation
spreadsheet.

1.5 Employee Remuneration Information


1.5.1 Wage Types for Employee Remuneration
Procedure
3. Access the activity using one of the following navigation options:
IMG Path Personnel Management  Personnel Administration  Payroll Data 
Employee Remuneration Information - Wage Types  Check Wage
Type Group ‚Employee Remuneration Information
Transaction SPRO
Code
4. Wage types for the Employee Remuneration infotype 2010 are provided to support the entry
of ‘Time’ related payments such as Overtime and Shift Premiums in the SAP Best Practices
for HCM U.S. The following wage types are delivered in the SAP Best Practices for HCM USA
for Employee Remuneration Information:
Wage Type Wage Type Text Wage Type Wage Type Text
1200 Regular working time 1252 Sick pay
1201 Lump sum period hours 1253 Comp time taken
1202 On Call / Standby 1254 Jury duty
1203 Training – internal 1255 Bereavement leave
1204 Training – external 1258 Family Medical Leave
1205 Overtime paid 1.0 1259 Maternity leave
1206 Overtime paid 1.5 1260 Short term disability
1207 Overtime paid 2.0 1264 Other Paid Absences
1210 Sunday premium 1410 Regular hours - tips
1211 Holiday premium 1411 Regular hours - tips
1212 Evening Shift premium 1415 Overtime hours - tips
1213 Night Shift premium 1416 Overtime hours - tips
1214 Weekend Shift premium 1420 Direct tip
1215 Call In pay 1425 Indirect tip
1250 Holiday pay 1430 Gross sales

1251 Vacation pay

For detailed information regarding all wage types that correspond to the payroll-related
configuration in Personnel Administration, please refer to the Wage Type Documentation
spreadsheet.

1.6 Leave Compensation


1.6.1 Time Quota Compensation Methods
Procedure
1. Access the activity using one of the following navigation options:
IMG Path Personnel Management  Personnel Administration  Payroll Data 
Leave Compensation  Time Quota Compensation  Define Time
Quota Compensation Methods
Transaction SPRO
Code
2. With time quota compensation (Infotype 0416), you can compensate entitlement to time off,
in particular leave entitlement, which is maintained in absence quotas. In the SAP Best
Practices for HCM USA, Quota Compensation methods for IT0416 have been configured for
each absence quota. If additional absence quotas are created in Time Management is may
be necessary to extend the delivered customizing.
ES PS Comp. Description Rul Description Quota
G G Method e Type

1 10 1000 Free Compensation

1 10 1001 Vacation Payout 003 Vacation


ES PS Comp. Description Rul Description Quota
G G Method e Type

1 10 1002 Sick time payout 004 Sick/Illness

1 10 1003 Personal Time Off payout 010 Personal Time Off

1 10 1004 Floating Holiday payout 002 Floating Holiday


Overtime Comp Time Comp Time for
1 10 1005 Payout 001 Overtime

2 10 1000 Free Compensation

2 10 1001 Vacation Payout 003 Vacation

2 10 1002 Sick time payout 004 Sick/Illness

2 10 1003 Personal Time Off payout 010 Personal Time Off

2 10 1004 Floating Holiday payout 002 Holiday Lieu


Overtime Comp Time Comp Time for
2 10 1005 Payout 001 Overtime

4 10 1000 Free Compensation

4 10 1001 Vacation Payout 003 Vacation

4 10 1002 Sick time payout 004 Sick/Illness

4 10 1003 Personal Time Off payout 010 Personal Time Off

4 10 1004 Floating Holiday payout 002 Holiday Lieu


Overtime Comp Time Comp Time for
4 10 1005 Payout 001 Overtime

1.6.2 Wage Types for Time Quota Compensation


Procedure
1. Access the activity using one of the following navigation options:
IMG Path Personnel Management  Personnel Administration  Payroll Data 
Leave Compensation  Time Quota Compensation  Wage Types 
Check Wage Type Group’ Time Quota Compensation’
Transaction SPRO
Code
2. The following wage types are delivered in the SAP Best Practices for HCM USA for Time
Quota Compensation:
Wage Type Wage Type Text
1294 FMLA Payout
1295 Vacation Payout
1296 Personal Time Off Payout
1297 Floating Holiday Payout
1298 Comp Time Payout
1299 Sick Payout
1.7 Membership Fees
1.7.1 Membership Types
Procedure
1. Access the activity using one of the following navigation options:
IMG Path Personnel Management  Personnel Administration  Payroll Data
 Membership Fees  Define Types
Transaction SPRO
Code
2. In the SAP Best Practices for HCM USA, Memberships infotype 0057 is used primarily for
Union Dues. If it is necessary to process other types of memberships such as Health Club,
Golf Club, etc. additional configuration can be added in this area. The following membership
types are delivered in the SAP Best Practices for HCM USA:
Subtype Membership Type Text Time Constraint
US01 Local 112 2
US02 Local 83 2

With use of a dynamic actions, infotype 0057 will be created in the background for Union
employees. A personnel calculation rule ZUSO has been created to take a deduction
based on a constant in T511K and the personnel calculation rule. A flat rate of $50.00 has
been configured for employees in Local 112 and a multiplier of 2 hours times the rate for
employees in Local 83.

1.7.2 Wage Types for Membership Fees


Procedure
1. Access the activity using one of the following navigation options:
IMG Path Personnel Management  Personnel Administration  Payroll Data 
Membership Fees  Membership Fees  Check wage type group
’Membership Fees’
Transaction SPRO
Code
2. Wage types for the Memberships infotype 0057 are provided to support Union Due
Deductions in the SAP Best Practices for HCM U.S. The following wage type is delivered in the
SAP Best Practices for HCM USA to support this process:
Wage Type Wage Type Text
2020 Union dues – amount
2021 Union dues – percent

For detailed information regarding all wage types that correspond to the payroll-related
configuration in Personnel Administration, please refer to the Wage Type Documentation
spreadsheet.

1.7.3 Revise Pay Scale Groups and Levels


In SAP Best Practices for HCM USA Salaried and Salaried Non-Exempt employees are indirectly
evaluated while Union and Hourly employees are directly evaluated. The Union and Hourly base rate
will default in Infotype 0008 based on entries in Pay Scale Groups and Levels. The Salaried and
Salaried Exempt have Pay Grades and Levels within Compensation Administration, which are
referenced when directly entering salary amounts in Info type 0008.
SAP delivers standard Pay Scale Groups and Levels for Salaried and Salaried Non-Exempt
employees, such as GRD01, EXEC, NPS, and SALES. SAP Best Practices for HCM USA
does not use them, but you will find them in the table.

Procedure
2. Access the activity using one of the following navigation options:
IMG Path Personnel Management  Personnel Administration  Payroll Data 
Basic Pay  Revise Pay Scale Groups and Levels
Transaction SPRO
Code
3. On the Determine Work Area: Entry , enter the following values and press enter.
Country Grouping Pay Scale Type Pay Scale Area
10 01 01

Many examples of Pay Scale Groups and Levels are provided in the SAP Best Practices for HCM
USA to provide the customer with an understanding of how to represent different types of employees
with different pay scales.

These are only example pay structures and must be updated to meet customer needs.
Type Area Grp PS Group Level WT Amount Currency
3000
03 01 1 H001 00 8.00 USD
3000
03 01 1 H001 01 8.50 USD

03 01 1 H001 02 9.00 USD

03 01 1 H001 03 9.50 USD

03 01 1 H001 04 10.00 USD

03 01 1 H001 05 11.00 USD

03 01 1 H002 00 12.35 USD

03 01 1 H002 01 14.55 USD

03 01 1 H002 02 16.00 USD

03 01 1 H002 03 20.75 USD

03 01 1 H002 04 21.00 USD

03 01 1 H002 05 23.25 USD

03 02 1 H001 00 10.00 USD

03 02 1 H001 01 10.50 USD

03 02 1 H001 02 11.00 USD

03 02 1 H001 03 11.50 USD

03 02 1 H001 04 12.00 USD

03 02 1 H001 05 14.00 USD


Type Area Grp PS Group Level WT Amount Currency

03 02 1 H002 00 16.35 USD

03 02 1 H002 01 17.55 USD

03 02 1 H002 02 19.00 USD

03 02 1 H002 03 21.75 USD

03 02 1 H002 04 23.00 USD

03 02 1 H002 05 25.25 USD

04 03 1 U001 00 12.35000 USDN

04 03 1 U001 01 13.55000 USDN

04 03 1 U001 02 15.00000 USDN

04 03 1 U001 03 17.75000 USDN

04 03 1 U002 00 19.00000 USDN

04 03 1 U002 01 22.25000 USDN

04 03 1 U002 02 24.00000 USDN

04 03 1 U002 03 28.85000 USDN

04 03 1 U003 00 30.00000 USDN

04 03 1 U003 01 31.00000 USDN

04 03 1 U003 02 32.00000 USDN

04 03 1 U003 03 34.00000 USDN

04 04 1 U001 00 14.75000 USDN

04 04 1 U001 01 16.20000 USDN

04 04 1 U001 02 18.00000 USDN

04 04 1 U001 03 19.05000 USDN

04 04 1 U002 00 22.00000 USDN

04 04 1 U002 01 24.00000 USDN

04 04 1 U002 02 27.00000 USDN

04 04 1 U002 03 30.00000 USDN

04 04 1 U003 00 31.00000 USDN

04 04 1 U003 01 32.45000 USDN

04 04 1 U003 02 33.20000 USDN

04 04 1 U003 03 34.00000 USDN

1.7.4 Define Pay Grades and Levels


Procedure
1. Access the activity using one of the following navigation options:
IMG Path Personnel Management  Personnel Administration  Payroll Data 
Basic Pay  Check Total Salary Against Salary Range  Define Pay
Grades and Levels
Transaction SPRO
Code
2. In SAP Best Practices for HCM USA, the pay grades and levels to make up the salary structures is
defined here.
3. On the ’Work Area’ entry field enter value ’ 10’ for’ Country Grouping’ and choose the ’Enter’
button. On the ’Change View „Grades“: Overview’ screen, select value ’Salaried Exempt – East
Region’ and double click on the ’Pay Grade Levels’ dialog structure. Repeat the steps with values
’Salaried Exempt – West Region’, ’Salaried Non-Exempt – East Region’, and ’Salaried Non-
Exempt – West Region’.
4. On the ‘Change View “Pay Grade Levels”: Overview ‘screen you will see the following values:
Pay Pay Description Pay Start Date End Date Currenc Time
Grade Grade Grade y Unit
Type Area
Salaried Exempt – 01/01/190 12/31/999
01 01 East Region EXEC 0 9 USD Annually
Salaried Exempt – 01/01/190 12/31/999
01 02 West Region EXEC 0 9 USD Annually
Salaried Non-Exempt 01/01/190 12/31/999
02 01 – East Region GRP01 0 9 USD Annually
Salaried Non-Exempt 01/01/190 12/31/999
02 02 – West Region GRP01 0 9 USD Annually

Description Leve Minimum. Grade Maximum Grade Reference


l Level Level Salary
Salaried Exempt – East Region 00 85,000.00 210,000.00 135,000,00
Salaried Exempt – West Region 00 80,000,00 180,000,00 120,000,00
Salaried Non-Exempt – East
Region 00 20,000,00 35, 000,00 27, 000,00
01 30,000,00 45, 000,00 37, 000,00
02 40,000,00 55, 000,00 47, 000,00
03 50,000,00 65, 000,00 57, 000,00
04 60,000,00 75, 000,00 67, 000,00
05 70,000,00 90, 000,00 80, 000,00
Salaried Non-Exempt – West
Region 00 16,000,00 24,000,00 20,000,00
01 25,000,00 45,000,00 35,000,00
02 32,000,00 55,000,00 32,000,00
03 42,000,00 65,000,00 53,000,00
04 55,000,00 75,000,00 55,000,00
05 62,000,00 85,000,00 73,000,00

1.8 Check Number of Periods


1.8.1 Decision Trees for Features (Customers) and Title of
Customer Features
Use
In this step you determine the number of periods in a year. The values specified in this step can be
used to convert the time unit. A conversion may be necessary if the salary structure and the Basic
Pay infotype (0008) do not have the same time unit.

Procedure
1. Access the activity using one of the following navigation options:
IMG Path Personnel Management  Personnel Administration  Payroll Data 
Basic Pay  Check Total Salary Against Salary Range  Check
Number of Periods
Transaction SPRO
Code
2. On the “Process feature PFREQ: decision tree” screen, you will see the following:
PFREQ Payment frequency for annual salary

MOLGA Country Grouping

07 Canada

Weekly 52
Two-weekly 26
Half-monthly 24
Four-weekly 13
Monthly 12
Quarterly 04
Half-yearly 01

1.8.2 Define Agreed Salary


Use
Some employees may be paid an amount negotiated with the company, known as an 'agreed salary',
regardless of the amount specified in the corresponding collective agreement. In most cases the
agreed salary is formed by:

 A set of standard wage types, and


 An 'incentive' wage type that consists of the difference between the agreed salary and the
collective agreement wage types.

Procedure
1. Access the activity using one of the following navigation options:
IMG Path Personnel Management  Personnel Administration  Payroll Data
 Basic Pay  Define agreed salary
Transaction SPRO
Code
2. On the ‘Display View “Wage Type Characteristics”: Overview’ screen, you will see the
following value:
Wage Type Wage Type Long Text Start Date End DateEnd Date
/102 401(k) Wages 01/01/1900 12/31/9999

1.8.3 Maintain Payroll Simulation Feature


Use
You can start a payroll simulation for the chosen personnel area from the Basic pay infoytpe (0008).
After the payroll has been successfully completed, a remuneration form is displayed in a modal
dialog box. In this step you determine whether the payroll simulation push button is displayed in the
Basic pay infotype (0008). You also determine here with which variant of the payroll program the
payroll simulation is started by working the push button. The variant for the remuneration
statement, defined in the variant of the payroll program, determines in which format the
remuneration statement is displayed.

Procedure
1. Access the activity using one of the following navigation options:
IMG Path Personnel Management  Personnel Administration  Payroll Data 
Basic Pay  Maintain payroll simulation feature
Transaction SPRO
Code
2. On the ‘Process feature PM004; decision tree’ screen, you will see the following value:
PM004 Determining the Simulation Variant for the Payroll Program

SCODE Simulation Code

GV Taxation of Pensions

GMVS

IT Basic Pay infotype

PM HR Funds and Position Management

1.8.4 Define Pay Scale Salary Ranges


In SAP Best Practices for HCM USA, the salary ranges have been configured as Pay Grades and
Levels within Compensation Administration.
SAP delivers standard Pay Scale Salary Ranges. However, SAP Best Practices for HCM
U.S. does not use them, but you will find them in the table.

Procedure
1. Access the activity using one of the following navigation options:
IMG Path Personnel Management  Personnel Administration  Payroll Data 
Basic Pay  Define pay scale salary ranges
Transaction SPRO
Code

1.9 Pay Scale Changes


1.9.1 Specify Pay Scale Reclassification
Procedure
1. Access the activity using one of the following navigation options:
IMG Path Personnel Management  Personnel Administration  Payroll Data 
Basic Pay  Pay Scale Changes - Specify Pay Scale Reclassification
Transaction SPRO
Code
2. Pay scale reclassification allows the client to automatically update the pay scale group and level
information on the Basic Pay infotype 0008. The data will be automatically updated when the
requirements for meriting reclassification are met, such as length of time at the enterprise, or
amount of time worked, for a specific employee.
Sample pay scale classifications have been configured in the SAP Best Practices for HCM U.S. If the
client chooses to process automatic reclassification this configuration will require modification to meet
their requirements.
Type Text Area Text CAP PS Group Level GrMD NPSGroup NPS Level
03 Hourly 01 East 1 H001 00 0100 H001 01
03 Hourly 01 East 1 H001 01 0100 H001 02
03 Hourly 01 East 1 H001 02 0100 H001 03
03 Hourly 01 East 1 H001 03 0100 H001 04
03 Hourly 01 East 1 H001 04 0100 H001 05
03 Hourly 01 East 1 H001 05 0100 H002 00
03 Hourly 02 West 1 H001 00 0100 H001 01
03 Hourly 02 West 1 H001 01 0100 H001 02
03 Hourly 02 West 1 H001 02 0100 H001 03
03 Hourly 02 West 1 H001 03 0100 H001 04
03 Hourly 02 West 1 H001 04 0100 H001 05
03 Hourly 02 West 1 H001 05 0100 H002 00
04 Union 03 Local 112 1 U001 00 0100 U001 01
04 Union 03 Local 112 1 U001 01 0100 U001 02
04 Union 03 Local 112 1 U001 02 0100 U001 03
04 Union 03 Local 112 1 U001 03 0100 U002 00
04 Union 04 Local 83 1 U001 00 0100 U001 01
04 Union 04 Local 83 1 U001 01 0100 U001 02
04 Union 04 Local 83 1 U001 02 0100 U001 03
04 Union 04 Local 83 1 U001 03 0100 U002 00
Payroll Transaction Codes –

Payroll
PC00_M10_CALC_SIMU - Simulation
PC00_M99_PA03_RELEA - Release payroll
PC00_M10_CALC - Start payroll
PC00_M99_PA03_CHECK - Check result
PC00_M99_PA03_CORR - Corrections
PC00_M99_PA03_END - Exit payroll
PC00_M10_CEDT - Remuneration statement
PC00_M10_HRF - Remuneration statement with HR-Forms
Bank transfer
PC00_M10_CDTE - Test transfer
PC00_M10_CDTC - Pre-program DME
PC00_M10_FFOT - Create DME
PC00_M99_FPAYM - Create DME - Payment Medium Workbench
FDTA - DME management
PC00_M10_FFOC - Print check
PC00_M10_RFFOAVIS - Print zero net advices

Off-cycle
PUOC_10 - Off-Cycle Workbench (10 refers to the country code for u.s.a so you should use
the country code of your client project)
PUOCBA - OC Batch: Follow-up for payroll
PUOCBLTI - OC Batch: Mass LTI-processing
PUOCLG - List batch table
PUOCLL - List replacements, reversals

Subsequent activities
Per payroll period
Evaluation
PC00_M10_CDTB - Advance payment
Posting to accounting
PC00_M99_CIPE - Execute posting run
PC00_M99_PPM - Execute posting run for payments
PCP0 - Process posting run
PC00_M99_CIPC - Check completeness
Third-party remittance
PC00_M99_URME - Evaluate remittance (New)
PC00_M10_U500 - Evaluation run
PC00_M99_URMU - Store evaluation run
PC00_M99_URMP - Create posting run
PCP0 - Process posting run
PC00_M99_URMR - Reconcile postings
PC00_M99_URMW - Check processing classes
PC00_M99_URMA - Acknowledge postings
PC00_M99_URMD - Undo processing steps
PC00_M99_URMC - Run remittance completeness check
Garnishment status
PC00_M10_IPIT0 - Active -> inactive
PC00_M10_IPIT1 - Pending -> active
PC00_M10_IPIT2 - Delimit
Lists/statistics
PC00_MNA_CC_ADM - Cost Center Report - Administrator
PC00_M10_CLJN - Payroll journal
PC00_M99_CWTR - Wage type reporter
PC00_M10_REC - Payroll reconcilation report
PC00_M10_CPRS - Payroll reconciliation report (scheduler)
Period-independent
Evaluation
Posting to accounting
PC00_M99_CIPE - Execute posting run
PCP0 - Process posting run
PC00_M99_CIPC - Check completeness
Third-party remittance
PC00_M99_URME - Evaluate remittance (New)
PC00_M10_U500 - Evaluation run
PC00_M99_URMU - Store evaluation run
PC00_M99_URMP - Create posting run
PCP0 - Process posting run
PC00_M99_URMR - Reconcile postings
PC00_M99_URMW - Check processing classes
PC00_M99_URMA - Acknowledge postings
PC00_M99_URMD - Undo processing steps
PC00_M99_URMC - Run remittance completeness check
Payroll supplement
Garnishments
PC00_M10_CPL3U0 - Garnishment statements
S_AHR_61016146 - Garnishment details report
PC00_M10_CPL5U0 - Print notice letter
PC00_M10_CPL7U0 - Print answer letter
PAUY - Adjustment Workbench (special retro processing)
PAUX - Adjustment Workbench
PU19 - Tax Reporter
PC00_M10_REC - Payroll reconciliation report
PC00_M10_CPRS - Payroll reconciliation report (scheduler)
PC00_M07_STDR - STD/LTD report
PC00_M10_CLAIMS - Claims processing
Tax utilities
PC00_M10_UBSIU7 - Compare delivered tax authorities
PC00_M10_UTMDU0 - Taxability models / tax types by tax authority
PC00_M10_UAUTU1 - Display tax authorities
PC00_M10_UAUTU2 - Tax authorities not in residence or work tax area
PC00_M10_UBTXU0 - Update clients
PC00_M10_UTAX - Delete entries

Outsourcing
Export
PC00_M10_OTEX - Gross Payroll Export
PC00_M10_OTEM - Master Data Export
S_PH0_48000542 - Mini Master Export
S_PH0_48000543 - Combined Payroll Export
PC00_OTTM - Time Wage Type Export
WE05 - Display IDocs
WE14 - Process Outbound
Import
PC00_OTIN - Process Inbound
WE05 - Display IDocs
PC00_OTRL - Release IDocs
PC00_M10_OTCL - Payroll Import
PC00_M10_OTLJ - Payroll Journal
PC00_OFPM - Special pay model
Tax Services
PC00_M10_OTUT - Periodic/Quarterly Reporting
PC00_M10_OTUY - Yearly Reporting
WE05 - Display Idocs
WE14 - Release Idocs
PC00_M10_OTUR - Reconciliation Utilities
Utilities
PC00_M10_OTUT_SETUP - Conversion
PC00_M10_OTUT_DISP - Pay Period Tax Field Display
PC00_M10_OTL1 - Cross Year Adjustment Display
PC00_M10_OTU1 - IF cluster delete by pay period

Info system
Payroll results
PC00_MNA_CC_MAN - Cost Center Report - Manager's Overview
S_AHR_61018754 - Display payroll results
S_ALR_87014259 - Payroll journal
S_PH9_46000172 - Wage type reporter
PC00_M10_REC - Payroll reconciliation report
PC00_M10_CPRS - Payroll reconciliation report (scheduler)
S_PH9_46000232 - Tip income and allocated tips report
S_PH9_46000233 - Pensionable earnings and hours report
S_AHR_61016146 - Garnishment details
S_AHR_61016148 - Workers' compensation report
Pay date
S_ALR_87014136 - Paydays on holidays or weekends
S_ALR_87014137 - Payday calendar
Tax
S_PH9_46000360 - Exemption expiration report
S_PH9_46000361 - W-4 withholding allowance report
S_AHR_61016142 - Tax infotype summary
S_AHR_61018777 - Taxability models/tax types by tax authority
S_AHR_61018778 - Display tax authorities
S_AHR_61018779 - Tax authorites not included in a residence or work tax area
PC00_M10_REC - Payroll reconcilation report
PC00_M10_CPRS - Payroll reconciliation report (scheduler)
Tax Reporter reconciliation
S_AHR_61018782 - Tax amounts in tax interface tables
PC00_M10_REC - Payroll reconcilation report
PC00_M10_CPRS - Payroll reconciliation report (scheduler)
Public Sector
Certification and Licensing
P0000_M10_CL0_PBS - Generate Qualification Groups or Qualifications
P0000_M10_CL1_PBS - Convert Certificate or License to Qualification
P0000_M10_CL2_PBS - Out-of-Field Report
P0000_M10_CL3_PBS - Perform Certificates/Licenses Selection
P0000_M10_CL4_PBS - Check Qualification and Certificate Consistency
Equal Employment Opportunity
P0000_M10_EEO_PBS - EEO-4 and EEO-5 Reporting
Savings Bond Purchase Plans
P0000_M10_SBT_PBS - Savings Bonds Purchase
P0000_M10_SVB_PBS - Display Savings Bonds Purchases
Non-Resident Alien Processing
P0000_M10_ORM_PBS - Form 1042-S Printing
P0000_M10_SPT_PBS - Substantial Presence Test
Effort Reporting
PRP_US_EFFR_BUND_ACT - Actual Effort Certification by Employee
PRP_US_EFFR_BUND_DUN - Dunning Report

Tools
PC_PAYRESULT - Display Results
SLG1 - Analyze Application Log
PUST - HR Process Workbench
PA03 - Control Record
PC00_M99_UTSV - List TemSe Objects
PC00_M99_CPRC - Payroll Calendar
Outsourcing - Interface Toolbox
Data Export
PU12_EXPORT - Export
PU12_CONVERT - Conversion
PU12_DOWNLOAD - Download
Export History
PU12_SHOW_CLUSTER - Display Interface Results
PU12_SHOW_FILE - Display TemSe File
Data Import
PU12_IDOC_CREATE - Create Idocs
PU12_IDOC_PROCESS - Process Idocs
PU12 - Interface Toolbox
Customizing Tools
PEST - Maintain Process Model
PE01 - Schema
PE02 - Calculation Rule
PE04 - Function/Operation
PU30 - Wage Type Maintenance
PC00_M99_DLGA20 - Wage Type Utilization
PC00_M99_DKON - Wage Type Assignment - Display G/L Accounts
PU22 - Archiving
Problem Solving
PU03 - Maintain Payroll Status
PU01 - Delete Payroll Result
PC00_M99_UDIR - Restructure Payroll Directory
PC00_M99_UCRT - Restructure Cumulation Tables
Settings
PC00_M99_CURSET - Current settings
PC00_M99_ABKRS - Set payroll area