SAP ABAP IMG Activity OHAIEOSP00112A (Define OSP and OMP Basic Payments)
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 OHAIEOSP00112A Define OSP and OMP Basic Payments  
Transaction Code S_AHR_61019398   (empty) 
Created on 19991202    
Customizing Attributes OHAIEOSP00112A   Define OSP and OMP Basic Payments 
Customizing Activity OHAGOSP00112A   Absence Payment, Rates, Divisors and Factors 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name OHAGOSP00112A    

Use

In this step, you specify business rules for your Occupational Absence (OxP) processing by:

  1. Setting up your absence payment groupings
  2. Updating Counting Classes and Generate Wage Types via payroll function PAB
  3. Filling the Valuation Bases used for Occupational Absence payments (/010, /011, /012, /013) with amounts from the employees' basic payments (Amount)
  4. Dividing the Valuation Bases used for Occupational Absence payments (/010, /011, /012, /013) by a divisor based on the employee groups' working Terms and Conditions (Rate) and applying the same factor that is used in the next step (Normally, Payroll Constant GENAU in Table T511K)
  5. Applying exactly the same rate calculation to the Part-Period Factors (PPF) used when an employee is absent.

    You use a divisor based on the employee groups working Terms and Conditions (Rate) and apply the same factor that is used in the next step (Normally, Payroll Constant GENAU in Table T511K)

Requirements

The standard SAP settings are that absence payments are treated as actual payments. In this way, the wage types created are physically paid and the employees basic pay is reduced by the proportion that they are absent in the pay period.

Standard settings

SAP recommends that you set up Occupational Adoption Pay (OAP), Occupational Paternity Pay (OPP), Occupational Sick Pay (OSP) and Occupational Maternity Pay (OMP) as payments for all your employee groups. The absence payment groupings (MODIF A) recommended are:

  • Hourly (1)
  • Waged (2)
  • Salaried (3)

The Personnel Calculation Rule (PCR) GMOD is provided to ensure that payroll uses the correct entries in the table Absence Valuation (T554C) for your distinct groups:

Hourly (1) : Customised using Working Hours (AH)

Waged (2) : Customised using Working Days (AT)

Salaried (3) : Customised using Calendar Days (KT)

To complement these settings, the Counting Classes used for adjusting the employee's Part-Period Factor (when they are absent) are all made completely unpaid (Table T554C). Basic pay is only paid for days when the employee is not absent due to Adoption, Paternity, Sickness or Maternity leave and OxP is paid when an employee is absent taking one of these four types of leave.

Note:

Statutory Adoption Pay (SAP), Statutory Maternity Pay (SMP), Statutory Paternity Pay (SPP), and Statutory Sick Pay (SSP) are not included in this section of the IMG as they will normally be paid for any qualifying statutory absence. The IMG step Offsetting Statutory and Occupational Absence Payments allows you to configure whether or not SAP, SPP, SSP or SMP will be paid in addition to reduced OxP (to a limit of Full Pay).

The five activities contained in this customising step are pre-delivered by SAP:

  1. Set up your absence payment grouping (MODIF A) to map to your employee groupings for payroll (ABART) using the Personnel Calculation Rule (PCR) GMOD or your own copy.
  2. All occupational absences are completely unpaid. The respective counting classes are reduced by 100% when an employee is absent. That is, an employee's Basic Pay is reduced proportionally by the amount he or she is absent. Notional wage types are then generated during the operation of payroll function PAB with a number against them, so that an employee will receive payment when he or she is absent. The rate is filled by the PCR G015 using the relevant valuation base and percentage against the notional wage type in table Wage Type Texts (T512W).
  3. The valuation bases /010, /011, /012 and /013 are delivered as identical, but should be modified to each clients specific needs. Do not attempt to use your own, as the offsetting code inside payroll function GBSxP only uses these four wage types to derive Full Pay. They are filled with gross payments via the PCR G010. If G010 needs amendment, you should copy it to a Z version before correction.
  4. The amounts in each valuation base /010, /011, /012 and /013 are divided down to a daily rate dependent on the employee grouping for payroll (ABART):
    1. Hourly (1) uses the employee's working hours
    2. Weekly (2) uses the employee's working days
    3. Salary (3) uses the employee's calendar days
  5. The Part-Period factoring applied when an employee is absent must use the identical calculation that has been used to derive the divisor used to divide down the amount of each valuation base /010, /011, /012 and /013 to a daily rate dependent on the employee grouping for payroll (ABART):
    1. Hourly (1) uses the employee's working hours
    2. Weekly (2) uses the employee's working days
    3. Salary (3) uses the employee's calendar days

Note:

The SAP standard solution multiplies the rates and Part-Period Factors by the payroll constant GENAU (T511K) to make certain that there are no rounding issues when dealing with absence payments.

To inform the OxP offsetting solution that the occupational daily rates and the amounts against the occupational wage types are factored by GENAU, the first parameter of GBSxP is set to X. This implies that the statutory payments held in table MSA will also be factored by GENAU. This ensures that offsetting is performed multiplied by GENAU and more importantly, that the results of the offsetting are also factored down by GENAU afterwards.

Activities

Set the entries in PCR GMOD, T554C, and the PCRs G010, G013 and GPPF to correspond to the business requirements for your different employee groups.

Generally, this decision is based completely on your own business practices. There are two options for Sickness, Maternity, Adoption and Paternity absence processing:

  • OxP Notional

    You can opt not to make a physical occupational absence (OxP) payment to an employee. The amount due will simply be part of an employee's basic pay. In this way, the employee does not receive Basic Pay and OxP. He or she simply receives Basic Pay. If an employee has been sick for a sufficiently long period, then Basic Pay is reduced from Full Pay. That is, an employee's Part-Period Factor (PPF) will be reduced from a whole pay period to a fraction of a whole pay period. His or her basic pay is then multiplied by the PPF.

  • OxP Payment

    Alternatively, you can opt to make a physical payment to an employee called OxP. The amount due will simply be added to an employee's basic pay. In this way, an employee receives Basic Pay and OxP. Basic Pay is paid for the days when he or she is not absent and OxP is paid for the days when he or she is absent.

    If an employee has been sick for a sufficiently long period, then his or her Basic Pay plus OxP will be reduced from Full Pay. That is, an employee's PPF will be reduced from a whole pay period to a fraction of a whole pay period whenever he or she is sick during a period. However, if an employee is still receiving Full Pay, the reduced Basic Pay will be topped up to full Basic Pay by the OxP payment generated for the days absent.

Example

This example further illustrates the two options outlined under Activities, using Occupational Sick Pay (OSP).

Stage 1

The employee groupings for payroll (ABART) are mapped to your absence payment groupings (MODIF = A) in the PCR GMOD or your own equivalent.

Stage 2

In this stage, payments are initaited to employees, as follows:

  1. You pay your employees OSP and have decided to make OSP a payment wage type.

    Firstly, Basic Pay must only be paid when an employee is not absent due to sickness. The valuation classes set up for OSP (T554C) must be 100% unpaid as you intend to physically pay OSP. The value of the Wage Type OSPP will be added into an employee's gross pay and the Wage Type OSPP will be posted to finance. (You must also check that the configuration of the postings matches your requirements.)

    The Wage Type OSPP will already have the legislative offsetting applied to it, so that OSP/SSP cannot exceed Full Pay.

    • When an employee is absent on Full, Half or Nil Pay OSP, he or she will receive Basic Pay (or a proportion of Basic Pay) + SSP (dependent on the settings in Feature GOFFS). If this value exceeds Full Pay, Wage Type OSPP will contain the over-payment as a negative value.
    • If SSP is paid optionally then the value will be created in the wage type SSPO.
    • If&#
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
OHAIEOSP00112A IE Ireland
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG OHAGOSP00112A 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
PCYC L - Logical transport object PE00 GMOD Absence Payment Groupings 
V_T554C V - View SM30 Absence Payment Rules 
PCYC L - Logical transport object PE00 G010 Absence Payment Rate Amounts 
PCYC L - Logical transport object PE00 G013 Absence Payment Rate Divisors 
PCYC L - Logical transport object PE00 GPPF Absence Part Period Factoring 
History
Last changed by/on SAP  19991202 
SAP Release Created in 46B