How To Fix MN773 - Supplier billing document type &1 not relevant to subsequent settlement

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 773

• Message text: Supplier billing document type &1 not relevant to subsequent settlement

What causes this issue?

Settlement document type &V1& is not relevant for subsequent settlement.
Settlement document type &V1& is assigned to rebate arrangement type
&V2& (subsequent settlement) for partial or final settlement.

System Response

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

How to fix this error?

Choose one of the following options:
Set indicator <LS>Relevant for rebate arrangement</> for settlement
document type &V1& or
Assign a suitable settlement document type to arrangement type &V2&.
Note that you can assign different settlement document types for the
arrangement type for partial/interim settlement and final settlement.
INCLUDE 'NA_CUST_MAINTAIN' OBJECT DOKU ID TX

<DS:SIMG.SIMG_CMMENUOLMEABREC>Control of the "Subsequent Settlement"
Process</>
<DS:SIMG.SIMG_CFMENUOLMEOMHD>Define arrangement types for subsequent
settlement</>
ENDIF

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 MN773 - Supplier billing document type &1 not relevant to subsequent settlement ?

  The SAP error message MN773 indicates that the supplier billing document type specified is not relevant for subsequent settlement processes. This typically occurs in the context of logistics and procurement processes where billing documents are created for suppliers, but the system does not recognize the document type as valid for further processing.
  Cause:
  
  Document Type Configuration: The billing document type may not be configured correctly in the system. It might not be set up to allow for subsequent settlement.
  Incorrect Document Type: The document type being used may not be intended for the type of transaction you are trying to perform.
  Status of the Document: The billing document may be in a status that does not allow for subsequent settlement.
  Missing Customization: There may be missing or incorrect customization in the configuration settings for the supplier billing document types.
  
  Solution:
  
  
  Check Document Type Configuration:
  
  Go to the configuration settings for billing document types in SAP (Transaction Code: SPRO).
  Navigate to Logistics > Materials Management > Purchasing > Invoice Verification > Define Invoice Document Types.
  Ensure that the document type in question is set up correctly for subsequent settlement.
  
  
  
  Verify Document Type Usage:
  
  Ensure that the document type you are using is appropriate for the transaction. If it is not meant for subsequent settlement, you may need to use a different document type.
  
  
  
  Review Document Status:
  
  Check the status of the billing document. If it is already processed or in a state that does not allow further actions, you may need to reverse or adjust the document.
  
  
  
  Consult with Configuration Team:
  
  If you are not able to resolve the issue, consult with your SAP configuration team or a functional consultant who can help review the settings and make necessary adjustments.
  
  
  
  Check for Notes and Updates:
  
  Look for any SAP Notes or updates that may address this specific error message. Sometimes, there are known issues that have been documented by SAP.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as ME23N (Display Purchase Order), MIRO (Enter Incoming Invoice), and others that may be involved in the process.
  Documentation: Review SAP documentation related to invoice verification and billing document types for a deeper understanding of how these elements interact.
  User Roles and Authorizations: Ensure that the user has the necessary authorizations to perform actions related to the billing document.
  
  By following these steps, you should be able to identify the root cause of the MN773 error and implement a solution to resolve it.