Backflush Operations in Discrete Manufacturing Behave Incorrectly with Component Write-off (Doc ID 1934973.1)

Last updated on OCTOBER 27, 2016

Applies to:

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

Symptoms


ACTUAL BEHAVIOR

We are trying to write off a backflushed component that does not have enough onhand and the system writes off another item


EXPECTED BEHAVIOR

Only the one backflushed component should be written off.


STEPS

The issue can be reproduced at will with the following steps:
1. Create a job
2. Issue material via backflush
3. Find a shortage in one component
4. Try to write off the one component
5. See an additional item written off


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