Search Results ahm_si_mtl_items_v




Overview
Explore in AI Chat

Overview

AHM_SI_MTL_ITEMS_V is a reporting view belonging to the AHM – Hosting Manager product, a module now classified as obsolete within Oracle E-Business Suite. The view exposes service item master details — item name, description, unit of measure, and inventory organization context — for items that qualify as subscription-based service items. In Oracle EBS 12.1.1 and 12.2.2, its principal role was to supply a filtered, read-only list of sellable service items to Hosting Manager configuration and provisioning flows, as well as to integrations requiring a narrowed item catalog rather than the full inventory item master.

The view is documented as not implemented in the reference database associated with the ETRM metadata. Consequently, the view definition below reflects the documented text rather than a verified deployment, and environments upgraded from earlier releases may or may not carry the object forward. The user's search term, customer_order_flag, is directly relevant: it appears in the view's WHERE clause as one of several mandatory predicates, meaning the view cannot return items that are not flagged as customer-orderable.

Underlying Base Objects

The documented view text selects exclusively from MTL_SYSTEM_ITEMS_B, the item master base table that stores organization-specific item definitions in Oracle Inventory. No additional documented base objects are referenced, and the ETRM metadata records no listed owner and no further referenced objects. In practice, MTL_SYSTEM_ITEMS_B is one of the largest and most heavily indexed tables in an EBS instance, and the view inherits its organization-scoped nature: because the base table is segmented by ORGANIZATION_ID, every query against the view implicitly targets a specific inventory organization supplied by the caller.

The view applies eight concurrent filter conditions against the base table, which is the defining characteristic of the object:

Key Columns

The ETRM documentation lists a column set that differs slightly in naming from the SELECT list in the view text, and developers should reconcile the two when building dependent logic:

  • INVENTORY_ITEM_ID — Surrogate primary key of the item in MTL_SYSTEM_ITEMS_B; the essential join key to any other item-related table.
  • NAME (SEGMENT1) — The user-facing item number/segment; the documented view text exposes SEGMENT1, while the column list refers to it as NAME.
  • DESCRIPTION — Item description as maintained on the item master.
  • INV_ORG_ID (ORGANIZATION_ID) — The inventory organization owning the item record; required for correctly scoping lookups.
  • UOM_CODE (PRIMARY_UNIT_OF_MEASURE) — The primary unit of measure, used for quantity and pricing normalization.

Common Use Cases and Queries

The view is typically used to populate LOVs, validate provisioning requests, and drive subscription item selection in Hosting Manager-era customizations. A representative query, scoped to a single organization, follows:

  • SELECT inventory_item_id, segment1, description, organization_id, primary_unit_of_measure FROM ahm_si_mtl_items_v WHERE organization_id = :p_org_id ORDER BY segment1;

Because customer_order_flag is hard-coded to 'Y' inside the view, it cannot be weakened externally; callers needing items that are not customer-orderable must query MTL_SYSTEM_ITEMS_B directly. Given the obsolete status of AHM, new development should treat this view as legacy and reference MTL_SYSTEM_ITEMS_B with explicit predicates instead.