Examples: Backflushing and Control Points

Backflushing Example #1 illustrates backflushing as it works for jobs. Operation 30 is designated as a control point. If you enter a transaction and post it for quantity complete of 5, then the system will assume that the quantity 5, was also completed for operations 10 and 20. (This also assumes that this is the only transaction that has been posted against this job.)

Backflushing Example #1


Operation	Quantity	Control Point Complete?	Complete?
10	5	No	Yes
20	5	No	Yes
30	5	Yes	Yes
40	0	No	No
50	0	Yes	No

For jobs, if you complete the operation which serves as a control point, the prior operations tied to the control point will be completed. From the example above, if you keyed a transaction for Operation 30, Complete?, "Yes," Operations 10 and 20 will have records created as a result that would complete them.

The system does not assume that all operations or control points must have transactions entered and posted for them. The system does not require or validate that previous operations or control points have been posted. Using the same example, you can post Operation 50 with a quantity complete of 5 and Complete, "Yes," without having posted operation 30, or any other previous operation.

The system will not prevent you from doing this. However, only Operation 50 (and Operation 40 that is tied to it), will backflush. The system will not go back and backflush Operation 30 (and Operations 10 and 20 that are tied to it). This is illustrated in Backflushing Example #2.

Backflushing Example #2


Operation	Quantity	Control Point Complete?	Complete?
10	0	No	No
20	0	No	No
30	0	Yes	No
40	5	No	Yes
50	5	Yes	Yes