Results for “qa_pc_criteria”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

QA_PC_CRITERIA is a Quality (QA) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the criteria governing when a child quality plan becomes applicable within a parent/child plan hierarchy. In EBS plan-to-plan relationships, a parent plan can spawn one or more child plans; QA_PC_CRITERIA defines the conditional logic—expressed as a characteristic, an operator, and low/high values—that determines whether a given child plan relationship should be triggered. The table therefore acts as the rule repository behind conditional plan generation and plan applicability.

From a heuristic Data Vault classification mined from the foreign key structure, QA_PC_CRITERIA is best modeled as a link. It carries a surrogate primary key, CRITERIA_ID (index QA_PC_CRITERIA_PK1), and connects two business entities through foreign keys: the plan relationship and the quality characteristic. This link-centric classification is a modeling suggestion only; the physical implementation remains a standard Oracle EBS transactional table with audit columns.

Key Information Stored

The table documents 14 physical columns in the 12.2.2 schema. The most significant are:

• CRITERIA_ID — surrogate primary key (QA_PC_CRITERIA_PK1) uniquely identifying each criterion row.
• PLAN_RELATIONSHIP_ID — foreign key to QA_PC_PLAN_RELATIONSHIP; identifies the parent/child plan relationship to which the criterion applies.
• CHAR_ID — foreign key to QA_CHARS; identifies the quality characteristic evaluated by the criterion.
• OPERATOR — the comparison operator used to evaluate the characteristic value.
• LOW_VALUE / LOW_VALUE_ID — lower bound of the acceptance range, stored as a display value and as a referenced value ID.
• HIGH_VALUE / HIGH_VALUE_ID — upper bound of the acceptance range, likewise paired as display value and ID.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard EBS audit columns recording who created and last modified the row and when.
• ZD_EDITION_NAME — editioning/archive column supporting the multi-edition data model.

The unique index QA_PC_CRITERIA_U1 (CRITERIA_ID, ZD_EDITION_NAME) confirms CRITERIA_ID as the business-key candidate once combined with the edition discriminator. Note that OPERATOR, LOW_VALUE, and HIGH_VALUE are the working condition values, while the *_ID columns reference the underlying specification values.

Common Use Cases and Queries

Typical uses include retrieving all criteria for a plan relationship to explain why a child plan fires, and joining criteria to characteristics for readable reporting.

• List criteria for a plan relationship: SELECT c.*, ch.char_name FROM qa_pc_criteria c, qa_chars ch WHERE c.char_id = ch.char_id AND c.plan_relationship_id = :rel_id;
• Trace applicability rules back to the plan hierarchy via QA_PC_PLAN_RELATIONSHIP.
• Audit reporting on who last changed criterion definitions using LAST_UPDATED_BY and LAST_UPDATE_DATE.
• Validate that each criterion's characteristic exists in QA_CHARS and is enabled.

Related Objects

• QA_PC_PLAN_RELATIONSHIP — referenced via QA_PC_CRITERIA.PLAN_RELATIONSHIP_ID; defines the parent/child plan linkage.
• QA_CHARS — referenced via QA_PC_CRITERIA.CHAR_ID; source of the evaluated characteristic.
• QA_PC_CRITERIA_PK1 — the primary key constraint on CRITERIA_ID.
• QA_PC_CRITERIA_U1 — unique index on CRITERIA_ID and ZD_EDITION_NAME.
• Adjacent Quality plan configuration tables that consume these criteria during child plan generation.

Together these objects let the QA module resolve, at runtime, which child plans apply based on measured characteristic values.