How To Fix FG679 - End of the retrieval run

SAP Error Message - Details

• Message type: E = Error

• Message class: FG - Program Error Messages

• Message number: 679

• Message text: End of the retrieval 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 FG679 - End of the retrieval run ?

  The SAP error message FG679, which states "End of the retrieval run," typically occurs in the context of the SAP system's data retrieval processes, particularly in the areas of inventory management, production planning, or logistics. This message indicates that the system has completed a data retrieval run, and it may not necessarily indicate an error but rather a status update.
  Cause:
  
  Completion of Data Retrieval: The message is often triggered when a data retrieval process has finished executing. This could be part of a batch job or a scheduled task that retrieves data from various sources.
  No More Data to Process: It may also indicate that there are no more records to process in the current run, which could be expected behavior if the job was designed to process a finite set of data.
  Configuration Issues: In some cases, if the retrieval process is not configured correctly, it may lead to premature completion without processing the expected data.
  
  Solution:
  
  Check Job Logs: Review the job logs or application logs to understand the context of the message. Look for any preceding messages that might indicate issues or warnings.
  Verify Data Availability: Ensure that there is data available for the retrieval process. If the process is expected to retrieve data but finds none, it may complete without processing anything.
  Review Configuration: If the message is unexpected, check the configuration settings for the retrieval process. Ensure that all parameters are set correctly and that the data sources are accessible.
  Re-run the Process: If you suspect that the process did not complete as expected, you can try re-running the retrieval job to see if it behaves differently.
  Consult Documentation: Refer to SAP documentation or help resources for specific details related to the retrieval process you are working with, as the context can vary widely depending on the module and configuration.
  
  Related Information:
  
  Transaction Codes: Depending on the context, you may want to check transaction codes like SM37 (Job Monitoring) to see the status of background jobs or SLG1 (Application Log) for detailed logs.
  SAP Notes: Search for relevant SAP Notes in the SAP Support Portal that may address specific issues related to the FG679 message.
  Community Forums: Consider checking SAP Community forums or other user groups for discussions related to this error message, as other users may have encountered similar situations.
  
  If the issue persists or if you need more specific guidance, it may be beneficial to consult with your SAP Basis or functional team for further investigation.