6. DISCUSIÓN
6.1. D ISTRIBUCIONES DE FRECUENCIAS DE LONGITUD SIMULADAS
6.1.2. Con selectividad sobre algún grupo de tallas
Lesson Duration: 75 Minutes
Lesson Overview
This lesson gives you an overview of how the time evaluation driver RPTIME00 works, how it ensures that time and labor data is evaluated without gaps, and how the data is saved.
Lesson Objectives
After completing this lesson, you will be able to:
• Run time evaluation
• Name the periods over which time and labor data can be evaluated
• Describe the data required by time evaluation as input
• Find out about the results of time evaluation
This lesson explains the concept of the time evaluation driver RPTIME00 and how it works. The lesson is central to the understanding of time evaluation and learning how to execute it.
Business Example
You have run time evaluation for an employee. You receive a message during time evaluation that you cannot explain. You therefore want to analyze the time evaluation run, correct the error, and run time evaluation again.
Concept of the Time Evaluation Driver RPTIME00
Figure 14: Evaluating Time Data
Explain that time evaluation consists of particular processing steps that are run in a fixed sequence. The individual processing steps are explained in detail later in the course.
Time data is evaluated in several processing steps, which are carried out in a fixed sequence. You determine the sequence and the individual processing steps in an evaluation schema in Customizing.
Figure 15: Time Evaluation Driver RPTIME00
First explain how time evaluation is carried out and for whom.
Time evaluation is generally run once daily (during the night as a background job) for a large number of employees. The results of that day are then available the next morning.
Time evaluation can also be run for individual employees for a given period, for example, for test purposes.
Mention the types of results again (messages, time wage types and time accounts, infotype updates).
Time evaluation is performed by the time evaluation driver RPTIME00. Time evaluation generally runs daily, overnight, and is scheduled as a background job. The evaluation usually encompasses as large a group of employees as possible.
You can also run time evaluation for individual employees, employee groups, or for past evaluation periods for test purposes, for example.
The time evaluation report can also be run for future periods. Evaluating future periods can be useful in the following situations:
• You want time evaluation to determine an employee’s anticipated absence entitlements when absence quotas are accrued automatically
Important time wage types
• Night bonus / bonus for work on a public holiday / overtime wage types Time wage types are primary wage types that are formed during time evaluation, provided that predefined conditions are fulfilled. Time wage types are formed on the basis of time information. They enter Payroll only as a number. They are not valuated on a monetary basis until they enter Payroll.
Important time accounts
• Flextime / overtime / attendance hours / attendance and absence quotas / planned working time
To access the time evaluation report, choose Human Resources→Time Management→Administration→Time Evaluation→Time Evaluation. You can also access time evaluation at other points in the time management menu.
Figure 16: Maintaining the Results of Time Evaluation
Use the slide to explain the following points:
• Time evaluation results are stored on a monthly basis. This is what is known as the time evaluation period and is the same for all employees.
Data is stored on the database by month for technical reasons; you can run time evaluation for any periods.
• Time evaluation evaluates each individual day and saves the results for the day to the database.
• It starts with the results of the last day to be evaluated completely.
• In the case of a recalculation, all days in the recalculation period are evaluated again.
The ability to run recalculations is a distinct advantage of SAP time evaluation. Emphasize that time evaluation guarantees an evaluation without gaps.
• Up to the current date, time evaluation uses the employee’s actual times to determine the times worked. For evaluations of future periods (starting with the day after the current day), it uses the employee’s planned times as a basis if no actual times have been recorded.
Time evaluation is usually run once daily, but can also be run for any period of your choice. The results are then determined for each individual day in the period.
The results are stored in file PCL2 in Cluster B2 according to the day being
Storing the results for individual days means that time evaluation can return to the results of a particular day at any time to perform a recalculation.
Hint: If back-dated changes are made to infotypes, a second evaluation can be triggered for days that have already been evaluated. This is controlled by the PDC recalculation field in the Payroll Status infotype (0003). If a recalculation is performed, RPTIME00 overwrites the previous results on the database.
Figure 17: Data Flow
Based on the data flow, explain which data is required by time evaluation and which results are generated. The previous results are required in order to update the current results (for example, to manage time accounts).
Only relevant in HR311: Point out that the TEVEN table is relevant only if external time recording subsystems are used.
Time evaluation processes the current master data, time data, and the time events. It groups the time events into pairs before it processes them. It refers to the previous evaluation results for many calculations, for example, for managing time accounts.
Balances, time wage types, and messages are generated and stored in file PCL2 in cluster B2. Certain infotypes are then updated.
Figure 18: Starting RPTIME00: Parameters
Show the RPTIME00 selection screen in the system.
Important program options of RPTIME00:
• Display log:
All the processing steps and substeps of the evaluation schema are logged.
• Test run (no update):
Simulation mode: Time evaluation is run without changes to the database.
Sample variants:
• Test mode:
Program options Display log and Test run
• Background processing:
All parameters BLANK except the schema
Figure 19: First Day to be Evaluated
The first day to be evaluated is determined automatically by SAP R/3.
Prerequisites for a correct evaluation:
• Time data must be evaluated without gaps
• Back-dated changes to employee data that affect the payroll must lead to a recalculation of the results already determined (= changes relevant to a recalculation)
If there are no changes relevant to a recalculation, time evaluation returns to the day after the last day evaluated without errors.
RPTIME00 checks the first day evaluated for each employee by reading the information in the Payroll Status infotype (0003). The system constantly updates the Payroll Status infotype (0003).
If you want to evaluate a period before the last day to be evaluated without errors, you can use the RPTIME00 parameter Forced recalculation as of to reset manually the first day to be evaluated.
To prevent the system processing periods that are no longer relevant to Payroll, you can set an earliest recalculation date:
• For individual employees:
Using the Personal earliest recalculation date field in the Payroll Status infotype (0003)
• For multiple employees:
You define the date in Customizing. For more information, see the Implementation Guide for Personnel Time Management and choose:
Time Evaluation →General Settings→Set Modifier for Earliest Recalculation Date
Time Evaluation→General Settings→Set Earliest Recalculation Date for Pair Formation/Time Evaluation
The earliest recalculation date for time evaluation specifies the earliest past date back to which time evaluation can run. This also applies if an employee’s Personal earliest recalculation date field in the Payroll Status infotype (0003) is before the value specified in Customizing.
The Personal earliest recalculation data for time evaluation is automatically set when time evaluation results are archived.
Figure 20: Recalculation Trigger
For each infotype, you can determine in the Infotypes view (V_T582A) whether changes are relevant to a recalculation. You can use the Retr.acct.PDC field to define which condition should trigger a recalculation:
• Any changes made to an infotype, or
• Only changes made to certain fields in the infotype.
You can determine which fields in the infotype should initiate a recalculation in the Field-Specific Recalculation Indicator view (V_T588G).
For more information, see the Implementation Guide for Personnel Management and choose:
• Personnel Administration→Customize Procedures→Infotypes→Set Up Infotypes
• Personnel Administration→Customize Procedures→Infotypes→Define Fields Relevant for Retroactive Accounting
Figure 21: How Were the Results Achieved?
Explain the meaning of the time evaluation log and how to use the log, referring to an example in the system. Show the participants how to access the time statement from the time evaluation log.
RPTIME00 generates a log for every time evaluation run. You can control the scope of the log in the program options for RPTIME00.
The time evaluation log is divided in the following way:
• A non-employee-specific section
• Employee-specific sections (dependent on the error status of the personnel numbers)
• Multiple-employee sections: all messages, statistics
You can expand the log to a particular level of detail. This allows you to track the input and output of the individual processing steps when the Display log parameter is activated.
You can save the level of detail as a variant, and access it at the start of RPTIME00 by using the Display variant log field.
Figure 22: Storing the Results of Time Evaluation
Explain the significance of the two clusters relevant to time evaluation, B1 and B2. Give a brief introduction to the contents of the most important tables in the clusters and their additional business use. Be sure to mention that the time evaluation results in cluster B2 are stored in relation to the time evaluation period.
Show the participants the cluster report RPCLSTB2 in the system so that they can see the complete results of a time evaluation run.
The file PCL2 contains the cluster B2, which is relevant for time evaluation:
• You can use report RPCLSTB2 (Display Time Evaluation Results (Cluster B2)) to view all the results of time evaluation, and the basic data and time data for each time evaluation period.
The time evaluation period is identical for all employees. In the standard system, it is one month.
The file PCL1 contains the cluster B1, which is relevant for time evaluation:
• You can use report RPCLSTB1 (Display Recording Data (Cluster B1)) to obtain an overview of all the processed and unprocessed time events, generated and not yet corrected or confirmed messages from time evaluation, and important status fields.
You can use the report RPCLSTxx (xx = name of the cluster) to view different clusters in the databases PCL1 and PCL2.
Menu: Human Resources→Time Management→Administration→Tools→ Tools Selection→Cluster
Figure 23: Archiving the Results of Time Evaluation
Only mention here that it is possible to archive the results of time evaluation.
Time evaluation should be archived at the same time as the results of Payroll.
This can be done using the archiving transaction.
Refer participants to the HR530 course (Technical Aspects in HR), which covers the archiving transaction in more detail.
The technical buffer is required during archiving to ensure that recalculations are performed correctly.
Menu: Human Resources→Time Management→Administration→Tools→ Archiving
The archiving is employee-specific. You can use a report to select employees according to particular factors (for example, employees’ leaving dates).
Only periods that are no longer relevant to a recalculation are archived, since archived periods cannot be recalculated.
When archiving the data, the transaction uses a buffer of an evaluation period to guarantee that any possible recalculations are taken into account if the previous day assignment is changed. The archiving transaction limits the the earliest recalculation date by changing the Earl.pers.rec.date field in the Payroll Status infotype (0003).
You can display the archived periods using the report RPCLSTB2 (Display Time Evaluation Results (Cluster B2)) if the system meets the access requirements.
For more information about archiving time evaluation results, see the SAP Library and choose Human Resources→HR Archiving→Archiving Data→ Archiving Payroll Results or Archiving Time Evaluation Results
Figure 24: Overview of Time Evaluation
This slide revises the contents and is intended to illustrate the process of time evaluation on a technical level. The significance of the individual cluster tables is addressed later in the course.