How To Fix /ACCGO/EXM_EXPENSE068 - Purchase orders belong to different company code

SAP Error Message - Details

• Message type: E = Error

• Message class: /ACCGO/EXM_EXPENSE -

• Message number: 068

• Message text: Purchase orders belong to different company code

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message /ACCGO/EXM_EXPENSE068 - Purchase orders belong to different company code ?

  The SAP error message /ACCGO/EXM_EXPENSE068 indicates that there is an issue with the purchase orders being processed in a transaction where they belong to different company codes. This typically occurs in scenarios involving expense reports or when trying to post expenses that reference multiple purchase orders from different company codes.
  Cause:
  
  Different Company Codes: The primary cause of this error is that the purchase orders referenced in the transaction belong to different company codes. In SAP, each company code is treated as a separate legal entity, and transactions involving multiple company codes must adhere to specific rules.
  Configuration Issues: There may be configuration settings in the system that restrict transactions across different company codes.
  Data Entry Errors: Users may inadvertently select purchase orders from different company codes when entering data.
  
  Solution:
  
  Verify Purchase Orders: Check the purchase orders involved in the transaction to ensure they all belong to the same company code. You can do this by reviewing the purchase order details in the SAP system.
  Adjust Transaction: If the purchase orders are indeed from different company codes, you will need to adjust your transaction to only include purchase orders from the same company code.
  Consult Configuration: If you believe that transactions across different company codes should be allowed, consult with your SAP configuration team to review the settings related to cross-company code transactions.
  User Training: Provide training to users to ensure they understand the importance of selecting purchase orders from the same company code when processing transactions.
  
  Related Information:
  
  SAP Documentation: Refer to SAP Help documentation for more details on handling transactions involving multiple company codes.
  Transaction Codes: Familiarize yourself with relevant transaction codes that may be involved in processing expenses and purchase orders, such as ME21N (Create Purchase Order), ME22N (Change Purchase Order), and FB60 (Enter Incoming Invoice).
  Error Logs: Check the error logs or transaction history for additional context on the error message and any related issues that may have occurred.
  
  If the issue persists after following these steps, it may be beneficial to engage with your SAP support team or consult with an SAP expert for further assistance.