The following requirements have been taken into account by the
new interface for posting payroll results to accounting in Release
To support Human Resources and Accounting systems that operate
separately and are linked by Application Link Enabling technology
To increase process security
To replace batch input technology with a direct interface to
To increase revision security
To remove the need to access the posting manually in
The posting process has been changed in the following ways:
The selection of data and the processing steps for creating
posting documents no longer take place within the 'Prepare
Evaluation' step (report RPCALCx0 with evaluation schema X500) or
within the 'Transfer to FI/CO' report (report RPCIPO00). Instead, a
special report is used that creates an evaluation run and
evaluation documents for posting. To access this report (RPCIPE00),
choose Payroll Accounting -> Subs. Activities.
The posting runs and documents are monitored and processed
using the 'Edit Run' transaction (transaction PCP0).
You can also access this transaction
by choosing Payroll Accounting -> Subs. Activities. You can use
it to perform the following activities:
The created documents can now be monitored online in the system
using a variable list. Previously, they could only be monitored
using the paper documents created during the transfer to
The documents are now posted to accounting via the RW interface
after the individual documents have been released and the 'Post
documents' action has been chosen. Previously, the documents were
posted to accounting using a batch input session and transactions
for FI and CO. Each recipient in accounting now receives the
appropriate information only.
User actions that were previously required in exceptional
circumstances when batch input sessions were processed are no
longer necessary because these circumstances are taken into account
when the documents are created (for example, closed cost
If you require detailed information for revision purposes, it
is no longer necessary to repeat the entire process using the
'Activate revision' parameter. As of Release 4.0A, permanently
stored documents can be examined. You can access detailed lists
that contain information about the composition of the individual
Previously, it was only possible to ensure that the posting
process was complete and correct by using organizational actions.
This is now supported by the system.
If possible, retroactive accounting results are now evaluated
using an index, instead of having to re-evaluate the payroll
The 'Prepare Evaluation' step (report RPCALCx0 with evaluation
schema X500) is now only required if additional datasets for other
evaluations are created in this step (for example, for a social
insurance statement in Germany).
It is still possible to transfer data between different clients
and systems, although the procedure for two 4.0 systems has been
completely converted to ALE technology. Integration of R/2 Systems
and earlier releases is also possible, although the procedure has
changed with Release 4.0.
The new functions are documented in detail. Descriptions can be
found in the documentation on Payroll Processes (Subsequent
Activities), on the Technical Basics of Payroll Accounting, in the
Implementation Guide (IMG) for Payroll Accounting, and in the IMG
for ALE scenarios.
As of Release 4.0, additional document information, evaluation
information, and index information is stored in HR. This increases
memory usage per payroll period.
User authorizations must be modified for the new transactions
and reports. This affects tables PPOIX, PPOPX, PCALAC, PPDHD,
PPDIT, PPDMSG, and PPDIX, transaction PCP0, and report programs
RPCIPE00, RPCIPA00, RPCIPP00, RPCIPS00 and RPCIPD00.
Change system parameters in customizing
Setting up the posting of payroll results has been changed and
To use the new functions, please make the following changes in
Customizing. Because most of these activities are contained in the
Implementation Guide (IMG) for Payroll Accounting, please access
them from the IMG.
1. Use the 'Employee Grouping for
Account Determination: Define Values' activity to enter your
required values for the 'Employee Grouping for Account
Determination' (table T52EM).
2. If you have modified personnel
calculation rule X510, please make the required changes in the
'Determine Assignment of EE Characteristics to EE Grouping for
Account Assignment' (feature PPMOD).
3. Run report RPUCVT30 to convert the
assignment of wage types to G/L accounts in T030. Check the log to
ensure that there are no inconsistencies in the previous table
Please note that the values for the
employee grouping for account determination and the symbolic
account, which were previously summarized in one field, were in two
fields. The symbolic account is converted as ccss where cc is the
country grouping and ss is the old symbolic account.
Furthermore, '*' entries were
converted to entries with employee grouping for account
determination. This allows you to use the modified functions for
such generic assignments.
Please note that the document split
account is now assigned in the step 'Assign Technical Accounts'
(table T030, transaction HRA). This means that the entry 'BS',
which was previously used in the 'Assign Financial Accounts' step
(table T030, transaction HRF), has been converted to the entries
'1001' and '1002' in the 'Assign Technical Accounts' step.
4. If you use person-related or
loan-related customer and vendor accounts, please change the
existing entries in the 'Assign Customer Accounts', 'Assign Vendor
Accounts' and 'Assign Customer Accounts for Loan-Specific Posting'
steps. As of Release 4.0A, the subledger account is determined when
the documents are created, which means it is necessary to store the
field previously used to record the search term in a coded form.
You can determine possible account key assignments for the field by
checking the appropriate step in the IMG.
Example: If you previously used
matchcode Y with the personnel number in the Customer Personnel
Number for Account Determination field to determine accounts,
replace the entry '*Y' with the entry '*0002'.
5. In the 'Define Symbolic Accounts'
step, please check the table of symbolic accounts (T52EK). The
table entries are entered automatically during conversion.
Please check that the assignment of
the 'EG-dependent' field is correct. If the assignment is generic
(see step 3), please delete the flag.
6. Ensure that calculation rule X520
has been modified. In Release 4.0, you can almost always make these
types of changes to the standard calculation rules by enhancing the
assignment of posting characteristics for symbolic accounts, and by
assigning wage types using table entries. In such cases, please
modify the wage type assignment and symbolic account entries
created by the conversion. If this is not possible, you can still
modify the symbolic account using the function exit
EXIT_RPCIPE00_001 in the SAP enhancement PCPO0001.
7. Please check the Posting Wage
Types table (view cluster V_T52EL), which is automatically filled
with existing data during the conversion. Take careful note of any
inconsistency messages that are displayed for the old Customizing
during automatic conversion (XPRA RPU40CIP) and during step 3 of
conversion report RPUCVT30.
If you have reloaded processing class
32 and evaluation classes 01 and 04 after automatic conversion
(XPRA RPU40CIP) using report RPU12W0C, report RPUCIA00 is available
to assist you in the clearing process (see the report
8. Please note that as of Release
4.0A, overhead cost assignments that are not employee-specific
('fixed cost centers', or 'fixed orders') can be defined for
specific business areas. When using business areas, determine
whether you require this function and, if necessary, change the
9. If you are using the new function
for replacing CO account assignments by substitute account
assignments, and if there are existing closed master cost centers
and closed CO account assignments for assigning accounts across
company codes, you will need to provide substitute cost centers.
Create suitable substitute cost centers in Controlling and define
the appropriate assignment to a specific business area in the step
'Set Up Substitution Cost Centers'.
10. If you want to use the new
functions for determining the posting date using a table or for
posting in special periods, you must manually create entries in the
Payroll Date Types table (table T549S, date modifier 04) for all
payroll periods affected by posting evaluations (not required for
countries for which the date has already been required, so that it
is already available). To do this, choose the step 'Maintain
Posting Date for Payroll Periods'.
Please note that the 'source ID'
(report parameter) required for the 'Generate Posting Date for
Payroll Period' step does not exist for the majority of countries
for the payroll periods that have already been generated. To avoid
inconsistencies during regeneration, we strongly recommend that you
do not regenerate existing payroll periods to obtain a similar
11. In the 'Create Posting Variants'
step, please create appropriate posting variants using the values
entered in the selection screen for 'Transfer to FI/CO' (report
RPCIPO00). These variants must be specified when you perform the
'Execute Run' step (report RPCIPE00).
12. If you used to start 'Transfer to
FI/CO' (report RPCIPO00) using variants, please create appropriate
variants for the 'Execute Run' step (report RPCIPE00). To do this,
perform the 'Create Report Variants' step to create variants on the
basis of those created for 'Transfer to FI/CO' (report
13. If you generated datasets for
further evaluations for your country in the 'Prepare Evaluation'
step, please delete the processing steps relevant to posting and
the steps for providing data to cost planning in your evaluation
14. If you need to export data for a
transfer to R/2 or to an R/3 System < 4.0, please enter the
relevant company codes in the 'Set Up Export to R/2 System or R/3
System < 4.0' step.
You can check the accuracy of the
steps by simulating evaluations of previous payroll periods and
then comparing the results with the posted documents or with the
paper documents created at that time.