Do you have any question about this error?
Message type: E = Error
Message class: MN - Message class for subsequent settlement (Purchasing)
Message number: 790
Message text: No. range object "Coll. processing of cust. billing docs." does not exist
Each debit-side settlement of an arrangement via the general customer
billing document interface is assigned a collective processing number
(customer billing documents).
However, the relevant number range object &V1& does not exist.
The settlement run is terminated.
If necessary, contact your system administrator. A number range object
is missing, and this should not happen.
&SYS_ADM&
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.
MN790
- No. range object "Coll. processing of cust. billing docs." does not exist ?The SAP error message MN790 indicates that the number range object for "Collective processing of customer billing documents" does not exist in the system. This typically occurs when you attempt to execute a transaction that requires a number range object that has not been defined or configured in the system.
Cause:
- Missing Number Range Object: The number range object for collective processing of customer billing documents has not been created or activated in the system.
- Configuration Issues: The configuration settings for the number range object may not be properly set up.
- Transport Issues: If the configuration was transported from another system, the transport may not have included the necessary number range object.
Solution:
To resolve this issue, you can follow these steps:
Check Number Range Object:
- Go to transaction code SNRO (Number Range Objects).
- Enter the object name related to collective processing of customer billing documents (usually something like
F2
orF3
depending on your configuration).- Check if the number range object exists. If it does not, you will need to create it.
Create Number Range Object:
- If the number range object does not exist, you can create it by following these steps:
- In transaction SNRO, click on "Create".
- Enter the name of the number range object and provide a description.
- Define the intervals for the number range.
- Save your changes.
Assign Number Ranges:
- After creating the number range object, you need to assign number ranges to it.
- Go to transaction SNRO again, select the object, and click on "Intervals".
- Define the intervals (e.g., start number, end number) and save.
Check Configuration:
- Ensure that the configuration for collective processing of customer billing documents is correctly set up in the relevant customizing settings (transaction SPRO).
- Navigate to the relevant section for billing document processing and verify that the settings are correct.
Transport Issues:
- If the number range object was supposed to be transported from another system, check the transport logs to ensure that it was included in the transport request.
- If necessary, re-transport the configuration.
Related Information:
By following these steps, you should be able to resolve the MN790 error and ensure that the number range object for collective processing of customer billing documents is properly configured in your SAP system.
Get instant SAP help. Start your 7-day free trial now.
MN789
No. range int. &1 "Coll. processing of cust. bill. docs." does not exist
What causes this issue? Each debit-side settlement of an arrangement via the general customer billing document interface is assigned a collective pro...
MN788
No. range object "Coll. processing of billing docs." could not be found
What causes this issue? Each debit-side settlement of an arrangement via the general customer billing document interface is assigned a collective pro...
MN791
Index created for settlement documents contains invalid entries
What causes this issue? An error occurred during the compilation of the index of the created settlement documents for condition records for arrangeme...
MN792
Unable to determine a settlement run number
What causes this issue? Each settlement run for an arrangement in Purchasing is assigned a unique run number. However, all the numbers in number rang...
Click on this link to search all SAP messages.