Go Back   Wiki NewForum > SAP HCM Forum > SAP HCM Time Management Forum

Reply
Views: 8630  
Thread Tools Rate Thread Display Modes
  #1  
Old 03-16-2009, 06:56 AM
freesaphr freesaphr is offline
Award Winner
 
Join Date:
Jan 2009
Posts: 10,503
Default Topic 37: Time Evaluation

Time management can be divided into 3 steps

1.Time Recording
2.Time Evaluation
3. Planning


Time Evaluation:

The recorded time data is grouped and converted to wage types which can be used by payroll for compensation. SAP provides a time evaluation program RPTIME00 for this purpose.

Standard schemas TM00 and TM04 are used for evaluation of time data got from positive and negative time recording approaches. Time evaluation program RPTIME00 also calculates accrual and entitlement for employees

Time Evaluation is accessing or evaluating the of an employee on a daily basis.



The time schema TM04, TM00 is read on daily basis for each and every employee. And what ever the Time Wage types formed during time evaluation are transferred to payroll thru ZL table, if there is any Time - Payroll integration is there.


Time Management status is the link between time management and payroll w.r.t how an employee's time data should be evaluated in payroll. The feature for this TMSTA.


If you want u give accruals based on time evolution this setting has to be done in infotype 0007 means that person should have this time management status.


The time management status 7 is used if there is no Payroll module and more over there is no integration with payroll. the same is maintained in the Feature "TMSTA" and in HR master of IT0007.


It is Basically used to define whether Time evaluation Exists in ur Organization and If so Whether Integration exists with Payroll/not.. The entries are maintained in T555V. All these are standard Entries and recommended not to change those...

Possible values for the Time Management status:
o 0 - No time evaluation
o 1 - Time evaluation of actual times
o 2 - PDC time evaluation
o 7 - Time evaluation without payroll integration
o 8 - External services
o 9 - Time evaluation of planned times


Time mgt status 7 is Time Mgt without payroll integration. we set this status in infotype 7. we generally use schema TQTA without payroll integration.

TQTA schema will accrue only ur absence quotas i.e ur leave quota.

This is all regarding the Time Mgt status 7, i think this will give u a idea.




Reply With Quote
  #2  
Old 03-16-2009, 07:01 AM
freesaphr freesaphr is offline
Award Winner
 
Join Date:
Jan 2009
Posts: 10,503
Default

The Time Evaluation component valuates employees’ working times. Time evaluation calculates planned times and overtime, administrates time accounts and forms wage types, updates time quotas, and is used to check working time specifications.

Implementation Considerations

You should implement the Time Evaluation component if you use time recording systems to record employees’ attendance times (actual times).

If you use other methods of time recording, the component is optional. Time data entered online can also be evaluated on a daily basis in the Integration with Time Management component in Payroll. The only functions available there are for determining wage types.

Structure link Integration with Time Management

Integration


Possible Integration with Other Time Management Components

Function Required

Component Required

Transferring data from time recording systems

Personnel time events

Possible Integration with Other Human Resources Components

Function Required

Component Required

Determining wage types for calculation of the gross wage

Payroll
Features
Choice of Several Standard Processing Methods

The standard system provides several time evaluation processes, which have different requirements on the time data to be evaluated and evaluate data using different methods:

Time evaluation for processing time data that is imported to the SAP system from time recording systems

Time evaluation for time management where only deviations to the work schedule are recorded, and not all employees’ attendance times

Time evaluation for processing time data where the duration of work performed, and not the start and end times, is required for checking working time regulations, overtime determination, and so on

Time evaluation for evaluating planned working times in future periods, for example, to receive an overview of the anticipated level of overtime

Time evaluation for automatically accruing absence entitlements
Time Evaluation Results

Time evaluation determines overtime and bonus wage types and automatically takes account of public holidays, weekdays, or conditions on the duration or time of work performed.

Time evaluation enables you to administrate time accounts, which can be individually defined. If necessary, it can check to ensure that values do not exceed or fall short of value limits.

Overtime, productive hours, absence times, and so on

Flextime balances

Annual working time accounts

It enables absence entitlements to be accrued automatically dependent on the times worked, for example.

Time evaluation issues messages when specific situations occur, for example, or if working time regulations are not adhered to. You can define your own messages for any situation. You can also order time evaluation to abort if particular errors occur.

You can display a statement of the balances determined each day for employees’ information.
Special Technical Features of Time Evaluation

You can modify time evaluation processing rules to suit the specific requirements of your enterprise.

The process flow and results of a time evaluation run are logged and can be displays in different levels of detail.

The results are saved to the database for specific days. This enables the results to be monitored for exact days, and it guarantees a recalculation without gaps.

A recalculation of periods that have already been evaluated is triggered automatically if changes are made to an employee’s time data or important master data after the first time evaluation run.

You can simulate time evaluation to estimate the amount of overtime or to calculate the expected absence entitlements, for example. The results determined in a simulation are not saved to the database.

Reply With Quote
  #3  
Old 03-16-2009, 07:03 AM
freesaphr freesaphr is offline
Award Winner
 
Join Date:
Jan 2009
Posts: 10,503
Default

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 signed 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.


Reply With Quote
  #4  
Old 03-16-2009, 07:06 AM
freesaphr freesaphr is offline
Award Winner
 
Join Date:
Jan 2009
Posts: 10,503
Default

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).
Reply With Quote
  #5  
Old 03-16-2009, 07:07 AM
freesaphr freesaphr is offline
Award Winner
 
Join Date:
Jan 2009
Posts: 10,503
Default

Running Time Evaluation
  1. Call up the transaction as follows:
    Menu Path
    From the Administration node, choose Time Evaluation Time Evaluation
    Transaction Code
    PT60
  2. Enter the following data:
    Field
    Data
    Personnel number
    1289
    Forced recalculation as of
    First day of current month
    Evaluation up to
    Current date
  3. Choose .
  4. Choose .
    The evaluation generates the error mentioned in the previous step; you will correct the error later by creating an absence through illness.
    Time Evaluation has generated a planned pair to process any possible subsequent days posted, and has stored the error in Time Management.
  5. Choose until the overview tree appears.
Choose Yes on the dialog box that appears.
Reply With Quote
Reply

New topics in SAP HCM Time Management Forum

Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Forum Jump


Powered by vBulletin® Version 3.8.10
Copyright ©2000 - 2020, vBulletin Solutions, Inc.