Process Flow for Cross-System Locks

Use

In this scenario we want to lock an object from system X in LUW A of system Y in all systems. System X is therefore the master system of the corresponding token. The process flow assumes that the token is not available locally in system Y (this is possible due to previous lock requests).

Prerequisites

  1. The CSL exists in system X.

  2. The CSL is activated in system Y for the lock object type that is assigned to the token.

Process

The application in system Y calls the CSLEO_ENQUEUE function module during the dialog of LUW A. If the prerequisites are not met, the call has no effect.

If the token is free when the lock is requested, the CSL moves the token from system X to system Y. This move is subject to its own transactional logic (LUWs A* and A**), which is independent of the application LUW A in system Y.

The graphic below illustrates this process flow. The red arrow shows the duration of the CSL: The CSL begins with the standard locking of the token in system X. This is required for blocking local lock requests while the token is being moved. The CSL ends with the release of the standard lock of the token in system Y. This release occurs implicitly at the end of LUW A.