How To Fix ILM_STOR653 - Transfer already taking place, a second call is not possible

ILM_STOR653 - Overview

• Message type: E = Error

• Message class: ILM_STOR -

• Message number: 653

• Message text: Transfer already taking place, a second call is not possible

What causes this issue?

Buffering takes place in two steps: First the data is transferred, then
it is inserted into the database.
The transfer phase can be spread out over multiple requests. However,
the URI of the resource is transferred with the first request. In all
additional requests the corresponding handle, which was returned as a
result of the first request, must be transferred.
In the current case, a second PUT request was sent for a URI. However it
was sent without a handle so that it was again handled like a first
request.

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

System Response

The procedure is terminated.

How to fix this error?

To correct this programming error, a program change has to be made.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

ILM_STOR653 - Details

• The SAP error message ILM_STOR653 ("Transfer already taking place, a second call is not possible") typically occurs in the context of Information Lifecycle Management (ILM) when there is an attempt to initiate a data transfer that is already in progress. This can happen in scenarios where multiple processes or users are trying to execute the same transfer operation simultaneously.
  
  Cause:
  
  Concurrent Transfers: The most common cause is that a data transfer process is already running, and a second attempt to start the same transfer is made before the first one has completed.
  System Locking: The system may have a locking mechanism that prevents multiple instances of the same transfer from being executed at the same time.
  Long-running Processes: If the initial transfer takes longer than expected, subsequent attempts may trigger this error.
  
  
  Solution:
  
  Check Running Processes: Use transaction codes like SM37 (Job Monitoring) to check if there are any active jobs related to the transfer. If