Skip to Content

SAP Note 1039346 – Q&A: RCIPE00/RPCIPE01 – distribution of

liabilities

Summary

Symptom

As of SAP Release ECC 6.0 (ERP 2005), the evaluation for the posting of

payroll to accounting was adjusted to the current legal requirements by the

International Financial Reporting Standards (IFRS).

There are questions concerning the posting of payroll

as of Release ECC 6.0, which were not dealt with in the documentation or

were not dealt with in enough detail.

Other terms

PCP0, RPCIPE00, RPCIPX00, RPCIPI00, RPCIPA00, RPCIPS00, RPCIPD00,

RPCIPP00, RPCIPB00, RPCIPT00, RPDKON00, RPCIPC00, RPCIPF00, RPCIPL00,

RPCIPM00, RPCIPQ00, RPCIPR00, RPAR4D00, RPAR4W00, RPAR6D00, RPAR6W00,

RW interface

Reason and Prerequisites

This note contains questions and answers about the process and about

posting payroll to accounting as of Release ECC 6.0. The questions concern

HCM and FI/CO settings. See also Note 1091802.

See the component FI-GL-GL-A for problems regarding the update in Financial

Accounting. For problems concerning account assignments or document

breakdown see the component FI-GL-FL.

See Note 1024468: This note must be implemented

(component AC-INT).

! This note may be updated at any time by SAP.

! Generally, path descriptions are not adjusted when changes are made.

Solution

Question 1: Which posting report can you use with which function

in Release EC 6.0?

Answer 1: In ECC 6.0 the following reports are available:

1. RPCIPE00 (run type PP):

a) Posting of payroll

b) Posting of payroll with CE (Concurrent Employment)

c) Posting when using new General Ledger Accounting with the payroll

function XCODI

2. H99_POST_PAYMENT (run type PM):

04.04.2013 Page 2 of 10

SAP Note 1039346 – Q&A: RCIPE00/RPCIPE01 – distribution of

liabilities

a) Posting of payment

b) Posting of payment with CE (Concurrent Employment)

c) Posting when using new General Ledger Accounting with the payroll

function XCODI

3. RPCIPE01 (depending on the posting variant used for run

types PP and PM):

a) Posting of payroll with run type PP

b) Posting of payment with run type PM

c) Posting when using new General Ledger Accounting with the payroll

function XLIDI

The payroll function XLIDI is currently not released.

For information about this, see Note 1276746 and following.

4. RPCIPE01CE (depending on the posting variant used for run

types PP and PM):

a) Posting of payroll with CE (Concurrent Employment) with run type PP

b) Posting of payment with CE with run type PM

c) Posting when using new General Ledger Accounting with the payroll

function XLIDI

The payroll function XLIDI is currently not released.

For information about this, see Note 1276746 and following.

If you do not use new General Ledger Accounting (function XLIDI), you can

use the report RPCIPE01CE for the following settings:

– Setting 0 (No distribution of liabilities):

– Setting 1 (distribution of liabilities according to infotype 0001)

For more information about the settings, see question 2.

5. RPCIPE00_OLD

Posting of payroll without new General Ledger Accounting This

corresponds to the setting 0 (no distribution of liabilities

according to expenses) in the table T52SWCODIST.

6. RPCIPE00_OLD_CE

Posting of payroll with CE without new General Ledger Accounting

This corresponds to the setting 0 (no distribution of liabilities

according to expenses) in the table T52SWCODIST.

04.04.2013 Page 3 of 10

SAP Note 1039346 – Q&A: RCIPE00/RPCIPE01 – distribution of

liabilities

Question 2:

Which setting for cost distribution in Customizing for payroll under

Payroll (country) -> Posting to Accounting -> Possible Solutions for New

G/L Accounting -> Define Distribution Type (the V_T52SWCODIST table) has

what effects on setting account assignment information in which line items?

Which setting applies to which posting report?

Answer 2:

a) Setting 0 (No distribution of liabilities):

Posting is carried out according to the old posting logic. The

expense items only contain derived account assignment information

such as profit center or segment. NO account assignment or

distribution of liabilities according to expenses takes place. A

zero balance is NOT set for each account assignment in HCM.

The setting applies to:

-RPCIPE00_OLD, RPCIPE00_OLD_CE

-RPCIPE00

-RPCIPE01, RPCIPE01CE

b) Setting 1 (distribution of liabilities according to infotype 0001):

The expense items contain derived account assignment information

such as profit center or segment from all infotypes. The liability

items are assigned to account according to the master cost center

from infotype 0001 (the table WPBP of the payroll). The system sets

a zero balance based on the Customizing settings under the

following path: Financial Accounting (new) -> General Ledger

Accounting (new) -> Business Transactions -> Document Splitting ->

Define Document Splitting Characteristics for General Ledger

Accounting (the table V_FAGL_SPLIT_FLD).

The setting applies to:

-RPCIPE00

-RPCIPE01, RPCIPE01CE

c) Setting 2 (distribution of liabilities according to expenses):

In addition to setting 1, there is a distribution of liabilities

from all infotypes according to expenses.

Posting using the report RPCIPE00

The wage types are distributed according to their grouping in the

table V_T52SWCODIST in accordance with the payroll table CODIST.

For setting 2, you have to use account assignment type FC for the

type balance sheet account. You then also have to define the wage

04.04.2013 Page 4 of 10

SAP Note 1039346 – Q&A: RCIPE00/RPCIPE01 – distribution of

liabilities

type posting characteristics accordingly.

The balance is set to zero based on the settings of the table

V_FAGL_SPLIT_FLD.

Posting using the report RPCIPE01, RPCIPE01CE

Activate cost distribution using the function XLIDI:

This function executes the distribution of liabilities according to

expenses already during the payroll run, and saves it in the

payroll table LIDI. During the posting run, the wage types that are

in the table LIDI are read from this and evaluated. All other wage

types are read from the table RT and evaluated, as previously.

The setting applies to:

-RPCIPE00

-RPCIPE01, RPCIPE01CE

d) Setting 3 (distribution of liabilities with inflow principle

according to expenses):

In addition to setting 2, there is a distribution of liabilities

with inflow principle from all infotypes according to expenses. For

setting 3, you have to use account assignment type FC for the type

balance sheet account. You then also have to define the wage type

posting characteristics accordingly. The balance is set to zero

based on the settings of the table V_FAGL_SPLIT_FLD.

The setting applies to:

-RPCIPE01, RPCIPE01CE

For more information about setting 3, see Notes 1137192 and

1276746, as well as the documentation for the payroll function

XLIDI.

For further information about the new general ledger function see SAP

Library (http://help.sap.com/) under the following path: Payroll Other

Countries -> Subsequent Activities -> Posting to Accounting -> Special

Business Requirements for Posting -> New General Ledger or in the SAP

Implementation Guide under Payroll: International -> Reporting for Posting

Payroll Results to Accounting -> New General Ledger: Distribution of

Liabilities According to Expenses.

Question 3:

In which countries is the “Distribution of liabilities according to

expenses” function released?

Answer 3:

Note that the function for the distribution of liabilities according to

expenses using the report RPCIPE00 is currently released only for the USA,

Germany and Switzerland.

04.04.2013 Page 5 of 10

SAP Note 1039346 – Q&A: RCIPE00/RPCIPE01 – distribution of

liabilities

Question 4:

For which entities are clearings and zero balance settings executed?

Answer 4:

Profit center, segment, business area, fund, grant

These entities are supplied in liability items.

Question 5:

How is the business area dealt with according to the settings in the table

V_FAGL_SPLIT_FLD?

Answer 5:

As soon as the business area is entered in the table V_FAGL_SPLIT_FLD, it

is a split criterion in FI (Financial Accounting).

As soon as you activate a distribution in HCM, the business area is filled

in expense items and liability items.

There are exceptions for technical document split items in HCM:

e) The business area is a split criterion and is not balancing and is

not a required entry field:

The business area is not filled in the technical document split

items.

f) The business area is a split criterion and is not balancing but is

a required entry field:

The business area is not filled in the technical document split

items.

g) The business area is a split criterion and is balancing:

The business area is filled in the technical document split items.

h) The business area is not a split criterion:

It accesses the “old logic” (according to the program

RPCIPE00_OLD):

The business area is not filled in customer and vendor rows (see

Note 203276). The business area is filled in the technical document

split rows, and if necessary a zero balance setting is executed for

the business area.

Question 6:

Why are the partner account assignments not always filled in the (company

code) clearing items?

Answer 6:

The partner account assignments are only filled if they are different to

the original account assignments.

That is, if the partner account assignment is not filled, there is no

clearing for this account assignment.

Question 7:

When are company code clearing accounts used and when are zero balance

clearing accounts used?

04.04.2013 Page 6 of 10

SAP Note 1039346 – Q&A: RCIPE00/RPCIPE01 – distribution of

liabilities

Answer 7:

If a clearing takes place between different account assignments, the

company code clearing account is always used for different company codes.

It does not matter how many other account assignments perform clearing;

this means that the zero balance clearing accounts are used only if the

company code is the same as the partner company code (that is, clearing

within the company code). The profit center is always created at

controlling area level (also see Note 826357).

If you use the distribution of liabilities, note that the profit centers

must be known in all company codes involved.

Question 8:

– In HCM, there is no active split of liabilities according to account

assignments (setting in the table V_T52SWCODIST is blank or 0). The

payables in FI are split using the document breakdown in FI, or (in HR or

payroll) there is retroactive accounting in periods in which the document

breakdown of General Ledger Accounting (new) was not active.

In these cases, are liabilities distributed correctly in Financial

Accounting?

Answer 8:

Create a constant or “enhancing constant” for the liabilities in the

document breakdown. If you intentionally leave out a field in the constant

definition, it is called an “enhancing constant”. When you set default

values from the constant, the defined fields are always considered to be a

combination, in other words, either all the account assignments are set or

none whatsoever are set. See Notes 824023, 1050082, 1069568 and 1072047 for

the full range of functions of the enhancing constants.

You must make the following settings:

– Define a constant in Customizing for Financial Accounting (new) ->

General Ledger Accounting (new) -> Business Transactions -> Document

Splitting -> Edit Constants for Nonassigned Processes.

– Assigning the constants for the relevant “Items categories to be edited”

(transaction GSP_RD)

Example for relevant item categories:

– Creditors (03000)

– Expenses (30000)

– Liabilities/Balance Sheet Accounts (01000)

– Tax (05100)

Comment: If the required field check is active in the document breakdown,

all line types found in posting documents must occur as item categories to

be edited in the relevant business transaction variant.

– Assign the business transaction variant to the document type, with which

the HCM documents are posted in FI.

If the business area (field GSBER) is used as a split criterion in the

document breakdown and business area financial statements are activated for

the relevant company code (transaction OB65), note the following: In

the constant that is to be defined, the business area field must remain

initial because this could also be set by FI when the setting is 0 (table

T52SWCODIST in HR).

If the business area is defined as a required field and the business area

is not set in all lines of the business area derivation, it is possible to

04.04.2013 Page 7 of 10

SAP Note 1039346 – Q&A: RCIPE00/RPCIPE01 – distribution of

liabilities

define a general constant (table fagl_activec) solely for the business

area. Alternatively, you can use the FI substitution (transaction OBBH)

to fill the business area.

Question 9:

The system issues error message GLT2 201 with the text: “Balancing field

“&1″ in line item &2 not filled”.

Answer 9:

New general ledger accounting is active in Financial Accounting. The

document breakdown is also active and the characteristic referred to in the

error message is set as a required entry field. At the time of the check

the information about the characteristic does not yet exist.

If the distribution of liabilities (distribution according to infotype 0001

or distribution off liabilities according to expenses in the table

T52SWCODIST) is not set in HCM, the error message can be removed by setting

a distribution in the HCM. Alternatively, implement the settings as

described in question 8. If a distribution is set in HCM, the problem may

be caused by missing Customizing for the document breakdown.

Question 10:

For setting 1 or setting 2 (setting for cost distribution in Customizing

for payroll), what Customizing settings should be made for document

splitting in FI?

Answer 10:

If setting 1 or setting 2 is active, HCM generates financial statement

postings in the entry view in terms of further entities (for example,

profit center, segment, and so on). Business clearing lines (KTOSL HRF) are

created, which post to the zero balance clearing account of the account key

000 for document splitting.

In transaction gsp_lz2, an item category other than item category 01001 is

assigned to this zero-balance clearing account. A suitable item category is

one that is normally never posted from HCM, for example, 07000 or a

customer-specific item category. (01001 cannot be used due to the

reconciliation of the general ledger view with the entry view. The item

category 01001 is considered only as a technical zero balance of the

general ledger view, and is therefore not updated in the entry view).

The documents posted from HCM must be posted using a document type that is

assigned to the unspecified posting in transaction gsp_vz3. In transaction

gsp_rd, the variant used must define the company code clearing line (item

category 01100) as the only base row to be assigned, comparable to business

transaction variant 0000 0001.

Question 11:

You are in the production system of FI in the migration phase for the new

general ledger, and use the validation of the document breakdown.

In addition, (in HR) you plan to activate setting 1 (distribution of

liabilities according to infotype 0001) or setting 2 (distribution of

liabilities according to expense) in the table T52SWCODIST in the

production system of HR.

Which settings do I have to make in HR and FI Customizing?

Answer 11:

The new logic for the distribution of account assignments in HR

only takes effect when General Ledger Accounting (new) is activated in FI.

04.04.2013 Page 8 of 10

SAP Note 1039346 – Q&A: RCIPE00/RPCIPE01 – distribution of

liabilities

However, this is not the case in the migration phase.

You have two options for the migration phase (“transition period”):

a) After you implement the corrections from Note 1137981 (component

FI-GL-FL), you can set switch 1 or switch 2 in HR in the table

T52SWCODIST. You must take care to leave the productive system

settings in FI as they are in the test system where you already

tested General Ledger Accounting (new). For retroactive accounting

in “old” periods in which General Ledger Accounting (new) was not

yet active, you must create a constant as described under point 7.

b) You use the setting 0 (that is, no distribution of payables

according to infotype 0001 and no expense-related distribution) in

HR as long as General Ledger Accounting (new) is not active in FI.

Therefore, you must create a constant, as described in point 7. In

addition, for the payables accounts, you must leave or enter

account assignment type F in setting 0.

If migration in FI is complete, the switches in HR (setting 1 or 2

according to T52SWCODIST) and the switch for General Ledger

Accounting (new) in FI can be activated simultaneously. Keep in

mind that the account assignment type FC must also be coded for the

payables in Customizing for HR if you choose setting 2 for the

expense-related distribution of payables.

Caution: It is not possible to retroactively convert to setting 0

in HR if you already activated setting 1 or 2 and have already

productively generated HR documents. This is because retroactive

accounting can be performed for posting runs already generated in

periods with setting 1 or 2 where the account assignment

information was also filled in the payable items. However, this is

not the case for setting 0. This can cause errors in the documents.

Question 12:

Document splitting is active in FI. When you post a payroll run in HR, the

system issues the runtime error SV_TNEW_PAGE_ALLOC_FAILED. Alternatively,

another symptom may be that performance problems occur.

Answer 12:

Check the business transaction variant for which the document type used in

HR is assigned in transaction GSP_VZ3. For the document types used in HR,

no business transaction variant that results in a rule-based distribution

must be assigned. That means that no distribution rules must be defined

for the business transaction variant used. For processing category 1, only

the standard variant 0000/0001 for the unspecified posting or your own

variant with a similar definition must be assigned. Alternatively, you can

define a constant for processing category 0, as already described under

question 8.

Question 13:

The system issues error message GLT2 201 “Balancing field “&1” in line item

&2 not filled” even though a constant was entered.

Answer 13:

Note that a document splitting characteristic (for example, profit center)

04.04.2013 Page 9 of 10

SAP Note 1039346 – Q&A: RCIPE00/RPCIPE01 – distribution of

liabilities

must not be flagged as a required entry field only, but the required entry

field must be analyzed only in connection with the zero balance

characteristic. For HCM postings, only characteristics that are defined as

financial statement characteristics are assigned to an account. In

Customizing, the required entry field indicator is not used to validate

that this field is filled, but the required entry field indicator is

defined as the additional attribute of a financial statement characteristic

that a financial statement must not contain any initial values.

In other words, it is correct to set the balancing indicator independently

of the required entry field indicator, but the required entry field

indicator is only analyzed depending on the balancing indicator.

Question 14:

The system issues error RW 602 “Required field GL_ACCOUNT was not

transferred in parameter ACCOUNTGL” when posting the payroll results to

Accounting using General Ledger Accounting (new).

Answer 14:

The error message for the failed account determination may mean that

different Customizing settings for document splitting apply for the

participating company codes in the FI receiver systems.

The same financial statement characteristics apply for all participating

company codes and New GL entities (for example, profit center and segment).

If there are company codes in different FI receiver systems, the same

Customizing prerequisites apply as those in an integrated scenario. If, for

example, the profit center and segment with a zero balance characteristic

and a required entry field are valid as criteria for company code A in FI

system 1, these must also be valid for company code B in FI system 2. In

this case, the profit center and segment entities must also be defined as

zero balance characteristics and required entry fields.

In a possible clearing scenario between entities, different Customizing

must not be set in document splitting because the relevant entities may not

be cleared correctly by the clearing otherwise.

For example:

An employee works proportionally in two different company codes A and B.

The HCM posting run generates postings for these different company codes

(in other words, there are receivables and payables between company codes A

and B). As a result, a cross-company-code process is posted in which the

postings must not only balance to zero at company code level, but it must

also be possible to generate a zero financial statement at Profit Center

Accounting level because it is selected as a financial statement

characteristic. However, to be able to generate a financial statement for

each profit center, each document must balance to zero for each profit

center. If, however, a cross-company code posting is made, this means that

the relevant account assignments must be available for each company code

and must balance to zero so that the zero balance clearing lines of the

single company code for which a profit center financial statement is

required can receive the relevant profit center account assignments and

partner account assignments in the company code clearing lines from the

other company code. Furthermore, zero balance clearing lines must be

generated with partner account assignments so that an elimination of

internal business volume is possible within the consolidated analysis.

See also Note 891144, which explains how subsequent changes to document

splitting are not permitted or may involve risks.

04.04.2013 Page 10 of 10

SAP Note 1039346 – Q&A: RCIPE00/RPCIPE01 – distribution of

liabilities

Header Data

Release Status: Released for Customer

Released on: 22.01.2013 09:56:52

Master Language: German

Priority: Recommendations/additional info

Category: FAQ

Primary Component: PY-XX-DT Posting

Secondary Components:

FI-GL-GL-A Posting/Clearing

Valid Releases

Software Component Release From

Release

To

Release

and

Subsequent

EA-HR 200 200 200

EA-HR 500 500 500

EA-HR 600 600 600

Related Notes

Number Short Text

1699381 Q&A – RPCIPE01/RPCIPE01CE

1628607 Document splitting: business process assigned in entry view

1577389 New General Ledger for South Africa

1576077 PY-TH New G/L

1567788 PY-ID New G/L

1567349 New General Ledger for Malaysia

1566813 New General Ledger for Philippines

1542629 New General Ledger for Non Profit Organizations

1502044 Enabling of New G/L for HR in New Zealand country version

1459529 RPCIPE01: Check of posted results

1276746 RPCIPE01, RPCIPE01CE: Additional changes

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply