How To Fix USMDZ10072 - Source and target company code must be different

SAP Error Message - Details

• Message type: E = Error

• Message class: USMDZ10 - Message Class for MDG-F BOL/genIL UI related texts

• Message number: 072

• Message text: Source and target company code must be different

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 USMDZ10072 - Source and target company code must be different ?

  The SAP error message USMDZ10072 indicates that there is an issue with the company codes being used in a transaction or process. Specifically, the error states that the source and target company codes must be different. This typically occurs in scenarios involving data migration, master data management, or when performing certain financial transactions.
  Cause:
  The error arises when a user attempts to perform an operation that requires the source and target company codes to be distinct, but they are inadvertently set to the same value. This can happen in various contexts, such as:
  
  Data migration processes where data is being transferred from one company code to another.
  Master data changes where the same company code is mistakenly selected as both the source and target.
  Financial postings or adjustments that require differentiation between the source and target entities.
  
  Solution:
  To resolve the error, follow these steps:
  
  
  Check Company Code Selection: Review the transaction or process where the error occurred. Ensure that the source and target company codes are indeed different. If they are the same, change one of them to the appropriate company code.
  
  
  Review Configuration: If this error occurs frequently, check the configuration settings related to the specific transaction or process. Ensure that the system is set up correctly to handle the intended operations.
  
  
  Data Migration Tools: If you are using data migration tools (like LSMW or SAP Data Services), verify the mapping of source and target company codes in your migration project. Make sure that the mappings are correct and that they reflect the intended business logic.
  
  
  Consult Documentation: Refer to SAP documentation or help resources related to the specific transaction or process you are working with. This can provide additional context on the requirements for company codes.
  
  
  Testing: After making changes, conduct tests to ensure that the error no longer occurs and that the intended operations can be completed successfully.
  
  
  Related Information:
  
  Transaction Codes: Depending on the context, you may be using specific transaction codes (e.g., FB50 for financial postings, or OX15 for company code settings) that could be relevant to the error.
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional guidance on handling company code configurations.
  User Roles and Authorizations: Ensure that the user has the necessary authorizations to perform actions involving multiple company codes, as restrictions may also lead to errors.
  
  If the issue persists after following these steps, consider reaching out to your SAP support team or consulting with an SAP expert for further assistance.