1 of 121

Personnel Administration

Brussels

1

2 of 121

Agenda

7

PA as ‘Consultant’ (Master Data Customizing)

1

Overview Personnel Administration (PA)

2

PA as ‘End User’ (Data maintenance)

Infotypes and subtypes

3

Time constraints and validity periods

4

5

Data maintenance procedures and actions

6

General concepts

IMG <> Table maintenance

8

Customizing tables

9

10

Infotypes structure and attributes

11

Personnel actions

12

Dynamic actions, features and user exits

13

Legacy System Migration Workbench

2

3 of 121

Course objectives

To learn:

Comprehend and carry out the basic processes of Personnel Administration

To be able to:

Explain major functional areas of SAP R/3 Human Resources

such as Personnel Administration

Maintain employee data
Execute Personnel Actions

3

4 of 121

Overview�Personnel Administration (1)

Organization

Management

Payroll &

Accounting

Compensation

management

Training & Event

Management

Recruitment

Performance

Management

Personal

Development

Personnel

Management

Time �Management

4

5 of 121

Overview�Personnel Administration (2)

Organization

Management

Payroll &

Accounting

Compensation

management

Training & Event

Management

Recruitment

Performance

Management

Personal

Development

Personnel

Management

Time �Management

5

6 of 121

Company structure management

12

Générale�de Banque

13

G-Fonds�

14

Cie belge�Fin. Indust.

15

Bq belge

pr étranger

16

Coperfort�

GBZB

Zone Bxl

GBZN�Zone nord

GBZS�Zone sud

GBEC�Ent Centr

GFON

GCOP

GBFI

GBET

BXLG�Général

NRDG

Général

SUDG

Général

Company code

Personnel Area

Personnel Subarea

NRDF

Ag. Franco

BXLP

Périphérie

SUDO

SO ex.Mons

SUDE

Cantons Est

Enterprise Structure

Personnel Structure

O

S

C

Position

Job

P

Employee

External

Contractors

Retiree

Active

Hourly Worker

Monthly worker�Executive�Manager

Senior Manager�Student

Expatriate

Inactive

Organizational Structure

Hourly Worker

Monthly worker�Executive�Manager

Senior Manager�Student

Executive�Manager

Senior Manager�

Hourly Worker

Monthly worker�Executive�Manager

Senior Manager�Student

Organizational Unit

6

7 of 121

Transaction code (1)

What ?

There is a transaction code for each SAP-HR process:

PA10: personnel file
PA20: display data
PA30: maintain data
PA40: maintain actions
PA70: fast entry
...

Also in customising and development

transaction codes lead to the different activities:

SPRO: Implementation guide
SE11: ABAP dictionary
SE38: ABAP development
SM30: table maintenance
...

/O to create new session

/N to erase old session

7

8 of 121

Transaction code (2)

How to find ?

What’s the transaction code of this process?

1st way:

See at the bottom of all pages

2nd way:

System 🡪 Status...

3rd way:

Extra 🡪 Settings 🡪 Display technical names

8

9 of 121

Agenda

7

PA as ‘Consultant’ (Master Data Customizing)

1

Overview Personnel Administration (PA)

2

PA as ‘End User’ (Data maintenance)

Infotypes and subtypes

3

Time constraints and validity periods

4

5

Data maintenance procedures and actions

6

General concepts

IMG <> Table maintenance

8

Customizing tables

9

10

Infotypes structure and attributes

11

Personnel actions

12

Dynamic actions, features and user exits

13

Legacy System Migration Workbench

9

10 of 121

Concept - End user

Example – different kinds of payroll end users:

Payroll Manager

Display HR master data and personnel file
Display remuneration statement, payroll

Payroll Process Administrator

Performs time evaluation and runs payroll
Creates remuneration statement
Creates file for wage and salary payments
Post payroll results to accounting

Payroll Administrator

Maintains HR master Data
Simulates payroll.

10

11 of 121

Concept -�Personnel Administration

manage data, from a single database

individual data
collective data

store data

used for internal and legal reporting

Goal:

enable other HR related ERP components to use accurate, efficient and unique data within the whole organization

11

12 of 121

Data maintenance

Who?

Search help for personnel number

Direct selection Match codes =n.lastname.firstname + *

What?

Infotypes

Menu F4 Direct selection

When?

Validity period of a piece of information

12

13 of 121

Concept - Personnel number

WHO?

13

14 of 121

Agenda

7

PA as ‘Consultant’ (Master Data Customizing)

1

Overview Personnel Administration (PA)

2

PA as ‘End User’ (Data maintenance)

Infotypes and subtypes

3

Time constraints and validity periods

4

5

Data maintenance procedures and actions

6

General concepts

IMG <> Table maintenance

8

Customizing tables

9

10

Infotypes structure and attributes

11

Personnel actions

12

Dynamic actions, features and user exits

13

Legacy System Migration Workbench

14

15 of 121

Infotype

IT0009

Fiscal Data

DEUTSCHE

MARK

DEUTSCHE

MARK

x x x x x x x x x x x

cheque

Family & related person

Addresses

Bank Details

Organizational

Assignment

Tax Office

Personal Data

Planned working time

Person X

Birth

certificate

IT0001

IT0021

IT0006

IT0101

IT0002

IT0007

One subject per screen

WHAT?

15

= A set of data that is grouped together according to subject matter

For every person the organization has a closet where all the information about this person is stored. For each kind of information another map is used. So the information about the name and surname of the person is conserved in another map than his address data.

In SAP all these maps are called infotypes. As a user of SAP we can also say that it’s one screen where you can see all kinds of data related to the same subject.

SHOW different infotypes !

The aim of the HR component is to enable the user to process employee data in an effective structure in accordance with business requirements.

From a technical perspective, the data structure of infotypes mirrors a logical set of data records. Infotypes can be identified by their four-digit keys (for example, the Addresses infotype (0006)).

To facilitate reporting on past employee data, infotypes can be saved for specific periods.

From the user perspective, infotypes are entry screens that support the maintenance of infotype records. You can edit infotype records individually or by using fast data entry.

The following functions are frequently used for infotype records:

Create; Change; Copy; Delimit; Delete

16 of 121

Subtype

1

2

Infotype 0021

Family

Subtype 2

Subtype 1

Spouse

Children

One subject per screen

16

17 of 121

Object ID

1

2

1

2

Infotype 0021

Family

Subtype 2

Subtype 1

nr 02

nr 01

Spouse

Children

One subject per screen

17

18 of 121

Screen parts

Title

Header

Validity period

Infotype content

Each infotype has these screen parts

18

19 of 121

Maintain infotypes

New records

Changing existing records

19

20 of 121

Infotypes:�Common <> country specific

Actions (IT0000)

Organizational Assignment (IT0001)

Personal Data (IT0002)

Addresses (IT0006)

Planned Working Time (IT0007)

Basic Pay (IT0008)

Date Specifications (IT0041)

●

Family Allowance A (IT0043)

Company Pension Fund CH (IT0046)

Tax Data GB (IT0065)

Social Insurance B (IT0100)

Fiscal Data B (IT0101)

Code INSEE F (IT0217)

CBS NL (IT0408)

●

SAP Standard Common

SAP Standard Local

20

21 of 121

Excercise: infotypes

Search for ‘Arinso Employee XX’ (50 to 75)

Display IT 0001
Create IT 0006
Create IT 0021 subtype 1 (start date 01/05/2005)
Create IT 0021 subtype 2 (start date 01/05/2005)
Copy IT0009
Change IT0006

Take a look at infotypes 7, 8, 9, 19, 41

21

22 of 121

Agenda

7

PA as ‘Consultant’ (Master Data Customizing)

1

Overview Personnel Administration (PA)

2

PA as ‘End User’ (Data maintenance)

Infotypes and subtypes

3

Time constraints and validity periods

4

5

Data maintenance procedures and actions

6

General concepts

IMG <> Table maintenance

8

Customizing tables

9

10

Infotypes structure and attributes

11

Personnel actions

12

Dynamic actions, features and user exits

13

Legacy System Migration Workbench

22

23 of 121

Validity period

Each screen has a validity period

The validity period indicates

when the infotype content is valid

WHEN?

23

24 of 121

Concept:�Time constraints (1)

determine how many times a certain screen must and can exist

defined at the level of:

the infotype
or the subtype

24

25 of 121

Concept:�Time constraints (2)

4 options :

1 : obligatory, no gaps, no overlappings

🡪 Personal data, official address

2 : optional, gaps, no overlappings

🡪 Spouse, company car

3 : optional, gaps, overlappings

🡪 Education, former employer

4 : per subtype

🡪 Addresses infotype

25

26 of 121

Data historic

Validity period + Time constraints

=

Data historic

01/05/2000

01/11/2000

31/12/9999

Create

$ 5000

$ 5500

$ 5000

$ 5500

26

27 of 121

Example

Official address – Infotype 0006

Hiring

01.05.2004

04.06.2004

01.08.2004

31.12.9999

Wrong number

Moving

01.05.2004 – 31.12.9999

Nr. 12

Nr. 20

01.05.2004 – 31.12.9999

Brussel

Nr. 34

Leuven

01.08.2004 – 31.12.9999

Nr. 20

Brussel

01.05.2004 – 31.07.2004

27

28 of 121

Excercise: time contraints

Create IT 0021 subtype 1 (start date: 01/07/2006)
Create IT 0021 subtype 2 (start date: 01/07/2006)

What is the difference between these subtypes?
What are the time constraints of these subtypes?

What is the difference between the overviews of IT 0002 and IT 0006?

28

29 of 121

Agenda

7

PA as ‘Consultant’ (Master Data Customizing)

1

Overview Personnel Administration (PA)

2

PA as ‘End User’ (Data maintenance)

Infotypes and subtypes

3

Time constraints and validity periods

4

5

Data maintenance procedures and actions

6

General concepts

IMG <> Table maintenance

8

Customizing tables

9

10

Infotypes structure and attributes

11

Personnel actions

12

Dynamic actions, features and user exits

13

Legacy System Migration Workbench

29

30 of 121

Infotype Screens

Change Organizational Assignment

Org Structure

Create Personal Data

Org Structure

Create Bank Details

Org Structure

Create Addresses

Org Structure

Create Planned Working Time

Org Structure

Create Actions

Org Structure

Recur. Payments/

Ded

Additional Payments

Fiscal Data D

Child Allowance D

with proposal

Fast Entry

1 Infotype

Multiple Personnel

Numbers

Fast Entry

1 Infotype

Multiple Personnel

Numbers

Single Screen

1 Infotype

1 Personnel number

Single Screen

1 Infotype

1 Personnel number

Personnel Actions

Sequence of Infotypes

1 Personnel number

Personnel Actions

Sequence of Infotypes

1 Personnel number

30

31 of 121

Data maintenance:�Predefined HR scenario’s

Organizational

Reassignment

Re-entry into

company

Retirement

Early

Retirement

Leaving

Family event

Hiring

Career

Interruption

Scenario's

Infotype access through actions

31

32 of 121

Personnel Actions (1)

Actions

Change of your organizational assignment (IT 0001)
Ex. : hiring, reassignment, pension, leaving, …
Stored in IT 0000

Administrative actions

No change of your organizational assignment, but of other infotypes
Ex. : change of your family situation,
Stored in IT 0000 and IT 0302

32

33 of 121

Personnel Actions (2)

Data maintenance for predefined �HR scenario’s by means of actions

33

34 of 121

Personnel Actions (3)

34

35 of 121

Hiring procedure

Create action

(Infotype 0000)

Organizational Assignment

(Infotype 0001)

Contracts

(Infotype 0016)

Date monitoring (expiry of contract)*

(Infotype 0019)

Date monitoring (expiry of probation)*

(Infotype 0019)

Personal Data

(Infotype 0002)

Family/Related Person (child)*

(Infotype 0021 subtype 2 )

Family/Related Person (spouse)*

(Infotype 0021 subtype 1)

or

Family/Rel. Person (companion)*

(Infotype 0021 subtype 7)

Addresses

(Infotype 0006)

Planned Working time

(Infotype 0007)

Basic Pay

(Infotype 0008)

Dates Specifications

(Infotype 0041)

Personnel Actions

Country specific infotypes

35

36 of 121

Infotype 0001

Additional

authorization

check

Determines

when

payroll is run

Determines

the

administrators

responsible

36

37 of 121

Payroll Area (1)

©

SAP AG 2003

Payroll Organization

Run payroll for previous

month

on 10th of the month

Run payroll for current

month on 28th of the month

Jan.

1

Feb. 1

Jan. 1

Payroll area YY

Payroll area XX

Feb. 1

37

38 of 121

Payroll Area (2)

©

SAP AG 2003

Payroll Control Record

Simulation

Payroll area

XX Salaried employees

Released for payroll

Released for corrections

Exit payroll

Check payroll results

Incorrect personnel no.

Payroll area

Payroll status

XX

monthly

The different stages of

Payroll

Release payroll

Start Payroll

Check Results

Corrections

Exit Payroll

International

Payroll

38

39 of 121

Payroll Area (3)

©

SAP AG 2003

Overview: Payroll Organization

Period

parameter

Date

modifier

and

Payroll

periods

Calendar for

cumulations

Control record

Assigned to the

payroll area

Exists for each

payroll area

For each combination

of period parameter

Date

modifier

and

Monthly or

weekly?

Additional

date types

Which payroll

year, start and end

of periods

Cumulations

of

wage types for

reporting purposes

Controls the individual

payroll phases

39

40 of 121

Organizational Key

©

SAP AG 2003

Personnel

subarea

1000

Organizational key

10001300

Organizational key

10001200

Personnel

subarea

1000

Cost center

1300

Cost center

1200

40

41 of 121

Administrator (1)

©

SAP AG 2002

Administrators

Time Recording

Administrator:

Error lists in

Time Management

Automatic mail

if changes are made to

infotypes

Reporting/

Evaluations

Payroll Administrator:

Contact

person

on remuneration

statements

Authorization

checks

Personnel Administrator:

Monitoring of Tasks

41

42 of 121

Administrator (2)

©

SAP AG 2002

Administrator Assignment

Group

Admin.

Name of administrator

F. of

addr

.

Tel.no.

SAP Name

0001

001

002

003

CA

NDP

Joanne Henderson

Edward Carter

Robert Bell

Chris

Appleman

Nicola Davenport

Ms

Mr

Ms

4711

5541

1239

6665

9848

HENDERSONJ

CARTER

BELLR

APPLEMAN

DAVENPORTN

Org. Assignment (0001)

Administrator,

Group,

HR,

Time Rec., Payroll

View: Change Administrator

42

43 of 121

Excercise: Personnel action

Hire 2 or more employees

Start date: 01/03/2005
Personnel area: ARBE, ARNL, ARUK, ARUS, ARPL
Employee group: 1
Employee subgroup: 01 - 05
Position: Use the position that you created yesterday or create a new one

43

44 of 121

Agenda

7

PA as ‘Consultant’ (Master Data Customizing)

1

Overview Personnel Administration (PA)

2

PA as ‘End User’ (Data maintenance)

Infotypes and subtypes

3

Time constraints and validity periods

4

5

Data maintenance procedures and actions

6

General concepts

IMG <> Table maintenance

8

Customizing tables

9

10

Infotypes structure and attributes

11

Personnel actions

12

Dynamic actions, features and user exits

13

Legacy System Migration Workbench

44

45 of 121

IMG <> Table maintenance

Two different ways:

IMG Table maintenance

Transactions

code

SPRO

SM31

45

IMG

Tool for configuring the SAP System to meet customer requirements. The Implementation Guide (IMG) explains all the steps in the implementation process, tells you the SAP standard (factory) Customizing settings and describes the system configuration activities. The hierarchical structure of the IMG is based on the application component hierarchy and lists all the documentation which is relevant for implementing the SAP System. The main component of the Implementation Guide is the IMG activities which go to Customizing, where the relevant system settings are made. You can also document projects in the IMG.

The SAP Reference IMG contains all IMG activities, sorted by application component and into "General settings" and "Enterprise structure".

The Enterprise IMG is a subset of the SAP Reference IMG containing only the IMG activities required for the application component to be implemented. (Note: The Enterprise IMG no longer exists after R/3 Release 4.6A.)

The Project IMG is a subset of the Enterprise IMG (until Release 4.5B) or the SAP Reference IMG (from Release 4.6A) containing the IMG activities required for the application component to be implemented in a specified Customizing project. Project views can be based on a Project IMG and specified attributes, for use in Release Customizing (Delta Customizing or Upgrade Customizing).

46 of 121

IMG <> Table maintenance

IMG Transaction code: SPRO

With the implementation guide, you can access all tables and features to configure the HR system.

You can maintain:

Set up infotypes
Infotypes menus
Actions:

Infogroups
Reasons for actions
Action menu

Dynamic actions etc…
Define infotype header
Infotypes screen control

46

47 of 121

IMG <> Table maintenance

Two different ways:

IMG Table maintenance

Transactions

code

SPRO

SM31

47

48 of 121

IMG <> Table maintenance

Table maintenance Transaction code: SM31, SM30

With the Table maintenance screen, you can access all tables that you know to customise the HR system.

48

49 of 121

Agenda

7

PA as ‘Consultant’ (Master Data Customizing)

1

Overview Personnel Administration (PA)

2

PA as ‘End User’ (Data maintenance)

Infotypes and subtypes

3

Time constraints and validity periods

4

5

Data maintenance procedures and actions

6

General concepts

IMG <> Table maintenance

8

Customizing tables

9

10

Infotypes structure and attributes

11

Personnel actions

12

Dynamic actions, features and user exits

13

Legacy System Migration Workbench

49

50 of 121

Customizing Tables:�Key and functional fields

Transaction code: SM30

An entry in a Customizing table consists of key fields and function fields.
Key fields identify a specific unique entry, whereas function fields describe this entry.
There is only one table entry with the same key fields.

50

51 of 121

Customizing Tables:�Delete and Save

Transaction code: SM30

To delete entries in Customizing tables,

select the entries that you want to delete and then select Delete.

You must save all the changes you make to Customizing tables

51

52 of 121

Customizing Tables:�Create and Copy

Transaction code: SM30

New Entries� The system displays an empty input screen and you must enter key and function fields.
Copy� Select an entry that you want to copy and overwrite the entries in the key and, if necessary, the function fields on the subsequent screen

52

53 of 121

Customizing Tables:�Delimit

Transaction code: SM30

©

SAP AG 2003

Change View "Pay Scale Groups": Overview

S

y

stem

E

dit

G

oto

H

elp

O

bject

Uti

l

ities

Grpg

PS group

Lv

.

WT

Start date

End date

Amount

Curr

.

01.01.79

1

WW

1010

31.12.9999

6.500,00

01.01.92

2

AT

31.12.9999

7.750,00

3

AT

01.01.79

31.12.9999

4.000,00

Validity Limit: Entry

Position...

Entry 1 of 1

Valid from

01.01.2003

If you want to make an entry invalid as of

a certain date, choose

Delimit

and enter

the delimitation date.

The system automatically creates a new

record, and you can overwrite the function

fields.

In time

-

dependent tables, the system

displays the record currently valid.

Use the

Expand

-

Collapse

function to

display the other

records.

53

54 of 121

Agenda

7

PA as ‘Consultant’ (Master Data Customizing)

1

Overview Personnel Administration (PA)

2

PA as ‘End User’ (Data maintenance)

Infotypes and subtypes

3

Time constraints and validity periods

4

5

Data maintenance procedures and actions

6

General concepts

IMG <> Table maintenance

8

Customizing tables

9

10

Infotypes structure and attributes

11

Personnel actions

12

Dynamic actions, features and user exits

13

Legacy System Migration Workbench

54

55 of 121

Infotypes structure (1)

F1

55

56 of 121

Infotypes structure (2)

Transaction code: SE11

F1

F9

56

57 of 121

Infotypes attributes:�IMG <> Table maintenance

Transaction code: SPRO Transaction code: SM31

Table

T582A

57

58 of 121

Infotypes attributes:�Overview

I. General attributes

II. Display en selection

III. Retroactive accounting trigger

IV. Technical data

Table V_T582A

58

59 of 121

Infotypes attributes:�Example

example: IT0002

59

60 of 121

Infotypes attributes:�General attributes (1)

I. General attributes

Time constraint

= A time constraint indicates whether more than one infotype record may be available at one time

60

61 of 121

Infotypes attributes:�General attributes (2)

Possible time constraints

1 => One record obligatory + continuity obligatory

note: timeconstraint 1 of IT0000, IT0001 and IT0002 cannot be edited in V_T582A

2 => Only one record at a time + continuity not obligatory

3 => Multiple records possible + continuity not obligatory

A => Only one record can exist from 01.01.1800 to 31.12.999;

these infotypes may not be deleted

(e.g. IT0003) see table V_582B

B => Idem A but these infotypes may be deleted

(e.g. IT0031)

T=> Time constraint depends of subtype

(e.g. IT0009)

Z => Only for time infotypes;

time constraint depends of timerelation class defined in table V_T554S_I (also see collision checks in V_T554Y)

(e.g. IT2001)

61

62 of 121

Infotypes attributes:�General attributes (3)

Time constraint table

= when the time constraint is subtype dependent

62

63 of 121

Infotypes attributes:�General attributes (4)

Maint. Aft. leave

example IT0006 Addresses => time constraint table V_T591A

= This field controls whether you can record master data after an employee has left the company.

A warning tells you whether you are permitted to do so or not.

Blank

= modifying the infotype after leaving is authorized

W

= modifying the infotype after leaving is authorized + the system will give a warning

E

= modifying the infotype after leaving is not authorized

63

64 of 121

Infotypes attributes:�General attributes (5)

Subtype obligatory

= If the layout of an infotype screen depends on the subtype, you must enter the subtype when creating a new record.

Subtype table

= table with subtypes of an infotype

Table V_T591A

Indicator Objid = define if multiple records of a subtype can exist at the same time

ex. IT0021 Subtype Chiild

Subtype field

= name of the field of the subtype in the structure of the PA-infotype (see trans SE11 struct. PSxxxx)

64

65 of 121

Infotypes attributes:�Display and selection (1)

II. Display and selection

Select w/start

= most 3: record valid on input date of selection screen

Select w/end

= always 5: record(s) with valid data in the selected period

Select w/o date

= 6: all records valid from cpu date to end of times

= These values of the fields define the way the records are displayed for input for begin and enddate.

65

66 of 121

Infotypes attributes:�Display and selection (2)

Create w/o strt

= define the begindate that will be proposed by the system when at creation of the infotype no begindate is filled in the selectionscreen

blank begindate is blank (vb. IT0023)

1 record does not exist => entry date = begindate

record exist => begindate of existing record

(vb. IT0002,IT0027)

2 startdate of actual organizational definition (vb. IT0100, IT0101, IT0105)

3 CPU datum = date of today (vb. IT0017)

66

67 of 121

Infotypes attributes:�Display and selection (3)

Create w/o end

= define the enddate that will be proposed by the system when at creation of the infotype no enddate is filled in the selectionscreen

blank no value (vb. IT0023)

1 enddate is 31.12.9999 by default

(vb. IT0100,IT0101)

2 enddate by default = date of leaving (vb. IT0007)

3 enddate by default = begindate of actual record

67

68 of 121

Infotypes attributes:�Display and selection (4)

List time per.

= define the period that will be show in the overview

Crossed = overview shows all periods from selectionscreen

blank = overview shows all periods without the selectionscreen

68

69 of 121

Infotypes attributes:�Retroactive accounting trigger (1)

III. Retroactive accounting trigger

Before ERA date

You can use the entry before earliest retroactive accounting date indicator to define if payroll relevant data may be entered in a personnel control record before the earliest retroactive accounting period of the relevant payroll accounting area (transaction code PA03).

69

70 of 121

Infotypes attributes:�Retroactive accounting trigger (2)

Retr.acct.payr.

When you make entries in the payroll past, the Earliest Change in Master Data Since Last Payroll field is set in the Payroll Status infotype (0003).

blank = Infotype is not relevant to retroactive accounting,

R = Change triggers retroactive accounting,

T = Retroactive accounting is field dependent according to T588G.

70

71 of 121

Infotypes attributes:�Retroactive accounting trigger (3)

Table V_T588G

71

72 of 121

Infotypes attributes:�Retroactive accounting trigger (4)

Entry of RA limit time

If checked it’s possible to make modifactions before the « Personal earliest retroactive accounting date ».

Retr.acct PDC

Define if the infotype at recalculationis relevant for time management

72

73 of 121

Infotypes attributes:�Retroactive accounting trigger (5)

Past entry all.

Permissibility of entries relating to the payroll past.�

Blank = Entries which relate to past payroll periods are permitted.�This type of entry is like changing or creating a database record with a start date which lies in the last payroll period or prior to this. The system displays a warning message.

X = Entries which relate to past payroll periods are permitted. The system displays a warning message.

E = Entries in the payroll past are not permitted. If payroll has has never been run for the employee in question, the entries are permitted.

I = Whether or not entries in the payroll past are permitted depends on which infotype is being processed. This entry is only suitable for certain infotypes. If used in other infotypes, the system does not perform a check.

73

74 of 121

Exercise:�Time constraints

What seems to you the correct time constraint for:

IT0000 procedures
IT0002 Personal Data
IT0007 Planned Working Time
IT0037 Insurance
IT0001 Organizational Assignment
IT0023 Other/Previous Employers

74

75 of 121

Excercise:�Payroll relevant infotypes

Choose and explain the meaning of blank, R or T for these infotypes:

IT0003 Payroll status
IT0014 Recur. Payments/Deds.
IT0002 Personal Data
IT0100 Social Insurance B
IT0022 Education
IT0021 Family/Related Person
IT0101 Fiscal Data B
IT0023 Other/Previous Employers
IT2001 Absences
IT0001 Organizational Assignment

75

76 of 121

Excercise:�Infotype configuration

For infotype 0032 we want to setup the following properties:

Only one record or no record at the same time
The field car regulation is payroll relevant when we modify it
When displaying an overview only show the selected period

76

77 of 121

Agenda

7

PA as ‘Consultant’ (Master Data Customizing)

1

Overview Personnel Administration (PA)

2

PA as ‘End User’ (Data maintenance)

Infotypes and subtypes

3

Time constraints and validity periods

4

5

Data maintenance procedures and actions

6

General concepts

IMG <> Table maintenance

8

Customizing tables

9

10

Infotypes structure and attributes

11

Personnel actions

12

Dynamic actions, features and user exits

13

Legacy System Migration Workbench

77

78 of 121

Master Data processes

Personnel actions

The personnel actions function

groups all of the infotypes together

that must be maintained when a particular human resource process is performed

Organizational

Reassignment

Re-entry into

company

Retirement

Early

Retirement

Leaving

Family event

Hiring

Career

Interruption

Scenario's

78

79 of 121

Personnel actions

Transaction code: PA40

= for each event (hiring, change of salary, bird of child, etc…) the user get a sequence of relevant infotypes

79

80 of 121

Personnel actions:�IMG

80

81 of 121

Personnel actions:�Table maintenance�and feature IGMOD

Transaction code: SM31 Transaction code: PE03

Table

T588C

T588D

T529A

T530

T588B

IGMOD

Feature

81

82 of 121

Personnel actions:�Define infogroups

User group dependency on menus and info groups

Here you can define if an infogroup is usergroup dependent

=> parameter ‘UGR’ in System/User profile/Own Data/Parameters.

V_T588C Menutype G = Infogroup

82

83 of 121

Personnel actions:�Define infogroups

Infogroup

Here we define the sequence of infotypes (and subtypes) for an infogroup.

Table V_T588D

83

84 of 121

Personnel actions:�Define infogroups

Infogroup

COP Copy

For other actions than first registration.

If at Copy the infotype does not exist it becomes create.

DEL Delete

Delete Infotypes

INS Create

For first registration.

At Create the system will check if an infotype with the same subtype exist. If so, INS becomes MOD

LIS9 Delimit

Infotypes delimit (at leaving).

Never use LIS9 for IT0000 and IT0001! These 2 infotypes have to stay with endda = 31.12.9999 even for employees who are leaving.

MOD Change

To change existing infotypes

INSS Create (no MOD)

Create even if an infotype exists.

No switch to MOD if the same infotype exist.

Possible operations

84

85 of 121

Personnel actions:�Define infogroups

Infogroup modificator

Feature IGMOD

85

86 of 121

Personnel actions:�Define infogroups

Infogroup modificator

Feature IGMOD

86

87 of 121

Personnel actions:�Define types of actions

Sequences of infotypes linked to an action (MASSN)

87

88 of 121

Personnel actions:�Define types of actions

Sequences of infotypes linked to an action (MASSN)

88

89 of 121

Personnel actions:�Define types of actions

TABEL T529A

Type of procedure (MASSN) = 01
Description procedure = Hiring
Function char for action = 1

1 First hiring; 7 Transfer from recruitment; 0 Other

Status clientspec. = blank

Sequences of infotypes linked to an action (MASSN)

89

90 of 121

Personnel actions:�Define types of actions

Employment Status = 3
Status special payment = blank
Feature for action sequence = blank

MSN20 leave; MSN21 rehiring; ...

Infogroup
Date control

Sequences of infotypes linked to an action (MASSN)

90

91 of 121

Personnel actions:�Change action menu

Here you define which procedure

must be displayed an in which sequence

91

92 of 121

Exercise: Personnel actions

Create a new procedure ‘EXTERNAL EMPLOYEE XX’

Use procedure ZA to ZZ

Include Infotype 0001 and Infotype 0002

Use infogroup ZA to ZZ

Include this in transaction PA40

Use action menu ’01’, reference usergroup ’00’ and line number XX

92

93 of 121

Agenda

7

PA as ‘Consultant’ (Master Data Customizing)

1

Overview Personnel Administration (PA)

2

PA as ‘End User’ (Data maintenance)

Infotypes and subtypes

3

Time constraints and validity periods

4

5

Data maintenance procedures and actions

6

General concepts

IMG <> Table maintenance

8

Customizing tables

9

10

Infotypes structure and attributes

11

Personnel actions

12

Dynamic actions, features and user exits

13

Legacy System Migration Workbench

93

94 of 121

Master Data processes:�Dynamic actions (1)

Dynamic actions

If the maintenance of an infotype has an impact on a second one,

the system will automatically propose you, just after,

another screen to maintain the second infotype.

In certain cases, this operation will be executed in background. (invisible for the user)

94

95 of 121

Master Data processes:�Dynamic actions (2)

Dynamic actions are performed automatically by the system, depending on certain conditions

95

96 of 121

Master Data processes:�Dynamic actions (3)

96

97 of 121

Master Data customizing:�Dynamic actions (1)

Table maintenance Transaction code: SM31

Dynamic actions

Table

T588Z

97

98 of 121

Master Data customizing:�Dynamic actions (2)

Example

98

99 of 121

Master Data customizing:�Dynamic actions (3)

Description of the different columns

1	Itype	Mandatory infotype from which the dynamic measure is activated
2	STy	Optional subtype from which the dynamic measure is activated
3	Field n	Optional field name from which the dynamic measure is activated
4	FC	Mandatory function applied on infotype from which the dynamic measure is activated
5	No	Sequential number permitting to read the data in a certain order
6	S	Optional step indicator
7	Variable function part	Mandatory command field

99

100 of 121

Master Data customizing:�Dynamic actions (4)

Description of the possible steps

P	Plausibility check : With this action you check certain conditions (for example, comparing the old and the new value).
I	Call infotype. With this action you call an infotype for further processing
W	Enter values : With this action you enter values for a new data record
V	Link to another action : With this action you group together fields for which you want the system to perform the same action
F	Call routine : With this action you call an internal or external form routine
M	Send mail : With this action you send an e-mail by entering a suitable feature
	Comment

100

101 of 121

Exercise: Dynamic actions

Which dynamic action is executed when you create (or copy) a record of IT 0016 with a probation period?

On which lines can you find the code in table T588Z?

Explain what the code does.

101

102 of 121

Master Data customizing: Features (1)

©

SAP AG 2002

Sub

-

objects

Feature

ABKRS

Payroll area

Decision tree

Attributes

Documentation

Display

Change

ABKRS

Payroll area

MOLGA

Country grouping

01

Germany

PERSG

5

4

02

Switzerland

10

USA

Employee group

3

5

02

5

otherwise

PERSK

Employee subgroup

5

01

Hourly wage earners

5

Via transaction PE03 or IMG

5

4

5

Default Payroll Area

Features: Initial Screen

Edit ABKRS Feature: Decision Tree

Active

102

103 of 121

Master Data customizing: Features (2)

©

SAP AG 2003

Sub

-

objects

Feature

ABKRS

ABKRS Default values for

Payroll area

Create

Decision tree

Attributes

Documentation

Display

Change

Features: Initial Screen (Transaction PE03)

Information on the structure

and the functions

Administration data of a

feature, including the

structure (fields that can

be queried in the

decision tree

)

and country assignment

Query data structure to

determine

return values.

You can maintain them

using

●

Table maintenance

or

●

Tree maintenance

103

104 of 121

Master Data customizing:�Features (3)

Two different views to maintain features:

Transaction code: PE03

Tree maintenance

Table maintenance

104

105 of 121

Features ABKRS

105

106 of 121

Feature PINCH

106

107 of 121

Feature NUMKR

©

SAP AG 2003

Feature NUMKR

Intervals

No.

From number

01

02

00000001

90000001

To number

90000000

99999999

Current number

4711

Ext

X

Decision tree

External number

assignment

Internal number

assignment

107

108 of 121

Exercise:�Defaulting via features

What is the function of feature ABKRS ?
What is the function of feature CONTR ?

108

109 of 121

User exits

Process before output

Defaulting
Messages

Process after input

Verification of entered data: messages, corrections
Defaulting

109

110 of 121

Overview�Transactions

Transactions

PA10: Personnel file
PA20: Display data
PA30: Maintain data
PA40: Personnel actions
PA70: Fast entry data
PE03: HR: Features
SE11: ABAP Dictionary
SM31: SAP Customizing Implementation Guide
SPRO: Implementation Guide
…

110

111 of 121

Agenda

7

PA as ‘Consultant’ (Master Data Customizing)

1

Overview Personnel Administration (PA)

2

PA as ‘End User’ (Data maintenance)

Infotypes and subtypes

3

Time constraints and validity periods

4

5

Data maintenance procedures and actions

6

General concepts

IMG <> Table maintenance

8

Customizing tables

9

10

Infotypes structure and attributes

11

Personnel actions

12

Dynamic actions, features and user exits

13

Legacy System Migration Workbench

111

112 of 121

LSMW (1) – Legacy System Migration Workbench

112

113 of 121

LSMW (2) – Maintain Object Attributes

113

114 of 121

LSMW (3) – Create Recording

114

115 of 121

LSMW (4) – Maintain Source Structures + Source Fields + Structure Relationships

115

116 of 121

LSMW (5) – Maintain Field Mapping and Conversion Rules

+ Maintain Fixed Values, Translations, User-Defined Routines

116

117 of 121

LSMW (6) – Specify Files

117

118 of 121

LSMW (7) – Read Data + Convert Data

+ Display Read Data

+ Display Converted Data

118

119 of 121

LSMW (8) – Create + Run Batch Input Session

119

120 of 121

Exercise: LSMW

Create an LSMW for IT 0023 (Other / Previous Employers)

Create the LSMW object IT0023_XX under Project AR_TR, Subproject AR_TR_PA.
Configure this LSMW project. Look at the previous slides for guidance. Try to create a recording IT0023_XX for transaction PA30 (or simply copy the existing recording IT0023).
Adapt the file IT0023_UPLOAD.txt for your personnel number(s). Enter multiple previous employers.
Import and convert your data, create and run a batch input session
Check IT 0023 for your employee(s)

120

121 of 121

Thank you for your attention

and

Enjoy working for ARINSO ! !

121