How To Fix /SCMB/DM_BOL702 - Document &1 Item &2: Unit of measure conversion from &2 to &3 failed

SAP Error Message - Details

• Message type: E = Error

• Message class: /SCMB/DM_BOL -

• Message number: 702

• Message text: Document &1 Item &2: Unit of measure conversion from &2 to &3 failed

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 /SCMB/DM_BOL702 - Document &1 Item &2: Unit of measure conversion from &2 to &3 failed ?

  The SAP error message /SCMB/DM_BOL702 Document &1 Item &2: Unit of measure conversion from &2 to &3 failed typically occurs in the context of SAP Supply Chain Management (SCM) when there is an issue with converting units of measure (UoM) for a specific document item. This error can arise in various scenarios, such as during the processing of deliveries, shipments, or inventory management.
  Cause:
  
  Missing Conversion Factors: The most common cause of this error is that there is no defined conversion factor between the two units of measure involved (from &2 to &3).
  Incorrect UoM Configuration: The units of measure may not be correctly configured in the system, leading to conversion failures.
  Data Inconsistencies: There may be inconsistencies in the master data, such as material master records, where the UoM settings are not aligned.
  Unit of Measure Group Issues: The UoM group assigned to the material may not include the necessary conversions.
  Custom Logic or Enhancements: If there are custom developments or enhancements in the system, they might interfere with the standard UoM conversion logic.
  
  Solution:
  
  
  Check UoM Configuration:
  
  Go to the transaction code CUNI (Unit of Measure Conversion) to check if the conversion factors between the two units of measure are defined.
  If not, create the necessary conversion entries.
  
  
  
  Review Material Master Data:
  
  Use transaction code MM03 to view the material master data and ensure that the UoM settings are correct.
  Check the base unit of measure and any alternative units of measure defined for the material.
  
  
  
  Validate UoM Groups:
  
  Ensure that the UoM group assigned to the material includes the required conversions.
  You can check this in the material master under the "Basic Data" or "Sales Org. Data" views.
  
  
  
  Check for Custom Logic:
  
  If there are any custom developments or enhancements, review them to ensure they are not causing the issue.
  Consult with your ABAP team if necessary.
  
  
  
  Test with Different Scenarios:
  
  Try to replicate the issue with different materials or documents to see if the problem is isolated to specific cases.
  
  
  
  Consult SAP Notes:
  
  Check the SAP Support Portal for any relevant SAP Notes that might address this specific error or provide additional guidance.
  
  
  
  Related Information:
  
  Transaction Codes: 
  
  CUNI for Unit of Measure Conversion.
  MM03 for Material Master Display.
  
  
  Documentation: Review SAP documentation on unit of measure management and conversion.
  SAP Community: Engage with the SAP Community forums for insights from other users who may have encountered similar issues.
  
  By following these steps, you should be able to identify the root cause of the error and implement the necessary corrections to resolve it.