Show TOC
Define fields
relevant for retroactive accounting
In this step you define the retroactive
accounting relevance of infotypes for Payroll and
Time Management.
- Retroactive Accounting Relevance of
Infotypes
In the view
Retroactive accounting relevance for payroll and time per
infotype (V_582A_D), check and, if necessary, change the
retroactive accounting relevance of infotypes for Payroll and Time
Management.
You can make the
settings for Payroll and Time Management entirely independently of one
another. If you set an infotype to relevant for field-dependent retroactive
accounting, you then have to list the infotype's fields that are relevant for
retroactive accounting in the the view
Field-dependent retroactive accounting
recognition (V_T588G).
- Field-dependent Retroactive Accounting
Relevance
If the
Retroactive accounting relevance for payroll field in V_582A_D
is set to T (field-dependent), you must list the fields which
trigger retroactive accounting for Payroll in V_T588G
Field-dependent retroactive accounting
recognition. In the field Type , enter
the value 1 for these fields.
If the
Retroactive accounting relevance for PDC time evaluation field
in V_582A_D is set to T (field-dependent), you must list the
fields which trigger retroactive accounting of time data in V_T588G. In the
field Type, enter the value 2 for
these fields.
You can still set
certain fields to unmodifiable in the payroll past. Such a setting could, for
example, be used for transfer data, since a retroactive change for such data
would not make any sense.
- Retroactive Accounting to Previous
Day
Under certain
circumstances it may be necessary to activate retroactive accounting to the
previous day. The retroactive accounting can be triggered subject to a variety
of parameters, such as the current action.
Set up the feature
RETRO (deviating retroactive accounting trigger). You will
find further information in the documentation on the feature.
- Retroactive Accounting Relevance on
Wage Type Level
You can forbid a
change in the payroll past for an infotype that is relevant for retroactive
accounting on the level of infotype and wage type. If you want to do this, you
should mark the indicator No entry in
payr.past for the chosen infotype and the wage type in the view
Wage type dependent retroactive
accounting trigger (V_T591B).
At present you can
use this function fot the infotypes Capital
Formation (0010), Recur.
Payments/Deds. (0014), Additional
Payments (0015), CP: Transaction Data
(0215) and One-Time Payments
Off-Cycle (0267).
Note
For performance reasons the system stores the
location of fields in the infotype structure and the format of these
fields.
If the definition of the infotype structure
"PSnnnn" in the Data Dictionary changes, you must update the values using the
Recalculate function in the view
Field-dependent retroactive accounting
recognition (V_T588G).
Example
- Field-dependent Retroactive Accounting
Relevance
The administrator fields in the
Organizational Assignment (0001) infotype are not relevant for
retroactive accounting. If these fields are changed in the payroll past,
retroactive accounting should not be triggered. Retroactive accounting of
Organizational Assignment is therefore marked as
being relevant for field-dependent retroactive accounting.
The fields that
trigger retroactive accounting are listed in the view
Field-dependent retroactive accounting
recognition (V_T588G).
- Retroactive Accounting to Previous
Day
When performing a
leaving action, you want retroactive accounting to the previous day to be
triggered, so that even if the date of leaving was after the payroll was run
for the current month, specific calculations are carried out in the next
payroll run.
Requirements
You must mark the infotype as relevant for
field-dependent retroactive accounting.
Standard
Settings
The standard SAP System contains infotypes with
meaningful settings for retroactive accounting relevance.
SAP has marked certain infotypes as relevant
for field-dependent retroactive accounting. The relevant fields are
defined.
Recommendation
System performance is better if you mark an
entire infotype as relevant for retroactive accounting and not only specific
fields. Only if an infotype contains fields which do not require recalculation
should these be defined as exceptions.