HR305 Course Notes

Instructor: Carloine Chapeauman

Familarization of SAP main menu, creating new role, and assign role to user.

User Menu




TC: SPRO_ADMIN is used to create your own IMG for a project. You do not need
to use SPRO to search entire configuration. Within the project, you can assign
resource, monitor status, and prepare documentation.



Select appropriate IMG tasks.



Generate Project IMG after selection of IMG items

Display your Project IMG



User profile:

There are two important user parameters required for HR/PAY processing; MOLGA (
Country code PID = MOL; e.g Canada = 07 ), another one is UGR ( User Grouping
).
Organization Structure

PA20/30 IT 0001 ( Org. Assignement)


Enterprise Structure:
the top subscreen in IT0001
- co code
- pers area
- cost center
- pers subarea
- Bus. area

Note: Table view V_001P_All to view all the grouping for PA and P. Subarea

Personnel structure:
Employee group
Employee subgroup
Payroll area
Contract

Note: Table view V_503_All to view all the grouping for EE Group and EE Subgroup


Org. Structure:
Position
Job key
Org. Unit
Org. key

PA40 - hire a new employee
choose action type ( in this case choose Action type HR305-05)
enter Personnel area, EE group, EE subgroup ( default by SAP delivered)
Execute ( go through each IT )


Info type grouping:

PA SAP delivered 0000 -0999
Customer 9001-9099

OM Org. Management 1000 1999
Customer 9100 9199

Time Time Management 2000-2999

Recruitment 4000-4999

Note: When position has been created under OM, then you can hire a new employee
using the Position.

Table PLOGI ORGA switch used to integrate PA and OM.

Note in PA20/30 search an infotype:

If you do not know the Infotype number, you can search by IT name in field Direct
Selection

e.g enter commun* ; system returns Communication infotype





OM ( Organization Management).

TC: PPOME





Use Seacrh Term to lookup the Org, Structure:





Select Position, and then Create Account Assignment, Work Schedule, etc for the
Position.

Note: Click Details horizontal bar to hide the detail

You can then hire new employee with the updated position.

Payroll Area and Organization Key:


Use IMG below to create new Payroll area



TC: PA03 to maintain Payroll Control record for a Payroll area



Maintain Org. Key as follows:


Maintain Creation Rules:







Maintain OM Administrator:




Administrator Group
An administrator group combines all administrators who are responsible for one organizational area in
personnel administration or recruitment.
Use
The group is defined in the feature Administrator group (PINCH).
Usually Group is the Payroll area


Feature:


Feature is used to determine default value in info type ( TC: PE03 )




Feature for Payroll area ABKRS ( decision tree )




Report RPUMKG00 to activate features or use ICON Activate to activate the current
one.

Feature NUMKR to assign personnel numbers.


Define default values for Administrator ( Feature )


SPRO->PM->PA->Org. data->Org. Assignment-> Define administrator

copy an existing admin. group to a new one

SPRO->PM->PA->Org. data->Org. Assignment-> Define administrator
group

you will find feature for PINCH

select Personnel area
delete the default value**** first
define default value and otherwise value
Activate the feature

See result below:




PA40 Now when changing the employee, the PA is changed to new one in the Org.
management screen ( 0001 ).

Feature related Programs:





HR Reports Naming Convention

Document RPD*
HR reports RPL*
HR Statistics RPS*
Payroll list RPC*
Time RPT*
Payroll RPU*
Batch Input RPI*
Personnel Planning RH*

Personal Data- IMG

IMG->PM->PA->Personal Data



Time constraint consideration:

Time constraint 1 for Permanent residence



Time constraint

1 l___________________________________________l
01/01/2000 31/12/9999

2 l___________l _______ _______l


3 l____________
l____________________l
l_________________________________


When creating a new address with Perm. address; the system will delimit the old
record and create a new one with new date to 12/31/9999.

For time constraint 1, the address record cannot be date delimited.


Bank Details:

Payment method default to U ( feature ZLSCH)



Use TC: FI01/02 to maintain Bank
Links between Planned Work Time and Basic Pay


IT0007 enter either Time mgmt status or Daily work hrs to populate Monthly
work hrs


Click Icon Work Schedule to display the work schedule



IT 0007 Employment percentage and Monthly working hrs are used in creating IT
0008 (Basic Pay )



If employee works part time ( 50% ), change Capacity level to 50 or change IT 7
Percentage to 50. ( not synchronized with IT 8 ; with a warning message Please
check Basic Pay infotype (0008).

Employee Subgroup grouping for Personnel Calculation rule:

SPRO->PM->PA->Payroll data->Basic Pay->Define EE Subgroup Grouping




The EE Subgroup Grouping is from IT 8 under PS Group and Level




Remuneration Structure

Either use

Pay scale Pay scale type ( for each region)
Pay scale area (based on collective agreement)
or using compensation model:

Salary Pay grade type
Pay grade area

Feature TARIF is used to default Pay Scale data

T510 table for PS entries

Assigning PS to Personnel subareas using IMG as follows:

SPRO->PM->PA->Payroll data->Basic Pay->Check Assignment pf Pay Scale to
Enterprise Structure




Features Directory table: T549D

Feature TARIF:

TARIF: Default Pay Scale Type/Area and Planned Remuneration Type in Basic
Pay

Object

Feature

Task

With this feature you control whether the default value is determined
from T001P from the personnel area and personnel subarea, or whether the
default value is determined directly from the feature.

The return value must have the form xx/yy/z, in which xx is the pay
scale type, yy the pay scale area, and z the planned remuneration type.

If the feature returns SPACE as a value, then the value pay scale type
or pay scale area is determined by table T001P. If the value does not
equal SPACE, then this value will be taken as the pay scale type or pay
scale area.

You can either enter return both values or only one of the two values.
The missing value is determined from table T001P.

Wage Type Configuration for Basic Pay


SPRO->PM->PA->Payroll data->Basic Pay->Wage Types Enterprise

Earnings
regular
bonus
overtime
comp. premium
benefits
etc
Deduction
tax
club membership
union
pension
donation
etc

Basic Pay enter wage type



Other IT related to Pay:

SPRO->PM->PA->Payroll data->Basic Pay->Recurring Payements and Deduction

0014 Recurring
4000 Vacatrion bonus
4001 Vacation bonus
etc..

SPRO->PM->PA->Payroll data->Basic Pay->Additonal Payements

0015 Addit. payment


2010 Employee Renumeration info.
2010 overtime
2020 overtime Sunday

WT is assigned to WT group.

Two types of WT

Primary/Dialog

Mxxx ( SAP delivered ) copy to customer one
customer 0001-9999 ( using Excel spreadsheet )
Direct ( manual entry )

Indirect
TARIF connected to table T510
PRZNT T539J
SUMME T539J



Secondary/Technical

SAP delivered:
starts with / /0001 Rate ( valuation basis)
/01xx Gross cumulation
/02xx Average bases
/03xx employee deduction (EI, RCP, RRQ,..)
/04xx Result wage types: SI
/05xx Net, Adjustment, retro
/08xx Factoring/CO
/Axx Outgoing WT in retro. acc. period
/HQC e.e /HON Ontario deduction
/Znn Incoming WT from previous period

Copy WT catalog from Model WT for Basic Pay

SPRO->PM->PA->Payroll data->Basic Pay->WAge Types->Create WT catalog



After copy, the system display all the WT tables affected.




Wage Type Permissibility

SPRO->PM->PA->Payroll data->Basic Pay->Wage Types->Check wage type
catalog



check permissibility for info type

check permissibility for PS and ESG





(based on the grouping --- IMG as follows:


SPRO->PM->PA->Payroll data->Basic Pay->Wage Types->Employee Subgroups for Primary
Wage Type



Note: V_512w_d view WT Evaluation

Wage Type Characteristics

Direct valuation amount to be use to valuate the wage type, entered in IT manually

Indirect valuation

Basic Pay:

SPRO->PM->PA->Payroll data->Basic Pay->Wage Types->Check wage type
characteristics



Detail screen:



TARIF Module/Variant ( Pay scale groups and level ) (V_T510S)


Indirect evaluation module
Name of a module that valuates wage types according to certain criteria. The following descriptions of
the diverse options can be used for wage types in the following infotypes:
Basic Pay (0008)
Standard Wage Maintenance (0052)
Recurring Payments/Deductions (0014)
Additional Payments (0015)
For some modules, the type of valuation depends on the specification of the module variant.
The following indirect valuation modules are available in the standard system:
TARIF
TAROD (only for Public Sector Germany)
VERGL (only for Public Sector Germany)
DIFFR (only for Public Sector Germany)
PRZNT
SUMME
UNITS
CONST
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


PRZNT , SUMME Basic wage type valuation( V_539J)



PRZNT
Valuation according to the "basic wage type" specifications in the IMG.
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

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.


SPRO->PM->PA->Payroll data->Basic Pay->Wage Types->Define valuation of
base wage types



When you print the table view, it will show the table name:




ARBPL Module - Indirct valuation of WT for Position/WC

SPRO->PM->PA->Payroll data->Basic Pay->Wage Types->Determine indirect
valuation for Position/Work Centers


Default Wage Type for IT 0008 using feature LGMST

Hourly Wage earners:
1010 standard wage
1020-standard bonus
Salary employee:
2010 standard salary
2020-standard bonus

LGMST->
- MOLGA (country)
- PERSG (employee group )
- PERSK (employee subgroup)

PE03 to maintain Feature (READ Documentation before editing feature )

LGMST Planned Payment Specification

Object

Feature

Task

Group the control features for wage type specifications used for
recording basic pay data.

Use

Planned Payment Specification table (T539A)

SPRO->PM->PA-Payroll data->basic pay->Wage types-> revise default wage type


Procedure

The planned payment specification in table T539A for adding basic pay
records (infotype 0008) can be defined in conjunction with these control
features: company code, personnel area, personnel subarea, employee
group, employee subgroup and the subtype of the record.

The return code matrix has the following structure: XX/YYYYYYYY, which
has the following meaning:
XX maximum number of wage types per record
YYYYYYYY name of the wage type model from T539A.







Report for changes to Remuneration

Indirect valuation on IT0008 amount does not shown in PA0008

Change pay scale group to create new pay increase

Program RPU51000 to maintain PS for simple pay increase



Update table T510 for PS group/

Run RPITRF00 to generate a basic pay history for a specified period of time



Note: ensure employee are unlocked and run in batch mode



Use SM35 to execute the BDC session if there is no error
PA20 now the employee has 3 records for IT0008 ( different periods )




Pay Scale Reclassification

Update PS groups and levels in IT0008 for each employee


Run RPIPSR00 to maintain Pay Scale Reclassification

Note: PS reclassification programs start with RPIT*

RPIPSR00 batch input processing creating new record in IT 0008

Report RPLTRF00 to report Time spent in each Pay Scale Area/Type/Group/Level

Note: perform pay scale reclassification before the Payroll run for each payroll period.


Infotypes

Attributes of each infotype consists of Dialog module, structure, and a transparent
table. Fro example; attributes for IT0002 : Dialog Module (rp_0002), structure
(p0002) Table (PA0002)

Configuring Infotypes require the following tasks:

create record without from./to date
screen header
time constraint
subtype mandatory
indicator for retroactive actg

SPRO->PM_>PA->Customizing procedures->Infotypes->Infotypes




IT0001 Org. Assignment:




Note: IT0006 using T as time constraint

Time constraint table/Subtype table t591a ( View v_t591a)
e.g. subtype for IT0006




Note: PA40 create new employee using a reference employee no, all IT will be
populated with the copied employee. ( see copy infotype in the attribute )

Attribute: Retroactive accounting trigger (refer to t588g for Retroactive acctg
recognition).

If retro acctg is field dependent, maintain the fields in table T588G using SM30 to
maintain view V_T588G





Assigning Infotypes to countries

SPRO->PM_>PA->Customizing procedures->Infotypes->Assign infotypes to
countires

View: V_T582L (Infotypes - country-specific settings)

Note: Feature can also be used to define screen controls; e,g feature P0007 for IT
0007


Customizing Screen Steps

SPRO->PM_>PA->Customizing user interface->

Step 1 - find the Screen header




Step 2 - Screen Modifier



Step 3 Maintain Modifier




Step 4 - Change Screen Modification

Find Module pool for IT ( e.g. mp000700 for IT 000 7 ).




Detail:


Option: Use feature P0007 to maintain screen control as well.
Infotype Menu

See below for PA20/30 Infotype menu

























Configuring user specific Infotype Menu


SPRO->PM_>PA->Customizing procedures->Infotype Menu

























Fast Entry PA70/71



Using With Proposal to execute

This menu can be personalized for another IT ( mass update )

PA71 used for mass update for Time.IT.


IMG to setup IT for fast entry

SPRO->PM_>PA->Customizing procedures->Infotype Menu->Setup IT menu for
fast data entry


Personnel Actions (PA40)


DFINF Feature determine from where default values should be taken for Infotype
when an IT is copied.

Personnel action sis user group dependent



Setting up a new Personnel action

define IT and their sequence
define characteristics of personnel action
store action reasons
include new personnel action in HR master data menu (action menu)











IMG: SPRO->PM->PA->Customizing->Actions..



1) Determining Infogroups ( user group depending on Infogroup, can also depend the
org. structure using FEATURE IGMOD)


inside infogroup, determine sequence subtype,default values
Operations (INS, COP, MOD, DEL, etc )



the above subtype M610 is an infotype
Copy Infotyp 6 using subtype 2 ( family member )

Note: this can also be achieved by SAP delievered Dynamic action ( when you enter a
dependent, it will bring the IT 21).


2) Determining Personnel Action types






















Details of Action types:



Use F1 help to view documentation for each column

Note: Prior to 4.6, cannot have more than one action for one day. Now, IT302 will be
used to store all actions under Additional Actions ( this will be shown under IT 0000 )

Update infotype 0302 when executing an action
The indicator U0302 defines whether the personnel action type is stored in the Additional Actions
infotype (0302).
Use
If you set the indicator U0302, the personnel action type is stored in the Additional Actions
infotype (0302).
If you want to automatically log all personnel action types which are executed for an employee,
set the indicator U0302 for all personnel action types. All personnel action types which are
executed for the employee and the related reasons are then stored in the Additional Actions
infotype (0302) for the specified key date.
If you do not set the indicator U0302, the personnel action type is not stored in the Additional
Actions infotype (0302).


Reasons for Action:

IMG: SPRO->PM->PA->Customizing->Actions->Create reasons for personnel
actions

























Action Menu

IMG: SPRO->PM->PA->Customizing->Actions-> Change Actions Menu



Dynamic Actions

Dynamic action triggers:
maintain another infotype record
send an email through SAPoffice

Table: t588z
View: v_t588z

e,g, infotype 0002




Note: Use F1 help for each column for detailed documentation

Note: step M send mail using function called M0001

e.g. Send email when payroll admin has been changed in IT0000

SACHA 06 0 *-SEND MAILS AFTER CHANGING
P0001-SACHA ---------*
SACHA 06 1 P PSPAR-TCLAS='A'
SACHA 06 2 M M0001

Also, you need to maintain Feature M0001

standard mail text template MAIL_FOR_I00001_A or B (Text id PAMA)

Call routine:

e,g,

0001 06 95 DEFAULT_NICAT1(RPUACTG1)

calling form Default_nicat1 in program RPUACTG1:

FORM default_nicat1. "#EC CALLED
*
DATA: l_p0002 LIKE p0000 OCCURS 0 WITH HEADER LINE.
*
* Called from IT0001 only
*
CHECK pspar-infty = '0001'.
*
* IT0002 must have been filled.
*
* Get P0002 that has just been created
*
PERFORM fill_infotype_table(sapfp50p) TABLES l_p0002
USING 'A'
pspar-pernr
'0002'
space
hr_low_date
hr_high_date
nop.
*
CHECK NOT l_p0002[] IS INITIAL.
*
* Call the standard routine...
*
PERFORM default_nicat.
*
ENDFORM. "default_nicat1



Fast entry of Actions


IMG: SPRO->PM->PA->Customizing user interfaces->Fast Entry of actions

TC: PA42 Fast Entry


PE01 Schema
e.g TM01