How To Fix BORGR857 - External identification 2 is not unique (see shipment &1)

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 857

• Message text: External identification 2 is not unique (see shipment &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 BORGR857 - External identification 2 is not unique (see shipment &1) ?

  The SAP error message BORGR857 indicates that there is a problem with the uniqueness of the external identification for a shipment. This error typically arises when you are trying to create or update a shipment in SAP, and the system finds that the external identification (in this case, "External identification 2") is not unique within the context of the shipment.
  Cause:
  
  Duplicate External Identifications: The most common cause of this error is that there are multiple entries in the system with the same external identification value for the specified shipment. This could happen if the same external ID is being used for different shipments or if there was an error in data entry.
  Data Migration Issues: If data has been migrated from another system, there may be duplicates that were not cleaned up.
  Configuration Issues: There may be configuration settings in the SAP system that enforce uniqueness for external identification fields, leading to this error when the uniqueness constraint is violated.
  
  Solution:
  
  
  Check for Duplicates: 
  
  Use transaction codes like SE16N or SE11 to check the relevant database tables (e.g., VTTK for shipment data) for existing entries with the same external identification.
  Identify and resolve any duplicates by either modifying or deleting the conflicting entries.
  
  
  
  Correct Data Entry: 
  
  Ensure that when entering external identification values, they are unique and do not conflict with existing entries.
  
  
  
  Data Cleanup: 
  
  If the issue is due to data migration, perform a cleanup of the data to remove duplicates or adjust the external identification values to ensure uniqueness.
  
  
  
  Consult Documentation: 
  
  Review SAP documentation or consult with your SAP Basis or functional team to understand the specific configuration settings that might be enforcing this uniqueness.
  
  
  
  Error Message Details: 
  
  Pay attention to the shipment number provided in the error message (e.g., shipment &1) to focus your investigation on the specific shipment causing the issue.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as VT01N (Create Shipment), VT02N (Change Shipment), and VT03N (Display Shipment) to manage shipments effectively.
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message.
  User Authorization: Ensure that you have the necessary authorizations to view and modify shipment data in the system.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.