Results for “qc_assy_val”

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

Overview

QC_ASSY_VAL is a configuration and validation table within the Oracle E-Business Suite GMD - Process Manufacturing Product Development module. As the name implies (Quality Control Assay Values), the table stores the set of valid assay values that quality control assays may be assigned. It acts as a controlled vocabulary or reference list against which individual assay measurements are validated, ensuring that process manufacturing quality results conform to predefined, acceptable value definitions.

In Oracle EBS 12.1.1 and 12.2.2, this object is delivered as part of the Process Manufacturing (OPM) Quality application stack. The documentation notes that it is not implemented in this database in the source environment, meaning it is a seed/definition table that is populated only in implementations actively using QC assay functionality.

Applying a heuristic Data Vault classification, the mined foreign-key structure suggests a link classification. The table primarily resolves relationships between two reference entities — QC_ASSY_TYP (assay type) and QC_TEXT_HDR (text/label header) — rather than functioning as a hub of unique business entities or a pure satellite of descriptive attributes.

Key Information Stored

The table's columns fall into surrogate, business-key, and descriptive roles. The most significant columns are:

• QCASSY_VAL_ID — The surrogate primary key (QC_ASSY_VAL_PK). Uniquely identifies each valid assay-value record.
• ORGN_CODE — Organization code. Part of the composite unique index QC_ASSY_VAL_U1, indicating assay values are organization-scoped.
• ASSAY_CODE — The assay identifier. Also part of the unique index U1, forming a business-key candidate alongside ORGN_CODE.
• ASSAY_VALUE — The stored valid assay value string/representation. Part of the U1 unique index.
• VALUE_NUM_MIN — A numeric minimum associated with the value, supporting range or tolerance validation.
• QCASSY_TYP_ID — Foreign key to QC_ASSY_TYP; classifies the assay value by its type.
• TEXT_CODE — Foreign key to QC_TEXT_HDR; links display text or label definitions to the value.

The unique index QC_ASSY_VAL_U1 (ORGN_CODE, ASSAY_CODE, ASSAY_VALUE) is the business-key candidate. The surrogate PK (QCASSY_VAL_ID) is referenced internally and should be treated as the stable join key. The combination of organization, assay, and value ensures no duplicate valid values exist per organization.

Common Use Cases and Queries

Typical scenarios include validating QC results against allowed values, reporting available assay values by organization, and joining to assay types for classification. Sample patterns:

• List valid assays for an organization:
  SELECT ASSAY_CODE, ASSAY_VALUE, VALUE_NUM_MIN FROM QC_ASSY_VAL WHERE ORGN_CODE = :org;
• Validate a submitted result: join QC_ASSY_VAL to confirm the entered value exists before commit.
• Classify values by type:
  SELECT v.ASSAY_CODE, v.ASSAY_VALUE, t.* FROM QC_ASSY_VAL v JOIN QC_ASSY_TYP t ON v.QCASSY_TYP_ID = t.QCASSY_TYP_ID;
• Retrieve display text: join to QC_TEXT_HDR on TEXT_CODE for labeled reporting.
• Set up concurrent/validation programs that load valid-value definitions from QC_ASSY_VAL during assay capture.

Because the table is not implemented in the reference database, reports and validation logic must gracefully handle empty or absent data.

Related Objects

• QC_ASSY_TYP — joined via QC_ASSY_VAL.QCASSY_TYP_ID = QC_ASSY_TYP.QCASSY_TYP_ID; defines assay value type.
• QC_TEXT_HDR — joined via QC_ASSY_VAL.TEXT_CODE = QC_TEXT_HDR.TEXT_CODE; supplies text/label header definitions.
• QC_ASSY_VAL_PK — the primary key constraint on QCASSY_VAL_ID.
• QC_ASSY_VAL_U1 — the unique business-key index on ORGN_CODE, ASSAY_CODE, ASSAY_VALUE.
• Related QC/OPM assay and specification tables that consume these valid values during results entry and quality data collection.