How To Fix GD199 - A new generation is automatically carried out at the next transfer

SAP Error Message - Details

• Message type: E = Error

• Message class: GD - EDT: External data transfer

• Message number: 199

• Message text: A new generation is automatically carried out at the next transfer

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 GD199 - A new generation is automatically carried out at the next transfer ?

  The SAP error message GD199, which states "A new generation is automatically carried out at the next transfer," typically relates to issues in the context of the SAP system's data transfer processes, particularly in the area of data archiving or data management.
  Cause:
  
  Data Transfer Issues: This message often indicates that there is a pending data transfer or archiving process that needs to be completed before the system can proceed with the next operation.
  Generation Management: The system is set to automatically generate a new version or generation of data during the next transfer, which may be due to changes in the data structure or configuration.
  Incomplete Processes: There may be incomplete or interrupted processes that are preventing the system from moving forward with the current operation.
  
  Solution:
  
  Check Background Jobs: Review the background jobs in the SAP system to see if there are any jobs related to data transfer or archiving that are currently running or have failed. You can do this using transaction codes like SM37.
  Monitor Data Transfer: Ensure that any data transfer processes are completed successfully. If there are any errors, resolve them before proceeding.
  Run the Transfer Manually: If the system indicates that a new generation will be created at the next transfer, you may need to manually trigger the data transfer or archiving process to ensure that it completes.
  Review Configuration: Check the configuration settings related to data archiving or transfer to ensure they are set up correctly. This may involve reviewing the settings in transaction SARA for archiving.
  Consult Documentation: Refer to SAP documentation or notes related to the specific module you are working with, as there may be specific instructions or patches available for your version of SAP.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SARA (Archive Administration), SARI (Archive Information System), and SM37 (Job Monitoring).
  SAP Notes: Check the SAP Support Portal for any notes related to error GD199, as there may be specific fixes or recommendations provided by SAP.
  System Logs: Review system logs (transaction SLG1) for any additional error messages or warnings that may provide more context about the issue.
  
  If the problem persists after following these steps, it may be beneficial to consult with your SAP Basis team or reach out to SAP support for further assistance.