How To Fix FKK_ID_XX_SAFT035 - No data extracted in period &1; specify period of extraction run

SAP Error Message - Details

• Message type: E = Error

• Message class: FKK_ID_XX_SAFT - SAFT message

• Message number: 035

• Message text: No data extracted in period &1; specify period of extraction run

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 FKK_ID_XX_SAFT035 - No data extracted in period &1; specify period of extraction run ?

  The SAP error message FKK_ID_XX_SAFT035 indicates that there was no data extracted for the specified period during a data extraction run. This error typically occurs in the context of SAP Convergent Charging or SAP Contract Accounts Receivable and Payable (FI-CA) when trying to extract data for reporting or integration purposes.
  Cause:
  
  
  No Data for the Specified Period: The most common cause is that there are no records available in the database for the specified extraction period. This could be due to:
  
  No transactions recorded in that period.
  Data not being posted or processed correctly.
  The extraction period being incorrectly defined.
  
  
  
  Incorrect Configuration: The extraction settings or parameters may not be configured correctly, leading to no data being selected.
  
  
  Timing Issues: If the extraction is run immediately after a posting period closes, there may be a delay in data availability.
  
  
  Selection Criteria: The selection criteria used for the extraction may be too restrictive, resulting in no data being selected.
  
  
  Solution:
  
  
  Check Data Availability: Verify if there are any records in the database for the specified period. You can do this by running relevant reports or queries in SAP to see if transactions exist.
  
  
  Review Extraction Parameters: Ensure that the parameters for the extraction run are set correctly. Check the date range and any filters applied to the extraction.
  
  
  Adjust Selection Criteria: If the selection criteria are too restrictive, consider broadening them to include more data.
  
  
  Run Extraction for a Different Period: If possible, try running the extraction for a different period where you know data exists.
  
  
  Check Configuration: Review the configuration settings related to the extraction process to ensure they are set up correctly.
  
  
  Consult Documentation: Refer to SAP documentation or notes related to the specific extraction process you are using for any additional troubleshooting steps.
  
  
  Related Information:
  
  Transaction Codes: You may want to use transaction codes like S_ALR_87012179 or S_ALR_87012180 to check for data in the relevant tables.
  Tables: Familiarize yourself with the relevant tables (e.g., FKKOP, FKKOPK, etc.) that store the data you are trying to extract.
  SAP Notes: Check SAP Notes for any known issues or patches related to the extraction process you are using.
  Support: If the issue persists, consider reaching out to SAP support for further assistance.
  
  By following these steps, you should be able to identify the cause of the error and take appropriate action to resolve it.