SAP Note 18979 - Networking not possible for repairs

Symptom:

When you attempt to process an object whose original lies in a different system, error message TR695, TK183, TK310, or TR694 is issued. They state that the object cannot be processed because it is already locked in another repair or another request.

Cause and prerequisites

Networking of several users is not possible during processing of repaired objects to the same extent as with the processing of original objects. The reason for this is that the description of an object as a "repaired object" always refers to the entire object, and not to parts of it.
Therefore, parts of a total object can always only be processed under the same repair.
Examples of sub-objects that are part of the same total object are:
Function modules from the same function group
Individual messages from the same message class
Screens from the same module pool

Solution

The long text of the error message contains precise instructions on how to proceed. The repair number or request number for which the object has been locked and the corresponding user are named in the error message or in the long text.
The following rules form the foundation for processing repaired objects:

• Sub-objects of the same total object can only be processed at the same time by one user in one repair

• If another wants to process sub-objects from the same total object, the first user's repair must be released or the user name of the repair must be changed.

• If the repair has been released to a change request, but the change request has not been released yet, the objects can be processed under a new repair that belongs to the same change request. If the second user is not yet participating with a task in the change order, the function "Add employee" can be used to create a task for that user. The task is added to the first repaired object.

• If the change request itself has been released, the objects can be processed again under any repair.