How To Fix FARR_MSG_CUSTOM836 - Item &1: The quantity unit in fulfillment differs from the orig. item

SAP Error Message - Details

• Message type: E = Error

• Message class: FARR_MSG_CUSTOM - Customizable Messages for Revenue Accounting

• Message number: 836

• Message text: Item &1: The quantity unit in fulfillment differs from the orig. item

What causes this issue?

You try to transfer fulfillment RAIs. But the quantity unit of this RAI
differs from the quantity unit of the corresponding order RAI.

System Response

Fulfillment RAI remains in raw status.

How to fix this error?

The quantity unit of the fulfillment and order RAI should be the same.
You should update the quantity unit in the source system and generate
new RAIs.
In some specific cases is the difference in quantity unit between order
RAI and fulfillment RAI allowed. In such case you can deactivate this
error message in transaction OBA5.

Procedure for System Administrators

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message FARR_MSG_CUSTOM836 - Item &1: The quantity unit in fulfillment differs from the orig. item ?

  The SAP error message FARR_MSG_CUSTOM836 indicates that there is a discrepancy between the quantity unit used in the fulfillment process and the original item’s quantity unit in the system. This error typically arises in the context of SAP's Advanced Returns Management (ARM) or similar modules where items are being processed for returns, exchanges, or other fulfillment activities.
  Cause:
  
  Unit of Measure (UoM) Mismatch: The unit of measure for the item being fulfilled does not match the unit of measure defined for the original item in the system. For example, if the original item is defined in pieces (EA) but the fulfillment process is trying to process it in boxes (BX), this error will occur.
  Configuration Issues: There may be configuration issues in the material master or in the return process settings that lead to this mismatch.
  Data Entry Errors: Manual entry errors during the fulfillment process can lead to incorrect units being specified.
  
  Solution:
  
  Check Item Master Data: Verify the unit of measure defined in the material master for the original item. Ensure that it matches the unit of measure being used in the fulfillment process.
  
  Transaction Code: MM03 (Display Material)
  
  
  Adjust Fulfillment Process: If the fulfillment process is using the wrong unit of measure, adjust it to match the original item’s unit of measure.
  Review Configuration Settings: Check the configuration settings in the SAP system related to the Advanced Returns Management or the specific module you are working with. Ensure that the settings allow for the correct handling of units of measure.
  Consult Documentation: Review SAP documentation or help resources for any specific guidelines related to unit of measure handling in the context of returns or fulfillment.
  User Training: If the issue is due to data entry errors, consider providing additional training to users involved in the fulfillment process to ensure they understand how to correctly enter units of measure.
  
  Related Information:
  
  Material Master Data: Understanding how units of measure are defined and managed in the material master is crucial. Each material can have multiple units of measure (base unit, sales unit, purchase unit, etc.).
  Unit of Measure Conversion: If applicable, check if there are any conversion factors defined that might allow for the fulfillment process to accept different units of measure.
  SAP Notes and Support: Check for any relevant SAP Notes that might address this specific error or provide additional troubleshooting steps.
  Transaction Codes: Familiarize yourself with relevant transaction codes such as MB1A, MB1B, or VL01N for goods movements and deliveries, as they may be involved in the fulfillment process.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.