SAP Knowledge Base Article - Public

3713678 - Document Splitting Inheritance logic in Public Cloud

Symptom

As part of the document splitting process sometimes the system cannot determine the account assignments of the document splitting characteristics for individual line items. In this case, the account assignments are may be determined via inheritance.

"Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental." 

Resolution

Inheritance of Account Assignments transfers the account assignments which are defined as split criteria. 

The values of the split criteria are always taken into consideration together as a combination of the account assignments. The field values are inherited only in case the account assignment combination is unique within the complete document. That means the account assignments are being inherited if the values of the split criteria in the complete document are the same.


Only account assignments relevant for the balance sheet (g/l split criteria) are taken over since it is rather a fallback mechanism for the unassgined processes. 

Examples:

In the Define Document Splitting Characteristics for General Ledger Accounting configuration activity, you can view and define document splitting characteristics.

The following characteristics are set:

 

Characteristics

Zero Balance

Partner Field

Mandatory

Profit Center

Not Selected

PPRCTR

Not Selected

Segment

Selected

PSEGMENT

Selected



Example 1

Journal Entry

Entry View: Document type SA: Derived business transaction variant 0000 (unspecified posting) 

Account assignment for Profit Center YB110 Segment 1000_A  in the document is unique. Profit Center YB110 Segment 1000_A  is inherited into item 2 in the Ledger View.




Example 2:

A Journal Entry is created with the following lines

Entry View




Ledger View 



If field B (Segment) is set with the default value of the account assignment and field A (Profit Center) is not filled, the Inheritance fills the value of field A.

Inheritance takes place in this example as the assignment of the line which inherits the assignment string has the same value as in the assignment string itself.

Example 3

A Journal Entry is created with the following lines

Entry View






Ledger View




Inheritance cannot work in this example as there is not a unique account assignment string. Inheritance will only work if the account assignment values are unique within the document.  The values of the split criteria are always taken into consideration together as a combination of the account assignments.  

See also kba 2810442 - Substitutions and Document Splitting

Never set a proposal account assignment characteristic in accounts in which an account assignment by document splitting is expected, this principle applies to all account assignments which you expect to be filled via rule base split, inheritance or constant.

Inheritance logic on partner account assignments

In the example configuration shown for the split criteria the field Zero balance is selected for the Segment and Partner Segment. The Zero balance field is not selected for the Profit Center and Partner Profit Center. 

The partner fields are only considered as part of the inheritance logic if the document splitting characteristic is marked as zero balance.

Entry view

 

Ledger view
No partner profit center is inherited as the profit center is not defined as a zero balance characteristic.  Partner Segment is inherited into the second line item. 



Further principles in relation to inheritance:

Inheritance via clearing: 

Automatic split for clearing processes

For clearing lines, the account assignments are derived by referring to the original line items to be cleared. During the automatic splitting, only the cleared items of the original documents are considered in order derive the relevant account assignments for the clearing lines and to split the line accordingly if necessary. If a clearing line contains a different account assignment in the entry view (which normally should not happen in the standard) it will be overwritten by the account assignments from the cleared items. This logic is followed in order to make sure that the whole clearing process does balance to zero also on the account assignment level.   

Inheritance via invoice reference:

If a document is posted with an invoice reference in fields Invoice Reference (REBZG), Invoice Reference Fiscal Year (REBZJ,), Journal Entry Line Item Reference (REBZZ), this is referring to the cleared items. Hence document splitting can derive the account assignments in the Ledger view of the residual items by using document splitting information of the referred item as base items, i.e. split the residual items by the same ratio of amounts per account assignment values.

Only items with the following values of Follow-On Document Type (REBZT) (and with a valid Invoice Reference (REBZG)) are always split via invoice reference regardless any other condition: A P V Z U O W T C Q

For example :

    • residual items posted to the same G/L account
    • down payment clearing

Unlike to "inheritance via clearing" the "inheritance via invoice reference" doe not overwrite account assignments from the entry view.

Inheritance during FI reversal

The account assignments in the reversal document should be the same as in the reversed document. If there were initial account assignments in the reversed document, these should also remain initial in the reversal document and should not be filled through inheritance.

See Also

Document Splitting

3662230 - Segment and Profit Center Constants within a two-step Bank Statement posting 


Keywords

KBA , FI-GL-FL-2CL , Flexible Structures (Public Cloud) , How To

Product

SAP S/4HANA Cloud Public Edition all versions

Attachments

Pasted image.png