vrv asia om&pa

Heading 1

SAP Best Practices System Configuration Documentation

V1.0August 2011English

System Configuration Documentation (IMG Activities Organisation Management and Personnel Administration)

SSTL1,6th Floor, Crow Court#128, Cathedral Road Chennai 600 086

1.1Use

The personnel area is an organizational unit that represents a specific area of your organization and is organized according to aspects of personnel, time management and payroll. A personnel area is further divided into several personnel subareas.

In this step, you define the Personnel Areas in your company, adapting the functional scope of a Personnel and Time Management to your organization.

1.2PrerequisitesNone

1.3Procedure

1.To carry out the activity, choose one of the following navigation options:

2.Choose New Entries, enter the values and SAVE the entries.

1.4Result

Personnel Area CodeEMMVEE PV General EMMVEE PhotoVoltaicEMMVEE Toughned GlassEMMVEE PV SystemsEMMVEE Solar DobasepetEMMVEE Corporate

2Maintain Personnel Sub Areas

3.1Use

The employee group allows you to divide your employees into groups and allows you to define their relationship to the enterprise. This will help you to distinguish your employees between persons actively employed and retirees.

In this step, you define the Employee groups in your company.


3.3Procedure

To carry out the activity, choose one of the following navigation options:

Choose New Entries, enter the values and SAVE the entries.It is recommended to use the SAP standard entries

3.4Result

To make use of the following SAP standard entriesPers areaPers SubareaPers areaPers subarea11001101EMMVEE PV General HRD 11001102EMMVEE PV General Admin 11001103EMMVEE PV General IT 11001104EMMVEE PV General Sub Staff 11001105EMMVEE PV General Receptionist 11001106EMMVEE PV General Purchase 11001107EMMVEE PV General Electrical 11001108EMMVEE PV General Finance A/cs 12001201EMMVEE PhotoVoltaic Maintaince PV 12001202EMMVEE PhotoVoltaic Stores PV 12001203EMMVEE PhotoVoltaic Quality PV 12001204EMMVEE PhotoVoltaic Production PV 13001301EMMVEE Toughned Glass Maintaince TG 13001302EMMVEE Toughned Glass Stores TG 13001303EMMVEE Toughned Glass Quality TG 13001304EMMVEE Toughned Glass Despatch TG 13001305EMMVEE Toughned Glass Marketing TG 13001306EMMVEE Toughned Glass Production TG 14001401EMMVEE PV Systems Marketing PS 14001402EMMVEE PV Systems Engineer PS 14001403EMMVEE PV Systems Quality PS 14001404EMMVEE PV Systems Supply Chain PS14001405EMMVEE PV Systems Stores PS 14001406EMMVEE PV Systems Production PS 14001407EMMVEE PV Systems PV Systems 15001501EMMVEE Solar Dobasepet Qaulity DB 15001502EMMVEE Solar Dobasepet Stores DB 15001503EMMVEE Solar Dobasepet Lathe DB 15001504EMMVEE Solar Dobasepet MS Tank Fab DB 15001505EMMVEE Solar Dobasepet SS Tank Fab DB 15001506EMMVEE Solar Dobasepet Enamel Plant DB15001507EMMVEE Solar Dobasepet Tank Insultn DB15001508EMMVEE Solar Dobasepet Collector DB 15001509EMMVEE Solar Dobasepet Struct Sectn DB15001510EMMVEE Solar Dobasepet Despatch DB 15001511EMMVEE Solar Dobasepet Installation DB15001512EMMVEE Solar Dobasepet Design&Dvlp DB 15001513EMMVEE Solar Dobasepet Elect Gn Mtn DB15001514EMMVEE Solar Dobasepet Purchase DB 15001515EMMVEE Solar Dobasepet HR Admin DB 15001516EMMVEE Solar Dobasepet Finance A/cs DB15001517EMMVEE Solar Dobasepet IT DB 15001518EMMVEE Solar Dobasepet Production DB 15001519EMMVEE Solar Dobasepet FAC Admin 15001520EMMVEE Solar Dobasepet Press 16001601EMMVEE Corporate Human Resource 16001602EMMVEE Corporate Finance A/cs 16001603EMMVEE Corporate Mktg & Sales 16001604EMMVEE Corporate Information Tec16001605EMMVEE Corporate Service 16001606EMMVEE Corporate Mktg Bgl South 16001607EMMVEE Corporate Mktg Bgl North 16001608EMMVEE Corporate Rest of Karnatk16001609EMMVEE Corporate South India 16001610EMMVEE Corporate Central India 16001611EMMVEE Corporate North India 16001612EMMVEE Corporate MD Office 16001613EMMVEE Corporate Installation

The employee subgroup represents a subdivision of the employee group. When you define employee subgroups, you are essentially begun to set up your personnel structure. Features are allocated to this in later steps. Employee Grades can also be used as a criterion to determine Employee Subgroups. The following business subtasks are provided among other things:Specification of processing in payroll accounting Specification of validity of primary wage types Specification of validity of work schedules Specification of validity of pay scale groups Specification of validity of time quota types

4.3


Choose New Entries, enter the values and SAVE the entrie

The Following Employee Sub groups have been created interpreted as Grades):Active Employee Directors 1140Active Employee Core Managment 1240Active Employee Senior Managment 1340Active Employee Middle Managment 1440Active Employee Junior Management 8040Active Employee Shop Floor & Others9240Active Employee Contractors

5Assignment of Personnel Area to Company code

5.1Use

In this step, you allocate each of your personnel areas to your company code. When you create a personnel number, the corresponding company code is allocated to it in the infotype Organizational allocation (0001), depending on the enterprise structure in which the employee is situated.

5.2Prerequisites

Company and the Personnel Areas should exist.

5.3Procedure


Choose corresponding company for the personnel areas created and save the details.

5.4ResultThe Following Personnel Areas assigned to company code

1100EMMVEE PV General 1000401200EMMVEE PhotoVoltaic 1000401300EMMVEE Toughned Glass 1000401400EMMVEE PV Systems 1000401500EMMVEE Solar Dobasepet 2000401600EMMVEE Corporate200040

5aAssign employee subgroup to employee group

5a.1Use

In this step, you assign your employee subgroups to their respective employee groups. In addition to this, you determine whether the employee group/employee subgroup combinations are allowed for the country groupings.

ExampleThe employee subgroup for trainees ahould be assigned to the employee group active and not to the employee group pensioners.

5a.2PrerequisitesYou must have created the employee subgroups and employee groups.

5a.3Procedure


3.Assign your employee subgroups to the relevant employee groups.

Familiarize yourself with the SAP sample entries.Delete all the sample entries that you do not need.Define the permitted country groupings for the employee group/subgroup combinations.

5a.4Result

Assigned the following Grades to Country India:All emp subgroup assigned to Ctry Grp India 40

6Maintain Number Ranges

6.1Use

In this step, you specify the number ranges for your Personnel Development objects and the type of number assignment.

6.2Prerequisites

None

6.3Procedure

To carry out the activity, choose one of the following navigation options:Use the Sub Group 01$$ for the number range specifications for the objects to be created (Organisation Units, Positions etc.)

You must assign a unique number to every object.You have the following options: Internal number assignment In this case, the R/3 System assigns numbers and the number ranges are indicated by the letters "IN". External number assignment In this case, the user assigns numbers and the number ranges are indicated by the letters "EX".

Select the specified row (01$$) and select the number range maintenance to maintain the number ranges. In the new screen specify the required number ranges to be used and use the appropriate box for the tick mark, to select Internal or External Assignment.

6.4Result

The following are the SAP standard number ranges, it is recommended to use the standard settings.

SubgroupNR int. assignmentNR. Ext. assignment$$$$INEX

7Maintain User Parameters

7.1Use

The necessary settings for the user will be set here, which includes the Country Grouping (MOL = 40), User Group (UGR=40), Authorization settings etc. Most of the HR Master Data and others are set for the User Group 40. Hence If you do not specify the User Group, views will differ.


7.3Procedure

Select the Parameters and Save the details

7.4ResultParametersParameter IdParameter ValueShort DescriptionPDKXISHMED: Patient Hist. Docu/Diag/NursAcui/NursServ/MR/ReqPRO_02 Project Management: Information Fields ShownPRO_09 Project Administration: Position Tree DisplayPRO_10 Project Administration: Position EditorSCLXUpper and lower case in source code: 'X' = lower, ' ' =upperSU53_STYLECLASSICLayout of SU53 and SU56 (CLASSIC or TREE)WLCX X XX X 00000Workflow: User-specific settings

8Maintain number range intervals for personnel numbers

8.1Use

In this step, you define the number range(s) for personnel number assignment.You have two basic options:

Internal number assignment

In this case, the SAP System assigns the personnel numbers.

External number assignment

In this case, the user assigns the personnel numbers.

To go for External Number Assignment for the existing employees before Go Live and subsequently move to Internal Number Assignment.

The number range intervals are not linked to the automatic recording of customizing changes. You must transport all the changes that are made during the maintenance of number range intervals manually.

To do this, choose Interval -> Transport on the initial number range interval maintenance screen.

8.2Prerequisites

None

8.3Procedure

Enter the from and to range along with the current number and save the details

8.4Result

Following entries have been created

Ranges

NoFromNumberToNumberCurrentNumberExternal0100000001900000000

029000000199999999

X

9Determine defaults for number ranges

9.1Use

To define the default rule number for Number Ranges when hiring new employees.


9.3Procedure


Select the Parameters and Save the details

9.4ResultThe default rule as 01 has been defined, which is Internal.

LineVariable KeyFCOperations000010 DMOLGA00002040 DPERSG00003040 1

&NUMKR=01

10Maintain Forms of Address

10.1Use

In this step, you can set up forms of address for employees.For each form of address, you must specify the form-of-address key, a short and long text and the gender.There are three gender keys (1 = male; 2= female; ' ' = not specified). Do not change these keys.


10.3Procedure


Choose New entries Enter Form of Address key, Title and the description, choose the appropriate gender and the save the details

10.4Result

Used the SAP standard settings and created address key 6 for gender type 2

Form of Address KeyF. Of AddressLong TextGender1MrMr12MrsMrs23MissMiss24MsMs25DrDr16Dr.Dr

11Create Name affixes

11.1Use

In this step you create possible academic titles, aristocratic titles and marks of nobility for employees/applicants and family members.Name affixes are structured as follows:'S' - academic title after name (USA only)'T' - academic title before name (e.g. Dr)'V' - Aristocratic prefixes between first and second name (e.g. von, van)'Z' - Aristocratic titles between first and second name (e.g. Baron, Count)11.2PrerequisitesNone

11.3Procedure

Choose New entries Select type of name affix, enter Name affix, Output text and save the details

11.4Result

Used the SAP standard settings.

12Maintain titles

12.1Use

In this step you create possible academic titles or aristocratic titles you use for your employees.ExampleAcademic titles Dr., Prof.Aristocratic titles Duke, Baron12.2PrerequisitesNone

12.3Procedure

Choose New Entries enter the Name affix, Output text and save the details entered

12.4Result

Used the SAP standard settings

13Create Marital status

13.1Use

In this step you create the possible marital status designations for employees. The standard SAP system contains the most common marital status designations. Create additional marital status designations to meet your requirements.


13.3Procedure

13.4Result

Used the SAP standard settings

Marital Stat.Description0Single1Marr.2Wid.3Div.4NM5Sep.6Unknwn9RegCou

14Create Religious denomination

14.1Use

In this step you create possible religious denominations for employees.


14.3Procedure


Choose New entries Enter the required Religion denomination key, Abbreviation and Description of the Religious denomination and Save the details.

14.4Result

Created the following religious denomination along with existing SAP standard details :

KeyAbbrDenomination Text60SIKHSikhism61JAINJainism

15Define Family types

15.1Use

InfotypeAn infotype is a collection of logical or business-related characteristics of an object. Data is not stored field by field on the human resources database, but is grouped together in logical groups. Examples : Family infotype, Organizational Assignment infotype, Basic Pay infotypeAdditional family member types can be created in this step. Every family member type represents a subtype of the infotype Family (0021).SubtypeAn infotype can be subdivided into a subtype, for example:Infotype 'Family' - Subtypes 'Spouse', 'Child'Infotype 'Addresses' - Subtypes 'Home address', 'Holiday address'Subtypes 'Permanent residence', 'Secondary residence'Standard settingsYou create additional family types in this step. Every family type represents a subtype of the infotype Family (0021).

15.2PrerequisitesInfotypes shall exist

5.3Procedure


a) Enter the value 0021 in the field Infotype.b) Enter the number of the new infosubtypes.c) Enter a short text for the family type.d) Determine the time constraint of the family type.

Definition of Time Constraint

A time constraint indicates whether more than one infotype record may be available at one time. The following time constraint indicators are permissible:

1: An infotype record must be available at all times. This record may have no time gaps. You may not delete the record last stored on the database because all records of this infotype would otherwise be deleted.2: Only one record may be available at one time, but time gaps are permitted.3: Any number of records may be valid at one time, and time gaps are permitted.

Other possible time constraint indicators are as follows:

A: Only one record may ever exist for this infotype. It is valid from 01/01/1800 to 12/31/9999. Splitting is not permissible.View V_T582B Infotypes, Which are Created Atomically controls whether the system automatically creates the infotype, record for an employee hiring or an applicant data entry action.Infotypes with time constraintA may not be deleted.B: Only one record may ever exist for this infotype. It is valid from 01/01/1800 to 12/31/9999. Splitting is not permissible.Infotypes with time constraint B may be deleted.T: The time constraint varies depending on the subtype.Z: Refers to time management infotypes. The time constraint for these infotypes depends on the time constraint class defined in view V_T554S_I Absence: General Control. Collision checks are defined in view V_T554Y Time Constraint Reaction.

15.4Result

Created the following family member types in addition to SAP standard settings starting from 91 to 94.

Sub TypeNameTime ConstraintObject ID1Spouse2

10Divorced spouse2X11Father2

12Mother2

2Child2X3Legal guardian2

4Brother2

5Sister2X6Stepchild2X7Emergency contact2

8Related persons2X9

2

91Father-in-law2

92Mother-in-law2

93Sister3X94Brother3X

16Create Address Types

16.1Use

In this step various address types can be created which can be subtypes of infotype 006, Addresses.

Example : Possible address types include the following:

Permanent residence, Secondary residence, Mailing address, Standard settings

The standard SAP system contains the most common address types, It is recommend adopting the standard settings.


16.3Procedure


Choose New entries Enter the required subtypes, Name, time constraint and save the details.

14.4ResultRenamed the following SAP standard Address types.

STypNameConstraint1Permanent Address12Temporary Address33Home Address 24Emergency address25Mailing address26Nursing address217Define State

17.1Use

This section of the implementation guide (IMG) will help in ensuring that all the states in which you do business are correctly entered in the system. (SAP Standard advisable)


17.3Procedure


Choose New entries Enter the country, region id description and save the details.

17.4Result

Retained the SAP standard States.

18Maintain Communication types

18.1Use

In this step you define the valid communication types, which will be stored for addresses.

ExamplesEmployees may have a second telephone and fax machine at an address.

Activities1. Enter the different communication types which your organization uses.2. Enter the communication category for each entry.3. Save your entries.


18.3Procedure


Choose New entries Enter the type, category, text and save the details

18.4Result

Retained the SAP standard Communication types

FAX12Telefax

FAX21Telephone

TEL21Telephone

TEL31Telephone

VOIC3Voice mail

WORK1Telephone

19Create Bank connection types

19.1Use

In this step you create the types of bank connection you require, the bank connection types are defined as subtypes of infotype 0009, Bank Details.

Example - Possible types of bank connection:Main bank connectionAdditional bank connectionsBank connection for travel expensesMain bank details for Off-CycleOther bank details for Off-Cycle

The standard SAP system contains the most common bank types, it is recommended to use the standard settings.


19.3Procedure

To carry out the activity, choose one of the following navigation options:Choose New entries Enter the subtype, Name of the connection, time constraint and save the details

19.4ResultRetained the SAP standard Bank connection typesSubtypeNameTime Constraint0Main bank11Other bank32Travel expenses25Main bank details for Off-Cycle36Other bank details for Off-Cycle3

20Define Payment method

20.1Use

In this step, you set up the payment methods in your system.

Example

The indicator "U" for a payment method means that amounts are transferred to the employee's account.The indicator "S" for a payment method means that the amount is paid by check.

The standard SAP System contains indicators for all the common payment methods, it is recommended to use the SAP default setting

It is recommended to use the SAP standard settings.


20.3Procedure


The Payment methods has to be maintained by Finance Department

20.4Result

Payment methods in company codesPymt. MethodDescriptionCChequeDDD paymentTBank Transfer ECash Payment

21Determine Default Payment Method

21.1Use

In this step, with the help of the feature Default value for payment method, you can define a payment method, which is later proposed as a default for certain countries and infotypes when you create bank details.

Example

You can use "U" (bank transfer) as the default indicating the payment method in Human Resources.

Requirements

Decide which indicator you wish to use as the default for the payment method in infotype 0009, Bank details.

The indicators for the payment method are now defined.

Standard settings

Feature ZLSCH, Default value for payment method proposes the indicator almost always used for the payment method as a default.

Recommendation

Use the default setting.

Activities

1. Call up the decision tree for feature ZLSCH.2. Check the default settings.3. Refer to the feature documentation.4. If necessary, maintain the new entries according to your own needs.


21.3Procedure

Call up the decision tree for feature ZLSCH.Check the default settings.Create the country node IN under country key LAND1, further create return value as `T (Bank Transfer) Save and activate the Feature.

21.4Result

Created T as default payment method in feature ZLSCH to default while creating Employee Payment method infotype 0009

22Maintain types of Identification

22.1Use

In this step you set up the types of Identity Cards, which an employee may possess. You also specify if the assignment of a certain IC type to an employee in infotype ID Data (0185) is to initiate the request for additional information, such as whether the employee possesses a work permit. The SAP standard delivery system contains IC types for all currently issued Identity Cards. If you want to use these entries, you first must copy them from client 000 since the table in which they are stored possesses delivery class C.

Example : Superannuation for India, PAN Number, Gratuity for India, Passport Number


22.3Procedure


Choose the Country type then choose New Entries - Enter type of identification, Description and save the details.

22.4Result

Following are the Identifications created along with the SAP standardId TypeDescriptionID ColorAddtl.InfoWorkPermitModuleNameProgram Name01Superannuation for India

02PAN Number

03Gratuity for India

04Resident status

05TAN No

23Maintain Residency types

23.1Use

In this step you maintain the residency types you want to use in the infotype Identification (0185). The SAP standard delivery system contains the most common residency types as sample entries. If you want to use these, you first must copy them from client 000 since the table in which they are stored possesses delivery class C.

Example : Citizen, Resident of India, Non-Resident of India


23.3Procedure

Select New entries.Enter a two digit, alphanumerical key that identifies the residency type.Enter a short description.Save your entries.

23.4Result

Following Residency types are createdRes.TypeText01Citizen02Resident of India03Non Resident of India

24Specify Examination types

24.1Use

In this step you define the examination types that you want. The examination areas are subtypes of the infotype Internal medical service (0028).

Example

In your enterprise, the following examinations are carried out regularly:

0000 medical examination for hiring0001 eye test0002 hearing test0003 reaction test


24.3Procedure

Enter the required subtypes for the infotype Internal medical service. (0028).Define a text for the subtype.Define the time constraint per subtype.

24.4Result

Retained SAP standard details

25Define Examination Area

25.1Use

The examination area is a medically relevant entity that can be made into the object of a medical examination for the employees in your enterprise.

Example

You want to determine the following examination areas for the examination type Medical examination for hiring:

01 height02 weight03 blood type

25.2PrerequisitesInfotype and the corresponding Subtype (Examination types)

25.3Procedure

Define the necessary examination areas per examination type. Note that you can define a maximum of 30 examination areas per examination type.Define a text for the examination areas.

25.4Result


26Define Permissible values for Examination Areas

26.1Use

In this step you define the permissible values for the examination areas. You must define permissible values for every examination area.

Example

For the examination type Medical examination for hiring, you have defined the examination area "height / women". You have stored the following input values for this examination area:

01 small (up to 1.60 meters)02 normal (up to 1.70 meters)03 tall (more than 1.70 meters)

26.2PrerequisitesInfotype, corresponding Subtype (Examination types), Examination area

26.3Procedure


Create the permissible values for entering your findings for each combination of examination type and examination area.Define a text for the results of your findings.

26.4Result


27Define Examination results

27.1Use

The last action you have to perform to set up the infotype Internal medical service (0028) is to store the possible outcome of the examination type in this step.

Example

The following input values are defined as outcomes of the examination type Medical examination for hiring:

01 able to work02 unable to work

27.2PrerequisitesInfotype, corresponding Subtype (Examination types)

27.3Procedure

Define the outcome of the examination Enter the result, description and save the details.

27.4Result


9Define International terms of employment

29.1Use

In this step, you define the possible terms of employment.

Example

You need an additional, optional means of distinguishing your human resource master data.


29.3Procedure


For the selected Country group choose New entries and add Contract id and Contract text and save the details.

29.4Result

Created the following details :

ContractContract text01Confirmation02Probationer03Trainee04Apprentice

30Create Payroll Area

30.1Use

In this step, you set up the payroll areas (accounting areas) that your enterprise needs. The payroll area fulfills two functions that are necessary for payroll:It groups together personnel numbers that are to be processed on the same date.It determines the exact payroll period.ExampleYou define one payroll area for salaried employees and one for industrial workers.


30.3ProcedureTo carry out the activity, choose one of the following navigation options:

Choose New entries Enter Payroll Area Id and Payroll area text put a tick in Payroll for PA if you want to run payroll for the Payroll Area.

30.4ResultCreated the following details :

Payroll AreaPayroll Area textPayroll for PA11CorporateX12SonapannhalliX

31Check Default Payroll Area

31.1Use

In this step, you define default values for the payroll area for your employees. When master data is being maintained, the payroll area is proposed as a default in the infotype Organizational assignment (0001).

Example

When new employees are hired or organizational changes take place in employee subgroups "wage", the payroll area "01" is proposed; for the employee subgroups "salary", the payroll area "02" is proposed.

In the standard SAP System, the payroll accounting area is determined according to the HR country grouping, the employee group and the employee subgroup.

31.2PrerequisitesYou must have created the payroll areas.

31.3Procedure


Call up the feature Default for payroll area (ABKRS). If necessary, change the decision tree according to your requirements.

31.4Result

The Feature ABKRS in the previous version had the Personnel Area and Personnel Sub Area fields for building decision tree, but in MySAP version these two fields are removed, hence not created the Default Payroll Area.

32Create Control Record

32.1Use

In this step, you set up the system controls for the payroll control record. This control record has the following functions in payroll:

It determines the current payroll period for the exact date.It defines the payroll past for the retroactive accounting recognition.It locks the master data and the time data to prevent changes from being made during the payroll run. This lock is valid for the payroll past and the payroll present. Changes, which affect the future, can still be made.It determines the earliest retroactive accounting period.

32.2PrerequisitesYou must have created the payroll areas.

32.3Procedure


Create a new control record for each payroll area.Assign the necessary data to each of these control records.

32.4ResultCreated Control record details for the following Payroll Area (earliest retro acctg. period is 01 -2010):

33.1Use

An organizational object used to depict the basic structure of an organization.

Organizational units are functional units of an enterprise. Depending on how tasks are distributed in an enterprise, an organizational unit can be a department, group, project team, or other unit.

Organizational units are different from other enterprise entities such as company codes, business areas, and personnel areas. Those enterprise entities are used to depict administrative or accounting structures in the corresponding components.


33.3Procedure


33.4Result

Following Organizational units created using transaction code PPOM_OLD :

34Define Jobs

34.1Use

A job describes a group of tasks, authorities and responsibilities and defines the level of education required to perform this work. It is assigned to different positions on the basis of the amount of work to be performed.

Jobs are areas of activity in a company, which are described by tasks.

Examples include "secretary", "clerk", or "financial accountant". Jobs can be created across organizational units.

34.2PrerequisitesOrganization Unit should exists if created through Organization structure using Transaction code PPOM_OLD.

34.3Procedure


34.4Result

Following jobs are created using transaction code PPOM_OLD :

Created by EMMVEE Users Not configured

35Define Positions

35.1Use

An organizational object (object type key S) used to distribute tasks to posts in an organizational plan and to model the reporting structure between posts.

Positions are concrete posts in an enterprise, which can be occupied by holders (employees or R/3 users), for example purchasing administrator, European sales manager, or secretary in the marketing department. Positions are not the same as jobs. A job is not a concrete position in an enterprise. It is a construct that enables you to create a number of positions with similar tasks and features.

35.2PrerequisitesOrganization Unit and Jobs should exist, if created through Organization structure using Transaction code PPOM_OLD.

35.3Procedure


35.4Result

Following Positions are created using transaction code PPOM_OLD :ObjectPositionPosition TextStart DateEnd DateOMS99999999Default position01.01.180031.12.9999

Created by EMMVEE users Not configured

39Contract Elements

39.1Use

In this step, you can create contract categories.

Example

An employee has a limited contract, and another has an unlimited contract like Confirmed Employee, Probationer, Trainee, Apprentice.

39.2Prerequisites

None

39.3Procedure

Carry out the activity, cChoose New Entries Enter Contract type, Contract Text and Fixed-term Contract (This indicator is used to control displaying and entering data for the contractual end date when infotype 0016 Contract Elements is maintained), then save the details.

39.4Result

Created following Contract types.

Contract TypeText - Contract TypeFixed term ContractC1Confirmed

C2ProbationerXC3TraineeXC4Apprentice

C5Temporary

40Determine Periods of Notice

40.1Use

In this step, you can define the periods of notice that you require within your enterprise.

Example

An employee must give six weeks' notice before the end of a quarter; another employee must give a month's notice before the end of the month he/she plans to leave. It is recommended to use the default SAP settings.

40.2Prerequisites

None

40.3Procedure

Carry out the activity, choose one of the following navigation options:

Choose New Entries enter period of notice and Description and save the details.

40.4Result


Period of Notice0102030405061241Determine Default Contract elements

41.1Use

In this step, you can determine default values, depending on various control features for the following fields:

Period of continued pay, Sick pay allowance period, Probation period, Contract categoryPeriod of noticeExample

You want to set up the default for the employee subgroup 'Salaried employees' in the infotype Contract elements (0016), so that this employee subgroup has 42 days' continued pay, 6 months' sick pay supplement and a period of notice that is 6 weeks before the end of the quarter. Industrial workers are to have the default of 42 days' continued pay, no sick pay supplement, a one-month probation period and a period of notice that is one week before the end of the month.

41.2Prerequisites

You need to have defined the periods of notice in the step "Determine periods of notice".You need to have created the contract categories in the step "Define contract categories".

41.3Procedure


41.4Result

SAP standard entries are retained not configured.

42Define Objects on Loan

42.1Use

In this step, you can store objects on loan to be given for employees in the organization.

Example

An employee receives work clothing from the enterprise, and another employee received certain tools on loan.

42.2Prerequisites

None

42.3Procedure


Select new entries and enter the Subtype (Loan type), Description and save the details.

42.4Result

SAP standard entries are retained added the following entries :

Sub TypeName1Key(s) 2Clothing 3Books 4Tool(s) 5Company ID 901Safety Shoes 902Mobile Phones 903Shields 904Acid/Alkali proof Rubber Gloves905Chemical Respirator 906Nitrile Rubber Gloves 907Leather Gloves 908Helmets 909Canvas/cotton Gloves 910Surgical Gloves 911Dust mask 912Gumboot

43Determine Task Type

43.1Use

In this step, you define task types with standard lead times and standard follow-up times as well as indicators for additional tests.

Example

You want to talk to a new employee two weeks before the end of his/her probation period.

43.2Prerequisites

None

43.3Procedure


Select new entries and enter the Task type, Description, Lead / Follow up time, Check for Public Holiday calendar and save the details.

43.4Result

Created following Task types :Task TypeTask Type TextLead/Follow Up TimeUnitOperator01Expiry of probation1Months0102Temporary contract2Months0203Pay scale jump2Months0304Work permit6Months0405Severe challenge6Months0506Training period10Days0607Dismissal protection10Days0708Expiry inactive con.2Months0809Expiry temp.contract2Months0910Appraisal10Days1040Prior attachment1Days4050Expiry of probation1Months5051Permanent - One Year1Months5170Next appraisal2Months7071Work permit expires4Months71

44Create Education Establishment Types

44.1Use

In this step you create education establishment types for your employees/applicants.

ExampleThese may include the following:Elementary school, High school, Technical college, University

44.2Prerequisites

None

44.3Procedure


Select new entries and enter Education establishment type and description and save the details.

44.4ResultCreated following Education establishment types :Edu.Est.TypeEdu.Est.Text1School 2College 3University4Others

44Create Education/Training

45.1Use

In this step you create traineeships/professions attained by employees/applicants.

Example

These might include the following:

Mechanic, Chemist, Technician, Engineer

45.2Prerequisites

None

45.3Procedure


Choose New entries enter Education / Training Id and the corresponding description and save the details.

45.4Result

Creating following Education / Training types

E & T typeE & T TextE & T typeE & T TextE & T typeE & T Text1Primary 44BTS 87MPHARMA 2Secondary 45BVSC 88MPhil 3PUC / High School 46CA 89MPM 4Matriculation 47CA(Inter) 90MSc 5Certificate 48CBSE 91MSW 6Diploma 49Chemist 92MTA 7Post Grad Diploma 50DBM 93MTech 8Advance Diploma 51DCP 94MTM 9Bachelor Degree 52DCT 95MVSC 10Master Degree 53Degcorrespondence 96NoCertificate 11PhD 54Degree 97PG 121stStandard 55DME 98PGBM 132ndStandard 56DMEE 99PGDBA 143rdStandard 57DPharm 100PGDBM 154thStandard 58Hotel 101PGDFM 165thStandard 59HSC 102PGDHRD 176thStandard 60ICSE 103PGDHRM 187thStandard 61ICWAI 104PGDIM 198thStandard 62ICWAI INTER 105PGDiploma 209thStandard 63Intermediate 106PGDM 21ACS 64ITI 107PGDMM 22AMIE 65ITIAttendentOperator 108PGDOM 23ASSLC 66ITIFitter 109PGDPM&IR 24Automechanic 67LLB 110PGDRD 25BA 68LLM 111PGHM 26BArch 69MA 112PGJMC 27BBA 70MBA 113MHRM 28BCA 71MBBS 114Physicist 29BCom 72MCA 115Shorthand Higher 30BE 73MCom 116SSC 31BEd 74MCSE 117SSLC 32BHM 75MD 118Translator 33BIT 76ME 119Others 34BL 77MEd 120Ist Class Boiler Attendant35BLib 78MFA 1212nd Class Boiler Attendant36BLIS 79MFM 122ITC 37BLM 80MHRM 123L M E 38BPharm 81MIRPM 124Shorthand Lower 39BS 82MLib 125Typing Higher 40BSc 83MLIS 126Typing Lower 41BSW 84MLM 127First Aid Certification 42BTCM 85MMS

43BTech 86MPharm

46Define Institute Type

46.1Use

In this step, you create institution types for your employees/applicants. These types are divided according to organizational attributes.

Example

These may include the following:Public, national, private

46.2Prerequisites

None

46.3Procedure


Choose New entries enter Institute type Id and description and save the details.

46.4Result

Created the following entries interpreted for future reference :

Institute typeDescription1national2public3private

47Create Educational Certificates

47.1Use

In this step you create the educational certificates obtained by employees/applicants.

Example

Possible educational certificates include:High school, diploma, BSc, MA, PhD

47.2Prerequisites

None

47.3Procedure


Choose New entries Enter certificate type id and description and save the details.

47.4ResultCreated the following certificates along with the SAP standard entries :

Cert. TypeCert. DescriptionCert. TypeCert. Description0No final certificate7PhD1Final certificate8Others2Diploma

3Post Grad Diploma

4Advance Diploma

5Bachelor Degree

6Master Degree

48Determine permissible certificates for education type

48.1Use

In this step you determine which educational certificates are permissible for the education types created.

The specifications you make here are used to check whether the educational certificate is allowed for the education type specified when entering data on an applicant's education.

To mark an educational certificate as permissible for an education type, you must specify the educational certificate key and the accompanying education type key. The system then automatically provides the text for the key.

Example

Permissible educational certificates for the education type "University" might include:

MA, BSc, First degree, PhD etc.

48.2Prerequisites

You should already have created the required education types in the step "Create education types".

You should also have created the required educational certificates in the step "Create educational certificates".

48.3Procedure


Choose New entries Enter the Institution type and the corresponding Certificate type and save the details.

48.4Result

Retained SAP standard Branches of study details.

Retained SAP standard Permissible Branches of study for Education type details.51Create employer's industry sector.

51.1Use

In this step you create all industry sectors in which a previous or current employer of an employee/applicant operates.An industry sector classifies enterprises according to the area of industry to which they belong.Example - Possible industry sectors include:Plant engineering and construction, Chemical industry, Mechanical engineering, Retail, Insurance, Pharmaceutical Industry


51.3Procedure


Choose New entries Enter the Industry type id and the description and save the details.

51.4Result

Created the following Industry types :IndustryDescriptionIndustryDescription1Chemical Industry 14Educational Inst. 2Cement 15Automobile 3Phamaceutical Ind.16Information Tech. 10Refineries 17Steel 11Textile Industry 18Medicine Marketing12Banking Sector 19Retail 13Research Institute20Others

52Create activities in employment

52.1Use

In this step you create all activites performed by an employee/ applicant in the service of a previous or current employer.

Example

Possible activities might include:Electrician, Accountant, Programmer

52.2Prerequisites

None

52.3Procedure

Carry out the activity, choose one of the following navigation options:Choose New entries Enter the Industry type id and the description and save the details.

52.4Result

Created the following details :

JobTextJobText1Marketing Representative 000000041Assistant Officer2Bricklayer 000000042Chief Financial Officer3Cook 000000043Area Business Manager4Programmer 000000044Executive5Translator 000000045Chartered Accountant6Systems analyst 000000046Senior Chemist7Accountant 000000047Junior Chemist10Chemist 000000048Male Nurse11Marketing Executive 000000049Doctor12Junior Engineer 000000050Director13Senior Engineer 000000051Group Leader14Technician 000000052Operator15Fitter 000000053Team Leader16Grinder 000000054Team Members17Store Keeper 000000055CEO18Executive Assistant 000000056COO19Programmer 000000057Trainee20System Analyst 000000058Data Entry Operator21Project Manager 000000059Research Associate22Project Leader 000000060Junior Executive23Consultant 000000061Senior Executive24Manager 000000062Asst Vice President25Deputy Manager 000000063Executive Secretary26General Manager 000000064Assistant27Vice President 000000065Helper28President 000000066Worker29Pharmacist 000000067Professor30Associate Business Manage000000068Lecturer31Secretary 000000069Telephone Operator32Company Secretary 000000070Administration33Regional Manager 000000071Asst.General Manager34Divisional Manager 000000072Deputy General Manager35Assistant Manager 000000073Senior Manager36Research Scientist 000000074Engineer37Lab Assistant 000000075Businees Manager38Scientist 76Others 39Senior Scientist

40Officer

53Work Contracts from Other Employers

53.1Use

In this step you create all activites performed by an employee/ applicant in the service of a previous or current employer.

Example

Possible activities might include:Electrician, Accountant, Programmer

53.2Prerequisites

None

53.3Procedure


Choose New entries Enter the work contract type id and description and save the details.

53.4ResultCreated the following work contract types :ContractContr.text01Trainee02Apprentice03Contract04Permenant05Probatiner06Terminated07Resigned08Consultant09TemporaryDefinition of Infotype / Subtype / Object Id

Infotype

A set of data grouped according to subject matter

The Human Resources component aims to enable the user to process employee data in an effective structure in accordance with business requirements.

The data structure of infotypes mirrors a logical set of data records. Their four-digit keys can identify Infotypes, example the Addresses infotype (0006).

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

You can edit infotype records individually or by using fast data entry.

The following functions are used for infotype records:

Create, Change, Copy, Delimit, Delete

Subtype

Further subdivision of an infotype, i.e,categories of information within an infotype.

Some infotypes do not need to be divided into subtypes. When you create an infotype with subtypes, you must specify the subtype in which you want to store information.

An infotype can be subdivided into a subtype, for example:

Infotype 'Family'Subtypes 'Spouse', 'Child'

Infotype 'Addresses'Subtypes 'Home address', 'Holiday address'Subtypes 'Permanent residence', 'Secondary residence'

Object Id

A unique eight-digit number identifies an object.

The object ID is assigned to the object when the object is created.

If an enterprise uses internal number assignment, the system assigns the object ID. If an enterprise uses external number assignment, the user assigns the object ID.

55aInfotypes

55a.1Use

In the step "Set up infotypes", you store the infotypes you require to enter employee data for administration, time recording and payroll.

Please see the glossary definition for the term infotype.

Please also see the glossary definition for the term subtype.

Subtypes may require further subdivision: object ID.

At least one infotype text is assigned to an infotype. Several different texts for the same infotype must have different screen types.

55a.2Prerequisites

55a.3Procedure

To carry out the activity, choose one of the following navigation options:Transaction CodeSPRO View reference V_582AIMG MenuIMG Personnel Management Personnel Administration Payroll data Basic Pay Define EE Subgroup Grouping for PCR and Coll.Agrmt.ProvisionCheck the infotypes that have been entered.If necessary, change the infotype entries or texts.Additional infotype texts

55a.4Result

Following infotype characteristics modified based on requirement:

EE GroupName of EE GrpEE Sub GrpName of ESGESG for PCRESG for CAPCGrpg

All subgroups ESG For PCR 3 ESG For CAP -3 Cgrp 40

55Infotype Menu

55.1Use

In this step, you define the infotype menus for maintaining and displaying Human Resources master data.These menus can be defined so that they are dependent on the user group (user parameter UGR).If there are no entries for an infotype menu for the user's user group or if the user has not maintained his/her user group, then the infotype menu is determined using the reference user group.

Example

You want to include an infotype in an infotype menu or define a new infotype menu for a user group.

55.2Prerequisites

Infotypes shall exist.

55.3Procedure


Choose menu category "I" and the infotype menu.Define whether the menu is to be dependent on the user group.If necessary, assign the system response for the case where the user has not maintained the user group or where there are no entries in the menu.Assign a reference user group which can be used to set up the menu, if necessary.

Infotypes in the infotype menuChoose menu category "I" and the infotype menu.Copy the infotypes into the menu for the user group.

55.4Result

Created the following User group dependency on menus and info groups :

Infotype MenuTextUser-DepReactionRef.M1Basic personal dataX40M2Contract dataX40M3Payroll DataX40M4Time DataX40M5IT DataX40

Created the following Infotype Menu :

a) Basic Personnel DataUser GroupNo.InfotypeScreenInfotype Text4010 Actions 4021 Organizational Assignment4032 Personal Data 4046 Addresses 405105 Communication 40621 Family Member/Dependents 40728 Internal Medical Service 40822 Education 40923 Other/Previous Employers 4010591 Nominations 401137 Insurance 4012185 Personal IDs 401332 Internal Data

b) Contract DataUser GroupNo.InfotypeScreenInfotype Text40020016 Contract Elements40030041 Date Specifications40040019 Monitoring of Tasks

c) Payroll DataUser GroupNo.InfotypeScreenInfotype Text4018 Basic Pay 4029 Bank Details 40378 Loan Payments 40415 Additional Payments 4053 Payroll Status 40637 Insurance 40745 Loans 40857 Membership Fees 409267 Additional Off-Cycle Payments4010185 Personal IDs 4021591 Nominations 402240 Objects on Loan 4023183 Awards

d) Time Data

User GroupNo.InfotypeScreenInfotype Text4017 Planned Working Time40250 Time Recording Info4032011 Time Events4042001 Absences4052002 Attendances4062003 Substitutions4072005 Overtime4082006 Absence Quotas40112051 Monthly Calendar

e) IT Data

User GroupNo.InfotypeScreenInfotype Text401580 Previous Employment Tax Details402581

Housing(HRA / CLA / COA) 403582

Exemptions 404583

Car & Conveyance 405584

Income From Other Sources 406585

Section 80 Deductions 407586

Section 80 C Deductions 4011590

Long term reimbursements

56Determine choice of infotype menus.

56.1Use

In this step, you define the infotype menu choice which appears in a dialog box when Human Resources master data is maintained and displayed, if the user chooses the pushbutton "Other menu" to change the current infotype menu.This choice can be defined so that it is dependent on the user group (user parameter UGR).

If you have defined the set-/get-parameter PMN (infotype menu), the corresponding infotype menu appears when you call the initial HR Master Data display/maintenance screen for the first time. Otherwise the infotype menu "01" is used.If there are no entries in the table for the user's user group, or if the user has not maintained his/her user group, then the infotype menu choice is determined using the reference user group.

Example

You have defined a new infotype menu and want this to appear in the dialog box.

56.2PrerequisitesInfotypes shall exist.

56.3Procedure

Carry out the activity, choose one of the following navigation options:User group dependency of the choice of infotype menuChoose menu category "S" and menu "01" for the infotype menu choice.Determine whether the menu is to be dependent on the user group.If necessary, assign the system response for the case where the user has not maintained his/her user group or where no entries exist.Assign a reference user group which can be used to set up the menu if necessary.

Infotype menus in infotype menu choicea) Choose menu category "S" and menu "01" for the infotype menu choice.b) Include the infotype menus for the user group.

56.4Result

Changed the following Text for Menu type 01 - :

MenuTextUser-DepReactionRef01Master DataX

40

Created following for Menu type S and Menu 01:

User GroupNo.MenuText400101Basic personal data400202Contract data400303Payroll Data400404Time Data400405IT Data

57Define Infogroups

57.1Use

In this step, you define the info groups that are processed when actions are carried out. This must be carried out before you proceed to the next step where you must define the work list, i.e. the info group, for every personnel action that is to be carried out.The info groups can be defined so that they are dependent on the user group (user parameter "UGR").If there are no entries for an info group for the user's user group or if the user has not maintained their user group, then the info group is determined using the reference user group.

In addition to this, the info group can be set up so that it is dependent on the employee's control data. You can do this by using feature Info group modifier (IGMOD).

Example

When hiring an employee, the infotypes Personal data (0002), Organizational assignment(0001), Address (0006), Planned working time (0007) etc., are created one after the other.

The standard SAP System contains one info group for every action. The info groups are generally dependent on the user group. In this case, the country grouping is used as a value of the user group. The info groups are set up independent of the employee's control data, i.e. the feature IGMOD has "space" as its return code.

57.2Prerequisites

None

57.3Procedure


57.4Result

Created the following :

a) User group dependency on menus and info gr Infogroup modifier

MenuTextUser DepReactionRef01Hiring X

4002Organisation Reassignment X

4004Confirmation X

4007Transfers X

4008Promotions X

4010Leaving X

40

b) Infogroup modifier

Using the feature IGMOD, you can default the Infogroup, which is defined as the Infogroup Modifier.

c) Info group

1. Hiring

IGUser groupInfogr mod.NoTextOp.ITypeSCstxInfotype text0140

1HiringINS2

Personal Data 0140

2HiringINS1

Organizational Assignment 0140

3HiringINS6

Addresses 0140

4HiringINS7

Planned Working Time 0140

5HiringINS8

Basic Pay 0140

6HiringINS9

Bank Details 0140

7HiringINS21

1Family Member/Dependents 0140

8HiringINS21


9HiringINS21


10HiringINS22

Education 0140

11HiringINS22

Education 0140

12HiringINS22

Education 0140

13HiringINS23

Other/Previous Employers 0140

14HiringINS23


15HiringINS23


16HiringINS16

Contract Elements 0140

17HiringINS19

Monitoring of Tasks 0140

18HiringINS591

BNESNominations 0140

19HiringINS591

BNGRNominations 0140

20HiringINS591

BNMBNominations 0140

21HiringINS591

BNPFNominations 0140

22HiringINS591

BNPNNominations 0140

23HiringINS591

BNSUNominations 0140

24HiringINS2006

30Absence Quotas 0140

25HiringINS2006


26HiringINS2006


28HiringINS105

CELLCommunication 0140

29HiringINS105

10Communication 0140

30HiringINS28

1Internal Medical Service 0140

31HiringINS580

Previous Employment Tax Details0140

32HiringINS581

Housing(HRA / CLA / COA) 0140

33HiringINS587

Provident Fund Contribution 0140

34HiringINS588

1Other Statutory Deductions 0140

35HiringINS588


36HiringINS588


37HiringINS27

1Cost Distribution

2. Organisation Reassignment

UserGrpInf.Grp.MdfrNoOperationInfotypeScInfotype TextSubtype40

01COP0001

Organizational Assignment4040

02COP0007

Planned Working Time40

3. Trainee to Probation

UserGrpInf.Grp.MdfrNoOperationInfotypeScSubtyInfotype Text40

1COP1


2COP16


3COP19


4COP7


5COP8

Basic Pay 40

6COP15

Additional Payments 40

7COP588

1Other Statutory Deductions40

8COP588


9COP588


10COP37

Insurance 40

11LIS9185

Personal IDs 40

12COP2006

30Absence Quotas 40

13COP2006

31Absence Quotas 40

14COP2006

32Absence Quotas

4. Confirmation


1COP1

Organizational Assignment

40

2COP16

Contract Elements

40

3MOD19

Monitoring of Tasks

40

5INS7

Planned Working Time

40

6COP8

Basic Pay

40

7COP2006

Absence Quotas 3040

8COP2006

Absence Quotas 3140

9COP2006

Absence Quotas 32

5. Extention of Probation/training


01COP0001


40

02COP0016

Contract Elements

40

03COP0019

Monitoring of Tasks

6. Change in Pay


01COP0001


40

02COP0008

Basic Pay

40

03COP0589

Individual Reimbursements

7. Transfers


1COP1


2COP6

Addresses 140

3COP6

Addresses 440

4COP7


5COP8

Basic Pay 40

6COP15

Additional Payments 40

7COP9

Bank Details 40

8COP16


9COP19


10COP2006

Absence Quotas 3040

11COP2006

Absence Quotas 3140

12COP2006

Absence Quotas 32

8. Promotions


1COP1


40

2COP16

Contract Elements

40

3COP19

Monitoring of Tasks

40

4COP7

Planned Working Time

40

5COP8

Basic Pay

40

6COP589


40

7COP2006

Absence Quotas 3040

8COP2006

Absence Quotas 3140

9COP2006

Absence Quotas 32

9. Demotions


1COP0001


40

2COP0016

Contract Elements

40

3COP0019

Monitoring of Tasks

40

4COP0008

Basic Pay

40

5COP0589


10. Leaving

UserGrpInf.Grp.MdfrNoOperationInfotypeScInfotype TextSubtype40 1DIS 2 Personal Data 40 2DIS 1 Organizational Assignment 40 3DIS 6 Addresses 140 5DIS 8 Basic Pay 40 6LIS99 Bank Details 40 7DIS 580 Previous Employment Tax Details 40 8LIS9581 Housing(HRA / CLA / COA) 40 10LIS9583 Car & Conveyance 40 11LIS9584 Income From Other Sources 140 12LIS9584 Income From Other Sources 240 13LIS9585 Section 80 Deductions 40 14LIS9586 Section 80 C Deductions 40 15LIS9587 Provident Fund Contribution 40 16LIS9588 Other Statutory Deductions 140 17LIS9588 Other Statutory Deductions 240 18LIS9588 Other Statutory Deductions 340 21LIS9591 Nominations BNES40 22LIS9591 Nominations BNGR40 23LIS9591 Nominations BNMB40 24LIS9591 Nominations BNPF40 25LIS9591 Nominations BNPN40 26LIS9185 Personal IDs 140 27LIS9185 Personal IDs 240 28LIS9185 Personal IDs 3

59Create reasons for personnel actions

59.1Use


59.2Prerequisites

None

59.3Procedure


Choose New entries Select the Action type and enter the reasons you would like to mention for the corresponding action and save the details.

59.4Result

SAP STD

60Change action menu - User group dependency of the action menu

60.1Use

In this step, you define a menu of actions which appears if the user chooses the function "Personnel actions" in HR master data maintenance.The menu can be defined so that it is dependent on the user group (user parameter "UGR").If there are no entries in the table for the user's user group, or if the user has not maintained their user group, then a so-called reference user group is determined, which is used to set up the menu.

Example

You want to include your own personnel action in the menu, or you want to set up a menu of certain personnel actions for a group of users.

60.2Prerequisites

You have already checked the existing personnel actions and, if necessary, created your own actions.

60.3ProcedureTo carry out the activity, choose one of the following navigation options:

User group dependency of the action menuChoose menu category "M" and menu "01" for the personnel actions.Determine whether the menu is to be dependent on a user group.If necessary, assign the system response for the case where the user has not maintained the user group or where there are no entries.Assign a reference user group which can be used to set up the menu, if necessary.Actions in the action menuInclude the new entries for the user group.

Further notes

Notes on creating batch input sessions:

The user parameters are not available when processing sessions in the background. Thus, if you coordinate the batch input session with a certain user group, this value must agree with the reference user group. Otherwise, the system calls up a totally different action.

SAP recommends that you do not call up the action in batch input with transaction "PA40", but that you use transaction "PA30" instead. Put the key of the action into the subtype field and assign the function code for "Create".

60.4Result

Following entries are created :

MenuTextUser-DepReactionRef.01ActionsX

4002Fast entry for actionsX

40

61Change action menu Action Menu

61.1Use


61.2Prerequisites

None

61.3Procedure

1. To carry out the activity, choose one of the following navigation options:Choose New entries Enter the User group, number, choose the action and save the details.

61.4Result

Created following details : Menu 01: ActionsUser GrpName of Action Type40Hiring40Organizational reassignment40Confirmation40Transfer40Promotion40Leaving

62Create Dynamic Actions

62.1Use

Here, you control the initiation of actions when maintaining an infotype record.This can be the maintenance of an additional infotype record or performing a routine.For each action, you can determine whether it is always carried out when you change an infotype or a subtype or whether it is only carried out if you change certain fields.You can state whether the action is to be carried out for "Change", "Create" and/or "Delete" record.You can store the conditions for executing the action, for example, the comparison of the old and new value of a field.Finaly, you can also specify default values for a record that is to be created.

Example

When you create the infotype Contract Elements (0016), you predefine a period for the probation period. The system creates a date/deadline record so that you can invite the employee to an employee inteview.

The social insurance number does not exist. The system creates a date/deadline record.

62.2Prerequisites

None

Determine which infotype, subtype or field is to trigger a dynamic action.Determine the infotype operation (please refer to the field documentation).You can now set up different actions using a sequential number:P - plausibility checks, that is conditions. If you also use Recruitment, you must make sure that the dynamic action is started for the correct application. You do this, by first calling up the transaction class: PSPAR-TCLAS="A" for Personnel Administration. PSPAR-TCLAS="B" for Recruitment.I - infotype accessesW - infotype valuesF - access for internal or external routinesCalling up an internal routine: just specify the name of the routine, this must be in the infotype's module pool "MPmmmm00". You cannot assign using-parameters.Calling up external routines: specify the name of the routine and, in parentheses, the name of the program in which the routine can be found. You cannot assign using-parameters.For additional information, refer to the documentation for the column variable function part.Further notesCreating a date/deadline recordDynamic actions are normally used for creating date/deadline records. However, the date of the deadline does not have to match the initializing date, but can be varied by a certain time interval.You can add or subtract a number of time units for an outgoing date. The time units "days" (internal 010), "weeks" (011), "months" (012) and "years" (013) are supported.Example: A year after an examination (infotype Internal Medical Service (0028)), the employee is to undergo a subsequent examination.used to store the contents of CSAVE. This means that the individual names of the infotypes are given.SAP recommends that you use the *-workarea for the infotype structure in each case (for example: *P0006).Internal table DYNMEAS: contains the infotype accesses (see indicator 'I').Internal table INITIAL_VALUES: contains the default values for an infotype that is created or copied. (see indicator 'W').

You want to call up a report - for example, the writing of a letter.Include a submit statement for this report in your routine.

Note on creating a batch input session:

Dynamic actions are not processed in a batch input session.In batch input, you must specify the exact sequence of the screens. To ensure this is the case, you must have already programmed the dynamic action checks before you create the batch input session.

To avoid errors only the static actions are processed when you program and process a session. Infotypes that usually only appear in the system as a result of a dynamic action should be updated by calling up the transaction separately. 62.4Result

Create the dynamic action as required.

InfotypeSubtypeFieldFunct.Seq.Ind.Variable function partChar.No.for step00459STF04100IINS,0267,1STP/D00459STF04102WP0267-BEGDA=P0045-BEGDA00459STF04104WP0267-BETRG=P0045-DARBT00459STF04106WP0267-OCRSN='0002'02671SAD06102IINS,0015/D02671SAD06104WP0015-LGART='2SRE'02671SAD06106WP0015-BETRG=P0267-BETRG02671SAD06108WP0015-BEGDA=P0267-BEGDA

63Create Screen Header

63.1Use

In this step you can change the infotype header, that is, the first three lines of the individual and list screens.Header Structure per InfotypeIn the view Header Structure per Infotype (V_582A_B), a header has been assigned to every infotype. It is also determined whether the data is valid from the system date or on the record's validity start date.

Header ModificationDepending on the transaction class (A = Personnel Administration, B = Recruitment) and the country grouping, a header modifier is assigned to this infotype header in the Header Modification view (V_T588I).

Infotype Header DefinitionYou can display any standard SAP infotype and subtype fields in the infotype header. In addition, you can use all applicant infotypes.

When doing so, set up the Infotype Header Definition view (T588J) to suit your requirements.Note, however, that not all infotypes will be relevant to your requirements. For example, the Actions infotype (0000) is only intended for employees. Likewise, the Applicant Actions infotype (4000) only has relevance for applicants.Passport PhotosIn addition to any infotype fields you can also include passport photos of your employees in the infotype header in Infotype Header Definition view (T588J).

In the System Table view (T77S0), determine the document type with which you want to enter the passport photos in the optical archive.Infotype Header Data Selection ControlIn the Infotype Header Data Selection Control view (T588H), you can control the selection date for data in the infotype headers depending on the infotypes/subtypes you want to edit or display.

Field names for screens different from DDIC entryIn the Field names for screens different from DDIC entry view (T588L), you can create your own key fields and long texts.

SAP recommends that you do not use your own key fields, since the documentation for the fields cannot be automatically adjusted to your changes.ExampleYou want to display the pay scale grouping of an employee.

00 - Initial screen of transactions PA20, PA30, PA51 and PA61 PB20, PB30, etc.

10 - Infotype 0000 - Actions Infotype 4000 - Applicant Actions

03 - Infotype 0001 - Organizational Assignment

01 - Infotype 0002 - Personal Data

04 - All infotypes of Time Management

02 - All other infotypesHeader IDs are assigned a header modifier, from which the structure of the respective headers is defined, as well as the HR country modifier and transaction class in table T588I Assignment of Header ID/ Country Grouping to Header modifier.

67Set up Integration with Personnel Administration

67.1Use

In this step, you activate integration between Organizational Management and HR Master Data in Personnel Administration. This guarantees data consistency between the two components.

Example

A person is to be transferred from the position "Controlling administrator" to the position "Manager of controlling". As soon as this transfer has taken place in Organizational Management, the corresponding changes are made in the "Organizational assignment" infotype (0001) in Personnel Administration.

A person can also be transferred between positions in Personnel Administration using the personnel action "Organizational Change". The relevant changes will then be made in Organizational Management.

67.2PrerequisitesUsing the entry "PLOGI PLOGI", you specify the active plan version that is to be the integrated plan version for Organizational Management, Personnel Development, Personnel Cost Planning, Shift Planning and Training and Event Management.

The entry has the function of a main switch: If this entry has the value ' ' (switch "off"), integration is switched off. If a plan version is determined using the switch, integration in this plan version is active for all persons who correspond to the feature "PLOGI" (see below).The entry "PLOGI ORGA" must contain an 'X'. This activates integration between Organizational Management and Personnel Administration via infotype 0001 ("Organizational Assignment").Activating integration has the following effects:

Changes to Organizational Management objects (organizational unit, job, position, cost center) relevant to integration are transferred to Personnel AdministrationChanges to the organizational assignment of employees (infotype 0001) are transferred from Personnel Administration to Organizational Management.Activating integration

The sequence in which you carry out preparations for activating integration depends on which one of the following is true of your enterprise:

You have Personnel Administration set up and want to install Organizational Management for the first time.You have Organizational Management set up and want to install Personnel Administration for the first time.You want to install both applications for the first time.In all three cases, you must ensure that Personnel Administration (infotype 0001) and Organizational Management (organizational assignment of employees) contain consistent data.

If the master data regarding the organizational assignment of the person is available in infotype 0001 (organizational unit, job, position and cost center), you must start report RHINTE00.If Organizational Management data is available, start report RHINTE10. This will create the relevant information in the Personnel Administration tables.

If the organizational assignment (position and organizational unit of a person) is also to be transferred from Organizational Management into infotype 0001 in Personnel Administration, you also have to start report RHINTE30.If you are installing both applications and integration is active, you can only maintain the organizational assignment (infotype 0001) of a person in Personnel Administration using an action. Alternatively, you can assign persons to positions in Organizational Management.

We recommend that you always make organizational changes using an action in Personnel Administration as by doing this, you will also be able to adjust information on working time and salary for this person.

You can build up one of the databases for the two components first without active integration and then proceed as described above.In all three cases, report RHINTE20 can correct any inconsistencies that may occur.To activate integration, you must check or make the following settings in addition to those you have already made in the step "Global Settings in Personnel Management":

1. Basic Settings

Integration switch for organizational assignment (T77S0: PLOGI ORGA)Default position (PLOGI PRELI)Update file PAnnnn (PLOGI PRELU)Department switch (PPABT PPABT)Default value for personnel subarea (PPINT BTRTL)Default value for personnel area (PPINT PERSA)Transfer short or long texts from Organizational Management toPersonnel Administraiton (PLOGI TEXTC, PLOGI TEXTO, PLOGI TEXTS)2. Participating in integration

67.4ResultDefined the following Personnel Calculation Rule and Collective Agreement Provisions for Employee Group and Employee Subgroup.

GroupSemIDValue abbrDescriptionPLOGIEVCCC02Master data action: company code changePLOGIEVCREXGenerate event with entry T77INT (action designat.PLOGIEVEGC02Master data action: employee subgroup changePLOGIEVENBEnhanced integration (X= on, Space= off)PLOGIEVPAC02Master data action for country reassignmentPLOGIORGAXIntegration Switch: Organizational AssignmentPLOGIPRELI99999999Integration: default positionPLOGIPRELUIntegration: PA update online or batchPLOGITEXTCIntegration: transfer short text of jobPLOGITEXTOIntegration: transfer short text of org.unitPLOGITEXTSIntegration: transfer short text of positionPPABTPPABT0Switch: departmentPPINTBTRTLDefault value for personnel subareaPPINTPERSADefault value for personnel area

1 If Positions are not reflecting while creating employees even after creating Organisation structure along with the corresponding positions

Execute the following report program for reflecting

RHINTE10

2 If the employees are not getting reflected under the corresponding positions in the Organisation structure

Execute the following report program for reflecting employees under positions

RHINTE00

vrv asia om&pa

Documents