How To Fix EPM027 - The ID <&1> does not adhere to naming conventions

EPM027 - Overview

• Message type: E = Error

• Message class: EPM - Messages for Plant Manager Role

• Message number: 027

• Message text: The ID <&1> does not adhere to naming conventions

What causes this issue?

The KPI ID <&V1&> contains special characters that are not allowed. The
ID does not adhere to naming conventions.

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

System Response

The KPI ID cannot be created.

How to fix this error?

Note the following conventions:
The ID can only contain the following characters:
<ZH>'_0123456789abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ'
</>
The ID must start with one of the following characters:
<ZH>'abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ' </>
The ID cannot contain two successive underscores
<ZH>'__'</>

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

EPM027 - Details

• The SAP error message EPM027 indicates that a specific ID (such as a report, variable, or other object) does not adhere to the naming conventions defined in the system. This error typically arises in the context of SAP Business Planning and Consolidation (BPC) or SAP BusinessObjects Planning and Consolidation (BPC) environments.
  
  Cause:
  The error is triggered when the ID you are trying to use does not meet the required naming conventions. Common reasons for this error include:
  
  Invalid Characters: The ID may contain special characters or spaces that are not allowed.
  Length Restrictions: The ID may exceed the maximum length allowed for identifiers in SAP.
  Prefix/Suffix Requirements: Certain IDs may require specific prefixes or suffixes as per the naming conventions set by your organization or SAP standards.
  Case Sensitivity: Some systems may be case-sensitive, and the ID may not match the expected case.
  
  
  Solution:
  To resolve the EPM027 error, you can take the following steps:
  
  
  Check Naming Conventions: Review