How To Fix GD172 - Transfer started by &1

SAP Error Message - Details

• Message type: E = Error

• Message class: GD - EDT: External data transfer

• Message number: 172

• Message text: Transfer started by &1

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 GD172 - Transfer started by &1 ?

  The SAP error message GD172 ("Transfer started by &1") typically indicates that a transfer process has been initiated, but there may be issues related to the transfer that need to be addressed. This message is often associated with data transfer processes in SAP, such as those involving the transfer of data between systems or within different modules of SAP.
  Cause:
  
  Transfer Process Initiation: The message indicates that a transfer has been initiated by a specific user or process (denoted by &1). This could be due to a manual action or an automated process.
  Incomplete Transfer: The transfer may not have completed successfully due to various reasons, such as network issues, system performance problems, or data inconsistencies.
  Authorization Issues: The user initiating the transfer may not have the necessary authorizations to complete the process.
  Configuration Issues: There may be configuration settings in the SAP system that are not correctly set up for the transfer to proceed.
  
  Solution:
  
  Check Transfer Status: Verify the status of the transfer process. You can do this by checking the relevant transaction logs or monitoring tools in SAP.
  Review Logs: Look at the application logs (transaction SLG1) for any additional error messages or warnings that may provide more context about the issue.
  User Authorization: Ensure that the user who initiated the transfer has the appropriate authorizations to perform the action.
  Configuration Review: Check the configuration settings related to the transfer process. Ensure that all necessary parameters are correctly set.
  Network and System Performance: Investigate any network issues or system performance problems that may be affecting the transfer. This may involve checking network connectivity, server load, or database performance.
  Retry the Transfer: If the issue appears to be transient, you may attempt to re-initiate the transfer process after addressing any identified issues.
  
  Related Information:
  
  Transaction Codes: Depending on the context of the transfer, you may need to use specific transaction codes to monitor or manage the transfer process (e.g., SM37 for job monitoring, SLG1 for application logs).
  SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address known issues related to the GD172 message.
  Documentation: Review SAP documentation related to the specific module or process you are working with to understand the expected behavior and troubleshooting steps.
  
  If the issue 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.