How To Fix BORGR547 - The external ID of the delivery note is not unique (see inb. dely &1)

SAP Error Message - Details

• Message type: E = Error

• Message class: BORGR - Messages Multi-Level Goods Receipt

• Message number: 547

• Message text: The external ID of the delivery note is not unique (see inb. dely &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 BORGR547 - The external ID of the delivery note is not unique (see inb. dely &1) ?

  The SAP error message BORGR547 indicates that there is a problem with the uniqueness of the external ID associated with a delivery note. This error typically arises when the system detects that the external ID (which is often used for integration with external systems or for tracking purposes) is not unique within the context of the specified inbound delivery.
  Cause:
  
  Duplicate External IDs: The most common cause of this error is that there are multiple inbound deliveries with the same external ID in the system. This can happen due to data entry errors, integration issues, or incorrect configurations in the system.
  Data Migration Issues: If data has been migrated from another system, it is possible that duplicate external IDs were introduced during the migration process.
  Integration Problems: If the system is integrated with external applications (like EDI systems), there may be issues with how external IDs are generated or transmitted.
  
  Solution:
  
  
  Check for Duplicates: 
  
  Use transaction codes like VL03N (Display Inbound Delivery) to check for existing inbound deliveries with the same external ID. 
  You can also run a query in the database to find duplicates.
  
  
  
  Correct the Data: 
  
  If duplicates are found, you will need to determine which entry is correct and either delete or modify the other entries to ensure that the external ID is unique.
  If the duplicate entries are due to a data migration issue, you may need to clean up the data in the source system or adjust the migration process.
  
  
  
  Review Integration Settings: 
  
  If the issue is related to integration with external systems, review the configuration settings to ensure that external IDs are generated correctly and are unique.
  Ensure that the external systems are not sending duplicate IDs.
  
  
  
  Consult Documentation: 
  
  Check SAP documentation or notes related to this error message for any specific recommendations or patches that may address the issue.
  
  
  
  Contact SAP Support: 
  
  If the issue persists and you cannot resolve it, consider reaching out to SAP support for assistance. They may provide insights or solutions based on the specific version of SAP you are using.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as VL03N (Display Inbound Delivery), VL02N (Change Inbound Delivery), and VL01N (Create Inbound Delivery) for managing inbound deliveries.
  SAP Notes: Search for SAP Notes related to BORGR547 for any known issues or patches.
  Data Consistency: Regularly check for data consistency in your SAP system to prevent such issues from occurring in the future.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.