You are on page 1of 5

1. All time management data is stored in the form of time pairs and time types. 2.

Each day for each employee , the attendance or absence time is analyzed in relation to the preset values of the relavant shift schedule. The first result is a series of time pairs that signal when something began and when it finished-work, absence, and so on. Each time pair is then classified. By referring to the rules for overtime and so on, the system can refine the classification until each unit of time is identified by its type, which is used to choose the wge type and eventually compute the compensation. 3. Two common methods of time recording. Negative time recording and Positive time recording. 4. Manual entry of hours attended or clock times can be used to update records in attendances infotype 2002. Infotypes can also be used to record absences. 5. Time infotypes often allow the entry of a list of many records for one employee. The fast entry facility allows you to enter a range of infotypes for several different employees. 6. Automatic time recording entails each employee having a time recording ID card to trigger the recording of actual clock-in and clock-out times at the front end recording terminal from which its uploaded to the R/3 system. 7. The time recording apparatus may be provided by any supplier that uses an SAP certified interface. This uses the R/3 Communication channel CC1 and operates by using the ALE (Application Link Enabling) Technology. 8. Time recording systems are installed to establish the time facts and collect the data. They cannot be used for evaluating time data, which is the province of the HR time management system. 9. The usual method is for the central system to dispatch to the time-recording system a record known as MINI-MASTER. This carries just enough data to accomplish what’s required –to collect the time data for a given individual at a specified work center in relation to the time schedule that has been assigned. 10. Time recording can be combined with admittance control. Employees may be admitted to a particular work center only. 11. The front end time recording system must be supplied with current information that the employees who use it can consult. This data comprises individual data such as leave and overtime balances. Thus , a download to time-recording terminal can be done, which includes 1.time evaluation results 2.HR master data records of employees likely to clock in or clock out 3. master data such as recognized attendance and absence reasons that an employee might enter 12. A DOWNLOAD is performed by a single transmission of what’s referred to as an HR MINIMASTER record. 13. An UPLOAD comprises all the data recorded at the terminal, such as clock-in and clock-out time and other enteries made by the employees. 14. The frequency and timing of uploads and downloads are controlled by the communication parameters. 15. The tasks of the external time recording system are 1.record time events 2.validate the time events against the HR3 mini-master for the day 3.confirm the validity of each attendance and absence reason entered against the master data for the day 4.confirm the validity of each external wage type entered against the master data

0release. These personnel numbers are stored in a table that provides an interface to HR. The R/3 system has the following duties. (using Time Evaluation driver . The actual times of individual employees can be entered by using a uniform data-entry screen for all applications 2. Approval procedures will be integrated across all applications 5. 2. Inexperienced users can operate the data-entry functions. These calculations are facilitated by a system of TIME TYPES that signify what a particular period of time should be counted as. The process of time data evaluation has the task of evaluating and comparing the planned and actual specifications of the work specifications of the work to be accomplished 3.upload time events via communication channel CC1 3. PP-Production planning. the PM-Plant maintenance. 18.3. 1. 4. The PM and PS system applications also can accept a personnel number with the entry of completion confirmation. The assignment of a time type allows the accumulation of time periods to form balances that can be assigned time wage types that are interpreted in payroll accounting. and so on. These costs are synchronously posted to CO-Controlling application. The time data needs to be collected and evaluated in one application and sent to another.Store time events in R/3 table RUECK. transfer HR mini-master records from the subsystem interface to the time-recording terminals. A work period or an absence can be defined by a pair of time events. data corrections are possible in CATS database. 2. even by those who are not familiar with R/3. templates and default field values will minimize the keystrokes needed. This diverse functionality for manipulating time data is being supplemented and integrated to make it easier to use.Read time events from the subsystem interface 2. A confirmation is posted when an activity is completed. 17. The evaluation of time data can be processed by a specialized component designed for this task. For example.4. and PS – Project system applications can collect data that records which tasks and activities are completed and the time taken by each employee assigned. The advantages of CATS technology are 1. There is timetype for Productive Hours. Cross Application Time Sheets(CATS) has been implemented as an add-0n feature since 3. The payroll accounting system itself can evaluate time data. transfer the validated time events to the subsystem interface for upload 6. 20. The data is collected by hardware or entered manually has to be formed into TIME PAIRS before it can be used in time management. where they can be used to compute the incentive wages 19.for the day 5. another for planned breaks. A timed event can be recorded by a specialized subsystem or entered manually in time events infotype 2011. 1. There are 2 Basic ways to handle time data. The system then refers to the stored activity prices of the activity types involved and calculates the actual costs of the completed activity. 16. TIME EVENTS 1.

It also determines which method is to be used according to the following. One item is the employee’s time-recording ID number. RPTIME00). 7. There should be atleast one Work schedule rule 2. a)P10-clock in b)P15. planned working time. This date is the first to be included in the next run of the time evaluation driver. P-35 Manual start of offsite work b)P45-Manual start of offsite work 3. 8. Evaluation of planned times(recording of exceptions to the work schedule) If an employee is assigned to status 2. 4) Payroll status infotype 0003 stores the recalculation date for PDC(plant Data Collection). This indicator must be set to have an employee take part in time evaluation. the . Prerequisites for Time Management:-1. The Time events infotype also accepts manual entries that correspond to the time event types normally entered by a time recording system. These time events allow an employee to begin and end work without corresponding clock-in or clock-out entry. EVALUATING TIME DATA 1. External Services 5. the time recording information infotype 0050 must be maintained with the master data needed to control the device on which actual times are to be recorded. includes a field interpreted as the status for time management. These events have to be entered manually in IT 2011.No time evaluation 2. The HR system holds additional infotypes used to interpret the information need for time management. Data is stored in the time recording information infotype for each employee. the ID is used to locate the correct time-recording card. it must store the event so that it can be matched or paired with another time and thus allow the calculation of the time interval between these events. In these instances. 1. Infotype 0050(Time recording Information). having a public holiday calendar and generated monthly work schedules suitable for each employee 3. The ID is first checked as soon as employee enters it manually to ensure that its unique. At a time-recording device. Two Time event types cant be generated at the time recording terminal. 9. The time evaluation driver offers the most versatile facilities and is discussed as Primary method.5.start of break c)P20 Clock out d)P25. For example the following time event types are determined by the time recording system and are recorded times tagged by these codes can be uploaded to the HR system via communication channel 1. Both methods depend on certain master data available in the system.Infotypes 0001.Evaluation of actual times 3.End of break e)P30-Start of offsite work f)P40End of offsite work. 6. A TIME EVENT TYPE is a useful category when seeking to form time pairs. Another data element in each employee’s 0050 infotype is a grouping code that ensures that any data downloaded to a subsystem will concern only those likely to use it. 2. The ID number is later converted to the employee’s personnel number after the time events are uploaded to the HR system and infotype can be consulted. Evaluation of actual time and PDC 4. Time Event Types: When a time recording device or manual input system accepts a time event. Infotype 0007.0002 and 0007.

2)The pairs for each day are formed 3)Time tickets are generated if you are using plant data collection (PDC) for incentive. If none is found. end of offsite work. who could make a manual entry of the event P35. 3. a pair comprising clock-in and clockout on the same day for a particular employee is assigned a status of BLANK because the pair is complete. . and thus complete the formation of a valid pair. there is an error message to the supervisor. The outcome is a stream of time pairs from which time wage types can be generated by the time evaluation process The following process of Time event can be customized. if a night shift is operating . 4. manual start of offsite work . such as P15 start of break. 5. When a time pair is formed its inserted in the pair table PT. such as P20 clockout and P45 manual end of offsite work A time pair can be completed by the time evaluation driver via processing rule TE30. Pair formation takes account of all time events uploaded to HR system from a time recording subsystem. If the time evaluation program is being run some specified time later than the unmatched entry. The status of this pair is then recorded as A to signify that the pair has been automatically delimited. For example. PAIR FORMATION The process of pair formation is largely automatic and takes place before the data is passed to the time evaluation driver. The term BLANK is used in programming the calculation rule If another clock-in has been entered without a corresponding clock-out. the system can be configured to generate an error message. A time event doesn’t need to apply to the day on which it was entered. However the time associated with the clock-out has to be incremented by 24 hours so that the length of time worked is correctly calculated. 2. such as P10 Clock-in and P35 manual start of offsite work. The time evaluation program searches for an event that marks the start of offsite work. As the HR system table TEVEN is loaded with new time events. plus any time events that have to be recorded in the time events infotype 2011 as a result of dialog at a terminal in which the employee or supervisor has entered time data. they are also copied to table NT1. the pair can be completed by automatically entering the next scheduled end of work following the clock-in.1) Time events that open a pair. For example. An empty status field is interpreted as an indicator that no special processing has been necessary.4. p25 end of break.P30 start of offsite work and P40 end of offsite work 3)Time events that close one pair but don’t open another. 2)Time events that close one pair and open another. and the time events 1. which identifies the time events that are not yet processed. an employee may record a time event P30 . 7. the time pair that ends it is normally assigned to the day on the which it began. which completes any missing entries if possible. 6. time event types are not carried as Communication Channel 1: a)01-Clockin(identical to P10) b)02-Clock out (identical to P20) c )03-Clockin or Clock-out d)04-Start of offsite work(identical to P30) There are 3 distinct groups of time events. The status of the time pair is recorded at the same time. 1)Each time event is assigned to the current or previous day. For example.

9. 6. A time pair is assigned any status other than Blank is an OPEN TIME PAIR. an error message can be generated so that a manual entry can be made to complete the data. 8. composing this pair are deleted from the list of unprocessed events(Table NT1). 3-No clock out. 2 employee is absent(this pair is not assigned to pair formation).5. Any time event that cant be processed because an error has been detected is logged in table NT2. the system updates the employees attendance status.order confirmation missing from PDC As each days time event is processed. If no rule is provided for a particular type of open pair. E. The time evaluation drivers rule-processing logic can be set up to process open pairs in whatever way your company requires. 1 employee is at work . 7. . 8 –No endtime for offsite work. For example. 4-No break end time. the normal start and end time of the working day may be used as default time events. 3 employee working offsite The status of a time pair is recorded when its formed and indicates whether further rule processing is required by the time evaluation driver. 7-No start time for offsite work . The status of a time pair is indicated as follows: BlankPair is complete:2-No clock in. The following codes are used to classify pair types according to the employees attendance or absence status: 0 unrecorded absence or break.