How To Fix J4138 - Last number is already assigned: Obj.&, no.&, CC &, year &

SAP Error Message - Details

• Message type: E = Error

• Message class: J4 - External Data Transfer

• Message number: 138

• Message text: Last number is already assigned: Obj.&, no.&, CC &, year &

What causes this issue?

All available numbers in the number range have been used.

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

System Response

The system cannot allocate numbers to any further objects. From now on,
it will calculate new numbers from the start of the number range.
Therefore, the numbers already allocated in the system will no longer
be
unique. In some cases this will cause serious errors.

How to fix this error?

Extend the number range immediately. Obj (<(>&<)>V1<(>&<)>), No.(
<(>&<)>V2<(>&<)>), Bank area
(<(>&<)>V3<(>&<)>), Year (<(>&<)>V4<(>&<)>).

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message J4138 - Last number is already assigned: Obj.&, no.&, CC &, year & ?

  The SAP error message J4138 indicates that a number range has been exhausted for a specific object, meaning that the last number in the defined number range has already been assigned. This typically occurs in the context of document numbering for various financial or controlling objects, such as cost centers, internal orders, or other financial documents.
  
  Cause:
  
  Exhausted Number Range: The number range defined for the specific object (e.g., cost center, internal order) has reached its maximum limit.
  
  Configuration Issues: The number range may not have been properly configured to allow for sufficient numbers.
  Incorrect Object Type: The system might be trying to assign a number to an object type that is not correctly set up.
  
  
  Solution:
  
  
  Extend the Number Range:
  
  Go to the transaction code SNRO (Number Range Objects).
  Find the relevant number range object associated with the error (e.g., for cost centers, it might be COSTCENTER).
  Check the current number range intervals and extend them if necessary.