Results for “alternate_itema”

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

Overview

APPS.PMIBV_INV_SUMMARY_V is a read-only reporting view owned by the APPS schema within the Process Manufacturing Intelligence (PMI) product family of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. Its documented purpose is to present inventory balances aggregated by item, warehouse, and quality grade, while simultaneously enriching those balances with descriptive and planning attributes sourced from the item master. Because Process Manufacturing (OPM) maintains inventory in its own tables rather than exclusively in Oracle Inventory (INV), this view serves as a consolidated access point that combines quantity information with item-level context in a single queryable object.

The view is defined WITH READ ONLY, which explicitly prevents DML operations against it. Its role is therefore confined to reporting, inquiry screens, and integration extracts. The INVSUM alias carries all transactional quantity measures, while the ITEM alias contributes descriptive columns. The outer join (ITEM.ITEM_ID = INVSUM.ITEM_ID(+)) ensures that inventory summary rows are preserved even where a matching item master record is not found, though in normal operation the join is effectively one-to-one.

Underlying Base Objects

The view is documented as being defined over two base objects, both exposed as synonyms in the APPS schema:

• IC_SUMM_INV — the Process Manufacturing inventory summary table. This is the primary source of all on-hand and pending quantity measures, warehouse code, grade, item identifier, and audit columns.
• IC_ITEM_MST — the Process Manufacturing item master table. This supplies item descriptions, alternate item numbers, units of measure, and planning class.

The join is driven on ITEM_ID, with IC_SUMM_INV as the driving (left) table in the outer join. No aggregation, grouping, or filtering clauses appear in the view text; the summation implied by the underlying IC_SUMM_INV table is inherited rather than performed by the view itself.

Key Columns

The quantity columns are the operational core of the view. ONHAND_QTY and ONHAND_QTY2 carry primary and secondary UOM on-hand balances, and parallel pairs exist for production, order, shipping, purchasing, in-transit, and committed quantities.

Of particular relevance to the search term production_pending_qty, the view exposes PRODUCTION_PENDING_QTY and its dual-UOM counterpart PRODUCTION_PENDING_QTY2. These represent production quantities that have been requested or scheduled but not yet received into inventory — an essential measure for gauging outstanding shop-floor output. The documented column list shows PRODUCTION_PENDING_QTY and PRODUCTION_PENDING_QTY2 among the exposed fields; note the view-text excerpt aliases the underlying ONHAND_PROD_QTY, so implementers should confirm the exact column-to-source mapping in their instance version.

Descriptive columns include ITEM_NO, ITEM_DESCRIPTION, ALTERNATE_ITEMA, ALTERNATE_ITEMB, ITEM_UOM, ITEM_UOM2, and PLANNING_CLASS. Keys and audit columns comprise ITEM_ID, WHSE_CODE, QC_GRADE, CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE, and LAST_UPDATED_BY.

Common Use Cases and Queries

Typical usage includes inventory balance reporting by grade, warehouse-level stock inquiries, and extracts feeding planning or reconciliation processes. To isolate pending production quantities for a specific item:

• SELECT item_no, whse_code, qc_grade, production_pending_qty, production_pending_qty2 FROM apps.pmibv_inv_summary_v WHERE item_no = :item AND production_pending_qty > 0;
• SELECT whse_code, SUM(onhand_qty), SUM(production_pending_qty) FROM apps.pmibv_inv_summary_v GROUP BY whse_code;
• SELECT item_no, item_description, planning_class, onhand_qty, committed_production_qty FROM apps.pmibv_inv_summary_v WHERE whse_code = :whse ORDER BY item_no;

Because the view is read-only, all access is confined to querying. Report developers should confirm column naming against the live dictionary, since the documentation lists display names while the view text uses source-column aliases.