Search Results inventory_item_description




Overview
Explore in AI Chat

Overview

CST_MGD_LIFO_ITEM_COSTS_V is a PL/SQL view owned by the APPS schema that presents item cost information maintained by the Oracle Periodic Costing (PAC) engine, specifically for the managed LIFO cost method. Within Oracle E-Business Suite 12.1.1 and 12.2.2, this view serves as the data source for the Periodic Costing Item Inquiry form, allowing users to review item-level costs, market values, and justifications recorded against a given cost group, PAC period, and cost type. The view is associated with the BOM (Bills of Material) product family because Periodic Costing processing is initiated and managed from the Bills of Material/Costing responsibility. Its status is VALID, and it exposes descriptive attributes of inventory items alongside PAC cost layer details, which makes it suitable both for the inquiry form and for ad-hoc reporting and integration extracts where periodic costing data must be reconciled or audited.

Underlying Base Objects

The view joins six underlying objects to assemble a single row per PAC item cost layer. The referenced objects are:

The joins enforce that item costs are only visible when a matching cost group, PAC period, cost type, item master record, and legal entity exist, which aligns the view with the accounting and costing model of Periodic Costing.

Key Columns

  • ROW_ID — the ROWID of the underlying CST_PAC_ITEM_COSTS row, used by the inquiry form for row identification.
  • COST_LAYER_ID — uniquely identifies the item cost layer within Periodic Costing.
  • INVENTORY_ITEM_ID and INVENTORY_ITEM_DESCRIPTION — the item identifier and its description from the item master; these are the columns typically referenced by users searching for inventory_item_description.
  • UOM_CODE — the primary unit of measure of the item.
  • LEGAL_ENTITY_ID — the legal entity associated with the PAC period.
  • PAC_PERIOD_ID, COST_GROUP_ID, COST_TYPE_ID — the period, cost group, and cost type that scope the cost record.
  • ITEM_COST and MARKET_VALUE — the recorded cost and market value for the layer.
  • JUSTIFICATION — the free-text justification entered for the cost.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns.
  • REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program context identifying the process that created the row.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — descriptive flexfield columns available for additional reporting detail.

Common Use Cases and Queries

Typical uses include verifying periodic costing values before and after PAC runs, reconciling item costs and market values by legal entity, and extracting item descriptions for reporting. The following example lists item costs for a specific PAC period:

  • SELECT inventory_item_description, uom_code, item_cost, market_value, justification FROM apps.cst_mgd_lifo_item_costs_v WHERE pac_period_id = :period_id AND cost_group_id = :group_id ORDER BY inventory_item_description;

To locate a specific item by description, the view can be filtered on the INVENTORY_ITEM_DESCRIPTION column, which is populated from MTL_SYSTEM_ITEMS_VL. Reports should always constrain on PAC_PERIOD_ID and COST_GROUP_ID, since unconstrained queries across all periods and organizations can be expensive due to the multi-table join.