Do you have any question about this error?
Message type: E = Error
Message class: KI -
Message number: 099
Message text: Account assignment objects have differing company codes
You entered several account assignment objects which are assigned to
different company codes. In a posting row, however, all account
assignment objects for which a company code assignment is maintained
must be assigned to the same company code.
Check and change the given account assignment objects. The following
company codes were assigned to or otherwise determined:
Company Code Type Object
&V1&
&V2&
&V3&
&v4&
If you want to permit postings in CO to account assignment objects
belonging to different company codes. In Customizing, you can prevent
this message from appearing it or change it from an error message to a
warning or a note. To do so, in the "General Controlling" section of
the Implementation Guide (IMG) choose
<DS:SIMG.SIMG_CFMENUORK3OBA5>"Change Message Control"</> (work area
"KI", message number "099").
Error message extract from SAP system. Copyright SAP SE.
KI099
- Account assignment objects have differing company codes ?The SAP error message KI099, which states "Account assignment objects have differing company codes," typically occurs in the context of controlling (CO) when you are trying to post a transaction that involves multiple account assignment objects (like cost centers, internal orders, etc.) that belong to different company codes. This is not allowed in SAP because each company code is treated as a separate legal entity, and transactions must be consistent within the same company code.
Cause:
The error is triggered when:
- You are trying to post a transaction that involves multiple account assignment objects (e.g., cost centers, internal orders) that belong to different company codes.
- The configuration of the account assignment objects is inconsistent, leading to a mismatch in company codes.
Solution:
To resolve the KI099 error, you can take the following steps:
Check Account Assignment Objects:
- Review the account assignment objects you are using in your transaction. Ensure that all objects (e.g., cost centers, internal orders) belong to the same company code.
Correct the Company Code:
- If you find that some of the account assignment objects are assigned to different company codes, you will need to either:
- Change the account assignment objects to ensure they all belong to the same company code.
- Split the transaction into separate postings for each company code if they must remain separate.
Review Configuration:
- If you are unsure about the company code assignments, you can check the configuration in the SAP system:
- For cost centers, navigate to Controlling (CO) > Cost Center Accounting > Master Data > Cost Center > Change and verify the company code.
- For internal orders, navigate to Controlling (CO) > Internal Orders > Master Data > Order > Change and check the company code.
Consult Documentation:
- If you are still facing issues, refer to SAP documentation or consult with your SAP support team for further assistance.
Related Information:
KS03
(Display Cost Center) or KO03
(Display Internal Order) to check the details of the account assignment objects.By following these steps, you should be able to identify the cause of the KI099 error and implement a solution to resolve it.
Get instant SAP help. Start your 7-day free trial now.
KI098
Balance sheet account & cannot be created as a cost element
INCLUDE KS036 OBJECT DOKU ID NA LANGUAGE ENHow to fix this error? Deactivate message <ZH>KI098</>. To do so, in Customizing choose <L...
KI097
Cost element for balance sheet account cannot be posted to &
What causes this issue? You are posting to a balance sheet account that is created in Controlling (CO) as a statistical cost element (<DS:DE.KATYP...
KI100
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 ...
KI101
Controlling area & does not exist
What causes this issue? Controlling area &V1& does not exist.System Response Without a valid controlling area you cannot continue processing...
Click on this link to search all SAP messages.