Redo job originating dynamic routing at end of dynamic process

Choices Are:

Yes/No

Default:

No

Enabled When:

Always

Meaning Depends on the Following Parameters:

None

Description:

If this parameter is set to Yes, a copy of the job at which the need for rework is determined is appended to the end of the set of jobs created from the dynamic routing process. This is the case when the same dynamic routing process might be appropriate after different original jobs, and yet require the work done in that original job to be done again after reworking, as in the case of an inspection job.

Even when rework is done as part of the same work order as the original production (i.e., when Dynamic Routing is a separate WO from original is set to No), to avoid double-counting the output of the originating job, the output of the dynamic routing jobs may not be returned to that job. Instead, a copy of the job is inserted. The copy of this job is identified as a dynamic routing job (i.e., the rework flag is set in the job table), just as it is for jobs instantiated from the dynamic routing process, since it is being done again due to the need for rework.

When Dynamic Routing is a separate WO from original is set to No, the output of this copied job is returned to the operation identified by the re-entry route code (if defined).