Search Results qa_pc_criteria
Overview
The QA_PC_CRITERIA table is a core data object within the Quality (QA) module of Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2. It functions as a rule repository for the hierarchical Quality Plans feature. Specifically, it stores the conditional criteria that determine when a child quality plan becomes applicable and should be executed within a parent-child plan relationship. This enables the creation of sophisticated, context-driven quality management workflows where the activation of subordinate inspection or data collection plans is contingent upon specific conditions being met in a parent plan, such as a particular test result or characteristic value.
Key Information Stored
The table's structure is designed to define a single criterion rule. Its primary columns, as indicated by its foreign key relationships, are CRITERIA_ID, PLAN_RELATIONSHIP_ID, and CHAR_ID. The CRITERIA_ID serves as the unique primary key for each rule. The PLAN_RELATIONSHIP_ID links the criterion to a specific parent-child plan relationship defined in the QA_PC_PLAN_RELATIONSHIP table. The CHAR_ID associates the criterion with a particular quality characteristic (from QA_CHARS) that will be evaluated. While the provided metadata does not list all columns, typical implementation would also include columns for the operator (e.g., =, >, <) and the target value or range against which the characteristic's result is compared to determine if the child plan should be triggered.
Common Use Cases and Queries
The primary use case is the dynamic execution of quality plans. For instance, a receiving inspection plan (parent) may have a criterion stating that if the characteristic "Visual Defect" equals "Major," then a detailed failure analysis plan (child) is automatically initiated. Common queries involve auditing plan hierarchies and troubleshooting. A reporting query to list all criteria for a given plan relationship would resemble:
- SELECT qpc.criteria_id, qc.name char_name, qpc.operator, qpc.target_value
- FROM qa_pc_criteria qpc,
- qa_chars qc
- WHERE qpc.char_id = qc.char_id
- AND qpc.plan_relationship_id = :p_relationship_id;
Another critical use case is data validation, ensuring that characteristics referenced in criteria are valid and active for the associated collection plan.
Related Objects
QA_PC_CRITERIA is centrally connected to other key Quality schema objects. It has a mandatory foreign key relationship with QA_PC_PLAN_RELATIONSHIP, which defines the parent and child plans involved. It also has a foreign key to QA_CHARS, the master table for quality characteristics. The table is primarily accessed through the Quality Plans user interface and supporting APIs. While not listed in the provided metadata, it is typically referenced by seed data scripts and is integral to the backend logic of the QA_PC_PKG or similar packages that evaluate criteria and launch child plans during transaction processing.
-
Table: QA_PC_CRITERIA
12.1.1
owner:QA, object_type:TABLE, fnd_design_data:QA.QA_PC_CRITERIA, object_name:QA_PC_CRITERIA, status:VALID, product: QA - Quality , description: This table stores criteria for the child plans to be applicable , implementation_dba_data: QA.QA_PC_CRITERIA ,
-
Table: QA_PC_CRITERIA
12.2.2
owner:QA, object_type:TABLE, fnd_design_data:QA.QA_PC_CRITERIA, object_name:QA_PC_CRITERIA, status:VALID, product: QA - Quality , description: This table stores criteria for the child plans to be applicable , implementation_dba_data: QA.QA_PC_CRITERIA ,
-
APPS.QA_SS_PARENT_CHILD_PKG dependencies on QA_PC_CRITERIA
12.1.1
-
APPS.QA_PC_CRITERIA_PKG dependencies on QA_PC_CRITERIA
12.1.1
-
APPS.QLTTRAWB dependencies on QA_PC_CRITERIA
12.2.2
-
APPS.QA_PARENT_CHILD_COPY_PKG dependencies on QA_PC_CRITERIA
12.1.1
-
APPS.QA_PARENT_CHILD_COPY_PKG dependencies on QA_PC_CRITERIA
12.2.2
-
APPS.QA_PARENT_CHILD_PKG dependencies on QA_PC_CRITERIA
12.1.1
-
APPS.QA_PC_CRITERIA_PKG dependencies on QA_PC_CRITERIA
12.2.2
-
APPS.QA_SS_PARENT_CHILD_PKG dependencies on QA_PC_CRITERIA
12.2.2
-
APPS.QA_CHAR_UPDATE_PKG dependencies on QA_PC_CRITERIA
12.1.1
-
APPS.QA_CHAR_UPDATE_PKG dependencies on QA_PC_CRITERIA
12.2.2
-
APPS.QA_PARENT_CHILD_PKG dependencies on QA_PC_CRITERIA
12.2.2
-
VIEW: QA.QA_PC_CRITERIA#
12.2.2
owner:QA, object_type:VIEW, object_name:QA_PC_CRITERIA#, status:VALID,
-
APPS.QA_PC_CRITERIA_PKG SQL Statements
12.1.1
-
APPS.QA_PC_CRITERIA_PKG SQL Statements
12.2.2
-
SYNONYM: APPS.QA_PC_CRITERIA
12.1.1
owner:APPS, object_type:SYNONYM, object_name:QA_PC_CRITERIA, status:VALID,
-
VIEW: APPS.QA_PC_CRITERIA_COLUMNS_V
12.2.2
-
TRIGGER: APPS.QA_PC_CRITERIA+
12.2.2
-
VIEW: QA.QA_PC_CRITERIA#
12.2.2
-
TRIGGER: APPS.QA_PC_CRITERIA+
12.2.2
owner:APPS, object_type:TRIGGER, object_name:QA_PC_CRITERIA+, status:VALID,
-
SYNONYM: APPS.QA_PC_CRITERIA
12.2.2
owner:APPS, object_type:SYNONYM, object_name:QA_PC_CRITERIA, status:VALID,
-
VIEW: APPS.QA_PC_CRITERIA_COLUMNS_V
12.1.1
-
PACKAGE BODY: APPS.QA_PC_CRITERIA_PKG
12.1.1
-
APPS.QA_PARENT_CHILD_PKG dependencies on QA_CHARS
12.1.1
-
PACKAGE BODY: APPS.QA_PC_CRITERIA_PKG
12.2.2
-
FUNCTION: APPS.QA_PC_CRITERIA=
12.2.2
-
12.2.2 DBA Data
12.2.2
-
TABLE: QA.QA_PC_CRITERIA
12.2.2
owner:QA, object_type:TABLE, fnd_design_data:QA.QA_PC_CRITERIA, object_name:QA_PC_CRITERIA, status:VALID,
-
TABLE: QA.QA_PC_CRITERIA
12.1.1
owner:QA, object_type:TABLE, fnd_design_data:QA.QA_PC_CRITERIA, object_name:QA_PC_CRITERIA, status:VALID,
-
APPS.QA_PARENT_CHILD_PKG dependencies on QA_CHARS
12.2.2
-
APPS.QLTTRAWB dependencies on QA_PC_PLAN_RELATIONSHIP
12.2.2
-
APPS.QA_PC_CRITERIA_PKG dependencies on QA_PC_CRITERIA_S
12.2.2
-
FUNCTION: APPS.QA_PC_CRITERIA=
12.2.2
owner:APPS, object_type:FUNCTION, object_name:QA_PC_CRITERIA=, status:VALID,
-
12.2.2 DBA Data
12.2.2
-
APPS.QA_PC_CRITERIA_PKG dependencies on QA_PC_CRITERIA_S
12.1.1
-
APPS.QA_PC_CRITERIA_PKG dependencies on DUAL
12.2.2
-
APPS.QA_PC_CRITERIA_PKG dependencies on DUAL
12.1.1
-
APPS.QA_PARENT_CHILD_PKG dependencies on QLTCOMPB
12.2.2
-
APPS.QA_PARENT_CHILD_PKG dependencies on QLTCOMPB
12.1.1
-
APPS.QLTTRAWB dependencies on QA_PLAN_CHAR_ACTIONS
12.2.2
-
APPS.QA_SS_PARENT_CHILD_PKG dependencies on QA_PC_ELEMENT_RELATIONSHIP
12.2.2
-
Table: QA_PC_PLAN_RELATIONSHIP
12.1.1
owner:QA, object_type:TABLE, fnd_design_data:QA.QA_PC_PLAN_RELATIONSHIP, object_name:QA_PC_PLAN_RELATIONSHIP, status:VALID, product: QA - Quality , description: This table stores the parent plan id and the child plan id, along with the relation type and a flag to indicate if the child plan is mandatory , implementation_dba_data: QA.QA_PC_PLAN_RELATIONSHIP ,
-
APPS.QLTTRAWB dependencies on QA_PLAN_CHAR_ACTION_TRIGGERS
12.2.2
-
Table: QA_PC_PLAN_RELATIONSHIP
12.2.2
owner:QA, object_type:TABLE, fnd_design_data:QA.QA_PC_PLAN_RELATIONSHIP, object_name:QA_PC_PLAN_RELATIONSHIP, status:VALID, product: QA - Quality , description: This table stores the parent plan id and the child plan id, along with the relation type and a flag to indicate if the child plan is mandatory , implementation_dba_data: QA.QA_PC_PLAN_RELATIONSHIP ,
-
PACKAGE BODY: APPS.QA_PC_CRITERIA_PKG
12.2.2
owner:APPS, object_type:PACKAGE BODY, object_name:QA_PC_CRITERIA_PKG, status:VALID,
-
View: QA_PC_CRITERIA_COLUMNS_V
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:QA.QA_PC_CRITERIA_COLUMNS_V, object_name:QA_PC_CRITERIA_COLUMNS_V, status:VALID, product: QA - Quality , description: This view is for getting all elements that form the criteria elements of current plan. , implementation_dba_data: APPS.QA_PC_CRITERIA_COLUMNS_V ,
-
APPS.QA_SS_PARENT_CHILD_PKG dependencies on QA_PC_ELEMENT_RELATIONSHIP
12.1.1
-
12.1.1 FND Design Data
12.1.1
-
Table: QA_CHARS
12.2.2
owner:QA, object_type:TABLE, fnd_design_data:QA.QA_CHARS, object_name:QA_CHARS, status:VALID, product: QA - Quality , description: Collection elements definitions , implementation_dba_data: QA.QA_CHARS ,