How To Fix FCMLHELP035 - No continuity check possible for first ckmi1 record selected.

SAP Error Message - Details

• Message type: E = Error

• Message class: FCMLHELP - HelpDesk

• Message number: 035

• Message text: No continuity check possible for first ckmi1 record selected.

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 FCMLHELP035 - No continuity check possible for first ckmi1 record selected. ?

  The SAP error message FCMLHELP035, which states "No continuity check possible for first CKMI1 record selected," typically occurs in the context of the Controlling (CO) module, particularly when dealing with cost object accounting or when trying to analyze cost flows.
  Cause:
  This error usually arises due to one of the following reasons:
  
  
  Missing or Incomplete Data: The CKMI1 table, which stores the cost management information, may not have the necessary records or may have incomplete data for the selected period or cost object.
  
  
  Data Consistency Issues: There may be inconsistencies in the data, such as missing entries or incorrect postings that prevent the system from performing a continuity check.
  
  
  Incorrect Selection Criteria: The selection criteria used to retrieve data from the CKMI1 table may not be appropriate, leading to no valid records being found.
  
  
  Technical Issues: There could be underlying technical issues, such as database inconsistencies or problems with the SAP system itself.
  
  
  Solution:
  To resolve the FCMLHELP035 error, you can take the following steps:
  
  
  Check Data Completeness:
  
  Verify that the CKMI1 table has the necessary records for the period and cost object you are analyzing. You can do this by running a query on the CKMI1 table to see if the relevant data exists.
  
  
  
  Review Selection Criteria:
  
  Ensure that the selection criteria you are using to retrieve data are correct. Adjust the criteria if necessary to ensure that valid records are being selected.
  
  
  
  Run Consistency Checks:
  
  Use transaction codes like KAH1 (for cost center accounting) or KSB1 (for cost center reports) to check for any inconsistencies in the data. You may also want to run the report RKAEP000 to check for inconsistencies in the cost accounting data.
  
  
  
  Repost Missing Data:
  
  If you find that there are missing records, you may need to repost the relevant transactions to ensure that all necessary data is available in the CKMI1 table.
  
  
  
  Consult SAP Notes:
  
  Check the SAP Support Portal for any relevant SAP Notes that may address this specific error. There may be patches or updates that can resolve the issue.
  
  
  
  Contact SAP Support:
  
  If the issue persists after trying the above steps, consider reaching out to SAP Support for further assistance. They can provide more detailed guidance based on your specific system configuration and data.
  
  
  
  Related Information:
  
  CKMI1 Table: This table is crucial for cost management and contains records related to cost object accounting.
  Transaction Codes: Familiarize yourself with relevant transaction codes in the CO module, such as KSB1, KAH1, and KOB1, which can help in analyzing cost data.
  Data Consistency: Regularly check for data consistency in your SAP system to prevent similar issues from arising in the future.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.