How To Fix OIUCM122 - Vendor & in company code & was changed.

SAP Error Message - Details

• Message type: E = Error

• Message class: OIUCM - E&P Common Messages Across All Sub-Systems

• Message number: 122

• Message text: Vendor & in company code & was changed.

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 OIUCM122 - Vendor & in company code & was changed. ?

  The SAP error message OIUCM122 typically indicates that there has been a change to the vendor master data for a specific vendor in a particular company code. This error can occur in various scenarios, such as during the processing of transactions that involve vendor data, like invoice processing, purchase orders, or payment processing.
  Cause:
  
  Vendor Master Data Change: The vendor's details (such as name, address, payment terms, etc.) have been modified in the vendor master data.
  Data Consistency Issues: The system may be trying to access outdated or inconsistent data related to the vendor.
  Transaction Locking: If multiple users are trying to access or modify the same vendor data simultaneously, it can lead to conflicts.
  Authorization Issues: The user may not have the necessary permissions to access or modify the vendor data.
  
  Solution:
  
  Check Vendor Master Data: Verify the vendor master data for any recent changes. You can do this by navigating to the vendor master record in the SAP system and checking the change logs.
  Refresh Data: If the error occurs during a transaction, try refreshing the data or re-entering the transaction after ensuring that the vendor master data is up to date.
  Reprocess the Transaction: If the transaction was interrupted due to the error, try to reprocess it after confirming that the vendor data is correct.
  Check for Locks: Use transaction codes like SM12 to check for any locks on the vendor data that might be causing the issue. If locks are found, you may need to wait for them to be released or contact the user who has locked the record.
  Authorization Check: Ensure that the user has the necessary authorizations to access and modify vendor data. This may involve checking roles and permissions in the user profile.
  Consult with IT Support: If the issue persists, it may be necessary to consult with your SAP support team or IT department for further investigation and resolution.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as:
  
  XK03: Display Vendor
  XK02: Change Vendor
  MK03: Display Material
  MK02: Change Material
  
  
  Change Logs: Use transaction code SCDO to view change documents related to vendor master data.
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. You can search for relevant notes in the SAP Support Portal.
  
  By following these steps, you should be able to identify the cause of the OIUCM122 error and take appropriate action to resolve it.