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 | OHAGOSP00108A | Activate the Customer Exit for Overriding Entitlements |
| Transaction Code | S_PH9_46000753 | (empty) |
| Created on | 19990704 | |
| Customizing Attributes | OHAGOSP00108A | Activate the Customer Exit for Overriding Entitlements |
| Customizing Activity | OHAGOSP00108A | Activate the Customer Exit for Overriding Entitlements |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | OHAGOSP00108A |
In this step, you can override the entitlements after they have been derived from the scheme rules and before the extensions or reductions are applied from the infotype Absence Scheme Override (0572).
In this step, you override the standard entitlements derived from the Customising tables using the code in the pre-delivered customer EXIT_SAPLHRGPBS_OSP_OMP_ENT.
Example
This routine adjusts the amount of entitlement that is about to be processed. Potentially relevant information could be held on an infotype other than the infotype 0572. In this case, this customer exit could be used to derive the necessary information and then amend the entitlement.
Why you may need to use this customer exit
If the entitlement amount defined using the standard tables provides an entitlement that does not meet your needs.
When is this customer 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 cover package 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" using the valuation rule associated with this payment band.
Just before this routine is called
The check window for defining a reference period to check whether all an employee's entitlements to a specific payment band may have already been used has already been derived. The entitlement for this scheme rule's absence grouping and payment band has already been derived.
Just after this routine is called
The discretionary reductions or extensions to a specific absence subtype grouping and payment class for an employee in infotype 0572 are derived. [This infotype may fulfil your requirements for amending an employee's entitlement.] Any reduction is subtracted from the entitlement. If there is still an entitlement to check, then all absences in the check window are checked for used entitlements.
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:
- 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 payroll GB 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.)
Further Information
By defining a customer rollback method, customer time units for a rollback period, and customer time units for entitlements and infotype 0572, there should be no need to use this customer exit.
If a multiple employment solution is necessary, look at the coding of the function module HRGPBS_OSP_OMP_CHECK_MARKS to decipher how to use the parameters passed in.
Simply speaking you need to:
LOOP through pernrs in IT0031.
DERIVE payroll results for each between p_start_date and p_end_date
LOOP through COVER-CDATE between p_start_date and p_end_date.
LOOP through Submarks in each COVER-MARK.
IF the submark matches p_submark (using offset and length)
TOTAL up the minutes in the submark. endif.
ENDIF.
ENDLOOP.
ENDLOOP.
ENDLOOP.
Divide the number of minutes by 1440 to get days and reduce p_entitlement_in_days accordingly.
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 |
|---|---|---|
| OHAGOSP00108A | GB | United Kingdom |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | OHAGOSP00108A | 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 |
| CMOD | L - Logical transport object | CMOD |
History
| Last changed by/on | SAP | 19991012 |
| SAP Release Created in |
