Backflush transactions pull components with Operation Pull and Assembly Pull supply types from inventory onto jobs and repetitive schedules. Backflush transactions can be launched by:
Completing assemblies at operations using the Move Transactions window
Moving and completing assemblies into inventory using the Move Transactions window
Completing assemblies into inventory using the Completion Transactions window
Receiving assemblies from an outside processing operation using the Oracle Purchasing, Enter Receipts window
Move transactions imported through the Open Move Transaction Interface can also create backflush transactions. Transactions imported through the Oracle Inventory, Inventory Transactions Interface can also create backflush transactions.
Additional Information: Backflushing reduces the number of manual material transactions required to process the discrete jobs and repetitive schedules.
You can reverse backflush transactions and automatically return backflushed components back to inventory. For example, pull components that are backflushed as you move assemblies to the next intraoperation step in a routing are automatically returned to inventory if you move assemblies to a previous step in the routing. Reverse backflush transactions can be created as you do the following:
Reverse operation completion transactions using the Move Transactions window
Return completed assemblies from inventory to jobs and schedules using the Completion Transactions
Move and return assemblies from inventory to jobs and schedules using the Move Transactions window
Return or correct transaction receipts in the Enter Returns or Enter Corrections windows in Oracle Purchasing
Move transactions imported through the Oracle Work in Process Open Move Transaction Interface can also reverse backflush transactions as can return transactions imported through the Inventory Transaction Interface.
Note: You can, if necessary, issue and return pull components to and from jobs and schedules to inventory using the Specific Component' option in WIP Material Transactions window.
For component items under revision control, the system always defaults the revision based on the item's current revision as of the date of the transaction. See: Item and Routing Revisions.
The following rules are enforced when performing backflush transactions:
An enabled default supply subinventory and, if required by the subinventory, locator must be defined for the component. See: Backflush Supply Subinventories and Locators
Routing references must be specified for non-standard discrete jobs. See: Defining Discrete Jobs Manually
Component item must be transactable. See: Status Attributes and Item Status Control
Subinventory you are backflushing from must be an asset subinventory if the Oracle Inventory Allow Expense to Asset Transfer profile option is set to No. See: Inventory Profile Options.
Backflush quantities in decimal values must be no more than five decimal places to create the backflush transaction.
The WIP: Ignore Zero Quantity Backflush profile option provides flexibility to choose whether to create errors or process the transactions when the backflush quantity transaction is less than the quantity of .000005. However, if processed in these cases, inventory transactions are not generated for quantities rounded to zero (0). See: WIP: Ignore Zero Quantity Backflush
Yield calculations are based on exact requirements, rather than rounded values.
Backflush transactions can be launched from the following windows:
Completion Transactions window. See: Assembly Pull Backflush Transactions
Move Transactions window. See: Operation Pull Backflush Transactions
Enter Receipts window in Oracle Purchasing. See: Entering Receipt Header Information
Transactions which reverse backflush transactions can be launched from the following windows:
Completion Transactions window
Move Transactions window
Enter Corrections in Oracle Purchasing. See: Entering Corrections
Enter Returns in Oracle Purchasing. See: Entering Returns
Assembly move completion and move return transactions imported through the Open Move Transaction Interface can also create and reverse backflush transactions. Similarly, assembly completion and return transaction imported through the Inventory Transaction Interface can create and reverse backflush transactions. See: Open Move Transaction Interface.
Assembly and Operation Pull components under lot, serial, or lot and serial number control can be backflushed. Push components that are requirements of work order-less schedules are always backflushed. The Backflush window provides efficient entry for large numbers of lot and serial controlled items when creating assembly move transactions - including scrap, reject, and assembly completion. This includes:
Transaction Quantity Defaulting
Transaction quantity for each backflushed component is defaulted to the required quantity.
Visual Indicators for Data Entry
Contrasting coloring on the Item field displays when information is required. The Lot and Serial button labeling corresponds to the information needed for each component.
Single Lot Entry
Lot information can be entered directly in the Backflush window, The Lot Entry window is accessed if a component is being consumed from more than one lot, or if serial number data is required on the Serial Entry window.
Lot Number Defaulting
When there are multiple backflush transactions for the same component on the same job, you can set the system to retain lot numbers used in the previous transactions. This value is used as a default for the current transaction.
Note: Backflush transactions occur either during move or completion transactions. Backflush transactions fail if the processing mode is set to background mode, and any of the following conditions exist for the component:
It is under serial control
It is under lot control and the lot derivation method is set to Manual
It is under lot control, but the lot cannot be derived
Work in Process parameters determine how lot numbers are assigned and verified during backflush transactions.
The Lot Selection Method parameter determines how lot controlled Assembly Pull and Component Pull component items are selected during backflush transactions. You can choose either manual or automatic methods. If the parameter is set to Manual, you must specify a valid lot number. You must also manually specify lot numbers if there is not enough on-hand inventory.
The Lot Verification parameter determines how lots are verified during backflush transactions.
The Lot Selection Method and Alternate Lot Selection Method parameters are used in combination with lot number defaulting. To default lot numbers previously transacted during backflush, set Lot Selection Method to Transaction History. In instances where there are no previous backflush transactions, the system uses the Alternate Lot Selection Method parameter to specify a method for selecting lots.
When you complete an assembly that has Assembly Pull components, these components are automatically pulled (backflushed) from their assigned supply subinventories/locators.
If the components being backflushed are under manual lot control, serial control, or lot and serial control, you must enter lot and/or serial numbers. If the job is tied to one or more sales orders, the system automatically completes the assembly for those orders.
Note: Purchasing transactions initiate backflushes only if they are tied to outside processing resources with an autocharge type of PO Move and only if requirements with a supply type of Operation Pull exist at the outside processing operation.