How To Fix OT161 - EPS file &1 already exists in transport subdirectory EPS/out

OT161 - Overview

• Message type: E = Error

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

• Message number: 161

• Message text: EPS file &1 already exists in transport subdirectory EPS/out

What causes this issue?

EPS file &v1& already exists in transport subdirectory EPS/out.

System Response

The EPS file transfer is not performed.

How to fix this error?

Ensure that the EPS file does not yet exist in transport subdirectory
EPS/out.

Procedure for System Administrators

What causes this issue?

Error message extract from SAP system. Copyright SAP SE.

OT161 - Details

• The SAP error message OT161 indicates that there is an issue with the transport directory, specifically that a transport request file (EPS file) already exists in the specified transport subdirectory (EPS/out). This typically occurs when you are trying to export or import a transport request, and the system detects that a file with the same name already exists.
  
  Cause:
  
  File Already Exists: The most common cause is that a transport request with the same name has already been created and exists in the EPS/out directory.
  Incomplete Deletion: If a previous transport request was not properly deleted or cleaned up, it may leave behind files that conflict with new requests.
  Concurrent Processes: Multiple processes trying to create or export transport requests simultaneously can lead to this error.
  
  
  Solution:
  
  
  Check Existing Files: Navigate to the transport directory on the server (usually located at /usr/sap/trans/EPS/out) and check for existing files. If a file with the same name exists, you