Search Results pmi_global




Overview
Explore in AI Chat

Overview

APPS.PMIFV_QC_ASSAYS_V is a reporting view in Oracle EBS Process Manufacturing (OPM) Quality Management. It presents assay (quality test) definitions together with their valid-value specifications and descriptive value text. The view consolidates data from the assay type and assay value tables, and resolves the organization code through a lookup on the PMI_GLOBAL lookup type. Its role is to provide a denormalized, read-only projection suitable for reporting, custom concurrent programs, and integration extracts that need a single row per assay value combination. The object resides in the APPS schema and is documented in ETRM 12.2.2, with the same definition applicable to 12.1.1.

Underlying Base Objects

The view is defined over the following documented objects:

  • QC_ASSY_TYP (synonym) — the assay type master, aliased QA. Supplies assay code, description, type, valid minimum and maximum, quality-control unit, and audit columns.
  • QC_ASSY_VAL (synonym) — the assay value detail, aliased VA. Supplies the descriptive value (VALUE_DESC), joined to the assay type on both ASSAY_CODE and QCASSY_TYP_ID as an outer join (the (+) operator).
  • FND_LOOKUPS (view) — aliased LKUP. Restricted to LOOKUP_TYPE = 'PMI_GLOBAL' and LOOKUP_CODE = 'GLOBAL', providing the default organization code via MEANING.
  • FND_GLOBAL (package) — referenced by the metadata as a base object, used to resolve session context such as the current organization.

The outer join from QC_ASSY_TYP to QC_ASSY_VAL means assay types with no defined values still appear, with VALUE returned as NULL. The NVL(QA.ORGN_CODE, LKUP.MEANING) expression substitutes the global lookup meaning when the assay type carries no explicit organization code.

Key Columns

Common Use Cases and Queries

The view is typically queried to list active assays and their specifications, to drive quality-data validation, or to feed downstream reporting. Because DELETE_MARK is exposed but not filtered in the view definition, callers must exclude deleted rows explicitly.

List active assays for an organization:

  • SELECT assay_code, assay_description, assay_type, min_value, max_value FROM apps.pmifv_qc_assays_v WHERE organization_code = :org AND nvl(delete_mark,0) = 0;

Retrieve allowed values for a specific assay:

  • SELECT assay_code, value FROM apps.pmifv_qc_assays_v WHERE assay_code = :assay AND value IS NOT NULL;

Extract full assay specifications for integration:

  • SELECT organization_code, assay_code, assay_description, assay_type, quality_control_unit_code, min_value, max_value FROM apps.pmifv_qc_assays_v WHERE nvl(delete_mark,0) = 0 ORDER BY organization_code, assay_code;

All queries should reference the view through the APPS schema with the standard EBS responsibility and MO/OPM operating unit context established so that the underlying FND_GLOBAL session values resolve correctly.