Search Results cst_item_list_temp




Overview
Explore in AI Chat

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

Overview

CST_ITEM_LIST_TEMP is a table owned by the BOM (Bills of Material) schema in Oracle E-Business Suite, defined with a status of VALID in both 12.1.1 and 12.2.2. The ETRM documentation describes its purpose concisely: it holds a temporary list of items for use in cost reporting. In practice, the table functions as a transient staging area into which cost reporting routines—typically concurrent programs and reporting engines that need to materialize a filtered set of inventory items and cost types before performing aggregation—insert rows that are subsequently consumed by downstream logic and purged.

The documented physical schema shows only three columns (INVENTORY_ITEM_ID, CATEGORY_ID, COST_TYPE_ID), confirming the table is deliberately narrow and optimized for a targeted reporting scope rather than as a persistent master or transactional store. From a Data Vault modeling perspective, the mined metadata classifies this object as standalone, meaning it participates in no hub-parent or satellite relationships other than the single foreign key noted below. This classification is a heuristic suggestion only; the table's temporary, reporting-driven nature means it does not naturally conform to a hub, link, or satellite pattern and is generally excluded from enterprise Data Vault models.

Key Information Stored

The documented schema exposes three columns. Because the table is a temporary reporting construct, no surrogate primary key is documented; the row identity is defined implicitly by the combination of the columns present.

  • INVENTORY_ITEM_ID — The inventory item identifier, the primary business-key candidate. It references the item master and identifies which items are included in the cost-reporting scope.
  • CATEGORY_ID — The item category identifier, used to qualify or group the items in the temporary list, supporting category-based cost reporting filters.
  • COST_TYPE_ID — The cost type identifier, which is the only documented foreign key. It references CST_COST_TYPES and determines the costing method (for example, standard, average, or frozen) under which the listed items are evaluated.

Together these three columns form the effective composite business key of the temporary set: an item, its category, and the cost type under which it should be costed. No additional descriptive, audit, or WHO columns are documented for this object in ETRM 12.2.2.

Common Use Cases and Queries

The table is populated and consumed by cost reporting programs. A representative query returns the item/cost-type combinations staged for a report run:

  • SELECT inventory_item_id, category_id, cost_type_id FROM bom.cst_item_list_temp;
  • Joining to the cost type master to label the costing method:
    SELECT t.inventory_item_id, t.category_id, c.cost_type
    FROM bom.cst_item_list_temp t, bom.cst_cost_types c
    WHERE t.cost_type_id = c.cost_type_id;
  • Counting items staged per cost type to validate report scope:
    SELECT cost_type_id, COUNT(*) FROM bom.cst_item_list_temp GROUP BY cost_type_id;

Because the contents are temporary, queries are typically diagnostic or troubleshooting in nature—verifying what a cost report included, confirming that a concurrent program populated the list correctly, or clearing stale rows before a re-run. The table is not a source for historical or trend reporting; persistent cost results reside in the CST cost tables.

Related Objects

The documented relationship data identifies a single foreign key. The most significant related objects are:

  • CST_COST_TYPES — referenced via CST_ITEM_LIST_TEMP.COST_TYPE_ID → CST_COST_TYPES. Defines the costing method applied to each staged item.
  • MTL_SYSTEM_ITEMS_B — the item master implied by INVENTORY_ITEM_ID; supplies item descriptions and attributes for reporting joins.
  • MTL_CATEGORIES_B — the category master implied by CATEGORY_ID; resolves category names for grouped cost reports.
  • Cost reporting concurrent programs and their report templates that read this table to drive item-level cost extraction.
  • Sibling CST temporary tables used by the same cost-reporting framework to stage complementary result sets.

Given its narrow schema and temporary role, CST_ITEM_LIST_TEMP should be treated as an internal implementation detail of the cost-reporting process rather than a durable integration point.