My Oracle Support Banner

After Disabling WMS Strategy and Running AutoDetail on a Batch Which was Previously AutoDetailed, Batch Reservation is Based on Disabled Strategy (Doc ID 2690838.1)

Last updated on JULY 15, 2020

Applies to:

Oracle Process Manufacturing Process Execution - Version 12.2.8 and later
Information in this document applies to any platform.

Symptoms

On : 12.2.8 version,

ACTUAL BEHAVIOR
---------------
Set up WMS picking strategy with two rules:
1. One to pick from subinventory 1,
2. And a second if no availability there, to pick from subinventory 2.

Have available inventory only in subinventory 2.
Run Autodetail on a batch to create a reservation based on the strategy/rules.
Material is reserved from subinventory 2, which is correct.

Then disable the strategy on Rules Workbench, and add the rule to only pick from subinventory 1, and run Generate rules.

On the batch which already had Autodetail run, delete the reservations.
Run Autodetail again. This time, nothing should be reserved, because the strategy is no longer enabled on Rules Workbench, only the Rule to select from subinventory 1, which has no available inventory.
However, the inventory in subinventory 2 is again reserved.

Create a new batch which did not have Autodetail run when the original strategy was enabled, and run Autodetail.
On this batch, we see the correct behavior, no reservation is created.

It turns out that when Autodetail was run the first time on the first batch, the pick_strategy_id was populated in mtl_txn_request_lines for the invisible move order (move_order_type 8) associated with the batch. This value then stays there, and Autodetail seems to use this strategy even after the strategy is no longer enabled on the Rules Workbench (and even after the strategy is disabled on the Strategies form).

Debug log from batch 1 shows two rule_id's, but debug log from batch 2 shows only one rule_id.

EXPECTED BEHAVIOR
-----------------------
Expect that if only currently enables strategies and rules be used, not a disabled on just because it was used previously on the batch.

Cause

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
Symptoms
Cause
Solution
References


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