Results for “conv_uom”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

APPS.PMI_REP_PROD_ACTUAL_PLAN_V is a reporting view in Oracle Process Manufacturing (OPM), part of the EBS 12.1.1 and 12.2.2 application schema. It exposes production batch quantities for both actual and planned material consumption, aggregated by organization, fiscal period, quarter, and year, and normalized to a single reporting UOM defined by a profile option. The view was created specifically to support the "Production Actual vs. Plan" style report, which compares what was actually consumed or produced against what was planned for a given batch. Because the view resolves the reporting unit of measure dynamically from a profile value rather than storing it, it becomes the canonical source for period-over-period production variance reporting in OPM.

The name's "REP" prefix signals its role as a reporting object rather than a transactional one. It is typically consumed by concurrent programs, Business Intelligence Publisher reports, and custom analytics that need fiscal-calendar-aligned OPM production figures without re-deriving period mapping or unit conversion logic.

Underlying Base Objects

The view joins several documented OPM and EBS objects:

• GME_BATCH_HEADER — batch master; filtered to batch_status IN (3,4) and batch_type = 0, restricting to completed/released production batches.
• GME_MATERIAL_DETAILS — batch line detail supplying item_id, item_um, line_type, actual_qty, and plan_qty.
• SY_ORGN_MST — organization master, providing co_code (company) and orgn_code (organization).
• GL_PLCY_MST — fiscal policy master, linking company to set of books and the fiscal calendar.
• PMI_GL_TIME_V — fiscal calendar view yielding YEAR_ID, QUARTER_ID, PERIOD_ID and period start/end dates.
• GMICUOM — the OPM UOM conversion package; its I2UOM_CV function converts quantities between item UOMs.
• FND_PROFILE — supplies the PMI$CONV_UOM profile value as the default reporting UOM.
• PMI_SECURITY_PKG — enforces organization-level security via SHOW_RECORD.

Key Columns

• COMPANY_ID / ORGANIZATION_ID — company and plant/organization identifiers from SY_ORGN_MST.
• YEAR_ID, QUARTER_ID, PERIOD_ID — fiscal calendar keys derived from PMI_GL_TIME_V.
• LINE_TYPE — material detail line classification (e.g., product vs. ingredient).
• ACTUAL_QTY — actual quantity converted via GMICUOM.I2UOM_CV(item_id, 0, item_um, actual_qty, default_uom).
• PLAN_QTY — planned quantity converted the same way, so both figures share one reporting UOM.

The conversion argument 0 and the fifth parameter profile.default_uom mean every returned row is expressed in the UOM set in the PMI$CONV_UOM profile.

Common Use Cases and Queries

The view is most often queried to build variance reports per fiscal period. A representative query:

• SELECT organization_id, period_id, line_type, SUM(actual_qty) actual, SUM(plan_qty) plan FROM apps.pmi_rep_prod_actual_plan_v WHERE year_id = :yr GROUP BY organization_id, period_id, line_type;
• Feeding BIP datasets for period variance dashboards.
• Validating that quantities reconcile after changing the PMI$CONV_UOM profile, since the same underlying data returns different values under different reporting UOMs.

Because organization security is enforced inside the view via PMI_SECURITY_PKG, users automatically see only the plants they are authorized to view, making it safe for direct reporting use.