Search Results cmp_batches

Overview

PMI_REP_PROD_STATUS_V is an APPS-owned database view in Oracle E-Business Suite that supports the Process Manufacturing Intelligence (PMI) Production Status Report. In the ETRM documentation for release 12.1.1 and 12.2.2, the object is flagged with a status of VALID, while its parent product, PMI – Process Manufacturing Intelligence, is marked Obsolete. The view consolidates batch-level production activity into period-oriented aggregates, exposing batch counts and monetary values partitioned by process batch status: pending, work-in-process, and completed. Because PMI reporting has been superseded, the view should be treated as a legacy reporting artifact retained for backward compatibility with historical or customized report definitions.

The view does not store data; it derives its output at runtime from batch headers, material details, pending inventory transactions, organization master data, and GL fiscal calendar and policy data. Its role in EBS reporting and integration is to provide a single query surface for the Production Status Report, allowing reporting engines and custom queries to retrieve production status metrics without embedding the complex join and DECODE logic themselves.

Underlying Base Objects

The documented base objects are GL_PLCY_MST (synonym), GME_BATCH_HEADER (synonym), GME_MATERIAL_DETAILS (synonym), IC_TRAN_PND (synonym), PMI_COMMON_PKG (package), PMI_GL_TIME_V (view), PMI_SECURITY_PKG (package), and SY_ORGN_MST (synonym). The synonyms resolve to the underlying process manufacturing and financial tables owned by the relevant product schemas.

• GME_BATCH_HEADER supplies batch identity, plant, batch type, and batch status used to classify records as pending, WIP, or completed.
• GME_MATERIAL_DETAILS contributes material detail lines restricted to LINE_TYPE = -1.
• IC_TRAN_PND provides pending production transactions linked by DOC_ID and LINE_ID, with TRANS_QTY driving value calculations.
• SY_ORGN_MST resolves organization codes and company codes, joining batch plant codes to fiscal policy companies.
• GL_PLCY_MST supplies the costing method (GL_COST_MTHD) and set of books linkage.
• PMI_GL_TIME_V provides the GL fiscal calendar hierarchy—year, quarter, and period—with period start and end dates.
• PMI_COMMON_PKG exposes PMICO_GET_COST, a cost lookup function invoked for each transaction line.
• PMI_SECURITY_PKG exposes SHOW_RECORD, enforcing organization-level security at query time.

Key Columns

• COMPANY_ID / ORGANIZATION_ID — Company and organization identifiers derived from the organization master.
• YEAR_ID, QUARTER_ID, PERIOD_ID — Fiscal calendar identifiers from PMI_GL_TIME_V, allowing period-based aggregation.
• PND_BATCHES / PND_VALUE — Count and value of batches with status 1 (pending). Value uses the negative of transaction quantity multiplied by unit cost.
• WIP_BATCHES / WIP_VALUE — Count and value of batches with status 2.
• CMP_BATCHES / CMP_VALUE — Count and value of batches with status 3 or 4 (completed).

The often-searched column PLAN_CMPLT_DATE appears in the view text as the costing date argument passed to PMICO_GET_COST for pending batches, and as an input to the TRUNC(DECODE(...)) expression that filters records into the fiscal period. For pending batches the period filter uses PLAN_CMPLT_DATE; for WIP batches it uses ACTUAL_START_DATE; for completed batches it uses ACTUAL_CMPLT_DATE. PLAN_CMPLT_DATE is therefore central to both period assignment and cost valuation in this view.

Common Use Cases and Queries

Typical uses include period-by-period production status reporting, reconciliation of pending versus completed batch values, and cost variance analysis across organizations.

SELECT COMPANY_ID, ORGANIZATION_ID, PERIOD_ID,
       PND_BATCHES, PND_VALUE,
       WIP_BATCHES, WIP_VALUE,
       CMP_BATCHES, CMP_VALUE
FROM   APPS.PMI_REP_PROD_STATUS_V
WHERE  PERIOD_ID = :period_id;

Because PLAN_CMPLT_DATE is not projected as a selected column in the view definition, users searching for it cannot query it directly. Its influence is internal—through period bucketing and cost derivation. Organizations planning a migration off the obsolete PMI module should identify dependent custom reports and reimplement the logic against current Oracle Process Manufacturing cost and batch tables.