Search Results no_of_samples_complet




Overview

APPS.PMIFV_BATCH_QC_V is a Business Intelligence System (BIS) view owned by the APPS schema in Oracle E-Business Suite, registered in FND Design Data under the internal name PMI.PMIFV_BATCH_QC_V. Its documented status is VALID in both Oracle EBS 12.1.1 and 12.2.2. The view consolidates batch quality control details, presenting production batch characteristics alongside quality sampling metrics and the associated GL accounting period context. It is one of the PMIFV series of Process Manufacturing (OPM) reporting views, intended primarily for operational reporting, dashboards, and downstream extract/integration jobs rather than for transactional data entry.

The view is not referenced by any other database object, confirming its role as a terminal reporting entity. Consumers query it directly through BI Publisher reports, custom concurrent programs, OBIEE/BI extracts, or ad hoc SQL. The specific column NO_OF_TIMES_ADJUSTED captures how many times a batch's quality or quantity records have been adjusted, making the view relevant to quality-hold and rework analysis.

Underlying Base Objects

The view's definition resolves across several OPM and inventory synonyms and packages:

Because PMI_SECURITY_PKG is invoked within the view logic, results returned to users are automatically filtered according to OPM security profile settings, an important consideration for report design and troubleshooting.

Key Columns

  • PLANT_CODE, COMPANY_CODE, WHSE_CODE — organizational context for the batch.
  • BATCH_ID, BATCH_NO — surrogate and displayed batch identifiers.
  • ACTUAL_CMPLT_DATE — actual batch completion date, used for period and trend analysis.
  • ITEM_ID, ITEM_NO, ITEM_DESC — the produced item's identity and description.
  • PLANNING_CLASS — planning classification of the item or batch.
  • NO_OF_SAMPLES_TAKEN, NO_OF_SAMPLES_COMPLET, NO_OF_SAMPLES_PASSED — QC sampling counts, supporting pass-rate and first-time-quality calculations.
  • NO_OF_TIMES_ADJUSTED — the number of adjustment events recorded against the batch, commonly surfaced for rework and variance reporting.
  • FISCAL_YEAR, PERIOD_CODE, PERIOD_NAME — GL calendar period in which the batch activity falls.

Common Use Cases and Queries

Typical scenarios include batch quality scorecards, adjustment frequency monitoring, and period-end production summaries.

  • Identify batches adjusted more than once:
SELECT batch_no, item_no, actual_cmplt_date, no_of_times_adjusted
FROM   apps.pmifv_batch_qc_v
WHERE  no_of_times_adjusted > 1
ORDER  BY no_of_times_adjusted DESC;
  • Compute sample pass rate by period:
SELECT period_name, fiscal_year,
       SUM(no_of_samples_passed) / NULLIF(SUM(no_of_samples_taken),0) pass_rate
FROM   apps.pmifv_batch_qc_v
GROUP  BY period_name, fiscal_year;
  • Compare samples taken against completed samples to detect incomplete QC:
SELECT batch_no, no_of_samples_taken, no_of_samples_complet
FROM   apps.pmifv_batch_qc_v
WHERE  no_of_samples_taken > no_of_samples_complet;

Because the view executes PMI_SECURITY_PKG, all queries inherit OPM organization security; developers should ensure the reporting responsibility possesses the appropriate plant access to avoid missing rows.