+13Hi All.
I’ve just updated APPS10 from UPD14 to 17 and I’m getting this failed transaction in Aurena Mobile MWO Maintenance 10.
The Assgnment is updated but the error occurs and also the flag “transfered to mobile” in worktask is still checked.
Instance of entity MOBILE_WORK_ORDER with objid [AAAT4TAAGAAAXsMAAl] not found in database.
Tried to find this mobile seq in tab but there is not anymore.
Tks a lot
Best answer by Bandula
Hi, We fixed a similar issue under Bug id 164281 - FT upon Complete & Return Work Assignment
Please see whether that fix is applied.
+14Hi,
This failed transaction is related to a RETURN state event of the mobile work order. Three scenarios,
(1) Could be the work order is already retuned (Work Assignment completed) and then there is no entity exist in the back end table for mobile work order because it’s not transferred to mobile user.
(2) May be some one manually process FTs caused this work assignment to complete (Result would be delete mobile work order). Can’t explain exact scenarios unless check all the deleted Failed Transactions and some other logs.
(3) Could be a bug in the Mobile Work Order logic where mobile Work Order DELETE happens bit early. Can remember there was a bug in the application.
Ping
Thanks
Kapila
+12Hi, We fixed a similar issue under Bug id 164281 - FT upon Complete & Return Work Assignment
Please see whether that fix is applied.
+13Hi, We fixed a similar issue under Bug id 164281 - FT upon Complete & Return Work Assignment
Please see whether that fix is applied.
Hi
Tks a lot
+13Hi,
This failed transaction is related to a RETURN state event of the mobile work order. Three scenarios,
(1) Could be the work order is already retuned (Work Assignment completed) and then there is no entity exist in the back end table for mobile work order because it’s not transferred to mobile user.
(2) May be some one manually process FTs caused this work assignment to complete (Result would be delete mobile work order). Can’t explain exact scenarios unless check all the deleted Failed Transactions and some other logs.
(3) Could be a bug in the Mobile Work Order logic where mobile Work Order DELETE happens bit early. Can remember there was a bug in the application.
Ping
Thanks
Kapila
Hi
Tks a lot
+13Did you manage to get this issue fixed?
Hi,
Br.
Lopes
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
