SAP ABAP Data Element HRWPC_PCR_PCR_EEGRP (Employee Grouping for Change Requests)
Hierarchy
☛ SAP_HRGXX (Software Component) Sub component SAP_HRGXX of SAP_HR
   ⤷ EP-PCT-MGR-HR (Application Component) Business Package for Manager Self-Service (HR)
     ⤷ PWPC_MAN_PERSCHANGEREQUEST (Package) PWPC_MAN_PERSCHANGEREQUEST
Basic Data
Data Element HRWPC_PCR_PCR_EEGRP
Short Description Employee Grouping for Change Requests  
Data Type
Category of Dictionary Type D   Domain
Type of Object Referenced     No Information
Domain / Name of Reference Type HRWPC_PCR_PCR_EEGRP    
Data Type CHAR   Character String 
Length 4    
Decimal Places 0    
Output Length 4    
Value Table TWPC_PCR_EEGRP    
Further Characteristics
Search Help: Name    
Search Help: Parameters    
Parameter ID   
Default Component name PCR_EE_GROUP   
Change document    
No Input History    
Basic direction is set to LTR    
No BIDI Filtering    
Field Label
  Length  Field Label  
Short 10 EE Group 
Medium 15 PCR EE Group 
Long 25 PCR Employee Group 
Heading 10 EE Group 
Documentation

Use

In the Change Request for Employee Data iView you can use employee groupings to create employee-specific assignments between request scenarios and request types.

You group the employees independently of the scenarios. That means that the grouping is valid for all scenarios.

In the Business Add-In HRWPC_PCR_EEGRP (Adjustment: Asignment Employee - Employee Grouping) you can create customer-specific employee groups for change requests.

If all request scenarios are valid for all employees without restrictions, you do not need to create any more employee groupings.

In that case you use the standard employee grouping SDEF.

Request types bundle the scenarios according to time and employee grouping. A request type can therefore group together different country-dependent change requests, or take into account limited validity of individual scenarios.

The system shows the manager the request types in the iView Change Request for Employee Data.

Examples

  1. You only want to use the Promotion scenario in the USA and Canada. In that case you must only create one employee grouping (for example USCA). For the employee grouping USCA you assign the Promotion scenario to the Promotion request type. In this example you must not use the grouping SDEF.
  2. You want to use different forms for the Special Payment scenario, for example one form for Germany and one form for the other countries. In that case you define an employee grouping (for example GER0) and two scenarios that reflect the two different forms. You define the request type Special Payment and assign to it the scenario Special Payment Germany for the employee grouping GER0, and the scenario Special Payment Others for the employee grouping SDEF. This assignment remains valid even if other employee groupings exist. If - as described in the first example - you need another employee grouping for another Promotion request type (for example USCA for USA and Canada), you can use the employee grouping SDEF. In this example, American and Canadian employees then fall automatically under the employee grouping SDEF.
  3. You want the Early Retirement Request scenario to only be valid for employees of or above a certain age. In that case you must create an employee grouping (for example 55+) for older employees. You assign the Early Retirement Request scenario to the Early Retirement Request request type only for this employee grouping. Here, complications can arise if an employee grouping (for example GER0 from example 2) already exists. Then you need a total of three groupings: GER0 for younger German employees, GER1 for older German employees, and 55+ for older, non-German employees. To the Special Payment request type from example 2 you assign the Special Payment Germany scenario for the employee groupings GER0 and GER1, and the Special Payment Others scenario for the employee group SDEF. To the request type Early Retirement Request, you assign the Early Retirement Request scenario for the employee groups GER1 and 55+ .
  4. On 01.01.2002 you want to add a new field to the Position Change form. In that case you create a new scenario, Position Change (as of 2002) . You delimit the request type Position Change on 01.01.2002 and create the following validities for the employee grouping SDEF:
    • For the Position Change (up to 2001) scenario, you specify validity until 31.12.2001.
    • For the Position Change (as of 2002) scenario, you specify validity as of 01.01.2002.

All change requests created before 01.01.2002 now use the previous form, while requests created as of 01.01.2002 use the new form.
History
Last changed by/on SAP  20030325 
SAP Release Created in 1999_1_46C