Basic Configuration for SAP HCM Since 2012

EHP5 for SAP ERP 6.0

January 2012

English

HCM Base Global Personnel Administration (F02)

SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany

Building Block Configuration Guide

SAP Best Practices for HCM EhP5 Package F02- Personnel Administration: Configuration Guide

SAP AG Page 2 of 50

Copyright

2011 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.

Oracle and Java are registered trademarks of Oracle.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, World Wide Web Consortium, Massachusetts Institute of Technology.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, SAP HANA, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. Business Objects is an SAP company.

Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase, Inc. Sybase is an SAP company.

All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.


SAP AG Page 3 of 50

Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Typographic Conventions

Type Style Description

Example text Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths and options.

Cross-references to other documentation.

Example

text Emphasized words or phrases in body text, titles of graphics and tables.

EXAMPLE TEXT

Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE.

Example text Screen output. This includes file and directory names and their paths, messages, source code, names of variables and parameters as well as names of installation, upgrade and database tools.

EXAMPLE TEXT Keys on the keyboard, for example, function keys (such as F2) or the ENTER key.

Example

text Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.

Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.

Example text This text denotes entries that are SAP standard settings. These entries are not configured by the SAP Best Practices for HCM EhP5 package and are included for informational purposes.


SAP AG Page 4 of 50

Contents 1 Purpose .................................................................................................................................... 7

2 Preparation ............................................................................................................................... 7

3 Basic Settings ........................................................................................................................... 8

3.1 Delete Standard Number Range Interval 02 .................................................................. 8

3.2 Maintain Number Range Intervals for Personnel Numbers ........................................... 8

3.3 NUMKR Feature: Maintain Number Ranges .................................................................. 9

4 Personnel Administration ......................................................................................................... 9

5 Personal Data ........................................................................................................................... 9

5.1 Personal Data ................................................................................................................ 9

5.1.1 Forms of Address ....................................................................................................... 9

5.1.2 Create Name Affixes ................................................................................................ 10

5.1.3 Maintain Titles .......................................................................................................... 11

5.1.4 Create Marital Status ............................................................................................... 11

5.2 Family ........................................................................................................................... 12

5.2.1 Define Possible Family Members ............................................................................ 12

5.3 Addresses .................................................................................................................... 13

5.3.1 Create Address Types ............................................................................................. 13

5.4 Bank Details ................................................................................................................. 14

5.4.1 Create Bank Connection Types ............................................................................... 14

5.4.2 Define Payment Methods ........................................................................................ 14

6 Organizational Data ................................................................................................................ 15

6.1 Set up Organizational Assignment ............................................................................... 15

6.1.1 Define Employee Attributes ..................................................................................... 15

6.1.2 Set Up Organizational Key ...................................................................................... 16

6.1.3 Check Default Payroll Area ...................................................................................... 17

7 Create Wage Type Catalog .................................................................................................... 18

7.1 Wage Types for Basic Pay ........................................................................................... 18

7.2 Employee Subgroups for Primary Wage Type............................................................. 18

7.3 Personnel Subareas for Primary Wage Type .............................................................. 19

7.4 Check Wage Type Permissibility for Each PS and ESG ............................................. 20

7.5 Remove ASAL from Wage Type .................................................................................. 20

8 Payroll Data ............................................................................................................................ 21

8.1 Basic Pay ..................................................................................................................... 21

8.1.1 Define EE Subgroup Grouping for PCR and Coll.Agrmt.Prov. ................................ 21

8.1.2 Pay Scale Conversion for Basic Pay ....................................................................... 22

8.1.3 Define Reason for Change ...................................................................................... 23

8.1.4 Pay Scale Types and Pay Scale Areas ................................................................... 23

8.1.4.1 Check Pay Scale Type ........................................................................................ 23

8.1.4.2 Check Pay Scale Area ......................................................................................... 24

8.1.5 Determine Default for Pay Scale Data ..................................................................... 24

8.1.6 Change Default Salary Sum Wage Type ................................................................. 25

8.1.7 Set up Payroll Period for Collective Agreement Provision....................................... 25

8.1.8 Revise Pay Scale Groups and Levels ..................................................................... 26


SAP AG Page 5 of 50

8.1.9 Specify Working Hours Fixed by Collective Agreement .......................................... 27

8.1.10 Enterprise Structure for Wage Type Model ............................................................. 27

8.1.11 Revise Default Wage Types .................................................................................... 28

8.1.12 Assign Wage Types Used for Determining Total Salary ......................................... 28

9 Evaluation Basis ..................................................................................................................... 29

9.1 Date Specifications ...................................................................................................... 29

9.1.1 Define Date Types ................................................................................................... 29

9.1.2 Determine Default Date Specification ...................................................................... 29

10 Communication ................................................................................................................... 30

11 Customizing Procedures ..................................................................................................... 31

11.1 Infotype Menus ............................................................................................................. 31

11.1.1 User Group Dependency on Menus and Info Groups ............................................. 31

11.1.2 Infotype Menu .......................................................................................................... 31

11.2 Determine Choice of Infotype Menus ........................................................................... 32

11.3 Actions .......................................................................................................................... 33

11.3.1 Define Info Groups ................................................................................................... 33

11.3.1.1 User Group Dependency ................................................................................ 33

11.3.2 Define Info Group ..................................................................................................... 34

11.3.2.1 Hiring Action .................................................................................................... 34

11.3.2.2 External Hire Action ........................................................................................ 34

11.3.2.3 Transfer Action ................................................................................................ 35

11.3.2.4 Position Change (Same OU) Action ............................................................... 35

11.3.2.5 Termination Action .......................................................................................... 35

11.3.2.6 Rehire Action ................................................................................................... 35

11.3.2.7 Retirement Action ............................................................................................ 36

11.3.2.8 Leave Of Absence Action ................................................................................ 36

11.3.2.9 Return from Leave of Absence Action ............................................................ 36

11.3.2.10 Initial Hire (Data Migration) Action .................................................................. 37

11.3.2.11 Position Assignment (Data Migration) Action .................................................. 37

11.3.3 Set Up Personnel Actions ........................................................................................ 37

11.3.4 Set Up Priority List for Personnel Action Types ....................................................... 39

11.3.5 Update Infotype 0302 when Executing an Action .................................................... 39

11.3.6 Create Reasons for Personnel Actions.................................................................... 40

11.3.7 User Group Dependency on Menus and Info Groups ............................................. 42

11.3.8 Action Menu ............................................................................................................. 42

11.4 Dynamic Actions .......................................................................................................... 43

12 Customizing User Interfaces............................................................................................... 43

13 Work Schedules .................................................................................................................. 44

13.1 Groupings for the Personnel Subareas ........................................................................ 44

13.2 Group Personnel Subareas for the Daily Work Schedule ............................................ 44

13.3 Define Work Break Schedules ..................................................................................... 45

13.4 Define Daily Work Schedules....................................................................................... 45

13.5 Period Work Schedules ................................................................................................ 46

13.6 Employee Subgroup Groupings (for Work Schedules) ................................................ 46


SAP AG Page 6 of 50

13.7 Assign Personnel Subarea to Public Holiday Calendar ............................................... 47

13.8 Work Schedule Rules ................................................................................................... 48

13.9 Defaults for the Work Schedule ................................................................................... 49

13.10 Set Default Value for Time Management Status ......................................................... 49

14 Generate Features .............................................................................................................. 49


SAP AG Page 7 of 50

1 Purpose This configuration guide provides the information you need to configure this building block manually.

2 Preparation Before you start installing this building block, you must install the prerequisite building blocks. For more information, see the Building Block Prerequisite Matrix for HCM. A link to this matrix (an Excel file) is provided on the DVD/Web site for the solution at the following locations:

Content Library

Site Map


SAP AG Page 8 of 50

3 Basic Settings

3.1 Delete Standard Number Range Interval 02

Use In this activity, you delete the number range interval 02.

Procedure 1. Access the activity using one of the following navigation options:

IMG Path Personnel Management Personnel Administration Basic Settings

Maintain Number Range Intervals for Personnel Numbers

Transaction Code

PA04

2. On the Personnel Administration Number Ranges screen, choose the Change Intervals pushbutton.

3. Select number range interval 02 as this is in conflict with 10.

4. Choose the Delete Interval pushbutton.

5. Save your entries.

3.2 Maintain Number Range Intervals for Personnel Numbers

Use Both external and internal number ranges have been configured in the SAP Best Practices for HCM EhP5 package. Personnel number assignment is controlled by the NUMKR feature, which uses the standard number ranges.



Maintain number range intervals for personnel numbers

Transaction Code

PA04

2. On the Personnel Administration Number Ranges screen, choose the Change Intervals pushbutton.

3. Choose the Insert Interval pushbutton and enter the following values:

No. From Number To Number Current Number External

01 00000001 00999999 Select

10 01000000 99999999 0



SAP AG Page 9 of 50

3.3 NUMKR Feature: Maintain Number Ranges

Use Number range 01 is set as the default for personnel numbers. This feature may require process legacy data or the sample data shipped with the SAP Best Practices for HCM EhP5 package to be modified.



Determine Defaults for Number Ranges

Transaction Code

PE03

2. On the Process feature NUMKR: decision tree screen, make the following entries::

NUMKR:

D MOLGA

99 &NUMKR=10,

* &NUMKR=01,


4. Choose Activate.

4 Personnel Administration This SAP Best Practices for HCM EhP5 package delivers a standard configuration for Personnel Management based on the most commonly used settings. This provides a realistic business model to enable customers to begin extending Customizing to meet their specific needs.

5 Personal Data

5.1 Personal Data

The following areas are maintained in the IMG under the heading Personnel Administration: Forms of address, name affixes, marital status, address types, family/related types, and so on.

5.1.1 Forms of Address

Use The most common forms of address are shipped with this SAP Best Practices for HCM EhP5 package.

The standard values shipped in an SAP system are shown in this table. The gender has also been included in the forms of address to allow for the default value for infotype 0002.


SAP AG Page 10 of 50

FOA Key Title Long Text Gender

1 Mr Mr 1

2 Mrs Mrs 2

3 Miss Miss 2

4 Ms Ms 2

5 Dr. Dr. 1

Procedure 1. To add new values, access the activity using one of the following navigation options:

IMG Path Personnel Management Personnel Administration Personal Data

Personal Data Create Forms of Address

Transaction Code

SPRO

2. On the Change View "Title Keys": Overview screen, choose the New entries pushbutton and enter the new values.

FOA Key Title Long Text Gender

5 Dr Dr 1


5.1.2 Create Name Affixes

Use Within this area, configuration has been completed for the most common Academic Titles. Below is just a sample of the standard SAP name affixes.

The standard values shipped in an SAP system are shown in this table.

Academic Titles Name Affix Output Text

S B.A. B.A.

S B.Sc. B.Sc.

S CPA CPA

S D.D. D.D.

S D.D.S. D.D.S.

S D.P.S. D.P.S.

S ENG. Eng.

S ING. Ing.

S M.D. M.D.



Academic Titles Name Affix Output Text

S MBA MBA

S P.ENG P.Eng.

S PhD PhD

S RA RA

S RI RI

Procedure 1. To add additional entries, access the activity using one of the following navigation options:


Personal Data Create Name Affixes

Transaction Code

SPRO

2. On the Change View "Name affixes": Overview screen, choose the New entries pushbutton and enter the new values.


5.1.3 Maintain Titles

Use The most commonly used titles have been configured for delivery with SAP. These titles can be deleted as only 2 titles are used with this SAP Best Practices for HCM EhP5 package.



Personal Data Maintain Titles

Transaction Code

SPRO

2. On the Change View "Name Affix": Overview screen, choose the New entries pushbutton and enter the following values:

Name Affix Output Text

Dr. Doctor

Prof. Professor


5.1.4 Create Marital Status

Use The most commonly used marital statuses have been configured for delivery with this SAP Best Practices for HCM EhP5 package.



The standard values shipped in an SAP system are shown in this table.

Mar.Stat Marital Status

0 Single

1 Marr.

2 Wid.

3 Div.

5 Sep.

6 Unknown

9 RegCou

Procedure 1. To add new entries, access the activity using one of the following navigation options:


Personal Data Create Marital Status

Transaction Code

SPRO

2. On the Change View "Marital Status Designations": Overview screen, choose the New entries pushbutton and enter the new values.


5.2 Family

5.2.1 Define Possible Family Members

Use SAP provides many different categories for the Family/Related Persons infotype 0021. Only those entries listed below are used in the SAP Best Practices for HCM EhP5 package. All other entries can be deleted.

SubType Name Time Constraint Obj. ID

1 Spouse 2

2 Child 2 Select

3 Legal guardian 2

4 Testator 2

5 Guardian 2 Select

6 Stepchild 2 Select

7 Emergency contact 2

8 Related person 2 Select

10 Divorced spouse 2 Select



SubType Name Time Constraint Obj. ID

11 Father 2

12 Mother 2

13 Domestic partner 2

14 Child of domestic partner 2 Select

15 Registered partner 2



Family Define Possible Family Members

Transaction Code

SPRO

2. On the Change View "Subtype Characteristics": Overview screen, choose the New entries pushbutton and enter the new values:


Testator refers to the individual who prepared the employee's will.

Emergency contact if this is used for other countries, we recommend using this subtype in IT0006 Addresses, where the telephone number field is common to all countries.

5.3 Addresses

5.3.1 Create Address Types

Use Although many address types are provided and can be assigned to employees, each employee must have address type 1 Permanent Residence, which is included in the HIRE action. If additional address types need to be defined for an employee at the time of hire, the HIRE action can be modified to include them. Alternatively, additional address information can be created at any time using the Maintain Master Data functionality.

The standard values shipped in an SAP system are shown in this table and are used by the SAP Best Practices for HCM EhP5 package. All other values can be deleted.

SubType Description Time Constraint

1 Permanent Residence 1

2 Temporary Residence 3

3 Home Address 2

4 Emergency Address 2

5 Mailing Address 2





Addresses Create Address Types

Transaction Code

SPRO

2. On the Change View "Subtype Characteristics": Overview screen, choose the New entries pushbutton and enter the new values.


5.4 Bank Details

5.4.1 Create Bank Connection Types

Use In this SAP Best Practices for HCM EhP5 package, the bank connection types shipped with the standard system have not been modified.

The standard values shipped in an SAP system are shown in this table and are used in the SAP Best Practices for HCM EhP5 package. All other values can be deleted.

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

Procedure 1. To add entries, access the activity using one of the following navigation options:


Bank Details Create Bank Connection Types

Transaction Code

SPRO

2. On the Change View "Subtype Characteristics": Overview screen, choose the New entries pushbutton and enter the new values.


5.4.2 Define Payment Methods

Use



The standard entries shipped for payment methods are used. Follow the procedure below to make payment method T available as the default method:



Bank Details Define Payment Method

Transaction Code

FBZP

2. On the Customizing: Maintain Payment Program screen, choose the Pmnt methods in company codes pushbutton.

3. On the Change View "Maintenance of Company Code Data for a Payment Method": Overview screen, select payment method T under company code RECO

4. On the Change View "Maintenance of Company Code Data for a Payment Method" screen, choose the Pmnt methods in ctry pushbutton.

5. On the Change View "Payment Method/Country": Details screen, select Allowed for personnel payments.


6 Organizational Data

6.1 Set up Organizational Assignment

6.1.1 Define Employee Attributes

Use In this activity, you define the employee attributes.


IMG Path Personnel Management Personnel Administration Organizational

Data Organizational Assignment Define employee attributes

Transaction Code

SPRO

2. On the 'Change View "Employee Subgroup Grouping f. Activities/Employment/Train" screen, the system displays the following values:

EEGrp

Name of Employee Grp

Employee Subgroup

Name of EE Subgroup

Activity Status

Employment Status

Training Status

1 Employee Y0 Non-

Exempt/Hourly 1 1 2

1 Employee Y1 Exempt/Salarie 1 2 2



EEGrp

Name of Employee Grp

Employee Subgroup

Name of EE Subgroup

Activity Status

Employment Status

Training Status

d

1 Employee Y3 Executives 1 1 2

1 Employee YE Students 1 1 1

1 Employee YF Temps 1 1 2

1 Employee YG Interns 1 1 1

1 Employee YJ Trainees 1 1 1

2 Retiree/Pensioner

Y7 Retirees 1 2 2

8 Expatriate Y0 Non-

Exempt/Hourly 1 1 2

8 Expatriate Y1 Exempt/Salarie

d 1 2 2

8 Expatriate Y3 Executives 1 2 2

9 External Y2 Contractors 9 9 9

9 External YF Temps 9 9 9

9 External YH Agency

Workers 9 9 9

A Part-time Y0 Non-

Exempt/Hourly 1 1 2

A Part-time Y1 Exempt/Salaried

1 2 2

A Part-time Y3 Executives 1 2 2

A Part-time YE Students 1 2 1

A Part-time YF Temps 1 2 2

A Part-time YG Interns 2 9 9

A Part-time YJ Trainees 1 2 1

U Inpatriate Y1 Exempt/Salarie

d 1 2 2

U Inpatriate Y3 Executives 1 2 2

6.1.2 Set Up Organizational Key

Use You can use all elements of the organizational structure to define the organizational key. The organizational key comprises a 14-character field. Each customer determines the structure of the key. The organizational key can be used for authorization checks.

In the SAP Best Practices for HCM EhP5 package, the variable key has been set to 01.





Data Organizational Assignment Set Up Organizational Key

Transaction Code

SPRO

2. On the Choose Activity screen, select the Organizational Key: Maintain feature VDSKI activity and choose the Choose pushbutton. On the Process feature VDSK1: decision tree" screen, the system displays the following values:

VDSK1:

D MOLGA

** &VDSK1=01,

6.1.3 Check Default Payroll Area

Use Once these payroll areas have been defined, you can specify default values for the payroll accounting area for your employees. When an employee's organizational assignment is maintained, the correct payroll area is proposed as default in the Organizational Assignment (0001) Infotype.

The ABKRS feature is used to define these defaults. This SAP Best Practices for HCM EhP5 package is delivered with the payroll default set to 99 for all employees:

1. Access the activity using one of the following navigation options:


Data Organizational Assignment Check Default Payroll Area

Transaction Code

SPRO

2. On the Process feature ABKRS: decision tree screen, the system displays the following values:

TCLAS Transaction Class for Data Retention.

3. Choose TCLAS and click Delete Node/Sub-tree. TCLAS decision field is removed from feature.

4. Make the following entries:

ABKRS:

NOTE: This is a change to standard configuration.

D MOLGA

99 &ABKRS=99,

** &ABKRS=99,


6. Choose Activate.



7 Create Wage Type Catalog

7.1 Wage Types for Basic Pay

Use Wage types for the Basic Pay infotype (IT0008) are provided to support both hourly and salaried employees as well as pensioners in this SAP Best Practices for HCM EhP5 package. The following wage types can be created by copying a delivered model wage type:


IMG Path Personnel Management Personnel Administration Payroll Data

Basic Pay Wage Types Create Wage Type Catalog

Transaction Code

SPRO

2. In the Wage Type Maintenance dialog box, choose Copy. Make sure the Country Grouping field contains the value 99 and the Wage Type Group field the value 0008.

3. Select the wage types to be copied based on the following entries:

Original Wage Type

Wage Type Long Text

Text Several Languages Available

Custom Wage Type

Wage Type Long Text

Text

M000 Hourly Wage

HrlyRate Select 1000 Hourly Rate

HrlyRate

M020 Monthly Salary

MoSalary Select 1020 Monthly Salary

MoSalary


7.2 Employee Subgroups for Primary Wage Type

Use You can have wage types assigned based on the employee definition. These are either for employee types that are not paid through payroll or who generally do not require certain wage types.



Basic Pay Wage Types Employee Subgroups for Primary Wage Type

Transaction Code

SPRO

2. On the Change View "Employee Subgroup Grouping for Primary Wage Type": Overview screen, make the following entries:

EG Employee Group ESG Employee Subgroup ESG Grouping



EG Employee Group ESG Employee Subgroup ESG Grouping

1 Employee Y0 Non-Exempt/Hourly 1

1 Employee Y1 Exempt/Salaried 3

1 Employee Y3 Executives 3

1 Employee YJ Trainees 3

1 Employee YE Students 3

1 Employee YG Interns 3

1 Employee YF Temps 3

2 Retiree / Pensioner Y7 Retirees 3

8 Expatriate Y0 Non-Exempt/Hourly 1

8 Expatriate Y1 Exempt/Salaried 3

8 Expatriate Y3 Executive 3

9 External Y2 Contractors

9 External YH Agency Workers

9 External YF Temps

A Part-time Y0 Non-exempt/Hourly 1

A Part-time Y1 Exempt/Salaried 3

A Part-time Y3 Executives 3

A Part-time YE Students 3

A Part-time YF Temps 3

A Part-time YG Interns 3

A Part-time YJ Trainees 3

U Inpatriate Y1 Exempt/Salaried 3

U Inpatriate Y3 Executives 3


7.3 Personnel Subareas for Primary Wage Type

Use In this section, a group 1 for primary wage types has been defined for all personnel subareas.



Basic Pay Wage Types Personnel Subareas for Primary Wage Type

Transaction SPRO



Code

2. On the Change View "Employee Subgroup Grouping for Primary Wage Type": Overview screen, make the following entries:

Personnel Area Personnel Subarea PS Grouping

9900 Global Personnel Area 1001 Administration 1

1002 Human Resources 1

1003 Finance 1

1004 Marketing 1

1005 Sales 1

1006 Operations 1

1007 Manufacturing 1


7.4 Check Wage Type Permissibility for Each PS and ESG

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



Basic Pay Wage Types Check Wage Type Catalog Define wage type permissibility for each PS and ESG

Transaction Code

SPRO

2. On the Country Grouping screen, in the Country field, select USA and choose Enter.

3. On the Change View "Permissibility of Wage Types": Overview screen, select the following entries:

WT Wage Type Long Text Start Date End Date

1000 Base Rate / Hourly Wage 01/01/1900 12/31/9999

1020 Monthly Salary 01/01/1900 12/31/9999

4. On the Change View "Permissibility of Wage Types": Details screen, set the value 1 for all personnel subareas.


7.5 Remove ASAL from Wage Type 1. Access the activity using one of the following navigation options:

Transaction SM31



Code

2. On the Maintain Table views: Initial Screen, in the Table/View field, enter V_511_B and

choose Maintain.

3. In the Country Grouping field, enter 99 and press Enter.

4. In the Change View "Permissibility of Wage Types" Overview screen, change all the EE Subgroup grouping and Personnel subarea values from 1 to blank.


8 Payroll Data

8.1 Basic Pay

8.1.1 Define EE Subgroup Grouping for PCR and Coll.Agrmt.Prov.

Use The employee subgroup grouping for the personnel calculation rule is required in Payroll Accounting. The collective agreement provision grouping is used to group employees with the same pay scale requirements.

The meanings of the grouping for the PCR are fixed and may not be changed. The CAP grouping values are not subject to any restrictions; however, the values defined here are used in further configuration steps. If the CAP values need to be changed, make sure that the configuration for Pay Scale Groups, Period Assignment for CAP and Hourly Rate with multiple decimals is reviewed.



Basic Pay Define EE Subgroup Grouping for PCR and Coll.Agrmt.Prov.

Transaction Code

SPRO

2. On the Determine Work Area: Entry screen, 99 defaults for Country Grouping (based on the MOL setting in User Parameters).

3. On the Change View "EE Subgroup Grouping for PCR and Coll.Agrmt.Prov ": Overview screen, choose the New Entries pushbutton and enter the following values:

EG Employee Group ESG Employee Subgroup PCR CAP

1 Employee Y0 Non-Exempt/Hourly 1 1

1 Employee Y1 Exempt/Salaried 3 3

1 Employee Y3 Executives 3 3

1 Employee YE Students 3 3

1 Employee YF Temps 3 3



EG Employee Group ESG Employee Subgroup PCR CAP

1 Employee YG Interns 3 3

1 Employee YJ Trainees 3 3

2 Retiree/Pensioner Y7 Retirees 3 3

8 Expatriate Y0 Non-Exempt/Hourly 1 1

8 Expatriate Y1 Exempt/Salaried 3 3

8 Expatriate Y3 Executives 3 3

9 External Y2 Contractors

9 External YF Temps

9 External YH Agency Workers

A Part-time Y0 Non-Exempt/Hourly 1 1

A Part-time Y1 Exempt/Salaried 3 3

A Part-time Y3 Executives 3 3

A Part-time YE Students 3 3

A Part-time YF Temps 3 3

A Part-time YG Interns 3 3

A Part-time YJ Trainees 3 3

U Inpatriate Y1 Exempt/Salaried 3 3


8.1.2 Pay Scale Conversion for Basic Pay

Use In this activity, you create the pay scale conversion for basic pay.



Basic Pay Pay Scale Conversion for Basic Pay

Transaction Code

SPRO

2. On the Change View "Employee Subgroup for PersCalcRule/CollAgreemProvision": Overview screen, make the following entries:

ES Grouping for PCR SGTx Long Text ESG for CAP Reaction

1 STD Hourly 1

1 STD Hourly 2

1 STD Hourly 4

1 STD Hourly 5



8.1.3 Define Reason for Change

Use Additional reason codes have been defined in this SAP Best Practices for HCM EhP5 package to accurately track reasons for changes in employee pay. The following basic pay reason codes are shipped with this SAP Best Practices for HCM EhP5 package:



Basic Pay Define reason for change

Transaction Code

SPRO

2. On the Change View "Reason for Change ": Overview screen, choose the New Entries pushbutton and enter the following values:

Reason Description

91 Change in Pay


8.1.4 Pay Scale Types and Pay Scale Areas The combination of pay scale type and area allows the customer to limit the selection of groups, grades, steps, and so on, that are available when the Basic Pay infotype is being maintained.

8.1.4.1 Check Pay Scale Type

Use Pay scale types are defined in this SAP Best Practices for HCM EhP5 package to support a variety of pay structure scenarios. Salaried employees are validated based on exempt versus non-exempt pay ranges, while hourly employees may be assigned to a union or standard pay scale structure. For companies that choose not to validate pay in any fashion, a non-pay scale type can be created to provide no validation of basic pay.



Basic Pay Check Pay Scale Type

Transaction Code

SPRO

2. On the Change View "Pay Scale Type ": Overview screen, choose the New Entries pushbutton and enter the following values:

Type Description

10 Salaried Pay Type

20 Hourly Pay Type




8.1.4.2 Check Pay Scale Area

Use Sample pay scale areas are delivered with this SAP Best Practices for HCM EhP5 package to show the most common use of this field, which is to group employees with common pay structures together. Customers need to determine how to best develop a structure of codes to meet their specific requirements.



Basic Pay Check Pay Scale Area

Transaction Code

SPRO

2. On the Change View "Pay Scale Area": Overview screen, choose the New Entries pushbutton and enter the following values:

Area Description

10 Global Pay Area


8.1.5 Determine Default for Pay Scale Data

Use In this SAP Best Practices for HCM EhP5 package, the TARIF feature is used to provide the default pay scale data based on the employee group and employee subgroup. This allows pay scale data to default based on a collective agreement or employee organizational assignment. Customers are recommended to refer to this feature as a guide when developing the correct defaults for their requirements.



Basic Pay Determine default for pay scale data

Transaction Code

SPRO

2. On the "Process feature TARIF: decision tree" screen, make the following entries:

TARIF

D MOLGA

99 D PERSG

99 9 &TARIF=,

99 ** D PERSK

99 ** Y1 &TARIF=10/10,

99 ** Y0 &TARIF=20/10,

99 ** Y3 &TARIF=10/10,

99 ** YJ &TARIF=10/10,



99 ** YG &TARIF=10/10,

99 ** YF &TARIF=10/10,

99 ** Y2 &TARIF=,

99 ** YH &TARIF=,

99 ** YE &TARIF=10/10,

99 ** Y7 &TARIF=10/10,


4. Choose Activate.

8.1.6 Change Default Salary Sum Wage Type

Use In this activity, you specify the wage type for determining the salary total.


IMG Path

Personnel Management Personnel Administration Payroll Data

Basic Pay Check Total Salary Against Salary Range Change Default Salary Sum Wage Type

Transaction Code

SPRO

2. On the Process feature ANSAL: decision tree screen, make the following entries:

ANSAL

D SUBTY

**** D MOLGA

**** 99 &ANSAL=ASAL,

8.1.7 Set up Payroll Period for Collective Agreement Provision

Use The pay period parameter is set based on the pay scale type, area and employee subgroup grouping for CAP. This configuration enables the default of the correct hours worked within a pay period for the Base Pay infotype 0008 to be used.


IMG Path

Personnel Management Personnel Administration Payroll Data

Basic Pay Set Up Payroll Period for Collective Agreement Provision

Transaction Code

SPRO

2. On the Choose Activity screen, select the second task, Pay scale > Period Parameter Assignment activity and choose the Choose pushbutton. On the Change View "Pay Scale > Period Parameter Assignment": Overview screen, make the following entries:



PT Pay Scale Type

PA Pay Scale Area

Group Start Date End Date Per Pay

Per Pay Text

10 Salaried Pay Type 10

Global Pay Area 3

01/01/1900 12/31/9999 1 Monthly

20 Hourly Pay Type 10

Global Pay Area 1

01/01/1900 12/31/9999 1 Monthly


4.

8.1.8 Revise Pay Scale Groups and Levels

Use In this SAP Best Practices for HCM EhP5 package, salaried and hourly employees are evaluated directly, which means that the salary amount or hourly rate defaults based on the entries defined in this table.



Basic Pay Revise Pay Scale Groups and Levels

Transaction Code

SPRO

2. On the Determine Work Area: Entry, enter the following values and press Enter.

Country Grouping Pay Scale Type Pay Scale Area

99 10 10

3. On the Change View "Pay Scale Groups": Overview screen, enter the following values and press Enter.

Pay Scale Type

Pay Scale Area

Grouping

PS Group

Level

Wage Type

Start Date

End Date Amount

Currency

10 10 3 01 01 1020 01/01/20

02 12/31/9999

EUR

4. On the Determine Work Area: Entry screen, enter the following values and press Enter.

Country Grouping Pay Scale Type Pay Scale Area

99 20 10



5. On the Change View "Pay Scale Groups": Overview screen, enter the following values and press Enter.

Pay Scale Type

Pay Scale Area

Grouping

PS Group

Level

Wage Type

Start Date

End Date Amount

Currency

20 10 1 01 01 1000 01/01/20

02 12/31/9999

EUR

8.1.9 Specify Working Hours Fixed by Collective Agreement

Use In this activity, you assign working times to the various combinations of pay scale type and pay scale group and specify both the standard weekly working time and the standard number of working days per week as stipulated in the collective agreement.



Basic Pay Specify working hours fixed by collective agreement

Transaction Code

SPRO

2. On the Change View "Standard Working Hours": Overview screen, make the following entries:

Pay Scale Type

Pay Scale Type Text

Pay Scale Area

Pay Scale Area Text

ESG/CAP

Start Date

End Date

Hours

Days

10 Salaried Pay Type 10

Global Pay Area 3

1/01/1900

12/31/9999 40 5

20 Hourly Pay Type 10

Global Pay Area 1

01/01/1900

12/31/9999 40 5


8.1.10 Enterprise Structure for Wage Type Model

Use The LGMST feature determines which default wage types are assigned in the Basic Pay infotype (0008).



Basic Pay Wage Types Enterprise Structure for Wage Type Model



Transaction Code

SPRO

2. On the Process feature LGMST: decision tree screen, make the following entries:

LGMST:

D MOLGA

99 D PERSG

99 9 &LGMST=,

99 2 &LGMST=10/----990-,

99 U &LGMST=10/----990-,

99 1 D PERSK

99 1 Y0 &LGMST=10/----991-,

99 1 ** &LGMST=10/----990-,

99 8 Y0 &LGMST=10/----991-,

99 8 ** &LGMST=10/----990-,

99 A Y0 &LGMST=10/----991-,

99 A ** &LGMST=10/----990-


4. Choose Activate.

8.1.11 Revise Default Wage Types

Use In this activity, you revise default wage types.



Basic Pay Wage Types Revise Default Wage Types

Transaction Code

SPRO

2. On the Change View "Default Wage Types for Basic Pay": Overview screen, make the following entries:

WT Model Start Date End Date Seq. F/O WT Description

----990- 01/01/1900 12/31/9999 1 O 1020 Monthly salary

----991- 01/01/1900 12/31/9999 1 O 1000 Hourly rate


8.1.12 Assign Wage Types Used for Determining Total Salary

Use In this step, you specify which wage types are used when determining the total salary. Only wage types that have been entered in the Basic Pay infotype (0008) can contribute to determining the total salary. Wage types that are defined in the view but not entered in the Basic Pay infotype (0008) are not taken into account.

Procedure



1. Access the activity using one of the following navigation options:


Basic Pay Define Annual Salary Relevant Wage Types for Annual Salary Valuation

Transaction Code

SPRO

2. On the Change View "Base Wage Type Valuation": Overview screen, make the following entries:

Valuate Long Text No. Start Date

End Date Base WT

Wage Type Long Text

Percent

ASAL Annual Salary

4 01/01/1900 12/31/9999 1000 Hourly wage 100.00

ASAL Annual Salary

5 01/01/1900 12/31/9999 1020 Monthly salary

100.00


9 Evaluation Basis

9.1 Date Specifications

9.1.1 Define Date Types

Use Date types can be proposed as defaults for the Date Specifications infotype (0041). Dates stored in date types can be used for reporting as well as payroll, time, and benefits eligibility.


IMG Path Personnel Management Personnel Administration Evaluation

Basis Date Specifications Define date type

Transaction Code

SPRO

2. On the Change View "Date Types": Overview screen, make the following entries:

DT Date Type Text Date Indicator

22 Start date

23 Seniority date


9.1.2 Determine Default Date Specification

Use The DATAR feature can be used to default date values when the Date Specifications infotype (0041) is maintained. For this SAP Best Practices for HCM EhP5 package, the DATAR feature is



defined with the date types proposed below when the Date Specifications infotype (IT0041) is maintained.


IMG Path Personnel Management Personnel Administration Evaluation

Basis Date Specifications Determine Default Date Specification

Transaction Code

SPRO

2. On the Process feature DATAR: decision tree screen, make the following entries:

DATAR:

D MOLGA

99 &DATAR=22, NEXTR A "Start date RDS"

99 A &DATAR=23, "Seniority date RDS"


4. Choose Activate.

10 Communication


IMG Path Personnel Management Personnel Administration

Communication Create Communication Types

Transaction Code

SPRO

2. The standard SAP system is delivered with certain communication types, as listed below. We recommend you do not delete the standard delivered entry of 0001 system user name. Communication types with a time constraint of 2 may have gaps but no overlapping records are allowed. Communication types with a time constraint of 3 also allow gaps but records may overlap or more than one subtype may exist at the same time.

Type Description Time Constraint

0001 System user name (SY-UNAME) 2

0002 SAP2 2

0003 Netpass 2

0004 TSO1 2

0005 Fax 2

0006 Voice mail 2

0010 E-mail 3

0011 Credit card number(s) 3

0020 First telephone number at work 2

0030 Private E-mail address 3

CELL Cell phone 3



Type Description Time Constraint

FR01 Health Insurance organization 3

MAIL E-mail 3

MPHN Mobile/car phone 3

PAGR Pager 3

The workflow templates delivered by SAP use Communication Type 0001 to identify the recipient.

11 Customizing Procedures

11.1 Infotype Menus Infotype menus are used to group infotypes to form a business functional area and for data sensitivity. The delivered menus assume the assignment to the user parameter of UGR 98 for the user group.

The tabs displayed in Display and Maintain Master Data can be easily customized to meet the customer's requirements. The infotype menus can be defined so that they depend on the user group and reference user group.

11.1.1 User Group Dependency on Menus and Info Groups

Use This SAP Best Practices for HCM EhP5 package has grouped together commonly used infotypes and created seven infotype menus. Additional infotype menus can be created and changes to the existing menus can be made to meet the client's requirements.


IMG Path Personnel Management Personnel Administration Customizing

Procedures Infotype Menus Infotype Menu User Group Dependency on Menus and Info Groups

Transaction Code

SPRO

2. On the Change View "User Group Dependency on Menus and Info Groups": Overview screen, make the following entries:

Menu Text User-dep. Reaction Ref.

98 Personal Data Select 00

99 Payroll Data Select 00

11.1.2 Infotype Menu

Use



Commonly used infotypes have been grouped together and seven infotype menus have been created in this SAP Best Practices for HCM EhP5 package. Additional infotype menus can be created and changes to the existing menus can be made to meet the client's requirements.



Procedures Infotype Menus Infotype Menu Infotype Menu

Transaction Code

SPRO

4. On the Change View "Infotype Menu": Overview screen, make the following entries:

Menu Menu Text UGR Seq. # Infotype Infotype Text

98 Personal Data 98 01 0000 Actions

98 05 0001 Organizational Assignment

98 10 0002 Personal Data

98 15 0006 Addresses

98 20 0021 Family Member/Dependents

98 25 0105 Communication

98 30 0032 Internal Data

99 Payroll Data 98 01 0000 Actions

98 05 0001 Organizational Assignment

98 10 0002 Personal Data

98 15 0003 Payroll Status

98 20 0007 Planned Working Time

98 25 0008 Basic Pay

98 30 0009 Bank Details

98 35 0041 Date Specifications

98 40 0031 Reference Personnel Numbers

5. Choose Determine Choice of Infotype Menus.

11.2 Determine Choice of Infotype Menus

Use Once the infotype menus have been created, the menus to be displayed and the order in which they appear must be defined.





Procedures Infotype Menus Determine Choice of Infotype Menus

Infotype Menu

Transaction Code

SPRO

2. On the Change View "Dialog Window - Choose Infotype Menus": Overview screen, make the following entries:

Menu Menu Text User Group No Menu Text

01 Personnel Administration 98 01 98 Personal Data

98 05 99 Payroll Data


11.3 Actions Actions are used to link infotypes together and form a business process, for example a hiring action. The delivered actions assume the assignment to the user parameter of UGR 98 for the user group.

11.3.1 Define Info Groups

11.3.1.1 User Group Dependency

Use All actions in this SAP Best Practices for HCM EhP5 package are user dependent and assigned to reference group 98. If the UGR parameter has not been maintained in the user defaults, a warning W is output when the user accesses the action.



Procedures Actions Define infogroups User Group Dependency on Menus

Transaction Code

SPRO

2. On the Change View "User Group Dependency on Menus and Info Groups": Overview screen, make the following entries:

Menu Text User Dep Reaction Reference

00 New Hire X W 98

31 Rehire X W 98

32 External Hire X W 98

33 Transfer X W 98

34 Position Change (same OU) X W 98

38 Leave of Absence (Paid) X W 98

39 Leave of Absence (Unpaid) X W 98

40 Return from Leave of Absence X W 98



Menu Text User Dep Reaction Reference

41 Termination X W 98

42 Retirement X W 98

98 Initial Hire (Data Migration) X W 90

99 Position Assignment (Data Migration) X W 90


11.3.2 Define Info Group 1. Access the activity using one of the following navigation options:


Procedures Actions Define Info Groups Info Group

Transaction Code

SPRO

2. In the Enter InfoGroup Number box, enter the info group defined in section 11.3.2.1, then choose Enter.

3. On the Change View "Info Group": Overview screen, make the entries defined in the table in section 11.3.2.1.


5. Repeat steps 2 through 4 above for the remaining sections (11.3.2.2 through 11.3.2.11).

11.3.2.1 Hiring Action The Hiring action is used to hire an employee in the system.

The following infotypes have been configured for the Hiring action:

Info Group UG IGM No Op IT Infotype Text Sub.

00 Hiring 98 01 INS 0001 Organizational Assignment

98 05 INS 0002 Personnel Data

98 10 INS 0006 Addresses 1

98 15 INS 0007 Planned Working Time

98 20 INS 0008 Basic Pay

98 25 INS 0009 Bank Details 0

98 30 INS 0041 Date Specifications

98 35 INS 0021 Family Member/Dependents

98 90 INS 0105 Communications 0001

98 95 INS 0105 Communications 0010

11.3.2.2 External Hire Action The External Hire action is used to hire non-employees in the system.

The following infotypes have been configured for the External Hire action:





32 External Hire 98 01 INS 0001 Organizational Assignment

98 05 INS 0002 Personnel Data

98 20 INS 0006 Addresses 1

98 25 INS 0007 Planned Working Time

98 30 INS 0021 Family Member/Dependents

11.3.2.3 Transfer Action The Transfer action is used when an employee moves within the company to another area or department/organization. The Transfer action may or may not result in a change of pay as well as a change in work schedule.


33 Transfer 98 01 INSS 0001 Organizational Assignment

98 10 COP 0007 Planned Working Time

98 15 INSS 0008 Basic Pay

11.3.2.4 Position Change (Same OU) Action The Position Change (same OU) action is used when an employee has a change in pay, change in working hours or part-time status. It may also be used when an employee moves to a new position within the same organization.


34 Position Change (same OU) 98 01 INSS 0001

Organizational Assignment


98 15 INSS 0008 Basic Pay

11.3.2.5 Termination Action The Termination action is used when the employee is not expected to return to the organization.


41 Termination 98 01 COP 0001 Organizational Assignment

98 05 COP 0006 Addresses 1

11.3.2.6 Rehire Action The Rehire action is similar to the Hiring action. It has been included as a separate action for two reasons. The first being that the action reasons associated may be different than the Hiring action. Secondly, the former employee may have a personnel number in SAP that is re-activated. Using the same personnel number provides a continuous history in the lifecycle of the employee's involvement with the organization. Operation COP is used instead of INS indicating that the previous record may be copied rather than created.




31 Rehire 98 01 INSS 0001 Organizational Assignment

98 05 MOD 0002 Personal Data



98 20 COP 0008 Basic Pay

98 25 COP 0009 Bank Details 0

98 30 MOD 0041 Date Specifications

98 35 COP 0021 Family Member/Dependents

98 90 COP 0105 Communications 0001

98 95 COP 0105 Communications 0010

11.3.2.7 Retirement Action The Retirement action is used when an employee retires from the organization.


42 Retirement 98 01 INSS 0001 Organizational Assignment



11.3.2.8 Leave Of Absence Action Two Leave of Absence actions are provided. The Paid status assumes that the employee is on paid leave while the Unpaid status assumes unpaid leave.


38 Leave of Absence (Paid) 98 01 COP 0001



39 Leave of Absence (Unpaid) 98 01 COP 0001


11.3.2.9 Return from Leave of Absence Action The Return from Leave of Absence action is used to return an employee from a leave of absence.


40 Return from Leave of Absence 98 01 COP 0001






11.3.2.10 Initial Hire (Data Migration) Action The Initial Hire (Data Migration) action is used during data migration to perform an initial load of employees into the SAP system. The following infotypes have been configured for the Initial Hire (Data Migration).


98 Initial Hire (Data Migration) 90 01 INS 0001


90 05 INS 0002 Personal Data

90 10 INS 0032 Internal Data

11.3.2.11 Position Assignment (Data Migration) Action The Position Assignment (Data Migration) action is used during data migration to place an employee in a valid position.


99 Position Assignment (Data Migration) 90 01 COP 0001


11.3.3 Set Up Personnel Actions In this SAP Best Practices for HCM EhP5 package, you can use personnel actions to carry out complex personnel administration procedures. A personnel action displays, in the correct sequence, the infotypes that have to be maintained for a specific action.

Use In this SAP Best Practices for HCM EhP5 package, you can create the personnel actions used to capture the major events that can occur with an employee. You can use personnel actions to carry out complex personnel administration procedures. A personnel action displays, in the correct sequence, the infotypes that have to be maintained for a specific action.



Procedures Actions Set Up Personnel Actions

Transaction Code

SPRO

2. In the Choose Activity dialog box, select Personnel Action Types.

3. On the Change View "Personnel Action Types": Overview screen, choose the New Entries pushbutton and enter the following values:

Action

Name of Action

FC

Customer Specific

Employment

Spec. Pymt

Check

P PA

EG

ESG

IG

Date Control

U0000

U0302

0 New 1 3 1 x x x x 0 X X



Action

Name of Action

FC

Customer Specific

Employment

Spec. Pymt

Check

P PA

EG

ESG

IG

Date Control

U0000

U0302

Hire

30 Transfer

0 x x x x 33

X X

31 Position Change (same OU)

0 x x 34

X X

27 Termination

0 0 0 MSN20

41

1 X X

3 Rehire 0 3 1 MSN21

x x x x 31

X X

28 Retirement

0 2 0 MSN32

x x 42

1 X X

46 Leave of Absence (Paid)

0 38

X X

37 Leave of Absence (Unpaid)

0 1 39

X X

48 Return from Leave of Absence

0 3 x x x x 40

X X

4 External Hire

1 3 1 x x x x 32

X X

97

Initial Hire (Data Migration)

1 3 1 x x x x 98

X X

98

Position Assignment (Data Migrati

0 3 1 99

X X



Action

Name of Action

FC

Customer Specific

Employment

Spec. Pymt

Check

P PA

EG

ESG

IG

Date Control

U0000

U0302

on)


11.3.4 Set Up Priority List for Personnel Action Types

Use You can define a priority list for the personnel action types that do not change status and must, therefore, not be stored in the Actions infotype (0000). If the personnel administrator performs no personnel action types that change status, but instead several that do change status on one particular day, the priority list specifies which of these personnel action types is to be stored in the Actions infotype (0000).



Procedures Actions Set Up Personnel Actions

Transaction Code

SPRO

2. In the Choose Activity dialog box, double-click Priority List for Personnel Action Types.

3. On the Change View " Priority List for Personnel Action Types ": Overview screen, make the following entries:

Action Name of Action Type Priority

30 Transfer 2

31 Position Change (same OU) 3

46 Leave of Absence (paid) 1


11.3.5 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 When 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 that are executed for an employee, set the indicator U0302 for all personnel action types. All personnel action types that 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)

The following personnel actions have been configured for the Additional Actions infotype (0302) to be displayed.



Personnel Actions

00 - New Hire 46 - Leave of Absence (Paid)

30 -Transfer 37 - Leave of Absence (Unpaid)

31 -Position Change (same OU) 48 - Return from Leave of Absence

27 - Termination 04 -External Hire

03 - Rehire 97 -Initial Hire (Data Migration)

28 - Retirement 98 -Position Assignment (Data Migration)

Additional Actions SAP standard functionality does not allow more than one status-changing personnel action to be executed on the same date.

Creating multiple actions that change the employee status fields causes the first action stored in the Actions infotype (0000) to be deleted. This means that you cannot run a Termination and a Retirement action on the same day. In this case, the second action run would overwrite the first.

All programs that evaluate an employee's status evaluate the Actions infotype (0000) exclusively. This infotype has the time constraint 1, which means that only one valid Actions infotype can exist in the system at any one time.

It is possible, however, to use the Additional Actions infotype (0302) functionality, which allows you to record more than one action on the same day, provided the overall employment status has not changed. For example, you may need to run a Transfer and a Leave of Absence (Paid) action or a Transfer and a Position Change action on the same day.

Only action types and reasons are saved in the Additional Actions infotype.

The indicators U0000 and U0302 are used to define whether personnel action types are to be stored in the Actions infotype (0000) and/or the Additional Actions infotype (0302). As part of the installation process, the SAP standard report RPUEVSUP Activation Additional Actions prepares the system for this functionality, including setting the switch ADMIN EVSUP in Table T77S0 to 1 (Additional Actions Infotype 0302 is activated).

Depending on the priority of the action, the system determines which action should be stored in the Actions infotype and which action(s) should be recorded in the Additional Actions infotype only. If no priority is specified, the system uses the action type identifier to determine the priority sequence.

11.3.6 Create Reasons for Personnel Actions

Use You can determine the reasons for actions in this SAP Best Practices for HCM EhP5 package.



Procedures Actions Create Reasons for Personnel Actions



Transaction Code

SPRO

2. On the Change View "Reason for Action": Overview screen, make the following entries:

Action Code / Description Code Infotype text

00 - New Hire

01 Replacement

02 Expansion

03 Acquisition

04 Special Projects

05 Trainee/Intern

30 - Transfer 01 Org Unit Change

02 Career Opportunity

03 Reorganization

04 Relocation

05 External to Regular

31 - Position Change (same OU) 01 Lateral Move

02 Promotion

03 Pay Change

27 - Termination 01 Notice by Employee

02 End of Contract

03 Mutual Agreement

04 Dismissal

05 Death of Employee

06 Did Not Start

03 - Rehire 01 Replacement

02 Expansion

03 Acquisition

04 Special Projects

28 - Retirement 01 Retirement

02 Early Retirement

03 Medical Retirement

46 - Leave of Absence (Paid) 01 Sickness Absence

02 Personal Leave

37 - Leave of Absence (Unpaid) 01 Sickness Absence

02 Personal Leave

48 - Return from Leave of Absence 01 Return to Work



Action Code / Description Code Infotype text

04 - External Hire 01 Contracting

02 Agency Work

03 Seasonal Work

97 - Initial Hire (Data Migration) 01 Initial Hire (Data Migration)

98 - Position Assignment (Data Migration) 01

Position Assignment (Data Migration)


11.3.7 User Group Dependency on Menus and Info Groups In this step, you define a menu of actions that appears if the user chooses the Personnel actions function in HR master data maintenance. The menu can be defined so that it depends on the user group (user parameter UGR). If there are no entries in the table for the user's user group or if the user has not maintained the user group, a reference user group is determined, which is used to set up the menu.

11.3.8 Action Menu

Use The Action menu controls the actions that are listed in PA40 Personnel Actions as well as the sequence.



Procedures Actions Change Action Menu Action Menu

Transaction Code

SPRO

2. On the Change View "Action Menu": Overview screen, make the following entries:

Menu Menu Text User Group Seq Action Text

01 Actions 98 01 00 New Hire

98 05 30 Transfer

98 10 31 Position Change (same OU)

98 15 46 Leave of Absence (Paid)

98 20 37 Leave of Absence (Unpaid)

98 25 48 Return from Leave of Absence

98 30 27 Termination

98 35 28 Retirement

98 40 03 Rehire

98 45 04 External Hire



Menu Menu Text User Group Seq Action Text

90 01 97 Initial Hire (Data Migration)

90 05 98 Position Assignment (Data Migration)


11.4 Dynamic Actions

Use Dynamic actions allow you to trigger certain types of process when maintaining an infotype. Examples of these processes are calling an additional infotype and executing a function module to generate a field value, or creating a new infotype and passing field values such as dates to the new infotype such as with infotype IT0041 Date Specification.

Dynamic actions are not shipped with this SAP Best Practices for HCM EhP5 package.



Procedures Dynamic Actions

Transaction Code

SPRO

12 Customizing User Interfaces

Use Different entry screens are provided for certain infotypes. Depending on the transaction class (A for employee, B for applicant) or the country grouping, a different screen can be used. In addition to this, you can also change the characteristics of the individual screen fields: For example, you can define fields as required entry fields or suppress any fields that are not required.

Screen modifications are not shipped with this SAP Best Practices for HCM EhP5 package.



User Interfaces Change Screen Modifications

Transaction Code

SPRO

2. On the Change View "Infotype Screen Control": Overview screen, make the required changes.




13 Work Schedules

13.1 Groupings for the Personnel Subareas

Use In SAP Time Management, personnel subarea groupings are used to apply settings to groups of employees. The personnel subarea groupings for time recording in this SAP Best Practices package vary depending on the specific function of the grouping code.


IMG Path

Time Management Work Schedules Personnel Subarea

Groupings Group Personnel Subareas for the Work Schedule

Transaction Code

SPRO

2. On the Change View "Personnel Subarea Grouping for Work Schedule ": Overview screen, make the following entries:

PA Personnel Area Text PSA PSA Text PS grouping

9900 Global Personnel Area 1001 Administration 99

9900 Global Personnel Area 1002 Human Resources 99

9900 Global Personnel Area 1003 Finance 99

9900 Global Personnel Area 1004 Marketing 99

9900 Global Personnel Area 1005 Sales 99

9900 Global Personnel Area 1006 Operations 99

9900 Global Personnel Area 1007 Manufacturing 99


13.2 Group Personnel Subareas for the Daily Work Schedule

Use In this step, you assign a personnel area grouping for daily work schedules to a personnel area grouping for work schedules.


IMG Path

Time Management Work Schedules Personnel Subarea

Groupings Group Personnel Subareas for the Daily Work Schedule

Transaction SPRO



Code

2. On the Change View "Assignment of PS grouping for Work Schedule to Daily Work Schedule ": Overview screen, make the following entries:

PS grouping DWS grouping

99 99


13.3 Define Work Break Schedules

Use Two work break schedules are delivered that provide both paid and unpaid breaks.


IMG Path Time Management Work Schedules Daily Work Schedules Define Break Schedules

Transaction Code

SPRO

2. On the Choose Activity screen, double-click the Determine Break Schedules activity.

3. On the Change View "Text for Work Schedule Grouping": Overview screen, choose the New Entries pushbutton.


GRP Break Sched. No Start End P Unpaid Paid After

99 NORM 00 12:00 13:00 1.00

99 PART 01 10:00 10:30 0.50


13.4 Define Daily Work Schedules

Use Several examples of daily work schedules are provided in the SAP system to support a variety of shifts.


IMG Path Time Management Work Schedules Daily Work Schedule Define Daily Work Schedules

Transaction Code

SPRO

2. On the Change View "Daily Work Schedule": Overview screen, review the following values:



GRP DWS Text Variant

Planned Working Hours

DWS Selection Rule

Planned Time WBS

Normal

Work Time

DWS Class

99 PART Part-time

04.00 99 08:00 12:30

PART 1

99 FREE Off 00.00 00:00 24:00

0

99 NORM Normal Hours

08.00 99 08:00 17:00

NORM 1

13.5 Period Work Schedules

Use Several period work schedules are provided in the SAP system.


IMG Path Time Management Work Schedules Period Work Schedules Define Period Work Schedules

Transaction Code

SPRO

2. On the Change View "Period Work Schedule": Overview screen, choose the New Entries pushbutton and enter the following values:

Grp PWS PWS Text Week 01 02 03 04 05 06 07

99 NORM Normal Hours 001 NORM NORM NORM NORM NORM FREE FREE

99 PART Part-Time Hours 001 PART PART PART PART PART FREE FREE


13.6 Employee Subgroup Groupings (for Work Schedules)

Use These groupings are linked to employee subgroups to define a specific work schedule that is allowed for a specific type of employee.


IMG Path

Time Management Work Schedules Work Schedule Rules and

Work Schedules Define Employee Subgroup Groupings

Transaction Code

SPRO



2. On the Choose Activity screen, choose the Group Employee Subgroups for Work Schedules activity and choose the Choose pushbutton.

3. On the Change View "Employee Subgroup Grouping for Work Schedule ": Overview screen, choose the New Entries pushbutton.


EG Employee Group ESG Employee Subgroup Grouping

1 Employee Y0 Non-Exempt/Hourly 1

1 Employee Y1 Exempt/Salaried 2

1 Employee Y3 Executives 2

1 Employee YJ Trainees 2

1 Employee YG Interns 2

1 Employee YF Temps 2

1 Employee YE Students 2

A Part-

Date post:	16-Nov-2015
Category:	Documents
Upload:	fahadsap
View:	78 times
Download:	14 times

Basic Configuration for SAP HCM Since 2012

Documents