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

SAP Error Message - Details

• 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 combination of key fields (like material, customer, etc.) that you are using in the transaction.
  
  
  Changes in Validity Period: If the validity period of the condition record was changed after it was created, it may no longer be valid for the current transaction.
  
  
  Solution:
  
  
  Check Validity Dates: Review the validity dates of the condition record in the condition maintenance transaction (e.g., transaction code VK11 or VK12). Ensure that the dates encompass the date of the transaction you are processing.
  
  
  Adjust Transaction Date: If possible, adjust the date of the transaction to fall within the validity period of the condition record.
  
  
  Create or Update Condition Records: If the condition record does not exist for the required combination or needs to be updated, create a new condition record or modify the existing one to ensure it covers the necessary validity period.
  
  
  Review Pricing Procedure: Ensure that the pricing procedure being used is correctly configured and that it includes the necessary condition types.
  
  
  Consult Documentation: If you are unsure about the validity periods or how to create/update condition records, refer to SAP documentation or consult with your SAP support team.
  
  
  Related Information:
  
  
  Transaction Codes: 
  
  VK11 - Create Condition Record
  VK12 - Change Condition Record
  VK13 - Display Condition Record
  V/06 - Maintain Pricing Conditions
  
  
  
  Condition Types: Understand the specific condition types involved in your pricing procedure, as different condition types may have different rules regarding validity.
  
  
  SAP Notes: Check for any relevant SAP Notes that may address specific issues or bugs related to condition records and validity periods.
  
  
  User Roles and Authorizations: Ensure that you have the necessary authorizations to create or modify condition records in the system.
  
  
  By following these steps, you should be able to resolve the MN387 error and ensure that your condition records are correctly adopted in your transactions.