Hook for WIP Job Component Revision Backflush
(Doc ID 2352683.1)
Last updated on MARCH 27, 2019
Applies to:Oracle Work in Process - Version 12.2.4 and later
Information in this document applies to any platform.
In a vertical integration situation requires to manufacture and backflush sub-assemblies in
the same organization. When a sub-assembly is in the process of a revision change, there is a wait to
implement the ECO until ready to manufacture the new revision. When ready to
manufacture the sub-assembly the ECO is implemented with an immediate effective date. This
allows production of inventory with the new revision. However, there is still on-hand inventory
for the previous revision that most times can be consumed to reduce obsolescence cost.
Currently move transactions for the parent assembly, backflush the current effective
implemented revision of the sub-assembly, in this case the new revision, even though there is
physical consumption of the previous revision. This backflush results in an inaccurate revision
transactions associated with a particular job and inventory inaccuracy. The goal would be to
make the electronic transaction match the actual consumption on the manufacturing floor.
Electronic transaction match the actual consumption on the manufacturing floor
The issue can be reproduced at will with the following steps:
1. Customer looking for implementation to provide a hook to default component revision during the run the move backflush.
Can check and add their revision change code business logic there.
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