How To Fix LEDSP067 - The number that was scanned (&1) is not unique

SAP Error Message - Details

• Message type: E = Error

• Message class: LEDSP - System Messages - Subsequent Delivery Split

• Message number: 067

• Message text: The number that was scanned (&1) is not unique

What causes this issue?

The number that was scanned (&V1&) is assigned to more than one handling
unit, meaning that there is more than one handling unit in the system
with the same number.

System Response

The system cannot identify the correct handling unit.

How to fix this error?

Assign a new number for the handling unit and print a new label (if
necessary).

You can make settings in Customizing that only allow handling unit
numbers to be assigned once (see also: <DS:SIMG.SIMG_HUMIDTVSHP>Set
Unique Number Assignment for HU Identification</>). You should make this
setting if you want to use these numbers to identify handling units (by
scanning them, for example).

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message LEDSP067 - The number that was scanned (&1) is not unique ?

  The SAP error message LEDSP067 indicates that the number scanned (represented by &1) is not unique within the context of the operation being performed. This typically occurs in scenarios involving inventory management, logistics, or warehouse management where unique identifiers (like serial numbers, batch numbers, or material numbers) are expected.
  Cause:
  
  Duplicate Entries: The scanned number may already exist in the system for the same material or item, leading to a conflict.
  Incorrect Scanning: The user may have scanned the wrong item or number, or there may be a mistake in the scanning process.
  Configuration Issues: The system may not be configured to handle multiple entries for the same identifier in certain contexts.
  Data Integrity Issues: There may be issues with data integrity in the database, such as corruption or improper data entry.
  
  Solution:
  
  Verify the Scanned Number: Check the scanned number against the database to confirm whether it is indeed a duplicate. Ensure that the correct item is being scanned.
  Check for Duplicates: Use transaction codes like MMBE (Stock Overview) or MB52 (List Warehouse Stocks on Hand) to check if the scanned number is already assigned to another item.
  Correct the Entry: If the scanned number is incorrect, re-scan the correct number or manually enter the correct identifier.
  Review Configuration: If this error occurs frequently, review the configuration settings in the relevant modules (like Inventory Management or Warehouse Management) to ensure they are set up correctly for handling unique identifiers.
  Consult with IT Support: If the issue persists, it may be necessary to consult with your SAP support team or IT department to investigate potential data integrity issues or system configuration problems.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes that can help in troubleshooting, such as MB1A, MB1B, MB1C, and others related to inventory management.
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. SAP frequently updates its knowledge base with solutions to common problems.
  User Documentation: Review user manuals or training materials related to the specific SAP module you are working with to understand how to properly handle unique identifiers.
  
  By following these steps, you should be able to identify the cause of the LEDSP067 error and take appropriate action to resolve it.