Hierarchy
SAP_AP (Software Component) SAP Application Platform⤷
AP-PRC-CON (Application Component) Condition Technique⤷
/SAPCND/TRANSPORT (Package) Transport: Objects of All Types 
Attribute
| Message class |  |
/SAPCND/TRANSPORT | |
| Short Description |  |
Condition Technique - Transportation | |
| Message Number |  |
027 | |
| Documentation status | Space: object requires documentation |
||
| Authorization check Error Message | |||
| Changed On |  |
20050219 |
Message Text
Help Document
Diagnosis
User who is currently executing condition maintenance, or who is in a transaction that initialized a condition maitenance session, has a read lock for the generation run of the after-import method for transport object R3TR TDAT /SAPCND/CUSTOMIZING (FB ,/SAPCND/CUS_AFTER_IMP_FCT_TRN), that that causes the generator of condition technique objects a runtime error.
During the generation run, the DDIC time stamp of DDIC objects to be generated, and DDIC objects in the generating programs are updated. If users have loaded these programs into the system, and if generation were to run simultaneously, this could lead to a deadlock situation that would 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 error to prevent this deadlock situation.
Procedure
Make sure that user ends his transaction. However, it is possible that other users also have shared locks.
Procedure for System Administration
In order to maintain an overview, which users have a shared lock for the generation 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 ensure that 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 will probably not produce a deadlock situation. If the lock remains, the generation run needs to be repeated.
History
| Last changed on/by | |
20130528 | SAP |
| SAP Release Created in | 20C |
