Collect Overflow Type P - Patching? Time evaluation?

Hi Experts!
I have an issue and I need your help.
The client is in the process of patching Development, QA and Production. They have patched the DEV and QA clients and have yet to complete production.
Testing in QA of time evaluation forced retro’d back a couple of years causes the following error (Collect_Overflow_Type_P) :
The ABAP’er came back with this:
I have processed time evaluation (with the log) at specific points in time to try and establish why the SALDO/TES tables are keeling over but I am really struggling to get to the bottom of this.
The issue is not present in production, I am concerned that if production is patched and this issue remains, there will be significant issues for payroll!
Is it a patching issue?
Is it relating to note 1879092
What is SALDO_NEW and is it something to do with this?
Any help would be greatly appreciated!
Will

Hi Inge,
I have had the same issue as you in the past so thats where I started investigating. None of the time types come anywhere near the limits... Thanks for your reply, its a great suggestion!
The ABAP'er is checking with the Basis Team  whether note 1942144 has been applied.
Will

Similar Messages

  • Attendance type in time evaluation

    Hi All,
    Need solutions for the below issues.
    1) Clock in and clock out information for an employee is stored in SAP in IT2011, if clock in or clock out information is missing for an employee it should trigger a mail to employee and his manager.
    2) Currently using one attendance type : On duty would be raised by employee when is on business trip. System should consider this as working.
    During time evaluation it should consider if any attendance type and clock in and clock out details for an employee. and generate the absence quotas.
    There is no integration with payroll.
    3) If the accumulated earned leaves cross 90 days, rest of the leaves to be encashed, is there any standard sap solution for this or need to write a PCR or custom development to be done.
    Please let me know ho to do.
    Regards
    Vish

    1. The TD20 PCR in time schema evaluates time pairs and errors out if times are missing. The errors are stored in the FEHLER table. Maybe you can write a custom program to read this table and send messages.
    2. The On duty will be entered in IT2002 I guess. The positive TE schema will read both IT2011 and IT2002 and so should not be a problem.
    3. You need to write a PCR to accomplish this. There are useful doc on this forum. This doc by Vivek is very helpful:
    http://scn.sap.com/docs/DOC-55755
    Regards
    Pramod

  • 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

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

  • Absence quota generation with PCR in Time Evaluation

    Dear All,
    I am generation absence quota Annual leave = 50 through PT60- ZM04. Its daily calculation and transfered at the month end.
    The quota entitlement is 30 days per year.
    I have written this pcr. Have configured a time type too. but not sure why its not generating any quota.
    The time type I have configured is:
    Time Type: 0097
    Save as day balance - No Formation
    Save as period balance - 1
    Store for time accounts - 1
    Have assigned the time type 0097 in Base entitlement for Absence quota generation as Day Balance and even in generation rules.
    Have placed the PCR with ACTIO Z003 before CUMBT fucntion.
    The PCR Z003 is:
    000010 D HRS?0
    000020 *
    000030 = D OUTAQTYP
    000040 = **
    000050 = 50 Z GCY ZQTY
    PCR ZQTY is:
    000010 D OUTWPMOLGA
    000020 **
    000030 99 HRS=FR50C ADDDB0097Z ADDDB0097 HRS=D0097
    I didnt mention anywhere in configuration or PCR that its 30 days per year.
    Do I need to do this?
    Have I missed out anything, please help me.
    Thanks & regards,
    Majid

    Hi,
    This you can do through config also without using PCR.
    Base entitlement is 30 for calender year. Selection rule- Accrual period is daily and transfer time is time evaluation period.
    Use appropriate rounding rule in selection rule.
    Rgds,
    Lata

  • Absence Quota Carry Forward without Time Evaluation (TQTR)

    Dear Experts,
    The client requires the left over from 2 quota types to be carry forward to 1 quota type next years.
    e.g. from Annual Leave and Casual Leave is to be carry fowarded to following year's Annual Leave. As well as the total quota for Annual Leaves cannot exceed 60.
    Now the problem is, if we were using Time Evaluation here, i know i couldve done it through TQTR, which woudve been very convinient. But we arnt generating quotas through the rule, neither are using TM00 or TM04.
    Your help and input in this regard would be highly appreciated.
    Thanks
    S.N.

    http://scn.sap.com/docs/DOC-35168
    for #1..assuming your quota follows calendar year 01/01 to 12/31. Refer to above link for more details. The idea is to do the following 3 steps in order to generate a carry forward quota bank.
    1. Setup a quota type "17" in the quota configuration and attach a daily balance time type to this quota type. E.g ZQ17
    2. Write a custom PCR...to read remaining balance for current year's quota ban on 12/31..and store this in a different time type. ZREM
    3. in the same PCR...on 01/01 (next day)...read the previous days balance in ZREM using HRS=LZREM...and assign this balance to ZQ17...this will generate you quota bank for 17 for the next year.
    for #2...
    instead of update program locking the previous years quota banks...its better for update program to create a IT2013 adjustment to 0 out the balance of the previous years quota. This can be an LSMW upload. You can get remaining balances of current quota banks for all applicable employees and then load IT2013...with reduce entitlement as radio button option.

  • Time Evaluation : Operation/Function to update quota entitlement

    Hi,
    within time evaluation quato entitlements are determined.
    Due to changes legislation, under particluar circumstancens the entitlement of the quota need to be updated.
    I've build all 'circumstances' in a time evaluation rule and now all what needs to be done, is to perform a deduction an a specific quuta type. The number of hours to be deducted is already stored in a time wage type (as part of the new calculation rules).
    Which operation or function can be used to update the quota entitlement with the number of hours stored in the time wage type.
    Thanks,
    Wilfred.

    Hi,
    if was looking at this operation but couldn't manage to get things working as I would like.
    Is there a link available with more detailed information on this operation besides the information available in SAP (PDSY)?
    Thanks,
    Wilfred.

  • Absence Quota creation during Time evaluation - Orgnaisational Assg change

    Hello Experts,
    I have one emplyee for whom the Transfer action has been run - his personal subarea has been changed from 1633 to 1654
    obviously the ps grouping for time quota type changed form 35 to 40.
    so function QUOTA is creating different quota for this employee than what there exist right now for infotype 2006.
    so during time evaluation below error is comming.
        Error entry no. 83 Error when creating absence quota
        A complex application error has occurred
    Kindly let me know how to overcome this error.
    Thanks Jay

    The reason 'error no. 83' occurs in RPTIME00 is because function QUOTA
    is trying to generate a quota type which does not exist for the employee
    on a specific day. It must have existed some time before.  Normally,
    the function QUOTA displays an error message concerning the
    non-existing quota types. In this case, the 'error no. 83' can only
    occur in the following scenarios:
    1. If you deleted a quota type that was to be generated
    2. If an employee has an organizational reassignment to a personnel
       subarea or employee subgroup which have different groupings for quota
       types and for these groupings the 'old' quota type does not exist.
    Function QUOTA checks to determine if the quota types to be generated
    are valid.  If the quota type is not valid anymore (see reason 2) then
    you will get a warning message.
    "the problem in these situations was the following:
    RPTIME00 is trying to generate a quota for a validity interval
    (defined in table T559D) during which the employee belongs to two
    different groupings, due to the transfer.
    In your case the quota type should be generated with a validity interval
    that begins before the employee's organizational change.
    Unfortunately, for the time between the validity begin up to the
    transfer of the employee there is no entry in table T556A for this quota
    type.
    or check the config of this quota running Rptquota_check in se38
    Therefore, it is possible to solve the problem by defining a dummy
    quota type for the 'old' groupings of the employee (table T556A).

  • How to Update Absence Quota with Time Evaluation

    Dear Friends,
    I would like to know how do we update absence quota within time evaluation. Currently i'm using UPDTQAXX, it works but when i search this forum everybody was using this simple code:
    HRS=something
    ADDDBxxxx
    and the quota is updated. I just dont get it, with adddb its only update the daily balance table, how does that enable us to updated the 2006 infotype? Many Thanks

    ADDDBxxxx adds the value of the number of hours field to the specified time type in the table of day balances (TES), it does not update the quota.
    You can use function QUOTA  to accrue absence entitlements periodically based on this customizing: Personnel 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 Selection.  
    You can use a time type to prorate that accrual

  • How to change the date generate absence quota(Time Evaluation)

    Hi all experts,
    Currently system use Time Evaluation, and generate absece quota in last day of month.
    So any way to change that system will use differ day to generate absence quota?
    Example use day 28 of each month will generate absence quota? Have any enhacement or configuration?
    Thank you,

    Tatsuya,
    there 2 better solutions for this, one is Generate Period Parameters and according accordingly the month end date you follow and use the same period parameter in V_T559L table to your Quota.
    and other Solutions is Write a PCR like Below.
    ABCD     (PCR Name)
       varstcrumo
            Varstreday
                 28
                   hrs=1
                   adddbTIME (TIME - Daily Time type - Create it in V_t555a table)
    Save it and go to TM04 Schema, and put this PCR with Function ACTIO and make sure to insert this before QUOTA Function and Before CUMBT. and save it, and dont forget to put TIME Time to your Base entitlement.
    you can run Time Evaluation to test it...let me know how it worked.

  • Time evaluation error "Error while positioning ABWKONTI" for leave entitlem

    We are currently running on SAP ECC5. Time evaluation is run with schema TQTA everymonth to create leave quotas in info type 2006.
    I am experiencing a time evaluation error "Error while positioning ABWKONTI" for one employee when running TQTA.
    This employee was engaged on 14/08/2006. When I checked the logged changes per infotype, I found that a record for 14/07/2006 was deleted. I did check all the infotypes and all is reflecting the correct start date. I would really appreciate if someone can tell me how to fix this problem. Currently the leave entitlements are being processed manually. Please see below the error I am receiving:-
    Log: Time Evaluation
    4 General data
    Successful personnel numbers
    Personnel numbers with errors
    Personnel numbers ended early
    5 Personnel Numbers Rejected
    5 00408765 Van Wyk Werner
    U Error while positioning ABWKONTI
    13A200608 0002006081320060714###%##
    Quota could not be positioned:
    2006 08 2006.07.14 2006.08.13
    Relative day in period: 13 200706
    Quota used/quota entitlement to be accounted: 1.25000
    Person rejected: 00408765
    Messages
    5 Statistics
    Selected personnel numbers 1
    Successful runs for 0
    including with errors 0
    Processing not completed for 0
    Rejected 1
    Total number of messages and error messages 1

    Hi,
    Which Function Ur using for TQTR, Check That other wise P2006 Function Used.
    I think the error is in ur PCR.
    First u Understand the business process then write the PCR.
    Send ur pcr what u had written.
    also send ur Business senerio.like Conditions........

  • Difference between Time Management and Time Evaluation

    Hello
    Is there any Difference between Time Management and Time Evaluation? if yes, then what is it? I guess there's no diff, time evaluation is a report..
    please advice
    Thanks

    Hi Charlene,
    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.
    Regards,
    Swapnil

  • How to Calculate Seniority of an Employee in Time Evaluation????

    Hi All,
    I am working on Carry Forward of the Vacation Quota from one year to the next.
    The number of hours of the Vacation Quota that an Employee could carry forward to the next year is based on the Seniority of the employee.
    My question to you all is:
    How do I calculate the Seniority of an employee in Time Evaluation, say using a PCR or so???
    Any suggestion from you on it is highly welcome.
    Looking forward to hear from you soon.
    Regards,
    Aslam

    You can write your PCR by quering on the IT0041 date type - Hire Date.

Maybe you are looking for