How To Fix /SRMSMC/CMN_BL073 - Request ID &1 not unique

/SRMSMC/CMN_BL073 - Overview

• Message type: E = Error

• Message class: /SRMSMC/CMN_BL -

• Message number: 073

• Message text: Request ID &1 not 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 /SRMSMC/CMN_BL073 - Request ID &1 not unique ?

  The SAP error message /SRMSMC/CMN_BL073 Request ID &1 not unique typically occurs in the context of SAP Supplier Relationship Management (SRM) or similar modules where request IDs are used to track transactions or requests. This error indicates that the system has encountered multiple entries with the same Request ID, which should be unique.
  
  Cause:
  
  
  Duplicate Entries: The most common cause of this error is that there are multiple records in the database with the same Request ID. This can happen due to:
  
  Data entry errors.
  System glitches or bugs.
  Issues during data migration or integration processes.
  
  
  
  Concurrency Issues: If multiple users or processes are trying to create or modify records simultaneously, it may lead to conflicts and duplicate Request IDs.
  
  
  
  Configuration Issues: Incorrect configuration in the system that manages Request IDs can also lead to this error.
  
  
  
  Solution:
  
  
  Identify Duplicates: 
  
  Use transaction codes like SE16 or SE11 to query the relevant database table (e.g., /SRMSMC/REQUESTS) to find all entries