How To Fix KI100 - The CO account assignment object belongs to company code &3, not &4

KI100 - Overview

• Message type: E = Error

• Message class: KI -

• Message number: 100

• Message text: The CO account assignment object belongs to company code &3, not &4

What causes this issue?

You want to make a posting in company code &V4&.
At the same time, a CO account assignment object was specified that is
assigned to company code &V3&.
This is account assignment object with <DS:DE.J_OBART3>object type</>
&V1&, and object key &V2&.

System Response

<DS:TX.COCODE_VALIDATION>Company code validation</> is active for
company code &V4&:
All account assignment objects in one posting row must be assigned to
the same company code.

How to fix this error?

You can
Make an assignment to company code &V3&.
Enter an account assignment object assigned to company code &V4&.
Change the assignment of object &V2& to company code &V3&. In this
case, you should note the document and edit it further after changing
the assignment.
If the posting is to a balance sheet account (category 90), you may
also decide whether to allow CO account assignment objects from other
company codes. If this is the case, deactivate the error message with
the IMG step <DS:SIMG.SIMG_CFMENUORK3OBA5>Change message control</>
(message ID "KI", message number 100).
You can set the following message types:
"-" Message is not sent
"W" Message is sent as a warning message
"E" Message is sent as an error message
Posting to cost elements of another category always results in the
message appearing as an error message, whether it has been deactivated
or not.
<DS:TRAN.OBA5>Execute "Change message control"</>

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message KI100 - The CO account assignment object belongs to company code &3, not &4 ?

  The SAP error message KI100 indicates that there is a mismatch between the company code associated with a cost object and the company code that is being used in the transaction. Specifically, the error message states that the cost object (such as a cost center, internal order, or project) belongs to one company code, but the transaction is being processed under a different company code.
  
  Cause:
  
  Company Code Mismatch: The cost object you are trying to use in your transaction is assigned to a different company code than the one you are currently working with.
  Incorrect Configuration: The configuration of the cost object may not be set up correctly, leading to the mismatch.
  Data Entry Error: There may be an error in the data entry where the wrong company code is being referenced.
  
  
  Solution:
  
  Verify Company Codes: Check the company code of the cost object you are trying to use. You can do this by navigating