Search Results max_value

Overview

PMIFV_QC_ASSAYS_V is a public Oracle E-Business Suite view owned by the APPS schema and defined in the Process Manufacturing Intelligence (PMI) product family. It carries a VALID status and is titled "QC Assays Full View," a naming convention that indicates it consolidates assay definition and assay value data into a single denormalized result set. The view is a reporting and integration artifact rather than a transactional object; it presents Quality Control assay master data joined to their permitted values, together with a translated organization label. In Oracle EBS 12.1.1 and 12.2.2 the view remains a read-only reporting surface, allowing process manufacturing quality analysts, custom concurrent programs, and downstream integration extracts to query assay tolerances and value lists without navigating the underlying normalized tables.

Underlying Base Objects

The documented base objects for this view are FND_GLOBAL (package), FND_LOOKUPS (view), QC_ASSY_TYP (synonym), and QC_ASSY_VAL (synonym). The view text joins QC_ASSY_TYP (aliased QA), the assay type definition table, to QC_ASSY_VAL (aliased VA), which stores the discrete permitted assay values, on both ASSAY_CODE and QCASSY_TYP_ID. The join to QC_ASSY_VAL is an outer join, so an assay with no enumerated values is still returned. A cross-reference to FND_LOOKUPS supplies a global organization label where the assay is not tied to a specific organization, and the PMI_SECURITY_PKG.SHOW_RECORD function (invoked through the FND_GLOBAL package infrastructure) enforces organization-level record security. The view is registered as APPS.PMIFV_QC_ASSAYS_V and is therefore queryable only by users granted access to the APPS schema objects, typically through a synonym or a custom responsibility.

Key Columns

The view exposes thirteen columns. ORGANIZATION_CODE returns NVL(QA.ORGN_CODE, LKUP.MEANING), substituting the global lookup meaning when no organization is assigned. ASSAY_CODE identifies the assay, while ASSAY_DESCRIPTION and ASSAY_TYPE describe it and classify it by assay type. MIN_VALUE and MAX_VALUE map to QA.MIN_VALID and QA.MAX_VALID, the numeric tolerance boundaries against which QC results are validated. QUALITY_CONTROL_UNIT_CODE carries the unit of measure. VALUE, drawn from QC_ASSY_VAL.VALUE_DESC, holds the discrete permitted values where the assay is value-based rather than range-based. The standard audit columns DELETE_MARK, CREATION_DATE, CREATED_BY, LAST_UPDATED_DATE, and LAST_UPDATED_BY support change tracking and soft-delete filtering. Users searching on "min_value" will find that the underlying physical column is MIN_VALID, aliased to MIN_VALUE in the view projection.

Common Use Cases and Queries

Typical uses include exposing assay specifications to LIMS interfaces, building quality specification reports, and validating QC results in custom extensions. Because the view is security-filtered, a query automatically returns only records whose organization the session user may see. A representative query listing active assays with their tolerances is:

• SELECT assay_code, assay_description, min_value, max_value, quality_control_unit_code FROM apps.pmifv_qc_assays_v WHERE delete_mark = 0 AND min_value IS NOT NULL;
• SELECT assay_code, value FROM apps.pmifv_qc_assays_v WHERE value IS NOT NULL ORDER BY assay_code;
• SELECT organization_code, assay_code, min_value, max_value FROM apps.pmifv_qc_assays_v WHERE assay_type = :p_assay_type;

Filtering on DELETE_MARK = 0 is recommended for all production queries, since the view does not exclude soft-deleted rows. For high-volume extracts, joining the view to order or batch quality data should be driven from the transactional side to avoid repeated evaluation of the security function.