Mickael QUESNOT ©

Business transaction cannot be processed by consolidation in SAP

Message no. F5583

Diagnosis

You enter an intercompany business transaction and at the same time post to an account which
represents an affiliated company. Such business transactions cannot be edited correctly by
consolidation.

System Response

You receive a warning message during entry. You receive a corresponding error message when trying
to post the document.

Procedure

You have to divide the transaction into two documents or use a document type which allows a cross-
company posting.

Mickaël QUESNOT © https://www.linkedin.com/in/mickaelquesnot/

SAP SCM & Cloud Solutions (Concur, EnableNow)

1|P a g e
Mickael QUESNOT ©

You park a document using an EnjoySAP transaction. You then add a G/L account line in another
company code to the document. The system issues warning message F5 583:

'Business transaction cannot be processed by consolidation'.

You post the document.

An update termination occurs within the update module POST_DOCUMENT and error message F1 105
appears:

'Document & & already exists in company code &'.

Other Terms

FV60, FV70, FV50, XBKPF, BKPF, BELNR, POST_DOCUMENT, F1 105, F1105, 105(F1), XMGES, XGSUB,
T003, VBUND, F5 583, F5583, 583(F5), cross-company code

Prerequisites

You parked the document with a document type that does not allow XGSUB (cross-company posting).
There is a trading partner in at least one line item.

Postings are made to more than one company code.

Mickaël QUESNOT © https://www.linkedin.com/in/mickaelquesnot/

SAP SCM & Cloud Solutions (Concur, EnableNow)

2|P a g e
Mickael QUESNOT ©

Mickaël QUESNOT © https://www.linkedin.com/in/mickaelquesnot/

SAP SCM & Cloud Solutions (Concur, EnableNow)

3|P a g e
Mickael QUESNOT ©

Inter-Company Posting

Indicator that is set at the document type level. It defines within a document that account assignment
can be cross-company. Cross-company means:

• Accounts are assigned to multiple trading partners.

• Accounts are assigned to one or more trading partners and one group-external business
partner.

It follows that the trading partner for each document is not unique. The company ID defined in the
master record for this affiliated business partner cannot be transferred to all line items.

Use

Do not set the indicator in the following cases:

• The partner company is to be inherited in all line items.

Transference of the trading partner is mainly required for consolidation purposes, since the
system requires this information on the trading partner when making elimination postings. An
exception to this transfer logic occurs if you post company code clearing items to an affiliated
company.

• You want to enter asset postings with this document type.

Mickaël QUESNOT © https://www.linkedin.com/in/mickaelquesnot/

SAP SCM & Cloud Solutions (Concur, EnableNow)

4|P a g e
Mickael QUESNOT ©

Set the indicator in the following cases:

• For business transactions where account assignment is to take place on an inter-company

basis.

This is especially true of adjustment postings (see example) and postings that have no effect
on sales (for example, automatic payments).
Example

In the following case, it may be necessary to set this indicator:

Problems can arise in payment transactions if a vendor or a customer has changed its status, for
example from a non-affiliated to an affiliated company. In the case of simultaneous payment of old
and new items, the trading partner in the document is no longer unique. The document type must
therefore allow cross-company posting.

Bd87

Mickaël QUESNOT © https://www.linkedin.com/in/mickaelquesnot/

SAP SCM & Cloud Solutions (Concur, EnableNow)

5|P a g e
Mickael QUESNOT ©

Mickaël QUESNOT © https://www.linkedin.com/in/mickaelquesnot/

SAP SCM & Cloud Solutions (Concur, EnableNow)

6|P a g e
Mickael QUESNOT ©

Mickaël QUESNOT © https://www.linkedin.com/in/mickaelquesnot/

SAP SCM & Cloud Solutions (Concur, EnableNow)

7|P a g e
Mickael QUESNOT ©

Mickaël QUESNOT © https://www.linkedin.com/in/mickaelquesnot/

SAP SCM & Cloud Solutions (Concur, EnableNow)

8|P a g e
Mickael QUESNOT ©

Mickaël QUESNOT © https://www.linkedin.com/in/mickaelquesnot/

SAP SCM & Cloud Solutions (Concur, EnableNow)

9|P a g e
Mickael QUESNOT ©

Mickaël QUESNOT © https://www.linkedin.com/in/mickaelquesnot/

SAP SCM & Cloud Solutions (Concur, EnableNow)

10 | P a g e
Mickael QUESNOT ©

Mickaël QUESNOT © https://www.linkedin.com/in/mickaelquesnot/

SAP SCM & Cloud Solutions (Concur, EnableNow)

11 | P a g e