SAP AG

Appendix Overview

Chapter 5: Appendix
Overview
The appendix contains detailed technical information. It is revised regularly, and extended for subsequent versions.

Contents
Personnel Calculation Rules in Time Evaluation: Overview .................................. 52 Views and Tables in Time Evaluation: Overview .................................................... 53 Internal Tables in Time Evaluation .......................................................................... 56 The Internal Table TIP .............................................................................................. 57 The Internal Table TOP ........................................................................................... 510 The Internal Table TZP ........................................................................................... 510 The Internal Table TES ........................................................................................... 512 The Internal Table ZML ........................................................................................... 514 The Internal Table DZL ........................................................................................... 515 Clusters ................................................................................................................... 515 Cluster B1................................................................................................................ 516 Cluster B2................................................................................................................ 517 Tables in Cluster B2 ............................................................................................... 518 Reports in Time Evaluation .................................................................................... 521 Result Lists in Time Evaluation ............................................................................. 521 Exploding Schemas and Personnel Calculation Rules ........................................ 522 Attendance and Absence Lists .............................................................................. 523 Work Schedule Reports.......................................................................................... 523 Time Data Lists ....................................................................................................... 524 Error Lists in Time Evaluation ............................................................................... 524 Interface Reports..................................................................................................... 525

May 1997

51

Appendix Personnel Calculation Rules in Time Evaluation: Overview

SAP AG

Personnel Calculation Rules in Time Evaluation: Overview

The overview lists all personnel calculation rules contained in the standard schema TM00. <Standard personnel calculation rules in schema TM00> Processing step in time evaluation Before day processing Day processing Retrieve data Name MODT TD10 TD20 TD30 TD40 TD60 TD80 TD90 Error checks TE10 TE20 TE30 Planned-actual comparison TL10 TF10 Determine planned pairs TP10 TP20 TB10 Short text Initialization: Set groupings Check if daily work schedule is still active Process pair formation errors Dynamic daily work schedule assignment Process the Overtime infotype (2005) Convert daily work schedule, in event of RWH (reduced working hours) or leave Process attendance/absence reasons (clock-in entry) Process locked records Adjust absences Day-specific error checks Pair-specific error checks Round first/last pair Starting point for dynamic breaks Adjust absences if flextime balance is greater than 0 Process absences with time compensation Shorten automatically delimited off-site work records Generate overtime approval, P0050 (overtime generation according to

Determine overtime

TO10

52

May 1997

SAP AG

Appendix Views and Tables in Time Evaluation: Overview

infotype 0050, Time Recording Information) TO15 TO16 TO20 Compensate overtime Form balances TC20 TR10 TR30 TR40 TR50 TR60 Final processing TS10 TS20 TS30 Evaluate overtime approval according to the daily work schedule (T550A) Calculate overtime for time pairs outside of planned working time Form overtime pairs Overtime compensation Form daily totals Calculate flextime balance for current day Check minimum daily working time Check maximum daily working time Check for core time violation Update leave balance Convert excess flextime to overtime (if employee is authorized to work overtime) Check for flextime excess/deficit

Views and Tables in Time Evaluation: Overview

This section introduces the main views and tables which are used to set up the time evaluation component. It should enable you to obtain an overview of the contents of the respective table, or the settings made when the system was customized (view maintenance).
Caution

It is advisable to maintain views via the steps described in the Implementation Guide. It contains all the information you require to maintain views. Please note that table maintenance is not connected to a transport system ! If you change table contents, you can only transport them to other clients via Enhanced table maintenance (view maintenance). Time types The time type tables define the characteristics of specific time balances which are processed during time evaluation.

May 1997

53

Appendix Views and Tables in Time Evaluation: Overview

SAP AG

Name Time types Time type generation Time balance revisions

View V_T555A V_T555Z

Table T555A T555Z

The characteristics of time balance revisions are defined in the time balance revision tables. Name View Table Time balance revisions Time balance revision: Transfer to time types Time balance revision: Transfer to wage types Time balance revision: Transfer to absence quotas
Error tables

V_T555P V_T555J V_T555K V_T555L

T555P T555J T555K T555L

Specific errors are defined in the error table and assigned a name. The errors are printed in time evaluation. Name Time evaluation errors Work time event type The internal indicators for clock-in and clock-out indicators etc. are defined and assigned a name in the tables for work time event types. Name Internal work time event types Function codes Work time event type groups Work time event type texts Function code texts Time wage type selection Rules for selecting time wage types are defined in the table for time wage type selection. View Table T705C T705D T705O T705U T705V View V_T555E Table T555E

54

May 1997

SAP AG

Appendix Views and Tables in Time Evaluation: Overview

Name Time wage type selection rule Wage type valuation

View V_T510S

Table T510S

The table for wage type valuation defines rules for the processing and evaluation of wage types in payroll accounting. Name Wage type valuation Valuation bases Selected processing classes, cumulations and evaluation classes Wage type texts Form tables You can use the form tables to customize the printout of the time statement list. Name View Table T512E T512G T512P T512Q V_512W_B V_512W_D; logical view name: 01_T510S - overtime compensation V_512W_T View Table T512W

Form-related control of wage V_T512E types Supplementary group texts Form background Fixed layout data Tables for general control V_T512G V_T512P V_T512Q

The following are general control tables in time evaluation. Name Employee grouping for time evaluation rule Overtime compensation type Time management status Attendance/absence reasons Subsystem Leave types V_T555D V_T5533 View Table T555N T555R T555U T555D T533

May 1997

55

Appendix Internal Tables in Time Evaluation

SAP AG

Internal Tables in Time Evaluation

The following section introduces the internal tables in time evaluation, which can be referenced in personnel calculation rules. The internal tables are referred to as the work tables of time evaluation. The tables are filled and changed in the course of the time evaluation run. If time evaluation requires specific data for a processing step, it queries the data from the internal tables and processing continues accordingly. At the end of a processing step, the modified data is entered back in the internal tables by the time evaluation driver. It can be accessed there for subsequent processing steps. The internal tables are temporary in nature and are deleted once the time evaluation run is complete for an employee. Any data which is still required - time balances and time wage types, for example - is exported to the tables in cluster B2, file PCL2, at the end of time evaluation.
Note

The time evaluation log allows you to check if and how the internal tables have been filled and changed at any stage in the program. Insert the following functions at the appropriate position in your schema: PRINT TIP PRINT TES PRINT DZL etc.

and choose the program option Logging on on the report selection screen. The following sections explain what the internal tables are used for, and what type of information they contain. Please see: The Internal Table TIP The Internal Table TOP The Internal Table TZP The Internal Table TES The Internal Table ZML The Internal Table DZL

56

May 1997

SAP AG

Appendix The Internal Table TIP

The Internal Table TIP

The internal table TIP (daily input) is the work table for time evaluation. The time pairs determined on the basis of the time events are inserted in TIP. In the course of time evaluation, the time pairs in TIP are processed, changed and made available for further processing. TIP provides the input of the previous results for the respective processing step. The time pairs are then transferred individually to a personnel calculation rule for processing. After processing, the new results are inserted in the internal table TOP (daily output). There are no more time pairs in TIP at this stage. TOP is renamed as TIP for the next function, in order that further processing is performed from a different perspective.
Table TIP

Column Begin / End

Meaning Decimalized begin and end times

Status 1: Status from pair formation 0 or BLANK = Pair is complete 2 = No clock-in (i.e. first time event of the day is missing) 3 = No clock-out (i.e. last time event of the day is missing) 4 = No end time for break. Employee is absent for a brief period. The System expects a second time event 7 = No start time for off-site work 8 = No end time for off-site work E = Order confirmation missing A = Delimited in time evaluation

Pair type 0 = Non-recorded time 1 = At work (Time Events infotype, 2011, clock-in/clockout entry, planned pair according to daily work schedule) 2 = Recorded absence (Absences infotype, 2001) 3 = Off-site work or recorded attendance (infotype 2002)

ID

Time identifier: in relation to daily work schedule 01 = Overtime (unapproved): time outside of daily work

May 1997

57

Appendix The Internal Table TIP

SAP AG

schedule 02 = Fill time 03 = Core time 04 = Core time break 05 = Fill time break 06 = Paid break 07 = Unpaid overtime break 08 = Paid overtime break 09 = Overtime break

CT

Processing type/time type class

Note

The processing type/time type class is stored in the view Processing type and time type according to attendance/absence class (T555Y).

Processing type - = Pair is deleted at a later stage BLANK = Pair not counted as productive time S = Planned working time pair M = Overtime A = Absence pair included in the calculation of planned working time P = Attendance pair included in the calculation of planned working time K = Core night work Time type
Note

TTyp

The time types are stored in view V_T555A, Time Types.

BR

Begin time event type Time event type of first entry

ER

End time event type

58

May 1997

SAP AG

Appendix The Internal Table TIP

Time event type of last entry

Overtime compensation type BLANK = Remuneration 1 = Remuneration (basic pay plus overtime bonus) 2 = Time off plus overtime bonus 3 = Compensation (time off)

Origin indicator of time pair E = Time event O = Overtime from infotype 2005, Overtime A = Absence from infotype 2001, Absences P = Attendance from infotype 2002, Attendances R = Availability from infotype 2004, Availability D = Generated planned pair C = Attendance/absence reasons

Internal key for availability duty

Note

The internal key for availability duty is stored in view V_T557, Availability Types.

BPIN

Begin attendance/absence type

EPIN

End attendance/absence type

PT

Pointer to attendance pairs from pair formation

Note

In order that table TIP is not supplied with too much information, further data which is relevant to the time pairs is stored in other tables. This division of the data is referred to as a split. Only the pointer to the respective data is listed in TIP. The number listed under the table split refers to the relevant record in the table. The numbers in these

May 1997

59

Appendix The Internal Table TOP

SAP AG

tables are assigned consecutively.

AL

Pointer to alternative payment

C1

Pointer to cost distribution

AB

Pointer to absence pairs

Number

Number of hours of a time pair

Please see, The Internal Table TOP

The Internal Table TOP

The internal table TOP (daily output) is a utility table in time evaluation, and is closely related to the internal table TIP. TIP provides the input of the previous results for the respective processing step. The time pairs are then transferred individually to a personnel calculation rule for processing. After processing, the new results are inserted in the internal table TOP. There are no more time pairs in TIP at this stage. TOP is renamed as TIP for the next function, in order that further processing is performed from a different perspective Please see: The Internal Table TZP

The Internal Table TZP

The internal table TZP is only used in time evaluation. The planned specifications from the employees personal work schedule are stored in TZP.
Note

Any substitutions, which overwrite the employees personal work schedule, are also taken into account.

510

May 1997

SAP AG

Appendix The Internal Table TZP

The system requires two pieces of information in order to calculate employees time balances: the planned specifications stipulate how the employee has to work (according to his/her work schedule). the actual specifications indicate when the employee actually worked. At the start of time evaluation, the planned specifications - in the form of the daily work schedule - are made accessible in table TZP. The system analyzes each point of time in the daily work schedule, and assigns it a time identifier. The time identifier denotes either overtime (time outside of the daily work schedule), fill time, core time or breaks. You can insert a PRINT TZP in the schema, after function P2011 or P2000, if you want to display the most important contents of table TZP. If you run report RPTIME00 with the test utilities ON, you can check the values calculated in the log. <The internal table TZP> Column/fields CLOCK TIME Meaning Time point: The daily work schedule specifies begin times for breaks, core time etc. as decimalized values. Times outside of the daily work schedule are also taken into account. CODE A time identifier is assigned to each time point to describe its place in the daily work schedule. The breaks are taken from the work break schedule which is assigned to the daily work schedule.
Example

Tim e poin t 000 000 080 000 090 000 095 000 100 000

Time identifier 01 Time outside of daily work schedule 02 Fill time 03 Core time 04 Core time break 03 Core time

May 1997

511

Appendix The Internal Table TES

SAP AG

BLOCK PDBEZ

This field is currently of no significance. Duration of paid break The duration of the paid break period is specified. The time wage types formed from this information are evaluated in payroll accounting.

PDUNB

Duration of unpaid break The duration of the unpaid break period is specified.

Further values which are accessible in TZP: PTYP1 Break type 1 is stored in the work break schedule (T550P). The break type 1 field indicates whether the break is during planned working time or overtime. The break type 1 field can be processed separately using function PBRKS. PTYP2 Break type 2 is stored in the work break schedule (T550P) and is user-definable. The break type 2 can be processed separately using function PBRKS. Special break processing can be performed for certain employees or employee groupings. Please see: The Internal Table TES

The Internal Table TES

All time types which are formed or processed in rule processing are stored in the internal table TES (daily balances) during time evaluation. All calculated balances are stored in TES. In order to form daily balances, the time types which have been assigned to the time pairs in table TIP are cumulated and converted to other time types. These time types are stored in table TES (daily balances).
Example

Balance formation Table TIP Table TES

512

May 1997

SAP AG

Appendix The Internal Table TES

Time type 0110

Fill

is stored in table TES as follows:

0100 = Fill time 0010 = Attendance 0003 = Skeleton time

time

Attendance The balances can be updated in table ZES (daily balances) and in table SALDO (monthly balances).
Example

The internal table TES: daily results of daily balances In the example, the employee worked 2 hours of overtime on the selected day. Time type 0000 0001 0042 0110 0100 0010 0003 0210 0200 0500 0040 0002 0005 0050 Text Utility time type 1 Utility time type 2 Overtime to compensate Fill time attendance Fill time Attendance Skeleton time Core time attendance Core time Break Overtime worked Planned time Flextime balance Productive hours Number 8.0000 10.0000 2.0000 3.7500 3.7500 8.0000 8.0000 4.2500 4.2500 1.0000 2.0000 8.0000 0.0000 10.0000

Please see: The Internal Table ZML

May 1997

513

Appendix The Internal Table ZML

SAP AG

The Internal Table ZML

The internal table ZML serves as an interim table in time evaluation. All overtime wage types are stored in ZML during time evaluation. Table ZML is processed when overtime is compensated (function POVT). The overtime compensation type indicates whether overtime should be remunerated or compensated by time off. The overtime compensation type can be entered for an overtime record in the Attendance Quotas (2007) and Overtime (2005) infotypes, or is stored for the wage type in processing class 17. If the overtime is to be remunerated, a wage type is generated and inserted in table DZL. If the employee is granted time off for overtime, the system forms an absence quota. The internal table ZML Column/Field BTime ETime Wage type Comp Meaning Start of overtime End of overtime Wage type Overtime compensation type: BLANK 1 2 3 I IFTYP Wage types are flagged using the IFTYP. The standard identifiers are: S - planned work M - overtime A - absence AL C1 AB Number Pointer to an alternative payment Pointer to a cost distribution Pointer to absence pairs Number of hours Remuneration Remuneration Time off plus overtime bonus Compensation (time off)

Please see:

514

May 1997

SAP AG

Appendix The Internal Table DZL

The Internal Table DZL

The Internal Table DZL

All wage types which are generated during time evaluation are stored in the internal table DZL for each employee and day. The wage types are updated to table ZL using function CUMBT. The internal table DZL Column/field Date BTime ETime Wage type Meaning Date for which wage type has been generated Begin time End time Wage type

IFTYP

Wage types are flagged with an IFTYP. The IFTYP indicates the type of work.
IFTYP S M A

Meaning Planned work Overtime Absence

AL C1 AB Number

Pointer to alternative payment Pointer to cost distribution Pointer to absence pairs Number of hours

Clusters
A data cluster is a grouping of several data objects. Elementary fields, field strings and internal tables can be grouped in a data cluster. Clusters B1 and B2 in files PCL1 and PCL2 are relevant to time evaluation, as is cluster PS which stores the generated schema.

May 1997

515

Appendix Cluster B1

SAP AG

Please see, Cluster B1 Cluster B2

Cluster B1
All cluster for entry data are contained in file PCL1. This also includes cluster B1 which stores several tables containing information on the employees time events and on status data for time evaluation.
Example

unprocessed time events error table ERT selected monthly balances table QT which contains various status fields for time evaluation

File PCL1 contains only temporary clusters. Cluster B1 tables are only filled if the data contained in them has not yet been processed by the time evaluation driver. If the results of time evaluation are not clear, you can use cluster reports to display the data determined. Report RPCLSTB1 allows you to view the data in cluster B1, arranged into tables. You can also view cluster B1 via the Time Management pool. You can display the content of cluster B1 tables for individual employees in the error processing transaction via Goto Evaluation result.
Internal tables in cluster B1

Balances, wage types and quota transactions Table NT1 Table NT1 contains pointers to all unprocessed time events and is used in pair formation and to recognize the necessity for a recalculation. The time events themselves are stored in table TEVEN.

NT2

Table NT2 contains pointers to time events which lead to a processing error.

ERT

Table ERT contains the messages from the last evaluation run.
Note

516

May 1997

SAP AG

Appendix Cluster B2

The following section contains information on the various types of message: Error Processing .

NCT

Table NCT contains date specifications for days for which the entire pair formation process must be carried out again.

IFT1

Table IFT1 is only used internally by SAP.

IFT2

Table IFT2 is the interface table to incentive wages. It describes the changes in table WST (time tickets, other documents), cluster B2, to the time tickets which have already been updated in incentive wages. Further information can be found in the documentation on Integration with Logistics - Plant data collection under the section Updating Time Tickets in Incentive Wages .

ST

Table ST contains selected balances which are transferred to the time recording systems for employees information the next time a download is performed.

QT

Table QT contains various items of information which must be updated daily, for example: date of last day for which pair formation and generation was carried out start and end of planned working time, public holiday class, day type and days daily work schedule class

Please see, Cluster B2

Cluster B2
File PCL2 contains the clusters for time evaluation result data. This includes cluster B2 which stores the result tables of time evaluation. These tables contain information on: basic data and work schedule balances, wage types and quotas time pairs and time tickets time data

May 1997

517

Appendix Tables in Cluster B2

SAP AG

evaluation status

The data in cluster B2 is stored for individual personnel numbers and periods.
Note

The period used for time evaluation can be determined when your system is customized. Please see the section Define accounting periods in the Implementation Guide. The clusters in file PCL2 are permanent. Data remains in cluster B2 until the cluster is reorganized. This allows you to view all data ever recorded and processed for an employee and to repeat time evaluation runs for test purposes. Evaluations are based on the data in cluster B2. If the results of time evaluation are not clear, you can use cluster reports to display the data determined. Report RPCLSTB2 allows you to view the data in cluster B2, arranged into tables. You can also view cluster B2 via the Time Management pool. You can display the content of cluster B2 tables for individual employees in the error processing transaction via Goto Evaluation result. Please see, Tables in Cluster B2

Tables in Cluster B2
Basic data and work schedule Table WPBP Table WPBP contains data on the employees work center and basic pay.

PSP

Table PSP contains data on the employees personal work schedule for each day.

Balances, wage types and quota transactions Table ZES Table ZES contains daily balances.

SALDO

Table SALDO stores all cumulated balances. The balances are added from table TES to SALDO in month-end processing.

518

May 1997

SAP AG

Appendix Tables in Cluster B2

ZKO

All quota transactions of the period are stored in table ZKO.

URLAN

Table URLAN contains information on the updating of the Leave Entitlement infotype (0005).

ZL

Table ZL represents the interface between time evaluation and payroll accounting. The existing time wage types have been derived via time wage type selection using the Time Wage Type Selection Rule table (T510S). The entries in table ZL contains pointers to the following tables: ALP - alternative payment C1 - cost distribution AB - absences An IFTYP is specified for the selected time wage types. The IFTYP is an indicator for payroll accounting and describes the origin of the wage type: S - planned work M - overtime A - absence

ALP C1

Table ALP contains the specifications on a different rate of payment Table C1 contains cost distribution specifications (account assignment).

VS

Table VS contains variable balances which can be defined by the user. These balances can be entered in the table during time evaluation using operation ADDVS, where they are available for customer-specific evaluations.

CVS

Table CVS contains the cumulated balances from table VS. Table CVS is filled automatically.

FEHLER

All messages generated during time evaluation are stored in table FEHLER.
Note

The following section contains information on the various types of message: Error Processing .

May 1997

519

Appendix Tables in Cluster B2

SAP AG

KNTAG

The string KNTAG shows whether or not the employee performs core night work (Germany, EstG 3b)

Time pairs and time tickets Table PT Table PT contains the time pairs generated in pair formation. This table is only required if you use time recording systems.

WST

Table WST contains the generated time tickets

CWST

Table CWST contains the cumulated time tickets

AT

Table AT is an assignment table which links time pairs and time tickets.

Time data Table AB Table AB contains all absences

ANWES

Table ANWES contains all attendances which have been entered using the Attendances infotype (2002).

VERT

Table VERT contains all substitutions entered in the Substitutions infotype (2003)

RUFB MEHR

Table RUFB contains all availability records entered in the Availability infotype (2004) Table MEHR contains all overtime data entered in the Overtime infotype (2005)

ABWKONTTable ABWKONTI contains all absence quotas from the Absence Quotas I infotype (2006)

ANWKONTTable ANKONTI contains all attendance approvals from the Attendance

520

May 1997

SAP AG

Appendix Reports in Time Evaluation

Quotas infotype (2007).

SKO

Table SKO contains all time balance revisions recorded in the Time Balance Revisions infotype (2012)

Status information Table BEZUG This table shows the recalculation dates for time evaluation, the time statement and a third-party payroll accounting system.

Please see, Reports in Time Evaluation

Reports in Time Evaluation

The following presents an overview of the most important reports and evaluations in time evaluation. Please see, Result Lists in Time Evaluation Exploding Schemas and Personnel Calculation Rules Attendance and Absence Lists Work Schedule Reports Time Data Lists Error Lists in Time Evaluation Interface Reports

Result Lists in Time Evaluation

You can display specific results using time evaluations overview lists.
Note

The majority of the following reports can be called within the Time Management pool.

May 1997

521

Appendix Exploding Schemas and Personnel Calculation Rules

SAP AG

RPCLSTB1 = Display Cluster B1, Database PCL1

You can use this report to display all data in cluster B1 tables. Cluster B1 contains all entry data.
RPCLSTB2 = Display Cluster B2, Database PCL2

You can use this report to display all data in cluster B2 tables. Cluster B2 contains all result data of time evaluation. After the report has been executed, the system displays the cluster B2 tables. You can call a table by double clicking on the relevant table name.
RPTEDT00 = Time Statement Forms

There are two main options for creating a time statement list for the employee: Parallel with time accounting (RPTIME00). In a separate form run (RPTEDT00). The form structure of both reports can be controlled using tables. Report RPTEDT00 is subdivided into several sections:

Print headers (personal data) Print the results of a day Print a period overview Print the generated time wage types for a period

Please see, Exploding Schemas and Personnel Calculation Rules

Exploding Schemas and Personnel Calculation Rules

RPDASC00 = Explode Schemas and Personnel Calculation Rules

You can use this report to explode and print all processing steps in schemas and personnel calculation rules. The options are as follows: 1. You can display several schemas with their functions, parameters and texts. 2. You can also display selected personnel calculation rules, or all personnel calculation rules which belong to a schema. 3. You can also display subordinate personnel calculation rules.
RPUCTC00 = List Personnel Calculation Rules

You can use this report to display one or more personnel calculation rules with all existing versions. On the report selection screen, you can specify the number of personnel calculation rules you want to display, and which employee subgroup groupings for the personnel calculation rule should be exploded.

522

May 1997

SAP AG

Appendix Attendance and Absence Lists

Please see, Attendance and Absence Lists

Attendance and Absence Lists

The attendance and absence reports provide an overview of periods of absence and offsite work.
RPTABS00 = Attendances and Absences per Employee

By entering the appropriate parameters on the selection screen, you can use this report to list your employees attendances and absences. The first part of the list contains an exploded and cumulated display of each employees attendance and absence days/hours. The planned days and planned hours are compared. For absences caused by incapacity to work , continued pay is indicated as follows: + (=paid) and - (=unpaid).
RPTABS10 = Attendances and Absences per Organizational Unit

This report lists your employees attendances and absences per organizational unit (e.g. company code, personnel area, etc.). For each selected parameter, the system displays a detailed list of attendances and absences, stating the number of day or hours. This is followed by a cumulated overview in which the attendance and absence times are compared to the planned times. For absences due to incapacity to work, continued pay is indicated by + (=paid) and (=unpaid). You can control the sort sequence by setting parameters on the selection screen.
RPTEAB00 = PDC Time Management - Attendance Check

Report RPTEAB00 enables you to display a list of employees who are at work on a specific day, at a specific time. Please see, Work Schedule Reports

Work Schedule Reports

RPTPSH10 = Display Work Schedule Data, Planned Working Time Infotype and Time Infotypes

This report generates an overview of the main working time data and time infotype records for the selected employees.
RPTDSH20 = Display Work Schedule

You can use this report to display an overview of daily work schedules, or choose daily work schedules according to content. The system lists all daily work schedules which fit

May 1997

523

Appendix Time Data Lists

SAP AG

the selection criteria. The Choose function allows you to view a daily work schedule in detail.
RPTSHF00 = Generate Monthly Work Schedules

You can use report RPTSHF00 to generate several monthly work schedules simultaneously. This prevents you from having to generate each monthly work schedule individually in dialog. The program automates data entry, and generates the selected monthly work schedules in a program run. Please see, Time Data Lists

Time Data Lists

RPTCMP00 = Time Leveling

You can use the time leveling report to compare your employees working times to the times documented by time or incentive wage data. Any necessary changes or additions can be made on the dataset.
RPTDOW00 = Time Accounts

This report can be used to check an employees current balances. Please see, Error Lists in Time Evaluation

Error Lists in Time Evaluation

RPTERR00 = PDC Error Processing

Report RPTERR00 can be used to display a list of employees for whom there were errors in time evaluation, and perform various processing steps directly from the overview list. You can also call the report by choosing the menu path Time management Time evaluation Time management pool (transaction PT40). Please see: Error Processing . Please see, Interface Reports

524

May 1997

SAP AG

Appendix Interface Reports

Interface Reports
1. Upload reports RPTEUP00 = Upload Time Events from Sequential File

Report RPTEUP00 reads the employees time events from a sequential file and posts them to the HR system.
2. Download reports RPTEDO00 = Download to Sequential File

Report RPTEDO00 reads selected master data and balances from time evaluation, and inserts them in a sequential file.
3. Other Supply Third-Party Payroll Accounting System

You can use report RPTEZL00 to supply a third-party payroll accounting system with wage types determined in time evaluation.
Time type

A time type is an allocation of times according to payment aspects, company-specific factors, etc. Time types assign a meaning to time intervals. The balances formed in time evaluation are updated in the time types. When the system is customized, the following specifications are made for each time type: 1. Is the time type taken over to the daily and monthly totals? 2. Should the time type be taken over from the previous month/year? 3. Should the time type be taken over to cluster B1 for entry data? 4. Should the time type be included in the balance display ?
Example

The meaning of time types is taken from time evaluations personnel calculation rules. The standard time types have the following meanings: 1. Time types for balance formation using time data with clock times 2. Time types for balance formation when only a number of hours is recorded
1. Time types for balance formation using time data with clock times

0003 - Skeleton time, as total of:

May 1997

525

Appendix Interface Reports

SAP AG

0110 - Attendance during fill time 0220 - Attendance during core time 0120 - Recorded absence during fill time 0220 - Recorded absence during core time 0130 - Off-site work during fill time 0230 - Off-site work during core time 0411 - Overtime hours in excess of quota 0540 - Paid break times

0005 - Flextime balance, derived from: 0003 - Skeleton time reduced by 0002 - Planned working time 0010 - Attendance, as total of: 0110 - Attendance during fill time 0210 - Attendance during core time 0020 - Recorded absence, as total of: 0120 - Recorded absence during fill time 0220 - Recorded absence during core time 0030 - Off-site work (recorded attendance from infotype 2002) as total of: 0130 - Off-site work during fill time 0230 - Off-site work during core time 0040 - Overtime worked, as total of: 0041 - Overtime to compensate with time off 0042 - Overtime to remunerate 0043 - Overtime to compensate with time off plus overtime bonus 0050 - Productive hours, as total of: 0010 - Attendance 0030 - Off-site work (recorded attendances from infotype 2002) 0040 - Overtime worked
Time types for balance formation when only a number of hours is recorded

2.

0002 - Planned working time according to daily work schedule 0003 - Skeleton time (times which count towards the planned time) as total of: 0010 - Attendances (pair type 1) 0020 - Recorded absences from infotype 2001 0030 - Recorded attendances from infotype 2002 0411 - Overtime hours in excess of quota 0540 - Paid break times 0005 - Flextime balance, derived from: 0003 - Skeleton time, reduced by 0002 - Planned working time

526

May 1997

SAP AG

Appendix Interface Reports

0010 - Attendances, as total of time types 11xx processing type/time type class xx 0020 - Recorded absences from infotype 2001, as total of: 12xx - Absences with processing class/time type class xx

- attendance with

0030 - Recorded attendances from infotype 2002, as total of: 13xx - Recorded attendances with processing type/time type class xx 0040 - Overtime worked, as total of: 0041 Overtime to compensate (with time off) 0042 Overtime to remunerate 0043 Overtime to compensate with time off plus overtime bonus 0050 - Productive hours, as total of: 0010 - Attendances (pair type 1) 0030 - Recorded attendances from infotype 2002 0040 - Overtime worked

Pair type

The pair type of a time pair denotes whether the employee is at work or absent. Type 0 1 2 3 Meaning Non-recorded times At work (Time Events infotype (2011), clock-in/clock-out entry, planned pair according to daily work schedule) Recorded absence (Absences infotype, 2001) Off-site work or recorded attendance (infotype 2002)
Processing type

The processing type is formed during time evaluation, and is of particular significance to time wage type selection. The wage types formed from a time pair are processed in payroll accounting according to the processing type. The processing type is important for determining planned pairs. The system also refers to an employees attendances and absences to determine planned working time. Planned working time pairs (S) and overtime pairs (M) are formed in a further processing step. Processing type BLANK P A Meaning Pair is deleted at a later stage Pair not counted as productive time Attendance pair included in the calculation of planned working time Absence pair included in the calculation of planned working time

May 1997

527

Appendix Interface Reports

SAP AG

S M K X G

Planned working time pair Overtime Relevant acc.to paragraph 3bESTG core night work (Germany) Attendance on public holiday (parallel to planned pair in daily work schedule) Guaranteed hours
Selection rule group for time wage types

The selection rule group for time wage types is a grouping of time wage type selection rules which are used to determine payment for a particular type of working period, for a particular group of employees.
Note

The selection rule group for time wage types is set in view V_T510S, Time Wage Type Selection Rule. The time wage type selection rule defines conditions for choosing a time wage type. These conditions are queried if wage types are to be generated from the employees time data. These conditions refer to the processing type, public holiday class, daily work schedule group and/or day type, time interval, etc.
Personnel calculation schemas (time evaluation)

The sub-steps in time evaluation are processed in a specific order. This sequence of substeps is determined when your system is customized and is referred to as a schema. There are several schemas in the standard system which all cater for different time evaluation requirements. The standard SAP system provides the following schemas for time evaluation: Schema TM00: Time evaluation with time events Schema TM01: Time evaluation for exceptions to the work schedule Schema TM02: Time evaluation for external services Schema TM04: Time evaluation without clock times
Note

To maintain schemas, choose the menu path Time management Tools Maintain schema . General information on schema maintenance is provided in the PA online handbook Personnel Administration and Payroll Accounting Tools.

528

May 1997

SAP AG

Appendix Interface Reports

Variable key

The variable key allows you to set up a decision tree which can be used to check the processing of wage types, for example. The variable key is used to define as many decision rules as required (decision rules are flagged as rule type D).
Rule type

The rule type determines the type of processing which is carried out. If no rule type is specified, the operations are processed sequentially. The following rule types exist: Rule type D Rule type D indicates a decision operation. The result of the decision operation is entered in the variable key. Rule type S Rule type S indicates a decision operation. The result of the decision operation is not entered in the variable key, but saved in table ES. Rule type P Rule type P indicates an operation which executes a further personnel calculation rule. Once this personnel calculation rule has been processed, the system goes back to the next operation. Rule type Z Rule type Z indicates an operation which executes an additional personnel calculation rule. After this additional personnel calculation rule has been processed, the system does not go back to the next operation.
Planned pair

Planned pairs are generated according to the specifications in the daily work schedule. In this was, you can run time evaluation for employees for whom only exceptions to the work schedule are recorded. An employees working time is determined exclusively on the basis of the planned pair in this case, if there are no infotype records which show exceptions. Planned pairs are generated in schemas TM01 and TM04 using function P2000. The daily work schedule is imported into the internal table TZP; clock times are decimalized. Time pairs are then formed according to the start and end of planned working time or start and end of normal working time in the daily work schedule, and entered in table TIP.
Example

Table TIP after function P2000

Table TIP

May 1997

529

Appendix Interface Reports

SAP AG

Begin 08.0000

End 16.5000

P 1

ID

CT 00

TTy

BR

ER

O D

BPIN EPIN PT AL C1

AB

No. 8.5000

530

May 1997