Search Results plan_cmplt_date




Overview
Explore in AI Chat

Overview

APPS.PMI_REP_PROD_STATUS_V is a reporting view in Oracle Process Manufacturing (OPM) that consolidates production batch status information into a period-based summary. It is designed to support production reporting and cost analysis by aggregating batch counts and values across pending, work-in-process (WIP), and completed states. The view joins batch header, material detail, transaction pending, and GL period data to present a fiscal-period-aligned picture of manufacturing activity.

A defining characteristic of this view is its reliance on the plan_cmplt_date column from GME_BATCH_HEADER. This date is used both as a grouping/timing reference for pending batches and as the cost-effective date passed into the PMI_COMMON_PKG.PMICO_GET_COST function. For batch status 1 (pending), plan_cmplt_date determines the period into which the record falls, making it central to the view's temporal logic.

Underlying Base Objects

The view is defined over the following documented base objects:

  • GME_BATCH_HEADER — Batch master data; provides batch_status, batch_type, batch_id, and the plan_cmplt_date, actual_start_date, and actual_cmplt_date columns.
  • GME_MATERIAL_DETAILS — Material line detail for each batch, filtered to line_type = -1 (product lines) and joined via material_detail_id.
  • IC_TRAN_PND — Pending inventory transactions, filtered to doc_type = 'PROD', supplying trans_qty and warehouse codes.
  • SY_ORGN_MST — Organization master, providing orgn_code and co_code.
  • GL_PLCY_MST — GL fiscal policy, supplying cost method and set of books linkage.
  • PMI_GL_TIME_V — GL calendar view supplying YEAR_ID, QUARTER_ID, PERIOD_ID, and period start/end dates.
  • PMI_COMMON_PKG — Costing package invoked via PMICO_GET_COST.
  • PMI_SECURITY_PKG — Security package enforcing organization-level access through show_record.

Key Columns

  • COMPANY_ID / ORGANIZATION_ID — Company and organization identifiers.
  • YEAR_ID / QUARTER_ID / PERIOD_ID — Fiscal calendar keys aligned to the batch's effective date.
  • PND_BATCHES / PND_VALUE — Count and value of pending batches (batch_status = 1), dated by plan_cmplt_date.
  • WIP_BATCHES / WIP_VALUE — Count and value of batches in process (batch_status = 2), dated by actual_start_date.
  • CMP_BATCHES / CMP_VALUE — Count and value of completed and closed batches (batch_status 3 and 4), dated by actual_cmplt_date.

Common Use Cases and Queries

This view is typically used for periodic production status reporting, cost rollups, and pending transaction analysis. A representative query filtering on the plan completion timeframe follows:

  • Production status by period and organization.
  • Cost valuation of pending and completed batches.
  • Reconciliation of pending production transactions.

Sample SQL:

SELECT company_id, organization_id, year_id, quarter_id, period_id,
  pnd_batches, pnd_value, wip_batches, wip_value, cmp_batches, cmp_value
FROM apps.pmi_rep_prod_status_v
WHERE organization_id = :org_id
ORDER BY year_id, quarter_id, period_id;