Balances are formed using time types. Time wage types are formed according to the processing type of the TIP entry.
The processing type and time type have a central significance for time evaluation:
Time types
The time types and the number of hours of the various TIP entries are cumulated to form time balances.
Processing type
The time wage types are selected according to the processing type
Example:
Processing type S→planned working time wage types
Processing type M→overtime wage types
The TIMTP function is used to merge the TIP entries (actual times) with the daily work schedule in the TZP table (planned times). This results in new TIP entries.
Through the comparison, the TIP entries receive a description of their position in relation to the Customizing entries of the employee's daily work schedule that applies on the day being evaluated (time identifier). The time identifier of the newly formed TIP entries determines whether the times are in the core time, fill time, time outside the daily work schedule, and so on.
The time identifier is used to assign a processing type and a time type to each new TIP entry according to the pair type. To do this, the TIMTP function reads the entries that are defined in the Customizing settings in the Time Type Determination view (V_T555Z).
The function also carries out the following activities:
Planned times for which there are no corresponding actual times are assigned TIP entries with the pair type 0
The resulting TIP entries are assigned a processing type and a time type according to the Time Type Determination view (V_T555Z).
For more information, see the Implementation Guide for Personnel Time Management and choose Time Evaluation→Time Evaluation With Clock Times→Time Data Processing→Set Time Type Determination.
A new TIP entry is formed in the TIP table for each new time point in the daily work schedule. In this process, the entries from TIP are compared with those in TZP.
In the Time Type Determination view (V_T555Z), you define which time types and processing types the TIP entries are assigned, based on the time identifier and the pair type:
Pair type 0: Unrecorded times
Pair type 1: Attendances from time postings and planned pairs
Pair type 2: Absences (infotype 2001)
Pair type 3: Attendances (infotype 2002) and off-site work postings
Hint
SAP ERP determines the pair type automatically.
You can assign the following processing types as a default for time wage type formation:
S: Pair is included in the daily calculation of planned time, without a maximum working time per day
M: Pair is valuated as an overtime pair; the time is not included in the daily planned working time
P: Pair is valuated as an attendance pair, that is, the time is included in the daily calculation of planned time
A: Pair is valuated as an absence pair, that is, the time is included in the daily calculation of planned time
"-": Pair is deleted at a later stage
" ": Pair is not valuated as productive time
K: Germany only
Hint
Processing type A is assigned for paid breaks so that the times are not included in the calculation of the daily maximum working time.
The processing type "K" is required for the German country version only. It is assigned for breaks because it is required for determining core night work using the KNTAG function.
The following information is specified for each break in the work break schedule:
What time the break starts or how many hours the employee must work before taking a break
Whether the break is paid
What duration of the break is paid
The length of the break is the total of the paid break plus the unpaid break.
Hint
You can use the DYNBR function to control the position of the dynamic breaks. The DYNBR function must be before the TIMTP function in the schema.
Example: Counting starts with the first clock-in time, and not with the start of planned working time (standard processing).
For more information, see the Implementation Guide for Personnel Time Management and choose:
Work Schedules→Daily Work Schedules→Define Break Schedules
Time Evaluation→Time Evaluation With Clock Times→Time Data Processing→Break Processing→Set Start of Break Dynamically
The PBRKS function evaluates the break specifications from the daily work schedule.
Hint
You have to use the PBRKS function only if you process variable breaks. If you process only break schedules without variable breaks, the TIMTP function provides all the information regarding the positions of the breaks. You therefore do not require the PBRKS function in this case.
You use parameter 2 of the PBRKS function to define the sequence in which the TIP entries for the break are calculated: You specify the sequence in which particular times, such as partial-day absences or those for which there are no time postings, are to be counted towards the break time.
Example: You have a break frame between 12: 00 and 14:00 with a one-hour break. You want to allow your employees to take their break off work premises if they have a partial-day absence (such as a doctor's appointment) or an absence within the fill time (= unrecorded time).
Parameter 2 has the following specifications:
1 – Unrecorded times (pair type 0) first, then all others in chronological order
2 – Absences (pair type 2) first, then unrecorded times (pair type 0), then all others in chronological order
3 – Absences (pair type 2) first, then attendances or off-site work postings (pair type 1/3), then all others in chronological order
4 – Unrecorded times (pair type 0), then absences (pair type 2), then all others in chronological order
5 – Attendances or off-site work postings (pair type 1/3) first, then unrecorded times (pair type 0), then absences (pair type 2)
6 – Attendances or off-site work postings (pair type 1/3) first, then absences (pair type 2), then unrecorded times (pair type 0)
7 – Unrecorded times (pair type 0) first, then attendances or off-site work postings (pair type 1/3), then absences (pair type 2)
For more information, see:
The Implementation Guide for Personnel Time Management: Choose Time Evaluation→Time Evaluation With Clock Times→Time Data Processing→Break Processing→Determine Break Times
The documentation for the PBRKS function
In parameter 3 of the PBRKS function, you specify how unrecorded times are processed:
blank: Only times within the break frame are counted
AFT: Unrecorded times immediately after the break frame are included in the calculation
BEF: Unrecorded times immediately before the break frame are included in the calculation
ALL: Unrecorded times immediately before and after the break frame are included in the calculation
ABE: All unrecorded times before the break frame are included in the calculation
In parameter 4 of the PBRKS function, you specify which TIP entries are taken into account in break processing. Parameter 4 is relevant only if partial-day attendances or absences are recorded without clock times.
OWTI: Breaks are generated only for pairs with clock times
NOTI: The clock times of the pairs are ignored. Breaks must be defined in the break schedule/daily work schedule in the form after x hours.
The DEFTP function is used to determine the planned work TIP entries. The function assigns the processing type S to TIP entries with processing types A and P, thereby ensuring that processing type S is assigned until (at most) the maximum daily working time is reached.
You can specify the maximum daily working time in the Daily Work Schedule view (V_T550A). If there is no information in the daily work schedule, the DEFTP function uses the value of the TGMAX constant from the Payroll Constants view (V_T511K).
The TIP entries with processing type S are only preliminary planned working time pairs; they could partially become overtime pairs (processing type M) when overtime is determined.
The DEFTP function collects
All attendance and absence times in auxiliary time type 0000
All attendance times in the auxiliary time type 0001
Both time types are used for determining overtime and for reducing absences. Time evaluation uses them to ensure that
Overtime is not generated until after the planned working hours per day have been reached
Partial-day absences do not increase the actual working time
TIP entries with processing type "–" are deleted.
For more information, see the Implementation Guide for Personnel Time Management and choose Time Evaluation→Time Evaluation With Clock Times→Time Data Processing→Indicate Planned Working Time Pairs.
In the TP10 personnel calculation rule, you can reduce certain partial-day absences so that they do not increase the flextime balance, that is, the absences do not exceed the planned specifications.
The TP10 personnel calculation rule is particularly relevant to flextime models. The absence is reduced only within time evaluation. The Absences infotype (2001) is not updated in the process.
You specify which absences you want to be reduced by grouping the absences into classes for time evaluation in the Absence: Time Evaluation view (V_554S_E).
The flextime balance represents the difference between the actual working time that is calculated as planned work and the planned working hours stipulated in the daily work schedule. The following count as applicable times worked, for example:
Attendances
Paid leave
Sickness with certificate
Overtime
For more information, see the Implementation Guide for Personnel Time Management and choose Time Evaluation→Time Evaluation With Clock Times→Time Data Processing→Shorten Absences of Less Than One Day.