How To Fix USMD1587 - Data model &1, entity type &2: Number range object is not required

USMD1587 - Overview

• Message type: E = Error

• Message class: USMD1 - Datenmodel

• Message number: 587

• Message text: Data model &1, entity type &2: Number range object is not required

What causes this issue?

You have defined a number range object for entity type &V2& from which
the system would generate temporary keys when creating an instance.
However, the number range object is only relevant for entity types with
internal key assignments. It is not possible to assign an internal key
for entity type &V2&.

System Response

You cannot activate the data model.

How to fix this error?

In the Customizing activity <DS:SIMG.FMDM_USMD001>Edit Data Model</>, do
not enter a number range object under <LS>Temporary Key</> for entity
types without internal key assignments.

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 USMD1587 - Data model &1, entity type &2: Number range object is not required ?

  The SAP error message USMD1587 indicates that there is an issue related to the number range object for a specific data model and entity type. This message typically arises in the context of SAP Master Data Governance (MDG) when you are trying to create or manage master data.
  
  Cause:
  The error message "Number range object is not required" suggests that the system is expecting a number range object to be defined for the specified entity type, but it is either not configured or not necessary for that particular entity. This can happen due to:
  
  
  Configuration Issues: The number range object may not be set up correctly in the system for the specified entity type.
  Entity Type Settings: The entity type may not require a number range object, but the system is still trying to validate it.
  Data Model Configuration: The data model may have been incorrectly configured, leading to this inconsistency.
  
  
  Solution:
  To resolve the error, you