Multi-Level Backflushing

Assume that parent A (which may be either a JIT part or an MRP part) is comprised of components B, C, D, and E, and there is a 1:1 relationship between A and each of the components.  (Part master or product structure scrap factors are assumed to be zero.)

A
|
B
|
C
|
D
|
E

      The Bill of Material for Part A

The table below demonstrates multi-level backflushing. 

             Multi-Level Backflushing

In this example, when 100 parents are received (part A), a flow receipt is automatically generated for 100 component B's and 100 component C's, because each of these components has an issue code of "T."  Because component D has an issue code of either "R" or "S," however, no flow receipts are created for it (although 100 component D's are issued).  Furthermore, component E is not backflushed.

Transfer Parts with Issue Code "T"

If a production schedule exists for a transfer part, it is processed as a manufactured part.  If no schedule exists, a stock transfer occurs automatically.  The issue and receiving locations are determined by the producing location, which is defined on the Part Master File (or the primary stock location if the producing location field is blank).

How Do You Multi-Level Backflush?

Multi-level backflushing is accomplished either through the Manufacturing Order Receipt conversation (IC130E) for manufactured or transfer JIT parts only or through the Flow Receipt conversation (JT120E) for manufactured or transfer JIT parts.  Note that scrap transactions are backflushed only one level.  If there are any components one level beneath the scrap component having "T" issue codes, they will be displayed in reverse image and will not be multi-level backflushed.  To multi-level backflush them, you will need to perform another transaction.