Search Results routing_step_number




Overview
Explore in AI Chat

Overview

PMIFV_QC_SAMPLE_V is an APPS-owned database view in Oracle E-Business Suite that presents a denormalized, reporting-ready representation of quality control sampling data. The object belongs to the Process Manufacturing Intelligence (PMI) product family, which Oracle classifies as obsolete in release 12.1.1 and 12.2.2. Despite that classification, the view remains marked VALID in the data dictionary and continues to be referenced by legacy Process Manufacturing (OPM/GME) reporting, extract, and integration routines that predate the modern OPM Quality module.

The view is described as the "QC Samples Full View" because it resolves the primary sampling master record into a single wide row that carries organization, item, formula, routing, batch, lot, customer, vendor, and user context. Rather than requiring the caller to join QC_SMPL_MST to a dozen surrounding master tables, PMIFV_QC_SAMPLE_V performs those outer joins internally, so a single SELECT yields a human-readable quality sample record suitable for operational reporting, warehouse sampling audits, and downstream interfaces to laboratory or quality systems.

For users searching on the term "routing_step_number," this view is the relevant access point: it exposes the routing step associated with a sample through the ROUTING_STEP_NUMBER column, which is sourced from FM_ROUT_DTL.ROUTINGSTEP_NO. This allows a sample to be traced to the specific step of a manufacturing routing at which it was taken.

Underlying Base Objects

The view is defined over twelve base objects, all accessed through APPS synonyms: QC_SMPL_MST (the driving sampling master table), FM_FORM_MST (formula master), FM_OPRN_MST (operation master), FM_ROUT_HDR (routing header), FM_ROUT_DTL (routing detail, the source of routing step data), GME_BATCH_HEADER (batch header), IC_ITEM_MST (item master), IC_LOTS_MST (lot master), FND_USER (application user), HZ_CUST_ACCOUNTS_ALL and HZ_PARTIES (customer account and party), and PO_VEND_MST (vendor master).

QC_SMPL_MST is the anchor: its columns supply sample number, description, organization, warehouse, location, sample date, quantity, unit of measure, delete mark, and external identifier. Every other table is joined to it with an outer join, meaning the view returns a sample row even when the related formula, routing, batch, lot, customer, or vendor reference is null. This defensive join strategy is important in process manufacturing, where samples are frequently taken outside the context of a specific batch or routing.

Row-level security is embedded in the view definition through a predicate that invokes PMI_SECURITY_PKG.SHOW_RECORD against the organization code. Access is therefore filtered by the responsibility's organization security profile rather than by a grant on the table alone.

Key Columns

Common Use Cases and Queries

Typical uses include quality sample registers by organization or date range, traceability reports that link a sample to its batch, lot, and routing step, and extracts feeding laboratory information management systems. The routing step element supports investigations such as identifying all samples taken at a particular step of a routing to evaluate in-process quality.

All samples with routing step information for an organization:

  • SELECT sample_no, item_number, formula_number, routing_number, routing_step_number, operation_number, batch_number, sample_date FROM pmifv_qc_sample_v WHERE organization_code = :org AND routing_step_number IS NOT NULL ORDER BY sample_date DESC;

Samples tied to a specific batch and lot for traceability:

  • SELECT sample_no, sample_description, item_number, lot_number, sub_lot_number, batch_number, sampled_by, sample_qty, sample_uom FROM pmifv_qc_sample_v WHERE batch_number = :batch AND lot_number = :lot;

Daily sample activity by warehouse:

  • SELECT warehouse_code, COUNT(*) sample_count FROM pmifv_qc_sample_v WHERE sample_date BETWEEN :start_date AND :end_date GROUP BY warehouse_code ORDER BY warehouse_code;

Because organization security is enforced inside the view via PMI_SECURITY_PKG.SHOW_RECORD, no additional organization predicate is strictly required, though supplying one improves performance. Given the obsolete PMI status, new development should consider current OPM Quality alternatives, but PMIFV_QC_SAMPLE_V remains a practical read-only reporting interface for legacy process manufacturing data in both 12.1.1 and 12.2.2.