How To Fix BORGR855 - Description is not unique (see shipment &1)

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 855

• Message text: Description 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 BORGR855 - Description is not unique (see shipment &1) ?

  The SAP error message BORGR855, which states "Description is not unique (see shipment &1)," typically occurs in the context of logistics or transportation management within SAP. This error indicates that there are multiple entries with the same description for a shipment, which leads to ambiguity in processing.
  Cause:
  
  Duplicate Descriptions: The primary cause of this error is that there are multiple shipments or items with the same description in the system. This can happen if the same description is used for different shipments or if there are similar entries that are not differentiated properly.
  Data Entry Errors: Sometimes, data entry errors can lead to unintentional duplication of descriptions.
  Configuration Issues: In some cases, the configuration settings in SAP may not be set up to handle unique descriptions properly.
  
  Solution:
  
  Identify Duplicates: Use transaction codes like SE16 or SE11 to check the relevant database tables (e.g., LIKP for delivery header data) to identify where the duplicates are occurring.
  Modify Descriptions: Once duplicates are identified, modify the descriptions to ensure they are unique. This can involve changing the text in the shipment or related documents.
  Check Configuration: Review the configuration settings in the relevant modules (like SAP Transportation Management) to ensure that they are set up to enforce unique descriptions where necessary.
  Data Cleansing: If the issue is widespread, consider performing a data cleansing exercise to standardize descriptions across the system.
  Consult Documentation: Refer to SAP documentation or help notes for specific guidance related to your version of SAP, as there may be additional considerations or patches available.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as VL03N (Display Outbound Delivery), VT03N (Display Shipment), and SE16 (Data Browser) for troubleshooting.
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. You can search for notes using the SAP Support Portal.
  User Exits and BAdIs: If you have custom developments, check if there are any user exits or BAdIs that might be affecting how descriptions are handled in your system.
  
  If the problem persists after trying the above solutions, it may be beneficial to consult with your SAP support team or a consultant who specializes in SAP logistics to further investigate the issue.