SAP ABAP IMG Activity OHAIEOSP00103D (Activate the Customer Exit for Time Unit Multipliers)
Hierarchy
SAP_HRCIE (Software Component) Sub component SAP_HRCIE of SAP_HR
   PY-IE (Application Component) Ireland
     P11C (Package) HR customizing: Ireland
IMG Activity
ID OHAIEOSP00103D Activate the Customer Exit for Time Unit Multipliers  
Transaction Code S_AHR_61019397   (empty) 
Created on 19991202    
Customizing Attributes OHAIEOSP00103D   Activate the Customer Exit for Time Unit Multipliers 
Customizing Activity OHAIEOSP00103D   Activate the Customer Exit for Time Unit Multipliers 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name OHAIEOSP00103D    

In this step, you can create the code to handle your own rollback period units and entitlement amount units. This code will be used when a time unit does not have a time unit multiplier on the Time Unit Multiplier table T5GPBS24.

Example

Why this exit may be necessary

If the time unit length defined using the standard tables provides a "length in days" that is not correct for your needs.

When is this exit processed

As each day of an absence is processed, the employee's applicable scheme rules are derived and processed through one by one. For the current scheme rule being processed, the check window, entitlement, absence grouping, and payment band are derived. Then the day is processed and if there are any entitlement days for the absence grouping and payment band that have not been used up in the check window, then the day will be "marked" with the valuation rule associated with the payment band.

Just before this routine is called:

The time unit is not an SAP standard one of "days" (010), "weeks" (011), "entitlement weeks" (E11), "rollback months" (R12), or "rollback years" (R13). So the time unit must be further defined into a number of days in some way.

If the time unit is not in the Time Unit Multiplier table, then it must be defined in this customer exit, otherwise this customer exit is omitted.

This customer exit will only be processed if a match was not found in the Time Unit Multiplier table.

Just after this routine is called:

The calculated length of the time in days is passed back to the calling routine. This will either be the "Derive Entitlement in Days" function or the "Derive the Rollback Period in Days" function. In the first case, this can be adjusted by the customer exit EXIT_SAPLHRGPBS_OSP_OMP_ENT and in the second by EXIT_SAPLHRGPBS_OSP_OMP_PER.

Example

This routine is used to derive the rollback period length in days (or entitlement in days) to a customer specification that cannot be simply stated by using a number of days.

Notes

Requirements

Standard settings

Recommendation

This customer exit is one of seven available as part of the absence evaluation and payment scheme functionality. They are ordered from the most likely to be used to the least likely:

  1. EXIT_SAPLHRGPBS_OSP_OMP_CVR

    Derive an employee's scheme according to client specific rules

  2. EXIT_SAPLHRGPBS_OSP_OMP_MIN

    Define a part day absence as entitlement in minutes

  3. EXIT_SAPLHRGPBS_OSP_OMP_SEN

    Define the seniority time unit parameters

  4. EXIT_SAPLHRGPBS_OSP_OMP_ENT

    Adjust the employee's entitlement

  5. EXIT_SAPLHRGPBS_OSP_OMP_LEN

    Define a time unit length in days

  6. EXIT_SAPLHRGPBS_OSP_OMP_MTD

    Define a rollback method

  7. EXIT_SAPLHRGPBS_OSP_OMP_MAN

    Perform customer-specific processing for manual splitting

These are the only customer exits provided to supplement the Payroll absence processing functionality. Before using any of the customer exits make sure you have consulted with SAP. This will ensure the changes you need are necessary (cannot be fulfilled elsewhere in Customising) and that the changes you are about to make will have the desired results with no negative impact on performance.

General information about interfaced data

All seven customer exits have the following fields:
IMPORTING
VALUE(P_PERNR) LIKE PERNR-PERNR
VALUE(P_CHECK_DATE) LIKE SY-DATUM
TABLES
P_P0000 STRUCTURE P0000
P_P0001 STRUCTURE P0001
P_P0002 STRUCTURE P0002
P_P0004 STRUCTURE P0004
P_P0007 STRUCTURE P0007
P_P0008 STRUCTURE P0008
P_P0016 STRUCTURE P0016
P_P0041 STRUCTURE P0041
P_P2001 STRUCTURE P2001
P_ERROR STRUCTURE EDIMESSAGE

Do not change the data in the infotype tables.

"P_ERROR" has the fields msgid, msgty, msgno, msgv1, msgv2, msgv3, and msgv4. This table should not be refreshed as it may contain "warning" messages that have not halted processing previously.

If an error happens in this function, then fill the record "P_ERROR" and append the record to the table. Do not perform any error handling in this function as it is used in payroll, dialog, and reporting (for example, statement "MESSAGE" etc.)

Activities

Further notes

By defining a customer time unit multiplier for each rollback period time unit and entitlement amount time unit or using the SAP standard ones there may be no need to use this customer exit.

Business Attributes
ASAP Roadmap ID 204   Establish Functions and Processes 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 2   Non-critical 
Country-Dependency I   Valid for countries specified 
Customizing Attributes Country Key Country Name
OHAIEOSP00103D IE Ireland
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG OHAIEOSP00103D 0 AHR0000011 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
CMOD L - Logical transport object CMOD  
History
Last changed by/on SAP  20060531 
SAP Release Created in 46B