Customizing Time Evaluation

Objective

After completing this lesson, you will be able to explain time evaluation features, time type significance, and how to adjust the time evaluation process.

Time Evaluation: Structures, Customization, and Practical Implementation

Screenshot of the Implementation Guide for Time Evaluation, showing expanded menu options under Personnel Time Management, Time Evaluation, Time Evaluation with Clock Times, and Time Evaluation Without Clock Times

The standard system supplies several personnel calculation schemas (or schemas for short), which have different requirements for time data to be evaluated, and which follow different evaluation strategies.

The Implementation Guide (IMG) contains two chapters that describe the two most important standard schemas. They also give a detailed explanation of how you can modify the schemas to suit your own company's requirements:

Time evaluation with clock times (standard schema TM00)

Time evaluation without clock times (standard schema TM04)

Diagram showing components of time evaluation customization: driver, rule processing/evaluation schema, and tables/views for payroll and time data

The rules that govern the valuation of time data are not hard-coded. This means that you have a variety of options for modifying time evaluation to suit your own requirements.

The boxes highlighted in color indicate the areas of time evaluation that you can customize.

The processing steps of time evaluation are grouped together in the schemas. The schema determines how time evaluation processes the steps and in which sequence. The system reads values from various Customizing tables during processing.

To start time evaluation, specify in the selection screen for RPTIME00 the schema you want to use to evaluate times.

Time data processing by the payroll driver has the same processing structure as within time evaluation.

Flowchart illustrating steps for time evaluation: select employees, define evaluation period, process rules/schema, export results, update infotypes.

The time evaluation driver evaluates employees' time data on a daily basis.

The individual processing steps that are defined in a schema are called functions. They are carried out in a particular sequence, which is determined by the arrangement of the functions in the schema.

Functions have precisely defined attributes. Some functions are used to carry out necessary, and therefore standardized, processing steps of time evaluation (for example, selecting time wage types).

Diagram explaining how functions and operations work, with steps including trigger processing, personnel rules, evaluation, and data customization.

Functions can carry out a variety of tasks, for example:

  • Set a switch for time evaluation

  • Carry out processing

  • Trigger processing

Some functions allow you to describe the individual processing steps more precisely, by accessing personnel calculation rules. In them, a sequence of elementary processing steps is carried out. The processing steps are triggered by operations. You can use the operations to:

  • Query whether the employee was at work

  • Query the day type of the day being evaluated

  • Form time balances

Functions and operations can query values that you have set in time evaluation views.

Screenshot of HR Documentation Maintenance interface showing document class Function (Time Management) and options for selecting object names

You can use the PDSY transaction (HR Documentation Maintenance) to access the documentation of all schemas, functions, personnel calculation rules, and operations. If necessary, you can create the documentation for specific clients.

To obtain a list of these objects, enter the appropriate documentation class, and use the possible entries help for the Object name field. You can also display the list in a modeless dialog box to keep a list of all operations while you are creating personnel calculation rules, for example.

Documentation classes relevant to Time Management:

  • SCHE: Personnel calculation schemas

  • CYCL: Personnel calculation rules

  • FUNT: Time Management functions

  • OPET: Time Management operations

  • 549B: Features

  • PRCL: Processing classes

  • SKON: Symbolic constants

When you maintain schemas and personnel calculation rules, context-sensitive HR documentation is displayed when you access the field help (F1).

Screenshot of the Personnel Calculation Schemas: Initial Screen, highlighting schema attributes such as program class and responsible person

You can use the schema editor (Transaction PE01) to display and maintain personnel calculation schemas.

You can determine characteristics of a schema in attributes. You can choose to permit only the person responsible to change the attributes and the schema.

The program class indicates where the schema is used (C = Payroll; T = Time Management).

The country grouping specifies whether the schema can be used in the country-specific versions of the payroll driver. There are no country versions of RPTIME00. The country grouping is therefore always assigned the value "*".

To access the tree structure for the schema to display the individual processing blocks, choose UtilitiesStructural graphics. You cannot edit the schema in the structural graphic.

Menu: Human ResourcesTime ManagementAdministrationToolsMaintain Schema.

Schema Editor layout with highlighted command line, line commands, function codes, parameters 1-4, inactive function, and descriptive text column

You can use the schema editor to display, change, and create schemas.

You can use the standard help function (F1 Help) in the schema editor to access documentation according to context (by positioning the cursor on a function, personnel calculation rule, and so on) as follows:

F1 help from the command line: Documentation for all permitted commands

F1 help from a line number: Documentation for all permitted line commands

Screenshot of the Personnel Calculation Rules initial screen with options to manage source texts, attributes, and documentation for rule TE20

You can use the personnel calculation rule editor (Transaction PE02) to display and maintain personnel calculation rules.

You edit personnel calculation rules according to the employee subgroup grouping for personnel calculation rules and the wage type or time type.

You can determine characteristics of a personnel calculation rule in attributes. You can choose to permit only the person responsible to change the attributes and the personnel calculation rule.

The program class determines where the personnel calculation rule is used (C = Payroll; T = Time Management).

The country grouping specifies whether the personnel calculation rule can be used in the country-specific versions of the payroll driver. There are no country versions of RPTIME00. The country grouping is therefore always assigned the value "*".

You can choose between two user interfaces to edit personnel calculation rules:

If you choose UtilitiesStructural graphics, the personnel calculation rule is displayed in a tree structure. If you choose UtilitiesTable display, you can edit the personnel calculation rules in a table view.

Menu: Human ResourcesTime ManagementAdministrationToolsMaintain Personnel Calculation Rules.

Diagram of the Rule Editor layout showing employee subgroup rules, variables, time type, and decision logic for planned work hours and employee presence

You can use the rule editor to display, enter, and change personnel calculation rules.

The variable key is used to build a decision tree. The decision tree enables you to perform processing differently according to organizational aspects, for example. It is only used for decision operations.

For each personnel calculation rule, the length of the variable key must not exceed 8 characters, inclusive of the spaces necessary between the keys.

If the length of the variable key is insufficient, you can use the PCY operation to branch to another personnel calculation rule. After this rule is processed, processing returns to the original personnel calculation rule, and the continues with the next operation in the line.

You can also use the GCY operation to branch to another personnel calculation rule. After this rule is processed, processing does not return to the original personnel calculation rule.

You can access context-sensitive documentation on the operations by using the F1 help.

To display a key of the colors used to identify different objects in the tree display, choose UtilitiesColor legend.

A chart showing time accounts and financial details for John Miller, including deposits, withdrawals, and productive hours calculation

You can use time evaluation to manage time accounts such as:

  • Overtime

  • Planned times

  • Flextime balances

Time accounts can be

  • Accumulated and deducted

  • Used for employees' information

  • Used to create statistics

Managing a time account is similar to running a bank account. Bank accounts and time accounts have the following features in common:

  • They are person-related

  • They are time-related

  • They are credited and debited

  • They show a certain value (credit) at a certain point in time

RPTIME00 maintains time accounts according to defined processing steps. The value of the respective time account is updated on every day that is processed in time evaluation.

Screenshot of Time Types view with data tables on planned, skeleton, and flextime balance, showing dates, time types, and numerical values

A time type is a technical name for a duration, and assigns it a concrete meaning. Time types that are related in a business administration context can be cumulated during time evaluation to form balances.

You can use the Time Types view (V_T555A) to determine which time types filled during time evaluation are stored as evaluation results. The following control options are available:

  • Transfer to total for day: Save in table ZES

  • Transfer to total for month: Cumulate in table SALDO

  • Transfer previous month/year: The value of the time type is passed on at the start of a new period or year.

  • Time type start of new period/year: At the start of a new period or year, the value of the time type is stored under the new time type specified.

  • Storing for time accounts: You can use report RPTDOW00 (Time Accounts) to evaluate the balances.

Up to 10 balances can be downloaded to the time recording system.

For more information, see the Implementation Guide for Personnel Time Management and choose Time EvaluationTime Evaluation SettingsDefine Time Types..

Diagram illustrating Time Type as a tool in time evaluation, showcasing grouping durations, forming balances, transferring times, and calculations

Time types perform many tasks during time evaluation. Important balances that are formed by calculations, transfers, or grouping of time types are collected into time types and made available for storage in cluster B2.

Flowchart illustrating time evaluation processing, including driver execution, schema processing with rules, and evaluation customization via tables/views

The complex processing structure of the time evaluation driver, schema processing, and evaluation customizing allow you to set up most of your requirements for time evaluation. If the options available in the standard system are not sufficient, you can also create your own functions and operations.

Menu: Human ResourcesTime ManagementAdministrationToolsFunctions/Operations

Related Information

For more information about the time management infotypes, see the SAP Library and choose: Human ResourcesPersonnel Time ManagementTime EvaluationTime Data Processing in Time Evaluation.

Glossary

Example

Time type:

Grouping of time and labor data that can be determined in time evaluation.

A time type is a technical name for a duration, and assigns it a concrete meaning. Time types that are related in a business administration context can be cumulated during time evaluation to form balances.