SAP ABAP IMG Activity CCE_00_GP_006 (Change Grouping Reasons for Personnel Assignments)
Hierarchy
SAP_HRRXX (Software Component) Sub component SAP_HRRXX of SAP_HR
   PA-CE (Application Component) Concurrent Employment
     PCCE_GROUPINGS_IMG (Package) IMG for Concurrent Employment Grouping
IMG Activity
ID CCE_00_GP_006 Change Grouping Reasons for Personnel Assignments  
Transaction Code S_AL0_96000485   (empty) 
Created on 20011204    
Customizing Attributes CCE_00_GP_ATTR   Attribute of the Editor for Personnel Assignment Groupings 
Customizing Activity CCE_00_GP_006   Create Grouping Reason for Personnel Assignments 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name CCE_00_GP_006    

Use

In this IMG activity, you check the grouping reasons for personnel assignments contained in the standard system.

A grouping reason can be assigned to a grouping context. You can display the documentation about this grouping context or the grouping context itself in the Class Builder. To evaluate the grouping context, you must create your own grouping rule and assign it to the relevant grouping reason.

You can assign other grouping rules than those defined in the standard system to grouping reasons that have the Changeability of assignments to a grouping reason indicator flagged. You can make this assignment in the IMG activity Change Standard Assignment of Grouping Rules to Grouping Reasons.

Requirements

Standard settings

The standard SAP system contains cross-country and country-specific grouping reasons. The grouping reasons are assigned the following namespaces:

SAP namespace

  • The name of cross-country grouping reasons begins with XX.

    The XALL (Person), XMOL (Country Grouping) and XNON (None) grouping reasons are exceptions.

  • The name of grouping reason in Personnel Time Management begins with TI.
  • The name of grouping reasons in Benefits begins with XXB.
  • The name of country-specific grouping reasons begins with the ISO code of the country, for example US.

Customer namespace

The name of customer-specific grouping reasons must begin with the letter Z.

Activities

Check the grouping reasons and consider the following aspects in particular:

  • In which areas would you prefer to implement Concurrent Employment ? In other words, which grouping reasons are particularly important for you?
  • For which areas do you not require any special groupings? In other words, which grouping reasons do you want to assign to one of the grouping rules XNON, XALL or XMOL?
  • Which grouping reasons can you assign to grouping rules other than those defined in the standard system?

You should only create your own grouping reasons in the following cases:

  • If you create a customer-specific infotype for Personnel Administration, you must determine for concurrently employed persons the personnel assignments for which this infotype's data should be kept the same. To do so, assign a grouping reason to your infotype to determine which grouping rule the system should use for this. If the grouping of personnel assignments for your infotype should proceed differently to the standard system, you must create your own grouping rule. You must also create your own grouping reason since the grouping rule is assigned to your infotype using the grouping reason.
  • If you create a customer-specific function or operation for Personnel Time Management or Payroll, you must define how the system should group the personnel assignments of a concurrently employed person for processing using this function or operation. To do so, assign a grouping reason and a grouping rule to your function or operation as you did for the customer-specific infotype. In this case, you also require your own grouping rule and your own grouping reason if you want to group the personnel assignments differently to the standard system.

To be able to assign a grouping rule to a customer-specific grouping reason, you must select the Changeability of assignments to a grouping reason indicator.

Example

Business Attributes
ASAP Roadmap ID 105   Define functions and processes 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 2   Non-critical 
Country-Dependency A   Valid for all countries 
Maintenance Objects
Maintenance object type C   Customizing Object 
Assigned objects
Customizing Object Object Type Transaction Code Sub-object Do not Summarize Skip Subset Dialog Box Description for multiple selections
T7CCE_GPREASON S - Table (with text table) SM30  
History
Last changed by/on SAP  20020415 
SAP Release Created in 470