Previous | Next | Contents | Index | Navigation | Glossary | Library |
For example, if you define the trigger 'Department = (equals) Inspection' for the Move Transaction collection transaction, data collection can be invoked each time assemblies are moved into the Inspection department. Furthermore, you can define this trigger regardless of whether the Department context element has been explicitly added to the collection plan because values for context elements are automatically saved in the quality data repository when you enter the parent transaction.
The following table lists the relationships between the various collection transactions and their associated context elements/triggers:
Purchasing Transactions | WIP Transactions | Service Transactions | |
---|---|---|---|
Context Element/ Trigger | Receiving and Inspection | Move | Service Request |
Actual Resolution Date | |||
ASL Status | |||
Customer | |||
Department | |||
Destination Type | |||
Expected Receipt Date | |||
Expected Resolution Date | |||
From Op Seq Number | |||
From Intraoperation Step | |||
Hazard Class | |||
Incident Type | |||
Inspection Result Action | |||
Item | |||
Item Category | |||
Item Description | |||
Job | |||
Location | |||
Locator | |||
Lot | |||
Operation Code | |||
Order Type | |||
Ordered Quantity | |||
Owner | |||
PO Line Number | |||
PO Number | |||
PO Release Number | |||
PO Shipment | |||
Parent Transaction Quantity | |||
Problem Code | |||
Production Line | |||
Quantity | |||
Reason Code | |||
Resolution Code | |||
Requestor | |||
Revision | |||
Sales Order Number | |||
Serial Number | |||
Severity | |||
Subinventory | |||
Supplier | |||
Supplier Description | |||
Supplier Lot Number | |||
To Intraoperation Step | |||
To Operation Code | |||
To Op Seq Number | |||
To Department | |||
Transaction Date | |||
Transaction Type | |||
UN Number | |||
UOM Name | |||
Urgency | |||
Vendor Item Number | |||
Table 1 - 9. (Page 3 of 3) |
Previous | Next | Contents | Index | Navigation | Glossary | Library |