120 Quality Implementation Guide
120 Quality Implementation Guide
120 Quality Implementation Guide
August 2010
Oracle Quality Implementation Guide, Release 12.1 Part No. E13679-04 Copyright 2003, 2010, Oracle and/or its affiliates. All rights reserved. Primary Author: Sujata Patnaik, Aravindan Sankaramurthy Contributing Author: Amy Sonczalla Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this software or related documentation is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065. This software is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications which may create a risk of personal injury. If you use this software in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy and other measures to ensure the safe use of this software. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software in dangerous applications. This software and documentation may provide access to or information on content, products and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third party content, products and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third party content, products or services.
Contents
Part 1
1
Implementation Considerations
Implementing Nonconformance and Disposition Solution.................................................... 2-1 Implementation Roadmap...................................................................................................... 2-12 Implementation Checklist.......................................................................................................2-16
Setting Up
Overview of Setting Up............................................................................................................. 3-2 Step 1 - Choose a configuration (mandatory)........................................................................... 3-3 Step 2 - Copy from Template Collection Plans (mandatory)................................................... 3-3 Step 3 - Update of Sequence prefix and suffix (mandatory).................................................... 3-8 Step 4 - Update of values for seeded collection elements (optional)..................................... 3-10 Step 5 - Update of menu entry to point to the correct plan (mandatory)............................... 3-11 Step 6 - Modify Collection Plan Details and Plan Element Prompts (optional)....................3-16 Step 7 - Update 'Execute a SQL script' Text (conditionally mandatory)................................ 3-17 Step 8 - Set Up Collection Plan Security (optional)................................................................3-20
iii
Step 9 - Add user defined elements to the plans (optional)................................................... 3-21 Step 10 - Link user defined plans to the system (optional).................................................... 3-22 Step 11 - Link Corrective Action system to Nonconformance and Disposition system (optional)................................................................................................................................. 3-23 Step 12 - Link the Transactional Collection Plan to the Nonconformance and Disposition system (optional)..................................................................................................................... 3-24 Step 13 - De-link Collection Plans from the Nonconformance and Disposition system (optional)................................................................................................................................. 3-25 Step 14 - Organize the Plan Elements into Folders (optional)............................................... 3-27 Step 15 - Set Up Profile Options (optional)............................................................................ 3-27 Step 16 - Setup within other modules (conditionally mandatory).........................................3-27 Considerations Prior to Implementation................................................................................ 3-27 Maintaining a Reference Copy of Collection Plans (optional).............................................. 3-27
Nonconformance Lifecycle
Overview of Procedures............................................................................................................ 4-1 Process Flow Chart.................................................................................................................... 4-1 Process Steps.............................................................................................................................. 4-2
Disposition Lifecycle
Overview of Disposition Lifecycle........................................................................................... 6-1 Process Flow Chart.............................................................................................................. 6-1 Process Steps........................................................................................................................ 6-2
Reporting
Overview of Reporting.............................................................................................................. 7-1 Quality Results Report Writer.................................................................................................. 7-1 Oracle Discoverer...................................................................................................................... 7-3
iv
Part 2
9
10
Implementation Roadmap
Overview of Implementation Roadmap................................................................................. 10-1 Implementation Considerations............................................................................................. 10-1 Prerequisites...................................................................................................................... 10-1 Corrective Action Request Types....................................................................................... 10-2 Corrective Action Request Sources.................................................................................... 10-2 Captured Data................................................................................................................... 10-3 Valid Values....................................................................................................................... 10-3 Corrective Action Identification......................................................................................... 10-4 Corrective Action Data Privileges...................................................................................... 10-4 Corrective Action Process........................................................................................................ 10-4 Implementation Checklist.......................................................................................................10-7
11
Setting Up
Overview of Setting Up...........................................................................................................11-1 Step 1 - Choose a configuration (mandatory)......................................................................... 11-2 Step 2 - Copy from template Collection Plans (mandatory)...................................................11-2 Step 3 - Update of Sequence prefix and suffix (mandatory).................................................. 11-5 Step 4 - Update of values for seeded collection elements (optional)..................................... 11-6 Step 5 - Update of menu entry to point to the correct plan (mandatory)............................... 11-7 Step 6 - Modify Collection Plan Details and Plan Element Prompts (optional)..................11-11 Step 7 - Add user defined elements to the plans (optional)................................................. 11-11 Step 8 - Link user defined plans to the system (optional)....................................................11-12 Step 9 - Organize the plan elements into folders (optional)................................................ 11-13 Step 10 - Set Up Profile Options (optional).......................................................................... 11-13 Step 11 - Setup within other modules (conditionally mandatory).......................................11-13 Step 12 - Set Up Collection Plan Security............................................................................. 11-13 Step 13 - Set Up Collection Element Security....................................................................... 11-14 Considerations Prior to Implementation.............................................................................. 11-15
12
Implementation
Implementing Corrective Action Solutions............................................................................12-1 Processing Corrective Action from an Audit ......................................................................... 12-1 Processing Corrective Action Generated from a Nonconformance....................................... 12-8 Processing Corrective Action for a Supplier.........................................................................12-22 Processing Corrective Action from a Customer Complaint................................................. 12-32
13
Reporting
Generating Reports on Corrective Action Information..........................................................13-1 Quality Results Report Writer................................................................................................ 13-1 Oracle Discoverer.................................................................................................................... 13-3
14
Part 3
15
Audits Solution
16
Implementation Considerations
Overview of Implementation Considerations........................................................................ 16-1 Prerequisites...................................................................................................................... 16-1 Types of Audits.................................................................................................................. 16-1 Audits Solution Implementation Tasks..............................................................................16-2 Valid Values....................................................................................................................... 16-3 Audits Identification.......................................................................................................... 16-3
vi
Audits Solution Data Privileges......................................................................................... 16-3 Implementation Roadmap...................................................................................................... 16-3 Implementation Check List..................................................................................................... 16-5
17
Setting Up
Overview of Setting Up...........................................................................................................17-1 Setup Prerequisites.................................................................................................................. 17-1 Setting up Audits Solution..................................................................................................... 17-3 Set Up Steps............................................................................................................................. 17-3
18
Implementation
Overview of Implementation.................................................................................................. 18-1 Process Steps............................................................................................................................ 18-1 Audits Solution Process.......................................................................................................... 18-3
19
Reporting
Reporting Overview................................................................................................................ 19-1
20
vii
Sample Code
Sample PL/SQL Code for finding Approver using Oracle Workflow.................................... C-1 Sample Code for Custom SQL*Plus Report.............................................................................C-3
D Stand-alone Collection Plan for Nonconformances Entered via Mobile Applications and Warehouse Management
Overview of Stand-alone Collection Plan................................................................................ D-1
viii
Template Audit Master Plan................................................................................................ L-1 Template Audit Master History Plan................................................................................... L-3 Template Audit Findings Plan............................................................................................. L-4 Template Audit Findings History Plan................................................................................ L-5 Template Audit Question and Response Plan..................................................................... L-5 Template Audit Question and Response History Plan........................................................ L-6 Template Audit Question Bank Plan................................................................................... L-7
Index
ix
Send Us Your Comments
Oracle Quality Implementation Guide, Release 12.1
Part No. E13679-04
Oracle welcomes customers' comments and suggestions on the quality and usefulness of this document. Your feedback is important, and helps us to best meet your needs as a user of our products. For example: Are the implementation steps correct and complete? Did you understand the context of the procedures? Did you find any errors in the information? Does the structure of the information help you with your tasks? Do you need different information or graphics? If so, where, and in what format? Are the examples correct? Do you need more examples?
If you find any errors or have any other suggestions for improvement, then please tell us your name, the name of the company who has licensed our products, the title and part number of the documentation and the chapter, section, and page number (if available). Note: Before sending us your comments, you might like to check that you have the latest version of the document and if any concerns are already addressed. To do this, access the new Oracle E-Business Suite Release Online Documentation CD available on My Oracle Support and www.oracle.com. It contains the most current Documentation Library plus all documents revised or released recently. Send your comments to us using the electronic mail address: appsdoc_us@oracle.com Please give your name, address, electronic mail address, and telephone number (optional). If you need assistance with Oracle software, then please contact your support representative or Oracle Support Services. If you require training or instruction in using Oracle software, then please contact your Oracle local office and inquire about our Oracle University offerings. A list of Oracle offices is available on our Web site at www.oracle.com.
xi
Preface
Intended Audience
Welcome to Release 12.1 of the Oracle Quality Implementation Guide. Oracle Quality applications implementers See Related Information Sources on page xv for more Oracle E-Business Suite product information.
Documentation Accessibility
Our goal is to make Oracle products, services, and supporting documentation accessible to all users, including users that are disabled. To that end, our documentation includes features that make information available to users of assistive technology. This documentation is available in HTML format, and contains markup to facilitate access by the disabled community. Accessibility standards will continue to evolve over time, and Oracle is actively engaged with other market-leading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers. For more information, visit the Oracle Accessibility Program Web site at http://www.oracle.com/accessibility/.
xiii
Structure
1 Overview of the Nonconformance and Dispositions Solution 2 Implementation Considerations 3 Setting Up 4 Nonconformance Lifecycle 5 Logging Nonconformances using MSCA and Oracle Warehouse Management 6 Disposition Lifecycle 7 Reporting 8 Tailoring Your Solution 9 Overview of the Corrective Action Solution 10 Implementation Roadmap 11 Setting Up 12 Implementation 13 Reporting 14 Tailoring Your Solution 15 Overview of Audits Solution 16 Implementation Considerations 17 Setting Up 18 Implementation 19 Reporting 20 Tailoring Your Solution A Nonconformance and Disposition Seeded Template Collection Plan Structure B Nonconformance and Disposition Seeded Template Collection Plan Details C Sample Code D Stand-alone Collection Plan for Nonconformances Entered via Mobile Applications and Warehouse Management E Collection Elements for Automated Disposition Action Processing F Nonconformance and Disposition Seeded Workflows Notifications G Corrective Action Seeded Template Collection Plan Structure H Corrective Action Seeded Template Collection Plan Details I Corrective Action Sample Code J Corrective Action Solution Seeded Workflow Notifications K Audits Seeded Template Collection Plan Structure L Audits Seeded Template Plan Details
xiv
Integration Repository
The Oracle Integration Repository is a compilation of information about the service endpoints exposed by the Oracle E-Business Suite of applications. It provides a complete catalog of Oracle E-Business Suite's business service interfaces. The tool lets users easily discover and deploy the appropriate business service interface for integration with any system, application, or business partner. The Oracle Integration Repository is shipped as part of the E-Business Suite. As your instance is patched, the repository is automatically updated with content appropriate for the precise revisions of interfaces in your environment.
xv
Part 1
Nonconformance and Disposition Solution
1
Overview of the Nonconformance and Dispositions Solution
This chapter covers the following topics: Nonconformance and Dispositions Solution Solution Templates
Solution Templates
Solution Templates aid in the ease of implementation with a pre-configured set of seeded collection plans. This set of seeded collection plans can be copied to real plans, modified if necessary, and implemented, enabling the implementation cycle time to be greatly reduced.
Objectives
The Nonconformance and Disposition Solution objectives are to primarily perform the following business functions: To log, track, review, and update Nonconformance Progress the Nonconformance through its lifecycle, identified by distinct statuses Record Material Review Board (MRB) discussion and approvals, if any Execute the Disposition of the Nonconformance and track the execution status
Contents
In order to achieve the Solution Template objectives, the solution templates contain the following contents: Seeded collection elements and associated lookup values for some of the seeded elements Seeded Template collection plans and corresponding values and actions Seeded parent-child collection plan structures with relationships, criteria, and data entry mode for the seeded template plans Copy Collection Plan process Automated Disposition Processor Seeded workflow for sending pre-configured workflow notifications
Features
The following table summarizes the key features provides with the Nonconformance and Disposition Solution. The details on how some of these features can be implemented are provided in later chapters:
Solution Template Features Key Feature Nonconformance Management and MRB Supported Activities Log and track a nonconformance through its lifecycle MRB discussion threads to review nonconformances Segregation of nonconforming material Audit trail on changes made to nonconformances E-mail alerts and workflow notifications to assign actions (for example, review and approval) for nonconformance lifecycle progress Different modes of use: Transaction Integration, Inspection Plan Integration, and Direct Data Entry Enterprise Wide Applicability Receiving and Supplier Inspection Work in Process Inspections Finished Goods Inspection Inventory/Warehouse Inspection Equipment Maintenance Service Applications Disposition Management Multiple Dispositions for a single nonconformance E-mail alerts and workflow notifications to assign and/or inform individuals for disposition implementation Maintain audit trail of dispositions
Supported Activities Work in Process Dispositions Creation of Rework Discrete Job Addition of Rework Operations Move to Rework Operation WIP Scrap Component Return and Issue Inventory Dispositions Inventory Scrap Move Order to segregate nonconforming material
Existing user group functionality Assignment of Privileges to create, update, insert, and/or delete from a collection plan
Menu Options
Menu options to invoke the nonconformance and dispositions in Enter, Update, and View modes
2
Implementation Considerations
This chapter covers the following topics: Implementing Nonconformance and Disposition Solution Implementation Roadmap Implementation Checklist
The nonconformance and disposition records are created, updated, and copied across plans throughout the lifecycle, by various participants within the business process. Notifications are sent to responsible parties to ensure that appropriate actions are taken. Some of the disposition execution can be automated. A predefined list of values is provided to ensure the validity of data. This implementation guide provides you with the most generic nonconformance and disposition business flow. Your specific nonconformance and disposition business processes can be different from the generic business flow. This solution is flexible and easily extensible, and can be tailored to suit your specific business needs. The following sections describe some of the factors that need to be considered before implementation.
What are the benefits of a transition from a paper based nonconformance and disposition system?
The basic premise of the solution templates provides a central repository for all the nonconformances and dispositions information, within an organization. By implementing the solution templates, you have the following advantages: Remove the paper trail, as well as reduce the maintenance of all paper records Provide a shorter cycle time to review and disposition nonconformances Notify the required personnel in your organization via e-mail alerts and workflow notifications, as well as e-mail alerts to mobile devices Easy retrieval of any nonconformance or disposition information, using the standard query capabilities of Oracle Quality Provide for an easier method of reporting on nonconformances over a period of time or for a specific item or assembly Ease in the extension of the solution templates to capture any additional information elements that need to be recorded and tracked If your organization still requires paper copies of records for compliance purposes, these can be printed using the Oracle Quality Report Writer, or by building custom reports
How will the solution template help your enterprise transition from stand-alone legacy systems?
If you are using different disparate, non-integrated systems to track nonconformances, as mentioned earlier, the solution templates aid to centrally maintain this information, In addition to using Oracle Quality, other integrations available within the e-Business Suite will help you to track nonconformances at different points within the supply chain.
material to your company. The supplier can use Oracle iSupplier Portal to submit the nonconformance electronically. Receiving Nonconformance: This type is recorded and subsequently dispositioned for purchased material and for material sent to the supplier for any outside processing operations. The nonconformance is usually recorded as a result of receiving inspection. Work In Process Nonconformance: This type is logged during the in-process inspection of a semi-finished assembly, or finished goods inspection prior to moving it to an inventory location. Inventory Nonconformance: This type can be logged during inventory inspection or during cycle/physical count activities. Customer Nonconformance: This type is logged when a customer reports that the products they have received do not meet the specified requirements. This can likely result in a Returned Material Authorization (RMA) that is issued, and the nonconforming material received back by the supplier for further evaluation and disposition. Maintenance Nonconformance: This type of nonconformance is logged to report defects on maintenance equipment used for critical production processes within an organization. Nonconformance logged through mobile devices: Since quality inspections can be performed on mobile devices using Oracle Warehouse Management and Mobile Supply Chain Applications functionalities, it is possible to log nonconformances for receiving or in-process inspection activities via mobile devices. Non-Material Nonconformance: In any organization, it is possible to report nonconformances on process issues, non-compliance to standard operating procedures, quality standards, and other non-material type issues.
Nonconformances logged from all sources are stored in a central repository titled, Nonconformance Master. Due to the tight integration of Oracle Quality with other modules within the Oracle eBusiness Suite, it is possible to record nonconformances during inspection or other transaction that are currently supported. Please refer to Setup Steps.
Details and Usage This configuration has all the collection plans and seeded data for implementing Nonconformance and Disposition Management (the master set of the next two configurations) This configuration consists of all collection plans and related seeded data used for Disposition Management only. Use this configuration if your business tracks disposition only and would like to take advantage of the automatic disposition transaction execution capability.
Disposition Only
Nonconformance Only
This configuration consists of all collection plans and related seeded data used for Nonconformance Management only. Use this configuration if your business does not require a systematic way of tracking disposition.
Additional data could be captured in user-defined collection elements and added to these collection plans. See: Setup Steps, Step 9. Alternatively, these elements can be grouped into additional plans and linked to the nonconformance/disposition system. See: Setup Steps, Step 10.
Steps, Step 2. You can choose to copy from the template collection plans, tailor these to your business needs, and make these a reference set of plans for your implementation. See: Considerations Prior to Implementation.
If your business organizes information in a simplified fashion, you can remove any level (collection plan) that is unnecessary. See: Setup Steps, Step 13.
These values can be modified to your valid values, according to your business rules. See: Setup Steps, Step 4.
used to inform, update, and adding individuals to specific tasks during the nonconformance and disposition lifecycle. Optionally, the e-mail alerts can be sent to mailing lists, or people outside of your organization, such as suppliers, customers, etc. They can also be sent to mobile devices.
This Quality Engineer has performed the analysis and requests a review by his manager by updating the same Nonconformance Detail:
Note Type Notes ANALYSIS Detailed results of the analysis...
Action Executed Action Executed By Next Action Type Next Action Description Next Action Assigned To
ANALYSIS Quality Engineer FOR REVIEW Please review this for analysis Quality Manager
The following screenshots illustrate how the Material Review process is handled using the Nonconformance and Disposition solution. All updates to these elements are captured in multiple history records of this parent record.
Nonconformance Detail Plan
the same.
How do you link the Corrective Action system to the Nonconformance and Disposition system?
When logging a Corrective Action Request as part of your Nonconformance or Disposition process flow, the Corrective Action system can be linked to the collection plan corresponding to the step in your process. See: Setup Steps, Step 11.
To maintain an association with the original nonconformance, you can create a new collection element, Parent Nonconformance, of character data type, and add the element to the Nonconformance Master and/or Details plan. When a new nonconformance is logged for each nonconforming component, a unique nonconformance number is generated. The Parent Nonconformance element can be used to maintain a link with the original nonconformance. Later, if all nonconformances for a specific parent nonconformance is required to be reported, the parent nonconformance number can be used as the query criterion to find all nonconformances. See: Reporting Overview.
Where appropriate, when entering the Nonconformances Details, enter the nonconformance cost for each line; the costs will be summed up from the nonconformance line level to the Nonconformance Master You can build reports using Oracle Quality Results Report Writer with the new cost collection element
Implementation Roadmap
The following process flow illustrates a generic nonconformance and disposition lifecycle:
Each rectangle represents an action step in the business flow and corresponds to step(s) to be executed in the Oracle Quality Nonconformance Solution. The following table illustrates the business flow step and the equivalent step in the nonconformance and disposition solution. Additional details, based on the function area of the nonconformance, are provided in the remaining chapters.
Oracle Quality Nonconformance and Disposition Solution Steps Enter a new record into the Nonconformance Master Collection Plan within Oracle Quality Update Owner collection element in the Nonconformance Master Enter information in the inventory or WIP segregation plan to segregate the material and move to a MRB or other quarantine subinventory Update elements such as Priority and Severity in the Nonconformance Master Enter a new record into the Nonconformance Detail (child collection plan of Nonconformance Master) to capture additional details and notes Update elements such as Notes and Action in the Nonconformance Detail
Log Nonconformance
Assign Owner
Review Nonconformance
Approve Nonconformance
Update Action Executed to Approval in the Nonconformance Detail (Customized workflows can also be used to achieve approvals, based on approval hierarchy)
Record Disposition
Enter a new record in Disposition Header to describe the Disposition Enter one or more records in the Disposition Detail (child plan of Disposition Header) to indicate the Disposition Action(s)
Disposition Implementation
Enter one or more records in the Disposition Implementation collection plan for the corresponding functional area (In-Process, Inventory) Update Status element to Closed in Disposition Implementation, Disposition Detail, and Disposition Header plans
Close Disposition
Oracle Quality Nonconformance and Disposition Solution Steps Update Status element to Closed in Nonconformance Detail and Nonconformance Master plans
Close Nonconformance
Implementation Checklist
The implementation might span multiple functional areas. The following list provides information on the process flow and steps to implement within these functional areas: Setup As seen in the above mapping table, the system is based on a set of Oracle Quality collection plans (Nonconformance Master, Nonconformance Details, Disposition Header, Disposition Details), and the most important setup step is to create these plans. See: Overview of Setting Up. Implementation by functional area Chapters 4 and 5 discuss the generic business process flow and the steps of implementation for each business function that would generate or report a nonconformance. The functional areas are limited to Supplier, Receiving, Work-in-Process, Inventory, and Customer Nonconformances. Refer to Process Steps for information on how nonconformance and disposition can be implemented in a mobile application environment (Oracle Warehouse Management or Mobile Supply Chain Applications). The appendices list all seeded collection plans, as well as their collection elements, parent-child relationships, and actions.
Note: It has been attempted to depict the business flow in a general
manner. It is possible that the actual business flow in your enterprise to report, review, and disposition nonconformances are different from the process flow diagrams above. Please use the process flow diagram as a guidance tool.
Reporting and other Solution Configurations Chapter 7 describes how to generate reports on Nonconformance and Disposition. Chapter 8 describes the other configurations that can be built on top of the Nonconformance and Disposition Solution. Some of them are Workflow configuration, SQL *Plus Report, and Modification of E-mail Notifications to suit
3
Setting Up
This chapter covers the following topics: Overview of Setting Up Step 1 - Choose a configuration (mandatory) Step 2 - Copy from Template Collection Plans (mandatory) Step 3 - Update of Sequence prefix and suffix (mandatory) Step 4 - Update of values for seeded collection elements (optional) Step 5 - Update of menu entry to point to the correct plan (mandatory) Step 6 - Modify Collection Plan Details and Plan Element Prompts (optional) Step 7 - Update 'Execute a SQL script' Text (conditionally mandatory) Step 8 - Set Up Collection Plan Security (optional) Step 9 - Add user defined elements to the plans (optional) Step 10 - Link user defined plans to the system (optional) Step 11 - Link Corrective Action system to Nonconformance and Disposition system (optional) Step 12 - Link the Transactional Collection Plan to the Nonconformance and Disposition system (optional) Step 13 - De-link Collection Plans from the Nonconformance and Disposition system (optional) Step 14 - Organize the Plan Elements into Folders (optional) Step 15 - Set Up Profile Options (optional) Step 16 - Setup within other modules (conditionally mandatory) Considerations Prior to Implementation Maintaining a Reference Copy of Collection Plans (optional)
Setting Up 3-1
Overview of Setting Up
This chapter outlines the steps necessary to set up Oracle Quality in order to use the Nonconformance and Disposition Solution Templates. The Nonconformance and Disposition Solution is delivered as a set of template collection plans and related seeded data. To utilize the solution, real collection plans need to be created and set up for use. These plans should also be modified according to your specific business needs. The following is a setup checklist:
Setup Checklist
Choose a configuration Copy from template collection plans Update of Sequence prefix and suffix Update of values for seeded collection elements Update of menu option to point to the correct plan Modify collection plan details and plan element prompts Update 'Execute a SQL Script' text Set up collection plan security Add user defined elements to the plans Link user defined plans to the system Link corrective action system to the nonconformance and disposition system Link transaction collection plan to the system Unlink unnecessary plans from the system Organize the plan elements into folders Set up Profile Options: Autoquery set to No Setup complete in other modules Maintain a reference copy of the plans
Nonconformance Only
Setting Up 3-3
structure of template collection plans into a set of real collection plans. The plans can be copied using the Copy Collection Plans process. It is required to specify the target or destination organization in which this set of plans will be used, as well as the user-defined names for these plans. .
Note: Template collection plans cannot store quality results and cannot
be updated.
2. 3.
Select Template from the Collection Plan Type list of values. Select a parent Collection Plan Name. Depending on the configuration (step 1) chosen for implementation. You can use the search page, as well, to search on the available template plans.
Partial List of Seeded Template Collection Plans with Disposition Configuration Highlighted
Setting Up 3-5
Partial List of Seeded Template Collection Plans with Nonconformance Configurations Highlighted
4.
The Organization will not be populated and is not necessary because the template plans are not assigned to an organization. Choose Search. Review the hierarchy of plans within the Results region.
5. 6.
7. 8.
Choose Copy. Enter New Plan Names for each of the template plan names displayed within the Source Plan Name column.
Note: Each individual plan name is required, and the plan names
should be unique.
Setting Up 3-7
9.
Select a Destination Organization. The collection plan structure will be copied to this organization.
10. Choose Finish. Plans with names you have chosen will be created with elements,
values, actions, and parent-child relationships, copied from the template plans.
11. You can optionally implement the process that enables suppliers to log
nonconformances via Oracle iSupplier Portal, prior to shipment. You can also log nonconformances within Oracle Enterprise Asset Management; you can copy the following stand-alone template collection plans: Template Supplier Nonconformance Record Plan Template Maintenance Nonconformance Record Plan
The steps to copy are similar to the steps described earlier, with the exception that these plans do not have a parent-child collection plan structure.
numbers, you can set up the appropriate prefix and suffix information; this should be performed before using and entering data in the Nonconformance and Disposition Collection Plans.
Note: After quality results have been entered for sequence collection
elements and saved into the nonconformance and disposition collection plans, the prefix/suffix cannot be changed.
1.
Navigate to the Collection Elements window. (N) Quality: Setup > Collection Element. Select Nonconformance Number and Disposition Number from the Collection Element list of values.
Update of Sequence Collection Element Attributes
2.
3. 4.
Choose Sequence. Enter your desired Prefix, Suffix, Separator, Increment, and Number Segment Length. Repeat these steps for the Disposition Number (Collection Element).
5.
Setting Up 3-9
6.
Navigate to the Collection Element window. Select the element, for which you want to change its value, from the Collection Element list of values. Choose Values. Add or modify these values to match your organization process statuses and codes. Save your work.
3. 4. 5.
Navigate to the Collection Plans window. Query the plan that contains the collection element that you modified above. Select the Collection Element, then choose Values. You can add or modify the values you had entered. Optionally, choose Defaults to copy the values from the collection element definition.
Note: Do not delete the seeded lookup values for the collection
4.
elements, Disposition Action and Disposition Status. These seeded values are internally used by Oracle Quality. You can add new lookup values to this list of elements.
Setting Up 3-11
2. 3.
Select the Collection Plan from the list of values. From the Help menu, select Diagnostic, then Examine, to display the Examine Field and Variable Values window.
4. 5. 6. 7. 8. 9.
Select Q_PLANS from the Block list of values. Select PLAN_ID from the Field list of values. The plan identification number is populated within the Value field. Switch to the System Administrator responsibility. Navigate to the Form Function window. Within the Description tabbed region, select the Function field, then select the Find (flashlight) icon. Perform a query on QA%QR% functions.
Setting Up 3-13
10. Select the Form tabbed region. 11. Select the Parameters field within the QANCMEQR Function row. Once selected,
ORA$QA_PLAN_NAME values (within their corresponding Parameters fields) to the plan name of the Nonconformance Master plan that was set up in previous steps .
14. Make similar changes for the other functions related to Dispositions (QADISPEQR,
QADISPVQR, QADISPUQR). Note that to access the Disposition forms functions, the Disposition ID and Disposition Name needs to be used.
15. Save your work.
and Disposition plans exist within the same organization, copy QA%QR% functions for each Nonconformance Master plan. Add these menu options to the responsibility of the authorized users. While form functions like QANCMEQR can be copied and renamed as required for the customer business scenario, the attachment icon would not be enabled for the custom form function created. To enable the attachment icon, each form function should have an entry in the attachments table. You can copy the attachments setups available for QANCMEQR and other functions
Setting Up 3-15
to their new form functions using Application Developer Responsibility. Setup the QACAREQR, QACARUQR and QACARVQR form functions using the CAR plan id and name in a similar manner as the NCM and Disposition form functions.
Step 6 - Modify Collection Plan Details and Plan Element Prompts (optional)
The copied plans from Step 2 have the description of the plan copied from the templates. The collection plan description can be modified to be more meaningful to the user. The collection element prompt in the copied nonconformance and disposition collection plans can be modified to suit specific user requirements.
For example, if Nonconformance Number is called Deviation Number, perform the following steps:
1. 2.
Navigate to the Collection Plans window. Select the Collection Plan for which you want to modify the prompt name for the collection element. In this example, query the plans that use Nonconformance Number. Within the Prompt field of the collection element, enter Deviation Number.
3.
Execute the following steps (after copying the corresponding template plans):
1. 2.
Navigate to the Collection Plans window. Select the Supplier and Maintenance Nonconformance, stand-alone collection plans (copied from the template) from the Collection Plan list of values.
Setting Up 3-17
3.
4.
5.
Change the string, TEMPLATE_NCM_MST1, to the name of the Nonconformance Master plan, set up during the previous steps. In the example above, the string, Q_TEMPLATE_NCM_MST1_IV, needs to be updated to Q_<Plan Name>_IV; the <Plan Name> is the Nonconformance Master collection plan that was previously set up.
Note: If the collection plan contains spaces, replace the spaces with
underscores.
6.
Change TEMPLATE NCM MST1 to the name of the Nonconformance Master plan, set up in the previous steps. In this case, do not replace the spaces with underscores. See: Figure-Update 2 to Action Details in the Supplier Nonconformance Plan
Setting Up 3-19
7. 8.
Save your work. Repeat steps one through seven for the Maintenance Nonconformance plan.
2. 3.
Create a new User Group. Assign users (members), whom will have the same roles and privileges, to the current user group. All users of the system should be Oracle Applications users with a valid login authority. Save your work.
4.
Navigate to the Grant Privileges window. In this window, any User Group can be grated privileges to perform various functions for any plan, If the Privilege check box is selected, the user group is granted that privilege for the specified collection plan. Depending upon the privileges that need to be granted to each user group, select the User Group name, the Collection Plan name, and the corresponding check boxes for Enter, View, Update, and Delete results. Save your work.
2.
3.
Navigate to the Collection Element window: Create a new element, Nonconformance Cost, with the following properties: Element Type = Variable
Setting Up 3-21
3. 4. 5.
Save your work. Navigate to the Collection Plans window: The new collection element, Nonconformance Cost, cane either be added tot he Nonconformance Master collection plan or the Nonconformance Detail collection plan. The decision needs to be based on the respective business process. If you want the costs to roll up to a parent plan, set up appropriate parent-child element relationships. For example, if you add Nonconformance Cost to the Nonconformance Master and Nonconformance Detail plans, then you can set up the parent-child element relationship in the following manner: Parent Plan: Nonconformance Master Child Plan: Nonconformance Detail Parent Element: Nonconformance Cost is the sum of Child element: Nonconformance Cost
Where appropriate, when entering the Nonconformance Detail, enter the nonconformance cost for each line; the costs will be summed up from the nonconformance line level to the nonconformance master.
6.
To keep track of updates to this element, add it to the Nonconformance Master History plan. Navigate to the Update Parent-Child Relationship page. Parent Plan: Nonconformance Master Child Plan: Nonconformance Master History Parent Element: Nonconformance Cost is copied to Child element: Nonconformance Cost
Navigate to the Collection Plan window: Enter a new plan Name, Description, and Plan Type. Add collection elements. Save your work.
Select your Nonconformance Master, as the Parent plan. Enter the plan, created in Step 10.1, as the Child plan. Select Immediate or Delayed from the Data Entry mode list of values. Save your work. When you enter a Nonconformance, you can invoke the Quality test plan from step 10.1.
Step 11 - Link Corrective Action system to Nonconformance and Disposition system (optional)
If logging a Corrective Action Request (CAR) is a part of your Nonconformance or Disposition process flow, the Corrective Action system can be linked to the collection plan, corresponding to the step within your process. Refer to Part 1 for more details.
Navigate to the Collection Element window. Enter Log CAR as the Collection Element name, Attribute as the Element Type, and Character as the Data Type. Save your work. Navigate to the Collection Plan window. Perform a query on your Nonconformance or Disposition plan, then add Log CAR to this plan.
3. 4. 5.
Setting Up 3-23
6.
Navigate to the Define Parent-Child Relationship page. Enter your Nonconformance or Disposition plan as the Parent plan. Enter your CAR plan as the Child plan. If you want to enforce the logging of CARs immediately after a Nonconformance and/or Disposition is logged, select Immediate from the Data Entry mode list of values. Otherwise, select Delayed. Optionally, enter Log CAR = YES, as the criteria.
5.
Step 12 - Link the Transactional Collection Plan to the Nonconformance and Disposition system (optional)
Nonconformances can be logged during inspection, receiving, or while a WIP move transaction is performed. To leverage the ability to log a nonconformance in a transaction-integrated session, perform the following steps:
Navigate to the Collection Plan window. Enter a new Plan Name, Description, and Plan Type. Choose Copy Element, then select the template collection plan for your transaction (for example, Template WIP Completion). Choose Transaction, then associate this plan with your transaction (for example, Work-In-Process Completion). Save your work.
4.
5.
Navigate to the Collection Element window. Enter Log NC as the Collection Element name, Attribute as the Element Type, and
Save your work. Navigate to the Collection Plan window. Perform a query on your plan, then add Log NC to this plan. Save your work.
Navigate to the Define Parent-Child Relationship page. Enter the plan you created in step 1 as the Parent plan. Enter your Nonconformance Master plan as the Child plan. If you want to enforce the logging of Nonconformances immediately after transaction data is entered, select Immediate from the Data Entry mode list of values. Otherwise, select Delayed. Optionally, enter Log CAR = YES, as the criteria. When you perform the transaction, you can invoke the transaction quality plan (step 12.1), then your Nonconformance Master. When a nonconformance is found independent of any transaction, invoke the Enter Nonconformance menu option, and enter a new record directly.
5.
Step 13 - De-link Collection Plans from the Nonconformance and Disposition system (optional)
In Chapter 2, the organization of the nonconformance and disposition data was discussed. Based on your possible need to capture granular level detail of the nonconformance, some of the collection plans can be de-linked from the existing collection plan structure. For example, if it was determined that you need only nonconformance and one disposition plan, and that you do not need the additional plans, then the follwi9ng diagram describes the steps necessary to de-link the collection plans that are not required. In this example, the nonconformance detail and disposition header plans are de-linked from the structure.
Setting Up 3-25
Navigate to the Update Parent-Child Relationship window. Search using Nonconformance Master as the Parent plan. Remove the relationship with Nonconformance Detail as the Child plan. Search using Disposition Header as the Parent plan. Remove the relationship with Disposition Detail as the Child plan. Save your work.
Navigate to the Define Parent-Child Plan Relationship page. Enter Nonconformance as the Parent plan
3.
Setting Up 3-27
This Reference set of plans can then be copied to collection plans that will be implemented and used. The Copy Collection Plan process can be utilized. This approach eliminates the need to copy from the template plans and modify the same for the implementation, within each organization. If you plan to deploy these plans multiple times without repeating the above setup steps, it is a good idea to preserve these plans with all the modifications in a reference copy that is not used for data entry. Copy from the reference to real plans. The following diagram depicts the implementation process of the consideration discussed above:
Reference Copy of Collection Plans Diagram
Your nonconformance and disposition solution plans are ready for implementation.
4
Nonconformance Lifecycle
This chapter covers the following topics: Overview of Procedures Process Flow Chart Process Steps
Overview of Procedures
This chapter details the procedures used to track and implement dispositions, using the Solutions Templates. These procedures include the various methods to initiate the disposition, assign dispositions, and set up automated execution of dispositions.
Process Steps
Identification of Nonconformance and its Source
There are many nonconformance sources that represent different functional areas within the Supply Chain. Quality Inspection Collection plans for receiving, work-in-process, and finished goods Other quality collection plans, such as testing, and packaging Nonconformance identified by suppliers Equipment nonconformances Nonconformance logged during Mobile Inspection using WMS/MSCA Nonconformance logged during OPM batch processing
Chapter 3 explained how to link a quality inspection plan to the nonconformance set of collection plans. The steps to link a supplier and maintenance nonconformance plan to the Nonconformance Master collection plan was also discussed. For mobile nonconformance collection plans, a stand-alone plan needs to be created. It will create the nonconformance within the Nonconformance Master collection plan. This is explained in Chapter 5.
Supplier Nonconformance
A supplier can log a nonconformance prior to shipment for the purchase order line of the item, or for an outside processing job, using Oracle iSupplier Portal. Prior to using the Supplier Nonconformance plan within Oracle iSupplier Portal, the plan should be associated with the Self Service Shipments and Self Service Outside Processing transactions in the collection plan definition, with any collection triggers that might be applicable. Some of the steps for logging a Supplier Nonconformance are explained below:
1.
Within Oracle iSupplier Portal, the supplier selects the Shipments tabbed region and then selects Quality. Search for the Purchase Order related to the nonconformance for the portion to be shipped. If the supplier is authorized to report non-material nonconformance, a dummy purchase order and shipment needs to be created. Select the link within the Quality Plans column, within the Quality Shipments Results table. Choose the pen icon within the Enter Quality Results column. Select the Supplier Nonconformance collection plan that was copied during setup. The supplier enters the details about the nonconformance. This information is dynamically propagated to the Nonconformance Master plan, and a notification is sent to the e-mail address specified while entering the collection plan result. The e-mail address is internal personnel (buyer, supplier quality engineer).
2.
3.
4.
5.
Receiving Nonconformance
If, during receiving inspection, a nonconformance is found, the receiving inspector can log a nonconformance. The applicable inspection collection plan must be set up as a parent to the Nonconformance Master. Some of the steps to log a Receiving Nonconformance are explained below:
1.
The receiving inspection plan should have a collection element, such as Log Nonconformance, as one of its elements. Parent-Child relationships should be set up between the receiving inspection plan and the Nonconformance Master to trigger nonconformance logging. The receiving inspector inspects the received material and enters the inspection results in the receiving inspection collection plan. If the inspector finds a nonconformance, he records the nonconformance as a child of the receiving inspection collection plan. When the nonconformance is logged, the related purchase order's data elements and other transaction context data elements default. After the nonconformance is logged in the nonconformance master, an e-mail or workflow notification is sent to the specified e-mail address.
2.
3.
4.
5.
6.
You can associate the Nonconformance Master collection plan with the respective WIP transaction, such as Move transaction, and Job Completion transaction. Set up Parent-Child relationships between the WIP inspection plan and the nonconformance master to trigger nonconformance logging. During WIP inspection, if the inspector or any authorized individual finds a nonconformance, it can be logged by initiating the Nonconformance Master collection plan. When the nonconformance is logged, the job related data elements and other transaction context data elements will default. After the nonconformance is logged in the Nonconformance Master, an e-mail notification is sent to the specified e-mail address.
2.
3.
4.
5.
Inventory Nonconformance
If nonconformances are found in material that resides in inventory, the Nonconformance Master needs to be initiated in direct data entry mode and the relevant information of the nonconformance, including the item, subinventory, locator, lot, and serial information can be entered.
Customer Nonconformance
Customer nonconformance can fall into two categories. The first category is when a customer reports a nonconformance in the shipped product at their site, but does not ship back the material. In this case, the Nonconformance Master collection plan can be initiated in the direct data entry and details on the nonconformance, including the entry of customer and sales order details. Subsequent disposition might require submitting a formal response to the customer. The second category is when a Returned Material Authorization (RMA) has been issued and the nonconforming product is returned by the customer. The steps associated with this type of nonconformance is similar to Receiving Nonconformance, with the exception of the data elements being related to the customer and sale order, and not supplier information. After the returned material is received, the review and disposition is carried out. Associating the nonconformance plans to the Service Request System, providing a mechanism to trigger nonconformance from Service Request, can also capture the Customer Nonconformance.
Maintenance Nonconformance
For a nonconformance that needs to be reported on maintenance equipment, the authorized user should, within Oracle Enterprise Asset Management (eAM), invoke the Maintenance Nonconformance Plan and enter the details on the nonconformance, during operation completion or work order completion. eAM transactions should be associated with the maintenance nonconformance plan before nonconformance can be logged. After the nonconformance is logged, the information is dynamically propagated to the Nonconformance Master plan. An e-mail or workflow notification is sent to the specified personnel.
Non-Material Nonconformance
Nonconformances reported in an enterprise do not need to be restricted to material nonconformances. There can be a business process related nonconformance, or audit related nonconformance. These can also be logged in the Nonconformance Master, using the collection elements, Process Step and Process Name. To track the non-material related nonconformance, the implementor can add data elements to capture the information.
OPM users can log material nonconformance, disposition them and implement corrective actions using Oracle Quality templates. The Template Nonconformance Master Plan and Template Nonconformance Master Plan (Nonconformance only), have the six process collection elements to enable this. Refer to: Understanding Nonconformance Tracking, Capturing Material Nonconformances, Capturing Resource Nonconformances, Disposing Nonconformances, Logging Nonconformances in the Oracle Manufacturing Execution System for Process Manufacturing User's Guide. Editing Batch Steps in the Oracle Process Manufacturing Process Execution User's Guide.
Implementation Considerations
When a nonconformance is logged within the Nonconformance Master, action rules can be set up to default the nonconformance owner, based on the nonconformance type, severity, and priority. Some of the other actions are defaulting the e-mail address based on the owner, date opened, date closed, and days to close.
The history plan for Nonconformance Details, for a given nonconformance line, will list all discussion that has existed, associated with the current nonconformance line.
Determine Disposition
After the review process has been completed for the nonconformance line, a disposition on the nonconformance is determined. It can be the responsibility of the owner to approve the disposition. Depending on the disposition chosen, automated disposition execution is accomplished.
Initiate Disposition
The dispositions are broadly classified into the following types: Accept-as-is: No action required Rework or Repair: Depending on the specific disposition action for rework, automated execution of the disposition can be initiated. Scrap: Depending on the specific disposition action for scrap, automated execution of the disposition can be initiated. Return to Vendor (RTV): This action requires the manual execution of the RTV transaction in inventory.
Depending on whether the disposition requires action and if it needs to be executed manually or automatically, the nonconformance owner can initiate disposition in the respective module or initiate the disposition process using the disposition set of collection plans (See: Process Steps).
5
Logging Nonconformances using MSCA and Oracle Warehouse Management
Process Steps
Following are the steps that need to be performed for logging nonconformances using MSCA and Oracle Warehouse Management.
Setting Up
Create a stand-alone Collection Plan
A stand-alone mobile nonconformance plan needs to be created with a subset of elements from the Nonconformance Master. The elements should be relevant to the transaction that most likely will enter the nonconformance. Because quality collection plans can be initiated from several mobile transactions that broadly fall into the categories of Receiving, Work In Process, and Inventory, if appropriate stand-alone collection plans, for each functional area, can be created. Refer to Appendix D for examples and the steps involved in creating the stand-alone collection plans.
Logging Nonconformances
Enter a Nonconformance using MSCA and/or Oracle Warehouse Management
When performing the mobile transactions in MSCA or Oracle Warehouse Management, if a nonconformance needs to be logged, you can invoke the appropriate stand-alone quality collection plan that was created in previous steps. You can then record the nonconformance. The background action populates the Nonconformance Master and an e-mail or workflow notification is sent to the Nonconformance owner.
6
Disposition Lifecycle
This chapter covers the following topics: Overview of Disposition Lifecycle
Process Steps
Identification of Disposition and its Source
Depending on the configuration chosen, the disposition tracking and execution system can exist independently or linked to the nonconformance tracking system. The disposition set of collection plans can be initiated via direct data entry or transaction association. See: Setup Steps for information on linking collection plans and associating them with transactions.
Logging a Disposition
When the decision has been made to log a disposition, the disposition header plan is invoked; you are required to enter the disposition source. If you navigated to the disposition header from the nonconformance system, the nonconformance number and associated information is copied to the disposition header. Rules can be set up to assign an owner to the disposition, based on the disposition source. If you set Default Values to YES, some elements are defaulted from the nonconformance master. Set Default Values to YES only when a nonconformance set of plans are associated with the disposition system. The details on the disposition header include the disposition source, source reference identifier, item, disposition owner, the source owner, and respective e-mail addresses. Background actions automatically update Date Opened, Date Closed, and Days to Close. When the disposition is logged, an e-mail or workflow notification is sent to the disposition owner and the source (nonconformance) owner.
WIP_REWORK_JOB). 2. The second line indicates that the disposition is Return to Vendor (RTV) for a quantity of three. Because the disposition was return to vendor for a nonconforming component in WIP, this requires a two-step process with two separate lines. The first line contains a RTV disposition and WIP_COMP_RETURN disposition action, enabling the component to return to a Material Review Board or quarantine subinventory. The second line contains a RTV disposition and MANUAL RTV disposition action. This requires that the RTV transaction is initiated within Oracle Inventory after the nonconforming component is returned to inventory.
Note: MANUAL RTV is not a seeded disposition action element value,
however, you can easily add it. See: Setup Steps, Step 4.
3. Because performing a WIP component scrap is not automated, the component scrap of two needs to be entered as two separate lines. The first line contains the SCRAP disposition and WIP_COMP_RETURN disposition action. The second line contains the SCRAP disposition and INV_SCRAP_ISSUE disposition action. INV_SCRAP_ISSUE is an Inventory Account alias for inventory scrap. Because each disposition can be executed by different people with different job functions, the owner assigns the disposition execution, using the Action Assigned to or Implementation By collection elements.
Disposition Implementation
When the implementor is ready to implement the automated disposition action, the disposition action value determines the WIP or Inventory disposition collection plan. After navigating to the implementation plan, the implementor can use Default Values to default information from the nonconformance master, as discussed earlier. When ready to execute the disposition action, the implementor will update the Launch Action collection element to YES, after entering the necessary collection elements for disposition execution. See: Appendix E -Collection Plans for information on the collection elements that need to be entered for each of the disposition actions.
The following table lists the automated disposition actions and the implementation plans containing the collection elements for executing the disposition:
Table 6-1 Supported, Automated Disposition Actions Disposition Action Creation of Inventory Move Order (INV_MOVE_ORDER) Inventory Scrap (INV_SCRAP_AAI) Component return to inventory (WIP_COMP_RETURN) Component issue to job (WIP_COMP_ISSUE) Creation of Rework Job (WIP_REWORK_JOB) Add rework operation (WIP_REWORK_OP) Move to rework operation (WIP_MOVE_REWORK) Assembly Scrap (WIP_MOVE_SCRAP) Implementation Collection Plan Inventory Disposition
In-Process Disposition
The automated disposition actions are processed when initiated from the disposition implementation collection plans. If the disposition implementation action initiated from the collection plan fails, manual intervention is required. The implementor would need to manually correct the transaction in the respective destination module, then resubmit the transaction. After the submitted transaction succeeds, the implementor should manually update the disposition status to SUCCESS, and notify the appropriate personnel. See Also Appendix E - Collection Plans for information on the collection elements that need to be entered for each of the disposition actions
Closing Dispositions
The disposition owner reviews the disposition lines and, if they have successfully been implemented, closes the disposition lines. The disposition is closed when all lines are closed. The nonconformance owner and other personnel are notified via e-mail or workflow notification.
7
Reporting
This chapter covers the following topics: Overview of Reporting Quality Results Report Writer Oracle Discoverer
Overview of Reporting
You can generate reports on Nonconformance and Disposition information using the following tools: Quality Results Report Writer - suitable for reporting on a single collection plan (Nonconformance Master or Disposition Header) Oracle Discoverer - suitable for analyzing data across multiple plans and providing an enterprise view of nonconformances across multiple organizations.
Reporting 7-1
The current functions (sum, count, average) available in Report Writer can be utilized to provide additional information on numerical collection elements.
Navigate to the Quality Results Report Writer window. Enter the following information: Report Name: NCM Avg Time Closure Report Collection Plan: Your Nonconformance Master Report Title: Average Time to Close a Nonconformance
3.
For report columns, list the following: Nonconformance Source Days to Close, Function: Average
4.
Report Output Example Nonconformance Source Inventory Receiving Work In Process Supplier Days to Close 2.5 3.85 1.5 2.65
Oracle Discoverer
Oracle Discoverer enables you to analyze nonconformances throughout your enterprise. Data from application schema is organized into Folders within Discoverer. The following are the steps to build folders for nonconformance analysis:
1.
Open business area, Quality Data Collection Analysis, using the Admin edition of Discoverer.
Reporting 7-3
2.
Create Folders in this area from the following views: Q_<NONCONFORMANCE MASTER PLAN>_V Q_<NONCONFORMANCE MASTER HISTORY>_V Q_<NONCONFORMANCE DETAIL PLAN>_V Q_<DISPOSITION HEADER PLAN>_V
Note: <NONCONFORMANCE MASTER PLAN> refers to the
name of your collection plan with spaces replaced by an underscore. the views are created dynamically when the collection plan is created or updated. The columns in the view correspond with the collection elements within the collection plan.
Create Folder Wizard in Discoverer Admin Edition
3.
Create Joins for these folders: One to Many Q_<NONCONFORMANCE MASTER PLAN>_V.NONCONFORMANCE_NUMBER -> Q_<NONCONFORMANCE DETAIL PLAN>_V.NONCONFORMANCE_NUMBER
One to Many
One to Many Q_<NONCONFORMANCE DETAIL PLAN>_V.NONCONFORMANCE_NUMBER -> Q_<DISPOSITION HEADER PLAN>_V.SOURCE_REFERENCE_ID, Q_<NONCONFORMANCE DETAIL PLAN>_V.NONCONFORMANCE_LINE_NUM -> Q_<DISPOSITION HEADER PLAN>_V.SOURCE_REFERENCE_LINE_ID
You can perform cross-plan analysis using Oracle Discoverer User Edition. For example, reporting all Defects and Causes by Supplier and time period.
Oracle Discoverer Workbook for Reporting on Supplier Nonconformance
Reporting on all Nonconformances for an Assembly and its Components You can report on all nonconformances related to an assembly. Assemblies consist of subassemblies. Subassemblies consist of subassemblies or components. Generally, users start with logging a nonconformance against an assembly:
Reporting 7-5
Item
Component Item -
Date Entered
Assembly
Time N
You can update the item and component elements within the master record to reflect that the nonconformance is in the subassemblies:
Nonconforman ce Number NC123 Nonconforman ce Item Type Component Item Component Item Subassembly1 Date Entered
Assembly
Time N+1
You can repeat this for multiple levels within a Bill of Material:
Nonconforman ce Number NC123 NC123 Nonconforman ce Item Type Component Component Item Component Item Subassembly2 Component Date Entered
Subassembly1 Subassembly2
You can review the progress of the above nonconformance. It displays that initially the nonconformance NC123 was reported for Assembly, at date/time N. Subsequent review and updates indicated that the component is the nonconformance cause. This nonconformance can be found by querying on NONCONFORMANCE_NUMBER from Q_<Nonconformance Master History>_V
where ITEM=<Assembly to be searched>. You can also generate the type of report (above) in Oracle Discover by creating a workbook, based on Q_<NONCONFORMANCE MASTER PLAN>_V + Q_<NONCONFORMANCE MASTER HISTORY>_V with these items from Q_<NONCONFORMANCE MASTER PLAN>_V folder and the criteria to be Q_<NONCONFORMANCE MASTER HISTORY>_V.ITEM=<Assembly to be searched>. You can report all nonconformances of components involved in manufacturing orders that manufacture a specific assembly. To report all nonconformances of components involved in manufacturing orders for a specific assembly:
1.
Find all manufacturing orders that manufacture the specific assembly. This utilizes WIP's Manufacturing Orders folder. The criteria is Item = <Assembly to be searched>. Find all material transactions issued to these manufacturing orders. This utilizes the existing join between Oracle Inventory's Material Transactions. The criteria is Mfg Order Id = Manufacturing Orders.Mfg Order Id. Find the serial numbers of these items. This utilizes the existing join between Material Transactions and Serial Numbers folders. Find all nonconformances with the specified Inventory Item Id and Serial Number. This requires a join between Serial Numbers and Oracle Quality's Nonconformance Master folder.
Note: Discoverer Folders from Oracle Inventory and Oracle
2.
3.
4.
Work In Process business areas need to be used to execute the steps listed above. These objects are part of Manufacturing Business Intelligence, and not part of Discrete Manufacturing Family Pack. Step 3 assumes components are serial controlled.
Reporting 7-7
8
Tailoring Your Solution
This chapter covers the following topics: Overview of Tailoring Solutions Workflow Configuration Using Oracle Approval Management Tailoring E-mail Notifications Tips and Techniques
Workflow Configuration
This solution includes generic workflow notifications for the Nonconformance and Disposition set of collection plans. You can replace these workflows with your own workflows. You can design Workflow notification messages in your own format. Responses entered on the notification can be written back to collection plans. For example, you can build a new workflow based on a the Disposition Detail Notification workflow: Send notification to the next approver (higher authority) Update the disposition record with an approval Reason Code from the notification
Refer to Appendix F for a list of seeded workflow notifications provided as part of the solution.
Copy the seeded workflow, Quality Generic Process, to a new workflow name. Modify the copied workflow.
Workflow Process Diagram for Nonconformance and Disposition Notification
3. 4. 5.
Add a new item attribute, X_APPROVAL_REASON, to this workflow. Display this item attribute within the message body of the current workflow. Add a call to the standard qa_results_wf_pkg.process_update procedure, within the Process Updates step. It can then write back all item attributes with an X_ prefix. This includes the Approval Reason. Add a call to custom PL/SQL code for finding approver, within the Find Approver step. Sample PL/SQL code to achieve this is illustrated in Appendix C. This sample code is for illustration purposes only, and has not been tested or certified by Oracle.
6.
Add an Approval Reason element to the Disposition Detail collection plan (See: Step 9 within Chapter 3). Replace the generic workflow, specified within the Workflow action (associated with the Send Notification element), with your new workflow. Add a new token, X_APPROVAL_REASON, to the Workflow action (associated with the Send Notification element) within the Disposition Detail. Map it to the Approval Reason element within the Disposition Detail.
2.
3.
nonconformances and dispositions. This application enables you to define business rules governing approvals. For example: IF Severity = MEDIUM, then one approval is required. IF Severity = HIGH, then two approvals are required.
Once the rules have been defined, the workflow uses APIs (Approval Management) to find the next approver (Step 6) until all approvals are obtained or rejected.
Register Nonconformance and/or Disposition as a new transaction type. Create Transaction attributes (Severity, Urgency, Nonconformance Type), which are used in rules to determine approvers. Define Approval Rules. In the first step of your workflow process, call ame_api.setFirstAuthorityApprover with the user specified in the Send Notification To item. If you are using Oracle Approvals Management to determine the first approver, call ame_api.getNextApprover to obtain the identification of the first approver. During the Find Approver step of your workflow process, call ame_api.getNextApprover to obtain the identification of the next approver. If ame_api.getNextApprover returns and empty ame_util.approverRecord, the transaction is approved. During the Notification step, call ame_api.updateApprovalStatus. This sends the approval status to Oracle Approvals Management.
3. 4.
5.
6.
7.
See Also How Should a Workflow use the Oracle Approvals Management API to Manage Approvals? Oracle Approvals Management Implementation Guide, Appendix C Oracle Workflow User's Guide Oracle Workflow Administrator's Guide Oracle Workflow API Reference Oracle Workflow Developer's Guide Oracle Workflow Customization, Oracle White Paper, August 2002
(N) Quality: Setup > Collection Plan Perform a query on the collection plan associated with the notification needing modification. Select the Send Email element. Choose Action. Select the Send an electronic email notification action, then choose Action Details. The Text area contains the notification's message text.
3. 4. 5. 6.
Field Security:
Depending on your business needs, it might be desirable to make a critical element within a collection plan protected from update by specific users. For example the Disposition Status should be protected from update, within the Disposition Header plan, by the MFG and PROJMFG users. Below are the steps used to set this scenario up: Step 1: Create a collection element to control record saving
1.
2.
Enter Save (or any unused name) as the Collection Element name, Attribute as the Collection Element Type, and Character as the Data Type. Save your work.
3.
(N) Quality: Setup > Collection Plan Perform a query on your Disposition Header plan, and add the collection element, Save. Make sure it is enabled but not displayed. Add an action to Save. Action Trigger: When Save = 2 Action: Reject the input with the message, "this record is protected from update by the current user." Note: Reject the input action rejects the whole row and not only the element to which the action is associated.
3. 4. 5.
6.
Add the current action to Disposition Status. When Disposition Status is entered, assign a value to Save with the following SQL script:
SELECT c FROM (SELECT 2 c from dual WHERE: parameter.user_id in (1003612, 1003614) -- user id of users that should not be able to update the Disposition Status UNION ALL SELECT 1 FROM dual) WHERE rownum = 1
With this action in place, when MFG users (1003612) and PROJMFG users (1003614) attempt to update and save the disposition status, their input will be rejected and a message will display.
Another example involves deriving the current user's telephone number information. This example is not included in the solution. Setting up telephone information derivation:
1.
Navigate to the Collection Element window (N) Quality: Setup > Collection Element. Create a collection element. Navigate to the Collection Plan window (N) Quality: Setup > Collection Plan. Query the plan that will receive the Telephone Number collection element. Add the Telephone Number element to the element block. Select a mandatory element and then choose Actions. Add the following action:
IF <collection element> is entered, assign a value to Telephone Number with SQL: SELECT p.work_telephone FROM PER_PEOPLE_F P, FND_USER U WHERE P.PERSON_ID = U.EMPLOYEE_ID AND U.USER_ID =: PARAMETER.USER_ID AND ROWNUM <= 1
2. 3. 4. 5.
Note: This SQL string is used for example purposes. It is not part of
Oracle's code; it has not been tested or certified by Oracle. Customers and implementors must use their discretion before implementing.
6.
Using SQL as the list of values of an element will simulate a lookup feature. For example, Supplier Contact Lookup (not included in the solution). Setting up a SQL as a list of values:
1.
Navigate to the Collection Element window (N) Quality: Setup > Collection Element. Create a Supplier Contact collection element. Enter the following SQL Validation String:
SELECT p.first_name ll ' ' ll p.last_name ll ' ' ll p.area_code ll '-' ll p.phone_code, v.vendor_name description FROM PO_VENDOR_CONTACTS P, PO_VENDOR_SITES S, PO_VENDORS V WHERE P.VENDOR_SITE_ID = S.VENDOR_SITE_ID AND S.VENDOR_ID = V.VENDOR_ID ORDER BY 2, 1
2. 3.
4. 5. 6. 7.
Navigate to the Collection Plan window (N) Quality: Setup > Collection Plan. Query the plan that will receive the Supplier Contact collection element. Add the Supplier Contact element to the element block. Save your work. You can now display this element's list of values. You can use it to find the name and phone number of a contact person, for any supplier.
Note: This SQL string is used for example purposes. It is not part of
Oracle's code; it has not been tested or certified by Oracle. Customers and implementors must use their discretion before
implementing.
After completing the following setup tasks, when users enter Electrical into the NONCONFORMANCE TYPE field, the NONCONFORMANCE CODE list of values will contain Short, No Solder, and Broken Lead. Setting up a dependent list of values:
1. 2. 3.
Navigate to the Collection Plan window (N) Quality: Setup > Collection Plan. Query your Nonconformance plan. Within the NONCONFORMANCE CODE element, choose Values. Enter the values within the above table. Within the NONCONFORMANCE TYPE element, choose Actions. Enter the following actions: IF NONCONFORMANCE TYPE is equal to Electrical, assign a value to NONCONFORMANCE CODE with value E%.
4.
IF NONCONFORMANCE TYPE is equal to Mechanical, assign a value to NONCONFORMANCE CODE with value M%.
5.
Save your work. When users enter Electrical as the NONCONFORMANCE TYPE, the NONCONFORMANCE CODE list of values will display, Short, No Solder, and Broken Lead.
Custom Reports:
You can write reports that are tailored to your business needs, using custom SQL. The Oracle E-Business Suite System Administrator's Guide - Configuration recommends custom SQL and a concurrent process to be defined, within a customer application (in this case, custom Quality). Setting Up a Custom Report
1.
Save your SQL under the directory, <custom Quality's base path>/sql/ (See: Applications DBA Duties, Oracle E-Business Suite System Administrator's Guide Configurationfor information on registering a new or custom application and where the Applications DBA specifies a base path for the application). Name it with your business' convention. Prefix it with custom Quality short name, and suffix it with .sql (XXCQA_NCMREP.sql). Navigate to the Concurrent Program Executable window (N) System Administrator: Concurrent > Program > Executable. Define an executable with SQL *Plus program style.
2.
3.
(N) System Administrator: Concurrent > Program > Define. Define a program, Material Review Report. For example, use the above executable. Choose Parameters. Enter three parameters in the following order:
Parameters Parameter Value Set Corresponding Parameter in Sample SQL &1 &2 &3
4.
The value sets are predefined and used for validation of parameter values.
Within the Manufacturing and Distribution Superuser responsibility, navigate to the Submit Request window (N) Quality: Reports > Submit Request. Select Material Review Report from the Name list of values (or any name that you created while setting up), and submit the process.
2.
Part 2
Corrective Action Solution
9
Overview of the Corrective Action Solution
This chapter covers the following topics: Overview of Solution Templates
Solution Templates
Solution Templates aid in the ease of implementation with a pre-configured set of seeded collection plans. This set of seeded collection plans can be copied to real plans, modified if necessary, and implemented, enabling the implementation cycle time to be greatly reduced.
Objectives
The Corrective Action Solution is comprised of several objectives, including the following: Enter, track, review, and implement a Corrective Action Request (CAR) Progress the CAR through its status lifecycle Execute the CAR's multiple review and implementation steps Automate the submission of an Engineering Change Order (ECO)
Contents
To achieve the Solution Template objectives, the templates contain the following:
Seeded collection elements and associated lookup values for some of the seeded elements Seeded Template collection plans and corresponding values and actions Seeded parent-child collection plan structures with relationships, criteria, and data entry mode for the seeded template plans Copy Collection process Engineering Change Order (ECO) submission processing code Seeded workflow for sending pre-configured workflow notifications
Features
The following table summarizes the key features provided with the Corrective Action Solution. Implementation details, on some of these features, are provided in later chapters:
Solution Template Features Key Feature Submission of Corrective Action Requests Supported Activities Ability to submit Corrective Action Requests (CAR) and track them using an unique identifier Different modes of submission: Direct Data Entry, Transaction Integration, Collection Plan Integration Identification of the source, severity, quality standards violated, etc. Information to the owner or assignee through e-mail alerts and workflow notifications Audit Trail on changes made to a CAR
Supported Activities Multiple phases/actions can be tracked for a CAR via Review and Analysis, Containment, Corrective Action, Preventive Action, Implementation, and Implementation Effectiveness Each phase/action can have an assignee The assignee can update the CAR with the relevant information The owner reviews the CAR and closes it if there are no pending actions
Can be used to track customer initiated CAR, internal CAR, and supplier CAR CAR can be submitted, based upon the context of the initiation (Purchase Order, Sales Order, Work Order, etc.)
Cost Tracking
Review and Implementation costs can be captured for a CAR Costs can be rolled up to the CAR to indicate Total Review and Total Implementation costs
ECO Submission resulting from a CAR can be initiated from a Quality Collection Plan Existing user group functionality Assignment of Privileges to create, update, insert, and/or delete from a collection plan
Menu Options
Menu options to invoke the corrective action requests in Enter, Update, and View modes
10
Implementation Roadmap
This chapter covers the following topics: Overview of Implementation Roadmap Implementation Considerations Corrective Action Process Implementation ChecklistCorrective Action SolutionImplementation Checklist
Implementation Considerations
You can identify factors that need to be considered, prior to setting up and implementing the Corrective Action Solution. Depending on your specific business processes, these factors may or may not be applicable. This section includes the following topics:
Prerequisites
Following are the prerequisites needed to implement the solution: Oracle Discrete Manufacturing Family Pack I Knowledge of Oracle Quality's functionality and capabilities, including Parent-Child Collection Plans (See: Parent-Child Collection Plans, Oracle Quality
User's Guide)
Internal CAR
This CAR category is primarily associated with resolving problems within Enterprise E. Examples of these problems are poor quality due to non-adherence to quality procedures, and recurring physical damage to assembly during handling and storage.
nonconformance trends, quality audits, or other sources. Following are some of the factors that need to be considered before you implement the Corrective Action Solution: If Nonconformance, Quality Audits, and Customer complaints are common CAR sources, then it is recommended to use the set of provided template parent-child collection plans. If you currently use Oracle Service - Service Requests to handle your customer complaints, and they are the only source for your Corrective Action Requests, then it is recommended to take advantage of the Oracle Quality and Oracle Service integration, using the stand-alone template collection plan.
Captured Data
Oracle Quality provides a data collection capability within Collection Plans; they can capture all data involved in your business process, including Corrective Action and related Quality test results. Additional data not covered by the template collection plans can be captured in user-defined collection elements, and added to collection plans. Alternatively, these elements can be grouped into additional plans and linked to the nonconformance/disposition system.
Valid Values
The solution has included commonly used values for validation of some collection elements. These values can be modified to your valid values, according to your business rules. Some of these elements are listed below: Request Source Request Type Standard Violation Section Violated Problem Solving Method Request Priority Request Severity Request Status Action Type
Implementation Type
Some of the procedural steps taken during the lifecycle of a Corrective Action Request are described below:
processes.
Assign Owner
Oracle Quality Step The assignees update the CAR Review plan with the Notes on the review actions that were performed, and the status of the review actions Owner/Assignee determines the root cause and updates the CAR plans with the information Assignees update the Corrective Action Implementation plans with the implementation actions, notes, resolution dates, and statuses of the actions Owner reviews the CAR and the child review and implementation plans to verify successful implementation. Additionally, the owner may set up a follow-up date to review implementation effectiveness If required, owner informs the customer, supplier, or any other internal or third party, on CAR status via e-mail alerts Owner closes the CAR in the Corrective Action Request Plan
Close CAR
Implementation Checklist
The implementation may span multiple functional areas; the following list provides information on the process flow and steps to implement within these functional areas:
Prerequisites
Set Up
In this implementation phase, it is important to identify the usage configuration of the Corrective Action System to be implemented. Subsequent to this decision, other steps can be executed. Refer to Overview of Setting Up for the required information.
Chapter 12 describes the steps for implementing a Corrective Action Request resulting from a Nonconformance, Quality Audit, etc. Additionally, a brief explanation is provided on how the Oracle Service and Oracle Quality integration can be leveraged to implement a Corrective Action System. Refer to the following topics: Corrective Action from an Audit Corrective Action Generated from a Nonconformance Corrective Action for a Supplier Corrective Action from a Customer Complaint
Reporting Overview describes how to generate reports on Corrective Action Requests. Chapter 14 describes how the Corrective Action Solution can be tailored to meet your specific organization needs. Some of the tailoring activities described include Workflow configuration and Modification of E-mail Notifications to suit your organization needs. Refer to the following topics: Tailoring E-mail Notifications Workflow Configuration Tips and Techniques
11
Setting Up
This chapter covers the following topics: Overview of Setting Up Step 1 - Choose a configuration (mandatory) Step 2 - Copy from template Collection Plans (mandatory) Step 3 - Update of Sequence prefix and suffix (mandatory) Step 4 - Update of values for seeded collection elements (optional) Step 5 - Update of menu entry to point to the correct plan (mandatory) Step 6 - Modify Collection Plan Details and Plan Element Prompts (optional) Step 7 - Add user defined elements to the plans (optional) Step 8 - Link user defined plans to the system (optional) Step 9 - Organize the plan elements into folders (optional) Step 10 - Set Up Profile Options (optional) Step 11 - Setup within other modules (conditionally mandatory) Step 12 - Set Up Collection Plan Security Step 13 - Set Up Collection Element Security Considerations Prior to Implementation
Overview of Setting Up
This chapter outlines the steps necessary to set up Oracle Quality to use the Corrective Action Solution Templates. This chapter contains the following topics: The Corrective Action Request solution is delivered as a set of template collection plans and related seeded data. To utilize the solution, real collection plans need to be set up for use. These plans should be modified according to your specific organization needs. The following is a setup checklist:
Setting Up 11-1
Setup Checklist
Choose a configuration Copy from template collection plans Update of Sequence prefix and suffix Update of values for seeded collection elements Update of menu entry to point to the correct plan Modify collection plan details and plan element prompts Set up collection plan security Add user defined elements to the plans Organize the plan elements into folders Set up Profile Options: Autoquery set to No
copied using the Copy Collection Plans process. It is required to specify the target or destination organization in which this set of plans will be used, as well as the user-defined names for these plans.
Note: Template collection plans cannot store quality results and cannot
be updated.
2.
Select Template from the Collection Plan Type list of values. The Organization will not be populated and is not necessary because the template plans are not assigned to an organization. Select a parent Collection Plan Name. Depending on the configuration (step 1) chosen for implementation, the appropriate parent plan should be chosen for the parent-child structure to be copied.
3.
Setting Up 11-3
Usage This configuration consists of all collection plans and related seeded data, used for Corrective Action Requests This configuration consists of a single seeded, stand-alone collection plan that can be integrated with the Oracle Service Requests system and used for Corrective Action Requests
4. 5.
Choose Search. Review the hierarchy of plans within the Results region.
Results Region
6.
Choose Copy.
7.
Enter a New Plan Names for each of the template plan names displayed within the Source Plan Name column.
Note: Each individual plan name is required to be entered. The first
8.
Select a Destination Organization. The collection plan structure will be copied to this organization. Choose Finish. Plans with names you have chosen will be created with elements, values, actions, and parent-child relationships, copied from the template plans.
9.
Setting Up 11-5
Note: After quality results have been entered for sequence collection
elements and saved into the corrective action collection plans, the prefix/suffix cannot be changed.
1.
2. 3. 4.
Select Corrective Action Num from the Collection Element list of values. Choose Sequence. Enter your desired Prefix, Suffix, Separator, Increment, and Number Segment Length. Save your work. Repeat steps one through five for the New ECO Name collection element.
5. 6.
process, these values can be modified either at the collection element level, or at the plan level.
Note: Do not delete the seeded lookup values for the collection
elements, Disposition Action and Disposition Status. These seeded values are internally used by the Oracle Quality. You can add new lookup values to this list of elements.
As part of the Corrective Action Solution, many new seeded collection elements have been provided. Some of these elements are listed below: Request Source Request Type Standard Violated Section Violated Problem Solving Method Request Priority Request Severity Request Status Action Type Implementation Type
Select the element, for which you want to change its value, from the Collection Element list of values. Navigate to the Collection Elements window. Choose Values. Add or modify these values to match your organization process statuses and codes. Save your work.
2. 3. 4. 5.
Setting Up 11-7
need to be modified by the System Administrator to point to the top most parent plan that was set up in Step 2. They need to point to the correct Corrective Action Request plan that was set up when copying the collection plan structures. You first need to find the plan identification number of the Corrective Action Request plan you have created.
1.
2. 3.
Select the Collection Plan from the list of values. From the Help menu, select Diagnostic, then Examine, to display the Examine Field and Variable Values window.
4. 5. 6. 7. 8.
Select Q_PLANS from the Block list of values. Select PLAN_ID from the Field list of values. The plan identification number is populated within the Value field. Switch to the System Administrator responsibility. Navigate to the Form Functions window.
Setting Up 11-9
9.
Within the Description tabbed region, select the Function field, then select the Find (flashlight) icon. Perform a query on QACAR% functions.
10. Select the Form tabbed region. 11. Select the Parameters field within the QACAREQR Function row. Once selected, the
ORA$QA_PLAN_NAME values (within their corresponding Parameters fields) to the plan name of your Corrective Action Request plan, created above.
14. Make similar changes for the other functions. 15. Save your work.
within the same organization, copy QACAR% functions to functions with different names and change the ORA$ token, accordingly. Add these functions to the QA_CAR menu.
Step 6 - Modify Collection Plan Details and Plan Element Prompts (optional)
The copied plans from Step 2 have the description of the plan copied from the templates. The collection plan description can be modified to be more meaningful to the user. The collection element prompt in the copied Corrective Action plans can be modified for specific user requirements. Depending on the business process in place and the terminology in use, some of the collection element prompt names in the collection plans can be modified to be more meaningful to end users.
For example, if Request Type is called CAR Type, perform the following steps:
1. 2.
Navigate to the Collection Plans window. Select the Collection Plan for which you want to modify the prompt name for the collection element. Within the Prompt field of the collection element, change the Request Type to CAR Type.
3.
Navigate to the Collection Elements window. Create a new element, Total CAR Estimate, with the following properties: Element Type = Variable Data Type = Number Decimal Precision = 2
3. 4.
Setting Up 11-11
5. 6.
Select the Corrective Action Request plan from the Collection Plan list of values. Add Total CAR Estimate Cost to the current collection plan. To keep an audit trail of updates to this element, you should also add this element to the Corrective Action Request History plan.
7. 8. 9.
Save your work. Navigate to the Update Parent-Child Plan Relationships page. Select Corrective Action request from the Parent Plan list of values.
10. Select Corrective Action Request History from the Child Plan list of values. 11. Choose Element Relationship. 12. Add a Copy relationship between Total CAR Estimate Cost in Parent and Child
plans.
13. Save your work.
Navigate to the Collection Plans window. Enter a new collection plan Name, Description, and Plan Type. Add collection elements to the current collection plan. Save your work.
Once the following steps are completed and you implement Corrective Action, you can invoke the Quality test plan from Step 9.
2. 3. 4. 5. 6.
Navigate to the Define Parent-Child Plan Relationships page. Enter your Corrective Action Implementation, as the Parent Plan. Enter the plan created in Step 8.1, as the Child Plan. Select Immediate or Delayed from the Data Entry Mode list of values. Save your work.
Setting Up 11-13
corrective action requests. A Purchasing Manager has access to view CARs, but not to enter or update them.
Navigate to the User Groups window: Create a new User Group. Assign users (members), who will have the same roles and privileges, to the current user group. All users of the system should be Oracle Applications users with a valid login authority. Save your work.
4.
Navigate to the Grant Privileges window. In this window, any User Group can be granted privileges to perform various functions for any plan, If the Privilege check box is selected, the user group is granted that privilege for the specified collection plan. Depending upon the privileges that need to be granted to each user group, select the User Group name, the Collection Plan name, and the corresponding check boxes for Enter, View, Update, and Delete results. Save your work.
2.
3.
To enable collection plan security, set the value for the following Profile Option to Yes: QA: Collection Plan Security After all the setup steps have been completed, the users will have access only to those collection plans to which they have privileges.
2. 3.
Navigate to the Collection Elements window: Enter Save (or any unused name) as the Collection Element name, Attribute as the Collection Element Type, and Character as the Data Type. Save your work.
3.
Navigate to the Collection Plans window: Perform a query on your Disposition plan. Add the Save collection element to the current collection plan. Select the Enabled check box. De-select Displayed. Add this Action to Save. When Save equals 2, reject the input with a message "This record is protected from update by the current user.". Add this Action to Request Status. When Request Status is entered, assign a value to Save with the SQL text:
Select C From (select 2 c from dual where :parameter.user_id in (1003612) Union all Select 1 from dual) Where rownum = 1
7.
8.
Setting Up 11-15
12
Implementation
This chapter covers the following topics: Implementing Corrective Action Solutions Processing Corrective Action from an Audit Processing Corrective Action Generated from a Nonconformance Processing Corrective Action for a Supplier Processing Corrective Action from a Customer Complaint
Implementation 12-1
1.
2.
Select CAR REQUEST PLAN from the Collection Plan list of values. The CAR number is loaded to identify the CAR with a pre-seeded, user-defined sequential number. You can now enter the specific CAR information. Select a Request Source from the list of values. This is what causes the CAR to generate. Valid values are AUDIT, CUSTOMER, NONCONFORMANCE, or OTHERS. If your organization requirements are such that more sources are required, you can add values to the collection element, Request Source, within the CAR REQUEST collection plan. Select a REQUEST TYPE from the list of values. Valid values are CUSTOMER, CUSTSUPP, INTERNAL, INTLSUPP, and SUPPLIER. Optionally, enter a SOURCE REFERENCE if there is a document, such as a nonconformance document. Optionally, select a STANDARD VIOLATED value from the list of values if the CAR is a result of the violation of any standard. Valid seeded values are 21CFR820, ISO9000, and QS9000. Optionally, select a SECTION VIOLATED value from the list of values. This value is the applicable section of the standard in violation. Optionally, select a PROBLEM SOLVING METHOD from the list of values. This value refers to the particular methodology that will be used to analyze the current CAR. Save your work.
3.
4.
5.
6.
7.
8.
9.
You can utilize the Attachments icon to store information in many formats, for the current CAR.
Implementation 12-3
Systemic Root Cause - used to record the reason for the system breakdown.
The following fields can be used to track the Requestor and the Owner information: Requestor Requestor E-mail Owner, Owner E-mail Address Date Open and Date Closed - used to track the beginning and ending of a CAR for analysis. The Expected Resolution and the Actual Resolution dates are also tracked. Follow Up Date - used to ensure that the appropriate action is taken at the appointed time. Days to Close - used to track the total number of days the CAR has been open, for reporting purposes.
CAR Approval:
The pre-seeded collection elements for approval enable the routing of the CAR. You can view what actions were taken and what actions still need to be taken.
Implementation 12-5
The CAR REVIEW plan was created as a Child Plan of the CAR REQUEST PLAN.
Implementation 12-7
Maintaining a complete history is an important tool utilized when researching how a CAR has been altered. You can utilize security to limit view authority to the Quality Manager or the System Administrator. User, date, and time information is recorded within every history collection plan.
Nonconformance Detail plan (LG_NCDETAIL) and the CAR Request plan (LG_CAR_REQUEST). This setup offers the option to create a Corrective Action.
Parent-Child Relationship between Nonconformance Detail and CAR Plan
Implementation 12-9
Implementation 12-11
Entering Nonconformance
Implementation 12-13
Nonconformance Detail
seeded collection element. It is used here for example purposes. Implementers need to create this element and establish parent-child relationships between the Nonconformance and CAR plans, if desired.
Implementation 12-15
Implementation 12-17
You can view plans that contain information regarding the current Nonconformance. Below, you can see that there are two nonconformance plans containing information. You can also obtain detailed information on the CAR.
Implementation 12-19
Query Results
You can choose the More Details icon to view the entire CAR plan. If there were attachments associated with the plan, you could view those attachments by choosing the Attachment (paperclip) icon.
Implementation 12-21
Implementation 12-23
corrective action.
Enter Analysis for Corrective Action Review
Implementation 12-25
Note: The above window depicts the supplier sending the response,
"The mold that we have supplier to you ... needs to be reworked...", to his contact within the enterprise. This contact will input this response into the CAR Supplier Response plan. Alternatively, the supplier could have directly entered this response via iSupplier Portal. See: Supplier Responds via iSupplier Portal.
Implementation 12-27
Notification to Supplier
(N) Shipment > Quality. Query the Purchase Order for the item, which requires Corrective Action.
Navigation on iSupplier Portal: Shipment > Quality > Available Quality Plans
For non-material CAR purposes (a Corrective Action related to a process), a "dummy" Purchase Order (not used for purchasing any real material) can be created. That dummy Purchase Order number would then be communicated to suppliers.
3.
Select the Supplier Corrective Action Response plan from the list of available Quality plans. Plans must be enabled for iSupplier Portal Shipment to be available within the list of values.
Implementation 12-29
4.
Enter the response with the Corrective Action number and then save your work.
Implementation 12-31
suppliers to update the CAR with their responses, please ensure that you remove the Notes collection element (Comments data type), and replace it with another colletion element of Character data type, to capture supplier response.
Implementation 12-33
Implementation 12-35
13
Reporting
This chapter covers the following topics: Generating Reports on Corrective Action Information Quality Results Report Writer Oracle Discoverer
Reporting 13-1
The current functions (sum, count, average) available in Report Writer can be utilized to provide additional information on numerical collection elements.
Navigate to the Quality Results Report Writer window. Enter the following information: Report Name: CAR Avg Time Closure Report Collection Plan: Your CAR plan Report Title: Average Time to Close a CAR
3.
For report columns, list the following: Request Source Days to Close, Function: Average
4.
Oracle Discoverer
Oracle Discoverer enables you to analyze Corrective Action throughout your enterprise. Data from application schema is organized into Folders within Discoverer.
Open business area, Quality Data Collection Analysis, using the Admin edition of Discoverer. Create Folders in this area from the following views:
2.
Reporting 13-3
Q_<CORRECTIVE ACTION REQUEST>_V Q_<CORRECTIVE ACTION REQUEST HISTORY>_V Q_<CORRECTIVE ACTION REVIEW>_V Q_<CORRECTIVE ACTION REVIEW HISTORY>_V Q_<CORRECTIVE ACTION IMPLEMENTATION>_V Q_<CORRECTIVE ACTION IMPLEMENTATION HISTORY>_V
Note: <CORRECTIVE ACTION REQUEST> refers to the name
of your collection plan with spaces replaced by an underscore. the views are created dynamically when the collection plan is created or updated. The columns in the view correspond with the collection elements within the collection plan.
Create Folder Wizard in Dicoverer Admin Edition
3.
Create Joins for these folders: One to Many Q_<CORRECTIVE ACTION REQUEST>_V.CORRECTIVE ACTION NUM-> Q_<CORRECTIVE ACTION REVIEW>_V.CORRECTIVE ACTION NUM
One to Many
Q_<CORRECTIVE ACTION REQUEST>_V.CORRECTIVE ACTION NUM-> Q_<CORRECTIVE ACTION IMPLEMENTATION>_V.CORRECTIVE ACTION NUM
One to Many Q_<CORRECTIVE ACTION REQUEST>_V.CORRECTIVE ACTION NUM-> Q_<CORRECTIVE ACTION REQUEST HISTORY>_V.CORRECTIVE ACTION NUM
One to Many Q_<CORRECTIVE ACTION REVIEW>_V.CORRECTIVE ACTION NUM-> Q_<CORRECTIVE ACTION REVIEW HISTORY>_V.CORRECTIVE ACTION NUM
One to Many Q_<CORRECTIVE ACTION IMPLEMENATION>_V.CORRECTIVE ACTION NUM-> Q_<CORRECTIVE ACTION IMPLEMENTATION HISTORY>_V.CORRECTIVE ACTION NUM
You can perform cross-plan analysis using the Discoverer User Edition. For example, reporting all Request Types and Causes by Supplier and Dates. See Also Oracle Discoverer User's Guide
Reporting 13-5
14
Tailoring Your Solution
This chapter covers the following topics: Overview of Tailoring Solutions Workflow Configuration Using Oracle Approval Management Tailoring E-mail Notifications Tips and Techniques Field Security Derive User Information using Assign-a-Value Lookup Feature Using SQL Validation Strings Dependent List of Values Custom Reports
Workflow Configuration
This solution includes generic workflow notifications for the Corrective Action set of collection plans. You can replace these workflows with your own workflows. You can design Workflow notification messages in your own format. Responses entered on the notification can be written back to collection plans.
For example, you can build a new workflow based on a the Disposition Detail notification workflow: Send notification to the next approver (higher authority) Update the disposition record with an approval Reason Code from the notification
Refer to Appendix J for a list of seeded workflow notifications provided as part of the solution.
Copy the seeded workflow, Quality Generic Process, to a new workflow name. Modify the copied workflow.
Workflow Process Diagram for Nonconformance and Disposition Notification
3. 4. 5.
Add a new item attribute, X_APPROVAL_REASON, to this workflow. Display this item attribute within the message body of the current workflow. Add a call to the standard qa_results_wf_pkg.process_update procedure, within the Process Updates step. It can then write back all item attributes with an X_ prefix. This includes the Approval Reason. Add a call to custom PL/SQL code for finding approver, within the Find Approver step. Sample PL/SQL code to achieve this is illustrated in Appendix C. This sample code is for illustration purposes only, and has not been tested or certified by Oracle.
6.
Add an Approval Reason element to the Disposition Detail collection plan (See: Step 9 within Setup Steps) Replace the generic workflow, specified within the Workflow action (associated with the Send Notification element), with your new workflow. Add a new token, X_APPROVAL_REASON, to the Workflow action (associated with the Send Notification element) within the Disposition Detail. Map it to the Approval Reason element within the Disposition Detail. See Also Using Oracle Approval Management
2.
3.
Once the rules have been defined, the workflow uses APIs (Approval Management) to find the next approver (Step 6) until all approvals are obtained or rejected.
Register Corrective Actions as a new transaction type. Create Transaction attributes (Severity, Urgency, Request Type), which would be used in rules to determine approvers. Define Approval Rules. In the first step of your workflow process, call ame_api.setFirstAuthorityApprover with the user specified in the Send Notification To item. If you are using Oracle Approvals Management to determine the first approver, call ame_api.getNextApprover to obtain the identification of the first approver. During the Find Approver step of your workflow process, call ame_api.getNextApprover to obtain the identification of the next approver. If ame_api.getNextApprover returns empty ame_util.approverRecord, the transaction is approved. During the Notification step, call ame_api.updateApprovalStatus. This sends the approval status to Oracle Approvals Management. See Also How Should a Workflow use the OAM API to Manage Approvals?, Oracle Approvals Management Implementation Guide, Appendix C Oracle Workflow User's Guide Oracle Workflow Administrator's Guide Oracle Workflow API Reference Oracle Workflow Developer's Guide Oracle Workflow Customization, Oracle White Paper, August 2002
3. 4.
5.
6.
7.
(N) Quality: Setup > Collection Plan Perform a query on the collection plan associated with the notification needing modification. Select the Send Email element. Choose Action. Select the Send an electronic email notification action, then choose Action Details. The Text area contains the notification's message text.
3. 4. 5. 6.
Field Security
Depending on your business needs, it might be desirable to make a critical element within a collection plan protected from update by specific users. For example the Implementation Status should be protected from update, within the Corrective Action Implementation plan, by the MFG and PROJMFG users. Below are the steps used to set this scenario up:
2.
Enter Save (or any unused name) as the Collection Element name, Attribute as the Collection Element Type, and Character as the Data Type. Save your work.
3.
(N) Quality: Setup > Collection Plan Perform a query on your Corrective Action Implementation plan, and add the collection element, Save. Make sure it is enabled but not displayed. Add an action to Save. Action Trigger: When Save = 2 Action: Reject the input with the message, "this record is protected from update by the current user." Add the current action to Implementation Status. When Implementation Status is entered, assign a value to Save with the following SQL script:
Note: The SQL below is for example purposes. It is not part of
3. 4. 5.
6.
Oracle's code; it has not been tested or certified by Oracle. Customers and implementors must use their discretion before implementing.
SELECT c FROM (SELECT 2 c from dual WHERE: parameter.user_id in (1003612, 1003614) -- user id of users that should not be able to update the Implementation Status UNION ALL SELECT 1 FROM dual) WHERE rownum = 1
With this action in place, when MFG users (1003612) and PROJMFG users (1003614) attempt to update and save the disposition status, their input will be rejected and a message will display.
Another example involves deriving the current user's telephone number information. This example is not included in the solution.
Navigate to the Collection Element window (N) Quality: Setup > Collection Element. Create a collection element. Navigate to the Collection Plan window (N) Quality: Setup > Collection Plan. Query the plan that will receive the Telephone Number collection element. Add the Telephone Number element to the element block. Select a mandatory element and then choose Actions. Add the following action:
IF <collection element> is entered, assign a value to Telephone Number with SQL: SELECT p.work_telephone FROM PER_PEOPLE_F P, FND_USER U WHERE P.PERSON_ID = U.EMPLOYEE_ID AND U.USER_ID =: PARAMETER.USER_ID AND ROWNUM <= 1
2. 3. 4. 5.
Note: This SQL string is used for example purposes. It is not part of
Oracle's code; it has not been tested or certified by Oracle. Customers and implementors must use their discretion before implementing.
6.
Using SQL as the list of values of an element will simulate a lookup feature. For example, Supplier Contact Lookup (not included in the solution).
Navigate to the Collection Element window (N) Quality: Setup > Collection Element. Create a Supplier Contact collection element. Enter the following SQL Validation String:
SELECT p.first_name ll ' ' ll p.last_name ll ' ' ll p.area_code ll '-' ll p.phone_code, v.vendor_name description FROM PO_VENDOR_CONTACTS P, PO_VENDOR_SITES S, PO_VENDORS V WHERE P.VENDOR_SITE_ID = S.VENDOR_SITE_ID AND S.VENDOR_ID = V.VENDOR_ID ORDER BY 2, 1
2. 3.
4. 5.
Navigate to the Collection Plan window (N) Quality: Setup > Collection Plan. Query the plan that will receive the Supplier Contact collection element.
6. 7.
Add the Supplier Contact element to the element block. Save your work. You can now display this element's list of values. You can use it to find the name and phone number of a contact person, for any supplier.
Note: This SQL string is used for example purposes. It is not part of
Oracle's code; it has not been tested or certified by Oracle. Customers and implementors must use their discretion before implementing.
Navigate to the Collection Plan window (N) Quality: Setup > Collection Plan. Query your Nonconformance plan. Within the PROBLEM CODE element, choose Values. Enter the values within the
above table.
4.
Within the TEST TYPE element, choose Actions. Enter the following actions: IF TEST TYPE is equal to Electrical, assign a value to PROBLEM CODE with value E%. IF TEST TYPE is equal to Mechanical, assign a value to PROBLEM CODE with value M%.
5.
Custom Reports
You can write reports that are tailored to your business needs, using custom SQL. The Oracle E-Business Suite System Administrator's Guide - Configuration recommends custom SQL and a concurrent process to be defined, within a customer application (in this case, custom Quality).
Save your SQL under the directory, <custom Quality's base path>/sql/ (See: Applications DBA Duties, Oracle E-Business Suite System Administrator's Guide Configurationfor information on registering a new or custom application and where the Applications DBA specifies a base path for the application). Name it with your business' convention. Prefix it with custom Quality short name, and suffix it with .sql (XXCQA_CARREP.sql). Navigate to the Concurrent Program Executable window (N) System Administrator: Concurrent > Program > Executable. Define an executable with SQL *Plus program style.
2.
3.
(N) System Administrator: Concurrent > Program > Define. Define a process, Corrective Action Report. For example, use the above executable. Choose Parameters. Enter three parameters in the following order:
Parameter Value Set Corresponding Parameter in QACAR.sql &1 &2
4.
QA_SRS_PLAN QA_SRS_PLAN
The value sets are predefined and used for validation of parameter values.
Within the Manufacturing and Distribution Superuser responsibility, navigate to the Submit Request window (N) Quality: Reports > Submit Request. Select Corrective Action Report from the Name list of values (or any name that you created while setting up), and submit the process. See Also Oracle E-Business Suite System Administrator's Guide - Configuration Sample Code for SQL*Plus Report for a description and the sample code of the custom report.
2.
Part 3
Audits Solution
15
Overview of Audits Solution
Audits Solution
The Quality Audits Solution enables you to plan, track, and measure the effectiveness of the Quality Management System (QMS). Quality Audit Solution gives a framework that helps you to standardize and streamline the process of conducting quality audits across the organization. It provides an electronic method to conduct audits and allows you to tailor the audit solution according to the business needs. It helps to identify quality systems problems across the organization as well as compare organizations in terms of compliance standards. The audits solution provides seeded parent-child collection plan templates that help to collect data and conduct quality audits. You can also store audit questions in the Audits Questions Bank and re-use them in different audits based on the scope of each audit.
Solution Templates
Audit Solution Templates comprise of seeded collection plans that can be copied, modified and implemented to conduct audits.
Objectives
The objectives of the Quality Audits Solution are to perform the following business functions: To establish the level of compliance to published standards To document any corrective actions needed To assist in the review processes and identify any weaknesses, risks and areas of future improvement To track previously identified non-conformances and monitor the implementation the required corrections
Contents
In order to achieve the objectives, the audits solution templates contain the following: Seeded collection elements and associated lookup values for some of the seeded elements Seeded Template collection plans and corresponding values and actions Parent-child collection plan structure with seeded collection elements and collection element in-list values Copy collection process and logging of corrective action Seeded workflow for sending pre-configured workflow notifications
Features
The following table gives the key features provided with the audits solution:
Key Feature Audit Initiation and Lifecycle Tracking Supported Activities Initiate and create a audit number to track its lifecycle Record the scope and objectives of the audit Attach policies and standards for auditors to review Define audit area and assign lead auditor for that area Create or copy questions for the audit Notify personnel of the upcoming audit Enable auditors to record findings of the audit Review and record if procedures are adequate and compliant Log Corrective Action Requests if needed Review if corrective actions have been implemented and end audit lifecycle by closing the audit
Supported Activities Choose and copy the relevant audit questions from the Question Bank for the audit that has been initiated Ability to add attachments like additional unstructured information such as evidence, multimedia files, etc., to collection results and collection plans User access to the system can be restricted so that User Groups and "Grant Privileges will be used to grant or restrict the ability to enter, update, delete or view Quality Results as well as change plan setup The implementer of the system can choose the data elements that need audit trail by using the history collection plans
16
Implementation Considerations
Prerequisites
The following are the prerequisites to implement the audits solution: Oracle Discrete Manufacturing Family Pack 1 Knowledge of Oracle Quality's functionality and capabilities, including Parent-Child Collection Plans (See Oracle Quality User's Guide)
Types of Audits
Audits addressed by the quality audits system are compliance based audit that measure processes in your organization according to a set standard and management based audits that focus on results that help auditors review the processes and question how they are accomplished. Following are the types of audits that you can execute:
Valid Values
The solution has included commonly used values for validation of some collection elements. These values can be modified to your valid values, according to your business rules. Some of these elements are listed below: Audit Type Audit Standard Audit Status
Audits Identification
When you initiate an audit, you generate a unique ID for tracking the audit during its lifecycle.
Implementation Roadmap
The following processes flows illustrate the general flow of an audit lifecycle.
The diagram traces the audits business flow from the initiation of an audit till the audit is scheduled for execution. To implement the initiation of an audit, you will copy the Audit Solution Template provided, modify it to suit your organization's needs, assign the lead auditor, and determine the scope and policies of the audit. The lead auditor will determine the audit areas, and auditors/audit teams, prepare the plan, schedules and distribute it for the audit execution.
This diagram traces the audits business flow from the beginning of its execution to the close or follow-up of the audit. To execute the audit, you will send out the pre-determined questionnaire to the auditees, evaluate the responses, collect data and determine if the evidence is enough. You will also determine if there are any negative findings for which you will log corrective actions, and plan follow-up actions to see that the corrective action is implemented. If satisfied with the audit, you will close the audit.
Prerequisites
Install Oracle Discrete Manufacturing Family Pack 1.
Set Up
Copy the Audits Solution Template using the Copy Collection program. Modify the plan to suit your business needs. Determine scope, policies and audit areas.
Refer to chapter 17 Setting Up for more details and the subsequent steps required for execution.
Audits Implementation
Initiate an internal audit within your organization. Initiate an external audit of suppliers. Log corrective action if necessary.
17
Setting Up
Overview of Setting Up
The Audits Solution is a set of template collection plans and related seed data. To use the audits solution, set up real collection plans and modify it to meet business needs. You would need to do the following: Create the Audit Plan from the seeded Audit template plans. Setup the sequence parameters for the collection elements Audit Num and Audit Finding Num. Verify whether Audit specific workflow definitions were loaded. Create Audit questions in the Question Bank after copying the Question Bank plan from the template.
Setup Prerequisites
Prior to setting up the solutions you need to create and copy the template plan in the Master organization to selected organizations. You can create users and grant them privileges to modify or update the templates. Following are the steps you need to verify before setting up the audits solution:
Navigate to Quality >Setup >Collection Elements and choose your organization. In the Define Collection element form query all the seeded collection elements.
Setting Up 17-1
Navigate to Quality > Setup and choose the organization. Copy the Audit Collection Plan templates into the organization using the Setup > Copy collection plans Query and verify the collection plan data definition. You now have a new Audits collection plan type that can be launched by navigating to Setup> Collection Plan types.
3. 4.
Navigate to Quality > Setup > Inquiries > Parent Child Plan Inquiries. In the Update/Inquire Parent Child Collection Plan relationship page , select the organization where the Audit Collection Plans are setup Select the Parent Plan from the list of values and click on Go. Repeat for all the relationships defined.
3.
Verify that Audit Question Bank Collection plan has been copied from the template and is available in the Organization. Insert the Question Bank Data into the Question bank. Navigate to Quality: Audit Administration: Import Audit Questions. Go to Update Collection Import and verify the process status of the records. Go to View Quality Results form to confirm that the data has been inserted into the Audit Question Bank Collection Plan.
2. 3.
4.
Copying Audit Questions Navigate to Quality: Audits: Audit Setup: Copy Audit Questions. You can copy audit questions for a specific audit standard. You can copy audit questions from multiple standards. You can copy audit questions from multiple question categories for a specific audit standard and audit section.
You can copy audit questions from multiple question categories for specific audit standard, audit section, and audit area. You can copy audit questions from multiple question categories for specific audit standard, audit section, audit area, and question category.
Copy Audit Solution Template Copy Audit Solution Question Bank Modify Collection Plans Enter/Update Audit Question Bank Build Reports
Set Up Steps
Step 1. Copy Audit Solution Template:
1. 2. 3. 4. 5. 6. 7.
Navigate to the Copy Collections Plan page. Select Template from the Collection Plan Type list of values. Select Template Audit Master Plan from Collection Plan Name. Click on Search. The Audit Solution Template parent-child plans will be displayed. Click on Copy. Enter Collection plan name for each of the collection plans in the New Plan Name field. Enter the Destination Organization. Click Finish to complete the copy set up step of Audit Solution Template.
8. 9.
Setting Up 17-3
Navigate to the Copy Collections Plan page. Select Template from the Collection Plan Type list of values. Select Template Audit Question Bank Plan from Collection Plan Name. Click on Search. You will see the Audit Question bank plan displayed. Click on Copy. Enter Collection plan name for each of the collection plans in the New Plan Name field. Enter the Destination Organization. Click Finish to complete the copy set up step of Audit Solution Question Bank.
8. 9.
Navigate to Quality: Set Up: Collection Elements. Create additional collection elements as required by you.
You can modify the list of values for the collection elements. You can add or remove collection elements. You can modify the seeded actions. You can add any new actions.
Relationship.
2.
Modify the seeded plan relationships that are available as part of the audit template and the associated criteria and copy relationships to suit your needs. Establish a parent-child relationship to the CAR collection plan, so you can log a corrective action request should an audit finding necessitate that.
3.
Navigate to Quality: Set up: Users Group. You can restrict or give access to different users. Navigate to Quality: Set Up: Grant Privileges. You can restrict or grant privileges to different users.
2.
Navigate to Quality: Audits: Audit Administration: Add/Update Question Bank. Enter audits questions directly into the audit question bank collection plan. Navigate to Quality: Audits: Audit Administration: Import Audit Questions. You can also import audit questions into the audits question bank collection plan.
2.
To build a simple report based on a single collection plan, use Quality Results ReportWriter. Navigate to Quality: Set Up: Quality Results ReportWriter.. Once you build the report navigate to Quality: Audits: Audit Inquiry and Reporting and submit the report. To build a detailed and complex report based on parent-child collection plan data and cross-organization reports use Oracle Discoverer-Quality integration.
2.
3.
Setting Up 17-5
18
Implementation
Overview of Implementation
Once you have completed the set up steps, you are ready to implement the audits solution.
Process Steps
Step 1. Initiate Audit:
Use the Audit Master Plan to initiate the audit.
1.
Navigate to Quality: Audits: Audit Set Up: Initiate Audit. Choose Organization and Collection Plan. Generate audit number and identify audit team by entering the details like Lead
2.
Implementation 18-1
Auditor, Internal Auditor, Auditee, Standard, and Start and End Dates.
3. 4.
Record the scope and objectives of the audits. You can also attach the policies, procedures, and other reference documents that you will use to conduct the audit If you are using Oracle Projects to plan and schedule the audit, you can reference the project and task number in the Audit Master plan. You can notify personnel of upcoming audit through email and workflow notifications.
5.
6.
Copy the questions from the audit question bank to the audit being conducted by navigating to Quality: Audits: Audits Setup: Copy Audit Question. Select Organization Code. This would be the organization where the audit question bank is maintained. Select Audit Question Bank Name, which would be the collection plan containing all the audit questions that you copied during the set up. The other search criteria are optional. To copy only the audit questions from a particular audit standard, section, etc., you can enter these fields to narrow down the search. Click on Go. The audit questions that relate to your search criteria will display. To see the details of the audit questions, you can expnad each one and click on the hyperlink. Select the questions relevant to the audit you are conducting and click on Copy to Audit Plan. Enter the Organization and the Target Audit Question and Response Plan to which you want to copy the audit questions. Enter the Audit Number and click on Apply. You will receive a confirmation message.
2.
3.
4.
5.
6.
7.
8. 9.
Navigate to Quality: Audits: Audits Execution: Execute and Update Audit. Begin by querying the Audit Master Plan.
3. 4.
Navigate to the child - the Audit Question Plan. Enter your responses to the audit questions.
Navigate to the Audits Finding Collection Plan. Enter your comments, observations and findings.
Navigate to the CAR collection plan from the audit findings collection plan. Depending on the audit findings, log a corrective action request (CAR).
After reviewing the audit finding ascertaining that the findings are meeting the compliance standards, you can close the audit. Alternatively, if you find the audit findings not complying to the standards, and you have logged a CAR, you can schedule a follow-up audit.
2.
You can now generate a report of the audit you have conducted and submit it to for management review.
Implementation 18-3
The following diagrams illustrate the process flow and life cycle of both internal audits and external audits:
Implementation 18-5
19
Reporting
Reporting Overview
Reports on Corrective Action information can be created using the following tools: Quality Results Report Writer - Generate reports on a single collection plan (Corrective Action Request or Corrective Action Implementation) Oracle Discoverer - Generate reports that analyze data across multiple plans and providing an enterprise view of corrective action requests across multiple organizations.
Oracle Discoverer
Oracle Discoverer enables you to analyze Audits throughout your enterprise. Data from application schema is organized into Folders within Discoverer. The following are steps to build folders for audits:
Reporting 19-1
The following are the steps to build folders for audit analysis:
1.
Open business area, Quality Data Collection Analysis, using the Admin edition of Discoverer. Create Folders in this area from the following views: Q_<AUDIT MASTER PLAN>_V
Note: <AUDIT MASTER PLAN> refers to the name of your
2.
collection plan with spaces replaced by an underscore. the views are created dynamically when the collection plan is created or updated. The columns in the view correspond with the collection elements within the collection plan.
3.
Q_<AUDIT MASTER HISTORY PLAN>_V Q_<AUDIT FINDINGS PLAN>_V Q_<AUDIT FINDINGS HISTORY PLAN>_V Q_<AUDITS QUESTION AND RESPONSE PLAN>_V Q_<AUDITS QUESTION AND RESPONSE HISTORY PLAN>_V
Create Joins for these folders: One to Many Q_<AUDIT MASTER PLAN>_V.AUDIT_NUMBER
You can perform cross-plan analysis using Oracle Discoverer User Edition. For example, reporting all Defects and Causes by Supplier and time period. See Also Oracle Discoverer User's Guide
20
Tailoring Your Solution
Workflow Configuration
This solution includes generic workflow notifications for the Audit set of collection plans. You can replace these workflows with your own workflows. You can design Workflow notification messages in your own format. Responses entered on the notification can be written back to collection plans. Send notification to the next approver (higher authority)
Refer to Appendix M for a list of seeded workflow notifications provided as part of the audits solution. See: Workflow Configuration in Tailoring your Solution chapter for Nonconformances and Disposition Solution and the Corrective Action Requests.
(N) Quality: Setup > Collection Plan Perform a query on the collection plan associated with the notification needing modification. Select the Send Email element. Choose Action. Select the Send an electronic email notification action, then choose Action Details. The text area contains the notification's message text.
3. 4. 5. 6.
A
Nonconformance and Disposition Seeded Template Collection Plan Structure
B
Nonconformance and Disposition Seeded Template Collection Plan Details
Prompt Sequence 70 80 90 100 110 120 130 140 150 160 170 180 190 200 210 220 230 240 250 260
Collection Element Name Nonconform Item Type Item Revision Supplier Lot Number Quantity UOM Component Item Component Revision Component Lot Number Component Serial Number Component UOM Quantity Nonconforming Nonconforming UOM Short Description Nonconform Severity Nonconform Priority Nonconformance Type Nonconformance Code Project Number Task Number
Prompt Nonconform Item Type Item Rev Supplier Lot Quantity UOM Component Item Rev Comp Lot Number Comp Serial Number UOM Quantity Nonconforming Nonconforming UOM Short Description Nonconform Severity Nonconform Priority Nonconformance Type Nonconformance Code Project No Task No
Prompt Sequence 270 280 290 300 310 320 330 340 350 360 370 380
Collection Element Name Contract Number Contract Line Number Deliverable Number Job From Op Seq Number Operation Code From Intraoperation Step Email Address Distribution List Owner Send Email Entered by User
Prompt Contract Number Contract Line Number Deliverable Number Job From Op Seq From Operation Code From Intraop Email Address Distribution List Owner Send Email? User Name
Action Number
Action Invoked
Comment
Send Email
Equals YES
10
Nonconformance Number Nonconformance Source Short Description Detailed Description Nonconform Severity Nonconform Priority Nonconformance Type Nonconformance Code Nonconform Item Type Item Revision Quantity UOM
Nonconformance Number Nonconformance Source Description Detailed Description Nonconform Severity Nonconform Priority Nonconformance Type Nonconformance Code Nonconform Item Type Item Rev Quantity UOM
20
General
30 40 50 60 70
80
General
90
General
Prompt Sequence
Prompt
140
Quantity Nonconforming Nonconforming UOM Nonconformance Status Owner Email Address Distribution List Send Email Entered by User Date Opened Date Closed Days to Close Job From Op Seq Number Operation Code From Intraoperation Step Department To Op Seq Number To Operation Code
Quantity Nonconforming Nonconforming UOM Nonconformance Status Owner Email Address Distribution List Send Email? Entered by User Date Opened Date Closed Days to Close Job From Op Seq From Operation Code From Intraop
150
General
160
General
170 180 190 200 210 220 230 240 250 260 270 280
General General General General General General General General In-Process In-Process In-Process In-Process
Prompt Sequence
Prompt
320
To Intraoperation Step To Department Production Line Line Operation Component Item Component Revision Component UOM Component Lot Number Component Serial Number Component Subinventory Component Locator Project Number Task Number Contract Number Contract Line Number Deliverable Number Subinventory
To Intraop Step
To Dept Production Line Line Operation Component Item Component Revision Component UOM Component Lot Number Component Serial Number Component Sub
400
In-Process
410
In-Process
Component Locator Project Number Task Number Contract Number Contract Line Number Deliverable Number Sub
470 480
Projects Inventory
Prompt Sequence
Folder (For reference only - not seeded) Inventory Inventory Inventory Inventory Inventory Inventory Supplier Supplier Supplier Supplier Supplier Supplier Supplier Customer Customer Customer Customer Customer Maintenance
Prompt
490 500 510 520 530 540 550 560 570 580 590 600 610 620 630 640 650 660 670
Locator Lot Number Serial Number License Plate Number Lot Status Serial Status Supplier PO Number PO Line Number PO Release Number PO Shipment Supplier Lot Number PO Receipt Number Customer Sales Order Number SO Line Number RMA Number RMA Line Number Asset Group
Locator Lot Number Serial Number License Plate Number Lot Status Serial Status Supplier PO Number PO Line Number Rel Shipment Supplier Lot Number PO Receipt Number Customer Sales Order Number SO Line Number RMA Number RMA Line Number Asset Group
Prompt Sequence
Prompt
Asset Activity Asset Number Maintenance Work Order Service Request Incident Type Item Instance Item Instance Lot Item Instance Serial
Service Request Incident Type Item Instance Item Instance Lot Item Instance Serial Number Process Name Process Step Workflow Notification Send Notification To Process Batch Number Process Batch Step Num Process Operation Process Activity Process Resource
Process Name Process Step Workflow Notification Send Notification To Process Batch Number Process Batch Step Num Process Operation Process Activity Process Resource
790 830
Workflow Process
840
Process
Prompt Sequence
Prompt
880
Process Parameter
Process Parameter
Relationship Number 1
Parent Plan
Child Plan
Element Relationships All elements are copied to child plan to maintain audit trail Nonconformanc e number, Item, and Component item information is copied to child plan Some elements are copied to child plan Some elements are copied to child plan
Template Nonconformanc e Master Record History Plan Template Nonconformanc e Detail Plan
Delayed
Delayed
Delayed
Action Number
Action Invoked
Comment
Date Opened
Is Empty
Action Number
Action Invoked
Comment
Assign a value to a collection element Assign a Value to a collection element Assign a Value to a collection element
Update Date Closed with current date Calculate the Days to Close
Days to Close
Owner
Is entered
The e-mail address of the owner is assigned to Email Address Sends a workflow notification
Workflow Notification
Equals YES
Launch a Workflow
Prompt Sequence 80 90 100 110 120 130 140 150 160 170 180 190 200
Collection Element Name Nonconforming UOM Short Description Nonconform Severity Nonconform Priority Nonconformance Type Nonconformance Code Email Address Distribution List Owner Send Email Entered by User Workflow Notification Send Notification To
Prompt Nonconforming UOM Description Nonconform Severity Nonconform Priority Nonconformance Type Nonconformance Code Email Address Distribution List Owner Send Email? Entered by User Workflow Notification Send Notification To
Action Number
Action Invoked
Comment
Send Email
Equals YES
Action Number
Action Invoked
Comment
Launch a Workflow
10
Nonconformance Number Nonconform Line Num Nonconformance Source Nonconform Item Type Defect Code Cause Code
Nonconformance Number Nonconform Line Num Nonconformance Source Nonconform Item Type Defect Code Cause Code
20
General
30
General
40
General
50 60
General General
Prompt Sequence
Prompt
70
Nonconform Line Status Entered by User Item Revision Quantity Nonconforming Nonconforming UOM Lot Number Serial Number Component Item Component Revision Component UOM Component Lot Number Component Serial Number Note Type Notes Action Executed Action Executed By
Nonconform Line Status Entered by User Item Rev Quantity Nonconforming Nonconforming UOM Lot Number Serial Number Component Item Component Revision Component UOM Component Lot Number Component Serial Number Note Type Notes Action Executed Action Executed By
80 90 100 110
120
Material
190
Material
Prompt Sequence
Folder (For reference only - not seeded) Action Assignment Action Assignment Action Assignment Action Assignment Action Assignment Action Assignment Action Assignment
Prompt
Action Type Action Description Action Assigned To Email Address Distribution List Send Email Workflow Notification Send Notification To
Action Type Action Description Action Assigned To Email Address Distribution List Send Email Workflow Notification Send Notification To
310
Action Assignment
Parent-Child Relationships Relationship Number 1 Parent Plan Child Plan Data Entry Mode History Element Relationships All elements are copied to child plan to maintain audit trail The nonconformance specific elements are copied to the child plan
Delayed
Seeded Collection Plan Actions Action Number Collection Element Action Assigned to Condition and Value Is entered Action Invoked Comment
Send email
Equals YES
Workflow Notification
Equals YES
Prompt Sequence 70 80 90 100 110 120 130 140 150 160 170 180 190 200 210 220 230 240 250 260
Collection Element Name Item Job From Op Seq Number Quantity Nonconforming Nonconforming UOM Component Item Component Revision Component Lot Number Component Serial Number Subinventory Locator Transaction Date Reason Code Disposition Status Disposition Message Concurrent Request ID Launch Action Action Fired Owner Email Address
Prompt Item Job From Op Seq Quantity Nonconforming Nonconforming UOM Component Item Rev Comp Lot Number Comp Serial Number Subinventory Locator Transaction Date Reason Code Segregation Status Segregation Message Concurrent Request ID Launch Action Action Fired Owner Email Address
Parent-Child Relationships Relationship Number 1 Parent Plan Child Plan Data Entry Mode History Element Relationships All elements are copied to child plan to maintain audit trail
Seeded Collection Plan Actions Action Number Collection Element Default Values Condition and Value Equals YES Action Invoked Comment
Multiple collection element values are assigned, based on the nonconformance number from the Nonconformanc e Master plan WIP component return transaction triggered E-mail sent on status of the segregation
Launch Action
Equals YES
Disposition Status
Action Number
Action Invoked
Comment
Launch a Workflow
Prompt Sequence 130 140 150 160 170 180 190 200 210 220 230 240 250 260 270 280 290 300
Collection Element Name Lot Number Serial Number To Subinventory To Locator Date Required Project Number Task Number Disposition Status Disposition Message Move Order Number Concurrent Request ID Launch Action Action Fired Owner Email Address Distribution List Workflow Notification Send Notification To
Prompt Lot Number Serial Number To Subinventory To Locator Date Required Project Number Task Number Segregation Status Segregation Message Move Order Number Concurrent Request ID Launch Action Action Fired Owner Email Address Distribution List Workflow Notification Send Notification To
Parent-Child Relationships Relationship Number 1 Parent Plan Child Plan Data Entry Mode History Element Relationships All elements are copied to child plan to maintain audit trail
Seeded Collection Plan Actions Action Number Collection Element Default Values Condition and Value Equals YES Action Invoked Comment
Multiple collection element values are assigned, based on the nonconformance number from the Nonconformanc e Master plan Move order is created E-mail sent on status of the segregation Sends a workflow notification
Launch Action
Equals YES
Disposition Status
Workflow Notification
Plan Details Prompt Sequence 10 20 30 40 50 60 70 80 90 100 110 120 130 140 150 160 170 180 190 Collection Element Name Disposition Source Source Reference ID Source Ref Line ID Disposition Number Item Disposition Quantity Disposition UOM Disposition Disposition Status Disposition Desc Disposition Owner Owner Email Default Values Source Owner Source Owner Email Entered by User Send Email Date Opened Date Closed Prompt Disposition Source Source Reference ID Source Reference Line ID Disposition Number Item Disposition Quantity Disposition UOM Disposition Disposition Status Disposition Description Disposition Owner Owner Email Default Values Source Owner Source Owner Email Entered by User Send Email Date Opened Date Closed
Parent-Child Relationships Relationship Number 1 Parent Plan Child Plan Data Entry Mode Delayed Element Relationships Some elements copied to child plan All elements are copied to child plan to maintain audit trail
History
Seeded Collection Plan Actions Action Number Collection Element Default Values Condition and Value Equals YES Action Invoked Comment
Multiple collection element values are assigned, based on the nonconformance number from the Nonconformanc e Master plan E-mail address is assigned
Disposition Owner
Is entered
Action Number
Action Invoked
Comment
Send an electronic mail notification Assign a value to a collection element Assign a value to a collection element Assign a value to a collection element Launch a Workflow
E-mail sent on disposition details Current date is assigned to Date Opened Date Closed value is assigned
Date Opened
Is empty
Disposition Status
Equals CLOSED
Date Closed
Is entered
Workflow Notification
Equals YES
Prompt Sequence 60 70 80 90 100 110 120 130 140 150 160 170 180 190 200 210 220 230 240 250
Collection Element Name Default Values Item Revision Lot Number Serial Number Job Component Item Component Revision Component Lot Number Component Serial Number Subinventory Locator License Plate Number PO Number PO Line Number PO Release Number PO Receipt Number PO Shipment Disposition Quantity Disposition UOM
Prompt Default Values Item Rev Lot Number Serial Number Job Component Item Component Revision Component Lot Number Component Serial Number Subinventory Locator License Plate Number PO Number PO Line Number Rel PO Receipt Number Shipment Disposition Quantity Disposition UOM
Prompt Sequence 260 270 280 290 300 310 320 330 340 350 360 370 380 390 400
Collection Element Name Disposition Disposition Action Disposition Status Disposition Line Desc Implementation By Email Address Distribution List Disposition Owner Owner Email Source Owner Source Owner Email Send Email Disposition Module Workflow Notification Send Notification To
Prompt Disposition Disposition Action Disposition Status Disposition Line Desc Action Assigned to Email Address Distribution List Disposition Owner Owner Email Source Owner Source Owner Email Send Email Disposition Module Workflow Notification Send Notification To
Parent-Child Relationships Relationship Number 1 Parent Plan Child Plan Data Entry Mode Delayed with criteria Disposition Module = WIP Element Relationships Some elements are copied to child plan
Template In-Process related Disposition Action and Result Template Inventory related Disposition Action and Result Template Disposition Detail History Plan
History
Seeded Collection Plan Actions Action Number Collection Element Default Values Condition and Value Equals YES Action Invoked Comment
Multiple collection element values are assigned, based on the nonconformance number from the Nonconformanc e Master plan E-mail address is assigned
Implementation by
Is entered
Action Number
Action Invoked
Comment
Send an electronic mail notification Assign a value to a collection element Launch a Workflow
E-mail sent on disposition details Disposition Module is assigned Sends a workflow notification
Disposition Action
Workflow Notification
Equals YES
Prompt Sequence 70 80 90 100 110 120 130 140 150 160 170 180 190 200 210 220 230 240 250 260
Collection Element Name Disposition Action Default Values Item Job Maintenance Work Order New Rework Job Rework Job Job Class Start Date End Date Bill Reference BOM Revision Routing Reference Routing Revision Rework Op Seq Number Rework Operation Code Rework Department Resource Seq Num Resource Code Assigned Units
Prompt Disposition Action Default Values Item Job Maintenance Work Order New Rework Job Rework Job Name Job Class Start Date End Date Bill Reference Item BOM Revision Routing Reference Routing Revision Rework Op Seq Number Rework Operation Code Rework Department Resource Seq Num Resource Code Assigned Units
Prompt Sequence 270 280 290 300 310 320 330 340 350 360 370 380 390 400 410 420 430 440 450 460
Collection Element Name Usage Rate From Op Seq Number Operation Code From Intraoperation Step Department To Op Seq Number To Operation Code To Intraoperation Step To Department Production Line Line Operation Disposition Quantity Disposition UOM Job MRP Net Quantity Scrap Account Alias Project Number Task Number Component Item Component Revision Component Lot Number
Prompt Usage Rate From Op Seq Op Code From Intraop Dept To Op Seq To Operation Code To Intraop Step To Dept Production Line Line Operation Disposition Quantity Disposition UOM Job MRP Net Quantity Scrap Account Alias Project No Task No Component Item Component Revision Component Lot Number
Prompt Sequence 470 480 490 500 510 520 530 540 550 560 570 580 590 600 610 620 630 640 650
Collection Element Name Component Serial Number Component Subinventory Component Locator Transaction Date Reason Code Disposition Status Disposition Message Concurrent Request ID Launch Action Action Fired Implementation By Email Address Distribution List Disposition Owner Owner Email Source Owner Source Owner Email Workflow Notification Send Notification To
Prompt Component Serial Number Component Subinventory Component Locator Transaction Date Reason Code Disposition Status Disposition Message Concurrent Request ID Launch Action Action Fired Action Assigned to Email Address Distribution List Disposition Owner Owner Email Source Owner Source Owner Email Workflow Notification Send Notification To
Parent-Child Relationships Relationship Number 1 Parent Plan Child Plan Data Entry Mode History Element Relationships All elements are copied to child plan to maintain audit trail
Seeded Collection Plan Actions Action Number Collection Element Default Values Condition and Value Equals YES Action Invoked Comment
Multiple collection element values are assigned, based on the nonconformance number from the Nonconformanc e Master plan The disposition actions are executed in the background E-mail sent on disposition status Workflow notifications sent
Disposition Action
Disposition Status
Workflow Notification
Equals YES
logged and the disposition action is executed, the reference context might be stale; you can update it for this reason. The plan contains the following collection elements:
Plan Details Prompt Sequence 10 20 30 40 50 60 70 80 90 100 110 120 130 140 150 160 170 Collection Element Name Disposition Source Source Reference ID Source Ref Line ID Disposition Number Disposition Line Num Disposition Disposition Action Default Values Item Revision Subinventory Locator Lot Number Serial Number License Plate Number To Subinventory To Locator Prompt Disposition Source Source Reference ID Source Reference Line ID Disposition Number Disposition Line Number Disposition Disposition Action Default Values Item Rev Subinventory Locator Lot Number Serial Number License Plate Number To Subinventory To Locator
Prompt Sequence 180 190 200 210 220 230 240 250 260 270 280 290 300 310 320 330 340 350 360 370
Collection Element Name Move Order Number Date Required Disposition Quantity Disposition UOM Scrap Account Alias Project Number Task Number Transaction Date Reason Code Disposition Status Disposition Message Concurrent Request ID Launch Action Action Fired Implementation By Email Address Distribution List Disposition Owner Owner Email Source Owner
Prompt Move Order Number Date Required Disposition Quantity Disposition UOM Scrap Account Alias Project No Task No Transaction Date Reason Code Disposition Status Disposition Message Concurrent Request ID Launch Action Action Fired Action Assigned to Email Address Distribution List Disposition Owner Owner Email Source Owner
Collection Element Name Source Owner Email Workflow Notification Send Notification To
Parent-Child Relationships Relationship Number 1 Parent Plan Child Plan Data Entry Mode History Element Relationships All elements are copied to child plan to maintain audit trail
Seeded Collection Plan Actions Action Number Collection Element Default Values Condition and Value Equals YES Action Invoked Comment
Multiple collection element values are assigned, based on the nonconformance number from the Nonconformanc e Master plan The disposition actions are executed in the background
Disposition Action
Action Number
Action Invoked
Comment
Workflow Notification
Equals YES
C
Sample Code
funcmode IN VARCHAR2, result OUT NOCOPY VARCHAR2) IS 1_recipient VARCHAR2(1000); BEGIN 1_recipient := wf_engine.getitemattrtext( itemtype => itemkey, item key => itemkey, aname => 'RECIPIENT');
-- IF the notification is currently read by USER1, i.e. current approver -- then make USER2 the next approver to receive the notification IF (1_recipient = 'USER1') THEN wf_engine.setitemattritext ( item type => itemtype, item key aname avalue => itemkey, => 'RECIPIENT', => 'USER2';
result := 'COMPLETE:Y'; -- for Find Approver step to go back to Notification step ELSE result := 'COMPLETE:N'; -- No further approval required END IF; EXCEPTION WHEN OTHERS THEN wf_core.context ('qa_results_wf_pkg', 'find_approver',
itemtype, itemkey, to_char (actid), funcmode); raise; END find_approver; END xxcqa_approval_wf_pkg;
REM (NOPRINT suppresses their value in the detail) REM COLUMN today NOPRINT NEW_VALUE today COLUMN ncm_no NOPRINT NEW_VALUE ncm_no COLUMN part_no NOPRINT NEW_VALUE part_no COLUMN part_desc NOPRINT NEW_VALUE part_desc COLUMN revision NOPRINT NEW_VALUE revision COLUMN work_order NOPRINT NEW_VALUE work_order COULMN ncm_qty NOPRINT NEW VALUE ncm_qty COLUMN ncm_source NOPRINT NEW_VALUE ncm_source COLUMN ncm_severity NOPRINT NEW_VALUE ncm_severity COLUMN ncm_status NOPRINT NEW_VALUE ncm_status COLUMN from_op_seq NOPRINT NEW_VALUE from_op_seq REM REM The following block fo COLUMN statements declares the REM look and feel format of the detail elements. REM COLUMN ncm_line_num TRUNCATE HEADING "NCM Line" COLUMN identidy FORMAT A20 WORD_WRAPPED HEADING "identidy" COLUMN note_type FORMAT A9 TRUNCATE HEADING "Note Type" COLUMN notes FORMAT A43 WORD_WRAPPED HEADING "Notes" COLUMN requirement FORMAT A20 TRUNCATE HEADING "Requirement" COLUMN deviation FORMAT A10 TRUNCATE HEADING "Deviation" COLUMN disp_num FORMAT A7 TRUNCATE HEADING "Disp#"
COLUMN disp_line_num TRUNCATE HEADING "Disp Line" COLUMN disposition FORMAT A12 WORD_WRAPPED HEADING "Disposition" COLUMN disposition_source FORMAT A10 TRUNCATE HEADING "Source" COLUMN disp_desc FORMAT A40 WORD_WRAPPED HEADING "Description" COLUMN disp_status FORMAT A10 TRUNCATE HEADING "Status" COLUMN disp_owner FORMAT A10 TRUNCATE HEADING "Owner" COLUMN date_opened FORMAT A10 TRUNCATE HEADING "Date Opened" COLUMN date_closed FORMAT A10 TRUNCATE HEADING "Date Closed" COLUMN disp_action FORMAT A20 TRUNCATE HEADING "Action" COLUMN disp_line_desc FORMAT A50 WORD_WRAPPED HEADING "Description" REM REM The following is the look and feel of the header block. REM TTITLE CENTER 'MATERIAL REVIEW REPORT' skip 1 CENTER today skip 3 LEFT 'NCM Number LEFT 'Work Order :' ncm_no skip 1 :' work_order skip 1 -
LEFT 'Part Number :' part_no skip 1 LEFT 'Revision :' revision skip 1 -
LEFT 'Description :' part_desc skip 1 LEFT 'Qty LEFT 'Source LEFT 'Severity LEFT 'Status :' ncm_qty skip 1 :' ncm_source skip 1 :' ncm_severity skip 1 :' ncm_status skip 1 -
SELECT sysdate today, ncm_mst.nonconformance_number ncm_no, ncm_mst.item part_no, substr(msi.description, 1, 75) part_desc, ncm_mst.revision, ncm_mst.nonconformance_source ncm_source, ncm_mst.nonconformance_severity ncm_severity, ncm_mst.nonconformance_status ncm_status, ncm_mst.job work_order, ncm_mst.from_op_seq_number from_op_seq, ncm_dtl.nonconform_line_num ncm_line_num, ncm_dtl.identidy identidy, ncm_dtl.note_type note_type, ncm_dtl.notes notes, ncm_dtl.short_description requirement, ncm_dtl.deviation deviation FROM q_&&3._ncm_master_v ncm_mst,
ncm_mst.nonconformance_number = ncm_dtl.nonconformance_number (+) AND ncm_mst.item_id = msi.inventory_item_id (+) AND ncm_mst.organization_id = msi.organization_id (+)
ORDER BY ncm_line_num; TTITLE OFF REM REM We now query the dispostions for each ncm line REM REM BREAK ON ncm_line_num REM SELECT disp_hdr.source_ref_line_id ncm_line_num, REM REM REM REM REM REM REM REM FROM REM WHERE REM disp_hdr.source_reference_id = '&1' disp_hdr.disposition_number disp_num, disp_hdr.disposition_source, disp_hdr.disposition, disp_hdr.disposition_desc disp_desc, disp_hdr.disposition_status disp_status, disp_hdr.date_opened, disp_hdr.date_closed, q_&3._ncm_disp_hdr_v disp_hdr
REM ORDER BY ncm_line_num, disp_num; REM REM We now query the disposition details for each disposition REM BREAK ON ncm_line_num on disp_num SELECT disp_dtl.source_ref_line_id ncm_line_num,
disp_dtl.disposition_number disp_num, disp_dtl.disposition disposition, disp_dtl.disposition_action disp_action, disp_dtl.disposition_line_desc disp_line_desc disp_dtl.disposition_status disp_status FROM q_&3._ncm_disp_dtl_v disp_dtl WHERE disp_dtl.source_reference_id = '&1' ORDER BY ncm_line_num, disp_num; REM REM The following is a refinement of the above to also print REM out resource usage for each operation of each Rework Job REM disposition. REM COLUMN disp_num NOPRINT NEW_VALUE disp_num COLUMN disp_line_num NOPRINT NEW_VALUE disp_line_num COLUMN disp_action NOPRINT NEW_VALUE disp_action COLUMN disp_line_desc NOPRINT NEW_VALUE disp_line_desc COLUMN new_rework_job NOPRINT NEW_VALUE new_rework_job COLUMN op_seq FORMAT 9999 HEADING "Op" COLUMN dept_code HEADING "Department" COLUMN job_desc FORMAT A50 WORD_WRAPPED HEADING Description COLUMN assigned_units FORMAT 999 HEADING "AssignedUnits"
COLUMN scheduled_units FORMAT A9 HEADING "ScheduledUnits" COLUMN scheduled_flag FORMAT A3 HEADING Sch COLUMN resources FORMAT A10 HEADING Resources TTITLE skip 5 CENTER 'MATERIAL REVIEW REPORT' skip 1 CENTER 'Operation Resource Usage' skip 1 CENTER today skip 3 LEFT 'NCM Number LEFT 'Part Number LEFT 'Revision LEFT 'Description LEFT 'Disp LEFT 'Disp Line LEFT 'Disp Action LEFT 'Description LEFT 'Rework Job BREAK ON disp_num SELECT --+ leading (q_&3.ncm_disp_wip_v.qr) dis_dtl.disposition_number disp_num, disp_dtl.disposition_line_num disp_line_num, disp_dtl.disposition_action disp_action, disp_dtl.disposition_line_desc disp_line_desc, disp_wip.new_rework_job, wor.operation_seq_num op_seq, wor.department_code dept_code, :' ncm_no skip 1 :' part_no skip 1 :' revision skip 1 :' part_desc skip 2 :' disp_num skip 1 :' disp_line_num skip 1 :' disp_action skip 1 :' disp_line_desc skip 1 :' new_rework_job skip 3
wor.resource_code resources, wor.assigned_units, wor.scheduled_units, decode(wor.scheduled_flag, 1, 'Y', 'N') scheduled_flag, wor.description job_desc FROM q_&3._ncm_disp_dtl_v disp_dtl, q_&3._ncm_disp_wip_v disp_wip, wip_entities we, wip_operation_resources_v wor WHERE disp_wip.disposition_number = disp_dtl.disposition_number AND (disp_dtl.disposition_line_num IS NULL OR disp_wip.disposition_line_num = disp_dtl.disposition_line_num) AND disp_wip.new_rework_job = we.wip_entity_name AND we.wip_entity_id = wor.wip_entity_id AND we.organization_id = disp_wip.organization_id AND disp_dtl.source_reference_id = '&1' ORDER BY disp_num, disp_line_num; COLUMN ncm_status FORMAT A10 HEADING Status COLUMN owner FORMAT A20 HEADING Owner COLUMN detail_desc FORMAT A50 WORD_WRAPPED HEADING Description COLUMN last_update_date HEADING 'Date' TTITLE skip 5 CENTER 'MATERIAL REVIEW REPORT' skip 1 -
CENTER 'Disposition History' skip 3 LEFT 'NCM Number :' ncm_no skip 1 -
LEFT 'Part Number :' part_no skip 1 LEFT 'Revision :' revision skip 1 -
LEFT 'Description :' part_desc skip 3 COLUMN title FORMAT A80 HEADING 'Details' SELECT ' ' as title FROM DUAL WHERE &&2 = 1; DECLARE 1_prev q_&3._ncm_disp_dtl_hist_v%ROWTYPE; first BOOLEAN := true; BEGIN IF &2 = 1 THEN FOR r IN (SELECT * FROM q_&3._ncm_disp_dtl_hist_v WHERE source_reference_id = &1 ORDER BY source_ref_line_id, disposition_number, creation_date) LOOP IF first THEN dbms_output.put_line('Disposition ' ll r.disposition_number ll ' created: 'llto_char(r.creation_date, 'DD-MON-YYYY HH24:MI:SS') ll ' by ' ll r.created_by); dbms_output.put_line('.'); 1_prev :=r;
first := false; ELSE IF (1_prev.source_ref_line_id <> r.source_ref_line_id) OR (1_prev.disposition_number <> r.disposition_number)THEN dbms_output.put_line('Disposition ' ll r.disposition_number ll ' created: 'llto_char(r.creation_date, 'DD-MON-YYYY HH24:MI:SS') ll ' by ' 11 r.created_by); dbms_output.put_line('.'); ELSE dbms_output.put_line(Record updated: 'llto_char(r.creation_date, 'DD-MON_YYYY HH24:MI:SS') ll ' by ' 11 r.created_by); IF r.disposition_status <> 1_prev.disposition_status THEN dbms_output.put_line('Disposition status updated from: 'll 1_prev.disposition_status ll ' to: 'll r.disposition_status); END IF; IF r.disposition <> 1_prev.disposition THEN dbms_output.put_line('Description updated from: 'll 1_prev.disposition ll' to: 'll r.disposition); END IF; ---
dbms_output.put_line('.'); END IF; 1_prev :=r; END IF; END LOOP; END IF; END;
D
Stand-alone Collection Plan for Nonconformances Entered via Mobile Applications and Warehouse Management
Setting Up
A stand-alone collection plan needs to be created and associated with every mobile transaction where nonconformances can be logged, for example, License Plate Number Inspection.
Stand-alone Collection Plan for Nonconformances Entered via Mobile Applications and Warehouse Management D-1
Sequence 50 60 70 80 90 100 110 120 130 140 150 160 170 180 190
Collection Element Name Nonconformance Type Nonconformance Code Nonconform Item Type Item Revision Quantity UOM Quantity Nonconforming Nonconforming UOM Nonconformance Status Owner Email Address Send Email Entered by User Date Opened
Prompt Nonconformance Type Nonconformance Code Nonconform Item Type Item Rev Quantity UOM Quantity Nonconforming Nonconforming UOM Nonconformance Status Owner Email Address Send Email Entered by User Date Opened
Stand-alone Collection Plan for Nonconformances Entered via Mobile Applications and Warehouse Management D-3
SQL Text
declare retval number; creid number; CURSOR USERID IS SELECT USER_ID FROM FND_USER WHERE USER_NAME = '&CRE'; begin INSERT INTO Q_NONCONFORMANCE_MASTER_IV ( PROCESS_STATUS, ORGANIZATION_CODE, PLAN_NAME, INSERT_TYPE, NONCONFORMANCE_SOURCE, NONCONFORM_ITEM_TYPE, ITEM, REVISION,
QUANTITY, UOM, QUANTITY_NONCONFORMING, NONCONFORMING_UOM, SHORT_DESCRIPTION, NONCONFORM_SEVERITY, NONCONFORM_PRIORITY, NONCONFORMANCE_TYPE, NONCONFORMANCE_CODE ) values ( 1, &ORG, 'NONCONFORMANCE MASTER', 1, &NCSOURCE, &ITEMTYPE, &ITEM, &ITEMREV, &QTY, &ITEMUOM, &SDESC,
Stand-alone Collection Plan for Nonconformances Entered via Mobile Applications and Warehouse Management D-5
&NCSEV, &NCPRI, &NCTYPE, &NCCODE ); OPEN USERID FETCH USERID INTO creid; retval:=fnd_request.submit_request ( application=>'QA', program=>'QLTTRAMB', argument1=>'20', argument2=>'1', argument3=>creid, argument4=>'NO'); commit; end; /
E
Collection Elements for Automated Disposition Action Processing
Collection Plans
The following tables list the mandatory and optional collection elements to execute an automated disposition within Oracle Quality.
Optional Collection Elements BILL REFERENCE BOM REVISION ROUTING REFERENCE ROUTING REVISION DISPOSITION QUANTITY JOB MRP NET QUANTITY
Disposition Action: Component Return to Inventory (WIP_COMP_RETURN) and Component Issue to Job (WIP_COMP_ISSUE) Mandatory Collection Elements JOB COMPONENT ITEM OPERATION_SEQ_NUMBER COMPONENT SUBINVENTORY DISPOSITION QUANTITY UOM REASON CODE REVISION (if applicable) COMPONENT LOT (if applicable) COMPONENT SERIAL NUMBER (if applicable) Optional Collection Elements -
Mandatory Collection Elements COMPONENT LOCATOR (if applicable) TRANSACTION DATE (if applicable)
Disposition Action: Move to Rework Operation (WIP_MOVE _REWORK) Mandatory Collection Elements JOB ITEM DISPOSITION QUANTITY UOM FROM & TO OPERATION SEQUENCE NUMBER FROM & TO INTRAOPERATION STEPS TRANSACTION DATE REASON_CODE Optional Collection Elements FROM & TO OPERATION CODE -
Disposition Action: Assembly Scrap (WIP_MOVE_SCRAP) Mandatory Collection Elements JOB ITEM DISPOSITION QUANTITY UOM Optional Collection Elements -
Mandatory Collection Elements FROM & TO OPERATION SEQUENCE NUMBER FROM & TO INTRAOPERATION TRANSACTION DATE SCRAP ACCOUNT ALIAS
Disposition Action: Add Rework Operation (WIP_REWORK_OP) Mandatory Collection Elements JOB REWORK OP SEQ NUMBER REWORK OPERATION CODE REWORK DEPARTMENT RESOURCE SEQ NUM RESOURCE CODE ASSIGNED UNITS USAGE RATE START DATE END DATE Optional Collection Elements -
Disposition Action: Creation of Inventory Move Order (INV_MOVE_ORDER) Mandatory Collection Elements ITEM DISPOSITION QUANTITY DISPOSITION UOM DATE REQUIRED FROM SUBINVENTORY TO SUBINVENTORY REVISION (if applicable) FROM LOCATOR (if applicable) TO LOCATOR (if applicable) PROJECT NUMBER (if applicable) TASK NUMBER (if applicable) LOT NUMBER (if applicable) SERIAL NUMBER (if applicable) Optional Collection Elements -
Disposition Action: Inventory Scrap (INV_SCRAP_AAI) Mandatory Collection Elements ITEM SUBINVENTORY SCRAP ACCOUNT ALIAS Optional Collection Elements TRANSACTION DATE -
Mandatory Collection Elements DISPOSITION QUANTITY DISPOSITION UOM REVISION (if applicable) LOT (if applicable) SERIAL NUMBER (if applicable)
F
Nonconformance and Disposition Seeded Workflows Notifications
G
Corrective Action Seeded Template Collection Plan Structure
H
Corrective Action Seeded Template Collection Plan Details
Prompt Sequence 70 80 90 100 110 120 130 140 150 160 170 180 190 200 210 220 230 240 250 260
Collection Element Name Section Violated Problem Solving Method Item Revision Customer Sales Order Number RMA Number Contract Number Contract Line Number Deliverable Number Supplier Supplier Site PO Number PO Line Number PO Release Number PO Shipment PO Receipt Number Department Request Priority Request Severity
Prompt Section Violated Problem Solving Method Item Rev Customer Sales Order Number RMA Number Contract Number Contract Line Number Deliverable Number Supplier Supplier Site PO Number Line Rel Shipment Receipt Dept Request Priority Request Severity
Prompt Sequence 270 280 290 300 310 320 330 340 350 360 370 380 390 400 410 420 430 440 450 460
Collection Element Name Short Description Detailed Description Cause Code Root Cause Systemic Root Cause Request Status Requestor Source Owner Email Owner Email Address Distribution List Date Opened Date Closed Expected Resolution Date Actual Resolution Date Follow up Date Approved By Approval Date Send Email Total Actions
Prompt Problem Description Detailed Description Cause Code Root Cause Systemic Root Cause Request Status Requestor Requestor Email Owner Email Address Distribution List Date Opened Date Closed Expected Resolution Date Actual Resolution Date Follow up Date Approved By Approval Date Send Email Total Actions
Prompt Sequence 470 480 490 500 510 520 530 540
Collection Element Name Pending Actions Review Cost Estimate Review Cost Actual Implementation Estimate Implementation Actual Days to Close Workflow Notification Send Notification To
Prompt Pending Actions Review Cost Estimate Review Cost Actual Implementation Estimate Implementation Actual Days to Close Workflow Notification Send Notification To
Relationship Number 1
Parent Plan
Child Plan
Element Relationships All elements are copied to child plan to maintain audit trail
Relationship Number 2
Parent Plan
Child Plan
Element Relationships Corrective Action Num, Reference request Num, Request Source, Request Type, Item, Revision, and Request Priority are copied to the child plan. Review Cost Estimate, Implementation Actual, and Pending Actions are the summation of the corresponding elements within the child plan.
Relationship Number 3
Parent Plan
Child Plan
Element Relationships Corrective Action Num, Reference request Num, Request Source, Request Type, Item, Revision, and Request Priority are copied to the child plan. Implementation Estimate, Implementation Actual, and Pending Actions are the summation of the corresponding elements within the child plan.
Delayed
Action Number
Action Invoked
Comment
Default the e-mail address of the requestor Default the e-mail address of the owner
Owner
Is entered
Action Number
Action Invoked
Comment
Assign a value to a collection element Assign a value to a collection element Assign a value to a collection element Send an electronic email notification Launch a Workflow
Make Date opened as current date Update Date Closed with current date Calculate the Days to Close
Request Status
Equals CLOSED
Days to Close
Send Email
Equals YES
Workflow Notification
Equals YES
Prompt Sequence 50 60 70 80 90 100 110 120 130 140 150 160 170 180 190 200 210 220 230 240
Collection Element Name Request Priority Request Severity Item Revision Request Status Action Type Action Description Action Assigned to Email Address Distribution List Action Executed By Note Type Notes Expected Resolution Date Actual Resolution Date Send Email Review Cost Estimate Review Cost Actual Approved By Approval Date
Prompt Request Priority Request Severity Item Rev Review Action Status Action Type Action Description Action Assigned to Email Address Distribution List Review Executed By Note Type Notes Due Date Actual Resolution Date Send Email Review Cost Estimate Review Cost Actual Approved By Approval Date
Parent-Child Relationships Relationship Number 1 Parent Plan Child Plan Data Entry Mode History Element Relationships All elements are copied to child plan to maintain audit trail
Seeded Collection Plan Actions Action Number Collection Element Action Assigned to Condition and Value Is entered Action Invoked Comment
Default the e-mail address of the assignee Send an electronic email notification Launch a Workflow
Send Email
Equals YES
Workflow Notification
Equals YES
Plan Details Prompt Sequence 10 20 30 40 50 60 70 80 90 100 110 120 130 140 150 160 170 180 190 Collection Element Name Corrective Action Num Reference Request Num Request Source Request Type Request Priority Request Severity Item Revision Request Status Implementation Type Short Description Action Assigned to Email Address Distribution List Action Executed By Note Type Notes Expected Resolution Date Actual Resolution Date Prompt Corrective Action Num Reference Request Num Request Source Request Type Request Priority Request Severity Item Rev Implementation Status Implementation Action Short Description Action Assigned to Email Address Distribution List Review Executed By Note Type Notes Due Date Actual Resolution Date
Prompt Sequence 200 210 220 230 240 250 260 270 280
Collection Element Name Follow up Date Send Email Implementation Estimate Implementation Actual Pending Actions Approved By Approval Date Workflow Notification Send Notification To
Prompt Follow up Date Send Email Implementation Estimate Implementation Actual Pending Actions Approved By Approval Date Workflow Notification Send Notification To
Parents-Child Relationship Relationship Number 1 Parent Plan Child Plan Data Entry Mode History Element Relationships All elements are copied to child plan to maintain audit trail Some of the elements are copied from parent to child plans
Delayed
Seeded Collection Plan Actions Action Number Collection Element Requestor Condition and Value Is entered Action Invoked Comment
Default the e-mail address Execute a SQL Script Send an electronic email notification Launch a Workflow
Launch Action
Equals YES
Disposition Status
Workflow Notification
Prompt Sequence 70 80 90 100 110 120 130 140 150 160 170 180 190 200 210
Collection Element Name New ECO Name ECO Type ECO Description ECO Approval List ECO Reason Code Requestor ECO Department ECO Priority Launch Action Action Fired Disposition Status Disposition Message Email Address Distribution List ECO Name
Prompt New ECO Name ECO Type ECO Description ECO Approval List ECO Reason Code Requestor ECO Department ECO Priority Launch Action Action Fired Submission Status Submission Status Email Address Distribution List ECO Name
Parent-Child Plans Relationship Number 1 Parent Plan Child Plan Data Entry Mode History Element Relationships All elements copied to child plan to maintain audit trail
Seeded Collection Plan Actions Action Number Collection Elements Requestor i Condition Action Invoked Comment
Is entered
Default the email address Execute a SQL Script Send an electronic mail notification Launch a workflow
Launch Action
Equals YES
Disposition Status
Workflow notification
Prompt Sequence 70 80 90 100 110 120 130 140 150 160 170 180
Collection Element Name PO Line Number PO Release Number PO Shipment Implementation Type Action Executed By Note Type Notes Expected Resolution Date Actual Resolution Date Follow up Date Email Address Send Email
Prompt Line Rel Shipment Implementation Type Implementation By Note Type Notes Due Date Actual Resolution Date Follow up Date Email Address Send Email
to directly record their responses to the CAR, please remove the Notes collection element from this plan; add a new element of datatype Character.
Parent-Child Relationships Relationship Number 1 Parent Plan Child Plan Data Entry Mode History Element Relationships All elements are copied to child plan to maintain audit trail
Seeded Collection Plan Actions Action Number Collection Element Send Email Condition and Value Equals YES Action Invoked Comment
Is entered
Prompt Sequence 30 40 50 60 70 80 90 100 110 120 130 140 150 160 170 180 190 200 210 220
Collection Element Name Supplier Supplier Site PO Number PO Line Number PO Release Number PO Shipment Root Cause Systemic Root Cause Review Cost Estimate Review Cost Actual Implementation Estimate Implementation Actual New ECO Name ECO Type ECO Description ECO Approval List ECO Reason Code Requestor ECO Department ECO Priority
Prompt Supplier Supplier Site PO Number Line Rel Shipment Root Cause Systemic Root Cause Review Cost Estimate Review Cost Actual Implementation Estimate Implementation Actual New ECO Name ECO Type ECO Description ECO Approval List ECO Reason Code Requestor ECO Department ECO Priority
Prompt Sequence 230 240 250 260 270 280 290 300
Collection Element Name Launch Action Action Fired Disposition Status Disposition Message Email Address Send Email Distribution List ECO Name
Prompt Launch Action Action Fired Submission Status Submission Message Email Address Send Email Distribution List ECO Name
Seeded Collection Plan Actions Action Number Collection Element Send Email Condition and Value Equals YES Action Invoked Comment
Launch Action
Equals YES
I
Corrective Action Sample Code
COLUMN today NOPRINT NEW_VALUE today COLUMN car_no NOPRINT NEW_VALUE car_no COLUMN part_no NOPRINT NEW_VALUE part_no COLUMN part_desc NOPRINT NEW_VALUE part_desc COLUMN revision NOPRINT NEW_VALUE revision COLUMN work_order NOPRINT NEW_VALUE work_order COULMN car_qty NOPRINT NEW VALUE car_qty COLUMN car_source NOPRINT NEW_VALUE car_source COLUMN car_severity NOPRINT NEW_VALUE car_severity COLUMN car_status NOPRINT NEW_VALUE car_status COLUMN from_op_seq NOPRINT NEW_VALUE from_op_seq REM REM The following block fo COLUMN statements declares the REM look and feel format of the detail elements. REM COLUMN note_type FORMAT A15 TRUNCATE HEADING "Review Type" COLUMN notes FORMAT A30 WORD_WRAPPED HEADING "Action" COLUMN due_date FORMAT A10 TRUNCATE HEADING "Due Date" COLUMN actual_resolution_date FORMAT A11 TRUNCATE HEADING "Actual Date" REM REM The following is the look and feel of the header block. REM TTITLE CENTER 'CAR REPORT' skip 1 CENTER today skip 3 -
LEFT 'Part Number :' part_no skip 1 LEFT 'Description :' part_desc skip 1 LEFT 'Source LEFT 'Severity LEFT 'Status :' car_source skip 1 :' car_severity skip 1 :' car_status skip 2 -
SELECT sysdate today, car_req.corrective_action_num car_no, car_req.item part_no, substr(msi.description, 1, 75) part_desc, car_req.revision, car_req.request_source car_source, car_req.request_severity car_severity, car_req.request_status car_status, car_rvw.expected_rsolution_date due_date, car_rvw.actual_rsolution_date actual_resolution_date, car_rvw.action_type note_type, car_rvw.action_description notes, FROM q_&&2_request_v car_req,
J
Corrective Action Solution Seeded Workflow Notifications
K
Audits Seeded Template Collection Plan Structure
L
Audits Seeded Template Plan Details
Prompt Sequence 100 110 120 130 140 150 160 170 180 190 200 210
Collection Element Name Registrar External Auditor External Auditee Start Date End Date Audit Status Customer Supplier Supplier Site Project Number Task Number Internal Auditor Email
Prompt Registrar External Auditor External Auditee Start Date End Date Audit Status Customer Supplier Audited Supplier Site Project Number Task Number Internal Auditor Email Address Internal Auditee Email Address Send Email? Audit Result Procedure Exists? Procedure Adequate? Procedure Compliant? Due Date
220
Send Email Audit Result Procedure Exists Procedure Adequate Procedure Compliant Due Date
Collection Element Name Follow up Date Notes Workflow Notification Send Notification to
Prompt Internal Auditor Email Address Internal Auditee Email Address Send Email Workflow Notification Send Notification to
200
Collection Element Name Internal Auditee Department Standard Violated Section Violated Audit Area Supplier Supplier Site Question Category Question Code Audit Question Detailed Description Due Date Notes
Prompt Internal Auditee Department Audit Standard Basis Audit Section Audit Area Supplier Audited Supplier Information Question Category Question Code Audit Question Audit Response Response Date Auditor Comments
Prompt Sequence 40 50 60 70 80
Collection Element Name Question Category Question Code Audit Question Detailed Description Notes
Prompt Question Category Question Code Audit Question Auditor Response Auditor Comments
M
Audits Seeded Workflow Notifications
N
Windows and Navigation Paths
Navigation Path iSupplier Portal: Shipment > Quality > Available Quality Plans Quality: Setup > Update Parent Child Plan Relationship Quality: Setup > User Groups Quality: Audits > Audit Administration Quality: Audits > Audit Administration Quality: Audits > Audit Administration Quality: Audits > Audit Administration Quality: Audits > Audit Setup Quality: Audits> Audit Setup Quality: Audits> Audit Setup Quality: Audits > Audit Execution Quality: Audit > Audit Execution Quality: Audit > Audit Inquiry and Reporting
User Groups Copy Audit Templates Collection Plan Modification Update Audit Plan Relationships Add/Update Question Bank Initiate Audit Copy Audit Questions Update Audit Questions Execute and Update Audit Corrective Action Update View Audits
Index
Symbols
Nonconformance and Disposition Lifecycle, 2-14 generating reports, 13-1 Corrective Action Information Generating Reports Quality Results Report Writer, 13-1 Corrective Action Plan Processing Corrective Action from a Nonconformance Confirming the Parent-child setup, 12-11 Parent-Child Plan criteria, 12-10 Corrective Action Request Sources, 10-2 Corrective Action Request Types, 10-2 CAR requiring Supplier Action, 10-2 Customer initiated CAR, 10-2 Customer initiated CAR requiring Supplier Action, 10-2 Internal CAR, 10-2 Internal CAR requiring Supplier Action, 10-2 Corrective Action Solution Considerations prior to implementation, 11-15 Reference Copy of Collection Plans, 1116 Corrective Action Process, 10-4 Corrective Action Process Flow, 10-4 executing the custom report, 14-13 Implementation Checklist, 10-7 Implementation Considerations, 10-1 Prerequisites, 10-1 Valid Values, 10-3 Implementing, 12-1 Processing corrective action from an audit, 12-1 Overview of Implementation Roadmap, 10-1 Overview of Solution Templates, 9-1
A
Audits Solution Implementation overview, 16-1 prerequisites, 16-1 Implementation Tasks, 16-2 audit setup tasks, 16-2 system administrator tasks, 16-2 overview, 15-1 Solution Templates, 15-1 Contents, 15-2 Features, 15-2 Objectives, 15-1 Types of Audits, 16-1 external audits of suppliers, 16-1 internal audits within an organization, 16-1
C
Collection Elements for Automated Disposition Action Processing, E-1 Collection Plans Window, 3-11 Contents Nonconformance and Disposition Solution Templates, 1-2 Corrective Action Data Privileges, 10-4 Corrective Action Identification, 10-4 Corrective Action information
Index-1
Processing Corrective Action for a Supplier, 12-22 Corrective Action- Action assigned, 1224 Corrective Action- Analysis Action, 1224 Corrective Action- For Analysis, 12-23 E-mail Notification to Supplier, 12-26 iSupplier Portal, 12-28 Notification to supplier, 12-27 Processing the corrective action, 12-22 Supplier CAR Review, 12-25 Processing Corrective action from a Customer complaint, 12-32 logging a CAR, 12-34 logging a service request, 12-33 Processing corrective action from an audit CAR approval, 12-5 CAR History Plans, 12-8 CAR implementation process- Child Plan, 12-7 CAR Item/Supplier/Contract/Customer information, 12-2 CAR priority and description, 12-3 CAR review process- Child Plan, 12-7 Cost estimates and actual cost tracking, 12-5 Finding the CAR root cause, 12-3 Parent-child collection plan structure, 126 Saving the CAR, 12-5 Submitting a CAR, 12-1 Tracking a CAR lifecycle, 12-4 Using e-mail in CAR process, 12-4 Viewing or updating the CAR, 12-6 Processing Corrective Action from a Nonconformance, 12-8 Adding information to the CAR, 12-17 Defining a Parent-Child Collection Plan Relationship, 12-9 Entering the Nonconformance, 12-12 Entering the Nonconformance detail child plan, 12-14 Entering the Nonconformance Master Plan, 12-13 Initiating a CAR, 12-16 Logging Corrective Action within
Nonconformance detail, 12-15 Self Service query of CAR Plan, 12-20 Self Service Query of Nonconformance Detail Plan, 12-20 Self Service Query of the Nonconformance and Corrective Action , 12-18 Setting up CAR as a Child Plan, 12-8 Setting Up Add user defined elements, 11-11 Choose a configuration, 11-2 Collection Element Security, 11-14 Collection Plan Security, 11-13 Copy from template, 11-2 Link user defined plans, 11-12 Modify Collection Plan Details, 11-11 Organize the plan elements, 11-13 Overview, 11-1 Setup Checklist, 11-2 Set up profile options, 11-13 Setup within other modules, 11-13 Update of menu entry, 11-7 Update of Sequence, 11-5 Update of Values, 11-6 setting up a custom report, 14-11 Solution Templates, 9-1 Contents, 9-1 Features, 9-2 Tailoring Solutions Overview, 14-1 Workflow Configuration, 14-1 Corrective Action Solution Implementation Consideration Captured Data, 10-3 Solution Templates Objectives, 9-1 Corrective Action Solutions Considerations prior to implementation Evaluation of Reference Copy of Collection Plan, 11-16
D
Disposition determine, 4-8 initiate, 4-8 review nonconformance status closure, 4-8
Index-2
F
Features Nonconformance and Disposition Solution Templates, 1-2
L
Logging Nonconformance, 4-3 Customer, 4-5 Determine Disposition, 4-8 Direct Data Entry, 4-6 Implementation Considerations, 4-6 Initiate Disposition, 4-8 Inventory, 4-4 Maintenance, 4-5 Mobile Devices (WMS/MSCA), 4-5 Nonconformance Details and Action Assignment, 4-7 OPM Batch Processing, 4-6 Receiving, 4-3 Review by Owner, 4-6 review nonconformance status closure, 4-8 Segregation of Nonconforming Material, 4-6 Supplier, 4-3 Work in Process, 4-4 Logging Nonconformance Non-Material, 4-5 Logging Nonconformances MSCA and Oracle Warehouse Management, 5-2 Logging Nonconformances using MSCA and Oracle Warehouse Management, 5-1
N
Nonconformance and Disposition Solution Implementation, 2-1 Implementation Checklist, 2-16 Implementation Roadmap, 2-12 Organization of Data, 2-6 Setting up Approval Process, 8-4 Setup Checklist, 3-2 Setup Sets Update of Menu Entry, 3-11
Setup Steps Add User Defined Elements, 3-21 Considerations prior to implementation, 3-27 Copy from Template, 3-3 De-link Collection Plans, 3-25 Link Corrective Action System, 3-23 Link the Transactional Collection Plan, 324 Link user defined plans, 3-22 Maintaining Reference Copy, 3-27 Modify Collection Plan, 3-16 Organize the Plan Elements, 3-27 Set Up Collection Plan Security, 3-20 Set up Profile Options, 3-27 Update 'Execute a SQL Script', 3-17 Update of Sequence, 3-8 Update of Values, 3-10 Solution Templates Contents, 1-2 Tailoring E-mail Notifications, 8-5 Tailoring your Solution Tips and Techniques, 8-6 Using Oracle Approval Management, 8-3 Workflow Configuration, 8-1 Workflow Process Diagram, 8-2 Nonconformance and Dispositions Solution disposition lifecycle, 6-1 nonconformance lifecycle, 4-1 overview of setting up, 3-2 process steps, 4-2 reporting, 7-1 Setup Steps Choose a Configuration, 3-3 Solution Templates Features, 1-2 Objectives, 1-1 Tailoring your solution, 8-1 Nonconformance Lifecycle, 4-1 process flow chart, 4-1 Nonconformance Management Flow, 2-13
O
Objectives Nonconformance and Disposition Solution
Index-3
Templates, 1-1 Oracle Discoverer, 7-3 Overview setting up the nonconformance and disposition solution, 3-2 Overview of Setting Up nonconformance and disposition solution, 3-2
P
Process Flow Chart disposition lifecycle, 6-1 nonconformance lifecycle, 4-1 Process Steps logging nonconformances using MSCA and Oracle Warehouse Management, 5-1 logging nonconformances, 5-2 setting up, 5-1 nonconformance lifecycle, 4-2
Q
Quality Results Report Writer, 7-1 corrective action reports, 13-1
R
Reporting nonconformance and disposition solution, 7-1 Reporting Overview nonconformance and disposition solution oracle discoverer, 7-3 quality results report writer, 7-1
T
Tailoring Solutions Corrective Action Solutions, 14-1
W
Workflow Configuration starting workflow builder, 14-2
Index-4