Collection plans are the structure that you use for data collection. Collection plans are composed of collection elements (the fields that you set up for the data that you want to collect), their values and specifications, and any actions that you want to initiate in response to quality results. You can create a collection plan that you can use as the default when you directly enter, view, and update quality results and when you view lot quality results, serial quality results, and action log entries. See: QA:Default Collection Plan.

Collection plan elements are the building blocks of collection plans. You can create collection plan elements by adding individual collection elements to your collection plan. You can also create collection plans by copying the collection elements from one collection plan into another. You can define lists of values for each collection plan element that you create.

You can customize collection plans to meet your specific data collection needs by:

• Associating specification types with collection plans, such as item, customer, or supplier

• Specifying which transactions in other Oracle Manufacturing products invoke a collection plan and thus quality data collection

• Defining values and lists of acceptable values for collection plan elements

• Defining action rules and when those action rules are invoked

• Attaching illustrative or explanatory files in the form of text, images, word processing documents, spreadsheets, video clips, and so on, to collection plans

• Associating devices to collection plan elements to enable device data collection, if Oracle Manufacturing Execution System (MES) for Discrete Manufacturing is installed.

Prerequisites

• Define collection elements. See: Defining Collection Elements.

   To create collection plans:

1. Navigate to the Collection Plans window.

   Attention: To assist you as you create collection plans, you can choose the Summary/Detail option from the View Menu and run a query to view existing collection plans in summary format. See:Combination Blocks.

2. Enter the Collection Plan name.

   Collection plan names can include alphanumeric characters and spaces. Collection plan names can have up to 30 characters, and the first 25 characters must be distinctive. The only special characters that can be included in a collection plan name are the underscore (_) and the single quotation mark (').

3. Optionally, enter the date that the Collection Plan becomes effective in the Effective "from" field, the first field after Effective.

   You cannot use the collection plan before this effective date. If you do not enter a "from" Effective date, the collection plan is effective immediately.

4. Optionally, enter the date that the Collection Plan expires in the Effective "to" field, the second field after Effective.

   You cannot use the collection plan after this date. Once a collection plan expires, you cannot enter quality results using the plan, but you can query records that already use it. If you do not enter a "to" effective date, the collection plan is valid indefinitely.

5. Select the collection Plan Type. See: Collection Plan Types.

6. Check the Display Multiple Rows in Workbench checkbox to display standalone and parent collection plans in the multiple row layout mode in the Quality Workbench.

7. Select the Record Option for entering quality results. The options are Per Row or Per Collection. This field only appears if the profile option value for EDR: E-records and E-signatures is Yes. See: E-records and E-signatures for Oracle Quality.

   Suggestion: The following example illustrates why you need to select Per Row as the record option:

   You must enter quality results for different item numbers using one collection plan. Item A requires the approval of Approver 1 and Item B requires the approval of Approver 2. In this scenario, you must capture e-records and e-signatures per row to enable both Approver 1 and Approver 2 to enter their e-signatures.

8. Choose Enable Deferred Signature if you want to enable deferred e-signatures when entering or updating quality results for this plan. This button only appears if the profile option value for EDR: E-records and E-signatures is Yes. See: E-records and E-signatures for Oracle Quality.

   Attention: This button only enables deferred e-signatures when entering or updating quality results directly or when entering or updating quality results during the following transactions:

   • Depot Repair Task Transaction (Depot Repair)

   • Process Nonconformance (Oracle Process Manufacturing)

   • Service Requests (Oracle Service)

   To copy collection elements and actions from a template plan:

See: Creating Collection Plans from a Template.

   To define collection plan elements:

See: Defining Collection Plan Elements.

   To copy collection element values to collection plans:

See: Defining Collection Plan Element Values.

   To define quality actions for collection plan elements:

See: Defining Collection Plan Element Actions.

   To associate specification types with collection plans:

See: Associating Specification Types with Collection Plans.

   To associate collection transactions with collection plans:

See: Associating Transactions with Collection Plans.

   To attach files to collection plans:

See: Attaching Files to Collection Plans, Specifications, and Results Lines.