Results for “warehouse_name”

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

Overview

The PMIFV_PERIODINVENTORY_V view is an APPS-owned database object within the Process Manufacturing Intelligence (PMI) product family of Oracle E-Business Suite. It exposes quantity and usage information for items held in inventory across closed accounting periods, broken down by warehouse, location, lot, and item. The view is primarily intended for reporting and analytical consumption, particularly in the context of period-end inventory analysis and process manufacturing intelligence dashboards.

The view plays a significant role in period-status reporting. Because its driving rows are drawn from IC_PERD_BAL (the period balance table populated for closed periods), the data surfaced by PMIFV_PERIODINVENTORY_V is inherently period-scoped. Each row carries a PERIOD_ID, FISCAL_YEAR, PERIOD, and joined period descriptors from PMI_INV_CALENDAR_V, enabling users to slice inventory quantities, usage, and yield by accounting period. The view is defined as a UNION ALL of closed-period balances and current location-level inventory, giving a combined picture of historical and present on-hand stock.

Underlying Base Objects

The view is defined over a mix of synonyms, views, and PL/SQL packages. The principal base table is IC_PERD_BAL (aliased as INV), which supplies period balances including on-hand, usage, yield, and value metrics. Supporting master data comes from IC_ITEM_MST, IC_LOTS_MST, IC_WHSE_MST, IC_LOCT_MST, and IC_LOTS_STS. Quality hold reasons are resolved through GMD_HOLD_REASONS_VL, while calendar and period descriptions are sourced from PMI_INV_CALENDAR_V. Organization and company codes are retrieved via SY_ORGN_MST.

Two programmatic dependencies are central to the view's behavior: PMI_COST_ANALZ_PACK supplies the GMCA_GET_MEANING function used to derive the translated period status label, and PMI_SECURITY_PKG enforces organization-level row security through the SHOW_RECORD function. The view also references IC_LOCT_INV in the second branch of its UNION ALL, providing current location-level inventory quantities where period balance records are absent.

Key Columns

• LOCT_ONHAND / LOCT_ONHAND2 — On-hand quantity at the location level, expressed in the primary and secondary unit of measure.
• LOCT_USAGE / LOCT_USAGE2, LOCT_YIELD / LOCT_YIELD2 — Period usage and yield quantities, in primary and secondary UOM.
• LOCT_VALUE — Inventory value associated with the lot/location for the closed period.
• PERIOD_ID, FISCAL_YEAR, PERIOD, LOG_END_DATE — Period identification and the log end date of the closing period.
• WHSE_CODE, WHSE_NAME, ORGN_CODE, CO_CODE — Warehouse and organization identifiers, including the company code resolved through SY_ORGN_MST.
• ITEM_ID, ITEM_NO, ITEM_DESC1, ITEM_UM, ITEM_UM2 — Item identifiers, description, and primary/secondary UOM.
• LOT_ID, LOT_NO, SUBLOT_NO, QC_GRADE, EXPIRE_DATE, VENDOR_LOT_NO — Lot-level attributes including quality grade and expiry.
• LOT_STATUS, STATUS_DESC — Lot status code and its descriptive meaning.
• QCHOLD_RES_CODE, QCHOLD_RES_DESC — Quality hold reason code and description.
• LOCT_DESC, CAPACITY, CAPACITY_UM — Location description and storage capacity attributes.
• PERIOD_STATUS — A derived column computed via PMI_COST_ANALZ_PACK.GMCA_GET_MEANING('PERIOD_STATUS', 1) and truncated to ten characters, providing the status label for the period.

Common Use Cases and Queries

The view is most commonly used for period-end inventory reporting, lot traceability, and process manufacturing period-status analysis. A representative query reconciling on-hand quantities with period status might read:

SELECT period, fiscal_year, period_status,
       whse_code, item_no, lot_no, sublot_no,
       loct_onhand, loct_usage, loct_value
  FROM apps.pmifv_periodinventory_v
 WHERE period_status = 'Closed'
   AND fiscal_year = 2024
 ORDER BY whse_code, item_no, lot_no;

Because organization-level security is enforced inside the view via PMI_SECURITY_PKG.SHOW_RECORD, users only see records for organizations to which they are authorized, making the view suitable for direct use in Discoverer workbooks, OBIEE reports, and custom concurrent program extracts. Analysts frequently join the view back to IC_ITEM_MST or GMD_HOLD_REASONS_VL for additional attributes, though most descriptive columns are already denormalized for convenience.