Change Request Lock
We have developed a custom equipment data model and have configured rule based WF and implemented access class methods SAVE, QUERY.
Now, when we try to create an equipment, WF gets stuck at all steps which require CR modification (eg: Changing CR Status) with message "Change Request is locked by user XXX"
The user in the above message is the one who has last processed the CR (eg: Requester, Approver)
If we manually remove the lock using SM12 and reprocess the work item, WF moves ahead without problems. Also, even in standard data models like MM, BP we notice that a lock entry is created in SM12 but it doesn't cause problems in WF.
Can someone please guide as to what needs to be done additionally to ensure these CR lock entries do not cause problems in WF processing?
We created a new data model and new CRs and now it works fine.
Not sure what the problem was.