Backflush happens when –
-
Line Hours job has run
-
Net yield program has run.
-
DVL program has run,
-
Only when all of the above have executed.
Backflush in SAP PP occurs when the Net Yield program has executed. This program calculates actual quantities consumed based on production confirmation and posts the goods movements automatically to inventory. The Line Hours job and DVL program are separate preprocessing steps that must complete before backflush can run, but they do not trigger it themselves.
Backflushing in SAP PP automatically posts goods issues for components/consumption at the point of order confirmation, based on a defined trigger. Per this course's process design, backflush is tied to the Net Yield program having run (rather than the Line Hours job or DVL program alone, or requiring all three), meaning the yield calculation step is what determines/triggers the material consumption posting in this org's custom production-confirmation sequence. This is bespoke process-flow logic specific to this client's implementation, so I can't independently verify the exact trigger dependency beyond the course material.