Results for “decimal_precision”

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

Overview

QA_PLAN_CHARS is a core Quality (QA) module table in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the association between collection plans and their assigned collection elements (characteristics), functioning as the bridge that defines which quality characteristics belong to a given collection plan. The table resides in the QA schema and is documented as VALID in the ETRM repository.

From a Data Vault modeling perspective, the metadata heuristically classifies QA_PLAN_CHARS as a link table. This is a modeling suggestion: the table resolves a many-to-many relationship between plans and characteristics and carries descriptive attributes (satellite-style) rather than serving as a standalone hub. Its primary key, QA_PLAN_CHARS_PK, is composed of PLAN_ID and CHAR_ID, which is characteristic of a link structure.

Key Information Stored

The table's identity and business keys are defined by plan and characteristic references:

• PLAN_ID — Foreign key to QA_PLANS; identifies the parent collection plan.
• CHAR_ID — Foreign key to QA_CHARS; identifies the collection element or characteristic assigned to the plan.
• PROMPT_SEQUENCE and PROMPT — Control the display order and label of the characteristic when presented to the operator.
• ENABLED_FLAG, MANDATORY_FLAG, DISPLAYED_FLAG, READ_ONLY_FLAG, INFORMATION_FLAG, OVERRIDE_FLAG — Behavioral flags governing whether the element is active, required, visible, editable, informational-only, or overridable.
• DEFAULT_VALUE and DEFAULT_VALUE_ID — Default value and its reference identifier applied to the element.
• RESULT_COLUMN_NAME — Maps the characteristic to a result storage column.
• DECIMAL_PRECISION and UOM_CODE — Numeric precision and unit of measure for quantitative characteristics.
• SS_POPLIST_FLAG and VALUES_EXIST_FLAG — Indicate valid-values-list behavior and whether value sets exist.
• DEVICE_FLAG and DEVICE_ID — Identify instrument or device association for automated collection.
• ZD_EDITION_NAME — Editioning column introduced in 12.2, supporting online patching and edition-based redefinition.

The unique index QA_PLAN_CHARS_U1 (PLAN_ID, CHAR_ID, ZD_EDITION_NAME) represents the business-key candidate in the 12.2.2 editioned schema, while QA_PLAN_CHARS_PK remains the primary key on PLAN_ID and CHAR_ID. Standard audit columns (LAST_UPDATE_DATE, CREATED_BY, and the fifteen ATTRIBUTEn flex columns) are also present.

Common Use Cases and Queries

Typical usage includes reporting which characteristics are attached to a collection plan and their display configuration, validating enabled or mandatory elements, and diagnosing data collection behavior.

• List characteristics for a plan: SELECT CHAR_ID, PROMPT, PROMPT_SEQUENCE, ENABLED_FLAG, MANDATORY_FLAG FROM QA.QA_PLAN_CHARS WHERE PLAN_ID = :plan_id ORDER BY PROMPT_SEQUENCE;
• Find required elements: SELECT PLAN_ID, CHAR_ID FROM QA.QA_PLAN_CHARS WHERE MANDATORY_FLAG = 'Y' AND ENABLED_FLAG = 'Y';
• Join to resolve names: SELECT p.PLAN_NAME, c.CHAR_NAME FROM QA.QA_PLAN_CHARS pc JOIN QA.QA_PLANS p ON pc.PLAN_ID = p.PLAN_ID JOIN QA.QA_CHARS c ON pc.CHAR_ID = c.CHAR_ID;

These patterns support collection plan setup, quality reporting, and troubleshooting of data entry screens.

Related Objects

• QA_PLANS — Parent collection plan; join on QA_PLAN_CHARS.PLAN_ID = QA_PLANS.PLAN_ID.
• QA_CHARS — Collection element definition; join on QA_PLAN_CHARS.CHAR_ID = QA_CHARS.CHAR_ID.
• QA_RESULTS — Stores collected values; related through plan/characteristic combinations.
• QA_SPEC_CHARS / specification tables — Constrain expected values for characteristics.
• QA_PLAN_API — Public API for creating and maintaining collection plan assignments.

These relationships make QA_PLAN_CHARS the central configuration link between plan setup and characteristic definition in Oracle Quality.