Managing Time Accounts

Objective

After completing this lesson, you will be able to manage employee time accounts by grouping time types, transferring times, checking value limits for time balances, and specifying appropriate system responses.

Managing Time Accounts

Funnel-shaped flowchart showing steps in time management process, with Manage time accounts highlighted
Diagram illustrating how time types are grouped into larger units for forming day balances in personnel calculation rule TR10

The TR10 personnel calculation rule adds the number of hours in the TIP entries to various comprehensive time types (time balances) to form day totals. The results of processing are entered in the TES table (day balances).

A diagram illustrating balance formation and time type determination

Time pairs in TIP have been split using the TIMTP function and classified by a time type and a processing type.

The TR10 personnel calculation rule now adds the number of hours in the respective time type to various comprehensive time types (time balances). You should read the entries in the Time Type Determination view (V_T555Z) as follows:

  • Horizontally to determine balances that relate to points of time in the day (for example, breaks, overtime hours)

  • Vertically to determine balances that relate to employees’ attendance and absence statuses

Diagram showing Function P2012 transferring hours from flextime balance to comp. time using specifications

Time transfer specifications allow you to change the results determined by time evaluation. You can use them to represent special situations related to individual employees or to ensure legacy data is transferred (such as the transfer of the flextime balance).

You can use time transfer specifications to transfer hours from a time type, time wage type, or an absence quota to a:

  • Time type

  • Time wage type

  • Absence quota

In addition, you can also set time types to a fixed value.

The P2012 function processes the time transfer specifications for the current day using tables.

For more information, see the Implementation Guide for Personnel Time Management and choose Time EvaluationTime Evaluation With Clock TimesProcessing BalancesTime Transfer.

Diagram showing processing time transfer specifications

The time transfer specifications are processed for each day of the infotype’s validity period. You would typically create a time transfer specification for a day.

Up to three processing steps (transfer time balances, wage types, and absence quotas) can be performed for each time transfer type. It is therefore possible, for example, to reduce a time type and an absence quota by five hours and to pass on a wage type with five hours to Payroll.

Diagram illustrating how you can form important balances with the TR30 rule. It shows flexitime balance and productive hours calculation.

The TR30 personnel calculation rule provides an example of how you can use arithmetical conversions in a personnel calculation rule to form important day balances from the balances determined until that point. The TR30 personnel calculation rule determines the following balances:

  • The flextime balance of the current day

    To do so, it subtracts the planned working time according to the daily work schedule from the skeleton time (planned hours worked).

  • Hours of overtime worked

  • Productive hours

The TR30 personnel calculation rule is important in a business sense. The results of balance formation are used

  • As a basis for generating absence quotas (QUOTA function)

  • To check working time regulations

  • To display on the employee’s time statement

  • To compile statistics such as overtime levels, productive times, absence times

You can add any additional time accounts to the standard processing.

The diagram illustrates the use of Function LMIT to check value limits for time balances. The text provides more details.

Many working time regulations, company agreements, and so on stipulate that value limits must be checked. You can use the LIMIT function to process your rules for checking the balances determined by time evaluation. This allows you to check whether time balances exceed or fall short of the individual balance limits, and to determine appropriate system reactions. A flexible Customizing table is available for determining the rules. You can use it to meet the following requirements, for example:

  • Determining the value limits according to fixed values or employees' master and transaction data (for example, number of planned hours, maximum working time)

  • Checking value limits within flexibly defined periods

  • Generating messages to give advance warning, even when the value limit has not yet been exceeded

  • Transferring the excess to another time balance or another wage type

  • Storing time balances in another time type over freely-definable periods, for example, weekly balances

  • Limiting the area of validity of the rule depending on the employee's age

For more information, see the Implementation Guide for Personnel Time Management and choose Time EvaluationTime Evaluation With Clock TimesProcessing BalancesBalance FormationBalance Limits.

The diagram illustrates how the process to determine value limits for time balances. It covers operation, rules, determination, setting limits, comparing balances, processing, control, and age dependency.

The LIMIT function determines the balances to be compared with the value limit for a fixed processing period. It can process the balances in the following ways:

  • Add (cumulate) day or period balances

  • Find the highest value (maximum)

  • Find the lowest value (minimum)

You can use different processing periods and check points, depending on whether you are processing day or period balances. The check point is the time at which the system applies the rule, for example, at the end of the evaluation period. The LIMIT function can therefore be placed in the following positions in the schema:

  • Processing day balances in day processing

  • Processing period balances in final processing

When it checks the value limits, time evaluation runs through all the balance rules belonging to a time balance rule group, and processes the ones that meet the specified conditions.

You can also use the LIMIT function to perform a particular type of processing at a particular point in the schema. The processing is then performed for all employees identically. You can set a time balance rule group in parameter 2 of the function. Note that you must use the MODIF operation to reset the original time balance rule group after this processing block.

Diagram illustrating the process to update results with function, CUMBT.

The CUMBT function cumulates time types from table TES into tables ZES (day balances) and SALDO (month balances) according to the rules in the Time Types view (V_T555A). All time wage types are transferred via the CUMBT function (without additional control) from the DZL table to the ZL table.

Tables ZES, SALDO, and ZL are tables from cluster B2 in file PCL2.

Hint

After the CUMBT function, there must be no more functions in day processing in the schema that change the day balances in the TES table and the wage types in the DZL table. These results are no longer saved.

In order to ensure an error-free recalculation, the SALDO table may only be filled using the TES table, or in final processing (between BEND and EEND) at the end of the time evaluation period.

To do so, proceed as follows in final processing:

  1. Use the IF EOM function to query the end of the time evaluation period.

  2. Use the ADDMB operation in a personnel calculation rule to enter balances in the SALDO table.

  3. Exit processing with ENDIF.

For more information, see the Implementation Guide for Personnel Time Management and choose Time EvaluationTime Evaluation With Clock TimesProcessing BalancesBalance FormationUpdate Cumulated Balances.