How To Fix /ACCGO/UIS_MSG688 - UoM record at vendor split and UIS does not match

SAP Error Message - Details

• Message type: E = Error

• Message class: /ACCGO/UIS_MSG -

• Message number: 688

• Message text: UoM record at vendor split and UIS does not match

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/UIS_MSG688 - UoM record at vendor split and UIS does not match ?

  The SAP error message /ACCGO/UIS_MSG688 typically indicates an issue related to Unit of Measure (UoM) records during a vendor split in the context of the Universal Integration Services (UIS) in SAP. This error suggests that there is a mismatch between the UoM records for the vendor and the UIS data.
  Cause:
  
  
  UoM Mismatch: The primary cause of this error is that the UoM defined for the vendor does not match the UoM expected by the UIS. This can happen if:
  
  The vendor master data has been updated with a different UoM.
  The UIS configuration is expecting a specific UoM that is not aligned with the vendor's UoM.
  There are inconsistencies in the UoM settings between different systems or modules.
  
  
  
  Data Inconsistency: There may be inconsistencies in the data being processed, such as:
  
  Incorrectly maintained master data for the vendor.
  Missing or incorrect UoM records in the relevant tables.
  
  
  
  Configuration Issues: There could be configuration issues in the UIS settings or in the vendor master data that lead to this mismatch.
  
  
  Solution:
  
  
  Check Vendor Master Data:
  
  Go to the vendor master data (transaction code XK03 or MK03) and verify the UoM settings.
  Ensure that the UoM defined for the vendor matches the UoM expected by the UIS.
  
  
  
  Review UIS Configuration:
  
  Check the UIS configuration settings to ensure that they are correctly set up to handle the UoM for the vendor.
  Make sure that the UoM mappings in UIS are correctly defined.
  
  
  
  Data Consistency Check:
  
  Perform a consistency check on the relevant data records to identify any discrepancies.
  Use transaction codes like SE16 or SE11 to view the relevant tables and check for inconsistencies.
  
  
  
  Update UoM Records:
  
  If discrepancies are found, update the UoM records in the vendor master or UIS configuration as necessary.
  Ensure that any changes are tested in a development or quality environment before applying them to production.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or notes related to UIS and UoM handling for any specific guidelines or known issues.
  
  
  
  Contact SAP Support:
  
  If the issue persists after checking the above points, consider reaching out to SAP support for further assistance.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as XK03 (Display Vendor), MK03 (Display Purchasing Info Record), and SE16 (Data Browser) for checking data.
  SAP Notes: Look for SAP Notes related to UIS and UoM issues, as they may provide additional insights or patches.
  Training and Documentation: Ensure that users involved in vendor management and UIS integration are trained on the importance of maintaining consistent UoM records.
  
  By following these steps, you should be able to identify and resolve the issue related to the error message /ACCGO/UIS_MSG688.