How To Fix KI113 - Cross-company-code purchasing is not allowed

SAP Error Message - Details

• Message type: E = Error

• Message class: KI -

• Message number: 113

• Message text: Cross-company-code purchasing is not allowed

What causes this issue?

You want to create an order for &V1& &V2&. This account assignment
object is assigned to company code &V3&. But you are creating the order
for company code &V4&.

System Response

Cross-company orders are only possible under the following conditions:
You carry out invoice verification using the Logistics function <LS>
Logistics -> Materials Management -> Invoice Verification -> Logistics
Invoice Verification</>.
The G/L accounts needed for purchasing are set up in all the company
codes involved.
The tax codes required for purchasing must be set up in all the company
codes involved.

How to fix this error?

If these conditions are met, you can deactivate this error message.
In Customizing for <LS>General Controlling</>, use the activity
<DS:SIMG.SIMG_CFMENUORK3OBA5.DC89C19F0599D211AE6200A0C9EAD00F>Change
Message Control</> (application area KI, message number 113) for this
purpose.
Postings that lead to a subsequent debit of the account assignment
objects are rejected with an error message in this case.
If the restrictions specified are <ZH>not</> met, you can only order for
objects that are assigned to company code &V4&.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message KI113 - Cross-company-code purchasing is not allowed ?

  The SAP error message KI113, which states "Cross-company-code purchasing is not allowed," typically occurs in the context of controlling and financial transactions when a purchase order or related document is created that involves multiple company codes. This error indicates that the system is configured to prevent cross-company-code transactions for purchasing activities.
  Cause:
  
  Configuration Settings: The primary cause of this error is the configuration settings in the SAP system that restrict cross-company-code purchasing. This is often set up to ensure that financial transactions remain within the same company code for accounting and reporting purposes.
  Purchase Order Setup: If a purchase order is created that references materials or services from different company codes, the system will trigger this error.
  Master Data Issues: The vendor or material master data may be set up in a way that does not allow for cross-company-code transactions.
  
  Solution:
  To resolve the KI113 error, you can consider the following steps:
  
  
  Check Configuration:
  
  Navigate to the configuration settings in the SAP system (Transaction SPRO).
  Go to Materials Management > Purchasing > Purchase Order > Set Up Cross-Company Code Purchasing.
  Ensure that the settings allow for cross-company-code purchasing if that is a requirement for your business processes.
  
  
  
  Review Purchase Order:
  
  Check the purchase order details to ensure that all line items belong to the same company code.
  If necessary, create separate purchase orders for each company code involved.
  
  
  
  Vendor Master Data:
  
  Verify the vendor master data to ensure that the vendor is set up correctly for the relevant company codes.
  If the vendor is supposed to be used across multiple company codes, ensure that the vendor master is maintained for each company code.
  
  
  
  Consult with Finance/Controlling Team:
  
  If you are unsure about the configuration or the business process, consult with your finance or controlling team to understand the implications of allowing cross-company-code purchasing.
  
  
  
  Testing:
  
  After making any changes, conduct thorough testing to ensure that the error is resolved and that the purchasing process works as intended.
  
  
  
  Related Information:
  
  Documentation: Refer to SAP Help documentation for detailed information on purchasing and company code settings.
  Transaction Codes: Familiarize yourself with relevant transaction codes such as ME21N (Create Purchase Order), ME22N (Change Purchase Order), and ME23N (Display Purchase Order) to troubleshoot and manage purchase orders effectively.
  User Exits and BAdIs: In some cases, custom logic may be implemented through user exits or BAdIs that could affect purchasing behavior. Review any custom developments if applicable.
  
  By following these steps, you should be able to address the KI113 error and facilitate the necessary purchasing processes within your SAP environment.