How To Fix MN789 - No. range int. &1 "Coll. processing of cust. bill. docs." does not exist

MN789 - Overview

• Message type: E = Error

• Message class: MN - Message class for subsequent settlement (Purchasing)

• Message number: 789

• Message text: 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 processing number
(customer billing documents).
However, number range &V1& does not exist.

System Response

The settlement run is terminated.

How to fix this error?

Please check your system settings. If necessary, contact your system
administrator.

<ds:SIMG.SIMG_XXMENUOLSDOVV5>Assembling groups of billing documents</>
<ds:SIMG.SIMG_CFMENUOLSDVSAX>Define number range for billing document
groups</>
ENDIF

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 MN789 - No. range int. &1 "Coll. processing of cust. bill. docs." does not exist ?

  The SAP error message MN789 indicates that there is an issue with the number range for the internal document number related to the collective processing of customer billing documents. This error typically arises when the system cannot find a defined number range for the specified document type.
  
  Cause:
  
  Missing Number Range: The number range for the internal document number for collective processing of customer billing documents has not been defined in the system.
  Incorrect Configuration: The configuration settings for the number range may be incorrect or incomplete.
  Authorization Issues: The user may not have the necessary authorizations to access or create the number range.
  Client-Specific Settings: The number range may be defined in a different client or not at all in the current client.
  
  
  Solution:
  
  
  Define Number Range:
  
  Go to the transaction code SNRO (Number Range Objects).
  Look for the number range object related to customer billing documents (usually F2 for billing documents).
  Check if the number range is defined.