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 | OHAGOSP00110 | De-activate Automatic Splitting of Absences |
| Transaction Code | S_PH9_46000755 | (empty) |
| Created on | 19990704 | |
| Customizing Attributes | ||
| Customizing Activity |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | OHAGOSP00110 |
Example
This process activates or de-activates the automatic splitting of absences in payroll according to the employee's Absence Evaluation Scheme.
The Payroll Constant for Manual Splitting must be switched to ' ', if Automatic Splitting of Absences in Payroll is to be activated. This is default setting on delivery. (Table T77S0: PTIME MANSP)
Requirements
The complete Absence Evaluation Scheme must be set up for ALL employees that are covered by the scheme. The Absence Entry Check performs the same calculation as payroll (except without SUBSTITUTIONS) and reports any errors or warnings. The Payroll Processing STILL performs the same calculation as before, reports any errors or warnings, BUT does NOT split the absence in table AB.
Standard settings
Recommendation
Switching 'ON' Manual Splitting DOES NOT perform the Manual Splitting of Absence Records in Infotype 2001. This MUST be performed MANUALLY.
If checking during Absence Entry is NOT active, then there is NO benefit setting up an customising ALL your scheme rules to then MANUALLY operate your scheme as the user inputting the absences in Absence Entry is unaware of any splits necessary.
EVEN if checking during Absence Entry IS active, the information stored on the database will slowly move away from the absence entries entered during Absence Entry. This is because the data in structure 'COVER' will EXACTLY follow the scheme rules, where as the Absence Data will not actually reflect that.
Activities
If this is activated, extra processing for splitting the absence table in payroll (table AB) is unnecessary. This will make Payroll marginally quicker.
Further notes
If you wish to operate your scheme manually AND still have checking active during Absence Entry, then use the Customer Exit in the function "HRGPBS_OSP_OMP_ABS_ENTRY_CHK" to perform the 'CORE' of your BESPOKE report that covers your scheme rules and then this code can action the user to split the Absence Manually.
To make payroll quicker, the function GPNAB should be commented out, as in this case, manual splitting will be informed completely on the processing of the 'CENTRAL CODE' of your BESPOKE report and NOT on the customising or processing of the Absene Evaluation Scheme.
Business Attributes
| ASAP Roadmap ID | ||
| Mandatory / Optional | ||
| Critical / Non-Critical | ||
| Country-Dependency |
Maintenance Objects
| Maintenance object type |
History
| Last changed by/on | SAP | 19990705 |
| SAP Release Created in |
