How To Fix PU820 - No transport information for specified user/transport found

SAP Error Message - Details

• Message type: E = Error

• Message class: PU - Upgrade and Transport Log Messages

• Message number: 820

• Message text: No transport information for specified user/transport found

What causes this issue?

User information and request-specific information about transports
which were carried out is stored in files in the central transport
directory. It was not possible to access the corresponding files for
any of the specified users (&V1&) or transport requests (&V2&). The
files no longer exist or they could not be opened.

System Response

The function terminates.

How to fix this error?

First try to determine the transport i nformation for another user or
transport request selection. It is possible that the users you selected
really did not carry out any transports or the selected transport
requests do not exist or they were not transported or they were
transported too long ago.
If the error does not depend on the user or transport request selection
and you are sure that you have selected users who carried out
transports recently, contact your system administrator. It is possible
that the central transport directory cannot be reached or that
incorrect authorizations were granated at operating system level.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message PU820 - No transport information for specified user/transport found ?

  The SAP error message PU820 ("No transport information for specified user/transport found") typically occurs when there is an issue with the transport management system (TMS) in SAP. This error indicates that the system cannot find the transport request or the associated transport information for the specified user.
  Causes:
  
  Missing Transport Request: The transport request you are trying to access may not exist or may have been deleted.
  User Authorization: The user may not have the necessary authorizations to access the transport request.
  Transport Directory Issues: There may be issues with the transport directory or the transport management configuration.
  Transport Request Not Released: The transport request may not have been released, making it unavailable for transport.
  Incorrect User Assignment: The transport request may not be assigned to the user trying to access it.
  
  Solutions:
  
  Check Transport Request: Verify that the transport request exists in the system. You can do this by using transaction code SE09 or SE10 to view the transport requests.
  User Authorizations: Ensure that the user has the necessary authorizations to access the transport request. You may need to check the user's roles and profiles.
  Release Transport Request: If the transport request is not released, you can release it using transaction SE09 or SE10.
  Check Transport Directory: Ensure that the transport directory is correctly configured and that there are no issues with the transport paths.
  Reassign Transport Request: If the transport request is not assigned to the correct user, you may need to reassign it or create a new transport request.
  Transport Logs: Check the transport logs for any additional error messages or information that may help diagnose the issue.
  
  Related Information:
  
  Transaction Codes: SE09 (Transport Organizer), SE10 (Transport Organizer for Workbench Requests), STMS (Transport Management System).
  Authorization Objects: Check for authorization objects related to transport management, such as S_TRANSPRT.
  SAP Notes: Search for relevant SAP Notes in the SAP Support Portal that may address specific issues related to transport management and error PU820.
  Transport Management Configuration: Review the TMS configuration to ensure that all systems are correctly connected and that the transport routes are properly defined.
  
  If the issue persists after trying the above solutions, it may be beneficial to consult with your SAP Basis team or SAP support for further assistance.