E1: 31: Inbound Super Backflush - R31123Z1I Does not Process a Record Reserved Work Order but Removes the Record Reservation on the Locked Work Order (Doc ID 2998973.1)

Last updated on MARCH 04, 2024

Applies to:

Symptoms

After applying Bug 35839914 - R31123Z1I NOT PROCESSING RECORDS CORRECTLY, a work order that has a record reserved by Business Object Reservation (P00095) removes the record reservation on the Locked Work Order that is processed by the UBE.
The R31123Z1I (Inbound Super Backflush) removes the Record Reservation on the Work Order that a user is logged into, which is also included in the data selection from the R31123Z1I run. Now, another user could potentially go into that same Work Order from another maintenance screen, which could end up with some corruption since the UBE R31123Z1I removes the Business Object Reservation for the work order.  This could cause one of the two modifications being made to be overridden by the other.

STEPS:

1. P48013 - Create 2 or 3 Super Backflush Work Orders and attach them with the correct Super Backflush Routing.
2. Create 2- 3 inbound Super Backflush transactions in the P3112Z1
3. Reserve the last Work Order (Open WO via the P48013 and leave open)
4. Run UBE R31123Z1I with data selection of EDSP = Blank
5. In the result of the UBE, you will see that the locked Work Order is not updated (that is normal), but then when the user goes back into the Business reservations (P00095), the lock on the actual Work Order is removed. That means that the user that is still in the Work order revision screen, that Work Order now does not have the business reservation anymore, and anybody else can make a change and maybe create corruption.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.