Você está na página 1de 121

Personnel Administration

Brussels

Agenda
1

Overview Personnel Administration (PA)


2

PA as End User (Data maintenance)


3 4 5 6 7

General concepts Infotypes and subtypes Time constraints and validity periods Data maintenance procedures and actions

PA as Consultant (Master Data Customizing)


8

IMG <> Table maintenance


9 10

Customizing tables Infotypes structure and attributes

11 12 13

Personnel actions

Dynamic actions, features and user exits

Legacy System Migration Workbench

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

Overview Personnel Administration (1)

Personnel Management

Recruitment

Payroll & Accounting

Compensation management

Organization Management

Training & Event Management

Performance Management

Time Management
Personal Development

Overview Personnel Administration (2)

Personnel Management

Recruitment

Payroll & Accounting

Compensation management

Organization Management

Training & Event Management

Performance Management

Time Management
Personal Development

Company structure management


Organizational Unit

O O O S O O S

Organizational Structure
Position

Job

Personnel Structure
Contractors Hourly Worker Monthly worker Executive Manager Senior Manager Retiree Student

S S

C P
Employee

External

Enterprise Structure
Company code
12 Gnrale de Banque GBEC GBZS SUDG
Gnral

Active

Hourly Worker Monthly worker Executive Manager Senior Manager Student

Executive Manager Senior Manager

13 14 15 16 G-Fonds Cie belge Bq belge Coperfort Fin. Indust. pr tranger

Expatriate

GBZN GBZB NRDG


Gnral

Ent Centr Zone sudZone nordZone Bxl

GFON

GBFI

GBET

GCOP

BXLG
Gnral

Personnel Area

Hourly Worker Monthly worker Inactive Executive Manager Senior Manager Student

SUDO

NRDF

BXLP

SO ex.Mons Ag. Franco Priphrie

SUDE
Cantons Est

Personnel Subarea

Transaction code (1)

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

PA10: PA20: PA30: PA40: PA70: ...

personnel file display data maintain data maintain actions fast entry

/O to create new session

Also in customising and development /N to erase old session transaction codes lead to the different activities: SPRO: Implementation guide SE11: ABAP dictionary SE38: ABAP development SM30: table maintenance ...

Transaction code (2)

How to find ?
Whats 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

Agenda
1

Overview Personnel Administration (PA)


2

PA as End User (Data maintenance)


3 4 5 6 7

General concepts Infotypes and subtypes Time constraints and validity periods Data maintenance procedures and actions

PA as Consultant (Master Data Customizing)


8

IMG <> Table maintenance


9 10

Customizing tables Infotypes structure and attributes

11 12 13

Personnel actions

Dynamic actions, features and user exits

Legacy System Migration Workbench

Concept - End user

10

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.

Concept Personnel Administration

11

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

Data maintenance Who?

12

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

Concept - Personnel number

13

WHO?

Agenda
1

14

Overview Personnel Administration (PA)


2

PA as End User (Data maintenance)


3 4 5 6 7

General concepts Infotypes and subtypes Time constraints and validity periods Data maintenance procedures and actions

PA as Consultant (Master Data Customizing)


8

IMG <> Table maintenance


9 10

Customizing tables Infotypes structure and attributes

11 12 13

Personnel actions

Dynamic actions, features and user exits

Legacy System Migration Workbench

Infotype

15

One subject per screen IT0021

WHAT?

IT0009 IT0001
DEUTSCHE MARK DEUTSCHE MARK

xxxxxxx xxxx

cheque

Organizational Assignment Family & related person

Bank Details

IT0007 IT0006
Addresses

Person X

Planned working time

IT0101
Tax Office

IT0002
Personal Data

Birth certificate

Fiscal Data

Subtype

16

Infotype 0021 Family

One subject per screen

2 1
Subtype 2 Children

Subtype 1 Spouse

Object ID

17

One subject per screen 2


Infotype 0021 Family

Subtype 2 Children

nr 02

Subtype 1 Spouse

nr 01

Screen parts

18

Title Header Validity period Infotype content


Each infotype has these screen parts

Maintain infotypes

19

New records

Changing existing records

Infotypes: Common <> country specific


SAP Standard Local

20

SAP Standard Common

l Actions (IT0000)

l Family Allowance A (IT0043) l Organizational Assignment (IT0001) l Company Pension Fund CH (IT0046)
l Personal Data (IT0002) l Addresses (IT0006) l Planned Working Time (IT0007) l Basic Pay (IT0008) l Date Specifications (IT0041) l Tax Data GB (IT0065) l Social Insurance B (IT0100) l Fiscal Data B (IT0101) l Code INSEE F (IT0217) l CBS NL (IT0408)

Excercise: infotypes

21

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

Agenda
1

22

Overview Personnel Administration (PA)


2

PA as End User (Data maintenance)


3 4 5 6 7

General concepts Infotypes and subtypes Time constraints and validity periods Data maintenance procedures and actions

PA as Consultant (Master Data Customizing)


8

IMG <> Table maintenance


9 10

Customizing tables Infotypes structure and attributes

11 12 13

Personnel actions

Dynamic actions, features and user exits

Legacy System Migration Workbench

Validity period

23

Each screen has a validity period

WHEN?

The validity period indicates when the infotype content is valid

Concept: Time constraints (1)


determine how many times a certain screen must and can exist

24

defined at the level of:


the infotype or the subtype

Concept: Time constraints (2)


4 options : 1 : obligatory, no gaps, no overlappings
Personal data, official address

25

2 : optional, gaps, no overlappings

Spouse, company car

3 : optional, gaps, overlappings


Education, former employer

4 : per subtype
Addresses infotype

Data historic

26

Validity period + Time constraints

=
Data historic

01/05/2000

01/11/2000

31/12/9999

$ 5000

Create

$ 5500

$ 5000

5500 $$ 5500

Example
Official address Infotype 0006

27

Hiring

01.05.2004
01.05.2004 31.12.9999

04.06.2004 Wrong number


01.05.2004 31.12.9999

01.08.2004 Moving
01.05.2004 31.07.2004 01.08.2004 31.12.9999

31.12.9999

Nr. 12 Brussel

Nr. 20 Brussel

Nr. 20 Brussel

Nr. 34 Leuven

Excercise: time contraints

28

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?

Agenda
1

29

Overview Personnel Administration (PA)


2

PA as End User (Data maintenance)


3 4 5 6 7

General concepts Infotypes and subtypes Time constraints and validity periods Data maintenance procedures and actions

PA as Consultant (Master Data Customizing)


8

IMG <> Table maintenance


9 10

Customizing tables Infotypes structure and attributes

11 12 13

Personnel actions

Dynamic actions, features and user exits

Legacy System Migration Workbench

Infotype Screens

30

Change Organizational Assignment


Org Structure

Fast Entry
with proposal Recur. Payments/ Ded Additional Payments Fiscal Data D Child Allowance D

Single SingleScreen Screen


11Infotype Infotype 11Personnel Personnelnumber number
Create Personal Data Create Bank Details Org Structure
OrgAddresses Structure Create

Fast FastEntry Entry


11Infotype Infotype Multiple MultiplePersonnel Personnel Numbers Numbers

Create Working Time OrgPlanned Structure Create Org Actions Structure


Org Structure

Personnel PersonnelActions Actions


Sequence Sequenceof ofInfotypes Infotypes 11Personnel number Personnel number

Data maintenance: Predefined HR scenarios

31

Infotype access through actions

Hiring

Leaving

Career Interruption

Re-entry into company

Scenario's

Organizational Reassignment

Retirement

Family event

Early Retirement

Personnel Actions (1)


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

32

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

Personnel Actions (2)

33

Data maintenance for predefined HR scenarios by means of actions

Personnel Actions (3)

34

Hiring procedure
Personnel Actions Create action (Infotype 0000) Organizational Assignment
(Infotype 0001)

35

Addresses
(Infotype 0006)

Planned Working time


(Infotype 0007)

Date monitoring (expiry of contract)*


(Infotype 0019)

Basic Pay
(Infotype 0008)

Date monitoring (expiry of probation)*


(Infotype 0019)

Contracts
(Infotype 0016)

Personal Data
(Infotype 0002)

Country specific infotypes Family/Related Person (child)*


(Infotype 0021 subtype 2 )

Dates Specifications Family/Related Person (spouse)*


(Infotype 0021 subtype 1) or (Infotype 0041)

Family/Rel. Person (companion)*


(Infotype 0021 subtype 7)

Infotype 0001

36

Determines when payroll is run

Additional authorization check

Determines the responsible administrators

Payroll Area (1)

37

Payroll Organization

Payroll area XX

Payroll area YY

Jan. 1

Feb. 1

Jan. 1

Feb. 1

Run payroll for current month on 28th of the month


SAP AG 2003

Run payroll for previous month on 10th of the month

Payroll Area (2)

38

Payroll Control Record


Payroll area XX Salaried employees

Payroll International Payroll

Incorrect personnel no. Payroll area Payroll status Released for payroll Released for corrections Exit payroll Check payroll results XX monthly

Simulation Release payroll Start Payroll Check Results Corrections Exit Payroll

The different stages of Payroll


SAP AG 2003

Payroll Area (3)

39

Overview: Payroll Organization

Monthly or weekly?

Additional date types Which payroll year, start and end of periods

Assigned to the payroll area

Period parameter

and

Date modifier

Payroll periods For each combination of period parameter

and

Date modifier Calendar for cumulations

Exists for each payroll area

Control record

Cumulations of wage types for reporting purposes

Controls the individual payroll phases

SAP AG 2003

Organizational Key

40

Organizational key 10001300


Personnel subarea 1000 Cost center 1300

Organizational key 10001200


Personnel subarea 1000 Cost center 1200

SAP AG 2003

Administrator (1)

41

Personnel Administrator: Monitoring of Tasks Payroll Administrator: Contact person on remuneration statements Authorization checks

Administrators
Reporting/ Evaluations Time Recording Administrator: Error lists in Time Management Automatic mail if changes are made to infotypes

SAP AG 2002

Administrator (2)

42

Administrator Assignment

View: Change Administrator


Group 0001 0001 0001 0001 0001 Admin. 001 002 003 CA NDP Name of administrator F. of addr. Joanne Henderson Edward Carter Robert Bell Chris Appleman Nicola Davenport Ms Mr Mr Ms Ms Tel.no. 4711 5541 1239 6665 9848 SAP Name HENDERSONJ CARTER BELLR APPLEMAN DAVENPORTN

Org. Assignment (0001) Administrator, Group, HR, Time Rec., Payroll

SAP AG 2002

Excercise: Personnel action

43

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

Agenda
1

44

Overview Personnel Administration (PA)


2

PA as End User (Data maintenance)


3 4 5 6 7

General concepts Infotypes and subtypes Time constraints and validity periods Data maintenance procedures and actions

PA as Consultant (Master Data Customizing)


8

IMG <> Table maintenance


9 10

Customizing tables Infotypes structure and attributes

11 12 13

Personnel actions

Dynamic actions, features and user exits

Legacy System Migration Workbench

IMG <> Table maintenance Two different ways:


IMG Table maintenance

45

Transactions code

SPRO

SM31

IMG <> Table maintenance IMG

46

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 Define infotype header Infotypes screen control

etc

IMG <> Table maintenance Two different ways:


IMG Table maintenance

47

Transactions code

SPRO

SM31

IMG <> Table maintenance

48

Table maintenance

Transaction code: SM31, SM30

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

Agenda
1

49

Overview Personnel Administration (PA)


2

PA as End User (Data maintenance)


3 4 5 6 7

General concepts Infotypes and subtypes Time constraints and validity periods Data maintenance procedures and actions

PA as Consultant (Master Data Customizing)


8

IMG <> Table maintenance


9 10

Customizing tables Infotypes structure and attributes

11 12 13

Personnel actions

Dynamic actions, features and user exits

Legacy System Migration Workbench

Customizing Tables: Key and functional fields


Customizing Tables: Key and Function Fields

50

Transaction code: SM30

Pay Scale Groups Grpg PS group


1 2 3 WW AT AT

Function fields: White fields give more information on an entry

Lv W. Type Start
1010 01.01.79 01.01.92 01.01.79

End

Amount Curr.

31.12.9999 6.500,00 31.12.9999 7.750,00 31.12.9999 4.000,00

Fields that are gray identify a unique table entry. There is only one table entry with specific key fields. If you overwrite the key field, the system creates a copy of the entry.

Position...

SAP AG 2002

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.

Customizing Tables: Delete and Save


Customizing Tables: Delete - Save
Change View "Pay Scale Groups": Overview Object Edit Goto Utilities System

51

Transaction code: SM30


Save: All changes made to the entries must be saved

Help

Exp. <-> Coll.

New entries

Delimit

Pay scale type Delete: Pay scale area

Select one or more entries and choose "Delete" .

Grpg PS group
1 2 3 WW AT G01A

Lv W. Type Start
1010 01.01.79 01.01.92 01.01.79

End
31.12.9999 31.12.9999

Amount
7.750,00 4.000,00

31.12.9999 6.500,00

SAP AG 2002

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

Customizing Tables: Create and Copy


Customizing Tables: Create code: - Copy Transaction
Change View "Pay Scale Groups": Overview Object Edit Goto Utilities System Help

52

SM30

Exp. <-> Coll.

New entries

Delimit

Var. List

Pay scale type Create: You receive an empty Pay scale area

input screen,in which you must enter both the key and the function fields.

Copy: Select an entry that is similar to the entry you want to create and overwrite at least one key field and possibly the function fields on the subsequent screen

Grpg PS group
1 2 3 WW AT G01A

Lv W. Type Start
1010 01.01.79 01.01.92 01.01.79

End
31.12.9999 31.12.9999

Amount
7.750,00 4.000,00

Curr.

31.12.9999 6.500,00

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

SAP AG 2002

Customizing Tables: Delimit


Transaction code: SM30
Change View "Pay Scale Groups": Overview Object Edit Goto Utilities System

53

Grpg PS group
1 2 3 WW AT AT

Lv. WT
1010

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 Start dateEnd date Amount Curr. fields. 01.01.79 31.12.9999 6.500,00 In timedependent tables, the system displays the record currently valid. 01.01.92 31.12.9999 7.750,00 Use the Expand-Collapse function to 01.01.79 31.12.9999 4.000,00 display the other records.
Help

Validity Limit: Entry


Valid from 01.01.2003

Position...

Entry 1 of 1

SAP AG 2003

Agenda
1

54

Overview Personnel Administration (PA)


2

PA as End User (Data maintenance)


3 4 5 6 7

General concepts Infotypes and subtypes Time constraints and validity periods Data maintenance procedures and actions

PA as Consultant (Master Data Customizing)


8

IMG <> Table maintenance


9 10

Customizing tables Infotypes structure and attributes

11 12 13

Personnel actions

Dynamic actions, features and user exits

Legacy System Migration Workbench

Infotypes structure (1)

55

F1

Infotypes structure (2) Transaction code: SE11

56

F1

F9

Infotypes attributes: IMG <> Table maintenance


Transaction code: SPRO Transaction code: SM31

57

Table T582A

Infotypes attributes: Overview


Table V_T582A

58

I. II. III. IV.

General attributes Display en selection Retroactive accounting trigger Technical data

Infotypes attributes: Example

59

example: IT0002

Infotypes attributes: General attributes (1)


I. General attributes

60

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

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

61

2 => 3 => A =>

Only one record at a time + continuity not obligatory Multiple records possible + continuity not obligatory 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)

Infotypes attributes: General attributes (3)

62

Time constraint table


= when the time constraint is subtype dependent

Infotypes attributes: General attributes (4)

63

Maint. Aft. leave


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.

example IT0006 Addresses => time constraint table V_T591A

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

Infotypes attributes: General attributes (5)

64

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)

Infotypes attributes: Display and selection (1)


II. Display and selection

65

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.

Infotypes attributes: Display and selection (2)

66

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 1 begindate is blank (vb. IT0023) record does not exist record exist (vb. IT0002,IT0027) => entry date = begindate => begindate of existing record

2 3

startdate of actual organizational definition (vb. IT0100, IT0101, IT0105) CPU datum = date of today (vb. IT0017)

Infotypes attributes: Display and selection (3)

67

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 1 no value (vb. IT0023) enddate is 31.12.9999 by default (vb. IT0100,IT0101) enddate by default = date of leaving (vb. IT0007) enddate by default = begindate of actual record

2 3

Infotypes attributes: Display and selection (4)

68

List time per.


= define the period that will be show in the overview
Crossed blank = overview shows all periods from selectionscreen = overview shows all periods without the selectionscreen

Infotypes attributes: Retroactive accounting trigger (1)


III. Retroactive accounting trigger

69

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

Infotypes attributes: Retroactive accounting trigger (2)

70

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 R T

= Infotype is not relevant to retroactive accounting, = Change triggers retroactive accounting, = Retroactive accounting is field dependent according to T588G.

Infotypes attributes: Retroactive accounting trigger (3)

71

Table V_T588G

Infotypes attributes: Retroactive accounting trigger (4)

72

Entry of RA limit time


If checked its possible to make modifactions before the Personal earliest retroactive accounting date .

Retr.acct PDC
Define if the infotype at recalculationis relevant for time management

Infotypes attributes: Retroactive accounting trigger (5)

73

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 message. = Entries which relate to past payroll periods are permitted. The system displays a warning

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.

Exercise: Time constraints


What seems to you the correct time constraint for:

74

IT0000 IT0002 IT0007 IT0037 IT0001 IT0023

procedures Personal Data Planned Working Time Insurance Organizational Assignment Other/Previous Employers

Excercise: Payroll relevant infotypes

75

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


IT0003 IT0014 IT0002 IT0100 IT0022 IT0021 IT0101 IT0023 IT2001 IT0001

Payroll status Recur. Payments/Deds. Personal Data Social Insurance B Education Family/Related Person Fiscal Data B Other/Previous Employers Absences Organizational Assignment

Excercise: Infotype configuration


For infotype 0032 we want to setup the following properties:

76

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

Agenda
1

77

Overview Personnel Administration (PA)


2

PA as End User (Data maintenance)


3 4 5 6 7

General concepts Infotypes and subtypes Time constraints and validity periods Data maintenance procedures and actions

PA as Consultant (Master Data Customizing)


8

IMG <> Table maintenance


9 10

Customizing tables Infotypes structure and attributes

11 12 13

Personnel actions

Dynamic actions, features and user exits

Legacy System Migration Workbench

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

78

Hiring

Leaving

Career Interruption Organizational Reassignment

Re-entry into company

Scenario's
Retirement Family event

Early Retirement

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

Personnel actions: IMG

80

Personnel actions: Table maintenance and feature IGMOD


Transaction code: SM31 Transaction code: PE03

81

Table T588C Feature

IGMOD

T588D
T529A T530

T588B

Personnel actions: Define infogroups


User group dependency on menus and info groups
Here you can define if an infogroup is usergroup dependent

82

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


V_T588C Menutype G = Infogroup

Personnel actions: Define infogroups


Infogroup

83

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

Personnel actions: Define infogroups


Infogroup
Possible operations
COP Copy

84

For other actions than first registration.


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

DEL INS

For first registration.


At Create the system will check if an infotype with the same subtype exist. If so, INS becomes MOD 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. Change To change existing infotypes Create (no MOD) Create even if an infotype exists. No switch to MOD if the same infotype exist.

LIS9

MOD INSS

Personnel actions: Define infogroups


Infogroup modificator

85

Feature IGMOD

Personnel actions: Define infogroups


Infogroup modificator

86

Feature IGMOD

Personnel actions: Define types of actions


Sequences of infotypes linked to an action (MASSN)

87

Personnel actions: Define types of actions


Sequences of infotypes linked to an action (MASSN)

88

Personnel actions: Define types of actions


Sequences of infotypes linked to an action (MASSN)
TABEL T529A Type of procedure (MASSN) Description procedure Function char for action Status clientspec.

89

= 01 = Hiring =1
1 First hiring; 7 Transfer from recruitment; 0 Other

= blank

Personnel actions: Define types of actions


Sequences of infotypes linked to an action (MASSN)

90

Employment Status Status special payment Feature for action sequence


Infogroup Date control

=3 = blank = blank
MSN20 leave; MSN21 rehiring; ...

Personnel actions: Change action menu


Here you define which procedure must be displayed an in which sequence

91

Exercise: Personnel actions


Create a new procedure EXTERNAL EMPLOYEE XX

92

Use procedure ZA to ZZ

Include Infotype 0001 and Infotype 0002

Use infogroup ZA to ZZ
Use action menu 01, reference usergroup 00 and line number XX

Include this in transaction PA40

Agenda
93

Overview Personnel Administration (PA)


2

PA as End User (Data maintenance)


3 4 5 6 7

General concepts Infotypes and subtypes Time constraints and validity periods Data maintenance procedures and actions

PA as Consultant (Master Data Customizing)


8

IMG <> Table maintenance


9 10

Customizing tables Infotypes structure and attributes

11 12 13

Personnel actions

Dynamic actions, features and user exits

Legacy System Migration Workbench

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.

94

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

Master Data processes: Dynamic actions (2)


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

95

Master Data processes: Dynamic actions (3)

96

Master Data customizing: Dynamic actions (1)


Table maintenance

97

Transaction code: SM31

Dynamic actions

Table T588Z

Master Data customizing: Dynamic actions (2)


Example

98

Master Data customizing: Dynamic actions (3)


Description of the different columns
1 Itype Mandatory infotype from which the dynamic measure is activated

99

2
3

STy
Field n

Optional subtype from which the dynamic measure is activated


Optional field name from which the dynamic measure is activated

4
5 6 7

FC
No S

Mandatory function applied on infotype from which the dynamic measure is activated
Sequential number permitting to read the data in a certain order Optional step indicator

Variable Mandatory command field function part

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). Call infotype. With this action you call an infotype for further processing Enter values : With this action you enter values for a new data record Link to another action : With this action you group together fields for which you want the system to perform the same action Call routine : With this action you call an internal or external form routine Send mail : With this action you send an e-mail by entering a suitable feature

100

I W V

F M

Comment

Exercise: Dynamic actions


101

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.

Master Data customizing: Features (1)

102

Via transaction PE03 or IMG

Default Payroll Area

Features: Initial Screen Feature ABKRS Payroll area

Edit ABKRS Feature: Decision Tree


ABKRS Payroll area MOLGA Country grouping Germany Switzerland USA

5
Sub-objects Decision tree Attributes Documentation

4 4 5

01 02 10

PERSG

Employee group
Active 02

5
5
Change

otherwise PERSK Employee subgroup Hourly wage earners

Display

01

SAP AG 2002

Master Data customizing: Features (2)

103

Features: Initial Screen (Transaction PE03) Administration data of a feature, including the structure (fields that can ABKRS Feature ABKRS Default values for be queried in the Payroll area decision tree) and country assignment Create Sub-objects Decision tree Attributes Documentation Display Change Query data structure to determine return values. You can maintain them using l Table maintenance or l Tree maintenance

Information on the structure and the functions


SAP AG 2003

Master Data customizing: Features (3)


Two different views to maintain features:

104

Transaction code: PE03

Features ABKRS
Maintaining Features (3)
Feature ABKRS
Feature Edit Goto Utilities View System Help

105

ABKRS ABKRS

Payroll area Country grouping

Decision operation Decision field value

Status: active

MOLGA

01 Germany

PERSG Employee group

1 Active

PERSK

Employee subgroup

4 4 4 4 4
SAP AG 2003

DE Trainee - industrial DF Trainee - commercial DI Hourly wage earners 20 DN Monthly wage earners DS Senior staff DT Non-PS employees DU Salaried employees 20

Return code

Feature PINCH
2) Default for Administrator Groups
PINCH PINCH TCLAS Administrator group Transaction class for data storage Applicant data APPL Status: active

106

otherwise ****

View: Change Administrator

Group 0001 0001 0001 0001 0001

Admin. 001 002 003 CA NDP

Name of administrator Joanne Henderson Edward Carter Robert Bell Chris Appleman Nicola Davenport

F. of addr Ms. Mr. Mr. Ms. Ms.

Tel.no. 4711 5541 1239 6665 9848

SAP name HENDERSONJ CARTER BELLR APPLEMAN DAVENPORTN

Org. Assignment (0001) Administrator group: personnel, time, payroll


SAP AG 2003

Feature NUMKR

107

External number assignment

Internal number assignment

Decision tree
Intervals

Feature NUMKR

No.
01 02

From number To number


00000001 90000001 90000000 99999999

Current number Ext


4711 X

SAP AG 2003

Exercise: Defaulting via features


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

108

User exits
Process before output Defaulting Messages Process after input Verification of entered data: messages, corrections Defaulting

109

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

Agenda
1

111

Overview Personnel Administration (PA)


2

PA as End User (Data maintenance)


3 4 5 6 7

General concepts Infotypes and subtypes Time constraints and validity periods Data maintenance procedures and actions

PA as Consultant (Master Data Customizing)


8

IMG <> Table maintenance


9 10

Customizing tables Infotypes structure and attributes

11 12 13

Personnel actions

Dynamic actions, features and user exits

Legacy System Migration Workbench

LSMW (1) Legacy System Migration Workbench

112

LSMW (2) Maintain Object Attributes

113

LSMW (3) Create Recording


114

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

115

LSMW (5) Maintain Field Mapping and Conversion Rules

116

+ Maintain Fixed Values, Translations, User-Defined Routines

LSMW (6) Specify Files


117

LSMW (7) Read Data + Convert Data

118

+ Display Read Data

+ Display Converted Data

LSMW (8) Create + Run Batch Input Session

119

Exercise: LSMW
120

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)

121

Thank you for your attention and Enjoy working for ARINSO ! !

Você também pode gostar