Time evaluation Class

Dear Experts
Please give me the information on Class for time evaluation  in T555y Table
Regards
Giri

Did you assign the holiday class 2 to any particular holiday??Then check on that particular holiday whether the class is 2.

Similar Messages

  • Time evaluation classes

    Hi Gurus,
    Can any one help by giving some data on time evaluation classes. what exactly it means? what r they? my mail id is [email protected]
    reward points will be given for all the helpful replies.
    Thanks in advance
    Regards
    Swarup

    hi,
    check, this.
    Time evaluation classes
    In this IMG activity you assign the time evaluation class to the attendance types, in which you calculate payment for worked Sundays, leaves and public holidays.
    Standard settings
    The SAP standard system provides you with the following calculation class values:
    10 Worked Sundays
    11 Worked Leaves
    12 Worked holidays
    Activities
    Determine the user wage types that are registered through the Attendance infotype (2001) and that apply in these cases.
    Further notes
    The time evaluation class defines the concept type to process (Sundays, leave or holidays). For that reason you already have values 10, 11 and 12 fixed, which are read from the MXPR rule, that processes the payments before mentioned.
    thanks,
    Time evaluation classes
    In this IMG activity you assign the time evaluation class to the attendance types, in which you calculate payment for worked Sundays, leaves and public holidays.
    Standard settings
    The SAP standard system provides you with the following calculation class values:
    10 Worked Sundays
    11 Worked Leaves
    12 Worked holidays
    Activities
    Determine the user wage types that are registered through the Attendance infotype (2001) and that apply in these cases.
    Further notes
    The time evaluation class defines the concept type to process (Sundays, leave or holidays). For that reason you already have values 10, 11 and 12 fixed, which are read from the MXPR rule, that processes the payments before mentioned.
    Vasu.

  • Time Constraint Class

    What is the number (0 to 7) stands for time constraint class in absence for the screen number 2001. I have a leave type CL (causual leave). What time constraint class shall i assign to it.
    Regards,
    Chinmay

    for ur info alreadt raghu has given the answer any way check this tooo
    A: Only one record may ever exist for the infotype (from 01/01/1800 - to 31/12/9999). Infotypes with time constraint A may not be deleted.
    B: Only one record may ever exist for the infotype (from 01/01/1800 - to 31/12/9999). Infotypes with time constraint B may be deleted.
    T: Time constraint varies depending on subtype.
    Z : Refers to time management infotypes.Time constraint for these ITs depend on time constraint class in table V_T554S_I. Collision checks : V_T554Y
    Apart from 1, 2, 3 there are some other types of Time Constraints: A, B, T, Z.
    The Infotypes with TC type A must exist, must have only one record in its lifetime, and these ITs cannot be deleted.
    Example: IT0003 (Payroll Status)
    The Infotypes with TC type B must have only one record in its lifetime.
    Example: IT0031 (Reference Personnel numbers)
    The Infotypes with TC type T will have subtypes, and the TC is based on the subtype.
    Example: IT0009 (Bank Details)
    The Time Mnagegement Infotypes will have TC type Z .
    Example: IT2001 (Absences)
    rule that determines whether collisions in time data are allowed, and if so, specifies how the system reacts to such collisions.
    Time contraints comprise the following:
    Time constraint classes that determine which collisions in time data records are allowed
    Time constraint table that contains the time-based collisions allowed in the time data records
    Time constraint indicator that displays whether a new data record that collides with an existing time data record can be transferred to the system or whether the transfer is prohibited
    When you update an infotype, old data is not lost but archived for historical evaluation. The system records a specific period of validity for each infotype, This enables the system to store more than one infotype record at the same time, even if their validity periods overlap. This means that the time relationships between infotype records must be defined. The concept of time constraints enables you to do this.
    HR master data uses the following three time constraints:
    Time Constraint 1
    For the entire time that the employee works at the enterprise, exactly one valid infotype record must exist. The validity periods of the individual records must not overlap. If a new record is created, the system automatically uses the start date of the new record as the delimitation date of the old record. Gaps are only allowed between the employeeu2019s entry date and the start date of the first record.
    Time constraint 1 must be used for all of the infotypes containing information that must be available at all times. This is particularly true of personal and organizational assignment data.
    If a record is delimited because of time constraint 1, the system displays an appropriate message.
    Time Constraint 2
    No more than one valid record can exist at any one time. Records with constraint 2 must not overlap. Their existence is not obligatory. If a new record is created, the system automatically delimits the previous record, if one exists.
    If a record is delimited because of time constraint 2, the system displays an appropriate message.
    Time Constraint 3
    Any number of valid records can exist at any one time. The individual records do not conflict with each other.
    Time Constraints:
    When an info type is updated, the old data is not lost. Instead, it remains in the system so that you can perform historical evaluations. Each info type is stored with a specific validity period. This means that the system can contain more than one record of the same info type at the sometime, even if their validity periods coincide.
    If you enter and save new information in an info type, the system checks whether the record already exists for this info type. If this is the case, the system reacts based on rules or TIME CONSTRAINTS set up for that particular info type or subtype.
    Time Constraint 1: This is mandatory information that must be uniquely available, gaps are not allowed
    Time Constraint 2: This is optional information that, if available, must be unique, gaps allowed.
    Time Constraint 3: This is optional information that, if available, can exist more than once.

  • Processing classes , evaluation classes and cumulation classes

    Hi All ,
       Can anybody give the details of PCR in HR and how to use processing classes and evaluation classes in PCR.
    Regards ,
    Santosh.

    Hi,
    we have an operation VWTCL which checks the Processing class and its specification in PCR.
    go to T.Code: PE04 and check the operations documentation you will get clarity.
    Operation VWTCL VV reads the specification of processing class VV for the current wage type in table T512W, and enters this as a single-character entry in the variable argument of the personnel calculation rule. Function VWTCL is a decision operation.
    for example:
    X010 Determination of valuation bases INTERNATIONAL
            VWTCL 01   Processing class
                ERROR      Cancel processing
              0
                ADDWT *    OT   Output table
        1
            VWTCL 01   Processing class
              0
              1
                ADDWT *    OT   Output table
                ELIMI Z    Elim.time period ID
    Regards,
    mohammed

  • Error ِِِِAfter Time Evaluation

    Dears ,
                     ِِAfter running of time evaluation , i faced this problem
                     i was testing new schedule rule but it failed
                     please advice me .

    Hi Waleed,
    Please define counting class for period work schedule.
    Please refer the below document for your reference.
    Public Holiday Calendar and Work Schedule Rules
    After creating the PWS, you must define counting class for Period Work Schedule in Table V_T551C. Please refer the below screenshot.
    Grpg             -        Personnel Subarea Grouping for Daily Work Schedules
    PWS             -        Name of Personnel Work Schedule. It can have maximum 4 characters.
    Start Date     -        Start date for counting class of PWS.
    End Date       -        End date for counting class of PWS.
    Cntg Class    -        Counting Class is used to count absence and attendance by specifying different methods of counting according to the period work schedule.
    I hope this resolves your issue.
    Thanks and regards,
    Vivek Barnwal

  • Evaluation classes and cumulation classes

    Hi All ,
       Can anybody give the information about evaluation classes and cumulation classes in HR and how they affects the payroll.It is better for me if any one give the scenario to understand these concepts.I know the basics of these things i.e in which view these details are maintained for wagtypes.
    Thanks in advance.
    Regards ,
    Santosh.

    Hi Santosh,
    For any wagetype to process in payroll these cummulation class and evlatuion class is important.As payroll is Country specific each county has specific base for calculating Cummulation class.
    Cummulation Class: In payroll there are two types of cummulation
    (a) Cummulation of wage types over another wage type
    (b) Cummulation of wage types over a period of time
    For the first one it is used to calculate the base for different tax calculation. It is represented by /1 series wage types. Examples  For HRA Basis it is /111  and the base is mainly Basic+DA...etc.
    For the second one it is calculated by Processing class 30 Specification 0,1,2,3 and T. The related tables are V-T54c1, V_T54c4 and V_T54c3
    Evaluation Class: This  is used mainly for reports i,e Form 16, Form 24, Payslips etc. In India mostly used Evaluation classes are
    02 - For Payments and Deductions in Payslip
    06 - For Sec 17(1) For Total Gross
    07 - For Sec 10 Deductions
    09 - For Sec 17(3) For Perks
    08 - For Sec 17(2) For Income from other sources
    11 - For Sec 217 2 (A)
    * All these reports you can see in table V-T512w_D or V_t512w_O
    I think this will help you
    Best Regards
    Baidya

  • Processing classes, cumulation classes and evaluation classes

    Hi Friends,
             What is the diff between  processing classes, cumulation classes and evaluation classes. where we see these three and what is the table no. for this?

    .) Processing Class - A wage type characteristic that controls processing during Payroll. There are different processing classes for the various processing steps that are performed within Payroll. During the payroll run, SAP R/3 processes a wage type in a specific processing step according to its individual specification in the respective processing class.
    Cumulation class - Cumulation class are used to cumulate the model wage types to generate the /1** technical wage types.
    Example - Processing class 20 is used for cumulation and processed by PCR X023. Now suppose you have set specifiction as 8. Now if you will check PCR X023 for spec 8, it says to cumulate wage type into cumulation class which are ticked. Like may be you want to cumulate a model wage type into /101, set PCL 20 as 8 and tick cumulation class 1.
    Evaluation Class - Wage type characteristic that controls processing when payroll results are evaluated and displayed. There are various evaluation classes for the different processing steps that are performed when payroll results are evaluated and displayed.
    Example
    In the standard system, the specifications for evaluation class 02 determine how a wage type is printed on a form  that is payslip.
    Specification 00: no printing on the form
    Specification 01: prints personal payments/deductions
    Specification 02: prints wage types included in the total gross amount
    Specification 03: prints wage types derived from time-based payments and included in the total gross amount

  • Time Evaluation Re Run in Mid Month & Mid Mont Initialization !

    Hi There,
    i was trying to run Time evaluation for the period 01.04.2011 to 31/12/2011.
    from April, that is 01.04.4011 to 30.06.2011 Time evaluation was good, now time evaluation has to run from 01.07.2011 but time evaluation has repeated from 12.06.2011 to 11.07.2011 as Initialization period 07/2011, and the same scenario is repeated for the rest of the year..all periods are initiated on 12th of each month from 6th month that is 12.06.2011.
    i was been trying to rectify this issue but was not bale to solve it, could any one please look in to it and let me know how to solve it?
    your help is appreciated.
    Thanks
    Kumar

    Can you please regenerate Period Parameters for 2011 year in T-Code for OG00 for period parameter 01 and then give the hire date in the field Forced Recalculation as of run in PT60 and run  the time evaluation.
    Best Regards,

  • Use of Time Evaluation to generate Absence Quota

    Hi,
    We are planning to use time evaluation to generate absence quota. At the moment we are using RPTQTA00 report to generate Absence Quota. We have negative time management and since, the project has already gone live i have very limited scope to change the basic settings for example we do not have any employee subgroup to identify part time employees, PT & FT are in one employee sub-groups. We have only one ESG & PSG for time recording, time quota etc. The base entitlement is defined for the FT employees and it is reduced propertionately based on the employement percentage in IT0007. Now we are going to adopt a change in design, and planning to have specific work-schedule for PT employees. In that case, we will not have the scope to maintain %age in IT0007 for part time employees but exact no of working hours will be used. It means that system will treat the PT emploees as FT while generating absence quota and output the FT absence entitlement. As i said earlier we can not differentiate PT employees from FT employees based on ESG or PSG, i can not create a separate quota selection rule for part time employees. Hence, we are moving from running RPTQTA00 report to time evaluation for absence quota generation purpose.
    Now can anybody please help finding a alternate solution for the above, if it is possible to do it through report RPTQTA00 or we have to adopt the time evaluation. In case we are going to generate absence quota through time evaluation, can we only generate absence quota and skip anything that is related to payroll.
    Any comments/suggestion/advise will be very helpful to us.
    Thanks.
    Sujit

    We are not able to generate absence quota for part-time employees as when we do that, system is treating PT employees as FT employees and the FT base entitlement is referred while calculating absence quota. i can not define separate absence entitlement for PT employees as we have only one ESG and PSG, and based on this quota selection group is defined. The QUOMO feature is defined based on work contract - employee sub-group (there is no separate emp sub-group for PT employees) - Pay Scale Group. We are having this problem as we have specific work schedule for PT employees now (Ex. we create 3 days work schedule with 15 hours: 4.5,4.5, 6 hours) and we are not maintaining employement percentage for them. So system is treating PT employee as FT employee with 100% employement percentage. Please let me know if you need any specific info to understand my issue.
    Thank you so much for the response.

  • Quota updation upon accural in no time evalution(TMSTA=0)

    Dear Team,
    We went go live on one and half year back and  using no time evaluation for all employee in info type 7.
    At the time of financial year starting we will generate Absence quotas say CL, PL through RPTQTA00,
    Entitlement is 12 days,Hence April month it self, record will be created in info type 2006.
    In mid of month/year Joining employee, based on prorate base entitlement will be updated in info type 2006.
    Now Client/My requirement is:
    He does" t want to give total entitlement in april it self. every month 1 leave needs to updated. (12 days entitlement for CL, hence prorate base 1 day in April once we run in Payroll, 2 days (11) in May, 3 days (11+1) in june.. so on and so fourth...
    How we can configure this. Please help me on this.
    Regards,
    MVR

    Hi,
    Try the following setting.
    SPRO -> IMG -> Time Management -> Time Data Recording and Administration -> Managing Time Accounts Using Attendance/Absence Quotas -> Calculating Absence Entitlements -> Rules for Generating Absence Quotas -> Set Base Entitlements
    In this select your Quota type and give ENTITLEMENT CONSTANT as 1.
    RELATED TO PERIOD as Accrual Period
    SPRO -> IMG -> Time Management -> Time Data Recording and Administration -> Managing Time Accounts Using Attendance/Absence Quotas -> Calculating Absence Entitlements -> Rules for Generating Absence Quotas -> Define Generation Rules for Quota Type Selection
    In this, double click your Quota Type then Goto Accrual Period Tab and select Month
    Now, the  Program RPTQTA00 has to be run run every month with suitable Data Selection Period
    Thanks and Regards
    Kiran

  • Time Evalution & PDC recalculation

    Dear Experts!
    I have to face an weird problem. My scenario is as below:
    1. I create a new Time Type to calculate the working date of employee in every month. My time wage type will replace an existed wage type in system, because it's configuration is not correct.
    2. After checking on Dev, QAS, the value of Earn Leave ( generated monthly) is CORRECT, we move this TR to PRD.
    And after moving it to PRD, there are a lot of employee re-run PT60 from Go Live Date. I don't know why.
    Could you please guide me the way to know which recalculation date in Time Evaluation, and How SAP decide the date to retro Time Evaluation in PT60? I just guess the field PDC recalculation in IT 3 ( I read F1 of this field), but now I'm mixed about this information.
    And you know, because we change the Earned Leave in Time ( I  run PT60) eg: Earned Leave for Feb-2010 will be modified, of course the value of Time Wage Type will be changed. The date Earliest MD change in IT3 is NOT Changed. But the Payroll for this guy is retro from Mar-2010.
    Can you please help me clear the way to re-run Time Evaluation & Payroll.
    Regards!
    Woody.

    Hi Woody,
    Please note  the below Points carefully, which may help you to solve your issue:
    Note -
    Retro Runs are based on Infotype,  If you change any Infotype related to Time / Payroll, then the system automatically maintain the "Earliest MD Change" date in IT 0003.
    For IT 0003
    1) When you change employee data that is relevant to payroll, the system stores the earliest date from which the master data change is valid. This date can be a future date after the last payroll run
    2) The system deletes the date in the Earliest master data change field after successful completion of the payroll run.
    The earliest recalculation date for time evaluation is also queried when master data and time data that is relevant to retroactive accounting is changed.
    For Payroll Controll Record
    Earliest retroactive accounting period
    1) Retroactive accounting in payroll can begin on the start date of this period at the earliest.
    2) If changes relevant for retroactive accounting have been made before this date, the system does not take these into account in either current or future retroactive accounting. However, retroactive accounting is initiated up to this period.
    3) If the earliest personal retroactive accounting date (from IT 0003) differs from the earliest retroactive accounting period, then it will be backdated to the later date.
    Comments:
    1) May be the Time Wage Type Change (related to Payroll) might have triggred the Retro Payroll, and once it retro run happens the "the system delets the date in the Earliest Master Data Change Field", that is why you are unable to find that field with values.
    2) Check the "Earliest Retroactive Accounting Period" in Control Record (Tcode PA03), so that you will get some idea. why it has happend.
    3) While determining the Retro, the system checks the IT0003, Control Record, it will take the date whichever is backdated date.
    Hope this helps.
    Regards
    Venu

  • Error in time evaluation

    Dear All,
    time evaluation is throwing an error msg "No entry in table T001P for key" for only one employee in the time evaluation display log.
    Its happening in the initialization part in time evaluation. for example,
    If i run the time evaluation for the month of 01.01.2009 to 24.02.2009. error message throwing on the initialization of 01.02.2009.
    I have checked all the groupings in table V_001P_all.  All are correct.
    Where should i do the correction. Pls
    Br.
    Manjula

    Hi Sikindar,
    I have checked all grouping in V_T001P_All  every think is correct,
    And how can i check with grouping with dates??
    This employee getting error message only in the initilation part in time evaluation log.
    example if i run the time evaluation from 01.01.2009 to 01.03.2009 . time evaluation running only from 01.01.2009 to 31.01.2009 . its not moving to next month.
    if i run time evaluation from 01.02.2009 to 01.03.2009 then its running only 01.02.2009 to 28.02.2009 its not moving to next month.
    In the initialization in the next month im getting error message (no entry in table T001P for key)
    Thnaks.
    Manju

  • Time Evaluation Re Run

    Hi There,
    i was trying to run Time evaluation for the period 01.04.2011 to 31/12/2011.
    from April, that is 01.04.4011 to 30.06.2011 Time evaluation was good, now time evaluation has to run from 01.07.2011 but time evaluation has repeated from 12.06.2011 to 11.07.2011 as Initialization period 07/2011, and the same scenario is repeated for the rest of the year..all periods are initiated on 12th of each month from 6th month that is 12.06.2011.
    i was been trying to rectify this issue but was not bale to solve it, could any one please look in to it and let me know how to solve it?
    your help is appreciated.
    Thanks
    Kumar

    Hi,
    thanks for reply but till now i have not yet customized the schema or any pcr, so it is pretty much standard TM04 schema, could  you plz elaborate your answer?
    Thanks.
    Kumar

  • Time evaluation:Regeneration of leaves for past with new slabs.

    Hi Gurus
    Find below our requirement and advice accordingly
    1.Employees annual leave entitlement slabs are bifurcated based on length of service as below
    Tenure with Company      Eligibility/Month
    1. Probation        1.5 Days
    2. 0-3 Years                           2 Days
    3. >3-6 Years     2.08 Days
    4. >6-10 Years     2.16 Days
    5. >10-20 Years     2.33 Days
    6. >20 Years Above     2.50 Days
    2.Probationary /regular employee bifurcation is done at employee subgroup level
    Emp Subgroups     Employee
    1. 01 - 10            Regular
    2. 11 - 20                          Probationary
    3. We use time evaluation schema ZM01 copy of TM01.
    4. On hiring, probationary will be assigned with employee subgroups 01-10 via hire action.
    5. On confirmation, probationary will be changed with employee subgroups 11-20.
    6. For probationary, system will generate monthly accruals of 1.5/month days till confirmation.
    7. After confirmation system will start generate 2 days/month.
    8.  We have a requirement that after confirmation action system should re generate the leaves from date of joining as per the employee after probation.
    Illustration:-
    1. Employee joined under probation on 01.06.2011.
    2. His monthly annual leave accrual till 31.12.2011 will be 9days i.e. (1.5 days * 6 months)
    3. On running confirmation action system should regenerate his annual leave from his date of joining with the new slabs and it should be 12 days i.e. (2 days * 6 months).
    Is it feasible in time evaluation. Pls advice.
    Thanks in advance, Thanesh

    Hi
    I have a couple of queries on this scenario.
    We can do it on the base of base entitlement but there is action dependency then its better to write PCR.
    First Check action type --> Then give the quota as 1.50 or 2 days as per req the nupdate the quota.
    Here before writing the PCR we need to take care of one thing that once employee changes the action it could not check the old action. Say for Ex when i am checking the probation and changed the Probation to permenant then it should not check the Probation again. So we need to put a counter check here.
    So i am writing a logic like first will check Probation an
    For Ex : We take Probation Action type as 01 and Permenant Action type as 02
    ZT05 Personnel Calculation Rule  ZT05                   
          " HRS?1      Decision op.     HRS                 
            " <                                             
              " OUTWPMASSN Action Type                      
                " 01                                        
                  " OUTWPMASSN Action Type                  
                    " 02                                    
                        HRS=1      Set                      
                        ADDDB1230  Add to day balance       
                        HRS=1.50   Set                      
                        ADDDB1234  Add to day balance       
                  " OUTWPMASSN Action Type                  
                    " 02                                    
                        HRS=2      Set                      
                        ADDDB1234  Add to day balance       
    Please create Time Type 1230 and 1234 at T555A.
    Hope this helps you. All the best. Let me know how it worked.
    Reg,
    Srini

  • Time Evaluation quota not transferred

    Hi,
    For a couple of employees when i run time evaluation, quota type 91 gets generated and transferred but quota type 93 does not. It remains 0.
    On analyzing the logs, i found that for these employees, there is an entry in table QTTRANS with the quota amount that was supposed to be transferred.
    According to doc on help.sap.com, {Table QTTRANS indicates the status of the transfer pool for each day. The cumulated entitlements are indicated until they have been transferred to the *Absence Quotas *infotype (2006) or until the entitlement has expired.}
    This means the quota amount for quota type 93 is being generated, but is not being transferred to infotype 2006. Also, the transfer time in the rule is not being shown on ad-hoc basis for these two employees for this particular Quota type. The other quota type 91 which is evaluated on exactly the same basis is working fine.
    I have checked the transfer period in config and it is monthly. Also, for other employees in the same grouping PSG, ESG, quota is being generated and transferred correctly.
    Quota of 2.5 should be transferred on the last day of every month.
    Further, analysis of QTTRANS over a period of time reveals the following results:
    Jan05 Quota transferred : 0 ;Table QTTRANS: 2.5
    Feb05 Quota transferred : 2.5 ;Table QTTRANS: 2.5
    Mar05 Quota transferred : 2.5 ;Table QTTRANS: 5.0
    Apr05 Quota transferred : 7.5 ;Table QTTRANS: 2.5
    May05 Quota transferred : 10 ;Table QTTRANS: 2.5
    Jun05 Quota transferred : 10 ;Table QTTRANS: 5.0
    Jul05 Quota transferred : 10 ;Table QTTRANS: 7.5
    Aug05 Quota transferred : 17.5 ;Table QTTRANS: 2.5
    Sep05 Quota transferred : 20 ;Table QTTRANS: 2.5
    Oct05 Quota transferred : 20 ;Table QTTRANS: 5.0
    Nov05 Quota transferred : 25 ;Table QTTRANS: 2.5
    Dec05 Quota transferred : 25 ;Table QTTRANS: 5.0
    For the entire year, it should have generated and transferred 30 but actually it is 25.
    I would be very grateful if anyone can point out the cause of this issue.
    Thank you,
    Regards,
    Zubair

    HI,
    You can view in IT2006 accumulated Quota means current year Quota + carry over Quota. In Time cluster tables "QTTRANS" you can view Quota transfer value.
    Refer T.code: Pt66 for Time cluster tables.

Maybe you are looking for