Search Results trans_value

Overview

The object PMI_EDW_BTCH_GRADE_F_IV is a database view belonging to the Process Manufacturing Intelligence (PMI) product family within Oracle E-Business Suite. PMI is documented as obsolete in the ETRM metadata, and the view itself carries the note "Not implemented in this database." This designation indicates that the object formed part of the legacy PMI extract, transform, and load (ETL) layer that fed the Process Manufacturing Intelligence data warehouse, a pre-OBIEE analytics solution for process manufacturing. In EBS 12.1.1 and 12.2.2 environments, PMI has been superseded by Oracle Business Intelligence Applications (OBIA) and the Process Manufacturing (OPM) schema objects that remain in the database.

The "_IV" suffix conventionally denotes an "interface view" — a lightweight projection built over a base table to expose a stable, denormalized column set for downstream extraction programs. The corresponding base object is PMI_EDW_BTCH_GRADE_F, a batch-grade fact table that stores quantity and value movements at the batch grade level. The view's role in EBS reporting and integration is therefore to present a flattened, currency-aware extract of batch-grade transaction data for loading into the PMI warehouse fact dimension.

Underlying Base Objects

The ETRM metadata for this view documents no referenced base objects, which is consistent with an obsolete object whose dependency chain is no longer maintained by the EBS data model. However, the embedded view text is explicit: FROM PMI_EDW_BTCH_GRADE_F. The view is a single-table projection — a SELECT ... FROM PMI_EDW_BTCH_GRADE_F — with no joins, unions, or aggregations present in the documented definition.

Two derived columns are notable. The view selects ROWID ROW_ID, exposing the physical row identifier of the underlying fact row, and aliases USER_ATTRIBUTE15 OPERATION_CODE, repurposing the fifteenth descriptive flexfield attribute as a warehouse operation code. Because the view is a straightforward projection, its columns map one-to-one to columns of PMI_EDW_BTCH_GRADE_F, with only these two exceptions. In a functioning environment the base fact table would be populated by PMI concurrent programs that extracted OPM batch and grade cost data.

Key Columns

• BASE_CURRENCY — the functional or base currency in which TRANS_VALUE is denominated; critical for any monetary reporting because it removes the need to re-derive ledger currency from the OPM costing tables.
• BATCH_GRADE_PK / BATCH_GRADE_PK_KEY — the primary key and surrogate key of the batch-grade record.
• COST_METHOD — the OPM cost method (for example, standard versus actual) applied when the transaction value was calculated.
• GRADE_PK_KEY, ITEM_FK_KEY, ITEM_UOM — surrogate keys to the grade and item dimensions, plus the unit of measure for the transaction quantity.
• LOT_NO, SUBLOT_NO, QC_GRADE — lot and sublot identifiers together with the quality-control grade of the batch.
• OPM_ORG_FK_KEY, TIME_FK_KEY — foreign keys to the OPM organization and time dimensions.
• TRANS_QTY, TRANS_VALUE — the transaction quantity and its monetary value in BASE_CURRENCY.
• USER_ATTRIBUTE1–15, USER_MEASURE1–5, USER_FK1–5_KEY — extensibility columns intended to carry customer-specific descriptive attributes, measures, and foreign keys through the extract.
• ROW_ID, OPERATION_CODE — the derived row identifier and the aliased operation code described above.

Common Use Cases and Queries

Historically, this view supported cost and yield reporting by base currency, batch grade, and organization. A typical extract query would filter on organization and time keys and sum the transaction value:

• SELECT BASE_CURRENCY, OPM_ORG_FK_KEY, GRADE_PK_KEY, SUM(TRANS_VALUE) FROM PMI_EDW_BTCH_GRADE_F_IV GROUP BY BASE_CURRENCY, OPM_ORG_FK_KEY, GRADE_PK_KEY;
• SELECT LOT_NO, SUBLOT_NO, QC_GRADE, TRANS_QTY, TRANS_VALUE FROM PMI_EDW_BTCH_GRADE_F_IV WHERE BASE_CURRENCY = 'USD' AND COST_METHOD = 'Standard';
• SELECT OPERATION_CODE, COUNT(*) FROM PMI_EDW_BTCH_GRADE_F_IV GROUP BY OPERATION_CODE;

Because the metadata records "Not implemented in this database," queries against this view will fail in a standard 12.1.1 or 12.2.2 installation unless the PMI schema objects were manually deployed. Consultants should treat it as a reference artifact when migrating legacy PMI extracts to OBIA or to custom OPM-based reporting.