SAP ABAP IMG Activity OHAIEOSP001B01 (De-activate Absence Entry Checking)
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 OHAIEOSP001B01 De-activate Absence Entry Checking  
Transaction Code S_AHR_61019410   (empty) 
Created on 19991202    
Customizing Attributes OHAIEOSP001B01   De-activate Absence Entry Checking 
Customizing Activity OHAIEOSP001B01   De-activate Absence Entry Checking 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name OHAIEOSP001B01    

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.

Note

During go-live batch entry of absence data the absence entry checking should not be activated. Alternatively, the absence data as a whole can be checked using the report RPLABSG0_SxP_OxP_HIST. Make sure that the constant HRPSG ABSCH in table T77S0 is set to none before running the batch routines to update 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 have the following absence entry checking options:

  • Operate absence splitting manually without absence entry checking

    There is no benefit doing this. The absence entry clerk is 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 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 1   Mandatory activity 
Critical / Non-Critical 1   Critical 
Country-Dependency I   Valid for countries specified 
Customizing Attributes Country Key Country Name
OHAIEOSP001B01 IE Ireland
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG OHAIEOSP001B01 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
V_T77S0 V - View OO_GB_OSP_OMP  
History
Last changed by/on SAP  20060531 
SAP Release Created in 46B