Process Flow for SAP Time Evaluation

To the world of a time data-entry person or anyone not thoroughly familiar with SAP's time processing, time management would seem like a simple process. You enter an absence or attendance, give it some hours, and payroll magically spits out a paycheck. Right? Unfortunately, it's not as simple as that. While not everyone in your company needs to know the ins and outs of time evaluation, it is beneficial to have some basic knowledge of the process flow when errors occur or your company adds additional functionality.

There are actually several phases that an attendance goes through before it reaches payroll. When an attendance is entered through IT2002, it is given at least an attendance type and number of hours, yet could contain a range of clock times, premium indicators, cost assignment, or a variety of other information. This alone is not enough information to create a time wage type however.

When time evaluation begins it's processing of an attendance it first has to load the attendance into the time type table (TIP). Function P2002 takes the data from IT2002 and creates time pairs for the day. A time pair can consist of several pieces of data.

The start and end times of the attendance. If none are specified, they are assigned based on the start of the daily work schedule rule and the number of attendance hours plus any breaks.   Pair type/attendance status. The pair type is assigned based on the function that loads the time pair into the schema. Pair type 1 is designated if the attendances have been imported through time recording terminals (P2011) or generated on the basis on the daily work schedule (P2000). Pair type 2 is used if the pair types come from absences (P2002). And pair type 3 is used if, like in our example, the pair types come from attendances (P2002).   Processing type/time type class. Each absence and attendance has a processing type/time type class assigned to it via V_554S_F that will aid in the creation of time types and processing types.   Time event types. Time event types for the beginning time and end times of the time pairs if time events are utilized (IT2011). Example: clock-in, clock-out.   Attendance/Absence reasons.   ALP splits. Alternative payment splits such as substitutions or premiums are loaded into the time pair.   Cost splits. Assignment to differing cost centers is split out in the time pairs in table TIP.   OT and absence pointers.   Number of hours for each time pair.

The next stage in time evaluation will create a time type and processing type for each time pair entry in the TIP. Function TYPES reads the time pairs and references them with customer-defined settings in T555Y and the modifier set by MODIF T to create the time types and processing types. Function TYPES along with T555Y use the following inputs to create time types for each

Personnel Subarea grouping for time recording associated with the personnel number.   Time type determination group set by function MOD, MODIF T =.   Processing type/time type class associated to the time type as assigned by the attendance type from V_554S_F.   Pair type/attendance status assigned to the time pair.

All of these inputs are referenced against T555Y and a processing type (i.e. S = planned work, M = overtime) and time type are generated and stored in table TIP.

The next phase in time evaluation involves setting the day modifier for time wage type generation. This is either done by setting MODIF D= or using the function DAYMO. DAYMO provides more flexibility as it allows you to set the modifier for four day conditions: not a public holiday - MON-SAT, not a public holiday - SUN, public holiday - MON-SAT, public holiday SUN.

Now the time types are ready to become wage types. The standard SAP method for converting time types to wage types is through the Time Wage Type Selection Table, T510S. The table is called using function GWT, generate wage types. GWT can be called for specific processing classes and the outputs can be stored in either the daily time wage types table, DZL, or the daily overtime wage types table, ZML. Table T510S can seem complicated to read but it allows for a very flexible method of time wage type generation in a variety of circumstances. There are several inputs to the table which define criteria for time wage type generation.

The time wage type selection rule group as set by MODIF W=   The day grouping as set by MODIF D= or DAYMO

These two criteria define a time wage type determination rule. The rule is made up of multiple table settings.

Up to four valid processing classes (S = planned time, etc.) are available per rule.   The days of the week, M-F, in which the rule is active.   The public holiday class of the previous day.   The public holiday class of the current day.   The public holiday class of the next day.   The daily work schedule class (working day, off days, etc.)   Specific day types for the wage type to be generated.   You can define time range during which the wage type can be generated (i.e. 19:00 - 30:00 for shift differential)   A fixed number of hours to store in the generated wage type.

When this is completed, the newly generated wage types are stored in either table DZL or ZML. The time wage type contain the following information.

Date of the attendance.   Start and end times of the attendance.   The wage type.   The information type. This is similar to the processing class associated with time types (M = overtime). · Alternative payment splits. These are created by premium indicators or shift substitutions.   Cost center splits.   Absence pointers.   Number of hours.

The time wage types will now become inputs to payroll processing when they are imported into the country-specific payroll driver (RPCALCU0 for the US, for example).