Hierarchy
SAP_HRCGB (Software Component) Sub component SAP_HRCGB of SAP_HR⤷
PY-GB-PS (Application Component) Öffentlicher Dienst⤷
P08P_ABSC (Package) HR Public Sector Great Britain Absence Evaluation Customing
IMG Activity
| ID | OHAGOSP001B02 | Define Absence Subtype Mapping |
| Transaction Code | S_PH9_46000824 | (empty) |
| Created on | 19990808 | |
| Customizing Attributes | OHAGOSP001B02 | Define Absence Subtype Mapping |
| Customizing Activity | OHAGOSP001B02 | Define Absence Subtype Mapping |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | OHAGOSP001B02 |
Use
In this step, you create the cross references from your old (manual)t o your new (automatic) Occupational Absence solution using the table Absence Evaluation Cross Reference (T5GPBS31).
Requirements
The customising of your old and new absence types in table Attendance and Absence Types (T554S) must be complete before you start to cross reference. Also you must have set up any absence groupings, payment bands, non-qualifying rules and from-where rules (which include any necessary waiting days specification).
Standard settings
The table T5GPBS31 is delivered empty. A one-off population of the table of all your absence subtypes is possible. This simply fills the table T5GPBS31 with the key fields of the table T554S. This is done by choosing Import (you find the Import pushbutton at the buttom of the table T5GPBS31). After entries are made in table T5GPBS31, the Import pushbutton will be hidden. To redisplay this pushbutton, all table entries must be deleted. Once the import is complete, you can maintain the table just like any other time-dependent view.
Note:
Do not try to add new records to the table T5GPBS31, this is not supported.
We recommend that you use new absence subtypes. This allows you to clearly identify the people that have moved to the new solution and when they moved. It also makes mapping simpler and customising the new absence subtypes much simpler.
Activities
To start your cross referencing, you must:
- Run the import
- Delete all unwanted subtypes from the table
- Customise only the remaining entries
- Delete unwanted time splits
- Choose Expand/Collapse to ensure that the only records in the table are the entries that must be and have been cross referenced
Example
You may decide to completely start again with new absence subtypes or wish simply to reconfigure the existing 100% subtype to work for the new absence evaluation scenario from a specific date. However, the latter option means that you must migrate all your employees to the new solution on exactly this date, which may not be practicable.
In either case, the old (manual) subtypes for reduced pay (for example 75%, 50%, 25%, 0%) must be configured in the table T5GPBS31. So must the old 100% pay subtype, however if it has been delimited, then care should be taken that the correct date range is being maintained in the view.
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| Mandatory / Optional | 1 | Mandatory activity |
| Critical / Non-Critical | 1 | Critical |
| Country-Dependency | I | Valid for countries specified |
| Customizing Attributes | Country Key | Country Name |
|---|---|---|
| OHAGOSP001B02 | GB | United Kingdom |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | OHAGOSP001B02 | 0 | HLA0009562 | Absences |
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 |
| V_T5GPBS31 | V - View | SM30 |
History
| Last changed by/on | SAP | 20020123 |
| SAP Release Created in |
