sap hr personnel administration training overview
DESCRIPTION
SAP HRTRANSCRIPT
Personnel Administration
Brussels
2Agenda
7777 PA as ‘Consultant’ (Master Data Customizing)
1111 Overview Personnel Administration (PA)
2222 PA as ‘End User’ (Data maintenance)
Infotypes and subtypes
3333
Time constraints and validity periods
4444
5555
Data maintenance procedures and actions6666
General concepts
IMG <> Table maintenance8888
Customizing tables9999
10101010 Infotypes structure and attributes
11111111 Personnel actions
12121212 Dynamic actions, features and user exits
13131313 Legacy System Migration Workbench
3Course 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 Resourcessuch as Personnel Administration
Maintain employee data Execute Personnel Actions
4
OverviewPersonnel Administration (1)
OrganizationManagement
Payroll &Accounting
Compensationmanagement Training & Event
Management
Recruitment
PerformanceManagement Personal
Development
PersonnelManagement
Time Management
5
OverviewPersonnel Administration (2)
OrganizationManagement
Payroll &Accounting
Compensationmanagement Training & Event
Management
Recruitment
PerformanceManagement Personal
Development
PersonnelManagement
Time Management
6Company structure management
12Générale
de Banque
13G-Fonds
14Cie belge
Fin. Indust.
15Bq belge
pr étranger
16Coperfort
GBZBZone Bxl
GBZNZone nord
GBZSZone sud
GBECEnt Centr
GFON GCOPGBFI GBET
BXLGGénéral
NRDGGénéral
SUDGGénéral
Company code
Personnel Area
Personnel Subarea
NRDFAg. Franco
BXLPPériphérie
SUDOSO ex.Mons
SUDECantons Est
Enterprise StructureEnterprise StructureEnterprise StructureEnterprise Structure
Personnel StructurePersonnel StructurePersonnel StructurePersonnel Structure
O
O O
O O
S
S
S
S
C
C
Position
Job
P Employee
ExternalExternalExternalExternal
Contractors
RetireeRetireeRetireeRetiree
ActiveActiveActiveActive
Hourly WorkerMonthly workerExecutiveManagerSenior ManagerStudent
ExpatriateExpatriateExpatriateExpatriate
InactiveInactiveInactiveInactive
Organizational StructureOrganizational StructureOrganizational StructureOrganizational Structure
Hourly WorkerMonthly workerExecutiveManagerSenior ManagerStudent
ExecutiveManagerSenior Manager
Hourly WorkerMonthly workerExecutiveManagerSenior ManagerStudent
Organizational Unit
7Transaction 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 developmenttransaction codes lead to the different activities:
SPRO: Implementation guide SE11: ABAP dictionary SE38: ABAP development SM30: table maintenance ...
/O/O to create new session
/N/N to erase old session
8Transaction 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
9Agenda
7777 PA as ‘Consultant’ (Master Data Customizing)
1111 Overview Personnel Administration (PA)
2222 PA as ‘End User’ (Data maintenance)
Infotypes and subtypes
3333
Time constraints and validity periods
4444
5555
Data maintenance procedures and actions6666
General concepts
IMG <> Table maintenance8888
Customizing tables9999
10101010 Infotypes structure and attributes
11111111 Personnel actions
12121212 Dynamic actions, features and user exits
13131313 Legacy System Migration Workbench
10Concept - 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.
11
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
12Data 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
13Concept - Personnel number
WHO?
14Agenda
7777 PA as ‘Consultant’ (Master Data Customizing)
1111 Overview Personnel Administration (PA)
2222 PA as ‘End User’ (Data maintenance)
Infotypes and subtypes
3333
Time constraints and validity periods
4444
5555
Data maintenance procedures and actions6666
General concepts
IMG <> Table maintenance8888
Customizing tables9999
10101010 Infotypes structure and attributes
11111111 Personnel actions
12121212 Dynamic actions, features and user exits
13131313 Legacy System Migration Workbench
15
IT000IT00099
Fiscal Data
DEUTSCHEMARK
DEUTSCHEMARK x x x x x x x x x x
xx x x x x x x x x x x
cheque
Family & related person
Addresses
Bank DetailsOrganizational Assignment
Tax OfficePersonal Data
Planned working timePerson X
Birthcertificate
IT0001IT0001
IT0021IT0021
IT0006IT0006
IT010IT01011
IT0002IT0002
IT0007IT0007
One subject per screen
Infotype
WHAT?
16Subtype
1111
2222
Infotype 0021
FamilyFamily
Subtype 2
Subtype 1
SpouseSpouse
ChildrenChildren
One subject per screen
17Object ID
1111
2222
1111
2222Infotype 0021
FamilyFamily
Subtype 2
Subtype 1
nr 02
nr 01SpouseSpouse
ChildrenChildren
One subject per screen
18
Title
Header
Validity period
Infotype
content
Each infotype has these screen parts
Screen parts
19Maintain infotypes
New recordsChanging
existing records
20
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
Infotypes:Common <> country specific
21Excercise: 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
22Agenda
7777 PA as ‘Consultant’ (Master Data Customizing)
1111 Overview Personnel Administration (PA)
2222 PA as ‘End User’ (Data maintenance)
Infotypes and subtypes
3333
Time constraints and validity periods
4444
5555
Data maintenance procedures and actions6666
General concepts
IMG <> Table maintenance8888
Customizing tables9999
10101010 Infotypes structure and attributes
11111111 Personnel actions
12121212 Dynamic actions, features and user exits
13131313 Legacy System Migration Workbench
23Validity period
Each screen has a validity period
The validity period indicates
when the infotype content is valid
WHEN?
24
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
25
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
26
Validity period + Time constraints
=
Data historic
Data historic
01/05/2000 01/11/2000 31/12/9999
Create
$ 5000
$ 5500
$ 5500$ 5000 $ 5500
27Example
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 Brussel
Nr. 34
Leuven
01.08.2004 – 31.12.9999
Nr. 20
Brussel
01.05.2004 – 31.07.2004
28Excercise: 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?
29Agenda
7777 PA as ‘Consultant’ (Master Data Customizing)
1111 Overview Personnel Administration (PA)
2222 PA as ‘End User’ (Data maintenance)
Infotypes and subtypes
3333
Time constraints and validity periods
4444
5555
Data maintenance procedures and actions6666
General concepts
IMG <> Table maintenance8888
Customizing tables9999
10101010 Infotypes structure and attributes
11111111 Personnel actions
12121212 Dynamic actions, features and user exits
13131313 Legacy System Migration Workbench
30Infotype Screens
Change Organizational Assignment
Org Structure
Create Personal Data
Org StructureCreate Bank Details
Org StructureCreate Addresses
Org StructureCreate Planned Working Time
Org StructureCreate Actions
Org Structure
Recur. Payments/ DedAdditional PaymentsFiscal Data DChild Allowance D
with proposal
Fast Entry
Fast Entry1 InfotypeMultiple PersonnelNumbers
Fast Entry1 InfotypeMultiple PersonnelNumbers
Single Screen1 Infotype1 Personnel number
Single Screen1 Infotype1 Personnel number
Personnel ActionsSequence of Infotypes1 Personnel number
Personnel ActionsSequence of Infotypes1 Personnel number
31
Organizational
ReassignmentRe-entry into
company
Retirement
EarlyRetirement
Leaving
Family event
Hiring
CareerInterruption
Scenario's
Infotype access through actions
Data maintenance:Predefined HR scenario’s
32Personnel 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
33Personnel Actions (2)
Data maintenance for predefined HR scenario’s by means of actions
34Personnel Actions (3)
35Hiring 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
36
Additionalauthorizationcheck
Determineswhenpayroll is run
Determines the
administratorsresponsible
Infotype 0001
37Payroll Area (1)
SAP AG 2003
Payroll Organization
Run payroll for previous Run payroll for previous monthmonth on 10th of the monthon 10th of the month
Run payroll for current Run payroll for current month on 28th of the monthmonth on 28th of the month
Jan.Jan. 11 Feb. 1Feb. 1 Jan. 1Jan. 1
Payroll area YYPayroll area XX
Feb. 1Feb. 1
38Payroll Area (2)
SAP AG 2003
Payroll Control Record
Simulation
Payroll areaPayroll area XX Salaried employeesXX 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 ofPayroll
Payroll
Release payroll
Start Payroll
Check Results
Corrections
Exit Payroll
International
Payroll
39Payroll Area (3)
SAP AG 2003
Overview: Payroll Organization
Periodparameter
Datemodifierand
Payrollperiods
Calendar forcumulations
Control record
Assigned to thepayroll area
Exists for eachpayroll area
For each combinationof period parameter
Datemodifierand
Monthly orweekly?
Additionaldate types
Which payrollyear, start and end
of periods
Cumulationsofwage types for
reporting purposes
Controls the individualpayroll phases
40Organizational Key
SAP AG 2003
Personnel subarea 1000
Organizational key10001300
Organizational key10001200
Personnel subarea 1000
Cost center 1300
Cost center 1200
41Administrator (1)
SAP AG 2002
Administrators
Time Recording Administrator: Error lists in
Time Management
Automatic mailif changes are made to
infotypes
Reporting/Evaluations
Payroll Administrator: Contact person on remuneration
statementsAuthorization
checks
Personnel Administrator:Monitoring of Tasks
42Administrator (2)
SAP AG 2002
Administrator Assignment
Group Admin. Name of administrator F. of addr. Tel.no. SAP Name
0001
0001
0001
0001
0001
001
002
003
CA
NDP
Joanne Henderson
Edward Carter
Robert Bell
Chris Appleman
Nicola Davenport
Ms
Mr
Mr
Ms
Ms
4711
5541
1239
6665
9848
HENDERSONJ
CARTER
BELLR
APPLEMAN
DAVENPORTN
Org. Assignment (0001)
Administrator, Group, HR, Time Rec., Payroll
View: Change Administrator
43Excercise: 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
44Agenda
7777 PA as ‘Consultant’ (Master Data Customizing)
1111 Overview Personnel Administration (PA)
2222 PA as ‘End User’ (Data maintenance)
Infotypes and subtypes
3333
Time constraints and validity periods
4444
5555
Data maintenance procedures and actions6666
General concepts
IMG <> Table maintenance8888
Customizing tables9999
10101010 Infotypes structure and attributes
11111111 Personnel actions
12121212 Dynamic actions, features and user exits
13131313 Legacy System Migration Workbench
45IMG <> Table maintenance
Two different ways:
IMG Table maintenance
Transactionscode
SPRO SM31
46IMG <> 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
47IMG <> Table maintenance
Two different ways:
IMG Table maintenance
Transactionscode
SPRO SM31
48IMG <> 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.
49Agenda
7777 PA as ‘Consultant’ (Master Data Customizing)
1111 Overview Personnel Administration (PA)
2222 PA as ‘End User’ (Data maintenance)
Infotypes and subtypes
3333
Time constraints and validity periods
4444
5555
Data maintenance procedures and actions6666
General concepts
IMG <> Table maintenance8888
Customizing tables9999
10101010 Infotypes structure and attributes
11111111 Personnel actions
12121212 Dynamic actions, features and user exits
13131313 Legacy System Migration Workbench
50
Customizing Tables:Key and functional fields
Transaction code: SM30
SAP AG 2002
Customizing Tables: Key and Function Fields
Pay Scale Groups
Grpg PS group Lv W. Type Start End Amount Curr.
01.01.791 WW 1010 31.12.9999 6.500,00
01.01.922 AT 31.12.9999 7.750,00
3 AT 01.01.79 31.12.9999 4.000,00
Position...
Function fields: White fields give more information on anentry
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.
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.
51
Customizing Tables:Delete and Save
Transaction code: SM30
SAP AG 2002
Customizing Tables: Delete - Save
Change View "Pay Scale Groups": OverviewChange View "Pay Scale Groups": OverviewSystemEdit Goto HelpObject Utilities
Pay scale typePay scale area
Grpg PS group Lv W. Type Start End Amount
01.01.7901.01.7911 WWWW 10101010 31.12.999931.12.9999 6.500,006.500,00
01.01.922 AT 31.12.9999 7.750,00
3 G01A 01.01.79 31.12.9999 4.000,00
Save:All changes made to the entries must be saved
Exp. <-> Coll. New entries Delimit
Delete:Select one or more entries andchoose "Delete".
SAP AG 2002
Customizing Tables: Delete - Save
Change View "Pay Scale Groups": OverviewChange View "Pay Scale Groups": OverviewSystemEdit Goto HelpObject Utilities
Pay scale typePay scale area
Grpg PS group Lv W. Type Start End Amount
01.01.7901.01.7911 WWWW 10101010 31.12.999931.12.9999 6.500,006.500,00
01.01.922 AT 31.12.9999 7.750,00
3 G01A 01.01.79 31.12.9999 4.000,00
Save:All changes made to the entries must be saved
Exp. <-> Coll. New entries Delimit
Delete:Select one or more entries andchoose "Delete".
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
52
Customizing Tables:Create and Copy
Transaction code: SM30
SAP AG 2002
Customizing Tables: Create - Copy
Change View "Pay Scale Groups": OverviewChange View "Pay Scale Groups": OverviewSystemEdit Goto HelpObject Utilities
Var. List
Pay scale typePay scale area
Grpg PS group Lv W. Type Start End Amount Curr.
01.01.7901.01.7911 WWWW 10101010 31.12.999931.12.9999 6.500,006.500,00
01.01.922 AT 31.12.9999 7.750,00
3 G01A 01.01.79 31.12.9999 4.000,00
Create: You receive an empty input screen,in which you must enter both the key and the function fields.
Exp. <-> Coll. New entries Delimit
Copy:Select an entry that is similar to the entry youwant to create and overwrite at least one keyfield and possibly the function fields on the subsequent screen
SAP AG 2002
Customizing Tables: Create - Copy
Change View "Pay Scale Groups": OverviewChange View "Pay Scale Groups": OverviewSystemEdit Goto HelpObject Utilities
Var. List
Pay scale typePay scale area
Grpg PS group Lv W. Type Start End Amount Curr.
01.01.7901.01.7911 WWWW 10101010 31.12.999931.12.9999 6.500,006.500,00
01.01.922 AT 31.12.9999 7.750,00
3 G01A 01.01.79 31.12.9999 4.000,00
Create: You receive an empty input screen,in which you must enter both the key and the function fields.
Exp. <-> Coll. New entries Delimit
Copy:Select an entry that is similar to the entry youwant to create and overwrite at least one keyfield and possibly the function fields on the subsequent screen
New EntriesThe system displays an empty input screen and you must enter key and function fields.
CopySelect an entry that you want to copy and overwrite the entries in the key and, if
necessary, the function fields on the subsequent screen
53
Customizing Tables:Delimit
Transaction code: SM30
SAP AG 2003
Change View "Pay Scale Groups": OverviewChange View "Pay Scale Groups": OverviewSystemEdit Goto HelpObject Utilities
Grpg PS group Lv. WT Start dateEnd date Amount Curr.
01.01.7901.01.7911 WWWW 10101010 31.12.999931.12.9999 6.500,006.500,00
01.01.922 AT 31.12.9999 7.750,00
3 AT 01.01.79 31.12.9999 4.000,00
Validity Limit: EntryValidity 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 newrecord, and you can overwrite the functionfields.In time-dependent tables, the systemdisplays the record currently valid.Use the Expand-Collapse function to display the other records.
54Agenda
7777 PA as ‘Consultant’ (Master Data Customizing)
1111 Overview Personnel Administration (PA)
2222 PA as ‘End User’ (Data maintenance)
Infotypes and subtypes
3333
Time constraints and validity periods
4444
5555
Data maintenance procedures and actions6666
General concepts
IMG <> Table maintenance8888
Customizing tables9999
10101010 Infotypes structure and attributes
11111111 Personnel actions
12121212 Dynamic actions, features and user exits
13131313 Legacy System Migration Workbench
55Infotypes structure (1)
F1
56Infotypes structure (2)
Transaction code: SE11
F1
F9
57
Infotypes attributes:IMG <> Table maintenance
Transaction code: SPRO Transaction code: SM31
Table
T582A
58
I. General attributesII. Display en selectionIII. Retroactive accounting triggerIV. Technical data
Table V_T582A
Infotypes attributes:Overview
59
example: IT0002
Infotypes attributes:Example
60
I. General attributes
Time constraint = A time constraint indicates whether more than one infotype record may be available at one time
Infotypes attributes:General attributes (1)
61
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)
Infotypes attributes:General attributes (2)
62
Time constraint table = when the time constraint is subtype dependent
Infotypes attributes:General attributes (3)
63
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
Infotypes attributes:General attributes (4)
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 infotypeTable 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:General attributes (5)
65
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.
Infotypes attributes:Display and selection (1)
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 begindate is blank (vb. IT0023)
1 record does not exist => entry date = begindaterecord 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)
Infotypes attributes:Display and selection (2)
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 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
Infotypes attributes:Display and selection (3)
68
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
Infotypes attributes:Display and selection (4)
69
III. Retroactive accounting triggerIII. 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).
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 (1)
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 = Infotype is not relevant to retroactive accounting,
R = Change triggers retroactive accounting,
T = Retroactive accounting is field dependent according to T588G.
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.
Infotypes attributes:Retroactive accounting trigger (2)
71
Infotypes attributes:Retroactive accounting trigger (3)
Table V_T588GTable V_T588G
72
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
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
Infotypes attributes:Retroactive accounting trigger (4)
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 = 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.
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.
Infotypes attributes:Retroactive accounting trigger (5)
74
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
Exercise:Time constraints
75
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
Excercise:Payroll relevant infotypes
76
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
Excercise:Infotype configuration
77Agenda
7777 PA as ‘Consultant’ (Master Data Customizing)
1111 Overview Personnel Administration (PA)
2222 PA as ‘End User’ (Data maintenance)
Infotypes and subtypes
3333
Time constraints and validity periods
4444
5555
Data maintenance procedures and actions6666
General concepts
IMG <> Table maintenance8888
Customizing tables9999
10101010 Infotypes structure and attributes
11111111 Personnel actions
12121212 Dynamic actions, features and user exits
13131313 Legacy System Migration Workbench
78Master Data processes
Personnel actionsThe personnel actions functiongroups all of the infotypes togetherthat must be maintained when a particular human resource process is performed
OrganizationalReassignment
Re-entry intocompany
Retirement
EarlyRetirement
Leaving
Family event
Hiring
CareerInterruption
Scenario's
79Personnel actions
Transaction code: PA40 = for each event (hiring, change of salary, bird of child, etc…) the user get a sequence of relevant infotypes
80
Personnel actions:IMG
81
Personnel actions:Table maintenanceand feature IGMOD
Transaction code: SM31 Transaction code: PE03
Table
T588C
T588D
T529A
T530
T588B
IGMOD
Feature
82
User group dependency on menus and info groups
Personnel actions:Define infogroups
Here you can define if an infogroup is usergroup dependent
=> parameter ‘UGR’ in System/User profile/Own Data/Parameters.
V_T588C Menutype G = Infogroup
83
Personnel actions:Define infogroups
Infogroup
Here we define the sequence of infotypes (and subtypes) for an infogroup.
Table V_T588D
84
Infogroup
COP Copy
For other actions than first registration.
If at Copy the infotype does not exist it becomes create.
DEL DeleteDelete 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 infotypesINSS Create (no MOD)
Create even if an infotype exists. No switch to MOD if the same infotype exist.
Personnel actions:Define infogroups
Possible operations
85
Personnel actions:Define infogroups
Infogroup modificator
Feature IGMOD
86
Personnel actions:Define infogroups
Infogroup modificator
Feature IGMOD
87
Sequences of infotypes linked to an action (MASSN)
Personnel actions:Define types of actions
88
Sequences of infotypes linked to an action (MASSN)
Personnel actions:Define types of actions
89
Sequences of infotypes linked to an action (MASSN)
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
90
Sequences of infotypes linked to an action (MASSN)
Employment Status = 3 Status special payment = blank Feature for action sequence = blank
MSN20 leave; MSN21 rehiring; ...
Infogroup Date control
Personnel actions:Define types of actions
91
Here you define which procedure
must be displayed an in which sequence
Personnel actions:Change action menu
92Exercise: 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
93
Agenda
7777 PA as ‘Consultant’ (Master Data Customizing)
1111 Overview Personnel Administration (PA)
2222 PA as ‘End User’ (Data maintenance)
Infotypes and subtypes
3333
Time constraints and validity periods
4444
5555
Data maintenance procedures and actions6666
General concepts
IMG <> Table maintenance8888
Customizing tables9999
10101010 Infotypes structure and attributes
11111111 Personnel actions
12121212 Dynamic actions, features and user exits
13131313 Legacy System Migration Workbench
94
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)
95
Dynamic actions are performed automatically by the system, depending on certain conditions
Master Data processes:Dynamic actions (2)
96
Master Data processes:Dynamic actions (3)
97
Master Data customizing:Dynamic actions (1)
Table maintenance Transaction code: SM31 Dynamic actions
Table
T588Z
98
Master Data customizing:Dynamic actions (2)
Example
99
Master Data customizing:Dynamic actions (3)
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
Description of the different columns
100
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
101Exercise: 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.
102
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
02 Switzerland
10 USA
Employee group
3
02
otherwise
PERSK Employee subgroup
01 Hourly wage earners
Via transaction PE03 or IMG
Default Payroll Area
Features: Initial Screen Edit ABKRS Feature: Decision Tree
Active
103
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 todetermine return values.You can maintain them usingTable maintenance
orTree maintenance
104
Master Data customizing:Features (3)
Two different views to maintain features:
Transaction code: PE03
Tree maintenance
Table maintenance
105Features ABKRS
SAP AG 2003
Maintaining Features (3)
ABKRS ABKRS Payroll area
MOLGA Country grouping
01 Germany
PERSG Employee group
1 Active
PERSK Employee subgroup
DE Trainee - industrial
DF Trainee - commercial
DI Hourly wage earners
20
DN Monthly wage earners
DS Senior staff
DT Non-PS employees
20
DU Salaried employees
Feature Edit Goto Utilities View System Help
Decision operation
Decision field value
Status: active
Return code
Feature ABKRS
106Feature PINCH
SAP AG 2003
2) Default for Administrator Groups
PINCH PINCH Administrator group
TCLAS Transaction class for data storage
B Applicant data
otherwise
APPL
****
Status: active
Group Admin. Name of administrator F. of addr Tel.no. SAP name
00010001000100010001
001002003CANDP
Joanne HendersonEdward Carter Robert Bell Chris ApplemanNicola Davenport
Ms.Mr.Mr.Ms.Ms.
47115541123966659848
HENDERSONJCARTERBELLRAPPLEMANDAVENPORTN
Org. Assignment (0001)
Administratorgroup: personnel,
time, payroll
View: Change Administrator
107Feature NUMKR
SAP AG 2003
Feature NUMKRFeature NUMKR
Intervals
No. From number
0102
0000000190000001
To number
9000000099999999
Current number
4711
Ext
X
Decision tree
External numberassignment
Internal numberassignment
108
Exercise:Defaulting via features
What is the function of feature ABKRS ? What is the function of feature CONTR ?
109User exits
Process before output Defaulting Messages
Process after input Verification of entered data: messages, corrections Defaulting
110
OverviewTransactions
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 …
111Agenda
7777 PA as ‘Consultant’ (Master Data Customizing)
1111 Overview Personnel Administration (PA)
2222 PA as ‘End User’ (Data maintenance)
Infotypes and subtypes
3333
Time constraints and validity periods
4444
5555
Data maintenance procedures and actions6666
General concepts
IMG <> Table maintenance8888
Customizing tables9999
10101010 Infotypes structure and attributes
11111111 Personnel actions
12121212 Dynamic actions, features and user exits
13131313 Legacy System Migration Workbench
112
LSMW (1) – Legacy System Migration Workbench
113
LSMW (2) – Maintain Object Attributes
114LSMW (3) – Create Recording
115
LSMW (4) – Maintain Source Structures + Source Fields + Structure Relationships
116
LSMW (5) – Maintain Field Mapping and Conversion Rules
+ Maintain Fixed Values, Translations, User-Defined Routines
117LSMW (6) – Specify Files
118
LSMW (7) – Read Data + Convert Data
+ Display Read Data
+ Display Converted Data
119
LSMW (8) – Create + Run Batch Input Session
120Exercise: 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)
121
Thank you for your attention and
Enjoy working for ARINSO ! !