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 | OHAGOSP0010A4 | Create Absence Evaluation Scheme Rules |
| Transaction Code | S_PH9_46000822 | (empty) |
| Created on | 19990806 | |
| Customizing Attributes | OHAGOSP0010A4 | Create Absence Evaluation Scheme Rules |
| Customizing Activity | OHAGOSP0010A4 | Create Absence Evaluation Scheme Rules |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | OHAGOSP0010A4 |
In this step, you create the different rules for your Absence Evaluation Schemes.
Requirements
You must already have set up your scheme identifiers and any other Background Customising that is necessary for your schemes and was not released as standard by SAP.
Standard settings
The SAP standard schemes are as follows:
- 08SALARY for salaried employees
- 08WAGES for waged employees
- 08CASUAL for casually employed employees.
These can be used as an example of a possible scheme.
Example
Step 1: Seniority and Age Bands
Your scheme has two specific seniority bands but is not age-specific:
- "Starters" up to 6 months
- "Others" over 6 months
Set up the two rules for your scheme:
- One with a seniority of 0 - 5 months and no age band
- One with a seniority of 6 - 99999 months and no age band
For each rule, enter a period of validity that has a date far enough in the past to incorporate all your absence history (infotype 2001), for example 01.01.1990, and also a date far enough in the future as not to require regular updating, for example 31.12.9999.
Note:
Each rule controls each of your different seniority or age bands, which are stipulated in the rules of your scheme. The ranges of the bands are inclusive, that is, a seniority band of 0 - 1 years implies that if an employee has a seniority of 1 year and 355 days, then they will still be within this band. The calculation is performed using the time unit specified, rounding down to the nearest whole number.
Step 2: Enter the Entitlement Bands for each Scheme Rule
Select a specific scheme rule and then double-click on Entitlement Bands in the Dialog Structure. This will display the entitlement bands for the scheme and rule number selected.
Create entitlement bands for each absence grouping, payment band and rollback periods necessary to fulfil the requirements of your scheme for that seniority and age band.
Step 2 Part 1: Entitlement Amount & Unit
The Amount field allows any integer amount up to 999999.
The Unit field only allows units that have been set up as available to be used as Entitlement Amount units (Table T5GPBS28).
If the unit is not days or entitlement weeks, then the unit must have either been entered in the Time Unit Multiplier (Table T5GPBS24) or have been coded in the customer exit "EXIT_SAPLHRGPBS_OSP_OMP_LEN".
Step 2 Part 2: Absence Grouping
The PS grouping field (personnel subarea grouping for absence types) simply allows more flexibility when customising the absence groupings. Normally this is the same as the country grouping (MOLGA).
The Absence Category field is used for grouping different absence subtypes, so that they all reduce one entitlement.
The Abs. Cat. Exclusive indicator is used to specify how strict the check for grouping different absence subtypes should be. If the indicator is set, both characters are checked. If not, then only the first character is checked.
When processing an absence, the lines in the relevant seniority banding are ordered by priority and then checked to ensure they match the absence grouping criteria. The personnel subarea grouping for absence types is derived for the employee and then the absence category is derived from the customising of the absence subtypes (Table T554S-ABSTY). The comparison between the absence and each line in the rule is performed to check which lines are applicable to this absence.
Step 2 Part 3: Payment Band
The Priority field, as explained above, is simply to make sure that an order is given to the processing of applicable payment bands, that is, Full pay is before Half pay and so on.
The Payment Band field is directly related to the way that this entitlement in this line will be paid. The valuation rules that are available for selection in this view cluster are set up in the customising of the Valuation Rule Groupings (Table T5GPBS27). The valuation rules are customised using Table T554C and mostly create wage types during operation of the payroll function PAB, which can be configured to pay the correct amounts.
Step 2 Part 4: Reference Period
The How Far Bck/Fwd field is simply to select the Check Window Start Rule.
The From Where field is simply to select the Check Window End Rule.
Once both rules have been specified, the window to check for used entitlement is fully defined for this line.
The Non-Qualifying Days field specifies which days during an absence do not qualify to reduce the employee's entitlement and which do.
The Warning Period field is used purely for message generation. During absence entry in infotype 2001, in the Entitlement Forecast Report and during payroll, this field is checked. If the amount of entitlement will be used up within the warning period, by this or a later absence, then a warning message is issued.
The two Entitlement Limits fields specify a futher limiting factor to the normal Reference Period that is checked to decide if this Entitlement Band is applicable or not. The first should be the most often limit to be "hit" and will not create a warning message. The second should be the rare limit to be "hit" and will automatically create a warning message.
Note:
These two fields are normally used for the One Year In Four rule which is explained in more detail in the IMG step Entitlement Limits.
Step 3: Check the Schemes
The Scheme Overview option has been added to each screen of the view cluster to aid in the checking of your schemes. It provides you with an overview of all the scheme rules at once.
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 |
|---|---|---|
| OHAGOSP0010A4 | GB | United Kingdom |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | OHAGOSP0010A4 | 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_T5GPBS23_CL | C - View cluster | OH02 |
History
| Last changed by/on | SAP | 20000326 |
| SAP Release Created in |
