How To Fix MN387 - Condition record not adopted due to discrepancy in validity period

MN387 - Overview

• Message type: E = Error

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

• Message number: 387

• Message text: Condition record not adopted due to discrepancy in validity period

What causes this issue?

A condition record of rebate arrangement &V1& has a validity period
that differs from that of the rebate arrangement (&V3& - &V4&).
Since the rebate arrangement is not subject to periodic settlement
accounting (no settlement calendar) no appropriate new validity period
can be determined.

System Response

The condition record was not adopted in the extended rebate arrangement
in the process of periodic extension.

How to fix this error?

Please check rebate arrangement &V2&. It may be necessary to enter the
condition with the key combination &V1& manually.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message MN387 - Condition record not adopted due to discrepancy in validity period ?

  The SAP error message MN387 ("Condition record not adopted due to discrepancy in validity period") typically occurs in the context of pricing conditions in SAP, particularly when working with condition records in the pricing procedure. This error indicates that there is a mismatch between the validity period of the condition record and the date or period being processed in the transaction.
  
  Cause:
  
  
  Validity Period Mismatch: The condition record you are trying to use has a validity period that does not include the date of the transaction. For example, if the condition record is valid from January 1, 2023, to December 31, 2023, and you are processing a transaction dated January 1, 2024, the condition record will not be adopted.
  
  
  Incorrect Date in Transaction: The date of the transaction may not fall within the validity period of the condition record.
  
  
  Condition Record Not Created: The condition record may not have been created for the specific