Locking Objects in Tasks and Requests
This section only refers to lockable objects (all Workbench objects are lockable; some cross-client Customizing objects are also defined as lockable).
If you create or change an object as part of a development project, the object is assigned to a change request.
The first user who starts work on an object has to specify a change request where the work will be recorded. This locks the object so that it can only be changed by users who are working on a task within the change request.
All users working on the object have a corresponding entry in the object list of their task. This enables you to determine which users have actually edited the object.
Object locks are deleted when change requests are released. The objects can then be edited again by all developers within the Transport Organizer.
If you enter objects manually in the object list of a task or request, these objects are not locked. There are two ways in which you can protect these objects from being changed by a third party.
In the request overview of the Transport Organizer (SE09), choose Request/task
In the request editor, select the object you want to lock on the Objects tab page while in change mode and choose Lock object.
You can usually only release requests when all the objects they contain have been locked. This makes sure that only released object versions are exported and that inconsistent intermediate versions are not imported into other SAP Systems. Exceptions: You have administration authorization or the request is a transport of copies. For more information, seeReleasing Requests.