How To Fix /ACCGO/BR_UIS073 - Qty in deliv. note should match LDC deliv. note qty, that is, &1

SAP Error Message - Details

• Message type: E = Error

• Message class: /ACCGO/BR_UIS -

• Message number: 073

• Message text: Qty in deliv. note should match LDC deliv. note qty, that is, &1

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/BR_UIS073 - Qty in deliv. note should match LDC deliv. note qty, that is, &1 ?

  The SAP error message /ACCGO/BR_UIS073 Qty in deliv. note should match LDC deliv. note qty, that is, &1 typically occurs in the context of logistics and delivery processing within the SAP system. This error indicates a mismatch between the quantity specified in the delivery note and the quantity expected in the LDC (Logistics Data Collection) delivery note.
  Cause:
  
  
  Quantity Mismatch: The most common cause of this error is that the quantity of items in the delivery note does not match the quantity that was recorded in the LDC delivery note. This could happen due to:
  
  Incorrect data entry when creating the delivery note.
  Changes in the order quantity that were not reflected in the delivery note.
  Issues during the transfer of data between systems or modules.
  
  
  
  Configuration Issues: There may be configuration settings in the SAP system that enforce strict matching of quantities between delivery notes and LDC records.
  
  
  Incomplete Processing: The delivery note may not have been fully processed or updated in the system, leading to discrepancies.
  
  
  Solution:
  
  
  Verify Quantities: Check the quantities in both the delivery note and the LDC delivery note. Ensure that they match exactly. If there is a discrepancy, correct the quantity in the delivery note to match the LDC delivery note quantity.
  
  
  Recreate Delivery Note: If the delivery note is incorrect and cannot be adjusted, consider deleting the incorrect delivery note and creating a new one with the correct quantities.
  
  
  Check Configuration: Review the configuration settings related to delivery processing and LDC in the SAP system. Ensure that they are set up correctly to avoid such mismatches.
  
  
  Data Consistency Check: Run a consistency check in the system to identify any other potential discrepancies that may not be immediately visible.
  
  
  Consult Documentation: Refer to SAP documentation or help resources for specific guidance on handling delivery note errors.
  
  
  Contact Support: If the issue persists and cannot be resolved through the above steps, consider reaching out to your SAP support team or consulting with an SAP expert for further assistance.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as VL01N (Create Outbound Delivery), VL02N (Change Outbound Delivery), and VL03N (Display Outbound Delivery) to manage delivery notes.
  SAP Notes: Check for any SAP Notes related to this error message that may provide additional insights or patches.
  User Exits and BAdIs: If you have custom developments, check if there are any user exits or BAdIs that might be affecting the delivery processing logic.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.