How To Fix CK839 - Planning date &1 (in the past) is not allowed for standard cost estimate


SAP Error Message - Details

  • Message type: E = Error

  • Message class: CK - Product Costing Messages

  • Message number: 839

  • Message text: Planning date &1 (in the past) is not allowed for standard cost estimate

  • Show details Hide details
  • What causes this issue?

    The <LS>Costing date from</> &v1& for the costing falls in the past.
    This is not allowed when you are using a costing variant for the
    standard cost estimate.

    System Response

    The cost estimate is not created.

    How to fix this error?

    Either choose another costing date or another costing variant which
    does does not allow the update of the standard prices.

    Procedure for System Administrators

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


    Error message extract from SAP system. Copyright SAP SE.


Smart SAP Assistant

  • What is the cause and solution for SAP error message CK839 - Planning date &1 (in the past) is not allowed for standard cost estimate ?

    The SAP error message CK839 indicates that the planning date specified for a standard cost estimate is in the past, which is not allowed. This error typically occurs when you attempt to create or update a standard cost estimate with a planning date that is earlier than the current date.

    Cause:

    1. Planning Date in the Past: The primary cause of this error is that the planning date you have entered is earlier than the current date. SAP does not allow cost estimates to be created or updated with past planning dates to ensure that cost estimates reflect current or future conditions.

    Solution:

    To resolve this error, you can take the following steps:

    1. Check the Planning Date: Review the planning date you have entered in the cost estimate transaction. Ensure that it is set to the current date or a future date.

    2. Update the Planning Date: If the planning date is indeed in the past, change it to the current date or a future date. You can do this in the transaction where you are creating or updating the cost estimate (e.g., CK11N for creating a standard cost estimate).

    3. Review Costing Variants: Ensure that the costing variant you are using allows for the desired planning date. Some configurations may restrict the planning dates based on the settings in the costing variant.

    4. Check for System Date Settings: Ensure that the system date on the SAP server is correct. If the server date is incorrect, it may lead to confusion regarding what constitutes a past date.

    5. Consult Documentation: If you are unsure about the correct planning date to use, consult your organization's documentation or SAP help resources for guidance on standard costing procedures.

    Related Information:

    • Transaction Codes: Common transaction codes related to standard cost estimates include CK11N (Create Standard Cost Estimate), CK40N (Change Standard Cost Estimate), and CK24 (Display Standard Cost Estimate).
    • Costing Variants: Costing variants define how costs are calculated and can influence the planning date settings.
    • SAP Notes: Check for any relevant SAP Notes that may provide additional insights or updates related to this error message.
    • User Authorizations: Ensure that you have the necessary authorizations to create or modify cost estimates in the system.

    By following these steps, you should be able to resolve the CK839 error and successfully create or update your standard cost estimate.

    • Do you have any question about this error?


      Upgrade now to chat with this error.


Instant HelpGet instant SAP help. Start your 7-day free trial now.


Related SAP Error Messages

Click the links below to see the following related messages:

Click on this link to search all SAP messages.


Rating
The AI Support Assistant is great. It provides comprehensive assistance even on the most difficult issues. I highly recommend this service.
Rate 1
John Jordan
SAP Consultant & Author