Kanban Card Is Not Always Allocated When Calling API inv_kanban_pub.Update_Card_Supply_Status
(Doc ID 2478397.1)
Last updated on FEBRUARY 28, 2019
Applies to:Oracle Inventory Management - Version 12.2.6 and later
Information in this document applies to any platform.
Kanban cards are not always being allocated after replenishment when using API inv_kanban_pub.Update_Card_Supply_Status.
To replenish a Kanban card, API inv_kanban_pub.Update_Card_Supply_Status is being used.
This procedure creates a Move Order (replenish) for a Kanban card.
For the item, the source type of the Kanban card is Intra Org, and the Auto allocate flag is checked.
Sometimes after calling the API, the move order is created but without an allocation.
On-hand is available to transact, but the generated move order is missing the allocation.
The move order can be manually allocated by opening the Transact Move Order form, querying for the Move Order,
checking the Select checkbox, and clicking the Allocate button. Doing this allocates the move order.
This provides evidence that the Move Order should be allocated when using the API.
After restarting the Mobile Server (the API is used via mobile), the next Kanban card is allocated correctly.
When capturing the INV Debug log for a case when the allocation does not occur, debug messages for procedure INV_QUANTITY_TREE_PVT are missing.
A debug log when allocation is successful reveals there are many message for procedure INV_QUANTITY_TREE_PVT.
Due to this issue, when a production worker creates the Kanban card replenishment, it does not always allocate so after some time production is stopping because material is not delivered.
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