How To Fix CRM_APO_I400 - Different company code detected; check ATP settings

SAP Error Message - Details

• Message type: E = Error

• Message class: CRM_APO_I - Messages for APO_I

• Message number: 400

• Message text: Different company code detected; check ATP settings

What causes this issue?

The consolidation location and purchasing location of the third-party
orders must be in the same company code. However, the company code of
the sales location can differ from the company code of the purchasing
location.
In the current order, the purchasing location &V1& belongs to company
code &V2&, and the consolidation location &V3& belongs to company code
&V4&.

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

System Response

System cannot process the order.

How to fix this error?

In the ATP settings, ensure that the determined consolidation location
and purchasing location belong to the same company code.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message CRM_APO_I400 - Different company code detected; check ATP settings ?

  The SAP error message "CRM_APO_I400 Different company code detected; check ATP settings" typically occurs in the context of Advanced Planning and Optimization (APO) when there is a mismatch in company codes between the sales order in the CRM system and the stock or availability check in the APO system. This can happen during the availability check (ATP check) when the system tries to determine if the requested product is available for the specified company code.
  Cause:
  
  Different Company Codes: The most common cause of this error is that the sales order in the CRM system is associated with a different company code than the one configured in the APO system for the product being checked.
  Configuration Issues: There may be configuration issues in the integration settings between CRM and APO, particularly in the settings related to ATP (Available to Promise).
  Master Data Issues: The material master data or the customer master data may not be correctly set up for the relevant company codes.
  
  Solution:
  
  
  Check Company Code Settings:
  
  Verify that the company code in the sales order matches the company code in the APO system. You can do this by checking the sales order details in CRM and the corresponding material master in APO.
  
  
  
  Review ATP Configuration:
  
  Go to the configuration settings in SAP and check the ATP settings for the relevant product. Ensure that the settings are correctly defined for the company codes involved.
  Check the configuration in transaction code SPRO under the path: 
  SAP Customizing Implementation Guide -> Advanced Planning and Optimization -> Global Settings -> Check ATP Settings
  
  
  
  
  Material and Customer Master Data:
  
  Ensure that the material master data is correctly maintained for the relevant company codes. You can check this in transaction MM03.
  Similarly, check the customer master data in transaction XD03 to ensure it is correctly assigned to the appropriate company code.
  
  
  
  Integration Settings:
  
  Review the integration settings between CRM and APO. Ensure that the settings for the relevant company codes are correctly configured in the integration model.
  
  
  
  Testing:
  
  After making the necessary adjustments, perform a test by creating a new sales order to see if the error persists.
  
  
  
  Related Information:
  
  Transaction Codes:
  
  MM03: Display Material Master
  XD03: Display Customer Master
  SPRO: Customizing Implementation Guide
  
  
  Documentation: Refer to SAP Help documentation for detailed guidance on ATP settings and integration between CRM and APO.
  SAP Notes: Check for any relevant SAP Notes that may address specific issues related to this error message.
  
  If the issue persists after following these steps, it may be beneficial to consult with your SAP Basis or functional team for further investigation, as there may be deeper integration or configuration issues at play.