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

SAP Error Message - Details

• 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 the Dates: If you find any entries with overlapping or incorrectly ordered dates, adjust them so that each planned price has a start date that is later than the end date of the previous price.
  Use Transaction CK11N/CK40N: If you are creating a cost estimate, use transaction codes like CK11N (Create Cost Estimate with Quantity Structure) or CK40N (Change Cost Estimate) to review and adjust the planned prices.
  Data Validation: Before saving any changes, validate the data to ensure that all planned prices are correctly sequenced.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as CK11N, CK40N, and MM02 (Change Material Master) for managing planned prices.
  Documentation: Refer to SAP documentation or help files for detailed instructions on managing planned prices and understanding the implications of validity dates.
  User Roles: Ensure that users making these changes have the appropriate authorizations to modify planned prices in the system.
  Testing: If changes are made, consider testing in a development or quality environment before applying changes in production to avoid disruptions.
  
  By following these steps, you should be able to resolve the CK368 error and ensure that your planned prices are correctly configured in SAP.