How To Fix MN757 - Cond. type & in calc. schema & contains requirement & (Please check)

MN757 - Overview

• Message type: E = Error

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

• Message number: 757

• Message text: Cond. type & in calc. schema & contains requirement & (Please check)

What causes this issue?

Calculation schema &V2& is used for price determination within the
framework of PO processing.
To make it possible for the data on the volume of business done with the
supplier to be updated for the purpose of "subsequent (end-of-period
rebate) settlement", the condition types for "subsequent settlement"
(condition class "C") must be entered in calculation schema &V2&. During
the price determination process, the system then searches for valid
condition records (relating to rebate arrangements). The condition
records that are found will be set with the condition value '0' or with
the provision that is to be made for accrued income.
Using various indicators

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

in the supplier master record
in the purchasing info record
in the PO item
you can specify whether an item is subject to "subsequent settlement"
(i.e. whether or not the cumulative supplier business volume data is to
be updated).
To achieve this, the appropriate requirement must be entered in
calculation schema &V2& for condition type &V1&.
In the standard system, requirement '026' is available for this purpose.
However, the calculation schema uses requirement &V3&.
&WHAT_TO_DO& (system administrator)
Check whether requirement &V3& really is to be used, and whether it
fulfills the above purpose.

<DS>
<ds:SIMG.SIMG_CFMENUOLMEKONDT>Set Up Condition Technique</>
ENDIF

Error message extract from SAP system. Copyright SAP SE.

MN757 - Details

• The SAP error message MN757 indicates that there is an issue with a condition type in a pricing calculation schema. Specifically, it suggests that the condition type specified in the message is associated with a requirement that is not being met. This can occur in various scenarios, such as during sales order processing, pricing determination, or invoice generation.
  
  Cause:
  
  Condition Type Configuration: The condition type may have a requirement that is not being fulfilled. This could be due to missing data or incorrect settings in the pricing procedure.
  Pricing Procedure: The pricing procedure may not be correctly assigned to the sales document type or may not be configured properly.
  Master Data Issues: The master data (such as customer master, material master, or info records) may not have the necessary information that meets the requirement for the condition type.
  Requirement Logic: The logic defined in the requirement associated with the condition type may not be satisfied