Results for “current_cost”

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

Overview

IC_ITEM_WHS is a table in the GMI (Process Manufacturing Inventory) product family within Oracle E-Business Suite 12.1.1 and 12.2.2. It resides in the GMI schema and carries a documented status of VALID. The ETRM metadata describes the table with the annotation "*NOT USED*," indicating that the object is retained in the physical schema for structural or historical reasons but is not actively referenced by current application logic. Despite this annotation, the table remains a valid, queryable object with a defined primary key and a documented set of foreign key relationships.

The table models the association between an inventory item and a warehouse. Its granularity is one row per item-and-warehouse combination, which makes it a natural candidate for a link table in a dimensional or Data Vault style model. The heuristic Data Vault classification mined from the foreign key structure is link. This classification is a modeling suggestion rather than an application-enforced designation: IC_ITEM_WHS connects an item dimension (IC_ITEM_MST / IC_ITEM_MST_B) to a warehouse dimension (IC_WHSE_MST), with its own descriptive attribute, CURRENT_COST, carried on the relationship.

Key Information Stored

The documented physical schema for IC_ITEM_WHS in ETRM 12.2.2 lists eight columns. The most significant columns and their roles are as follows:

• ITEM_ID — Identifies the inventory item. It participates in the composite primary key and in two foreign key relationships, referencing IC_ITEM_MST_B and IC_ITEM_MST.
• WHSE_CODE — Identifies the warehouse. It participates in the composite primary key and is a foreign key to IC_WHSE_MST.
• CURRENT_COST — Holds the current cost value associated with the item at the given warehouse. This is the only non-key, non-audit descriptive attribute documented for the table.
• CREATION_DATE — Audit column recording when the row was inserted.
• CREATED_BY — Audit column identifying the user or process that created the row.
• LAST_UPDATE_DATE — Audit column recording the most recent modification timestamp.
• LAST_UPDATED_BY — Audit column identifying the user or process responsible for the most recent change.
• LAST_UPDATE_LOGIN — Audit column capturing the login session associated with the last update.

The surrogate primary key is IC_ITEM_WHS_PK, defined over (ITEM_ID, WHSE_CODE). Because the primary key is composite and built from two business-meaningful columns rather than a generated sequence, there is no separate surrogate identifier distinct from the business key. The unique index IC_ITEM_WHS_PK (ITEM_ID, WHSE_CODE) is documented as the sole business-key candidate, enforcing uniqueness of each item-and-warehouse pairing.

Common Use Cases and Queries

Although the table is annotated as not used, analysts frequently encounter it while tracing item-to-warehouse relationships. A typical query joins IC_ITEM_WHS to IC_ITEM_MST and IC_WHSE_MST to resolve codes and descriptions:

• Warehouse coverage by item — select ITEM_ID, WHSE_CODE, CURRENT_COST from IC_ITEM_WHS where ITEM_ID = :item_id, to list every warehouse associated with an item.
• Cost comparison across warehouses — aggregate CURRENT_COST by WHSE_CODE to compare item valuation between facilities.
• Reconciliation against master data — left join IC_ITEM_WHS to IC_ITEM_MST on ITEM_ID to identify items with no warehouse assignment, or join to IC_WHSE_MST on WHSE_CODE to find orphaned warehouse codes.
• Duplicate detection — group by ITEM_ID, WHSE_CODE and count rows greater than one to validate the IC_ITEM_WHS_PK constraint at the reporting layer.
• Audit and change tracking — filter on LAST_UPDATE_DATE to report rows modified within a given period.

Because the object is not actively used, reports built on it should be validated against the live item-warehouse tables before being treated as authoritative.

Related Objects

The foreign key metadata documents the following relationships, all of which are useful join paths:

• IC_ITEM_MST_B — referenced by IC_ITEM_WHS.ITEM_ID; the base item master table.
• IC_ITEM_MST — referenced by IC_ITEM_WHS.ITEM_ID; the primary item master table holding item definitions.
• IC_WHSE_MST — referenced by IC_ITEM_WHS.WHSE_CODE; the warehouse master defining valid warehouse codes.

These three tables form the complete documented dependency set for IC_ITEM_WHS. Joins should be made on ITEM_ID for the item masters and on WHSE_CODE for the warehouse master. No views or APIs referencing this table are documented in the ETRM excerpt, and the "*NOT USED*" designation suggests downstream consumers should prefer the currently active inventory item-warehouse tables for production reporting.