Backflushing, Multi-Level Backflushing, and Issue Codes

Reducing effort is an important JIT function.  One way the JIT module accomplishes this is by reducing inventory transaction recording, which occurs when a completed part is received from the floor.  When a flow receipt is generated, all of the part's components are issued, regardless of whether the parts are MRP or JIT, or have issue codes "R," "S," or "T."  Backflushing or multi-level backflushing are methods for recording the receipt and issuance of parts.

With backflushing, when a completed part is received from the floor only a single simultaneous issue and receipt (SIR) transaction is recorded, instead of recording both parent receipt and components issue transactions. 

Multi-level backflushing is very similar to backflushing; however, when the parent is received, components at all levels in the bill of material can be automatically received/issued, rather than just the first-level component.  Only components having an issue code of "T" may be multi-level backflushed.

Related

• Issue Codes
• Where Do You Define Issue Codes?
• Validation Rules for Issue Code "T"
• Backflushing
• Multi-Level Backflushing