Hierarchy
⤷ PY-GB-PS (Application Component) Öffentlicher Dienst
⤷ P08P_ABSC (Package) HR Public Sector Great Britain Absence Evaluation Customing
IMG Activity
ID | OHAGOSP00109A | Activate Absence Entry Checking |
Transaction Code | S_PH9_46000757 | (empty) |
Created on | 19990705 | |
Customizing Attributes | OHAGOSP00109A | Activate Absence Entry Checking |
Customizing Activity | OHAGOSP00109A | Activate Absence Entry Checking |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | OHAGOSP00109A |
Use
In this step, you decide whether or not all absences entered in infotype Absences (2001) are checked against the employee's entitlements to absences.
Requirements
- If you operate absence splitting manually with absence entry checking using the standard absence evalution customising and routines, the complete absence evaluation scheme must be set up for all employees who are covered by the scheme. The absence entry check performs the same calculation as payroll (except without substitutions) and reports any errors or warnings.
- If you operate absence splitting manually with absence entry checking using a BESPOKE report, the customer exit must be maintained to issue the correct warning and error messages when an error occurs due to an employee's data or when an employee's entitlement band changes part way through an absence.
- If you operate absence splitting automatically with absence entry checking, the complete absence evaluation scheme must be set up for all employees who are covered by the scheme. The absence entry check performs the same calculation as payroll (except without substitutions) and reports any errors or warnings.
Standard settings
You can implement any of the following absence entitlement checks:
- Operate absence splitting manually without absence entry checking
There is no benefit doing this. A payroll administrator will be unaware that a split may be necessary without doing extensive checking or running a report outside absence entry.
- Operate absence splitting manually with absence entry checking
- Using the standard absence evaluation customising and routines
- The information stored in the database will slowly diverge from the absence entries entered during absence entry. This is because the data in structure COVER will exactly follow the scheme rules, whereas the absence data splits will be manual.
- If this is activated, extra processing for splitting the absence table in payroll (table AB) is unnecessary and so omitted but the rest of the checking is performed. This will make payroll faster. The manual splits could be kept in line with the automatic ones using the infotype Absence Scheme Override (0572).
- Using a BESPOKE report
- Use the provided customer exit EXIT_SAPLHRGPBS_OSP_OMP_MAN to perform the calculation of your BESPOKE report that covers your scheme rules and then this code can action the clerk to split the absence manually.
- To activate the use of this customer exit, set the manual splitting switch to R for report.
- To make payroll quicker, the function GPNAB should be commented out from the schema as manual splitting is active.
- Operate absence splitting automatically without absence entry checking
The absence entry clerk will be unaware that a split will occur during the absence and so a standard report will have to be run periodically to find out whether or not an employee's entitlements should be overridden using infotype 0572.
Also any errors in the employee's data or in the scheme set up will only occur during payroll and so can only be solved retrospectively, instead of proactively. - Operate absence splitting automatically with absence entry checking
The default setting will split automatically and perform checking.
Activities
To activate absence entry checking, the payroll constant for absence checking (HRPSG ABSCH in table T77S0) must be set to either X or W.
- If you set HRPSG ABSCH to X any errors will be automatically reported and will not allow the data to be saved. Any band changes that occur during the absence will be automatically reported.
- If you set HRPSG ABSCH to W any errors will be automatically reported and will not allow the data to be saved. Any band changes that occur during the absence will be automatically reported. Any warnings that occur during processing can be reported as well.
If absence entry checking is activated, extra processing is necessary. This will make absence entry slower (especially for open-ended absences).
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 |
---|---|---|
OHAGOSP00109A | GB | United Kingdom |
Assigned Application Components
Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
---|---|---|---|---|
SIMG | OHAGOSP00109A | 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 |
V_T77S0 | V - View | OO_GB_OSP_OMP |
History
Last changed by/on | SAP | 20020203 |
SAP Release Created in |