PJM - On Hand Quantities Lying in Staging Project Locators with No Other Segments Populated than Project (and Task) Segment(s)
Last updated on JULY 21, 2017
Applies to:Oracle Warehouse Management - Version 12.1.1 and later
Oracle Project Manufacturing - Version 12.1.1 and later
Oracle Inventory Management - Version 12.1.1 and later
Information in this document applies to any platform.
Find Sales order issue transactions stuck in the Inventory material transactions open interface table MTL_TRANSACTIONS_INTERFACE with the following error.
Related organization is PJM enabled.
The problem occurs with sales order lines with a project (and task) stamped.
The following happened:
Related delivery detail lines got staged but the pick release (pick confirm or Transact Move Orders form) moved the material into dummy staging locators with no other segments populated than the project (and task) segment(s). Example: "...<project>.<task>"
Then the Interface Trips Stop created Sales order issue transactions that got stuck in the transactions open interface with error "Negative balances not allowed" because no Locator (and no project) is stamped on these Sales order issue transactions.
Negative balances not allowed
The issue can be replicated at will per the below steps:
1. Get on hand quantities for two items defined as below:
Item 1 with Locator Control = No locator control
Item 2 with Locator Control = Dynamic entry
2. Create two sales orders, one for each item, both with a project (and task) stamped on the sales order line
3. Release the two sales orders with Auto Allocate=No and Auto Pick Confirm=No
4. Query the sales orders in Transact Move Orders form
In Transact Move Orders window:
Select the line
Close the form
5. Ship confirm the sales orders eg launch the Interface Trip Stop for the related deliveries
6. Review the open interface transactions
See the Sales order issue transactions are stuck with error "Negative balances not allowed"
-- Business impact
Due to this issue, the shipped material is still lying in the staging subinventory (in the system) which is inaccurate data.
A data fix procedure is required to resolve the stuck transactions.
Also the issue will prevent users from closing the Inventory accounting period. (due to the related unprocessed shipping transactions)
The problem started to occur when users suddenly started to associate projects (and tasks) to sales order lines for this shipping organization.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms