How To Fix CM_REPORT_GEN036 - Identification listing &1 not found

CM_REPORT_GEN036 - Overview

• Message type: E = Error

• Message class: CM_REPORT_GEN - Report Generation

• Message number: 036

• Message text: Identification listing &1 not found

What causes this issue?

On the <LS>Repeating Group</> tab page for user exit <LB>MRG_EX_ES</>,
you have entered user exit parameter &V1& as the identification listing.
This identification listing does not exist in the system.

System Response

Instead of the specified identification listing, the system uses
identification listing D_DEFAULT. If this identification listing does
not exist in the system, no identifiers are output.

How to fix this error?

Where possible, enter a valid identification listing as the user exit
parameter.

Procedure for System Administrators

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message CM_REPORT_GEN036 - Identification listing &1 not found ?

  The SAP error message CM_REPORT_GEN036, which states "Identification listing &1 not found," typically occurs in the context of the SAP system when a specific identification listing (often related to materials, products, or other entities) cannot be found in the database. This can happen for various reasons, and understanding the cause is essential for resolving the issue.
  Causes:
  
  Missing Data: The identification listing specified by the identifier (&1) does not exist in the database. This could be due to data not being created or deleted.
  Incorrect Identifier: The identifier used in the transaction or report may be incorrect or misspelled.
  Authorization Issues: The user may not have the necessary authorizations to view the identification listing.
  Data Synchronization Issues: If the system is integrated with other systems, there may be synchronization issues leading to missing data.
  
  Configuration Issues: There may be configuration settings that prevent the identification listing from being recognized.
  
  Solutions:
  
  Verify Identifier: Check the identifier you are using