How To Fix GI737 - Not all documents were transferred

SAP Error Message - Details

• Message type: E = Error

• Message class: GI - FI-SL update

• Message number: 737

• Message text: Not all documents were transferred

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 GI737 - Not all documents were transferred ?

  The SAP error message GI737, which states "Not all documents were transferred," typically occurs during the process of transferring documents between systems or within the same system, such as during a goods movement, invoice verification, or other document-related processes. This error can arise due to various reasons, and understanding the cause is essential for finding an appropriate solution.
  Causes of GI737 Error
  
  
  Incomplete Document Transfer: The system may not have been able to transfer all the necessary documents due to network issues, system downtime, or other technical problems.
  
  
  Authorization Issues: The user may not have the necessary authorizations to view or transfer certain documents.
  
  
  Data Consistency Issues: There may be inconsistencies in the data being transferred, such as missing or incorrect entries in the database.
  
  
  Configuration Issues: Incorrect configuration settings in the SAP system can lead to problems in document transfer.
  
  
  Batch Input Issues: If the transfer is being done through batch input sessions, there may be errors in the session that prevent all documents from being processed.
  
  
  Solutions to GI737 Error
  
  
  Check System Logs: Review the system logs (transaction codes like SLG1) to identify any specific errors or warnings that occurred during the document transfer process.
  
  
  Verify Authorizations: Ensure that the user has the necessary authorizations to perform the document transfer. This can be checked in transaction SU53 or by consulting with your security team.
  
  
  Data Consistency Check: Run consistency checks on the relevant data to ensure that all required entries are present and correct. This may involve checking the relevant tables or using transaction codes like SE16 or SE11.
  
  
  Reprocess the Transfer: If the error occurred during a batch input session, you can reprocess the session using transaction SM35. Check for any errors in the session and correct them before reprocessing.
  
  
  Configuration Review: Review the configuration settings related to document transfer in the SAP system. This may involve checking settings in the relevant modules (e.g., MM, SD, FI).
  
  
  Consult SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error. There may be patches or updates that resolve known issues.
  
  
  Contact SAP Support: If the issue persists and cannot be resolved through the above steps, consider reaching out to SAP Support for further assistance.
  
  
  Related Information
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SLG1 (Application Log), SM35 (Batch Input Monitoring), and SU53 (Authorization Check).
  Documentation: Review SAP documentation and user manuals related to the specific module you are working with (e.g., MM for materials management, SD for sales and distribution).
  User Forums: Engage with SAP community forums or user groups where similar issues may have been discussed, and solutions shared.
  
  By following these steps, you should be able to diagnose and resolve the GI737 error effectively.