Chapter 4 PA Configuration in Less Than 24 Hours

7/26/2019 Chapter 4 PA Configuration in Less Than 24 Hours

1/33

Chapter 4. PA Configuration in Less Than 24Hours

In this chapter, we will explore how Personnel Administration(PA) is configured to meet aclient's requirements. We will see how different infotypes are configured to meet the businessrequirements.

In this chapter, we are going to cover the following topics

!ersonnel "dministration infotypes

Important infotypes and their configuration

#onfiguring the submodule

#onfiguring personnel action

Personnel Administration infotypes

Infotype is a four$digit number, and nnnnis assigned to each infotype. %he number range &, to &,&&&is reserved forcustomer and not standard "!. !ersonnel administration is everything to do with themaster data of an employee. %he details of the employee are captured in infotypes.

%he details of an employee such as personal data, ban details, and address are all captured in infotypes.%he employee details such as which associated department he or she belong to, his or her currentposition, and his or her personal details such as date of birth, residential address, pay details, ban details,and so on, are captured using this submodule.

tandard !" infotypes are in the range of $&&&. *ach number has a name associated with it. +orinstance, is personal data. We will cover all the mandatory infotypes in the following chapters.#ustomer or customi-ed infotypes are in the range of &,$&,&&&. %here are some country$specificinfotypes such as court ordersstudent loans /0 (infotype 1), which is specific to /reat 0ritain.

Important infotypes that are mandatory and theirconfiguration steps

%here are some important infotypes that need to be maintained for processing the payroll and time. %heyare as follows

0000("ctions)

0001(2rgani-ation "ssignment)

0002(!ersonal 3ata)

000("ddress)

000!(!lanned Woring %ime)

000"(0asic !ay)

000#(0an 3etails)

Tip

%he 4 infotype (!ayroll tatus) is created automatically when the hiring action is performed5 we will learnabout this infotype in the following chapters.

Functions of infotypes

6et's quicly cover the functionalities of each infotype in detail.


2/33

The 0000 $Actions% infotype

%he "ctions infotype is an important infotype that captures the activities surrounding an employee from,say, hiring to separation.

When the employee is hired, the action type is 7hire7, and when there is another activity such as promotion

or reassignment that needs to be performed, then again there is a different action type.

*ach action has a start and end date to capture the history of the activities. 6et's say the hire action isperformed on 8anuary 9, 94 (the start date). "nother action is performed, for example, the employee ispromoted on 3ecember 9, 94. In this scenario, there will be two line items to capture the history.

%he "ctions infotype also clearly illustrates the reason for performing a particular action. +or example, hirecan be an action type, and the reason for performing the hiring action could be replacement. %hese fieldsare very useful for reporting and administrative purposes, as demonstrated in the following screenshot

Tip

Important activities such as change of address, addition of a family member, change in ban details, and so on,are not considered as actions but as part of the master data maintenance.

%he "ctions infotype also has an important configurable field that shows the employment status ofan employee with the company. %hey are standard "! values, and each one has a meaning. %hestandard employment statuses are as follows

"ctive

Inactive

:etiree

Withdrawn

Tip

%he status is maintained in the T529Utable, and it can be accessed via SE16or V_T529Uin

the SM30/31%$code, as demonstrated in the following screenshot


3/33

;ultiple actions can be performed in a single day.


4/33

%he important payroll$related control feature, payroll area, is captured in these infotypes. %his helps all theemployees to be grouped together when the payroll is processed. %he master cost center is default in thisinfotype. %his infotype also holds the ey to an organi-ation5 this ey can be used for authori-ationpurposes, if necessary.

The 0002 $Personal (ata% infotype

%he !ersonal 3ata infotype is used to capture an employee's first name, last name, marital status, anddate of birth.

Tip

%he start date of !ersonal 3ata infotype is the birth date. If we note, in this case, the date of birth of theemployee is eptember >, 9&?, and the start date of the employee is eptember >, 9&?.

The 000 $Address% infotype

%he "ddress infotype is used to capture the permanent and temporary addresses of the employee. %headdress entered is also used in the & (0an 3etails) infotype. %his is demonstrated in the followingscreenshot


5/33

The 000! $Planned )or*ing Time% infotype

%he !lanned Woring %ime infotype is used to capture the wor schedule of the employee. @sing thisinfotype, theemployee's stipulated woring time can be captured. %his is a crucial infotype that is useful forpayroll. %he holiday calendar is lined directlyindirectly through this infotype.

%he dailyweely wor pattern is captured in this infotype. We can also get the total amount of wor doneon a daily, weely, and monthly basis through this infotype. %his is customi-ed by navigating to I+,A Time+anagementA )or* -chedule uleA )or* -chedule ules and )or* -chedules. We will cover thisexhaustively in#hapter >, Time Management Configuration Negative Time. %he following screenshotdemonstrates this infotype
https://www.safaribooksonline.com/library/view/sap-hcm/9781782172208/ch05.htmlhttps://www.safaribooksonline.com/library/view/sap-hcm/9781782172208/ch05.htmlhttps://www.safaribooksonline.com/library/view/sap-hcm/9781782172208/ch05.html


6/33

%he wor schedule will give us a detailed planned woring time of the employee. %heemployment percentage is passed on to the 0asic !ay infotype as capacity utili-ation level. %he data flowsfrom the %ime ;anagement submodule to the !ersonnel "dministration submodule when the 0asic !ayinfotype details are maintained in the system, as shown in the following screenshot


7/33

Tip

%he T588Minfotype screen control has the feature of hiding or maintaining the required fields of an infotype. Itcan also be accessed by navigating to -P&A Personnel +anagementA PersonnelAdministrationA Customising user interfacesA Change -creen +odifications.

The 000" $/asic Pay% infotype

%he 0asic !ay infotype is used to capture the fixed pay componentsearnings drawn by the employee. %heemployee industry type and physical location$specific details are captured in the form of payscale type andarea.

%he components captured in the 0asic !ay infotype are referred to as wage types, and we will cover themexhaustively in#hapter ?, Payroll Configuration. +or example, housing allowance and conveyanceallowance are referred to as wage types, and they have a number and text to identify them.

%he integration point between time and payroll is also evident in this infotype. We will see the capacityutili-ation level fed from the value stored in the 1 (!lanned Woring %ime) infotype. %he followingscreenshot shows the 0asic !ay infotype
https://www.safaribooksonline.com/library/view/sap-hcm/9781782172208/ch06.htmlhttps://www.safaribooksonline.com/library/view/sap-hcm/9781782172208/ch06.html


8/33


9/33

%he name of the employee is populated from the (!ersonal 3ata) infotype, and the addresspopulates from the ? ("ddress) infotype. %he standard ban detail types provided by "! are as

follows

;ain ban

2ther ban details

%ravel expenses

%he account number is mandatory if the payment method is ban transfer.

Tip

%he payment is configured normally through the +I#2 module.


10/33

!ersonnel area

!ersonnel subarea

%he company is the client for whom the implementation is done.

%he company code is designed by the +I#2 component, and it actually depends on the legal entities of the

client, or in other words, it has its own profit and loss statement. " different line of business can berepresented as company code in "!. +or example, company "0# can have multiple businesses such asI% services and manufacturing. %hese two are represented by a company code.

%he personnel area can either be designed based on the geographical location or functional location. +orexample, "0# company has its head office in #hicago, @", and its plant in Cew Dor, @". We cancreate two personnel areas.

%he factors that influence the number of personnel areas needed are as follows

"t least one personnel area is needed for each country

%he number of personnel areas needed depends on the reporting requirements

It may depend on the number of plants, the number of states in which the company has offices,and so on

It may depend on the authori-ation needs

It may depend on the business needs in time management, payroll, and in benefits modules

Tip

!ersonnel areas and subareas are four$digit alphanumeric code identifiers with long text.

!ersonnel subareas are a further bifurcation of personnel areas. %he business characteristics are normallystored at the personnel subarea level. We will see groupings done in payroll and time management atpersonnel subareas and employee subgrouping levels.

What makes the personnel structure?

%he following components mae up the personnel structure

*mployee group

*mployee subgroup

!ayroll area

2rgani-ation ey

%he personnel structure can be designed for the purposes of both administrative and organi-ationperspectives.

%he employee group and subgroup define the relationship of the employee with the company. ay, forexample, a full$time employee can be designed as employee group, and the different grades can bedesigned as employee subgroups such as grade ".

%he payroll area allows us to group employees for whom the payroll is processed at the same time and inthe same frequency, for example, monthly, bi$weely, and so on.

2rgani-ation ey is useful for authori-ation purpose, and its is a 9E$digit ey that also defines theenterprise and personnel structure.

%he 2rgani-ational "ssignment infotype (9), as discussed earlier, holds the enterprise and personnelstructure data of an employee, as seen in the following screenshot


11/33

Cow, let's loo at the configuration of enterprise and personnel structure in detail. %he company andcompany code is created by a +I#2 consultant.


12/33

%he next step is the creation of the company code. It can be accessed by navigating to -P&A nterprise-tructureA(efinitionA inancial Accounting 3 dit Copy (elete Chec* Company Code.

%he company code is below the company, and there can be 7C7 number of company codes mapped to acompany, as shown in the following screenshot

When the copy option is chosen, the related tables are automatically filled with entries, so it is advisableand the best practice in order to prevent a 7Co entry in table7 error while performing a configuration. %his isshown in the following screenshot

%here will be many associated tables when an obFect is copied. %he frequent pit falls while configuringcould be 7#ustomi-ing *rror7 or 7Co entry in table7 error messages. Cow, when we clic on copy, it will asus to enter the company code, as shown in the following screenshot

We need to give from the company code say, 9,, and the company code is the one +I consultant

creates which is, &,. %he system throws a warning message5 we need to clic on5esto proceed andconfirm.


13/33

If we wish to allocate the same chart of accounts to the new company that we are defining, then we canclic on5es, or we can clic on 6o, as shown in the following screenshot

"ll the associated tables get copied when the action is performed. %he obFective here is to assign adifferent currency to the target company code we copied. ay, the reference company currency is *uro,while the target company code currency is @3. %he system prompts a message that the copy action hasbeen successfully carried out, as demonstrated in the following screenshot

%he other details about the company code such as the address, phone number, and so on can be enteredby clicing on address (ShiftG F5). %he details that we enter here will be useful for reporting purpose. %he

following screenshot shows the various fields that are to be filled


14/33

We have to define the personnel areas, subareas, employee group, and subgroups to do the assignment.

%he design of enterprise and personnel structure is critical for the successful implementation of the proFectand mapping the client process in "!. %he best practice is to try out multiple designs before the blueprintis submitted to the client for execution.

%he personnel area and subareas are defined by navigating to -P&A nterprise-tructureA (efinitionA Human esource +anagementA Personnel Areas. %his is shown in thefollowing screenshot


15/33

%he personnel area defined can be used for reporting purpose, and they are organi-ed according to theaspects of payroll, time, and personnel. It can be specific either to the geographical location or functionallocation. It is based on the client$business process and setup.

We can copy the entries from the existing "! standard delivered personnel area and rename theseentries to your customer$specific entries, as shown in the following screenshot

#lic on Copy, delete, chec* personnel area, and give the form to the personnel area. 7+rom7 isbasically the "! standard personnel area, while7 %o7 is the customer$specific entry. It is a four$digitalphanumeric code with the text name, as shown in the following screenshot

%he personnel subarea holds the business characteristics. We use it for payroll and time, hence, it's criticalthat we get our design of the personnel area and subareas correct to have a smooth configuration andmapping of the business process in "!.

" personnel area can have 7C7 number of personnel subareas.

%he personnel subarea is defined by navigating to -P&A nterprise -tructureA (efinitionA Humanesource +anagementA Personnel -u7areas. %his is shown in the following screenshot

Tip

%he best practice is to prepare a 8ey (ata -tructure(8(-) in *xcel. #opy and paste it in a table5 it can save alot of time and effort.

#lic on Create Personnel -u7areaand choose the personnel area for which the personnel subareas aremapped. %his is demonstrated in the following screenshot


16/33

When we start defining the employee group and employee subgroups, we are ready with the personnelstructure. %he employee group is defined by navigating to -P&A nterprise-tructureA (efinitionA Human esources +anagementAmployee ,roups. %his is shown in thefollowing screenshot

%he employee group can also be defined directly via the T501table. It is a one$digit alphanumeric code. It

can also be a special character, as shown in the following screenshot

%he employee subgroup is defined by navigating to -P&A nterprise -tructureA (efinitionA Humanesource +anagementA mployee -u7groups.

It's a two$digit alphanumeric code and is mapped to employee group created in the earlier step. It is shownin the following screenshot

%he configuration of enterprise and personnel structure is complete only when the mapping is donebetween company code, personnel area, employee group, and employee subgroups.

%he assignment of company code to the company is done by navigating to -P&A nterprise

-tructureA AssignmentAAssign company code to company. It is demonstrated in the followingscreenshot


17/33

When the employee is hired, the company and the company code, by default, are automatically based onthe mapping or assignment that is done in this step. %his is shown in the following screenshot

%he personnel area is assigned to the company code. %he mapping of the employee group and subgroupis done in the next step, as shown in the following screenshot

%his assignment determines the employee company code mapping that happens through personnel area,as shown in the following screenshot

%he employee group and employee subgroups have an added feature of maintaining the permissibility$per$country grouping. %he standard country (;olga) grouping numbers in "! are, for example, @"$9and /ermany$9. %his is shown in the following screenshot

%he allowed flag serves as an input chec when the employee grouping is mapped to the employee. %heflag denotes that it's permissible for country grouping, while unflag means that it's not permitted.


18/33

Tips and tric*s that 9ill 7e handy 9hileconfiguring the su7module

We will learn the configuration steps for the !" mandatory infotypes. %he first thing that is requiredis customi-ing of a number range. It's an eight$digit numeric code and is created by navigating

to -P&A Personnel +anagementA Personnel AdministrationA /asic -ettingsor directly viathe PA04%$code.

Recommendation on number range assignment

We will now see the recommendation on number assignment. %he following ey ideas need to be adheredto

3uring the hiring process, if the system generates an employee number, then it is called 7internal

number assignment7. %his method is recommended as part of the "! implementation when acompany wants to have uniformity of number assignment with more digits.

" company has a number of third$party systems where employee numbers are maintained and

used in lot of interfaced programs. In such cases, it is important and necessary that we maintainthe same employee numbers in "! as well. In this case, we use the concept of external numberassignment.

In some cases where a company has multiple office locations, we may use external number

assignment for some locations, and we may use internal number assignment for other locations.

"s a !" consultant, you have to discuss the number range and the number of digits to be used

with the client.

%he following screenshot shows the number range assignment

%he 2; and !" number range concepts are the same. We flag whether it's external (manually inputted bythe user) or internal (system generated). %his is shown in the following screenshot

%he feature used for default number ranges is C@;H:. %he return value is the two$digit code that

is maintained in the NRIVtable via the SE16%$code.

Tip

%he number ranges are maintained in the NRIVtable and are accessed via the SE16%$code.

%he RP_PRELobFect name is for !" and RP_PLANis for 2;.


19/33

%he preceding table has the number range code and number range series based on which it getsexecuted when the hiring action is performed for an employee.

Configuring mandatory infotypes

+irst, let's loo at personal data by navigating to -P&A Personnel +anagementA Personal(ataA Personal (ataACreate forms of address. %his is shown in the following screenshot

%he address table T522Galso has the gender category that is configurable. %he standard possible entries

provided are as follows

!ermitted for males only

!ermitted for females only

!ermitted for males and females

%he address table T522Gis shown in the following screenshot

%he marital status of the employee can also be configured by navigating to -P&A Personnel

+anagementA Personal (ataA Personal (ataA Create marital statusor via the V_T502_T%$code, as

shown in the following screenshot

%his table is freely configurable according to the client's requirement, as shown in the following screenshot


20/33

%he "ddresses infotype is accessed by navigating to -P&A Personnel +anagementA Personal(ataA AddressesACreate address types. %he following screenshot demonstrates this

%he ? "ddresses infotype can be used to capture the temporary and permanent addresses of theemployee.

%he subtypes are a further classification of infotype, and in this case, the different address types aremapped as subtypes in "!. %his concept is demonstrated in the following screenshot

%he regions and countries are standard "!$delivered entries, and it is recommended that you retain the

same and not mae any changes. %his is demonstrated in the following screenshot

%he country ey in "ddresses (?) infotype is maintained by navigating to -P&A /asicsettingsA Create countries :countries of 7irth:nationalities. %he country global parameters

table, V_T005, has the standard entries maintained. +or instance, %he @nited tates of "merica is

maintained as ;-.


21/33

6ote

*very employee master data must contain the "ddresses infotype with subtypes and the permanent address.

3uring payroll processing, in the 7preprogram 3;*7 step, the system checs the permanent address of theemployee master data. If the permanent address is not maintained, the preprogram 3;* will generate error

messages.

%he employee mode of payment is captured in the 0an 3etails infotype (&). %he countrywise standard"! entries are as follows

# chec

% ban transfer

#ash

%he payment method is normally configured by an +I consultant and is defaulted using the 6#< feature.%he paymentmethod gets defaulted in &, and the infotype is maintained.

%he standard entry is 7main ban7, and this is configured by navigating to -P&A PersonnelAdministrationAPersonal (ataA /an* (etailsA Create 7an* connection types. %he followingscreenshot demonstrates this


22/33

%he 2rgani-ational "ssignment infotype (9) is an important infotype that holds the ey characteristicsof an employee, such as personnel area, subarea, employee group, and employee subgroup.

%he 2rgani-ational "ssignment infotype is configured by navigating to -P&A Personnel

+anagementA &rgani'ational (ataA (efine employee attri7utesor via the V_503_H%$code.

%he employment status, raining status, and activity status are standard entries, and only if necessary, "!recommends customi-ing them. %his is shown in the following screenshot

%he standard entries in "! are for the status of an activity. %hey are as follows

"ctive employee

:etiree

*arly retiree

2thers

!art$time wor for retirees

%he standard entries in "! for employment status are as follows

Industrial worerhourly paid worer

alaried employee

#ivil servant 2thers

%he control record and payroll area are critical customi-able obFects for payroll and reporting purposes.%he payroll is created for mapping an employee whose payroll is processed in the same frequency and onthe same date, say, monthly or biweely for that matter.

*very payroll area must have a control record. %he control record controls how the payroll is processed.

%hey are configured by navigating to -P&A Personnel AdministrationA &rgani'ational

(ataA &rgani'ational AssignmentA Create payroll areaor via the V_T549A%$code. %he following

screenshot shows this

We can group the employees together and map them to a payroll area so that it is easy to process for agroup of employees in one shot.


23/33

%he control record determines the current period for which the payroll is processed. It also determines thepayroll period past date, up to which the system allows you to mae changes to the master and time dataand is called as :etro in "!.

%here are multiple statuses in control record such as 7released7 for payroll, which means master and timedata is loced, and the correction of master data is not possible.

%he release of correction implies that the system allows us to mae corrections to the master and timedata, and exit payroll means that we are done with processing the current payroll period, and it can beexited.

%he incorrect personnel numbers are captured in match code 7W7. %he system captures incorrectlyprocessed employees during payroll. %his needs to be corrected, and we need to rerun the payroll for thesame.

%he earliest retro period in control record determines how far bac in time the system can allow us to maecorrections to processed payroll periods.

%he 0asic !ay (B) infotype is crucial for processing the payroll and is configured by navigating

to -P&A Personnel +anagementA Personnel AdministrationA Payroll (ataA /asic Pay. %hefollowing screenshot demonstrates this


24/33

%he employee subgroup grouping for personnel calculation rule(PC) and collecti


25/33

Tip

%here are many associated table entries that get copied when the tool is used. We see the associated tableentries in the following screenshot

%he wage type texts are normally stored in the T511and T512series tables, while the assignment of

wage type grouping, base type valuation, and so on are stored in T52series tables. %he !lanned Woring

%ime (1) infotype serves as an integration point between the %ime ;anagement and !ayrollsubmodules.

!lanned Woring %ime has the wor schedule of the employee. %his is entangled with public holidays andthe woring time for a wee, month, and so on.

It is configured via the %ime ;anagement submodule that we will be covering in the next chapter. %he worschedule rule that we generate becomes the default one in the !lanned Woring %ime (1) infotype.

%he !lanned Woring %ime (1) infotype is configured by navigating to -P&A Time

+anagementA )or* -chedulesA)or* -chedule ules and )or* -chedules, and is shown in thefollowing screenshot


26/33

Customi'ing the infotype menu and info groups%he infotype menu is the one that the user sees in PA30. %here are different tabs that can be maintained

and different infotypes can be defaulted under each tab. %his functionality is provided for simplifying theuser maintenance of master data of the employees.

Infotype menus are configured by navigating to -P&A Personnel +anagementA PersonnelAdministrationACustomi'ing ProceduresA Infotype +enusA Infotype +enu. %his is shown in thefollowing screenshot

%he menu can be or cannot be maintained based on the user group of the user.

Tip

%he SU3or SU01%$code is used to maintain the @/:.

If we would lie to have the menus dependent on a particular user group, "! has a functionality to meet

this requirement. ay, a particular menu is applicable for only a group of users mapped as @/: 95 in thiscase we have to configure the settings by navigating to -P&A Personnel +anagementA PersonnelAdministrationA Customi'ing ProceduresAInfotype +enusA Infotype +enuA ;ser ,roup(ependency on +enus and Info ,roups. hould the ;ser=dep.field be flagged, it means the menu isdependent on @/: parameter that is maintained in the @4 transaction code for the user. %his is shown inthe following screenshot


27/33


28/33

Infogroups group together infotypes that populate sequentially one after another. 6et's say, in order toperform a hiring action, the infotypes such as actions (), organi-ational assignment (9), and basic

pay (B) need to be filled in by the user. Infogroups can also be based on user grouping such as infomenu. %hey are configured by navigating to -P&A Personnel +anagementA PersonnelAdministrationA Customi'ing ProceduresA ActionsA (efine infogroups. %his is shown in the followingscreenshot

%he menu type of the infogroup that needs to be configured is 7/7. %his infogroup can also be madedependent on the user by flagging the user$dependent chec box and mentioning the reference user group

number maintained in the SU3SU01%$code. It is shown in the following screenshot

%he infogroup 0>can be used to map all the related infotypes that need to be captured for a hiring action.We will see how the mapping is done in the table via the info menu. %he infotypes are configured bynavigating to -P&A Personnel +anagementA Personnel AdministrationA Customi'ingProceduresA ActionsA Info ,roup. %his is shown in the following screenshot


29/33


30/33

%he action type is a two$digit alphanumeric code with text such as hire, change of position, and so onassociated with it. *ach action type will have the infogroup code mapped to it, and based on the personnelaction chosen by the user, the infotype defaults sequentially. %he +# denotes the function character for thepersonnel action. +or example, for hiring, we can use 01, which is the first hiring, and for other actions, wecan use .

"!$delivered function codes can be used and don't require customi-ing. %hey are as follows

?1? %his refers to first hiring

?!? %his refers to first hiring and transfer of data from recruitment

?"? %his refers to activation of personnel assignment in the host country (for global employees)

?#? %his refers to activation of personnel assignment in the home country (for global employees)

?0? %his refers to other actions

%he "! standard employment status (%"%) can be used and will normally fulfill the requirements. %hestandard entries are as follows

0 %his refers to an employee not with the company

1 %his refers to an employee woring with the company, but inactive

2 %his refers to an employee woring with the company, but as a retiree

> %his refers to an employee who is active in the company

0ased on the personnel action, we can map the status number accordingly. +or example, we can use 4 forhiring personnel action and for resignation or separation of personnel action.

%his is how the PA40%$code loos when the user executes to maintain the master data


31/33

"! also has the functionally of defining the reason for each personnel action. +or instance, the hiringpersonnel action can be executed based on multiple reasons such as ramp up, replacement, and so on.

%hey are configured by navigating to -P&A Personnel +anagementA PersonnelAdministrationA Customi'ing ProceduresA ActionsA Create reasons for personnel actionsor

directly or via the V_T530%$code. %his is shown in the following screenshot

%he possible reasons for each personnel action are maintained in the table and can be used in

the PA40%$code. %his will be very useful for reporting purposes, and is shown in the following screenshot

%he menu created needs to be mapped to the standard menu provided by "!.9, which needs to beused. %he following screenshot demonstrates this


32/33

%he standard menu can be configured by navigating to -P&A Personnel +anagementA PersonnelAdministrationACustomi'ing ProceduresA ActionsA Change action menuA ;ser ,roup (ependencyon +enus and Info ,roups.

%he menu can be made dependent on the user maintained in the SU3SU01%$code. %his is shown in the

following screenshot

"ll the personnel actions are mapped to the standard 01menu. %his is shown in the following screenshot

Dynamic actions

%hese are very useful for the maintenance of infotypes. %hey are triggered automatically when a particularchange of aninfotype is performed. %hey are configured by navigating to -P&A Personnel+anagementA Personnel AdministrationACustomi'ing ProceduresA (ynamic Actionsor directly

via T588Z. %his is shown in the following screenshot


33/33

Tip

+or more information on configuring personnel action, there is an excellent reference guide, Unleash the Powerof Dynamic ctions! Ti"s an# Tric$s to %et the &est 'esults, by :ehan aidi.

%he following screenshot demonstrates an overview of the dynamic action

%he infotype and subtype are used to maintain the infotype number for which we want the dynamic actionto be triggered. Wecan also use a specific field name if we want dynamic action to trigger on the changesmade to them. %here are standard function characters that "! has delivered, and we can use them in the

table. %hey are as follows

00 %his is used if it is independent of the current function carried out

02 %his is used for change

04 %his is used for create

0 %his is used for change and create

0" %his is used for delete

10 %his is used for change and delete

12 %his is used for create and delete

%he standard function characters, along with the indicator for step, form the ey for dynamic action. %hestandard "!$delivered indicators for steps are as follows

P %his is used to chec conditions

I %his is used to maintain the record of infotypes

) %his is used to set the default values when creating a new record

@ %his is used to reference to another step

%his is used to call routine

+ %his is used to send mail

+inally, the variable function has to be maintained.

-ummaryIn this chapter, we covered how to configure master data for employees. We have also covered how tocustomi-e info groups, menus, and dynamic actions.

In the next chapter, we will closely loo at configuring the %ime ;anagement submodule and explore thestandard functionalities provided by "!.

Documents

Chapter 4 PA Configuration in Less Than 24 Hours