Search Results subscription_item_map_id




Overview
Explore in AI Chat

Overview

AHM_SI_DETAILS_V is a reporting view shipped with the Oracle E-Business Suite Hosting Manager module (product code AHM). Its documented purpose is to expose the detail of Service Items and Online Services — that is, the intersection of orderable service items held in inventory and the subscription-to-item mappings that drive hosted service provisioning. The view is classified as obsolete in the ETRM metadata for both 12.1.1 and 12.2.2, and the implementation note states that it is not implemented in the reference database. Consequently it should be treated as legacy documentation rather than a supported runtime object in current environments.

The view does not carry a defined owner in the documented metadata, and no base objects are formally registered against it. Its reporting role was to present a flattened, human-readable list of hosted services together with the inventory item attributes that identify each service, allowing operational and integration reporting to resolve a subscription item map identifier back to a describable service item.

Underlying Base Objects

The view text defines joins across three sources: MTL_SYSTEM_ITEMS (aliased A), AHM_SERVICE_SEL_V (aliased B), and AHM_SUBSCRIPTION_ITEMS_MAP (aliased C). MTL_SYSTEM_ITEMS is the standard Oracle Inventory item master, and AHM_SUBSCRIPTION_ITEMS_MAP is the AHM mapping table that associates subscription inventory items with hosted services. AHM_SERVICE_SEL_V is itself a view, indicating a layered definition; the ETRM record for AHM_SI_DETAILS_V documents no referenced base objects, so the underlying resolution of AHM_SERVICE_SEL_V must be confirmed against the environment in question.

The join predicates are explicit and restrictive. The item must carry ORDERABLE_ON_WEB_FLAG = 'Y' and SERVICE_ITEM_FLAG = 'Y'. The item is linked to the subscription map on both INVENTORY_ITEM_ID and ORGANIZATION_ID (matched to C.INVENTORY_ORG_ID), and the map row is linked to the service selection view on C.HOSTED_SVC_ID = B.HOSTED_SVCS_ID. All conditions are applied in the WHERE clause, so the result set is an inner join across all three sources.

Key Columns

  • HOSTED_SVCS_ID — identifier of the hosted service, sourced from AHM_SERVICE_SEL_V and matched to the subscription map's hosted service identifier.
  • SUBSCRIPTION_ITEM_MAP_ID — primary identifier of the subscription item mapping row; this is the column users most frequently search for when tracing a service item back to its subscription configuration.
  • ITEM_TYPE — classification of the mapped item as recorded on the subscription items map.
  • SEGMENT2 — the second segment of the inventory item key flexfield, typically carrying the item identifier component of the concatenated key.
  • DESCRIPTION — the inventory item description from MTL_SYSTEM_ITEMS.
  • UNIT_OF_MEASURE — the primary unit of measure of the service item, exposed as UNIT_OF_MEASURE although selected from A.PRIMARY_UNIT_OF_MEASURE.

Common Use Cases and Queries

The principal use case is resolving a subscription item map identifier to the service item that fulfils it, or listing all hosted services that are exposed as orderable service items. A typical query returns the service identifier, mapping identifier, and descriptive attributes:

  • SELECT hosted_svcs_id, subscription_item_map_id, item_type, segment2, description, unit_of_measure FROM ahm_si_details_v WHERE subscription_item_map_id = :map_id;
  • SELECT hosted_svcs_id, subscription_item_map_id, description FROM ahm_si_details_v ORDER BY hosted_svcs_id;

Because the object is documented as obsolete and is not implemented in the reference database, queries against it will fail on environments where the view was never deployed or was removed during upgrade. In 12.1.1 and 12.2.2 the equivalent information is more reliably obtained by joining AHM_SUBSCRIPTION_ITEMS_MAP directly to MTL_SYSTEM_ITEMS on INVENTORY_ITEM_ID and ORGANIZATION_ID, applying the same ORDERABLE_ON_WEB_FLAG and SERVICE_ITEM_FLAG filters. Any migration or reconciliation effort should therefore treat the view text above as the authoritative statement of intended logic rather than as a callable interface.