Search Results default_uom

Overview

PMI_REP_PROD_ACTUAL_PLAN_V is a reporting view owned by the APPS schema within the Process Manufacturing Intelligence (PMI) product family. It serves as the base view for the PMI Production Variance Reports, providing a consolidated, period-oriented comparison of actual and planned material consumption against production batches. The view is registered as VALID in Oracle EBS 12.1.1 and 12.2.2 and is intended primarily as a data source for BI Publisher and Oracle Reports deliverables shipped with PMI, rather than as a transactional object.

Functionally, the view joins batch execution data from the process manufacturing execution tables to the organization master, the fiscal calendar policy, and a derived PMI time dimension. It returns one row per material line per batch, expressed in a common unit of measure driven by the profile option PMI$CONV_UOM. Because the view applies row-level security through PMI_SECURITY_PKG.SHOW_RECORD, users only see records for organizations to which they have been granted access.

Underlying Base Objects

The view is defined over the following documented objects:

• GME_BATCH_HEADER (synonym) — batch master records; supplies batch status, batch type, plant code, and actual completion date.
• GME_MATERIAL_DETAILS (synonym) — batch material lines; supplies item, unit of measure, actual quantity, planned quantity, and line type.
• SY_ORGN_MST (synonym) — organization master; supplies company code and organization code.
• GL_PLCY_MST (synonym) — fiscal policy master; links the company code to a set of books name.
• PMI_GL_TIME_V (view) — PMI time dimension; supplies period, quarter, and year identifiers together with period start and end dates.
• GMICUOM (package) — provides I2UOM_CV, the quantity conversion routine used to normalize quantities into the reporting UOM.
• FND_PROFILE (package) — retrieves the PMI$CONV_UOM profile value used as the default reporting unit of measure.
• PMI_SECURITY_PKG (package) — enforces organization-level security via the SHOW_RECORD function.
• DUAL (synonym) — used to materialize the profile value as a single-row inline view.

Key Columns

• COMPANY_ID — company code derived from SY_ORGN_MST.CO_CODE; identifies the legal entity for reporting.
• ORGANIZATION_ID — organization code (ORGN_CODE) of the plant that produced the batch.
• YEAR_ID, QUARTER_ID, PERIOD_ID — fiscal calendar identifiers sourced from PMI_GL_TIME_V, enabling period-based variance aggregation.
• LINE_TYPE — classification of the material line (for example, ingredient or product), allowing actual and plan rows to be distinguished in variance calculations.
• ACTUAL_QTY — actual consumed or produced quantity, converted by GMICUOM.I2UOM_CV into the profile-defined default UOM.
• PLAN_QTY — planned quantity for the same material line, converted using the same routine so that actual and plan are directly comparable.

Common Use Cases and Queries

The view is most commonly used to drive production variance analysis: comparing planned versus actual material usage per batch, per period, and per organization. A representative query aggregates variances by period:

• SELECT period_id, organization_id, line_type, SUM(actual_qty) actual_qty, SUM(plan_qty) plan_qty, SUM(actual_qty - plan_qty) variance FROM pmi_rep_prod_actual_plan_v GROUP BY period_id, organization_id, line_type;
• Filtering by company or organization for a specific fiscal period to support plant-level performance reviews.
• Feeding BI Publisher templates for the standard PMI Production Variance reports.

Because quantities are returned in a single normalized UOM, the view is well suited to cross-plant comparisons. Consumers should note that only batches with BATCH_STATUS in (3, 4) and BATCH_TYPE = 0 are included, and that completion date must fall within the derived period boundaries. As with all PMI reporting views, results are constrained by PMI security, so the same query may return different row sets for different users.