In this tutorial I shall show you how to configure Actions in PA40.

The IMG steps are:

SPRO > IMG > Personnel Management > Personnel Administration > Customizing Procedures > Actions

1. Define infogroups

Infotype Groups or INFOGROUPS are set of infotypes that shall pop up one after the other when the Action is carried out through PA40. Infogroups is nothing, but actions.

Screenshot from 2014-03-24 16:09:26.png

Double Click on User Group Dependency on Menus and Info Groups

Create entries as below:

Screenshot from 2014-03-24 16:10:29.png

Save the entries and return back. Double Click on Info group

Create Entries as per Menus entred above:

Screenshot from 2014-03-24 16:16:43.png

Enter all the infotypes that needs to populate while hriirng:

Screenshot from 2014-03-24 16:17:34.png

The following operations are used :

COP Copy                                      
DEL Delete                                    
DIS Display                                   
EDQ Lock/unlock                               
INS Create                                    
LIS9 Delimit                                   
MOD Change                                    
INSS Create for Actions is not converted to Change

As while hiring, new record is created so INS operation is used.

Screenshot from 2014-03-24 16:21:42.png

Screenshot from 2014-03-24 16:22:49.png

Screenshot from 2014-03-24 16:24:26.png

Screenshot from 2014-03-24 16:24:55.png

Screenshot from 2014-03-24 16:25:37.png

Screenshot from 2014-03-24 16:26:05.png

Screenshot from 2014-03-24 16:26:42.png

Screenshot from 2014-03-24 16:27:10.png

Screenshot from 2014-03-24 16:27:39.png

Screenshot from 2014-03-24 16:28:05.png

Thus, Infogroups are created.

IGMOD: This is the short form for info group modifier. IGMOD is basically used if you need different kinds of info types to appear in the action sequence for the same personnel action to different employees belonging to the same UGR but to 2 different personnel areas for example. This can also be queried on Employee groups, employee subgroups, company code, personnel subarea etc.

2. Set up personnel actions

Screenshot from 2014-03-24 16:43:06.png

Double click on Personnel Action Types

Screenshot from 2014-03-24 16:44:17.png

Here following columns should be noted:


Customer-Specific Status

Use

The three status indicators have the following meanings: 1. Customer defined: Not used in the standard system. You can use

this indicator according to your requirements. 2. Employment: 0: Employee not with company

1: Employee with company, but inactive

2: Employee with company, but as retiree

3: Employee active in company 3. Special payment: 0: Special payment: no entitlement

1: Special payment: standard wage type

2: Special payment: special wage type

Employment Status

Use

The three status indicators have the following meanings: 1. Customer defined: Not used in the standard system. You can use

this indicator according to your requirements. 2. Employment: 0: Employee not with company

1: Employee with company, but inactive

2: Employee with company, but as retiree

3: Employee active in company

3. Special payment:

0: Special payment: no entitlement

1: Special payment: standard wage type

2: Special payment: special wage type

Special Payment Status

Use

The three status indicators have the following meanings: 1. Customer defined: Not used in the standard system. You can use

this indicator according to your requirements. 2. Employment: 0: Employee not with company

1: Employee with company, but inactive

2: Employee with company, but as retiree

3: Employee active in company 3. Special payment: 0: Special payment: no entitlement

1: Special payment: standard wage type

2: Special payment: special wage type

Feature for checking action sequence

When you create a new action, the system checks whether the features of this action match the features of the previous action. The feature you enter in this field controls performance of this check.

Save the entries and return back.

3. Create reasons for personnel actions

Screenshot from 2014-03-24 16:49:39.png

Screenshot from 2014-03-24 16:50:03.png

In this way Reason for Action can be customised. If no reason is maintained for an action type, the system creates a blank value. If any type of Reason is maintained, then this field becomes a mandatory field.

Save the entries and return back.

4. Change action menu

Screenshot from 2014-03-24 16:51:43.png

Double Click on Action menu

Screenshot from 2014-03-24 16:52:21.png

Enter in the sequence the Actions to be displayed in PA40

Screenshot from 2014-03-24 16:52:56.png

Save the entries

Now the most important step is creating User Group Parameter in SU3 as below:

Go to TCode SU3, in the parameters table enter UGR in Parameter column, and maintain the parameter value as shown below:

Screenshot from 2014-03-24 16:55:01.png

Save the entries.

Go to PA40:

Screenshot from 2014-03-24 16:55:40.png

Regards,

Bhagyashree

To report this post you need to login first.

10 Comments

You must be Logged on to comment or reply to a post.

  1. Nisha S

    Hi Bhagyashree,

    Good effort made. It would make document more good if you explain in detail what are infogroups or infogroup modifiers, why menu groups, in what scenarios the operations like ins, del etc are used, importance of each field in step SET UP PERSONNEL ACTIONS, etc, may not be in detail but atleast in brief.

    (0) 
      1. santosh mohanty

        Hi Sanky,

        Let me share a scenario for the IGMOD feature.

        The scenario is as such, The personnel action need to be configure for one of my client whose branches are located in all most all the states in India. The professional tax applicability is vary from state to state. Few states are there for whom state govt. charge professional tax like west bengal, Andra Pradesh and Odisha etc and for few states it’s not applicable such as Chattisgarh, Delhi and Haryana etc. So client requirement to map the personnel action in such a way that if user is hiring an employee for west bengal the IT588 with subtype for Ptax automaticaally populates and for the employee who belongs to Chattisgarh or Delhi the IT588 infotype with Ptax subtype skiped automatically. User is not going get the infotype details for non- professional states employee hiring.

        At present I don’t ve any system with me. So I asked Bapu Mohapatra to share the configuration document details in scn.

        Thanks,

        Santosh

        (0) 
        1. Bhagyashree Naik Post author

          Hi Santosh,

          Well in that case, you need to mention the Employee Subgroup likewise. IGMOD has the following fields:

          PERSK Employee Subgroup
          ITYGR Infotype Group Number
          MASSN Action Type
          MASSG Reason for Action

          So you cannot add the Personnel Area. For Employee Group, you can follow this scenario as below:

          IGMOD.PNG

          01 and 02 will be your User Group. They shall have respective infotype as required for hiring.

          Regards,

          Bhagyashree

          (0) 

Leave a Reply