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 | OHAIEOSP00110B | Activate the Customer Exit for Seniority Calculation Adjustment |
| Transaction Code | S_AHR_61019408 | (empty) |
| Created on | 19991202 | |
| Customizing Attributes | OHAIEOSP00110B | Activate the Customer Exit for Seniority Calculation Adjustment |
| Customizing Activity | OHAIEOSP00110B | Activate the Customer Exit for Seniority Calculation Adjustment |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | OHAIEOSP00110B |
Use
In this step, you can override the standard calculation of days into years, months, and weeks by activating the customer exit for seniority calculation adjustment EXIT_SAPLHRGPBS_OSP_OMP_SEN.
Standard settings
The standard calculation uses the values which are defined in the table Time Unit Multiplier (T5GPBS24):
- S11 defines the number of days in a week
- S12 defines the number of days in a month
- S13 defines the number of days in a year
These values are used by the seniority calculation, which passes out the employee's calculated seniority in years, months, and days. For example, 365 days of seniority are passed out as 1 year, 0 months, and 5 days (whereas the calculation uses 30 days in a month and 360 days in a year).
The seniority bands in the scheme rules are in whole years, months, weeks, or days. For example, 1 year, 0 months, and 5 days is converted into 1 year, 12 months, 52 weeks, and 365 days using the standard seniority time units of the table T5GPBS24.
Changing the standard time units should be sufficient for your needs, but if they are not then the customer exit allows you complete flexibility.
Activities
As each day of an absence is processed, the employee's seniority is calculated using any of the possibilities in the feature GLOSS. If the return value of the feature implies the seniority calculation is necessary then the customer exit EXIT_SAPLHRGPBS_OSP_OMP_SEN is called.
Immediately before this routine is called, the seniority is passed from the function module HR_SEN_CALCULATE_COMPLETE to the function module HRGPBS_ABS_SENIORITY_CALCULATE, which passes out the seniority structure.
Immediately after this routine is called, the values in the seniority structure are passed back to the main routine to allow the correct seniority band in table Rules for the Refinement of Absences (T556G) to be selected.
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:
- EXIT_SAPLHRGPBS_OSP_OMP_CVR to derive an employee's scheme according to client specific rules.
- EXIT_SAPLHRGPBS_OSP_OMP_MIN to define a part day absence as entitlement in minutes.
- EXIT_SAPLHRGPBS_OSP_OMP_SEN to define the seniority time unit parameters.
- EXIT_SAPLHRGPBS_OSP_OMP_ENT to adjust the employee's entitlement.
- EXIT_SAPLHRGPBS_OSP_OMP_LEN to define a time unit length in days.
- EXIT_SAPLHRGPBS_OSP_OMP_MTD to define a rollback method.
- EXIT_SAPLHRGPBS_OSP_OMP_MAN to perform customer-specific processing for manual splitting.
These are the only customer exits provided to supplement the 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 little impact on performance.
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
Note:
Do not change the data in the infotype tables.
P_ERROR contains 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 occurs 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).
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 |
|---|---|---|
| OHAIEOSP00110B | IE | Ireland |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | OHAIEOSP00110B | 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 |
