Do you have any question about this error?
Message type: E = Error
Message class: AU - FI-AA utility program error messages
Message number: 234
Message text: Number range interval not updated in the data base.
None of the number ranges were updated in the database. Possible
reasons are either:
No changes were carried out, since all number ranges are defined as
external
An error occurred during update
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
If an error occurred, you need to maintain the number ranges by hand,
or else start the legacy data transfer again.
Error message extract from SAP system. Copyright SAP SE.
AU234
- Number range interval not updated in the data base. ?The SAP error message AU234, which states "Number range interval not updated in the database," 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:
- Number Range Configuration Issues: The number range interval may not be properly defined or activated in the system.
- Authorization Issues: The user may not have the necessary authorizations to update the number range.
- Database Locking: There may be a database lock that prevents the update of the number range.
- Technical Errors: There could be underlying technical issues, such as database inconsistencies or problems with the SAP application server.
Solutions:
Check Number Range Configuration:
- Go to transaction code SNRO (Number Range Objects).
- Find the relevant number range object and check if the intervals are correctly defined and active.
- Ensure that the number range is not exhausted (i.e., all numbers in the range have been used).
Review Authorizations:
- Ensure that the user has the necessary authorizations to create or modify the number range. This can be checked in transaction code SU53 after the error occurs.
Check for Database Locks:
- Use transaction code SM12 to check for any locks on the database that might be preventing updates. If locks are found, they can be released if they are no longer needed.
Check for Technical Issues:
- Review the system logs (transaction code SM21) for any related errors or warnings that might provide more context.
- If necessary, perform a database consistency check or consult with your database administrator.
Recreate Number Range:
- If the number range is corrupted, you may need to delete and recreate the number range interval. Be cautious with this step, as it may affect existing data.
Consult SAP Notes:
- Check the SAP Support Portal for any relevant SAP Notes that might address this specific error message or provide patches.
Related Information:
If the problem persists after trying the above solutions, it may be necessary to involve your SAP Basis team or SAP support for further investigation.
Get instant SAP help. Start your 7-day free trial now.
AU233
A currency field has an incorrect entry format.
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
AU232
An error occurred during recalculation of accumulated depreciation.
What causes this issue? An error occurred during the recalculation of accumulated depreciation. This could be for one of the following reasons: failu...
AU235
Fiscal year of legacy data transfer could not be determined
What causes this issue? The system could not determine the fiscal year for company code &.System Response The system issues an error message and...
AU236
The last day of the fiscal year could not be found.
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.