Overtime Generation and Valuation Using T510S

OVERTIME GENERATION AND VALUATION USING T510S

PREREQUISITES

• Valid Work Schedule Rule• Hired Employees•Attendance Type•Wage type Created for Overtime

ATTENDANCE GIVEN TO THE EMPLOYEE FOR THE DAYS WORKED (4 SCENARIOS WHERE IN THE EMPLOYEE HAS WORKED OVERTIME)

Scenario 1 – Employee has worked Overtime on Saturday

Scenario 2 - Employee has worked Overtime on Weekday (Mon- Fri)

Scenario 3 - Employee has worked Overtime on Sunday

Scenario 4 - Employee has worked Overtime on Public Holiday

SCHEMA USED FOR CALCULATING OVERTIME IN TM04 (TIME EVALUATION WITHOUT CLOCK EVENTS)

Block Where Overtime is

Generated and Valuated using the

Sub Schemas TW15, Using Function

DAYMO, GWT and TC40

MODIFICATIONS DONE TO GENERATE OVERTIME IN SUB SCHEMAS TW15

PCR TO01 and TO02 are used to generate the Overtime Worked. However A few Modifications were done to these rules to fit in the Current Scenario

Here the requirement is the for ‘n’ planned hours the overtime should be calculated. Rules TO01 and TO02 Calculate the overtime on a certain set value i.e. 8 to generate the overtime. Hence in general, if The EE has worked more than 8 hours, the extra hours worked are considered as Overtime. Though the planned hours for the EE is more than or less than 8. In order to generate the correct overtime, her we have made certain changes where the overtime is calculated based on the Planned hours. The changes made are shown in the next slide.

PCR &O01 which has been Modified to Set the Overtime Limit for the day

PCR – TO02 Which calculates the Overtime worked

TIME EVALUATION FOR THE PERIOD 01.01.2012 – 31.01.2012

For the Overtime to be calculated and generated, we need to run Time evaluation (Tcode – PT60/ Report – RPTIME00) for the period the attendances are given.Here Modified Schema &M04 is being used as the Sub Schemas TW15 and other functions have been Modified.Here is the modified schema ‘&W15’ being used in the Schema ‘&M04’.

Subschema TW15 has been modified as &W15:

Time Evaluation for the EE for the Period 01.01.2012-31.01.2012 ( Tcode – PT60) :

Input Table for &O02 for OT worked on 07.01.2012 :

Processing Of Rule &O02 :

Output Table For the PCR &O02 :

Here after processing of this rule, We see that the Overtime Worked on Saturday( Weekly Off) is generated for 9 hrs.

The Processing Type M is for Overtime. Here Time type 0040 is generated with the number of hours worked. As the day was a Saturday, all the hours worked were calculated as Overtime.

Similarly Overtime is calculated for 15.01.2012 (Weekly Off) and 26.01.2012 (Public Holiday). However the Rule calculates the Overtime worked on a working day i.e. here 09.01.2012, after deducting the number of planned working hours.

The Rule processes for each entry in the table and generates the Processing Type ‘M’ when the overtime conditions are met. In the Input table i.e. TIP entry. The last entry marked in the above Picture is the overtime worked.The next slide shows us how the rule is processed and the Overtime is calculated.

Overtime worked for that

day

After Processing, The output is as follows :

Overtime Generate

d

OVERTIME COMPENSATION BY TABLE T510S

Table T510S is used to generate the time wage type (Here 7OVT) for the overtime worked. Here the Overtime worked is generated by the Sub Schema &W15. Based on the day grouping and Condition for the day an Conditions for the time, the time wage type is populated.For the configuration of the entries in table T510S, We need to have the time wage type grouping for table T510S and the Day Groupings.

Time Wage type grouping for the table T510S is given by the PCR TMON.In the PCR we check for the value assigned to ‘W’ using Operation MODIF.

Personnel calculation rule TMON uses operation PAYTP to check whetherthe employee being processed is a salaried employee or an hourly wageearner. Operation MODIF sets the following groupings:

• "W": Time wage type selection (Time Wage Type Selection Rule Group table (T510S))

•"T": Assignment of time type to time pair (T555Z)

• "A": Absence valuation (T554C)

Our Requirement as follows, we need the grouping for W which is ‘03’.

DAYMO GROUPING FOR VARIOUS DAY TYPES

We use function DAYMO to set the day grouping for time wage type selection from the Time Wage Type Selection table (T510S) to a particular value. The value is set according to the type of day on which the table is accessed. DAYMO must always be set before function GWT in day processing. This Function is in use in TM04 Schema

Par1 - Not a public holiday :- 01 - Monday - Saturday

Par2 - Not a public holiday :- 02 - Sunday

Par3 - Public holiday :- 03 - Monday - Saturday

Par4 - Sunday and Public Holiday :- 04 - Sunday

IMG PATH FOR TIME WAGE TYPE SELECTION AND OVERTIME COMPENSATION

Path Description

Easy Access Menu

IMG Time Management Time Evaluation Time Evaluation without Clock Times Time Wage type Selection and Overtime Compensation

Transaction Code

SPRO

Here in this path, First we define the Valuation Class for the Period Work Schedule Generated for the respective Employees. After this step, following all the IMG steps one after the other till “Define Generation Rules (T510S)”.These steps help us in maintaining the Table and the prerequisite steps required to maintain the table.

TABLE T510S MAINTENANCE

Table T510s Configuration for Weekly Off Saturday:

As discussed earlier, for the Time Wage type Selection rule – 000(Generation Rule for the Weekly Off –Saturday) , Time Wage type Selection Group value ‘03’ is picked from the PCR TMON and The DAYMO Grouping is 01 (Not A public Holiday).The wage type earlier created for the Overtime Compensation 7OVT is given in the Wage type field which needs to be populated with the overtime worked values.In the conditions for the day , we give in the details as to how the system should calculate the overtime worked and should be processed.As in in the previous slide, in the table we see that under the block conditions for the day w have maintained certain rules for the day.

1. Weekdays – Here we give in ‘x’ for all the weekdays except Sunday as DAYMO grouping for Sunday is different.

2. PH For Previous Day – Referring to public holiday for the Previous day. Here it does not effect the current day. So we select al the classes.

3. PH For Current Day – Referring to current day. It should be 0 (Working Day) as Weekly Off is not a public holiday and should be considered as a working day.

4. PH For Sub Day - Referring to public holiday for the Next day. Here it does not effect the current day. So we select al the classes.

5. Valuation Class for PWS – Defined in the path mentioned in the previous slide, we need to assign a valuation class to the PWS( Table – V_551C_B) of the Respective Employee.

6. DWS Class – Here the DWS class would be 0 as it is an weekly off. Hence letting the system know that the Planned hours for that day is 0.

7. Day Type – Here the Day type would be 0-Work and Paid as weekly off s usually considered as a working day. Except for that the planned hours are ‘0’.

Similarly for the Weekdays i.e. Monday – Friday, the following is the Generation Rule configured.

Similar to Rule 000, for the Generation Rule 001 (Generation Rule for the Weekday Mon-Fri) , Time Wage type Selection Group value ‘03’ is picked from the PCR TMON and The DAYMO Grouping is 01 (Not A public Holiday).The wage type earlier created for the Overtime Compensation 7OVT is given in the Wage type field which needs to be populated with the overtime worked values.In the conditions for the day , we give in the details as to how the system should calculate the overtime worked and should be processed.As in in the previous slide, in the table we see that under the block conditions for the day we have maintained certain rules for the day.

1. Weekdays – Here we give in ‘x’ for all the weekdays except Sat and Sun .2. PH For Previous Day – Referring to public holiday for the Previous day. Here it does not

effect the current day. So we select al the classes.3. PH For Current Day – Referring to current day. It should be 0 (Working Day).4. PH For Sub Day - Referring to public holiday for the Next day. Here it does not effect the

current day. So we select al the classes.5. Valuation Class for PWS – Defined in the path mentioned in the previous slide, we need to

assign a valuation class to the PWS( Table – V_551C_B) of the Respective Employee.6. DWS Class – Here the DWS class would be according to the DWS class you have assigned

to your DWS Rule in table- V_T550A.7. Day Type – Here the Day type would be 0-Work and Paid.

In Addition to the conditions on the day worked, Here we also tell the system that the Overtime valuation worked on a weekday should be restricted to 5 hours and the employee should put in more than two hours for the Overtime to be valuated.

Similarly for the Weekly Off Sunday, the following is the Generation Rule configured.

As discussed earlier, for the Time Wage type Selection rule – 004(Generation Rule for the Weekly Off –Sunday) , Time Wage type Selection Group value ‘03’ is picked from the PCR TMON and The DAYMO Grouping is 02 (Sunday & Not A public Holiday).The wage type earlier created for the Overtime Compensation 7OVT is given in the Wage type field which needs to be populated with the overtime worked values.In the conditions for the day , we give in the details as to how the system should calculate the overtime worked and should be processed.As in in the previous slide, in the table we see that under the block conditions for the day w have maintained certain rules for the day.

1. Weekdays – Only Sunday is marked here according to the day Grouping given DAYMO - 02


3. PH For Current Day – Referring to current day. It should be 0 (Working Day) as Weekly Off is not a public holiday and should be considered as a working day.

4. PH For Sub Day - Referring to public holiday for the Next day. Here it does not effect the current day. So we select al the classes.

5. Valuation Class for PWS – Defined in the path mentioned in the previous slide, we need to assign a valuation class to the PWS( Table – V_551C_B) of the Respective Employee.

6. DWS Class – Here the DWS class would be 0 as it is an weekly off. Hence letting the system know that the Planned hours for that day is 0.

7. Day Type – Here the Day type would be 0-Work and Paid as weekly off s usually considered as a working day. Except for that the planned hours are ‘0’.

Similarly for the Public Holiday – Mon - Sat, the following is the Generation Rule configured

For the Time Wage type Selection rule – 003(Generation Rule for the Public Holiday) , Time Wage type Selection Group value ‘03’ is picked from the PCR TMON and The DAYMO Grouping is 03 (Mon-Fri and Public Holiday).The wage type earlier created for the Overtime Compensation 7OVT is given in the Wage type field which needs to be populated with the overtime worked values.In the conditions for the day , we give in the details as to how the system should calculate the overtime worked and should be processed.As in in the previous slide, in the table we see that under the block conditions for the day we have maintained certain rules for the day.

1. Weekdays – Here all weekdays except for Sunday need to be marked as DAYMO for Mon-Sat is


3. PH For Current Day – Referring to current day. It should be 1 (Public Holiday)4. PH For Sub Day - Referring to public holiday for the Next day. Here it does not effect the

current day. So we select al the classes.5. Valuation Class for PWS – Defined in the path mentioned in the previous slide, we need to

assign a valuation class to the PWS( Table – V_551C_B) of the Respective Employee.6. DWS Class – Here the DWS class would be according to the DWS class you have assigned to

your DWS Rule in table- V_T550A.7. Day Type – Here the Day type would be 1- Off and Paid as it is a Public Holiday.

PROCESSING OF TABLE T510S ENTRIES IN DURING TIME EVALUATION

Processing of Time wage type Selection rule for Overtime worked on Saturday – 07.01.2012:

TIP entry FOR Function GWT before Processing of the table T510s-

Processing of the Table T510s based on the entries given for that current day . Here The current day is a Saturday and the oT generated through TO02 is 9 hours.

Output: The output we are looking for is the generated wage type needs to be sent to the table ZML .

TC40 is the PCR which calls the data from the ZML table and Processes and sends it to the DZL table from where it is imported to ZL table using CUMBT function in the PCR.

The rule Queries on the Processing Class 17 specification assigned to the Wage type 7OVT. Here the Specification is 0 for this Processing class which stores the value as generated.

Processing of the Rule TC40 :

Output for The PCR TC40 wherein we see that DZL table contains the generated Time Wage type.

Similarly please find enclosed in the following Slides the processing and out puts for each of the days the employee has worked Overtime.

i.e. Overtime Worked on 09.01.2012 – Working Day (4 Hrs)Overtime worked on 15.01.2012 – Sunday ( 9 Hrs)Overtime worked on 26.01.2012 – Public Holiday (9 Hrs)

In total the employee has worked 29 hrs as Overtime which has to be compensated @150% as defined in the table v_512w_b under Valuation.

Input Table for Overtime worked on 09.01.2012 ( Weekday)

For this Scenario, In table T510s, in conditions of time, We have given that for a weekday Overtime should be valuated only after EE has put in more than 2 hrs for the day and have restricted to maximum of 5 hours, I.e. even though the employee works for 7 hours OT that day, only 5 hours of the whole OT worked would be valuated and paid.

The following Slide Shows how the time Wage type is populated for that day.

Here, Based on the conditins for the day, the system chooses the Generation Rule 001 as it is a working day.

Output for this scenario is as follows:

Using rule TC40, the same is sent to the DZL Table:

The same is picked up by the ZL table through CUMBT function and is processed in Payroll for payment.

Input Table for Overtime worked on 15.01.2012 ( Weekly Off- Sunday & DAYMO Grouping – 02)

Processing of the table for the Day :

Output Table entry For that Day :



Input Table for Overtime worked on 26.01.2012 ( Weekday - Public Holiday & DAYMO Grouping – 03)

Processing of the table for the Day :

Output Table entry For that Day :



PAYROLL RUN FOR THE EMPLOYEE FOR THE MONTH OVERTIME WAS WORKED

TCODE :– PC00_M40_CALC Payroll for the employee is run for the month the Overtime was worked. The function ZLIT in the Schema IN00, Sub Schema XT00 fetches the Wage type from the ZL table and imports it to the IT Table. From where it is picked up for Valuation.

ZL table Entries

IT Table before the Wage types are added

Output IT table after fetching the values from the ZL table

Here, The Wage type is added to the IT table for valuation. In total there are 29 Hours that are to be valuated. Hence, through Function ZLIT this is achieved.

Rule X015 valuated the Time wagetypes based on the Valuation basis & percentage defined for the Wagetype in the Table V_512W_B ,

Input for Rule X015 –

Output Table for X015 – Here as mentioned earlier , We hve given the valuation percentage at 150% of the existing per hour rate. Hence We have the value as follows – 406.7*150% = Rs 610.05 (Rounded off to 610.1)610.1 *29 Hours = Rs 17,692.00

The Payslip for the month is as follows

THANK YOU

Overtime Generation and Valuation Using T510S

Documents

Transcript of Overtime Generation and Valuation Using T510S