OPM Incremental Backflush Material Exceptions Defaulting Entire Planned Quantity Instead of Just Backflushed Quantity (Doc ID 1676574.1)

Last updated on AUGUST 03, 2017

Applies to:

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

Symptoms

On : 12.1.3 version, Batches

ACTUAL BEHAVIOR
---------------
When doing Incremental Backflushing in a situation where there is a valid reservation for a lot but it is either for a subinventory different than the supply subinventory or it does not specify subinventory and locator, the transaction that gets created is for the full planned quantity instead of the quantity that should be backflushed.

This can be reproduced in two ways:
1. With Auto Consume from Supply Subinventory Only checked, create a fully detailed reservation from a subinventory/locator different than the supply subinventory on the ingredient line. Note that this occurs if the subinventory on the ingredient line is blank or different than the one on the reservation.
2. Create a reservation for a lot without a subinventory/locator.

In either case, when you do IB, the Material Exceptions form displays. The top part of the form shows the correct Target Qty and Exception Qty (the correct calculated qty to be backflushed), but the actual transaction line on the bottom section of the form has the Transaction Qty equal to the entire planned quantity, not the backflushed quantity.

The problem does not occur when there is no reservation at all, because in that case when Material Exceptions displays, there is no row already in the transactions block, and when you click down into that block the transaction qty gets set correctly.

EXPECTED BEHAVIOR
-----------------------
Expect the transaction line to have the qty that is being backflushed, not the entire planned qty.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
See description above

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, the wrong quantities are being backflushed..

Cause

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