How To Fix GD173 - Transfer started in the background

SAP Error Message - Details

• Message type: E = Error

• Message class: GD - EDT: External data transfer

• Message number: 173

• Message text: Transfer started in the background

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 GD173 - Transfer started in the background ?

  The SAP error message GD173, which states "Transfer started in the background," typically occurs when a background job is initiated for a data transfer process, and it indicates that the transfer is not being executed in the foreground. This can happen in various scenarios, such as during data uploads, migrations, or when using certain transaction codes that involve data processing.
  Cause:
  
  Background Job Initiation: The system is set to run the transfer process as a background job instead of in the foreground. This can be due to user settings or the way the transaction is designed.
  Long Processing Time: If the data transfer is expected to take a long time, the system may automatically switch to background processing to avoid timeouts or to allow the user to continue working.
  System Configuration: Certain configurations in the SAP system may dictate that specific processes run in the background.
  
  Solution:
  
  Check Job Status: Use transaction code SM37 to check the status of the background job. You can see if it is running, completed, or if there were any errors during execution.
  Review Job Logs: If the job has completed, review the job logs for any errors or warnings that may provide insight into what happened during the transfer.
  Adjust Settings: If you prefer to run the transfer in the foreground, check the transaction settings or user parameters to see if there is an option to change this behavior.
  Monitor Performance: If the transfer is taking too long, consider optimizing the data being transferred or the process itself to reduce the time taken.
  Consult Documentation: Refer to SAP documentation or notes related to the specific transaction or process you are using to see if there are known issues or recommended practices.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SM37 (Job Monitoring), SM21 (System Log), and ST22 (Dump Analysis) for troubleshooting.
  SAP Notes: Check SAP Notes for any updates or patches related to the specific transaction or process you are working with.
  User Roles and Authorizations: Ensure that the user has the necessary authorizations to execute the transfer in the desired mode (foreground vs. background).
  
  If the issue persists or if you need further assistance, consider reaching out to your SAP Basis team or SAP support for more detailed troubleshooting.