Lock Object Types 

A token key contains the logical system, the standard lock object, and the lock argument (or concatenated lock arguments). The last two parts of the key are used to identify the standard lock object within a system.

Internally, the CSL maps the name of the standard lock object onto a lock object type. Before you can use the CSL, developers must define the lock object types in the Customizing function. Changes to lock object types in a production system can cause problems if tokens have already been generated.

Lock object types are cross-release and cross-component, and enable you to assign local objects in different systems with different standard lock objects to one token.

Using the Lock Object Type

In CRM, requests are replicated from the ERP System into the CRM system. If you want to use the CSL in this scenario to lock the replicated objects in multiple systems, remember that the request in the CRM system uses a different standard lock object than in the ERP system, but both objects must be locked if changes are made. This is where the lock object type comes into play. For lock requests, the CSL uses a lock object type and a defined mapping of the standard lock objects to this type to recognize that it is the same token that is requested.

The CSL does not support mapping for the logical system or the lock argument of the token. This means that, for this example, the CRM developers and the ERP developers have to agree on a request number and a logical system for calling the CSL.