patim44e
TRANSCRIPT
SAP AG Appendix
Overview
May 1997 5–1
Chapter 5: Appendix
Overview
The appendix contains detailed technical information. It is revised regularly, andextended for subsequent versions.
Contents
Personnel Calculation Rules in Time Evaluation: Overview .................................. 5–2
Views and Tables in Time Evaluation: Overview .................................................... 5–3
Internal Tables in Time Evaluation .......................................................................... 5–6
The Internal Table TIP .............................................................................................. 5–7
The Internal Table TOP ........................................................................................... 5–10
The Internal Table TZP ........................................................................................... 5–10
The Internal Table TES ........................................................................................... 5–12
The Internal Table ZML ........................................................................................... 5–14
The Internal Table DZL ........................................................................................... 5–15
Clusters ................................................................................................................... 5–15
Cluster B1................................................................................................................ 5–16
Cluster B2................................................................................................................ 5–17
Tables in Cluster B2 ............................................................................................... 5–18
Reports in Time Evaluation .................................................................................... 5–21
Result Lists in Time Evaluation ............................................................................. 5–21
Exploding Schemas and Personnel Calculation Rules ........................................ 5–22
Attendance and Absence Lists .............................................................................. 5–23
Work Schedule Reports.......................................................................................... 5–23
Time Data Lists ....................................................................................................... 5–24
Error Lists in Time Evaluation ............................................................................... 5–24
Interface Reports..................................................................................................... 5–25
Appendix SAP AG
Personnel Calculation Rules in Time Evaluation: Overview
5–2 May 1997
Personnel Calculation Rules in Time Evaluation: Overview
The overview lists all personnel calculation rules contained in the standard schemaTM00.
<Standard personnel calculation rules in schema TM00>
Processing step in timeevaluation
Name Short text
Before day processing MODT Initialization: Set groupings
Day processing TD10 Check if daily work schedule is stillactive
Retrieve data TD20 Process pair formation errors
TD30 Dynamic daily work schedule assignment
TD40 Process the ‘Overtime’ infotype (2005)
TD60 Convert daily work schedule, in event ofRWH (reduced working hours) or leave
TD80 Process attendance/absence reasons(clock-in entry)
TD90 Process locked records
Error checks TE10 Adjust absences
TE20 Day-specific error checks
TE30 Pair-specific error checks
Planned-actualcomparison
TL10 Round first/last pair
TF10 Starting point for dynamic breaks
Determine planned pairs TP10 Adjust absences if flextime balance isgreater than 0
TP20 Process absences with time compensation
TB10 Shorten automatically delimited off-sitework records
Determine overtime TO10 Generate overtime approval, P0050(overtime generation according to
SAP AG Appendix
Views and Tables in Time Evaluation: Overview
May 1997 5–3
infotype 0050, Time RecordingInformation)
TO15 Evaluate overtime approval according tothe daily work schedule (T550A)
TO16 Calculate overtime for time pairs outsideof planned working time
TO20 Form overtime pairs
Compensate overtime TC20 Overtime compensation
Form balances TR10 Form daily totals
TR30 Calculate flextime balance for current day
TR40 Check minimum daily working time
TR50 Check maximum daily working time
TR60 Check for core time violation
Final processing TS10 Update leave balance
TS20 Convert excess flextime to overtime (ifemployee is authorized to work overtime)
TS30 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 timeevaluation component.
It should enable you to obtain an overview of the contents of the respective table, or thesettings 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 viaEnhanced table maintenance (view maintenance).
Time types
The time type tables define the characteristics of specific time balances which areprocessed during time evaluation.
Appendix SAP AG
Views and Tables in Time Evaluation: Overview
5–4 May 1997
Name View Table
Time types V_T555A T555A
Time type generation V_T555Z T555Z
Time balance revisions
The characteristics of time balance revisions are defined in the time balance revisiontables.
Name View Table
Time balance revisions V_T555P T555P
Time balance revision:Transfer to time types
V_T555J T555J
Time balance revision:Transfer to wage types
V_T555K T555K
Time balance revision:Transfer to absence quotas
V_T555L T555L
Error tables
Specific errors are defined in the error table and assigned a name. The errors are printedin time evaluation.
Name View Table
Time evaluation errors V_T555E T555E
Work time event type
The internal indicators for clock-in and clock-out indicators etc. are defined and assigneda name in the tables for work time event types.
Name View Table
Internal work time event types T705C
Function codes T705D
Work time event type groups T705O
Work time event type texts T705U
Function code texts T705V
Time wage type selection
Rules for selecting time wage types are defined in the table for time wage type selection.
SAP AG Appendix
Views and Tables in Time Evaluation: Overview
May 1997 5–5
Name View Table
Time wage type selection rule V_T510S T510S
Wage type valuation
The table for wage type valuation defines rules for the processing and evaluation of wagetypes in payroll accounting.
Name View Table
Wage type valuation T512W
Valuation bases V_512W_B
Selected processing classes,cumulations and evaluationclasses
V_512W_D; logical viewname: 01_T510S - overtimecompensation
Wage type texts V_512W_T
Form tables
You can use the form tables to customize the printout of the time statement list.
Name View Table
Form-related control of wagetypes
V_T512E T512E
Supplementary group texts V_T512G T512G
Form background V_T512P T512P
Fixed layout data V_T512Q T512Q
Tables for general control
The following are general control tables in time evaluation.
Name View Table
Employee grouping for timeevaluation rule
T555N
Overtime compensation type T555R
Time management status T555U
Attendance/absence reasonsSubsystem
V_T555D T555D
Leave types V_T5533 T533
Appendix SAP AG
Internal Tables in Time Evaluation
5–6 May 1997
Internal Tables in Time Evaluation
The following section introduces the internal tables in time evaluation, which can be referenced inpersonnel 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 timeevaluation requires specific data for a processing step, it queries the data from the internaltables and processing continues accordingly. At the end of a processing step, themodified data is entered back in the internal tables by the time evaluation driver. It canbe accessed there for subsequent processing steps.
The internal tables are temporary in nature and are deleted once the time evaluation run iscomplete for an employee. Any data which is still required - time balances and time wagetypes, for example - is exported to the tables in cluster B2, file PCL2, at the end of timeevaluation.
Note
The time evaluation log allows you to check if and how the internal tables have beenfilled and changed at any stage in the program. Insert the following functions at theappropriate 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 ofinformation 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
SAP AG Appendix
The Internal Table TIP
May 1997 5–7
The Internal Table TIP
The internal table TIP (daily input) is the work table for time evaluation. The time pairsdetermined on the basis of the time events are inserted in TIP. In the course of timeevaluation, the time pairs in TIP are processed, changed and made available for furtherprocessing.
TIP provides the input of the previous results for the respective processing step. The timepairs are then transferred individually to a personnel calculation rule for processing. Afterprocessing, the new results are inserted in the internal table TOP (daily output). There areno more time pairs in TIP at this stage. TOP is renamed as TIP for the next function, inorder that further processing is performed from a different perspective.
Table TIP
Column Meaning
Begin / End Decimalized begin and end times
1 Status 1: Status from pair formation
0 or BLANK = Pair is complete
2 = No clock-in (i.e. first time event of the day ismissing)
3 = No clock-out (i.e. last time event of the day ismissing)
4 = No end time for break. Employee is absent for a briefperiod. 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
P Pair type
0 = Non-recorded time
1 = At work (Time Events infotype, 2011, clock-in/clock-out entry, planned pair according to daily workschedule)
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
Appendix SAP AG
The Internal Table TIP
5–8 May 1997
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 viewProcessing type and time type according to attendance/absenceclass (T555Y).
P 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 plannedworking time
P = Attendance pair included in the calculation ofplanned working time
K = Core night work
TTyp Time type
Note
The time types are stored in view V_T555A, TimeTypes.
BR Begin time event type
Time event type of first entry
ER End time event type
SAP AG Appendix
The Internal Table TIP
May 1997 5–9
Time event type of last entry
C Overtime compensation type
BLANK = Remuneration
1 = Remuneration (basic pay plus overtime bonus)
2 = Time off plus overtime bonus
3 = Compensation (time off)
O 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
I Internal key for availability duty
Note
The internal key for availability duty is stored in viewV_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 muchinformation, further data which is relevant to the timepairs is stored in other tables. This division of the datais referred to as a split. Only the pointer to therespective data is listed in TIP.
The number listed under the table split refers to therelevant record in the table. The numbers in these
Appendix SAP AG
The Internal Table TOP
5–10 May 1997
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 closelyrelated to the internal table TIP.
TIP provides the input of the previous results for the respective processing step. The timepairs 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 nomore time pairs in TIP at this stage. TOP is renamed as TIP for the next function, inorder 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 fromthe employee’s personal work schedule are stored in TZP.
Note
Any substitutions, which overwrite the employee’s personal work schedule, are alsotaken into account.
SAP AG Appendix
The Internal Table TZP
May 1997 5–11
The system requires two pieces of information in order to calculate employees’ timebalances:
• the planned specifications stipulate how the employee has to work (according tohis/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 workschedule - are made accessible in table TZP. The system analyzes each point of time inthe daily work schedule, and assigns it a time identifier. The time identifier denotes eitherovertime (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 wantto display the most important contents of table TZP. If you run report RPTIME00 withthe test utilities ON, you can check the values calculated in the log.
<The internal table TZP>
Column/fields Meaning
CLOCKTIME
Time point:
The daily work schedule specifies begin times for breaks, coretime etc. as decimalized values.
Times outside of the daily work schedule are also taken intoaccount.
CODE A time identifier is assigned to each time point todescribe its place in the daily work schedule. The breaksare taken from the work break schedule which is assignedto the daily work schedule.
Example
Timepoint
000000
080000
090000
095000
100000
Time identifier
01 Time outside of daily work schedule
02 Fill time
03 Core time
04 Core time break
03 Core time
Appendix SAP AG
The Internal Table TES
5–12 May 1997
BLOCK This field is currently of no significance.
PDBEZ Duration of paid break
The duration of the paid break period is specified. The timewage types formed from this information are evaluated inpayroll 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 duringplanned working time or overtime.
The break type 1 field can be processed separately usingfunction PBRKS.
PTYP2 Break type 2 is stored in the work break schedule (T550P) andis user-definable.
The break type 2 can be processed separately using functionPBRKS. Special break processing can be performed for certainemployees 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 internaltable TES (daily balances) during time evaluation. All calculated balances are stored inTES.
In order to form daily balances, the time types which have been assigned to the time pairsin table TIP are cumulated and converted to other time types. These time types are storedin table TES (daily balances).
Example
Balance formation
Table TIP Table TES
SAP AG Appendix
The Internal Table TES
May 1997 5–13
Time type0110
→ Filltime
→Attendance
is stored in table TES asfollows:
0100 = Fill time
0010 = Attendance
0003 = Skeleton time
The balances can be updated in table ZES (daily balances) and in table SALDO (monthlybalances).
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 Text Number
0000 Utility time type 1 8.0000
0001 Utility time type 2 10.0000
0042 Overtime to compensate 2.0000
0110 Fill time attendance 3.7500
0100 Fill time 3.7500
0010 Attendance 8.0000
0003 Skeleton time 8.0000
0210 Core time attendance 4.2500
0200 Core time 4.2500
0500 Break 1.0000
0040 Overtime worked 2.0000
0002 Planned time 8.0000
0005 Flextime balance 0.0000
0050 Productive hours 10.0000
Please see:
The Internal Table ZML
Appendix SAP AG
The Internal Table ZML
5–14 May 1997
The Internal Table ZML
The internal table ZML serves as an interim table in time evaluation. All overtime wagetypes are stored in ZML during time evaluation. Table ZML is processed when overtimeis compensated (function POVT).
The overtime compensation type indicates whether overtime should be remunerated orcompensated by time off. The overtime compensation type can be entered for anovertime record in the Attendance Quotas (2007) and Overtime (2005) infotypes, or isstored 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 Meaning
BTime Start of overtime
ETime End of overtime
Wage type Wage type
Comp Overtime compensation type:
BLANK
1
2
3
Remuneration
Remuneration
Time off plus overtime bonus
Compensation (time off)
I IFTYP
Wage types are flagged using the IFTYP. Thestandard identifiers are:
S - planned work
M - overtime
A - absence
AL Pointer to an alternative payment
C1 Pointer to a cost distribution
AB Pointer to absence pairs
Number Number of hours
Please see:
SAP AG Appendix
The Internal Table DZL
May 1997 5–15
The Internal Table DZL
The Internal Table DZL
All wage types which are generated during time evaluation are stored in the internal tableDZL for each employee and day.
The wage types are updated to table ZL using function CUMBT.
The internal table DZL
Column/field Meaning
Date Date for which wage type has been generated
BTime Begin time
ETime End time
Wage type Wage type
IFTYP Wage types are flagged with an IFTYP. TheIFTYP indicates the type of work.
IFTYPSMA
Meaning
Planned work
Overtime
Absence
AL Pointer to alternative payment
C1 Pointer to cost distribution
AB Pointer to absence pairs
Number Number of hours
ClustersA data cluster is a grouping of several data objects. Elementary fields, field strings andinternal tables can be grouped in a data cluster.
Clusters B1 and B2 in files PCL1 and PCL2 are relevant to time evaluation, as is clusterPS which stores the generated schema.
Appendix SAP AG
Cluster B1
5–16 May 1997
Please see,
Cluster B1
Cluster B2
Cluster B1
All cluster for entry data are contained in file PCL1. This also includes cluster B1 whichstores several tables containing information on the employee’s time events and on statusdata 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 datacontained 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 thedata determined. Report RPCLSTB1 allows you to view the data in cluster B1, arrangedinto tables.
You can also view cluster B1 via the Time Management pool. You can display thecontent of cluster B1 tables for individual employees in the error processing transactionvia → 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 inpair 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
SAP AG Appendix
Cluster B2
May 1997 5–17
The following section contains information on the varioustypes of message: Error Processing .
NCT Table NCT contains date specifications for days for which the entire pairformation 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 changesin table WST (time tickets, other documents), cluster B2, to the time ticketswhich have already been updated in incentive wages.
Further information can be found in the documentation on Integration withLogistics - Plant data collection under the section Updating Time Tickets inIncentive Wages .
ST Table ST contains selected balances which are transferred to the timerecording systems for employees’ information the next time a download isperformed.
QT Table QT contains various items of information which must be updateddaily, for example:
• date of last day for which pair formation and generationwas carried out
• start and end of planned working time, public holiday class,day type and day’s daily work schedule class
Please see,
Cluster B2
Cluster B2
File PCL2 contains the clusters for time evaluation result data. This includes cluster B2which 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
Appendix SAP AG
Tables in Cluster B2
5–18 May 1997
• 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 iscustomized. Please see the section → Define accounting periods in theImplementation Guide.
The clusters in file PCL2 are permanent. Data remains in cluster B2 until the cluster isreorganized. This allows you to view all data ever recorded and processed for anemployee and to repeat time evaluation runs for test purposes. Evaluations are based onthe data in cluster B2.
If the results of time evaluation are not clear, you can use cluster reports to display thedata determined. Report RPCLSTB2 allows you to view the data in cluster B2, arrangedinto tables.
You can also view cluster B2 via the Time Management pool. You can display thecontent of cluster B2 tables for individual employees in the error processing transactionvia → 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 employee’s work center and basic pay.
PSP Table PSP contains data on the employee’s personal work schedule for eachday.
Balances, wage types and quota transactions
Table
ZES Table ZES contains daily balances.
SALDO Table SALDO stores all cumulated balances. The balances are added fromtable TES to SALDO in month-end processing.
SAP AG Appendix
Tables in Cluster B2
May 1997 5–19
ZKO All quota transactions of the period are stored in table ZKO.
URLAN Table URLAN contains information on the updating of the LeaveEntitlement infotype (0005).
ZL Table ZL represents the interface between time evaluation and payrollaccounting. The existing time wage types have been derived via time wagetype 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 anindicator for payroll accounting and describes the origin of the wage type:
S - planned work
M - overtime
A - absence
ALP Table ALP contains the specifications on a different rate of payment
C1 Table C1 contains cost distribution specifications (account assignment).
VS Table VS contains variable balances which can be defined by the user. Thesebalances can be entered in the table during time evaluation using operationADDVS, where they are available for customer-specific evaluations.
CVS Table CVS contains the cumulated balances from table VS. Table CVS isfilled automatically.
FEHLER All messages generated during time evaluation are stored in table FEHLER.
Note
The following section contains information on the varioustypes of message: Error Processing .
Appendix SAP AG
Tables in Cluster B2
5–20 May 1997
KNTAG The string KNTAG shows whether or not the employee performs core nightwork (Germany, EstG 3b)
Time pairs and time tickets
Table
PT Table PT contains the time pairs generated in pair formation. This table isonly 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 theAttendances infotype (2002).
VERT Table VERT contains all substitutions entered in the Substitutions infotype(2003)
RUFB Table RUFB contains all availability records entered in the Availabilityinfotype (2004)
MEHR Table MEHR contains all overtime data entered in the Overtime infotype(2005)
ABWKONTI
Table ABWKONTI contains all absence quotas from the Absence Quotasinfotype (2006)
ANWKONTTable ANKONTI contains all attendance approvals from the Attendance
SAP AG Appendix
Reports in Time Evaluation
May 1997 5–21
I Quotas infotype (2007).
SKO Table SKO contains all time balance revisions recorded in the Time BalanceRevisions infotype (2012)
Status information
Table
BEZUG This table shows the recalculation dates for time evaluation, the timestatement 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 timeevaluation.
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 evaluation’s overview lists.
Note
The majority of the following reports can be called within the Time Managementpool.
Appendix SAP AG
Exploding Schemas and Personnel Calculation Rules
5–22 May 1997
RPCLSTB1 = Display Cluster B1, Database PCL1
You can use this report to display all data in cluster B1 tables. Cluster B1 contains allentry data.
RPCLSTB2 = Display Cluster B2, Database PCL2
You can use this report to display all data in cluster B2 tables. Cluster B2 contains allresult data of time evaluation. After the report has been executed, the system displays thecluster 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 becontrolled 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 andpersonnel 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 calculationrules 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 allexisting versions.
On the report selection screen, you can specify the number of personnel calculation rulesyou want to display, and which employee subgroup groupings for the personnelcalculation rule should be exploded.
SAP AG Appendix
Attendance and Absence Lists
May 1997 5–23
Please see,
Attendance and Absence Lists
Attendance and Absence Lists
The attendance and absence reports provide an overview of periods of absence and off-site work.
RPTABS00 = Attendances and Absences per Employee
By entering the appropriate parameters on the selection screen, you can use this report tolist your employees’ attendances and absences. The first part of the list contains anexploded and cumulated display of each employee’s 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 andabsences, stating the number of day or hours. This is followed by a cumulated overviewin which the attendance and absence times are compared to the planned times. Forabsences due to incapacity to work, continued pay is indicated by + (=paid) and -(=unpaid). You can control the sort sequence by setting parameters on the selectionscreen.
RPTEAB00 = PDC Time Management - Attendance Check
Report RPTEAB00 enables you to display a list of employees who are at work on aspecific day, at a specific time.
Please see,
Work Schedule Reports
Work Schedule Reports
RPTPSH10 = Display Work Schedule Data, Planned Working Time Infotype and TimeInfotypes
This report generates an overview of the main working time data and time infotyperecords for the selected employees.
RPTDSH20 = Display Work Schedule
You can use this report to display an overview of daily work schedules, or choose dailywork schedules according to content. The system lists all daily work schedules which fit
Appendix SAP AG
Time Data Lists
5–24 May 1997
the selection criteria. The Choose function allows you to view a daily work schedule indetail.
RPTSHF00 = Generate Monthly Work Schedules
You can use report RPTSHF00 to generate several monthly work schedulessimultaneously.This prevents you from having to generate each monthly work schedule individually indialog. The program automates data entry, and generates the selected monthly workschedules 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 thetimes documented by time or incentive wage data. Any necessary changes or additionscan be made on the dataset.
RPTDOW00 = Time Accounts
This report can be used to check an employee’s 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 errorsin 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 → Timeevaluation → Time management pool (transaction PT40). Please see: Error Processing .
Please see,
Interface Reports
SAP AG Appendix
Interface Reports
May 1997 5–25
Interface Reports
1. Upload reports
RPTEUP00 = Upload Time Events from Sequential File
Report RPTEUP00 reads the employee’s time events from a sequential file and poststhem to the HR system.
2. Download reports
RPTEDO00 = Download to Sequential File
Report RPTEDO00 reads selected master data and balances from time evaluation, andinserts 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 withwage types determined in time evaluation.
Time type
A time type is an allocation of times according to payment aspects, company-specificfactors, etc.
Time types assign a meaning to time intervals. The balances formed in time evaluationare 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 evaluation’s personnel calculationrules. 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:
Appendix SAP AG
Interface Reports
5–26 May 1997
0110 - Attendance during fill time0220 - Attendance during core time0120 - Recorded absence during fill time0220 - Recorded absence during core time0130 - Off-site work during fill time0230 - Off-site work during core time0411 - Overtime hours in excess of quota0540 - Paid break times
• 0005 - Flextime balance, derived from:0003 - Skeleton time reduced by0002 - Planned working time
• 0010 - Attendance, as total of:0110 - Attendance during fill time0210 - Attendance during core time
• 0020 - Recorded absence, as total of:0120 - Recorded absence during fill time0220 - Recorded absence during core time
• 0030 - Off-site work (recorded attendance from infotype 2002) as total of:0130 - Off-site work during fill time0230 - Off-site work during core time
• 0040 - Overtime worked, as total of:0041 - Overtime to compensate with time off0042 - Overtime to remunerate0043 - Overtime to compensate with time off plus overtime bonus
• 0050 - Productive hours, as total of:0010 - Attendance0030 - Off-site work (recorded attendances from infotype 2002)0040 - Overtime worked
2. Time types for balance formation when only a number of hours is recorded
• 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 20010030 - Recorded attendances from infotype 20020411 - Overtime hours in excess of quota0540 - Paid break times
• 0005 - Flextime balance, derived from:0003 - Skeleton time, reduced by0002 - Planned working time
SAP AG Appendix
Interface Reports
May 1997 5–27
• 0010 - Attendances, as total of time types 11xx - attendance withprocessing type/time type class xx
• 0020 - Recorded absences from infotype 2001, as total of:12xx - Absences with processing class/time type class xx
• 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 remunerate0043 - 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 20020040 - Overtime worked
Pair type
The pair type of a time pair denotes whether the employee is at work or absent.
Type Meaning
0 Non-recorded times
1 At work (Time Events infotype (2011), clock-in/clock-out entry, planned pairaccording to daily work schedule)
2 Recorded absence (Absences infotype, 2001)
3 Off-site work or recorded attendance (infotype 2002)
Processing type
The processing type is formed during time evaluation, and is of particular significance totime wage type selection. The wage types formed from a time pair are processed inpayroll accounting according to the processing type.
The processing type is important for determining planned pairs. The system also refers toan employee’s attendances and absences to determine planned working time. Plannedworking time pairs (S) and overtime pairs (M) are formed in a further processing step.
Processing type Meaning
- Pair is deleted at a later stage
BLANK Pair not counted as productive time
P Attendance pair included in the calculation of planned working time
A Absence pair included in the calculation of planned working time
Appendix SAP AG
Interface Reports
5–28 May 1997
S Planned working time pair
M Overtime
K Relevant acc.to paragraph 3bESTG core night work (Germany)
X Attendance on public holiday (parallel to planned pair in daily workschedule)
G Guaranteed hours
Selection rule group for time wage types
The selection rule group for time wage types is a grouping of time wage type selectionrules which are used to determine payment for a particular type of working period, for aparticular group of employees.
Note
The selection rule group for time wage types is set in view V_T510S, Time WageType 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 employee’s timedata.
These conditions refer to the processing type, public holiday class, daily work schedulegroup 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 sub-steps 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 timeevaluation 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 → Maintainschema . General information on schema maintenance is provided in the PA onlinehandbook Personnel Administration and Payroll Accounting → Tools.
SAP AG Appendix
Interface Reports
May 1997 5–29
Variable key
The variable key allows you to set up a decision tree which can be used to check theprocessing of wage types, for example. The variable key is used to define as manydecision 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 isspecified, 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 isentered in the variable key.
• Rule type S
Rule type S indicates a decision operation. The result of the decision operation is notentered in the variable key, but saved in table ES.
• Rule type P
Rule type P indicates an operation which executes a further personnel calculationrule. Once this personnel calculation rule has been processed, the system goes backto the next operation.
• Rule type Z
Rule type Z indicates an operation which executes an additional personnelcalculation 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. Inthis was, you can run time evaluation for employees for whom only exceptions to thework schedule are recorded. An employee’s working time is determined exclusively onthe basis of the planned pair in this case, if there are no infotype records which showexceptions.
Planned pairs are generated in schemas TM01 and TM04 using function P2000. Thedaily 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 orstart and end of normal working time in the daily work schedule, and entered in table
TIP. Example
Table TIP after function P2000
Table TIP
Appendix SAP AG
Interface Reports
5–30 May 1997
Begin End 1 P ID CT P TTy BR ER C O I BPIN EPIN PT AL C1 AB No.
08.0000 16.5000 1 00 D 8.5000