My Oracle Support Banner

Bogus AQ Transaction In Storeroom Log (Doc ID 758000.1)

Last updated on MARCH 20, 2019

Applies to:

Oracle Utilities Work and Asset Management - Version 1.7.15 and later
Information in this document applies to any platform.
This problem can occur on any platform.


The storeroom log shows an “AQ” transaction entry that should not be able to happen. This is how
it takes place:

User opens up the Storeroom module and locates the required stock code.
The User attempts to makes an inventory adjustment by selecting the 'Adjust Inventory Quantity'
A "New Quantity” amount and the “Adjustment Reason” are entered, but the User does NOT SAVE AS OF
The User leaves this module and goes to the Stock Check out screen to issue the same stock code
against a work order.
The stock code is issued.
The User returns to the Storeroom Module and tries to finish the Inventory Adjustment transaction.
As soon as the SAVE button on the inventory adjustment screen is selected, the User receives a
message informing them that the record has been updated by another user-requery is required to see
the change.
The User selects Undo and Refresh
The User then goes back under the “Actions” and clicks on “Adjust Inventory Quantity”.
User again enters a "New Quantity” amount and the “Adjustment Reason” and hits SAVE
Check the Storeroom Transaction Log.
The application shows 2 AQ transactions instead of one. It’s like the system has held on to the
1st “bad” transaction instead of letting it go (like it appears to the user because they got an
error message and did the “Undo” and “Refresh”) and posts it like it happened 5 seconds before the
good transaction.


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

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