Ansicht
Dokumentation

OHADOEU32 - Define Events for Start of New Calculation Period

General Material Data   ABAP Short Reference  
This documentation is copyright by SAP AG.

In this step, you assign the events used in the calculation of the leave and sick pay premium to the pre-defined models for the start of a new calculation period.

In Payroll Accounting, all events for a model are checked and, if necessary, a new calculation period is started. Neither a premium rate that is fixed at this point, nor cumulated calculation bases are taken into account for the premium payment.

You can also specify the number of calendar months after the corresponding event in which the valuation bases are not cumulated (lock period for cumulation bases).

The following section describes all events that you can use:

• New entry

New entry as entered in the Actions infotype (0000)

• Re-entry

Re-entry as entered in the Actions infotype (0000)

• Change in working time (h/week)

Change in the weekly working time as entered in the Planned Working Time infotype (0007)

If the system identifies a change, it then checks whether the change is due to a change in the individual working time. This means the standard weekly working time in table T510I is also checked.

If the ratio of the individual working time to the standard working time remains unchanged after the change in infotype 0007, the individual working time for the employee has not changed. This means that no new calculation period can be started.

• Change of employer (action)

Change of employer as entered in the Actions infotype (0000)

For this event, the system checks whether there is an action that is classified as a change of employer (specification 05) with the Irregular Payments indicator.

For more information on this indicator, see the section Maintain Personnel Actions.

• Change of calculation model

Change of calculation model for premium calculation as defined in table T5D87.

If a new calculation model must be used due to a change in the organizational assignment or pay scale type for the employee, this event triggers a new calculation period.

• Change of pay scale type

Change of pay scale type in Basic Pay infotype (0008)

• Change of training status

Change of training status as defined in table T503

The start of a new calculation period occurs with this event if the training status for the employee (table T503) has changed due to a change in the employee subgroup.

• Date type

The start of a new calculation period is entered in the Date Specifications infotype (0041) using the date type 31.

This event triggers a check of infotype 0041. If a date with the date type 31 is entered for an employee, a new calculation period is started on this date.

• Wage type

A new calculation period is defined using a wage type

As with the Date type event, a new calculation period can be entered for a particular employee.

However, this variant should only be included in the model if you have already used the wage type in the past in the calculation of the premium rate. (In the BAT pay scale, the model wage types ONUA and ONUB are used for this purpose.)

Otherwise, you should use the date type to enter the start of a new calculation period for a specific employee.

In the standard system, the events are assigned to the respective model in accordance with the collective agreement.

1. Check the events that are assigned to the model for your collective agreement.
2. In the Lock column (lock period for cumulation), check the lock period during which the valuation bases are not cumulated (in months).

BAL_S_LOG - Application Log: Log header data   TXBHW - Original Tax Base Amount in Local Currency  
This documentation is copyright by SAP AG.

Length: 5098 Date: 20240524 Time: 010110     sap01-206 ( 65 ms )