How To Fix PU731 - Import transport again

PU731 - Overview

• Message type: E = Error

• Message class: PU - Upgrade and Transport Log Messages

• Message number: 731

• Message text: Import transport again

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 PU731 - Import transport again ?

  The SAP error message PU731 ("Import transport again") typically occurs during the transport of objects in the SAP system, particularly when there is an issue with the transport request or the objects being imported. This error can arise due to various reasons, including inconsistencies in the transport request, missing objects, or issues with the transport directory.
  Causes:
  
  Incomplete Transport Request: The transport request may not have been fully completed or may be missing some objects.
  Transport Directory Issues: There could be issues with the transport directory, such as missing files or incorrect permissions.
  Dependencies: The objects being transported may have dependencies on other objects that are not included in the transport request.
  Version Conflicts: There may be version conflicts between the source and target systems.
  Transport Layer Issues: The transport layer may not be correctly configured, leading to issues during the import process.
  
  Solutions:
  
  Re-import the Transport Request: As the error message suggests, try to re-import the transport