Results for “assay_type”

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

Overview

PMIBV_QC_ASSAYS_V is a seeded Oracle E-Business Suite database view owned by the APPS schema and shipped with the Process Manufacturing Intelligence (PMI) product family. It is exposed as a base business view in the ETRM (E-Business Suite Technical Reference Manual) and carries a VALID status in the documented releases 12.1.1 and 12.2.2. The object presents quality control assay definitions in a denormalized, reporting-ready format, joining assay master data, permissible assay values, and global lookup translations into a single queryable structure.

The view serves the classical EBS reporting and integration role: it shields downstream consumers — BI Publisher reports, Discoverer workbooks, OBIEE repositories, and custom PL/SQL interfaces — from the normalization and multilingual complexity of the underlying quality tables. Rather than querying QC_ASSY_TYP and QC_ASSY_VAL directly and manually resolving the organization code and global lookup meaning, report authors reference PMIBV_QC_ASSAYS_V and receive pre-resolved, business-friendly column aliases.

Underlying Base Objects

The documented base objects referenced by this view are:

• QC_ASSY_TYP (SYNONYM) — aliased as QA in the view text; the primary source of assay header attributes such as assay code, description, type, valid range, and unit of measure.
• QC_ASSY_VAL (SYNONYM) — aliased as VA; supplies permissible assay result values and is joined with an outer-join (+) on both ASSAY_CODE and QCASSY_TYP_ID.
• FND_LOOKUPS (VIEW) — aliased as LKUP; filtered to LOOKUP_TYPE = 'PMI_GLOBAL' and LOOKUP_CODE = 'GLOBAL' to resolve a global organization-level code where the QC assay record has no ORGN_CODE.
• FND_GLOBAL (PACKAGE) — referenced for session-level context (typically organization and user identity) used implicitly by the join and NVL translation logic.

Because QC_ASSY_VAL is outer-joined, an assay definition without associated permissible values still appears in the result set, with the VALUE column returned as NULL.

Key Columns

• ORGANIZATION_CODE — NVL(QA.ORGN_CODE, LKUP.MEANING); resolves the plant/organization identifier, falling back to the global lookup meaning when no organization is set.
• ASSAY_CODE — the unique assay identifier used as the join key across quality data.
• ASSAY_DESCRIPTION — the descriptive name of the assay.
• ASSAY_TYPE — classifies the assay (for example numeric versus discrete value sets).
• MIN_VALUE / MAX_VALUE — the valid numeric boundaries for result entry.
• QUALITY_CONTROL_UNIT_CODE — exposes QA.QCUNIT_CODE; the unit of measure applied to assay results. This is the column most directly associated with the search term quality_control_unit_code.
• VALUE — the permissible value description from QC_ASSY_VAL.
• DELETE_MARK, CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY — standard EBS audit and soft-delete columns; active records typically require DELETE_MARK = 0.

Common Use Cases and Queries

Typical scenarios include QC specification listings by organization, feed for LIMS or lab-equipment integrations, and unit-of-measure validation in assay result entry. A representative query follows.

SELECT organization_code, assay_code, assay_description, assay_type, min_value, max_value, quality_control_unit_code, value FROM apps.pmibv_qc_assays_v WHERE delete_mark = 0 ORDER BY organization_code, assay_code;

For unit-specific reporting:

SELECT assay_code, quality_control_unit_code FROM apps.pmibv_qc_assays_v WHERE delete_mark = 0 AND quality_control_unit_code = :p_unit;

As with all APPS-owned views, grants or synonyms are required for non-APPS access, and the FND_LOOKUPS join assumes a valid PMI_GLOBAL lookup configuration in the target instance.