To associate collection plans with transactions:Once you setup and define a collection plan to be used with a transaction, you then must associate it with the transaction and enable it. This makes the associated collection plan available on the transaction's list of values when Quality collection is invoked.
To associate collection plans with transactions:Navigate to the Collection Plan window.
Select a Collection Plan.
Choose the Transactions button. The Collection Transactions window appears.
In the Quality Collection Transactions region, select a collection transaction. See: Quality Collection Transactions.
In the Workbench Layout field, select whether you want to enter a single set of results or multiple rows of results at one time when using the Quality Workbench.
This field is only enabled for those transactions that you can enter using the Oracle Applications Framework interface.
Optionally, check the Mandatory check box to indicate that quality data collection is mandatory when the transaction is entered, and that all of the conditions specified in the collection triggers, if any, must be met. If you do not check the Mandatory check box, you can skip quality result entry for this transaction.
Note: Mandatory is the default for Purchasing Receiving Transactions. Non-mandatory is the default for all other transactions, except for Purchasing Inspection transactions, which cannot be set to non-mandatory, and Oracle iSupplier Portal transactions, which ignore mandatory settings.
Optionally, check the Background check box to indicate that quality data collection occurs in the background. The default is non-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 perform a transaction associated with a collection plan marked 'background' and all the conditions specified in the collection triggers, if any, are met. Quality results are automatically saved as you save the transaction.
Attention: Inspection (Purchasing) collection transactions and Oracle iSupplier Portal transactions cannot be set to background (background settings for iSupplier Portal transactions are ignored).
Optionally, check the Enabled check box to indicate that data collection for this quality collection plan is enabled. The default is non-enabled.
This makes the collection plan available for quality data collection during transactional data entry.
To define triggers for collection plans used with transactions:Navigate to the Collection Triggers region.
Select the Trigger Name.
The trigger name specifies which context collection element is used to define the trigger. See: Reference Information Collection Elements.
Select the Condition that must be met to trigger results entry. See: Query Operators.
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 for the current transaction selected.
Just as you can create AND and OR relationships for transactions, you can create AND and OR relationships between triggers. To create an OR relationship between triggers, enter a second record for the same transaction in the Transaction Description field, within the Quality Collection Transactions region. For example, the windows below imply that, for the Line Operation Completion Transaction, the Item Category trigger must equal 060.00 AND the Line Operation trigger must be greater than 10 OR the Line Operation trigger must equal 20.
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.
Save your work.
