How To Fix /SAPAPO/CFM_MSG068 - Gap identified: expected start date &1 does not match the provided &2

SAP Error Message - Details

• Message type: E = Error

• Message class: /SAPAPO/CFM_MSG -

• Message number: 068

• Message text: Gap identified: expected start date &1 does not match the provided &2

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message /SAPAPO/CFM_MSG068 - Gap identified: expected start date &1 does not match the provided &2 ?

  The SAP error message /SAPAPO/CFM_MSG068 indicates that there is a mismatch between the expected start date of a process or activity and the date that has been provided. This error typically occurs in the context of SAP Advanced Planning and Optimization (APO), particularly in the context of Capacity Planning or Production Planning.
  Cause:
  The error is caused by a discrepancy between the expected start date of a planned order, production order, or any other scheduling-related object and the date that is being provided in the system. This can happen due to several reasons, including:
  
  Incorrect Date Configuration: The system may have been configured with incorrect dates for the planning process.
  Changes in Planning Parameters: If planning parameters or settings have been changed after the initial planning run, it may lead to inconsistencies.
  Manual Adjustments: Manual changes to dates in the planning or scheduling process that do not align with the expected dates.
  Data Migration Issues: If data has been migrated from another system, there may be inconsistencies in date formats or values.
  
  Solution:
  To resolve this error, you can take the following steps:
  
  Check the Dates: Verify the expected start date and the provided date. Ensure that they match and are correctly configured in the system.
  Review Planning Parameters: Check the planning parameters and settings to ensure they are correctly set up and have not been altered unexpectedly.
  Adjust Dates: If necessary, adjust the dates in the planning or scheduling process to ensure they align with the expected values.
  Re-run Planning: If changes have been made, re-run the planning process to ensure that the system recalculates the dates based on the updated parameters.
  Consult Logs: Check the application logs for any additional information or warnings that may provide context for the error.
  SAP Notes: Look for any relevant SAP Notes or documentation that may address this specific error or provide additional troubleshooting steps.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as /SAPAPO/CFM for Capacity Planning or /SAPAPO/SDP94 for Demand Planning, depending on where the error is occurring.
  SAP Help Portal: Utilize the SAP Help Portal for documentation related to APO and specific error messages.
  Support: If the issue persists, consider reaching out to SAP support or your internal SAP support team for further assistance.
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution to resolve it.