HR305 Course Notes

5/21/2018 HR305 Course Notes

1/60

HR305 Course Notes

Instructor: Carloine Chapeauman

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

User Menu


2/60

TC: SPRO_ADMINis 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.


3/60

Generate Project IMG after selection of IMG items

Display your Project IMG


4/60

User profile:

There are two important user parameters required for HR/PAY processing; MOLGA (

Country codePID = MOL; e.g Canada = 07 ), another one is UGR ( User Grouping

).Organization Structure

PA20/30IT 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


5/60

Org. Structure:

Position

Job key

Org. UnitOrg. 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 -0999Customer 9001-9099

OM Org. Management 10001999

Customer 91009199

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 PLOGIORGA switch used to integrate PA and OM.

Note in PA20/30search 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


6/60

OM ( Organization Management).

TC: PPOME

Use Seacrh Termto lookup the Org, Structure:


7/60

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.


8/60

Payroll Area and Organization Key:

Use IMG below to create new Payroll area


9/60

TC: PA03to maintain Payroll Control record for a Payroll area

Maintain Org. Key as follows:


10/60

Maintain Creation Rules:


11/60

Maintain OM Administrator:

Administrator Group

An administrator group combines all administrators who are responsible for one organizational area inpersonnel administration or recruitment.

Use

The group is defined in the feature Administrator group (PINCH).

Usually Group is the Payroll area


12/60

Feature:

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

Feature for Payroll areaABKRS ( decision tree )


13/60

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 administratorgroup

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:


14/60

PA40Now when changing the employee, the PA is changed to new one in the Org.

management screen ( 0001 ).

Feature related Programs:


15/60

HR ReportsNaming Convention

Document RPD*

HR reports RPL*

HR Statistics RPS*

Payroll list RPC*

Time RPT*

Payroll RPU*

Batch Input RPI*

Personnel Planning RH*


16/60

Personal Data- IMG

IMG->PM->PA->Personal Data

Time constraint consideration:

Time constraint 1 for Permanent residence


17/60

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 methoddefault to U ( featureZLSCH)


18/60

Use TC: FI01/02 to maintain Bank


19/60

Links between Planned Work Time and Basic Pay

IT0007enter either Time mgmt status or Daily work hrs to populate Monthly

work hrs

Click Icon Work Schedule to display the work schedule


20/60

IT 0007 Employment percentage and Monthly working hrs are used in creatingIT

0008 (Basic Pay )


21/60

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


22/60

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

T510table 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


23/60

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 determinedfrom 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.


24/60

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 membershipunion

pension

donation

etc

Basic Payenter wage type

Other IT related to Pay:

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


25/60

0014Recurring

4000Vacatrion bonus

4001 Vacation bonus

etc..

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

0015Addit. payment

2010Employee Renumeration info.

2010overtime

2020overtime 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 /HONOntario 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


26/60

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


27/60

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


28/60

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


29/60

SPRO->PM->PA->Payrol l data->Basic Pay->Wage Types-> Employee Subgroups for Pr imary

Wage Type

Note: V_512w_dview WT Evaluation

Wage Type Characteristics

Direct valuationamount 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 typecharacteristics


30/60

Detail screen:

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


31/60

Indirect evaluation module

Name of a module that valuates wage types according to certain criteria. The following descriptions ofthe 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 IMGstep:

Module variant 'A'

Country grouping derived from the employee's personnel areaPay scale type from infotype 0008/0052Pay scale area from infotype 0008/0052Pay scale indicator derived from the employee subgroupPay scale group from infotype 0008/0052Pay scale level from infotype 0008/0052Wage type = SPACE

Module variant 'B'

like module variant 'A' except:Wage type = wage type to be valuated indirectly


32/60

Module variant 'C'

like module variant 'A' except:Pay scale level = SPACEWage type = wage type to be valuated indirectly

Module variant 'D'

like modul variant 'A' except:Pay scale group = SPACEPay scale level = SPACEWage type = wage type to be valuated indirectly

PRZNT , SUMMEBasic 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'


33/60

The basic pay is determined from the total of all basic wage type amounts entered in infotype0008 according to the specifications in the "basic wage type valuation" step irrespective ofwhich infotype is being valuated. Wage types in the Wage Maintenance infotype (0052) arethen 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 payby 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 theinfotype currently being valuated according to the specifications in the "basic wage typevaluation" step. The wage types in the Wage Maintenance infotype (0052) are then valuatedusing 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 payby 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 wagetype 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


34/60

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


35/60

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 )

LGMSTPlanned 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


36/60

YYYYYYYY name of the wage type model from T539A.


37/60

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


38/60

Note: ensure employee are unlocked and run in batch mode

Use SM35to execute the BDC session if there is no error


39/60

PA20now 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*

RPIPSR00batch input processing creating new record in IT 0008

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

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


40/60

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

IT0001Org. Assignment:


41/60

Note: IT0006 using T as time constraint

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


42/60

Note: PA40create 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


43/60

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


44/60

Step 2 - Screen Modifier


45/60

Step 3Maintain Modifier

Step 4 - Change Screen Modification

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


46/60

Detail:

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


47/60

Infotype Menu

See below for PA20/30 Infotype menu


48/60

Configuring user specific Infotype Menu

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


49/60

Fast EntryPA70/71

Using With Proposal to execute

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

PA71used 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


50/60

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)


51/60

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

1) Determining Infogroups ( user group depending on Infogroup, can also depend the

org. structure using FEATURE IGMOD)


52/60

inside infogroup, determine sequence subtype,default values

Operations (INS, COP, MOD, DEL, etc )

the above subtype M610 is an infotype


53/60

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


54/60

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 U0302defines whether the personnel action type is stored in theAdditional Actionsinfotype (0302).

Use

If you set the indicator U0302, the personnel action type is stored in theAdditional Actionsinfotype (0302).

If you want to automatically log allpersonnel action types which are executed for an employee,set the indicator U0302for all personnel action types. All personnel action types which areexecuted for the employee and the related reasons are then stored in the Additional Actionsinfotype (0302) for the specified key date.

If you do not set the indicator U0302, the personnel action type is not stored in theAdditionalActionsinfotype (0302).


55/60

Reasons for Action:

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

actions


56/60

Action Menu

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


57/60

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 Msend 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 templateMAIL_FOR_I00001_A or B (Text idPAMA)


58/60

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'spacehr_low_datehr_high_datenop.

*CHECK NOT l_p0002[] IS INITIAL.

** Call the standard routine...*

PERFORM default_nicat.*ENDFORM. "default_nicat1


59/60

Fast entry of Actions

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

TC: PA42Fast Entry

PE01Schema

e.g TM01


60/60

HR305 Course Notes

Documents

Transcript of HR305 Course Notes