Generation of time wage types is considered as one of the very important and complex concepts in time management. It is important because it drives the time based payments such as shift allowance, overtime etc. for an employee and its complex because of the numerous combinations of rules that can be configured. Also, when multiple rules are applicable for any particular group of employees, utmost care needs to be taken in designing the rules so that any undesired wage type does not get generated mistakenly.


This document would focus on explaining all the fields of a rule created in T510S. Also we would see some examples for detailed understanding. This document is created with an assumption that the reader has a basic understanding of time pair formation and processing types.


Let’s take a look at how the screen looks like and then we’ll understand all the fields in detail.
/wp-content/uploads/2014/09/1_551977.png

Time WT Sel. Rule group: Grouping assigned to MODIF W


Day Grouping: Grouping assigned to MODIF D. Same grouping can be assigned to all those employees for whom the same set of time wage types are applicable and have same rules of their generation.


Sequential No.: In case multiple rules are to be defined for the same set of employees under MODIF W and D, they can be defined sequentially specifying the sequence number.


Wage Type: The time based wage type to be generated if all the conditions of the rule are satisfied. This WT is written to ZL once generated.


Valid Processing Types: System allows any rule to be applicable for 4 different processing types which can be listed in this section. If any time pair has a processing type listed among these 4, then this rule would be evaluated for that time pair.


Conditions Day: This section specifies a list of conditions based on the working day of the employee, each of which should hold true for the wage type to be generated.


Weekdays: Each position in this field specifies a day of the week with 1 being Monday and 7 being Sunday. X at any position denotes that the rule is applicable for that day. Thus if we have X at the first 5 positions, it would mean the wage type can be considered for generation only from Monday to Friday.


PH pre. Day: Each position in this field denotes a holiday class on the previous day. The first position means holiday class 0 (not a public holiday), second position means holiday class 1 (full day public holiday) and so on. This field is used to specify a condition for the previous day for WT generation. For example, we may want to generate a WT only if the previous day was not a public holiday. In this case we will only put a X under the first position, i.e. for holiday class 0.


PH cur. Day: Each position in this field denotes a holiday class on the current day, starting with Holiday Class 0 (current day is not a public holiday) to Holiday Class 9. This can be used in cases where a wage type needs to be generated based on whether the current day is a public holiday or not.


PH sub. Day: Each position in this field denotes a holiday class on the subsequent day. This can be used in cases where a wage type needs to be generated based on whether the next day is a public holiday or not.


Valuation Class: If any wage type needs to be generated for employees on specific period work schedule, then this section can be used to make the rule applicable for the appropriate valuation class of the period work schedule. Table V_551C_B defines the valuation class for a PWS and the same can be positioned in this section. The positions are from 0 to 9.


DWS Class: This section can be used to make the rule applicable for specific DWS Classes. The positions denote DWS class from 0 to 9. Generally, DWS classes are used to categorize the different work shifts. Thus as an example, if we have defined DWS class 1 for morning shift and we want the rule to be applicable for only morning shift then we put a ‘X’ at the second position.


Day Type: If you want a specific wage type to be generated only for specific day types, this section can be utilized.


Conditions Time: SAP provides a provision to allow generation of wage types based on specific timing that the employee has worked for. This is configured in the section for Conditions Time. If has the below fields:


Start and End: These fields are used to specify the start and end time within which the time pair should exist or should atleast partially overlap for the wage type to be generated.


Min.: This field is used to specify the minimum number of hours for which the employee should work within the specified time frame for the wage type to get generated.


Max.: The maximum number of hours for which the wage type would be generated. For example, an employee worked overtime from 6pm to 11pm but this field for the overtime WT has 3 hours, then the overtime WT would be generated only for 3 hours even though the employee did an overtime of 5hrs.


Relevant Proc. Type: Out of all the processing types which are valid for the rule, this section can be used to specify which ones would be applicable for the “Conditions Time” section. For example, meal allowance WT is generated for 2 processing types – S (for working day) and X (for public holiday). However, we want to give meal allowance only if the employee has worked between 9am to 4pm on the public holiday.  In this case, only X would be mentioned in the Relevant Proc. Types section and Start and End times specified accordingly.


Interval: This checkbox is used to indicate how the time pairs would be considered in comparison with rule’s time interval for the wage type generation. When this is selected the system starts the hours calculation from the start of the rule interval. If not, then from the start of the time pair interval. This is elaborately explained in the examples shown further in this document.


Fixed Val.: This field is used to specify the fixed number of hours for which the wage type would get generated if day conditions are satisfied irrespective of the actual duration of work.


Exit Rule: Using this field you can specify that the system stops processing the current rule as soon as the wage type for a TIP entry is selected. Time wage type selection is then continued with the next rule.


Stop Time Wage Type Selection: Using this field you can specify that the system stops time wage type selection as soon as the wage type for a TIP entry is selected. The rules which follow are then no longer taken into consideration during time wage type selection.


Now let’s go through some examples.


For all the below examples, we would consider an employee working from 7:00 to 19:00 as standard working hours for the day. Also we would consider the “Conditions Day” section to be true for the employee. Our focus would be on the “Conditions Time” section. Let us first see some examples where we have used the minimum hours criteria. The rule looks like below:

/wp-content/uploads/2014/09/2_551984.png

Example 1: Overtime booked from 5:00 to 7:00.


Time pair generated is as below: (Processing Type M = overtime)

/wp-content/uploads/2014/09/3_551985.png

/wp-content/uploads/2014/09/4_551986.png

Here the wage type does not get generated as the time pair for overtime does not exist between 21:00 to 24:00.


Example 2: Overtime booked from 21:00 to 22:00

/wp-content/uploads/2014/09/5_551987.png

/wp-content/uploads/2014/09/6_551988.png

Here again, the WT does not get generated as it does not meet the condition of minimum 2hours. Thus, even though our time pair lies within the timeframe condition but since it does not meet the minimum hours criteria the WT doesn’t get generated.


Example 3: Overtime booked from 21:00 to 22:00 and 23:00 to 24:00


Here, even though we have booked 2 hours of overtime they are not continuous. The TIP looks as below:

/wp-content/uploads/2014/09/7_551989.png

/wp-content/uploads/2014/09/8_551993.png

Even though the employee has actually worked 2 hours between our condition timeframe, the overtime still does not get generated as the individual time pair does not meet the minimum criteria. Thus for the condition to hold true it is important that it should get satisfied for a single time pair.


Now let us see some examples for the maximum hours criteria. The work timings of the employee remain same as 7:00 to 19:00. We would use the below rule for our testing.


First lets check and example where the Interval checkbox is selected.

/wp-content/uploads/2014/09/11_551995.png

Example 1: Overtime booked from 00:00 to 06:00.

/wp-content/uploads/2014/09/12_552002.png

/wp-content/uploads/2014/09/13_552003.png

/wp-content/uploads/2014/09/14_552004.png

Since the checkbox for Interval was selected in the rule, the system started the hours calculation from the start of the rule’s interval which is 2:00. Thus, it calculated 4 hours of the time pair which overlapped with the rule interval, thereby generating the wage type from 2:00 to 6:00.

Now lets see how the system behaves when the checkbox for Interval is not selected for the same situation.

/wp-content/uploads/2014/09/15_552005.png

Below is how it gets processed:

/wp-content/uploads/2014/09/16_552006.png

/wp-content/uploads/2014/09/17_552007.png

As you see here, only 2 hours of overtime wage type is generated. The reason being that the system starts the calculation of overtime hours from 00:00 since the Interval checkbox is not selected. Also, since we have set the max limit as 4 the system calculates hours only from 00:00 to 04:00. Now this interval overlaps with the rule only for 2 hours from 02:00 to 04:00. Thus, the wage type is generated only for 2 hours.

The rules can be configured in several ways based on what the requirement is. The best way to understand the functionality in greater depths is to try out different situations. Happy Learning!!


Regards

Shruti

To report this post you need to login first.

12 Comments

You must be Logged on to comment or reply to a post.

Leave a Reply