Skip to Content
author's profile photo Former Member
Former Member

Business transaction can not be processed by consolidation message no f5583

Hi

when i try to process F-30 transcation i got the error as Business transaction can not be processed by consolidation message no f5583

Business transaction cannot be processed by consolidation

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.

please do needful.

regards

jay

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

3 Answers

  • Posted on Jun 28, 2011 at 02:34 PM

    Check the following notes:-

    1) Note 364589 - F5583 - consolidation Error

    2) Note 377349 - Error F5583 w/cross-company code posting

    thanks

    G. Lakshmipathi

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Jun 28, 2011 at 03:28 PM

    Dear,

    Which document type you are using for posting in F-30, please check out the configuration of this document type in OBA7 and check if inter company posting and trading partner is checked. You can use a document type with characteristics as mentioned above for cross company posting. Please check and revert back.

    Regards

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Jun 28, 2011 at 09:12 PM

    Hi Jay,

    Please kindly review the logic of the trading partner fillment agian:

    For cross-company code postings, the trading partners (BSEG-VBUND) in the company code clearing line items are determined as following:

    In the company code clearing line items of the receiving company codes, the trading partner (BSEG-VBUND) is filled with the company (-> T001-RCOMP) of the leading company code.

    And in the company code clearing line items of the leading company code, the trading partner is filled with the company (-> T001-RCOMP) of the receiving company code (-> in the company code clearing line items BSEG-VBUND is filled with the company of the other company code).

    This is the standard logic. A problem can occur if one of the company code clearing accounts contains a trading partner in its master data (-> customer master data: KNA1-VBUND; vendor master data: LFA1-VBUND):

    In this case first the trading partner contained in the master data of the company code clearing account (-> customer master data:

    KNA1-VBUND; vendor master data: LFA1-VBUND) is copied to BSEG-VBUND of the corresponding company code clearing line item, and later the system tries to copy the company (T001-RCOMP) of the other company code (-> as described above) to BSEG-VBUND of the corresponding company code clearing line item. If the trading partner in the master data of the company code clearing account is not the same like the company (-> T001-RCOMP) of the other company code, error message F5 583 is raised.

    Please go trough your customising according the above info. Also, please review the SAP Note No. 779844 for additional information.

    I believe this will hel you with this error.

    Best Regards,

    Vanessa.

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.