An ERP Job number may appear in Matics as several different jobs if its production activities were discontinuous.
A job in Matics represents a specific production run, at a particular time period and using particular assets and resources. Changes in the asset allocation or as well as other interruptions in production that occur either before or during production will cause a job to be re-indexed in Matics.
Actions and changes that result in job re-indexing include the following:
Suspending a job that is to be continued at another time or at another work-station.
Splitting an ERP job into several runs to be produced simultaneously on several work-stations.
Transferring a job between work-stations mid-production due to a breakdown or another problem.
The Job Lifecycle Tree always displays the complete lifecycle of a single ERP Job. If you reach the tree from one of the downstream re-indexed branches, you will still see the complete tree.
Related articles