How To Fix CK368 - Validity dates for planned price must be in ascending order

CK368 - Overview

• Message type: E = Error

• Message class: CK - Product Costing Messages

• Message number: 368

• Message text: Validity dates for planned price must be in ascending order

What causes this issue?

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

System Response

How to fix this error?

Enter the validity dates for the selected planned prices in
chronological order. In other words, the date for the second planned
price must be after the date for the first planned price. The date
for the third planned price, in turn, must be after the date for the
second planned price.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message CK368 - Validity dates for planned price must be in ascending order ?

  The SAP error message CK368, which states "Validity dates for planned price must be in ascending order," typically occurs during the maintenance of planned prices in the Material Master or during the creation of a cost estimate. This error indicates that the validity dates for the planned prices you are trying to enter are not in the correct order, meaning that the start date of a subsequent price is earlier than the end date of a previous price.
  
  Cause:
  
  Incorrect Date Sequence: The planned prices have been entered with overlapping or non-sequential validity dates.
  Data Entry Error: A user may have mistakenly entered the dates in the wrong order.
  Existing Data Conflicts: There may already be existing planned prices in the system that conflict with the new entries.
  
  
  Solution:
  
  Check Existing Planned Prices: Review the existing planned prices for the material in question. Ensure that all validity dates are in ascending order and do not overlap.
  Correct