Previous  Next          Contents  Index  Navigation  Glossary  Library

Transactional Data Collection Fundamentals

Collection plans that have been associated with collection transaction can be used to collect quality results as you transact in other Oracle Manufacturing Applications. You can optionally define collection triggers so that quality data collection is invoked when certain transaction conditions are met. When invoked, data collection occurs either automatically in background or the Enter Quality Results window appears. See: Quality Collection Transactions and Associating Transactions with Collection Plans.

For example, if you create an In-Process Inspection collection plan and add the context elements Job, Item, and From/To Operation Sequence Numbers to it. You can then associate this collection plan with the Oracle Work in Process move transaction using the Collection Transactions window.

In this example, if you define the collection triggers 'Item equals (=) C31556' and 'From Operation Sequence equals (=) 20', when C31556 assembly items are moved From Operation Sequence 20, the system determines that the trigger conditions are met and the In-Process Inspection collection plan is automatically invoked.

Mandatory Data Collection

When you associate a collection transaction with a collection plan, you can choose whether data collection for the transaction is mandatory or whether it is optional. If you make a collection transaction mandatory, you must save at least one quality data record before saving the parent transaction.

For example, if all parts that are resurfaced at a grinding operation must be surface inspected before being moved to the next operation, you can make data collection at the grinding operation mandatory. You can do this by associating the collection plan and with the WIP move transaction and by defining the following collection trigger and trigger conditions:

When assemblies are moved from operation 40 to operation 60, the collection triggers are evaluated and data collection is automatically invoked. The operator must enter the results of the surface inspection before the move transaction can be completed and saved.

Attention: Inspection Transactions must always be made mandatory. See: Inspection Collection Plans.

Background Data Collection

Background data collection allows you to collect quality results for context elements without invoking the Enter Quality Results window. Collection plan that have collection transactions defined as 'background,' can be used to collection data in the background. Background data collection is initiated when a you enter a 'background' collection transaction, and the system finds, selects, and initiates quality data collection using -- but does not display -- the appropriate collection plan or plans.

If there are collection triggers defined for the background collection transaction, data collection is initiated only if all collection trigger conditions are satisfied. Collection transactions and triggers are defined in the Collection Transactions window.

As indicated above, several collection plans can have a background collection transaction in common. When this is the case, results for context elements on all of these collection plans are automatically saved when the parent transaction is saved. For example, if you have four collection plans that are associated the Work in Process move transaction, and the move transaction is defined as a 'background' collection transaction on each, then results for context elements are automatically saved for each of the four collection plans when move (parent) transactions are saved.

Non-Displayed Collection Plan Elements

You are not prompted to enter quality results for collection plan elements that are defined as non-displayed. Any collection plan element can be defined as non-displayed but normally only context elements, for which data is automatically collected as you transact, are suppressed. This is useful because values for context elements are automatically collected and cannot be changed, therefore displaying them to the user is unnecessary.

For example, you can create a Scrap collection plan that contains the following collection plan elements: Item, Serial Number, Job, Quantity, Scrap, and Operator, so that you can collect quality data each time defective assemblies are scrapped using the Work in Process move transaction. You can associate this collection plan with the Work in Process move transaction and optionally define a collection trigger so that the Scrap collection plan is invoked each time assemblies are moved into a Scrap intraoperation step.

If you define the context elements on this collection plan (Item, Job, and To/From Operation Sequences) as non-displayed, the results values for these context elements are not displayed when the Scrap collection plan is invoked for data entry. Thus you are prompted to enter results values for only those collection plan elements that are defined as displayed (Quantity, Scrap, and Operator).

See Also

Creating Collection Plans

Associating Transactions with Collection Plans

         Previous  Next          Contents  Index  Navigation  Glossary  Library