This chapter covers the following topics:
Reports on Corrective Action information can be created using the following tools:
Quality Results Report Writer - suitable for reporting on a single collection plan (Corrective Action Request or Corrective Action Implementation)
Oracle Discoverer - suitable for analyzing data across multiple plans and providing an enterprise view of corrective action requests across multiple organizations.
The Oracle Quality Results Report Writer can be utilized to build simple reports on corrective action requests, based on a single collection plan. You can create reports, like the following, and custom build them according to your business needs:
All Corrective Action Requested for a given item or assembly
Supplier CARs in a specific time period
All Open CARs
CAR Cycle Time
Cause Code Report
Corrective Action Implementation Report
Corrective Action Review History Report
The current functions (sum, count, average) available in Report Writer can be utilized to provide additional information on numerical collection elements.
Report Setup Example
We will define a report for the average time to close a CAR.
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
For report columns, list the following:
Request Source
Days to Close, Function: Average
Criteria: All CAR after March 1, 2003
Quality Results Report Writer - Report Definition
Report Output Example
Nonconformance Source | Days to Close |
---|---|
Customer | 2.5 |
Audit | 3.85 |
Nonconformance | 1.5 |
Oracle Discoverer enables you to analyze Corrective Action throughout your enterprise. Data from application schema is organized into Folders within Discoverer.
Building Folders for Corrective Action Analysis
Open business area, Quality Data Collection Analysis, using the Admin edition of Discoverer.
Create Folders in this area from the following views:
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
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