How To Fix MRNB024 - No message condition record found for partner &1 / company code &2

MRNB024 - Overview

• Message type: E = Error

• Message class: MRNB - Messages for Revaluation (Retro Active Pricing)

• Message number: 024

• Message text: No message condition record found for partner &1 / company code &2

What causes this issue?

The system was unable to generate any output messages for business
partner &V1& in company code &V2&.

System Response

If the system cannot find an output condition record for the supplier in
an invoice document, and therefore cannot create an output message, then
it has not created the document.

How to fix this error?

Configure the message determination in Customizing for Invoice
Verification so that the system can create an output message for the
supplier 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>Proceed</>

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message MRNB024 - No message condition record found for partner &1 / company code &2 ?

  The SAP error message MRNB024 indicates that there is no message condition record found for a specified partner and company code. This error typically arises in the context of message determination in SAP, particularly when dealing with purchasing documents, invoices, or other transactional data that require message output.
  
  Cause:
  
  Missing Condition Records: The most common cause of this error is that there are no condition records set up for the specified partner (vendor or customer) and company code in the message determination configuration.
  Incorrect Partner or Company Code: The partner or company code specified in the transaction may not match any existing records in the system.
  Message Type Not Defined: The message type you are trying to use may not be defined for the specific partner or company code.
  Inconsistent Data: There may be inconsistencies in the data setup, such as missing or incorrect entries in the relevant tables.
  
  
  Solution:
  
  
  Check Condition Records:
  
  Go to the transaction code