Operation pull backflush transactions automatically pull inventory for all Operation Pull components defined at the operation. They also pulls components for all non-backflush operations between the current operation and the last completed backflush operation. Whether the backflush occurs automatically during a move transaction is determined by the whether the operation is or is not defined as a backflush operation. See: Operations. and Creating a Standard Operation.

   Backflush Operations:

You cannot backflush at operations that are specified as non-backflush operations. If you assign Operation Pull components to non-backflush operations these components are backflushed at a backflushing operation later in the routing. The last operation in the routing should always be defined as a backflush operation to ensure that all Operation Pull components are backflushed by the end of the routing.

   Count Point and Autocharge Operations:

When you define operations in Oracle Bills of Material, you can specify whether an operation is a count point and whether resources at that operation should be automatically charged during a move transaction. You can update this information in Work in Process using the Operations window. Operations that are non-count point/autocharge operations must be defined as backflush operations. See: Count Point and Autocharge Fields.

   Negative Requirements Backflushes:

When Operation Pull components that have negative requirement quantities are backflushed, they are returned to instead of supplied from inventory.