Organisational Management

Organisational management is a sub-module which is used to set up the organisational structure as well reporting structure of a company in SAP system. Organisational structure is a structure which runs across organisational units, positions and persons. Reporting structure is a structure which flows across positions only. It is integrated with MM, SD & FICO.

OBJECTS OF ORGANISATIONAL MANAGEMENT (OM):

Objects are used in OM to set up the structures. There are two categories of objects:
Various object categories are derived by SAP. To denote every object uniquely.

1. INTERNAL OBJECTS:

O - Org units
C - Job
S - Position
P - Person
T - Tasks

2. EXTERNAL OBJECTS:

K - Cost center
A - Work center
Q - Qualification

RELATIONSHIPS:

Relationship is an element which is used to link the objects. It should have a 3- character alpha-numerical code and a long text. Relationships are categories in to 2 types,

1. SAP Standard Relationships: These are the relationships which are delivered by SAP. They are denoted by numbers & have a range 000-999.

2. Customer Specific Relationships: These are the relationships which are created by the consulting team where SAP standard relationships are not meeting customer specific requirement. They are denoted by alphabets & have a range AAA-ZZZ.

DIRECTION:

Direction of relationship is an element which is used to denote the direction or flow of the relationship between the objects. Two alphabets are delivered by SAP to denote the direction of relationships among the objects. They are,

A - denotes bottom to top
B - denotes top to bottom

002 relationship is used to link the related object. Ex: O -- O, S --S
003 relationship would be used to link one org unit to position. Ex: O -- S
007 relationship which is used to link one job to position. Ex: C -- S
008 relationship would be used to link one position to person. Ex: S -- P

Organisational plan is used to denote the flow of objects in hierarchy. The objects would be org units, positions and persons. Their can be so many plan versions but always only one plan version can be active. Current plan version would be by default active plan version. Their can be so many statues used for an organisational plan,
1. Proposed
2. Submitted
3. Approved
4. Rejected
5. Active

OBJECT CHARACTERISTICS:

There are characteristics assigned to objects. These are categorized into two:

1. Main characteristics are mandatory characteristics assigned to objects.
Ex: Object Id, Relationships,ect...

2. Additional characteristics denote optional characteristics which can be assigned to an object.
Ex: Object description, Object address,ect...

OBJECT INTERFACES:

Object interfaces are used to set up the organisation structures as well as reporting structure in OM using the objects as well relationships. There are 3 types of object interfaces,

1. ORGANISATION & STAFFING:

This is an interface where the organisational structure is maintained in a user friendly manner. This is very simple in nature & the structure is represented picto-graphically using colorful icons. There are 3 important transaction codes in this interface. They are,

PPOME which is used to maintain the structure.
PPOCE used to create the structure.
PPOSE to display the structure.

PPOME/PPOCE/PPOSE Screen:

1.     SEARCH AREA	3.   OVERVIEW AREA
2.     SELECTION AREA	4.   DETAILED AREA

Search area: It is used to search for the desired object.
Selection area: It is used to choose or select the desired object from the search list.
Overview area: It is used to look at the relationship of the selected objects with other objects.
Detailed area: It is used to maintain or retrieve the details of the selected object.

2. INFOTYPE MAINTENANCE:

It is an interface where infotypes are used to create the objects & maintain the relationships.

1000 - Object - This infotype is used to create the desired object say an org unit, position, etc.,
1001 - Relationship - This infotype is used to create or maintain the relationship of an object to another object.
1002 - Description - This infotype is used to maintain additional details or description for the selected object.
1007 - Vacancy - This infotype is maintained for the object "position". This is used to set up the period for which the position was vacant.
1008 - Account assignment - This infotype is used to assign the account assignment features to an object. For example, for the object say org unit in this infotype we can assign the details like company code, cost center, personnel area & personnel sub-area.
1013 - Employee group/employee sub-group - This infotype is also maintained for the "position". This is used to assign the employee group & sub-group to the position.
1014 - obsolete - This infotype is also maintained for the object "position". This is used to set an position obsolete ( a position which is no more used & removed)

P010 - Maintain org units
P013 - Maintain positions

3. SIMPLE MAINTENANCE:

Simple maintenance is an interface when the organisational as well reporting structure are set up in a simple way. This interface is more user friendly as well very fast in approach. In this interface the organisational structure can be displayed in structural graphics mode in a user friendly way such that non - SAP users can also easily understand the flow of the hierarchy. The reporting structure which flows across the positions can be set up in simple maintenance in a very user friendly manner. There are 2 different options in which the reporting structure could be set up,

1. With in the organisational unit reporting structure is a reporting structure in which the reporting relationships are maintained among the positions belonging to the same organisational unit.
2. General reporting structure is a reporting structure where the reporting relationships are set up among the positions belonging to different organisational units.


INTEGRATION SETTINGS:

Integration between OM and other modules.

1. PLOGI PLOGI: The PLOGI PLOGI entry in table "T77S0" acts as a central switch for integration. If the entry contains a plan version then integration is activated for all employees.

2. PLOGI ORGA: The switch PLOGI ORGA activates integration between OM & PA.

3. PLOGI PRELI: PLOGI PRELI with the value all 9's would mean the default position integrated with PA.

RHINTE XX REPORTS:

RHINTE XX reports are ABAP programmers which are used to set integration between PA & PD/OM. They are mainly used after data conversion or bulk updates or to correct any errors. There are few types in this. They are,

i. RHINTE00: This report transfers PA records into PD positions.
ii. RHINTE10: It prepares integration of PD/OM to PA.
iii. RHINTE20: It creates OM objects in PA tables.
iv. RHINTE30: Bulk updates of infotype 0001.

Number ranges in OM is always internal but during data upload it will be external & after uploading they will be transformed to internal.
The infotype related data for PA module would be residing in PAXXXX tables where XXXX denotes PA infotype number.
The data relating to object in OM would be residing in HRPXXXX table where XXXX denotes OM infotype number.
The transaction code "SE16" & "SE16N" would be used to retrieve information from any infotype table.

CONFIGURATION:

1. Organisational & staffing:

 SAP eassy access à Human resources à Organisational management à Organisational plan à Organisation & staffing à Validity period(given data) à to create go to detailed area & give id in organisation units & text & save à Account assignment à Give company code, personnel area & sub-area & save à Go to overview screeb & select the created org unit & create.

2. Infotype maintenance:

SAP eassy access à Human resources à Organisational management à Expert mode

3. Simple maintenance:

PPOC-OLD - Create

PPOM-OLD - Maintain

PPOS-OLD - Display

 SAP eassy access à Human resources à Organisational managemen à Expert mode à Simple maintenance

Blue - Org unit

Yellow - Position

Green - Person

In Organisation & staffing objects are differentiated by icons.

In infotype maintenance objects are differentiated by transaction codes.

In Simple maintenance objects are differentiated by colors. 

4. Reporting Structure:

i. With in:

 Select the position à Menu bar (Go to) à reporting structure à will get a reporting structure screen à select superior position à menu bar (edit) à Elevate à with in org unit à will get a screen and assign the sub-ordinates & save.

ii. General:

Choose the superior à Menu bar (Go to) à reporting structure à will get a reporting structure screen à select superior position à menu bar (edit) à Elevate à General à will get a screen and assign the sub-ordinates & save.

Recruitment

It is the sub module of SAP-HCM which is used to store the details of the candidates when recruitment process is going on.

APPLICANT NUMBER: 

It denotes a unique key which is used to identify every applicant. It is 8 character numerical code.

APPLICANT NUMBER RANGE:

These are used to assign the numbers to the applicants. There are 2 categories of applicant number range. They are;

      1.      Internal number range: It is a range from which a number is allotted to the applicant by the system.

      2.      External number range: It is a range from which a number is allotted to the applicant by the user.

PB04 is the transaction code used to maintain applicant number ranges.

NUMAP is the feature used to default the applicant number ranges. 

APPLICANT CLASS:

Applicant class denotes an element which is used to denote whether an applicant is internal or external to the organisation. There are 2 applicant classes,

      1.   Internal applicant class: It is an element which is assigned to all such applicants who are internal to the organisation. This is identified by ‘P’.

      2.      External applicant class: It is an element which is assigned to all such applicants who are external to the organisation. This is identified by ‘AP’.

APPLICANT STRUCTURE:

Applicant structure is a structure which is used to create an identity for the applicants in the SAP system based on the recruitment policies. It has 3 elements,

      1.      Applicant group: It is an element which is used to denote the broad classification the applicants based on the recruitment policies. Applicant class must be assigned to the applicant group. Example: Manager, Officer.

      2.      Applicant range: It denotes further classification of the applicant. Example: Sr.Manager, Sr.Officer.

         3. Unsolicited applicant group: It is an element which is assigned to all such applicants who have applied without any vacancy. Example: HR, Finance, IT...

APPL is the administration group for applicants. SAP name is the user name.

PINCH is the feature used to default the administration group.

TRANSACTION CLASS:

 It is an element which is used to denote whether a particular person is applicant or not. The transaction class for applicants is ‘B’.

ADVERTISING MEDIA & INSTRUMENTS:

Advertising media acts as a source to process the resources for the said vacancies. For every advertising medium the element applicant class has to be assigned in order to know which category for applicants are processed by that medium. Advertising instrument denotes an element under the advertising medium which is used to prove the resources.

APPLICANT STATUS:

A status assigned to an applicant in the selection process is called as applicant status. There are 2 statuses,

      1.      Vacancy assignment status: It is a status which is assigned to the applicant with specific reference to the vacancy applied.

      2.      Overall status: It is a status which is assigned to every applicant in general.

Status text: SAP has some standard status text,

1 – In process

2 – To be hired

3 – On hold

4 – Reject

5 – Offered

6 – Offer rejected

Status text is assigned to the vacancy assignment status & overall status.

STATUS REASONS:

Status reasons must be given to every status text in order to know why the status text is performed. Reasons must be linked to the status text in backend.

STATU is the feature used to default the permissibility of a vacancy assigned status or overall status.

PRIORITY:

Priorities can be used in the cases where applicant has applied for more than one vacancy. Top priority will be given to such position where the applicant profile is best matched & followed by least priority for other positions.

TRANSACTION CODES:

PB20 – To display applicant data.

PB30 – To maintain applicant data.

PB40 – To execute applicant actions.

PB04 – To maintain applicant number ranges.

INFOTYPES:

4000 – Applicant actions: This infotype is used to store all actions executed on an applicant through PB04 transaction code.

4001 – Applications: This infotype is used to store all the details regarding the applications sent by the applicants. An applicant can apply with reference to vacancies. In such case this infotype will have the vacancy details for the applications were sent. At times applications would be sent by applicants without any reference to vacancies in such cases this infotype will have the unsolicited application group details.

4005 – Applicants personnel number: This infotype is maintained only for such applicants who have been selected & have been hired as employees in personnel administration module. This infotype is used to store the personnel number assigned to an applicant in Personnel administration (PA) module.

0139 – Employees applicant number: This infotype is relating to personnel administration. This is also maintained in personnel administration but it is used in context with recruitment sun module. It is used to store the applicant number allotted in recruitment module to this employee.

The features used for the integration between personnel administration and recruitment modules are,

PRELI it is used for integration of internal applicants. The return value of this feature is (*). If (*) is maintained as a return value the integration is active.

PRELR it is the feature for integration of applicant to employee. The return value of this feature is (*E) when this value is maintained the integration in active.

CREATE POSITIONS:

This node is not used commonly. All the positions usually created in organisational management (OM) module. With the integration settings being active between OM & recruitment as well as OM & PA positions created in OM can be seen as well as used in PA as well as recruitment sub modules. By any chance if positions are to be created in recruitment module the said positions can be created in this node (create position). In this note there is a column called OM. If the value of this column is ‘P’ for any position then it is to be taken that all such positions are maintained in OM module & if column left blank such positions are maintained in recruitment module.

APPLICANT ACTIONS:

All the applicant actions taken through PB40 transaction code would aim at changing the overall status of the applicant.

Initial entry of basic data: It is the action to be executed on the applicants to have them created in SAP recruitment sub module. The overall status for such applicants created would be set to ‘1’.

Enter additional data: This action would be executed on the applicants in order to create additional details of the applicant. The additional details might be related to vacancy assignment, educational qualifications & previous employer details of the applicant. In this action the overall status will be set to ‘1’. This is the action where the vacancy assignment statuses are assigned to the applicant. STATU feature would be called in the background by the system in order to check whether the vacancy assignment status is allotted to the applicant are permitted under the overall status.

Put applicant on hold: This action is used to assign the overall status of the applicant to ‘3’.

Reject applicant: This action is used to set the overall status of the applicant to ‘4’. In such cases the vacancy assignment statuses (if any) will also be required to be set as ‘4’.

Offer applicant: This action would be executed in order to set the overall status of the applicant to ‘5’.

Offer rejected: This action is a particular action will be uses to set the overall status of the applicant to ‘6’.

Prepare to hire: This action would be executed on all such applicants for whom the offers were rolled out & the same are accepted by the applicants. The overall status of the applicant by this action would be set to ‘2’.

If any applicant selected, offered & the same has been accepted by the applicant the next activity would be to hire this particular applicant as an employee. To hire as an employee we need to move to transaction code PA40, when this activity is being executed enough care has to be taken that applicant is not locked in any if the screens. By any chance if the applicant is locked the data cannot be transferred for that applicant from recruitment to PA module. In the PA40 screen the standard action “Hire applicant” has to be executed. While executing personnel number field should be left blank as well as start date field should also left blank in the PA40 screen.

The system identifies “hire” action in PA module as initial hiring action but it identifies “hire applicant” as initial hiring & data transfer from recruitment. For the action “hire” system will not look for applicant data to be transferred but for the action “hire applicant” it looks for the applicant data in recruitment module to be transferred to PA module. This is because of the value in the field “function character (F)” for action mentioned against an action type while setting up the personnel action. If the value is mentioned as ‘7’ in this field system would consider that action as the action to have data transfer from recruitment & if the value in this field for an action is set as ‘1’ system considers the action as initial hiring action in PA module and will not lock for data transfer from recruitment sub-module.

NAVIGATION:

SPRO à Reference IMG à Personnel management à Recruitment à Basic settings à Create number ranges for applicants numbers à Edit & Save à Choose number ranges à set up number ranges à Back & work force requirement & advertisement à Create media à New entries & Save à Create recruitment instruments à New entries & Save à Back & Applicant administration à Create personnel officer à New entries & Save à Applicant structure à Create applicant groups à New entries(give 1 character code) & Save à Create applicant ranges à New entries & Save à Create unsolicited application group à New entries(give 3character code) & Save à Back & Applicant selection à Applicant status à Change status text( standard status text & not mandatory to change, if customer needs more statuses oher than these than can be created) à Create status reason à New entries & Save à Back & Set permissible status reasons for each applicant status à New entries & Save à Set permissibility vacancy assignment status for each over status (STATU feature) à Create priorities for vacancy assignment.

Personnel Administration

It is a sub module of SAP-HCM whis is used to store and maintain the employee master data.
Personnel number denotes a unique numerical key which is used to identify every employee. It should be 8 numerical character.
                                  00000001 - 9,99,99,99

INFOTYPE - It denotes information type. Technically speaking infotype as logical grouping of data fields. It should have a 4 character numerical and a long text.
It might have sub type. Few infotypes depending on the nature of information getting saved would have sub types.

SUBTYPE - It denotes further classification of an infotype, It includes validity period which will have start and end date.

Infotype is classified into 2 types,

1. SAP Standard Infotypes -  These are the infotypes delivered by SAP. The ownership rights or propitiatory rights of such infotypes would be rested with SAP.

2.  Customer Specific Infotypes - These are the infotypes which are created by the consulting team in order to meet customer specific requirements where SAP standard infotypes are not. Thes infotypes are created by SAP - HR ABAPers.

SAP Standard infotypes are divided into 2 types. They are,

1. International Infotypes - These are the infotypes which are used globally.
Ex, Personnel details, Address details which are common in all countries.

2. country specific Infotypes - These are the infotypes delivered by SAP to meet country specific requirements.
Ex, Payroll, Tax, PF...ect, which are specific to a particular country.

Ranges of Infotypes -

- Personnel administration and payroll related will range in between 0001 - 09XX
- Organisational management, Training, Personnel development will range in between 1XXX - 19XX
- Time management will range in between 2XXX - 29XX
- Recruitment will range in between 4XXX - 49XX
- E-Recruitment will range in between 5XXX - 59XX
- Customer specific will range in between 9XXX - 99XX

COMMON INFOTYPES -

1. Action Infotype (0000) - This is used to store the details of all the actions which are executed on an employee through PA40 transaction code.

2. Organisational Assignment (0001) - This infotype is used to store the details regarding assignment of the employee to the organisation. This is the infotype where we can find the elements of structures assigned to an employee.

3. Personal Details (0002) - This infotype is used to store personal details of an employee.

4. Address (0006) - This infotype is used to store address details of an employee.

5. Planned working time (0007) - This infotype is used to store the details regarding the scheduled working hours, holidays belonging to employees.

6. Basic pay (0008) - This infotype is a very important infotype for payroll. The details regarding standard components of salary for an employee would be stored in this infotype. only payments are stored in this infotype nut not deductions.

7. Bank details (0009) - This infotype is used to store the details regarding bank name, bank account no., to which the employee salary is credited.

8. Recurring payments and deductions (0014) - This infotype is used to store the details regarding all payments and deductions which are recurring in nature.

9. Additional payments (0015) - This infotype is used to store the details regarding payments & deductions which are non-recurring in nature. Ex: Bonus, Overtime

10. Contract details (0016) - This infotype is used to store the details regarding contract elements of an employee.

11. Monitoring of tasks (0019) - This infotype is used to store the details regarding all such tasks which are to be taken on an employee at a future date.

12. Family dependents (0021) - This infotype is used to store the details regarding family members of an employee.

13. Skills (0022) - This infotype is used to store the details regarding the skills of an employee.

14. Previous employer details (0023) - This infotype is used to store the details regarding the previous employer of the employee.

15. Qualifications (0024) - This infotype is used to store the details regarding qualifications of an employee.

16. Appraisals (0025) - This infotype is used to store the details regarding appraisal results of an employee.

17. Date specification (0041) - This infotype is used to store the details regarding important dates belonging to an employee.

Functions used to maintain HR master data:

1. For creating new data:

i. CREATE: It creates new records. History (old information) is maintained.
ii. COPY: It creates a new record by copying the existing record. History is maintained.

2. For maintaining data:

i. CHANGE: It changes the existing information. History is not maintained.
ii. DELIMIT: It delimits the end date of an existing record. History is maintained.
iii. DELETE: It deletes the existing record. History is not maintained.

3. For Seeing the data:

i. DISPLAY: It displays the most recent/current record.
ii. OVERVIEW: It gives a snapshot of all the records.

To perform all these functions go to PA30 transaction code.
To search employee names with their starting letter then we need to type as (A*).


PERSONNEL NUMBER RANGES:

It denotes the ranges which are created to have the personnel numbers allotted. There are 2 categories of personnel number ranges in SAP-HCM. They are;

1. Internal personnel number range - It is a range from which a number is allotted to the employee by the system.

2. External personnel number range - It is a range from which a number us allotted to the employee by the user.

PA04 is the transaction code which is used to maintain personnel number ranges. Two important points have to be taken into consideration when the number ranges are being set up. They are;

i. No two ranges can have the same code.
ii. No two ranges can overlap.

Current number denotes the last assigned number. It could be maintained by the system & is only for the internal personnel number ranges. Numbers would be allotted in a sequence in internal personnel number ranges.

Ext. field in the screen PA04 would enable the user to differentiate an internal number ranges from the external number range.
- If this tick box is ticked system counts that particular number range as external number range.
- If this filed is left blank system counts the same as external number range.
Change status option in PA04 screen would enable the user to change the current number value.

TIME CONSTRAINT CLASS:

Time constraint class is an element which is assigned to the infotypes as well subtypes. For all SAP standard infotypes this time constraint class is predetermined. The consulting tea, will have the option of allotting time constraint class to the customer specific infotypes which are created by the consulting team to meet customer specific requirements. The time constraint class is an element which controls the reaction of a system whenever an infotype/sub-type is maintained.

Three major time constraint classes:

Out of the three time constraint classes only one will be assigned to an infotype/subtype. The nature of information getting stored in an infotype/subtype would denote which time constraint class has to be assigned.

1. Only one record must exist for a given time period. Gaps are not allowed.
2. Only one record must be exist for a given time period. Gaps are allowed.
3. Many records can exist for a given time period. Gaps are allowed.

Navigation to set up time constraint class:

SPRO à IMG personnel management à Personnel adminstration à Personnel data à Family à Personnel data à Define family types

FEATURE:

Features are used to default values automatically. Documentation is an option which gives more details about a particular feature & its purpose. Attributes section gives more information about technical details of a feature. Structure gives the list of fields which can be used for decision making in order to default a return value or values. Decision tree is a tree structure which is used to set up the conditions in order to default a return value or values.
After setting up press ok. If any error is there then the system will give a pop-up and we can see pink color where there is error. To avoid this we will have few options,

1. Check: This option in any feature would enable the user to check for any inconsistencies while setting up the conditions.
2. Save: This option in an feature would enable the user to save the settings made in a feature.
3. Activate: This option would enable the user to save as well activate the changes made.

INFOGROUP:

Infogroup denotes group of infotypes which is processed when a personnel action is executed. For every corresponding action there should be an infogroup created.
Usergroup denotes a parameter which is used to create & save the user specific settings.

Creating Personnel actions:

For HA(Hiring actions) it includes 3 status,

1. Customer specific status
2.  Special payment: If any employee having any special payments like if an employee goes on global assignment then he will have special pay.
3. Employment specific status: It includes,
0 - Employee withdrawn: It is used when a person is leaving the company.
1 - Employee with company but inactive: It is used when a person is in long leave.
2 - Employee with company as a retiree: It is used when a company is giving pensions to the employees.
3 - Employee active in the company
Reasons are created for knowing why the actions are made.
Action menu - standard action menu is 01.
User parameter (Transaction code - SU3) - To show only user specific actions & hide standard actiuons.

Creating customer specific actions:

1. Create Infogroup: If 2 actions must be created then 2 infogroups must be created.

2. Create personnel actions & link the infogroup with respective action.

3. Create reasons why those actions are made.

4. Finally, to show the actions created on the PA40 screen then action menu is used to show them & save them.

Navigation to create Infogroup:

SPRO à SAP Refernce IMG à Personnel management à Personnel administration à Customising procedures à Actions à Define infogroups à user group dependency on menu & infogroups à Copy required actions & edit as required à Back and infogroup à Work area (give infogroup name) à New entries à Create infotypes & save à Back à Set up personnel actions à Personnel action types à Select & copy required action & edit, save & back à Create reasons for personnel actions à New entries or copy the required & edit, save & back à Change action menu( give standard action menu i.e., 01) à New entries à Edit, save & back à To show only customer specific action then go to /o SU3 à Parameters & edit & save.                                             

INFOGROUP MODIFIER:

Infogroup modifier is an element which is used to assign more than one set of infotypes to an infogroup which is linked to a personnel action. To default infogroup modifier we need to use a feature i.e., IGMOD.

EXECUTING ACTIONS:

All the actions in SAP-HCM must be executed through PA40. All the actions executed must have apersonnel number mentioned in PA40 transaction code. But only for hiring action the personnel number in PA40 screen must not be mentioned because at that particular point of time it is not sure weather the personnel number will be allotted from an internal /external personnel number range.

INFOTYPE MENU:

It denotes group of infotypes grouped together for the purpose of maintaining or displaying master data. These infotype menus would facilitate the user to have the list of infotypes in one place which he/she accesses. We can configure our own infotype menus to meet customer specific requirements where SAP standard infotype menus are not meeting.

Navigation:

SPRO à Personnel management à Personnel adminstration à Customising procedures à Infotype menus à User group dependency on menus & infogroups à New entries à Save & back à Infotype menu à Give menu name à New entries à Save & back à Determine choice of infotype menus à Infotype menus à New entries à SU3 à Parameters & edit & save & back.

ADDITION ACTIONS (0302):

Additional actions infotype is a particular infotype which is created automatically by the system based on certain conditions & is not created by the user. This is an additional infotype or a secondary infotype attached to primary infotype. Addition action infotype is the secondary infotype to actions infotype. Technically speaking this infotype will not have a structure table assigned to it. This infotype cannot be displayed or maintained directly. The details of the infotype can be viewed in the primary infotype i.e., actions infotype. The information in this infotype will be created by the system only when this infotype is activated. System will create the data in this infotype only when it is active & only when more than one action is executed on an employee & on the same date where employment specific status is not changed by the actions executed. Go to view table T77SO & activate the additional actions. Execute reports for the particular employee. Go to personnel actions screen & change field U0000 & U0302 and tick then they will be activated. 

Navigation:

SM30 à V-T77S0 à Select additional actions (EVSUP) à Select admin group à in the value abbr column give one to activate à Back & SPRO à Reference IMG à Personnel management à Personnel administration à Customising procedures à Actions à Set up personnel actions à Activation additional actions à or go to SA38 transaction code à AAC à Personnel number

The abbreviation EVSUP acts as the switch for additional actions. If the value is placed as '1' for this abbreviation the additional actions functionality is 'activated' & if the abbreviation is left with 'blank' value the additional actions functionality is 'deactivated'. The program is "RPUEVSUP" which is used to activate additional actions for the desired employees. "SE38/SA38" is the transaction code which is used to execute any program.

Testrun & execute à Personnel actions types à tick U0000 & U0302 to activate & Save

Program "RPUUEVSUP" can be executed in 2 modes,

1. Test run 

2. Live run 

Test run is a dummy run which can be used by the users to cross check whether the result is expected. When any program is executed in the test mode changes will not be updated by the system.

Live run denotes any update made when any program is executed in this mode the changes are updated to the data base.

SCREEN MODIFICATION:

How to view screen number?
Select any field in the infotype & click on help --> Technical information --> Screen number.

Navigation:

SPRO à Reference IMG à Personnel management à Personnel adminstration à Customising user interfaces à Change screen modification

After going to screen modifications the correct entry should be selected for which the changes are to be made. In the example, changes are to be made for the infotype 2 i.e., personal details & relating to germany. With the technical information of the infotype 0002 we can learn the screen number for germany is(2001) so now enough care should be taken in the screen modifications mode that changes are made to the module pool program of infotype 0002 for germany.

Select the entry with the vale (MP000200) in the module pool program filed & the value (2001) in the field alternate (Alr) screen --> go to details --> do changes for the particular changes & save.

DYNAMIC ACTIONS:

Dynamic actions are the actions which are executed automatically by the R/3 system during the maintenance of the infotypes. You may set up your own dynamic actions in the table T588Z in order to trigger activities automatically which are linked to infotype maintenance. 

Navigation:

SPRO à Reference IMG à Personnel management à Personnel administration à Customizing procedures à Dynamic actions

Fields in dynamic actions:

1. Infotype: This specifies the infotype for which the dynamic action is maintained & triggered.

2. Subtype:  This field is used to narrow down the focus of the dynamic action to a subtype of the specified infotype.

3. Field name: The dynamic action is triggered when a maintenance function is performed on a particular field. 

4. Function character: It specifies the various maintenance operations to which the dynamic action being set up must respond. The standard function given by SAP are,

02 - Change

04 - Create 

06 - Create & change

08 - Delete 

10 - Change & delete

12 - Create & delete

Dynamic actions are never triggered for the display function,

5. Sequence number: This field refers to the sequence number in which order the logic should flow.

6. Step indicator: It specifies the particular type pf actions. No dynamic action is executed without a step indicator specified. The following are the values allotted,

P - Plausibility check which allows you to check for a specific condition

I - Calls an infotype for processing

W - Called after the I statement & used to assign values for the fields while creating or copying another infotype through I statement.

F - Calls a form routine (sub routine in ABAP) during your action

V - Lets you treat collectively a number of fileds for which you want to set up a dynamic action.

M - Sends SAP office mail.

7. Function part: The variable function part along with the step indicator forms the core part of the dynamic action. It specifies the processing logic of the dynamic action being triggered. The coding is done and the system knows to follow the steps as AND or OR. If the sentence is left blank then it is left blank & /x indicates 'OR'.

Reports: 

HRM --> Personnel management --> Administration --> Infosystem --> Reports.