3791825 - EBRR Posting Does Not Include Trading Partner Information - SAP S/4HANA Cloud Public Edition

• An expense is posted via the Upload Journal Entry App on a project with a trading partner assigned.
• Revenue recognition documents do not contain trading partner information.

SAP S/4HANA Cloud Public Edition

1. Post an expense via the Upload Journal Entry App on a project with a trading partner assigned.
2. Trigger EBRR posting
3. Observe that the revenue recognition documents do not contain trading partner information.

EBRR does not read the trading partner from the original document. Architecturally, EBRR derives all account assignment characteristics exclusively from its own master data objects (sales order item, WBS element, service contract, etc.) and from the associated customer master records.

The trading partner represents the company that is the counterparty to the transaction from a group consolidation perspective. This is a characteristic of the customer relationship, not of an individual billing document. In SAP S/4HANA, the trading partner must be maintained on the sold-to customer master, as this is the architecturally correct location for this information.

The trading partner field (VBUND) on the original document may reflect a different intercompany layer (for example, a purchasing company code) that is not the same as the revenue recognition counterparty. EBRR intentionally ignores the VBUND field on the original document to maintain a clean and consistent derivation, independent of the billing document structure. This behavior is by design.

EBRR posting, trading partner , KBA , CO-PC-OBJ-EBR-2CL , Event-Based Revenue Recognition (Public Cloud) , Problem