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 &

  • Show details Hide details
  • 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:

    1. Exhausted Number Range: The number range defined for the specific object (e.g., cost center, internal order) has reached its maximum limit.
    2. Configuration Issues: The number range may not have been properly configured to allow for sufficient numbers.
    3. Incorrect Object Type: The system might be trying to assign a number to an object type that is not correctly set up.

    Solution:

    1. 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. You can add new intervals to allow for more numbers to be generated.
    2. Check Number Range Assignment:

      • Ensure that the number range is correctly assigned to the relevant object type in the configuration settings.
      • Use transaction code OKA0 (for cost centers) or similar transactions for other objects to verify the assignment.
    3. Review Configuration:

      • If you are not the system administrator, contact your SAP Basis or configuration team to review the number range settings and make necessary adjustments.
    4. Monitor Usage:

      • Regularly monitor the usage of number ranges to prevent future occurrences of this error. Set up alerts or reports to track the remaining numbers in the range.

    Related Information:

    • Transaction Codes:
      • SNRO: Number Range Objects
      • OKA0: Maintain Number Ranges for Cost Centers
      • KOT2: Maintain Number Ranges for Internal Orders
    • Documentation: Refer to SAP Help documentation for detailed instructions on managing number ranges and understanding the implications of number range exhaustion.
    • Support: If the issue persists after attempting the above solutions, consider reaching out to SAP support for further assistance.

    By following these steps, you should be able to resolve the J4138 error and ensure that your number ranges are properly configured and maintained.

    • Do you have any question about this error?


      Upgrade now to chat with this error.


Instant HelpGet instant SAP help. Start your 7-day free trial now.


Related SAP Error Messages

Click the links below to see the following related messages:

Click on this link to search all SAP messages.


Rating
ERPlingo simplifies finding the accurate answers to SAP message errors. I now use every week. A must have tool for anyone working with SAP! Highly recommended!
Rate 1
Kent Bettisworth
Executive SAP Consultant