Previous  Next          Contents  Index  Navigation  Glossary  Library

Quality Collection Transactions

You can collect quality data as you enter transactions in other Oracle Manufacturing Applications.

Collection Transactions

You can associate collection transactions entered in Oracle Purchasing, Oracle Work in Process, and Oracle Service with collection plans. Available transactions are as follows:

You can associate more than one collection plan with a collection transaction. For example, you can create a collection plan to track final test (e.g., pass/fail status) results and another to record the serial numbers of serial controlled assemblies that fail final test. You can associate the Work in Process move transaction with both collection plans to ensure that both final test and serial number data is captured as assemblies are moved.

You can also associate collection plans with more than one collection transaction. For example, you might associate both the Move Transaction and the Inspection Transaction collection transactions with a Surface Inspection collection plan. Doing so allows you to use the same collection plan to collect surface inspection data as you move assemblies and complete resurfacing operations and as you receive assemblies resurfaced by an outside supplier.

When you collect quality data as you transact in other Oracle application, the context elements associated with the parent transaction are automatically saved in the quality data repository. Even if you do not explicitly add these context elements to you collection plans, you can use them to define collection triggers. For example, the values for context elements such as Job, Item, and From and To Operation Sequence Numbers which are derived as assemblies are moved, can be used to define collection triggers even if they are not added to the collection plan. Collection triggers are evaluated as transactions are entered and can be used to determine which collection plan should be used in the quality data collection process.

Collection Triggers

Collection triggers are events or conditions that a transaction must satisfy before quality data collection is invoked. Quality data collection is automatically invoked only when all conditions for all collection triggers are met.

For example, if you define the following collection triggers for the Move Transaction collection transaction:

Quality data collection is automatically invoked only when both triggers conditions are met (C45268 assembly items are moved out of operation sequence 40). In this example, these triggers work together to ensure that the right data is collected at the right point -- operation sequence 40, a critical inspection point in an assembly's routing.

You can define as many collection triggers as are required to make data collection as specific as possible. They are optional.

         Previous  Next          Contents  Index  Navigation  Glossary  Library