PM with route does not generate parent work order

Issue: PM does not generate Parent work orders, but generate child work orders

Solution: Most of the PMs have a route associated with it and has multiple job plans associated with each PM. We noticed the Parent work orders were not created, but the child work orders were created. The Child work order has the parent WO number tagged with it, but if you navigate to the parent wo, the record doesn't exist in the system.

I verified the parent work order from workorder, workview, wostatus objects, but the record doesn't exist in any object.

After enabling logging I noticed the parent work order was created, but the system  is deleting the record from all relevant objects.

So I picked up the PM (The PM has a route with multiple job plans) which was having a problem and tried to generate work orders manually. I noticed that after successfully generating work orders, the system is trying to save the PM and while saving the PM an error is displayed "Record has been updated by another user" and as the PM wasn't successfully saved, the system is trying to delete the work order generated. But to my surprise, system is deleting only the parent PM work order, but not child work order and other relevant activities - This could be a Maximo bug.

Now coming to reason why the PM was not successfully saved: the system is trying to update JPSEQINUSE to 1 (the current value is 0) as there are multiple job plans associated with the PM. We identified the PMs were loaded through MIF and the JPSEQINUSE was set to 0 irrespective of the multiple job plans associated with the PM.