How To Fix BORGR860 - Not all external identifications are unique

BORGR860 - Overview

• Message type: E = Error

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

• Message number: 860

• Message text: Not all external identifications are unique

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 BORGR860 - Not all external identifications are unique ?

  The SAP error message BORGR860 ("Not all external identifications are unique") typically occurs in the context of Business Object Repository (BOR) or when dealing with external identification of objects in SAP. This error indicates that there are multiple entries with the same external identification, which should be unique.
  
  Cause:
  
  
  Duplicate External Identifications: The primary cause of this error is the presence of duplicate external identifiers in the system. This can happen if:
  
  Data was imported or migrated incorrectly.
  There are inconsistencies in the data entry process.
  Multiple systems are trying to register the same external identification.
  
  
  
  
  Configuration Issues: Sometimes, the configuration settings for external identification may not be set up correctly, leading to conflicts.
  
  
  
  Solution:
  
  
  Identify Duplicates: 
  
  Use transaction codes like SE16 or SE11 to access the relevant tables (e.g., BOR tables) and check for duplicate entries.
  You can run SQL queries to find duplicates based on the external identification field.
  
  
  
  Data Cleanup:
  
  Once duplicates are identified, you will need to