Associating Transactions with Collection Plans
You can associate a collection plan with more than one collection transaction. Conversely you can associate more than one collection plan with each transaction. You can define a unique set of collection triggers for each collection transaction that you associate with a collection plan.
To associate collection transactions with collection plans:
1. Navigate to the Collection Plan window.
2. Select a Collection Plan.
If you do not check the Mandatory check box, you can skip quality result entry for this transaction.
The default is mandatory for Receiving Transactions in Purchasing and non-mandatory for all other transactions.
Attention: Receiving Inspection collection transactions cannot be set to non-mandatory
6. Check the Background check box to indicate that quality data collection occurs in the background. The default is non-background.
Attention: Receiving Inspection collection transactions cannot be set to background.
Background data collection allows you to collect quality results without invoking the Enter Quality Results window. Background data collection is initiated when a you enter a 'background' collection transaction and all the conditions specified in the collection triggers, if any, are met. Quality results are automatically saved as you save the transaction.
7. Check the Enabled check box to indicate that data collection for this collection plan quality data collection is enabled. The default is non-enabled.
When a collection transaction is enabled, the collection plan it is associated with can be selected and used for quality data collection during transactional data entry.
To define collection triggers for collection transactions:
1. Navigate to the Collection Triggers region.
The condition entered determines when quality data collection is triggered. For example, for the WIP move transaction you might choose to trigger data collection when assemblies are moved from the To Move intraoperation step of Operation Sequence 20 to the Queue intraoperation step of Operation Sequence 30. Before quality data collection can be invoked, all collection triggers and conditions must be met.
4. Based on the Condition, enter a value, or range of values for the specified trigger.
If the condition requires a single value enter only a From value. If the condition selected requires a range, you must enter both a From and To value.
Transactional Data Collection Fundamentals
Entering Quality Results for Move Transactions