Results for “pmifv_batch_trans_v”

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

Overview

PMIFV_BATCH_TRANS_V is an APPS-owned read-only view in Oracle E-Business Suite, delivered under the PMI (Process Manufacturing Intelligence) product family. The ETRM metadata identifies the object as "Batch Transaction Details," and its purpose is to expose batch-level inventory transaction activity in a form suitable for cost, grade, and period reporting. Unlike a simple transactional table view, PMIFV_BATCH_TRANS_V enriches each qualifying inventory transaction with item master attributes, quality grade derivation, transaction value computed from standard costing logic, and the fiscal calendar period into which the transaction falls. It also enforces organization-level security, making it an appropriate source for operational reports, dashboards, and integration extracts where controlled visibility by plant is required. Because the view is declared WITH READ ONLY, it cannot be used for DML and serves strictly as a query and reporting artifact.

Underlying Base Objects

The view is defined over a mix of synonyms, views, and packages across the APPS schema. Its driving source is the IC_TRAN_CMP_VW1 view, aliased TRANCMP, which supplies the core inventory transaction rows. Item descriptive data is joined from the IC_ITEM_MST synonym, while the fiscal period context comes from PMI_GL_CALENDAR_V. Company-level policy information, including base currency, is retrieved from GL_PLCY_MST. Organization security is applied through a subquery on the SY_ORGN_MST synonym, filtered by PMI_SECURITY_PKG.SHOW_RECORD. Two additional package dependencies support derived values: PMI_PRODUCTION_SUM.FIND_PROD_GRADE supplies the quality grade, and PMI_COMMON_PKG.PMICO_GET_COST returns the unit cost used to compute transaction value.

Key Columns

• PLANT_CODE (ORGN_CODE): The organization responsible for the transaction.
• COMPANY_CODE (CO_CODE): The legal entity or company associated with the transaction.
• WHSE_CODE: Warehouse in which the transaction occurred.
• BATCH_ID (DOC_ID): Identifier linking the record to its originating batch document.
• ITEM_ID / ITEM_NO / ITEM_DESC: Item identity and description from the item master.
• LOT_ID: Lot identifier for the transacted material.
• PLANNING_CLASS / ITEM_UM: Item planning classification and unit of measure.
• QC_GRADE: Quality grade derived from PMI_PRODUCTION_SUM.FIND_PROD_GRADE, truncated to four characters.
• TRANS_QTY: Transaction quantity; only non-zero quantities are returned.
• TRANS_VALUE: Transaction quantity multiplied by the unit cost returned by PMI_COMMON_PKG.PMICO_GET_COST.
• FISCAL_YEAR / PERIOD_CODE / PERIOD_NAME: Fiscal calendar attributes from PMI_GL_CALENDAR_V.
• BASE_CURRENCY: Base currency code from GL_PLCY_MST, giving the currency context for TRANS_VALUE.

Common Use Cases and Queries

Typical uses include batch transaction reporting, grade mix analysis, period-end valuation, and secured plant-level extracts. Because the view already resolves item descriptions, costs, grades, and periods, consuming queries remain concise. Filtering by period and plant is the most common pattern, and the underlying WHERE clause restricts results to LINE_TYPE 1, non-zero quantities, and transactions whose date falls within an active calendar period.

A representative query returning period activity for a specific plant:

• SELECT plant_code, item_no, lot_id, qc_grade, trans_qty, trans_value, period_name, base_currency FROM apps.pmifv_batch_trans_v WHERE plant_code = :p_plant AND fiscal_year = :p_year AND period_code = :p_period ORDER BY item_no, lot_id;

A second pattern aggregates transaction value by item and grade to support batch valuation:

• SELECT item_no, qc_grade, SUM(trans_qty) total_qty, SUM(trans_value) total_value FROM apps.pmifv_batch_trans_v WHERE period_name = :p_period GROUP BY item_no, qc_grade ORDER BY item_no;

Users should note that results depend on organization security configuration and on the availability of costing data for each item and warehouse combination; where no cost is resolved, the computed TRANS_VALUE may be null or zero.