How To Fix OT158 - EPS file &1 does not exist in transport subdirectory EPS/out

SAP Error Message - Details

• Message type: E = Error

• Message class: OT - SAP Online Correction Support (SOCS)

• Message number: 158

• Message text: EPS file &1 does not exist in transport subdirectory EPS/out

What causes this issue?

EPS file &v1& does not exist in the transport subdirectory EPS/out of
the target host specified in RFC destination &v2&.

System Response

The EPS file transfer is not performed.

How to fix this error?

Make sure that the EPS file exists in the transport subdirectory
EPS/out.

Procedure for System Administrators

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message OT158 - EPS file &1 does not exist in transport subdirectory EPS/out ?

  The SAP error message OT158 indicates that the system is unable to find a transport request file in the specified transport subdirectory (EPS/out). This typically occurs during the transport of objects between SAP systems, such as when you are trying to release or import a transport request.
  Cause:
  
  Missing Transport File: The transport file specified in the error message does not exist in the EPS/out directory. This could be due to a failed transport export or a manual deletion of the file.
  Incorrect Transport Directory: The transport directory may not be correctly configured in the system settings.
  Transport Request Not Released: The transport request may not have been properly released, leading to the absence of the required files.
  File System Issues: There may be issues with the file system, such as permissions or disk space problems, preventing the creation or access of transport files.
  
  Solution:
  
  Check the EPS/out Directory: Navigate to the transport directory on the file system and verify if the specified EPS file exists. The path is typically something like /usr/sap/trans/EPS/out/.
  Re-export the Transport Request: If the file is missing, you may need to re-export the transport request from the source system. Ensure that the transport request is released properly.
  Check Transport Directory Configuration: Verify the transport directory settings in the SAP system. You can check the configuration using transaction RZ10 or RZ12 to ensure that the transport paths are correctly set.
  Check for File System Issues: Ensure that the file system where the transport directory resides has sufficient space and that the SAP user has the necessary permissions to read/write in that directory.
  Transport Management System (TMS) Configuration: Ensure that the Transport Management System is correctly configured and that all systems in the transport landscape are properly connected.
  Check Logs: Review the transport logs for any additional error messages that might provide more context on why the file is missing.
  
  Related Information:
  
  Transaction Codes: 
  
  SE01 - Transport Organizer
  SE09 - Workbench Organizer
  SE10 - Customizing Organizer
  
  
  SAP Notes: Check SAP Notes related to transport issues for any known bugs or additional troubleshooting steps.
  Documentation: Refer to SAP Help documentation for detailed information on transport management and troubleshooting transport issues.
  
  If the problem persists after following these steps, consider reaching out to your SAP Basis team or SAP support for further assistance.