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 | OHAIEOSP00101C | Activate the Customer Exit for "From Where" Methods |
| Transaction Code | S_AHR_61019386 | (empty) |
| Created on | 19991202 | |
| Customizing Attributes | OHAIEOSP00101C | Activate the Customer Exit for "From Where" Methods |
| Customizing Activity | OHAIEOSP00101C | Activate the Customer Exit for "From Where" Methods |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | OHAIEOSP00101C |
In this step, you can define your own specific "From Where" methods by entering the code in the customer exit EXIT_SAPLHRGPBS_OSP_OMP_MTD.
Customer-Specific Rollback Methods
There are two customer-specific methods for defining a point in time from which to rollback, Y and Z.
The general principle of these rollback methods is that the SAP standard methods, though reasonably comprehensive, are unlikely to satisfy all of your absence evaluation rollback requirements. For this reason, two methods that can be customised have been included in the values allowed for the rollback methods. Any 10-character parameter is allowed to complement either method.
The customer exit (EXIT_SAPLHRGPBS_OSP_OMP_MTD) is available to process any customer-specific method.
If you have more than two methods, then a single method can be split into further methods by using an employee's master data and choosing which method to use (inside the customer exit) from the employee's master data (employee subgroup).
Example
In rare cases a client may not be able to use one of the standard methods, such as in the following.
The client has seasonal workers who receive varying entitlements depending on the season. During the "low season" the absence may roll back from the start date of the absence, during the "high season" the absence may roll forward from the employee's most recent hire.
In this case, being absent during the "high season" is treated more harshly than during the "low season".
This method would have to be used in conjunction with a new rollback period time unit that "switched" depending on the date of the absence.
Requirements
Standard settings
Recommendation
Only use this customer exit as a last resort, normally the standard methods will be sufficient by simply adapting the rollback method, period, and the entitlements received during that period.
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
Derive an employee's scheme according to client specific rules.
- EXIT_SAPLHRGPBS_OSP_OMP_MIN
Define a part day absence as entitlement in minutes.
- EXIT_SAPLHRGPBS_OSP_OMP_SEN
Define the seniority time unit parameters.
- EXIT_SAPLHRGPBS_OSP_OMP_ENT
Adjust the employee's entitlement.
- EXIT_SAPLHRGPBS_OSP_OMP_LEN
Define a time unit length in days.
- EXIT_SAPLHRGPBS_OSP_OMP_MTD
Define a rollback method.
- EXIT_SAPLHRGPBS_OSP_OMP_MAN
Perform customer-specific processing for manual splitting.
These are the only customer exits provided to supplement the GB 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 Customizing) and that the changes you are about to make will have the desired results with little 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
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 |
|---|---|---|
| OHAIEOSP00101C | IE | Ireland |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | OHAIEOSP00101C | 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 | 20060530 |
| SAP Release Created in | 46B |
