Diagnosis
User &v1& who is currently executing condition maintenance, or who is ina transaction that initialized a condition maitenance session, has aread lock for the generation run of the after-import method fortransport object R3TR TDAT /SAPCND/CUSTOMIZING (FB,/SAPCND/CUS_AFTER_IMP_FCT_TRN), that that causes the generator ofcondition technique objects a runtime error.
During the generation run, the DDIC time stamp of DDIC objects to begenerated, and DDIC objects in the generating programs are updated. Ifusers have loaded these programs into the system, and if generation wereto run simultaneously, this could lead to a deadlock situation thatwould always interrupt generation silently.
You cannot prevent the above-described deadlock situation from occurring
, however, this is still not acceptable.

System Response
The program that the generator calls consciously forces a runtime errorto prevent this deadlock situation.

Procedure
Make sure that user &v1& ends his transaction. However, it is possiblethat other users also have shared locks.

Procedure for System Administration
In order to maintain an overview, which users have a shared lock for thegeneration run, choose transaction SM12 with the table name ='/SAPCND/GENERATOR_LOCK', across client and users.
If it is not possible to (for example in a productive system) to ensurethat all users leave the transaction, or if user locks were not removed,then it is possible to remove all locks in the system for table =/SAPCND/GENERATOR_LOCK using SM12 manually.
Thereafter, the generation run starts the after-import-method, and willprobably not produce a deadlock situation. If the lock remains, thegeneration run needs to be repeated.