How To Fix PU773 - Import end of &1 to &3 detected with return code &2 (&4)

SAP Error Message - Details

• Message type: E = Error

• Message class: PU - Upgrade and Transport Log Messages

• Message number: 773

• Message text: Import end of &1 to &3 detected with return code &2 (&4)

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 PU773 - Import end of &1 to &3 detected with return code &2 (&4) ?

  The SAP error message PU773 indicates that there was an issue during the import process of a transport request. The message typically includes details such as the transport request number, the return code, and possibly additional information that can help diagnose the problem.
  Cause:
  The error message PU773 can occur due to several reasons, including but not limited to:
  
  Transport Request Issues: The transport request may be incomplete or corrupted.
  Authorization Problems: The user performing the import may not have the necessary authorizations to complete the import.
  System Configuration: There may be inconsistencies in the system configuration or settings that prevent the import from completing successfully.
  Dependencies: The transport request may depend on other requests that have not been imported yet.
  Database Issues: There could be database-related issues, such as locks or connectivity problems.
  
  Solution:
  To resolve the PU773 error, you can follow these steps:
  
  Check the Transport Logs: Review the transport logs for more detailed error messages that can provide insight into what went wrong during the import process.
  Verify Transport Request: Ensure that the transport request is complete and not corrupted. You can check the status of the transport request in the Transport Management System (STMS).
  Check Authorizations: Make sure that the user performing the import has the necessary authorizations to execute the transport.
  Review Dependencies: Check if there are any dependent transport requests that need to be imported first. Import them in the correct order.
  System Configuration: Verify that the system configuration is correct and consistent. This includes checking for any configuration changes that may have been made recently.
  Database Health: Ensure that the database is functioning correctly. Check for any locks or connectivity issues that may be affecting the import process.
  Retry the Import: After addressing any identified issues, try to re-import the transport request.
  
  Related Information:
  
  Transaction Codes: You can use transaction codes like STMS (Transport Management System) to manage transport requests and check their status.
  SAP Notes: Search for relevant SAP Notes in the SAP Support Portal that may address specific issues related to the PU773 error.
  Documentation: Review SAP documentation related to transport management for best practices and troubleshooting steps.
  
  If the issue persists after following these steps, consider reaching out to SAP support for further assistance, providing them with the detailed error logs and any relevant information about the transport request.