Topic 64: Real Time Questions & Answers: Time Management

[welcomewiki]

What is the Counting rule in Time Management? After uploading of leave i am getting error Counting class of period work schedule not available on some specific date.


Counting Classes are used to define your various Counting rules for your A/A types. You need to define counting rule for each absence type. You can do it through SPRO


TM->TM data Recording & admn->Absence->Define Absence Counting Rule.
Table - T556C.


You have to define Counting Class on this node:


TM-->TM data recording-->Absences catalogue-->Absence counting
-->Define Counting classes for Period Work schedule


Counting Rule is different and not related to error which you are getting.
Counting rule defines the rule for counting the attendances / absences.
T556 takes into account: Conditions for the current day, Conditions for work schedule, Condition for planned hours, Condition for absence / attendance, Counting and Deduction rule.


Under Condition for work schedule, you can define Counting class for PWS and DWS class. You need to define a suitable counting class to period work schedule before using it here in this table.

[welcomewiki]

Plz tell me the schema we use in Time management and payroll. tell me the what is the exact use of this rules.




ANS:1 Payroll schema is K000, Time management should be a copy of TM00 or TM04, so you can adapt it to your own need. About the use of rules and schema, you should refer to the standard SAP documentation to get started, It is hard to answer such a generic question.

ANS: 2 US Payroll schema is U000, Time schema can be TM04, TM00, TQTA
PCR's are used for specific functions which needed to be carried out for running payroll and time requirements.

[welcomewiki]

We are implementing Positive Time Management. We are very new in this area and facing some issues in Positive Time Management. We configured Work schedules and Absence types and Quotas.

1. Work Schedules : All Breaks are unpaid breaks, there is no Tolerance Time and All are salaried employees.
We are going to take attendance from Time Recording Terminals. ( like Employee Clock in and Clock Out )


2. Leave Management : We configured all leave types and Quotas.
Note : The problem is we have to do the Time evaluation. When i run the RPTIME00 Report with the help of TM00 Schema. It is showing Error. There is no entry in T549Q( Payroll Periods) I maintained that table also. Later it is Showing . KNTAG K Determine indicator for core night work. It showing this error also.



You need to update the table T510s, and you have to define the processing types,
We should not use the direct Schema TM00, but we have to copy the schema to our Schema (e.g., XM00) and you need to modify the function QUOTA and DAYMO functions and try the evaluation, then you will get the expected results. If you are clear with this or if you are not getting the solution, pls let me know, so that i can help you more.


Q. Based on you inputs i run the Time Evaluation (TM00) and it is working fine (such as " Absences, Absence quotas, Clock in and Clock out entires, Substitutions are effecting). But it is not calculating Overtime.


Here we are capturing the Actual clock in/out's. My requirement is when i maintain the clock in/out in Time Events (2011) then the overtime should get calculated automatically when i run the Time Evaluation.


Now when i run Time Evaluation in Overtime it is showing as "0".


Example:
Shift St Timne : 09:00 End TIme : 17:00
Actual Clock in : 09:00 Clock Out: 19:30
------------------------------------------------------------
Overtime : 02:30
Overtime Rate : Double
I have configured One Attendance type, Counting rule and assined that couning rule to Attendance type. Later I maintained Time types( T555A), Time type determination (T555Z) and Time type processing (l T555Y) and i activated Schema TW15 and Rules TO01 and TO02.

[welcomewiki]

Could some help on the infotypes and tables which are used in negative time management?

The time infotypes which are used for Time Management are as follows:


1. 2001 -> Absence Infotype
2. 2006 -> Absence Quota type Infotype
3. 2002 -> Attendance Infotype
4. 2007 -> Attendance Quota Type Infotype



For negative time management, tou need to specift TIME MANAGEMENT STATUS as '9' in infotype '0007' i.e, Planned working time of your employee.


Could u give the general definition of the below mentionad
1. Time types
2. Taime pairs
3. Time wagetypes
4. Time balances (Day balance, Period balance


Process Flow for SAP Time Evaluation
To the world of a time data-entry person or anyone not thoroughly familiar with SAP's time processing, time management would seem like a simple process. You enter an absence or attendance, give it some hours, and payroll magically spits out a paycheck. Right? Unfortunately, it's not as simple as that. While not everyone in your company needs to know the ins and outs of time evaluation, it is beneficial to have some basic knowledge of the process flow when errors occur or your company adds additional functionality.

There are actually several phases that an attendance goes through before it reaches payroll. When an attendance is entered through IT2002, it is given at least an attendance type and number of hours, yet could contain a range of clock times, premium indicators, cost assignment, or a variety of other information. This alone is not enough information to create a time wage type however.

When time evaluation begins it's processing of an attendance it first has to load the attendance into the time type table (TIP). Function P2002 takes the data from IT2002 and creates time pairs for the day. A time pair can consist of several pieces of data.


The start and end times of the attendance. If none are specified, they are assigned based on the start of the daily work schedule rule and the number of attendance hours plus any breaks.



Pair type/attendance status. The pair type is assigned based on the function that loads the time pair into the schema. Pair type 1 is designated if the attendances have been imported through time recording terminals (P2011) or generated on the basis on the daily work schedule (P2000). Pair type 2 is used if the pair types come from absences (P2002). And pair type 3 is used if, like in our example, the pair types come from attendances (P2002).

Processing type/time type class. Each absence and attendance has a processing type/time type class assigned to it via V_554S_F that will aid in the creation of time types and processing types.



Time event types. Time event types for the beginning time and end times of the time pairs if time events are utilized (IT2011). Example: clock-in, clock-out.



Attendance/Absence reasons.
ALP splits. Alternative payment splits such as substitutions or premiums are loaded into the time pair.
Cost splits. Assignment to differing cost centers is split out in the time pairs in table TIP.
OT and absence pointers.
Number of hours for each time pair.

The next stage in time evaluation will create a time type and processing type for each time pair entry in the TIP. Function TYPES reads the time pairs and references them with customer-defined settings in T555Y and the modifier set by MODIF T to create the time types and processing types. Function TYPES along with T555Y use the following inputs to create time types for each


Personnel Subarea grouping for time recording associated with the personnel number.



Time type determination group set by function MOD, MODIF T =.
Processing type/time type class associated to the time type as assigned by the attendance type from V_554S_F.
Pair type/attendance status assigned to the time pair.

All of these inputs are referenced against T555Y and a processing type (i.e. S = planned work, M = overtime) and time type are generated and stored in table TIP.

The next phase in time evaluation involves setting the day modifier for time wage type generation. This is either done by setting MODIF D= or using the function DAYMO. DAYMO provides more flexibility as it allows you to set the modifier for four day conditions: not a public holiday - MON-SAT, not a public holiday - SUN, public holiday - MON-SAT, public holiday SUN.

Now the time types are ready to become wage types. The standard SAP method for converting time types to wage types is through the Time Wage Type Selection Table, T510S. The table is called using function GWT, generate wage types. GWT can be called for specific processing classes and the outputs can be stored in either the daily time wage types table, DZL, or the daily overtime wage types table, ZML. Table T510S can seem complicated to read but it allows for a very flexible method of time wage type generation in a variety of circumstances. There are several inputs to the table which define criteria for time wage type generation.

The time wage type selection rule group as set by MODIF W=
The day grouping as set by MODIF D= or DAYMO
These two criteria define a time wage type determination rule. The rule is made up of multiple table settings.
Up to four valid processing classes (S = planned time, etc.) are available per rule.
The days of the week, M-F, in which the rule is active.
The public holiday class of the previous day.
The public holiday class of the current day.
The public holiday class of the next day.
The daily work schedule class (working day, off days, etc.)
Specific day types for the wage type to be generated.
You can define time range during which the wage type can be generated (i.e. 19:00 - 30:00 for shift differential)

A fixed number of hours to store in the generated wage type.
When this is completed, the newly generated wage types are stored in either table DZL or ZML. The time wage type contain the following information.
Date of the attendance.
Start and end times of the attendance.
The wage type.
The information type. This is similar to the processing class associated with time types (M = overtime). · Alternative payment splits. These are created by premium indicators or shift substitutions.
Cost center splits.
Absence pointers.
Number of hours.
The time wage types will now become inputs to payroll processing when they are imported into the country-specific payroll driver (RPCALCU0 for the US, for example).

[welcomewiki]

Could someone help on activities of Year end process of Time Management?


The activities of year end on Time Management depend upon the configuration and settings have been done for your organization. When you upload the new patches for year end process, you have to retest all the Business processes for Time Management of your system.


Few other activities are as:
1. Configuration of Public holiday calendar for next year
2. Approve & Transfer all the time for current year if you have year end closer for FI module
3. Generate Work Schedule rule for next year
4. Update your quota

ANS: don't know if you would like to term it as an Year-end process..I would add the Vacation Carryover (accrual of leave balances) to the list.. at most places, the carryover is done during Jan & any accruals/payouts etc need to be attended to...