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.
Standard settings
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.
Activities
1. User group dependency of the info group.
a) Choose menu category G and the info group.
b) Determine whether the info group is to be dependent on the user group.
c) 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 info group.
2. Info group modifier
a) Maintain the feature IGMOD.
b) Always call up the info group as the first decision rule, otherwise you will need to make entries for the respective return codes for each info group.
c) For additional decision rules, you can call up country grouping, company code, personnel area, personnel subarea, employee group, and employee subgroup.
3. Infotypes of the info group
a) Choose the info group.
b) Assign the operations, infotypes and info subtypes for the user group and the return value of the feature IGMOD.
Read the field documentation for the allowed operations.
Further notes
Please consider the following when using the operation INS for creating:
When carrying out actions, the system checks to see whether an infotype already exists (possibly with the same subtype) when creating infotypes. In this case, the system switches from "Create" to "Change".
It normally only makes sense to use the operation "Create" (INS) for a hiring action. For all other actions, you should use the function code "Copy" (COP) . When copying, existing records with the start date of the action are proposed. If no records exist for the infotype, the system internally switches to "Create".
In some cases, you need to create a new record. When you run the Birth of a child action, the infotypes Personal Data (0002), Family/Related Persons (0021), Additional Payments (0015) need to be processed one after the other. You need to create a new record for the infotype "Family/Related Persons" that is independent of the records that already exist. In this instance, choose the operation "Create for actions" (INSS) . The system does not switch to the "Change" operation MOD.
During a leaving action, you use the operation LIS9 for delimiting records.
Note that the infotypes Actions (0000) and Organizational assignment (0001) must never be delimited.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.