How To Fix M8446 - ERS settlement: No message was found for partner &1/company code &2

SAP Error Message - Details

• Message type: E = Error

• Message class: M8 - Invoice Verification/Valuation

• Message number: 446

• Message text: ERS settlement: No message was found for partner &1/company code &2

Parts of this text similar to message M8 444 and M8 443

What causes this issue?

You use the evaluated receipt settlement (ERS) procedure to invoice a
business partner's (&V2&) goods receipts in company code &V1&. In order
to inform your business partner, you want to create a document using
message determination.

System Response

If no message record was found for a partner because of the message
control settings, meaning that no output message can be created, no
invoice documents are created.

How to fix this error?

In Customizing for Invoice Verification, check that the data for message
determination has been maintained in such a way that an output message
can be created for the suppliers in the invoice document.

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

<DS:CHAP.SIMG_CFMENUOLMRNACH>Execute function</>
If you do not want to create a document using message determination, you
can switch off this message in Customizing.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message M8446 - ERS settlement: No message was found for partner &1/company code &2 ?

  The SAP error message M8446, which states "ERS settlement: No message was found for partner &1/company code &2," typically occurs in the context of the Evaluated Receipt Settlement (ERS) process. This error indicates that the system could not find a corresponding message for the specified partner and company code during the ERS settlement process.
  Cause:
  
  Missing or Incorrect Data: The error often arises when there is no valid message (such as an invoice or a goods receipt) for the specified vendor (partner) and company code in the system.
  Configuration Issues: There may be configuration settings in the ERS process that are not set up correctly, leading to the inability to find the necessary messages.
  Timing Issues: The message may not have been created yet, or it may have been deleted or archived.
  Document Status: The documents related to the ERS process may not be in the correct status to allow for settlement.
  
  Solution:
  
  Check for Messages: Verify that there are valid messages for the specified partner and company code. You can do this by checking the relevant documents in the system (e.g., purchase orders, goods receipts).
  Review ERS Configuration: Ensure that the ERS configuration is correctly set up in the system. This includes checking the settings for the relevant purchasing organization and company code.
  Document Status: Make sure that the documents involved in the ERS process are in the correct status. For example, ensure that the goods receipt has been posted and is not blocked or deleted.
  Reprocess ERS: If the messages were missing due to a temporary issue, try reprocessing the ERS settlement. This can sometimes resolve the issue if the necessary messages are now available.
  Consult Logs: Check the application logs for more detailed error messages or warnings that could provide additional context for the issue.
  
  Related Information:
  
  Transaction Codes: You may want to use transaction codes like ME23N (Display Purchase Order) or ME2N (Purchase Orders by PO Number) to check the status of purchase orders and related documents.
  SAP Notes: Look for relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  Documentation: Review SAP documentation on Evaluated Receipt Settlement for a better understanding of the process and requirements.
  
  If the issue persists after following these steps, it may be beneficial to consult with your SAP support team or a technical consultant who can provide more in-depth analysis and assistance.