How To Fix CRD_MDA130 - Error during number assignment for number range interval &1

SAP Error Message - Details

• Message type: E = Error

• Message class: CRD_MDA - Messages for Master Data Administration - Credentialing

• Message number: 130

• Message text: Error during number assignment for number range interval &1

What causes this issue?

An error was detected while checking the assignment ID (
<DS:GLOS.3526B521AFAB52B9E10000009B38F974>number range</> &v1&).
The following errors may have occurred:
An external number range was chosen, but the assignment ID is initial;
that means the number will be automatically assigned.
An internal number range was chosen, but the assignment ID is <ZH>not
</> initial, in other words the number was manually assigned.

System Response

The incorrect assignment will not be written on the database.

How to fix this error?

Choose either a <DS:GLOS.3526B523AFAB52B9E10000009B38F974>number range
interval</> for internal number assignment and leave the assignment ID
blank, or choose a number range interval for external number assignment,
in which case you must assign the assignment ID yourself.

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 CRD_MDA130 - Error during number assignment for number range interval &1 ?

  The SAP error message CRD_MDA130, which indicates "Error during number assignment for number range interval &1," typically occurs when there is an issue with the number range configuration in the SAP system. This error can arise in various contexts, such as when creating or processing documents that require a unique number assignment.
  Causes:
  
  Exhausted Number Range: The number range interval specified may have been exhausted, meaning that all available numbers in that range have been assigned.
  Incorrect Configuration: The number range may not be properly configured or activated in the system.
  Authorization Issues: The user may not have the necessary authorizations to access or use the specified number range.
  System Lock: The number range might be locked due to a transaction or process that is currently using it.
  Technical Issues: There could be underlying technical issues, such as database problems or inconsistencies in the number range table.
  
  Solutions:
  
  
  Check Number Range Status:
  
  Go to transaction code SNRO (Number Range