SAP ABAP IMG Activity OHADOE570 (Set Up Automatic Triggering of Calculation of Basis for Supplement)
Hierarchy
SAP_HRCDE (Software Component) Sub component SAP_HRCDE of SAP_HR
   PY-DE (Application Component) Germany
     P01C (Package) HR Customizing: Germany
IMG Activity
ID OHADOE570 Set Up Automatic Triggering of Calculation of Basis for Supplement  
Transaction Code S_AHR_61005520   IMG Activity: OHADOE570 
Created on 19981221    
Customizing Attributes OHADOE570   Set Up Automatic Triggering of Calculation Basis for Supplement 
Customizing Activity OHADOE570   Set Up Automatic Triggering of Calculation of Basis for Supplement 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name OHADOE570    

In this step, you make the settings necessary to trigger the calculation of the maternity pay supplement. This only applies if you are currently using a calculation model that does not take future salary changes into account.

However, when the corresponding regulation comes into force on January 1, 1997, this should no longer be the case.

If you still want to use such a calculation model, the bases are not calculated automatically. They must be triggered using a wage type. The use of the wage type can consequently be supported by setting up a dynamic event. If a Maternity Protection absence has been entered, a date is set for the start of the maternity protection period and a wage type is created in the Additional Payments/Deductions infotype (0015) three months before the start of the maternity protection period.

You can also use this function if you create a data record for the Maternity Protection infotype (0080).

Standard settings

The standard settings are based on the following model entries:

  • Absence type MZMG
  • Date type 25
  • Wage type OZMG

Instead of the correct absence 0500 for maternity protection, the absence type MZMG is used only to deactive the dynamic event in the standard SAP system. The system assumes that the current supplement model triggers the calculation automatically.

Activities

You should make the following modifications, depending on which model entries have not been copied from the standard SAP settings:

  1. To copy the absence MZMG to your customer name range, perfrom the activity Dynamic event for Maternity Protection absence.
  2. Copy the standard entries for MZMG to the subtype for your own absence type and then delete the model entries.
  3. If you have created your own date type in the step Create Maternity Protection Date Type, change the date type 25 in the corresponding line of the Variable function part column to the value for your own deadline type.
    1. Choose Save.
  4. Perform the activity Dynamic event for date at start of Maternity Protection for the Calculation of Supplement Basis wage type.
    1. In the corresponding lines, change the wage type OZNG to the value of your own wage type.
  5. Choose Save.

Further notes

If you want to save the date record in the Dates infotype and the wage type in the Additional Payments/Deductions (0015) in the background without repeating the confirmation, you can do this using the supplement /D in the lines for the action I.

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
OHADOE570 DE Germany
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG OHADOE570 0 HLA0003745 Gross 
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
VV_T588Z_2001___AL0 V - View SM30 Dynamic Actions: Maternity Protection Absence 
VV_T588Z_0019___AL0 V - View SM30 Dynamic Actions: Task for Maternity Protection Start 
History
Last changed by/on SAP  20101116 
SAP Release Created in