![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
|
Previous | Next | Contents | Index | Navigation | Glossary | Library |
For example, if you add the Lot Number collection element to a collection plan, before adding the Item collection element, you are warned that you should add Item to the collection plan before adding Lot Number. The following table lists all context dependencies.
Context Element... | ..Depends On (Add first) |
---|---|
From/To Operation Sequence | Job Name or Production Line |
From/To Intraoperation Step | From/To Operation Sequence |
Production Line | Item (Repetitive) |
Subinventory | Item |
Locator | Subinventory |
Serial Number | Item |
Lot Number | Item |
Revision | Item (under revision control) |
Unit of Measure | Item |
Component Subinventory | Component Item |
Component Locator | Component Subinventory |
Component Revision | Component Item |
Component Lot Number | Component Item |
Component Serial Number | Component Item |
Component Unit of Measure | Component Item |
PO Line Number | PO Number |
PO Release Number | PO Number |
Project | Task |
SO Line Number | Sales Order Number |
Table 1 - 6. Collection Element Dependencies |
You can choose to save a collection plan that you have added a dependent collection element (Lot Number) to even if you do not add the collection element that it is depends on (Item). However, when you enter results using this collection plan, the field for the dependent collection element (Lot Number) is disabled and you are prohibited from entering results.
It is possible to sequence collection plan elements so that a dependent collection element (Lot Number) precedes the collection element it depends on (Item). In this case, as you enter results, the Lot Number field remains disabled until Item results are entered.
Previous | Next | Contents | Index | Navigation | Glossary | Library |