Search Results qa_pc_value_lookups_pk

Overview

QA_PLAN_CHAR_VALUE_LOOKUPS is an Oracle Quality (QA) module table in the EBS 12.1.1 and 12.2.2 schemas. It stores the set of permissible values ("lookups") available for a given collection element (characteristic) within a specific collection plan. In effect, it defines the allowed pick-list of valid entries that an operator may select when recording a result for a mandatory- or list-constrained collection element. This makes the table central to enforcing data-entry validation in the shop-floor and inspection workflows governed by Oracle Quality.

From a Data Vault modeling perspective, the metadata heuristic classifies this object as a link table. It resolves the many-to-many relationship between a collection plan (QA_PLANS) and its collection elements (QA_CHARS), with the permissible value acting as a descriptive attribute on that association. It is not a hub nor a satellite in the strict sense; rather, it is an associative structure whose business key is composed of the participating references plus the short code.

Key Information Stored

Of the 27 documented columns, the following are the most operationally significant:

• PLAN_ID — Foreign key to QA_PLANS; identifies the collection plan under which the permissible values are defined.
• CHAR_ID — Foreign key to QA_CHARS; identifies the specific collection element (characteristic) that the value set constrains.
• SHORT_CODE — The permissible value itself; the entry an operator may choose during collection.
• DESCRIPTION — Human-readable meaning or label for the permissible value.
• SHORT_CODE_ID — Identifier linking the entry to its short-code definition.
• ZD_EDITION_NAME — Editioning column supporting Oracle EBS 12.2.2 online patching (AD/TXK editions).
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — The standard Oracle EBS descriptive flexfield column set, allowing customers to extend the value-lookup record with site-specific data.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard "WHO" audit columns tracking creation and modification.

The primary key is the constraint QA_PC_VALUE_LOOKUPS_PK, defined over (PLAN_ID, CHAR_ID, SHORT_CODE). A separate unique index, QA_PLAN_CHAR_VALUES_LOOKUPS_U1, is defined over (PLAN_ID, CHAR_ID, SHORT_CODE, ZD_EDITION_NAME), reflecting the edition-aware uniqueness required in 12.2.2. Notably, the table has no separate surrogate system-generated key; the business key itself serves as the primary key.

Common Use Cases and Queries

Typical uses include validating that an operator's entered result belongs to the approved value set, populating selection lists in Quality data collection forms, and reporting on allowed values per plan and element.

• List permissible values for a plan and characteristic:

  SELECT short_code, description
  FROM   qa.qa_plan_char_value_lookups
  WHERE  plan_id = :plan_id
  AND    char_id = :char_id;

• Locate the plan/chars that use a particular short code:

  SELECT plan_id, char_id, short_code
  FROM   qa.qa_plan_char_value_lookups
  WHERE  short_code = :short_code;

• Reporting on configured value sets by plan, joined to QA_PLANS for the plan name and QA_CHARS for the element name.
• Data validation queries used during migration or integration to confirm that incoming results match an allowed lookup.

Related Objects

• QA_PLANS — Parent plan definition; join on QA_PLAN_CHAR_VALUE_LOOKUPS.PLAN_ID = QA_PLANS.PLAN_ID.
• QA_CHARS — Collection element definition; join on QA_PLAN_CHAR_VALUE_LOOKUPS.CHAR_ID = QA_CHARS.CHAR_ID.
• QA_PLAN_CHARS — Associates plans and characteristics; complements the value lookups in defining collection behavior.
• QA_RESULTS — Stores collected results; permissible values here constrain the allowed SHORT_CODE entries recorded there.
• QA_CHAR_VALUES / QA_CHAR_VALUE_LOOKUPS — Related characteristic value definitions referenced by the QA validation engine.
• QA_SPECS / QA_PLAN_SPECS — Specifications linked to plans that consume these value sets.

These relationships are enforced via the foreign keys to QA_PLANS and QA_CHARS, making the table a dependent link in the Oracle Quality data model.