SAP ABAP IMG Activity OHAGOSP0010A3 (Refine Absence Evaluation Scheme)
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 OHAGOSP0010A3 Refine Absence Evaluation Scheme  
Transaction Code S_PH9_46000792   (empty) 
Created on 19990723    
Customizing Attributes OHAGOSP0010A3   Refine Absence Evaluation Scheme 
Customizing Activity OHAGOSP0010A3   Adapt Absence Evaluation Scheme 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name OHAGOSP0010A3    

In this step, you further specify the requirements for your Absence Evaluation Schemes.

Three additional functionalities can be included or excluded for each scheme. These are:

  • Part-time Processing
  • Entitlements in ENTWEEKs
  • Nil Pay Processing

The default setting is that these functionalities are all excluded. If you include these options, they should be specified for all schemes to avoid later rejections in payroll that may occur.

Requirements

  • This step is optional, but if you do not carry out the customising activities within it, the following will occur:
    • If an employee in this scheme is part-time, then they will simply receive the same entitlement as a full-time employee.
    • If an employee is a shift worker and receives an entitlement in Entitlement Weeks (E11), then he or she will be rejected during absence entry checking (if active) and payroll processing.
    • If an employee runs out of entitlement, the remainder of the absence will be paid as if it has been customised according to the Valuation Rule set up on the Absence Subtype definition [Table Attendance and Absence Types (T554S)]. That is, either payable or non-payable as a specific percentage.
  • The Nil Pay Default valuation rule must be set up in Customising, but there is one pre-delivered by SAP.

Standard settings

Recommendation

Activities

Part-time Processing

If the scheme is attached to a mixture of part-time employees and full-time employees, then the part-time employees will receive a proportion of the full-time employees' entitlements.

Here you specify which time units should be compared with an employee's actual hours or days on the Planned Working Time (0007) infotype and their standard hours or days stored in Table T510I. The entitlement factoring can also be based on an employee's hours or days.

There are five options:

  • "No Part Time Processing"
  • Compare HOURS to derive if an employee is part-time and specify the entitlement in HOURS, using HOURS for factoring.
  • Compare HOURS to derive if an employee is part-time but specify the entitlement in DAYS, using DAYS for factoring.
  • Compare DAYS to derive if an employee is part-time but specify the entitlement in HOURS, using HOURS for factoring.
  • Compare DAYS to derive if an employee is part-time and specify the entitlement in DAYS, using DAYS for factoring.

Entitlements in ENTWEEKs

If the scheme is attached to employees with personal work schedules that fluctuate, then it is sensible to use ENTWEEKS to define their entitlements. The entitlement unit Entitlement Week (E11) is directly connected to the employee's Planned Working Time in HOURS or DAYS. The amount of entitlement that employee receives for each of their Entitlement Weeks is based on one of the following five options:

  • Entweeks not used
    • That is, no scheme rule attached to this scheme uses the entitlement unit Entitlement Weeks (E11)]
  • Weekly Working Hours (T510I) uses the hours from table T510I
  • Weekly Working Days (T510I) uses the days from table T510I
  • Weekly Working Hours (Infotype 0007) uses the hours from infotype 0007.
  • Weekly Working Days (Infotype 0007) uses the days from infotype 0007.

The used of entitllement weeks automatically causes the entitlement to be pro-rated when the employee's planned working time changes. So if the base entitlement changes (IT0007 or T510I), then the employee's left entitlement is re-calculated taking into account the fluctuation in the based definition of the entitlement.

Option 2 and 4 make the base entitlements in hours. To accurately process entitlements in hours, the feature GENTT must be customised to process all employees attached to this scheme according to an Hourly Entitlement Calculation.

Options

Option 1 and 3 make the base entitlements in days. To accurately process entitlements in days, the feature GENTT must be customised to process all employees attached to this scheme according to a Daily Entitlement Calculation.

Employee's with entitlements defined in ENTWEEKs must have their Non-Qualifying Days defined as the days that they do not work. Otherwise, the employee will reduce entitlements on non-working days and so run out of entitlement prematurely.

Nil Pay Processing

Once an employee has used all his or her entitlement for a specific absence type, they will automatically move to Nil Pay. This can be treated in one of three ways:

  1. Do not make any customising settings.

    Nil Pay is not processed in payroll and so cannot be reported on. If a whole absence were to receive Nil Pay, for example, the absence would not be split in payroll at all and would retain its original valuation rule from the absence subtype that was entered in absence entry.

  2. Add an infinitely large payment band in the scheme rules that has a valuation rule with a wage type against it that receives no pay.

    The entitlement to Nil Pay will be recorded on the database and can therefore be reported on.

  3. Customise a valuation rule for Nil Pay. Then attach the valuation rule to each of your schemes, using the step in this section.

    This processing is absence grouping independent, that is, all absence groupings will receive the same Nil Pay valuation rule. Generally, you will not need to breakdown Nil Pay absences by absence type as these days do not receive payment and therefore have no employer costs associated with them.

    This third option is the SAP-recommended approach for customising Nil Pay.

Further notes

If your scheme rules do not require you to keep an breakdown of Nil Pay by absence type, just the fact that an absence or part of an absence received Nil Pay means that the same Nil Pay valuation rule can be used for any type of absence when an employee has used all his or her normal entitlements.

Simply use the Nil Pay Default valuation rule provided. No further benefit is derived from creating a customer-specific rule.

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
OHAGOSP0010A3 GB United Kingdom
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG OHAGOSP0010A3 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
VV_T5GPBS29_1 V - View SM30  
History
Last changed by/on SAP  19991202 
SAP Release Created in