Search Results test_provider_code




Overview
Explore in AI Chat

Overview

PMIFV_QC_RESULTS_V is an APPS-owned database view in the Oracle EBS Process Manufacturing Intelligence (PMI) product family. It is designated as the "QC Results Full View," and its purpose is to present a denormalized, reporting-friendly projection of quality control results captured in Process Manufacturing. The view joins result-level data from QC_RSLT_MST to the specifications, samples, lots, batches, formulas, routings, operations, items, customers, and vendors that give those results business meaning.

In the context of ETRM 12.2.2 the object is owned by APPS and is reported as VALID. It functions primarily as a read-only reporting and integration surface: rather than requiring report authors or interface developers to reconstruct the underlying multi-table joins, the view exposes a single flat structure with resolved foreign keys presented as human-readable identifiers such as item numbers, lot numbers, batch numbers, and party names. The user search term test_provider_code maps directly to the TEST_PROVIDER_CODE column selected from QC_RSLT_MST, which records the provider responsible for a given quality result.

Underlying Base Objects

The view is defined over a set of APPS synonyms and, per the documented metadata, references FND_GLOBAL as a package and FND_LOOKUPS as a view. The qualifying synonyms are FM_FORM_MST, FM_OPRN_MST, FM_ROUT_HDR, GME_BATCH_HEADER, HZ_CUST_ACCOUNTS_ALL, HZ_PARTIES, IC_ITEM_MST, IC_LOTS_MST, PO_VEND_MST, QC_ASSY_TYP, QC_RSLT_MST, QC_SMPL_MST, and QC_SPEC_MST.

The driving table is QC_RSLT_MST (aliased QR), which supplies the actual result values, result date, test provider code, location, and routing step number. Specification context comes from QC_SPEC_MST (QS), joined on the QC specification identifier. Sample context comes from QC_SMPL_MST (SAM), which is itself joined outward to formulas (FM_FORM_MST), routings (FM_ROUT_HDR), customers (HZ_CUST_ACCOUNTS_ALL and HZ_PARTIES), and items (IC_ITEM_MST). Batch context is joined through GME_BATCH_HEADER, lot context through IC_LOTS_MST, and vendor context through PO_VEND_MST. Lookup meanings for the ACCEPT_ANYWAY and FINAL_MARK flags are resolved from FND_LOOKUPS. Most of these joins are outer joins, signaled by the (+) notation, which means results are retained even where optional related data such as batch, routing, or customer is absent.

Key Columns

Common Use Cases and Queries

Typical uses include quality result trending by item or lot, supplier quality analysis keyed on test provider, batch release reporting, and extraction to a data warehouse. Because the view resolves so many relationships, it is well suited to ad hoc querying and to integration feeds where a flat QC results record is required.

To isolate results attributable to a specific test provider, filter on TEST_PROVIDER_CODE:

  • SELECT item_number, lot_number, batch_number, test_provider_code, num_result, text_result, result_date FROM apps.pmifv_qc_results_v WHERE test_provider_code = :p_provider_code AND delete_mark = 0 ORDER BY result_date DESC;
  • SELECT organization_code, item_number, num_result, min_spec, max_spec, result_date FROM apps.pmifv_qc_results_v WHERE num_result > max_spec AND delete_mark = 0;
  • SELECT customer_name, vendor_name, test_provider_code, COUNT(*) FROM apps.pmifv_qc_results_v WHERE delete_mark = 0 GROUP BY customer_name, vendor_name, test_provider_code;

Because the view depends on synonyms rather than exposing raw table access, query it through the APPS schema or a suitable synonym, and always include DELETE_MARK = 0 to restrict output to active rows.