SAP Note 28508 - Order settlement and IBVE in reconcil.ledger

Symptom:

After order settlement, cost flows from internal activity allocation (IAA) are revealed between company codes in the reconciliation ledger which do not correspond to the initial posting (IAA for the order) or to the situation after settlement (exchange of services between cost centers).
See the following example!

Cause and prerequisites

Example:
IAA posting from cost center 1 (in company code 1)
to order 2 (in company code 2)
Order settlement from order 2 (in company code 2)
to cost center 3 (in company code 3)
What are the cost flows from the point of view of the reconciliation ledger?
Which reconciliation postings should therefore be generated?
How must the reconciliation reports and the object-specific reports be defined to represent consistent values?
How are postings made in 3.0FCS and 3.0A (and 2.2) ?
Postings in CO: Cost flows: ILV: 610000 OR2 KS1 S RKL 50.- 1->2 50.- (1)
610000 KS1 OR2 H RKL -50.- 2->1 -50.- (2)
AA: 650000 KS3 OR2 S KOAO 50.- 2->3 50.- (3)
650000 OR2 KS3 H KOAO -50.- 3->2 -50.- (4)
610000 KS1 OR2 H KOAO 50.- 2->1 50.- (5)
610000 KS1 KS3 H KOAO -50.- 3->1 -50.- (6)
Views of the individual company codes: Company code 3: 2->3 50,-
Company code 2: 1->2 50,-
2->3 50,-
Company code 1: 1 ->3 50,-
---> The statements in the company codes are contradictory !

Solution
The correction records from the order settlement (to eliminate internal business volumes in cost center reports) are written under a separate value type.
The CO data from 2.2 cannot be converted (affects totals records and line items). Therefore, the COSS records available from 2.2 must be skipped explicitly when determining the reconciliation postings or when restructuring the reconciliation ledger.
This way, the reconciliation ledger has no knowledge of the adjustment postings and, consequently, the reconciliation reports cannot eliminate the internal business volume from total business, which has the result that the branch reports should also be defined without IBVE.
To do this in 'normal' reporting, the new value type must be read internally for reports with IBVE.
Reports without IBVE can skip the new value type.
Note: The data selection of the Report Writer is defined by the report group. The new value type must, therefore, also be read if at least one report is defined with IBVE a report group.

Additional key words

Internal business volume elimination
reconciliation ledger