Skip to Content
avatar image
Former Member

Retroactive acct. relevance for PDC time evaluation

Hello all,

A very quick question, I'd like to check if there is anyone here who has checked the Retr.acct.PDC field in Infotype Attributes table, for Actions & Org Assignment infotypes.


Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Best Answer
    avatar image
    Former Member
    Sep 18, 2012 at 10:32 AM

    Hello ,

    You need to check in IT0003.

    Earliest personal retroactive accounting date

    Defines the date in the payroll past up to which master and time data changes are allowed as well as the date up to which the system carries out retroactive accounting.

    The retroactive accounting limit is determined by:

    • The earliest period for which retroactive accounting can be run that is specified for the payroll area in the payroll administration record
    • The earliest personal retroactive accounting date that is stored in the Payroll Status infotype (0003) for the personnel number
    • The hiring date that is stored for the personnel number

    The system determines the latest date as the retroactive accounting limit from these date specifications.

    Run payroll up to – End of processing 1 (run payroll for up to)

    Date up to which the payroll is run for the employee, even if he or she has left the company.

    In this payroll run, the system selects an employee who is not active in this payroll period if the end of processing 1 is set.

    You can set the end of processing 1 in the Payroll Status (0003) infotype. The end of processing 1 can also be set by the system through various functions, in deductions for example.

    This date must be in a period in which the employee is not active.

    Do not account after – End of processing (do not run payroll for after)

    Final date up to which payroll is run for the employee.

    After this date the employee is no longer selected for the payroll. You cannot override this date.

    The employee may not be active on the day after the end of processing.

    Accounted to

    The Accounted to date specifies the date up to which payroll accounting has been run for the employee.

    Payroll accounting cannot be run for personnel numbers which are to be accounted in payroll periods in which the end date is before the Accounted to date.

    E.g. The January payroll run cannot be repeated once payroll accounting has been executed for February. If the payroll area changes, payroll can only be run after the Accounted to date.

    Earliest master data change since last payroll run

    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.

    The payroll program uses this date to determine if and, if so, from when, a payroll run must be carried out again in order to take the master data change into account. Depending on the control record status, the system automatically triggers either retroactive accounting or a repeat payroll run.

    E.g. You have run payroll for an employee up to March 31. There is a change in the master data of an infotype which is relevant for payroll: The start date is 09.06.1998; the date in the Earliest master data change is set to 09.06.1998. Retroactive accounting is not performed during the next payroll run.

    The start date is 04.03.1998; the date in the Earliest master data change field is set to 04.03.1998. This period is recalculated in the next payroll run.


    You can set retroactive accounting relevance either per infotype (infotype features) or per field (fields related to retroactive accounting).


    The system deletes the date in the Earliest master data change field after successful completion of the payroll run.

    Exception: If the employee has a status other than ’0′ or ’7′ in time management (infotype planned working time (0007)) and is not present for the total specific payroll dates evaluation results (cluster B2), payroll fills the field with the first day on which the time evaluation result is available.

    The time evaluation program also sets this field using the function CHECK RPR.

    Earliest payroll-relevant master data change (bonus)

    This field, like the ‘Earliest master data change’ field, is set when master data is changed. The Earliest master data change bonus field is set by the master data processing and deleted by bonus payments in the payroll program as well as by unauthorized manual checks (NAMC, only for U.S.) It allows retroactive accounting of bonuses following changes in master data.

    The system deletes the date in the Earliest master data change bonus field after each regular payroll run and after bonus payroll runs (or NAMC) if the date is higher than that of the last bonus run or the last NAMC.


    You can use the Bonus Info function to display additional retroactive accounting information from table T52RIC. This function is only active if appropriate entries exist for the current personnel number in the table.

    When you select the Bonus Info function, the H99UDEL_T52RICreport is started and the relevant entries from table T52RIC are displayed. If you edit infotype 0003 using transaction PU03, you can also delete existing entries from the table. Ensure that when you delete entries, this happens immediately in the database and not only when you save infotype 0003.

    For more information, see the documentation of the H99UDEL_T52RIC report.

    Indicator: Personnel number locked for payroll

    If you flag the persno locked (personnel number locked) indicator, the employee is excluded from payroll. The employee’s personnel number is then not selected for processing. If you do not flag the Persno locked indicator, the employee’s personnel number will be selected for processing.

    Indicator: Payroll correction run necessary

    The system automatically activates the payroll correction indicator, if a personnel number was rejected in the payroll run or if changes were made to payroll-relevant data in the correction phase.

    At the same time, the system writes this personnel number into the payroll correction run search help. This search help is installed as a search help for personnel numbers in Personnel Administration.

    By calling up the search help, you can select personnel numbers that have previously been rejected in the payroll report and run the payroll again. The payroll correction indicator is removed from all personnel numbers that are accepted in the new payroll run in the payroll status infotype (0003).

    Earliest personal recalculation date for time evaluation

    The earliest personal retroactive accounting date for time management, enables you to restrict the earliest retroactive accounting period for time evaluation (including pair formation) for individual employees.

    You can restrict retroactive accounting for time evaluation and pair formation to prevent the evaluation results from being changed. The earliest retroactive accounting date is determined by the following:

    Control record for Time Management: The view ‘Earliest Retro accounting Periods for Control Record’ enables you to limit the earliest retroactive accounting periods for particular organizational units.

    Earliest personal retroactive accounting date time evaluation field in Payroll Status infotype (0003):

    This field enables you to determine the earliest recalculation date for individual employees.

    If these two values differ for an employee, the later date is taken as the earliest possible retro accounting period.

    The earliest recalculation date for time evaluation is also queried when master data and time data that is relevant to retroactive accounting is changed.

    Date as of which personal calendar must be generated

    Specifies the date as of when you have to generate the employee calendar. The personal calendar is used in the following countries, for example: Austria. The international calendar (database PCL1, cluster PC) does not use this field. Belgium, in the report RPTGENB0


    A value is supplied for the field by the report RPTGENA0 (generate personal calendar).

    You can also update this field by entering or changing time data. However, modification of time data affects the field only if the changed data refers to a date earlier than that which is saved in the field.

    Recalculation date for PDC

    This field specifies the date on which the next time evaluation run should start. When time evaluation is complete, the date is set to the first day for which the report has not yet been run. This field is used for the retroactive accounting recognition in Time Evaluation.



    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Well, true, we do have negative time.

      It's hard to see why the absence entry triggered the retro- RPUAUD00 wasn't conclusive; the entry was for previous month, but retro went back to the date in PDC recalc field, which was a number of years.

      I've just noticed that the entry for feature TIMMO is 01, which is set to before the control record date in T569R- (01.01.1990). That might possibly be a factor.

      Thanks for the input.

      (Update:  I checked the employee's org unit cost distribution and it was replaced with another cost centre backdated to 1.08.2008 hence the long retro due to inheritance- always simple!)

      Message was edited by: Farhan Khan