How To Fix MN319 - Current condition record in purchasing doc. &, item &, is inactive

MN319 - Overview

• Message type: E = Error

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

• Message number: 319

• Message text: Current condition record in purchasing doc. &, item &, is inactive

What causes this issue?

There is no provision for the updating of condition records from the
"subsequent (end-of-period rebate) settlement" area which are subject
to condition exclusion.

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?

You can correct the faulty update by carrying out a recompilation of
the statistics or by carrying out a business volume comparison and
agreement process.
Please check whether a new price determination process was carried out
after the updating of the LIS statistics relating to "subsequent
settlement" with respect to purchase order no. &V1&, item &V2&. As a
result, the pricing types may have been changed or the exclusion of
conditions relating to "subsequent settlement" activated.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message MN319 - Current condition record in purchasing doc. &, item &, is inactive ?

  The SAP error message MN319 indicates that the current condition record in the purchasing document (PO) and item specified is inactive. This typically occurs when the pricing conditions for a specific purchasing document are not valid or have been deactivated in the system.
  
  Cause:
  
  Inactive Condition Record: The condition record for pricing (like discounts, surcharges, etc.) has been marked as inactive in the system.
  Validity Period: The condition record may have a validity period that has expired.
  Condition Type: The condition type may not be applicable for the specific purchasing document or item.
  Master Data Issues: There may be issues with the vendor master data or material master data that affect the condition records.
  
  Configuration Issues: The pricing procedure may not be correctly configured to include the condition type in question.
  
  
  Solution:
  
  
  Check Condition Records:
  
  Go to transaction code MEK1 (Create Condition) or MEK2 (Change Condition) to check the condition records for the relevant condition type.
  Ensure that the condition