Results for “pmi_yes_no”

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

Overview

APPS.PMIBV_QC_RESULTS_V is a reporting view in Oracle EBS Process Manufacturing (formerly OPM) that consolidates quality control (QC) result data with specification, sampling, batch, lot, formula, routing, customer, and vendor context. It belongs to the PMI (Process Manufacturing Intelligence) family of views, which are designed to flatten normalized OPM base tables into denormalized, business-friendly result sets suitable for operational reporting, ad-hoc inquiry, and integration extraction. In Oracle EBS 12.1.1 and 12.2.2 the view ships under the APPS schema and is defined with an outer-join pattern (notably the (+) syntax), allowing QC results to be retrieved even when related sampling, batch, formula, routing, vendor, or customer records are absent.

The view is discoverable in ETRM under the title "VIEW: APPS.PMIBV_QC_RESULTS_V". Its presence in the Process Manufacturing Intelligence library means it is commonly accessed by quality analysts, lab personnel, and reporting developers building QC dashboards or extracting results to external systems.

Underlying Base Objects

The view is defined over the following documented base objects: QC_SPEC_MST, QC_RSLT_MST, QC_SMPL_MST, QC_ASSY_TYP, IC_ITEM_MST, IC_LOTS_MST, GME_BATCH_HEADER, FM_FORM_MST, FM_ROUT_HDR, FM_OPRN_MST, PO_VEND_MST, HZ_CUST_ACCOUNTS_ALL, HZ_PARTIES, and FND_LOOKUPS (with FND_GLOBAL referenced as a package). In OPM these are commonly exposed as synonyms within the APPS schema.

The driving table is QC_RSLT_MST (alias qr), which holds individual QC result rows. It joins to QC_SPEC_MST (qs) for specification limits and assay information, QC_SMPL_MST (sam) for sample-level context, and QC_ASSY_TYP (assy) for assembly type. Item details come from IC_ITEM_MST and lot details from IC_LOTS_MST. Manufacturing context is supplied by GME_BATCH_HEADER (batches), FM_FORM_MST (formulas), FM_ROUT_HDR (routings), and FM_OPRN_MST (operations). Vendor information is provided by PO_VEND_MST, while customer context is resolved through HZ_CUST_ACCOUNTS_ALL and HZ_PARTIES. Finally, FND_LOOKUPS is joined twice (aliases alkup and flkup) to translate coded values for accept-anyway and final-mark flags into their display meanings.

Key Columns

• organization_code / warehouse_code — Identifying context of the QC result's organization and warehouse.
• result_date, text_result, num_result — The QC outcome, both textual and numeric.
• accept_anyway, final_mark — Lookup meanings decoded from FND_LOOKUPS, indicating disposition and final result marking.
• text_spec, min_spec, max_spec, target_spec — Specification boundaries against which the result is evaluated.
• assay_code, Quality_Control_Unit_Code, vendor_specification, customer_specification — Specification classification and unit context.
• item_number, item_description, lot_number, sub_lot_number, sample_number — Material identification.
• batch_number, formula_number, formula_version, routing_number, routing_version, operation_number, operation_version, routing_step_number — Manufacturing and routing context.
• customer_number, customer_name, vendor_no, vendor_name — External party context.
• delete_mark, last_update_date — Record status and audit information.

Common Use Cases and Queries

Typical usage includes QC result inquiry by batch or lot, specification conformance reporting, and extraction of results for external LIMS or analytics platforms. The user's search term "pmi_yes_no" suggests interest in the lookup-backed flag columns, particularly accept_anyway and final_mark, which are resolved via FND_LOOKUPS.

SELECT batch_number,
       item_number,
       sample_number,
       num_result,
       text_result,
       min_spec,
       max_spec,
       final_mark
FROM   apps.pmibv_qc_results_v
WHERE  batch_number = :batch
AND    NVL(delete_mark, 0) = 0;

To inspect results flagged for acceptance despite being out of specification:

SELECT lot_number,
       item_number,
       num_result,
       accept_anyway
FROM   apps.pmibv_qc_results_v
WHERE  accept_anyway IS NOT NULL
AND    result_date >= :from_date;

Because the view relies on outer joins, results without an associated batch, formula, or vendor are still returned, which is important when reporting on samples taken outside a production context.