Search Results no_of_samples_complet

Overview

The view APPS.PMIFV_BATCH_QC_V (Batch QC Details Consolidated) is a reporting and integration object delivered within the Process Manufacturing Intelligence (PMI) module of Oracle E-Business Suite, applicable to releases 12.1.1 and 12.2.2. Its purpose is to consolidate batch production records with their associated quality control metrics and the fiscal calendar context in which those batches were completed. Rather than requiring report authors to join batch headers, material details, item master records, organization master records, and a GL calendar view, the view presents a single denormalized row set that can be consumed directly by OBIEE dashboards, custom concurrent programs, or ad hoc SQL.

The view is read-only (defined WITH READ ONLY) and is therefore intended strictly for query and reporting access, not for DML. A defining characteristic is that it enforces organization-level security through the PMI_SECURITY_PKG.SHOW_RECORD call embedded in its WHERE clause, meaning operators see only the plants to which their responsibility grants access.

Underlying Base Objects

PMIFV_BATCH_QC_V is constructed from several joined sources. The primary driver is GME_BATCH_HEADER, restricted to batches with BATCH_STATUS > 2 (i.e., released or completed batches rather than pending ones). It joins to GME_MATERIAL_DETAILS on BATCH_ID, filtered to LINE_TYPE = 1 so that only the product line — not ingredient or by-product lines — is returned. The item master IC_ITEM_MST supplies item number, description, and planning class. Organization data flows from SY_ORGN_MST, and the fiscal mapping is resolved through PMI_GL_CALENDAR_V, which provides period year, period number, and period name by comparing the batch completion date against calendar start and end dates via the company code. The formula master FM_FORM_MST_B is included solely to validate the batch's formula identifier. Finally, the package PMI_PRODUCTION_SUM is invoked repeatedly as an inline function call to compute the quality control aggregates.

Key Columns

The view exposes the following principal columns:

• PLANT_CODE / COMPANY_CODE / WHSE_CODE — Organizational context: manufacturing plant, legal company entity, and warehouse.
• BATCH_ID / BATCH_NO — Internal and user-facing batch identifiers.
• ACTUAL_CMPLT_DATE — The actual completion date of the batch, which drives both the calendar lookup and the security filter.
• ITEM_ID / ITEM_NO / ITEM_DESC / PLANNING_CLASS — Product identification and its planning classification.
• NO_OF_SAMPLES_TAKEN — Count of quality samples drawn for the batch.
• NO_OF_SAMPLES_COMPLET — Count of samples for which QC testing was completed.
• NO_OF_SAMPLES_PASSED — Count of samples that met specification.
• NO_OF_TIMES_ADJUSTED — The number of occasions on which the batch required adjustment (e.g., rework or specification correction). This is the column referenced by the search term no_of_times_adjusted and is a key indicator of process variability and first-pass quality.
• FISCAL_YEAR / PERIOD_CODE / PERIOD_NAME — Fiscal period attribution derived from PMI_GL_CALENDAR_V.

Common Use Cases and Queries

Typical usage centres on batch quality trending, plant yield and first-pass analysis, and QC exception reporting. A representative query illustrates the core benefit — retrieving adjusted batches with the QC context already assembled:

SELECT plant_code,
       batch_no,
       item_no,
       actual_cmplt_date,
       no_of_samples_taken,
       no_of_samples_complet,
       no_of_samples_passed,
       no_of_times_adjusted,
       period_name
  FROM apps.pmifv_batch_qc_v
 WHERE no_of_times_adjusted > 0
   AND period_name = :p_period
 ORDER BY no_of_times_adjusted DESC;

Because the security predicate is embedded, this query automatically excludes plants outside the running user's authority. A common secondary pattern aggregates pass rates across plants and periods to support quality dashboards or KPI extracts for the PMI analytics layer. Report developers should note that the aggregate columns are computed per-row via the PMI_PRODUCTION_SUM package, so wide date-range reports on large batch populations can be resource intensive and benefit from tight fiscal period filters.