Ansicht
Dokumentation

SIMG_OHT72 - Calculate Overtime on the Basis of General Periods

CPI1466 during Backup   RFUMSV00 - Advance Return for Tax on Sales/Purchases  
This documentation is copyright by SAP AG.

This is a special function which you can use if the standard functions are not sufficient for your purposes.

In this step, you specify how overtime is checked on the basis of a general evaluation period. This is necessary if you only want overtime to be generated after a certain working time has been exceeded within a specific period. The function is a more general version of the weekly overtime analysis.

An employee is authorized to work 2 hours of overtime per day and has a planned working time of 40 hours a week. Overtime should only be generated if the amount of time worked within two weeks exceeds 80 hours. The employee works 9 hours on two days of the first week, and 7 hours on one day of the second week, but on all other days he/she works 8 hours. One of the two overtime hours in the first week is deducted to compensate for the missing hour in the second week. The employee is then credited with one hour of overtime.

Subschemas TOP0 and TOP1 show examples of a two-weekly overtime analysis.

The planned working time for the period being analyzed must be stored in the system or calculated in the schema using appropriate values.

The options are as follows:

The planned time is specified for each day in the daily work schedule.

Average values for the daily, weekly and monthly planned working times are defined in the work schedule rules.

Planned specifications can also be stored in the 'Payroll Constants' view.

All the values named above can be referenced in time evaluation using operation HRS.

The periods to be analyzed must be defined as evaluation periods. The relative days and the first and last days of a period can be queried in a time evaluation rule using operation VARST.

Use schemas TOP0 and TOP1 as references to perform an analysis of overtime for a general period. Change the period modifier accordingly and define new planned specifications, if required.

In schema TOP0, overtime is generated first for time pairs which exceed the daily planned time but fall short of the maximum daily working time, and for which there is an attendance quota. This is done in personnel calculation rule TOP1.

The day's planned hours and overtime hours are then logged in different time types in personnel calculation rule TOP2.

In personnel calculation rule TOP3, the system checks to see if there is a correction quota. Time pairs within the scope of the correction quota are flagged and assigned the time type for planned work.

The flagged pairs are converted to planned working times. The total of converted hours is logged in the time type "additional planned time/period". Overtime is generated definitively for pairs that have not been converted to planned working time pairs.

The correction quota is set up in subschema TOP1. A check is made first to see whether the employee has completed his/her planned working time for the period (personnel calculation rule TOP6). If not, the number of hours to be corrected is entered in a utility time type. In TOP7, a batch input session is generated from the utility time type and used to import the correction quota.

The function is not active in the standard system.

Schedule a periodic batch job to import the batch input session. Use report RSBDCSUB.

Decide whether you want overtime to clear a shortfall in planned working time within the period.

If you do, insert functions COPY TOP0 and COPY TOP1 in your schema instead of the weekly overtime analysis. You can use the line selection function to call maintenance screens for subschemas and personnel calculation rules. Replace standard rules with your own rules if required.

Please note that the names of any rules you create yourself should start with 'Z'.

• Please see the section on processing overtime approval from a quota for details on generating overtime on the basis of an attendance quota.

RFUMSV00 - Advance Return for Tax on Sales/Purchases   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

Length: 4464 Date: 20240523 Time: 190854     sap01-206 ( 90 ms )