Search Results support_inv_item_id

Overview

AHM_PARTY_SUB_ITEMS_V is a reporting view in the Oracle E-Business Suite Hosting Manager (AHM) module, which is identified as obsolete in the provided ETRM metadata. The view returns information about all subscribed items associated with a given party identifier, consolidating subscription records with their corresponding inventory item master definitions. Its primary role is to support reporting and integration queries that require a denormalized, party-centric perspective of service subscriptions, including item descriptions, units of measure, quantities, and service duration attributes.

The view is defined in the ETRM documentation for releases 12.1.1 and 12.2.2, but the metadata explicitly states that it is not implemented in this database. Consequently, it functions as documented metadata rather than a queryable object in the environment from which the excerpt was derived. The presence of the column SERVICE_DURATION_PERIOD_CODE — the term the user searched for — indicates that the view exposes subscription-level duration semantics for hosted or supported services.

Underlying Base Objects

The view is defined over two base tables through an inner join:

• AHM_SUBSCRIBED_ITEMS (aliased A) — the subscription transaction table that stores the association between a party's subscribed service, the inventory item, quantity, support item, and service duration information.
• MTL_SYSTEM_ITEMS_B (aliased B) — the inventory item master, providing descriptive and unit-of-measure attributes.

The join predicates are B.INVENTORY_ITEM_ID = A.INVENTORY_ITEM_ID and B.ORGANIZATION_ID = A.INVENTORY_ORG_ID. This ensures that each subscription row is matched to the item definition valid within the specific inventory organization recorded on the subscription. The join is an equi-join (inner join), so subscriptions whose item or organization cannot be resolved against MTL_SYSTEM_ITEMS_B are excluded from the result set. The ETRM metadata records no additional referenced base objects beyond these two.

Key Columns

• SUBSCRIBED_SVC_ID — identifier of the subscribed service to which the item belongs.
• SUBSCRIBED_ITEM_ID — unique identifier of the subscribed item record.
• STATUS — current status of the subscription (for example, active or inactive, per AHM conventions).
• INVENTORY_ITEM_ID and INVENTORY_ORG_ID — the item and organization keys used to join to the item master.
• QUANTITY — quantity of the subscribed inventory item.
• SUPPORT_INV_ITEM_ID — inventory item identifier representing the support entitlement.
• SUPPORT_QUANTITY — quantity associated with the support item.
• SEGMENT1 — item number (concatenated segment) from MTL_SYSTEM_ITEMS_B; it appears twice in the select list, so consuming queries should alias the projection explicitly.
• PRIMARY_UNIT_OF_MEASURE — primary UOM of the item.
• DESCRIPTION — item description.
• SVC_NAME — listed in the documented column set, representing the service name associated with the subscription.
• SERVICE_DURATION_PERIOD_CODE — code denoting the duration period applicable to the subscribed service, used to express the term or coverage period of the subscription.

Common Use Cases and Queries

Typical use cases include reporting all subscribed items for a party, auditing service duration terms across subscriptions, and reconciling support quantities against inventory items. The view is well suited to feed integrations that need item descriptions and UOMs alongside subscription data without re-joining the item master.

Sample query retrieving subscriptions with their duration codes:

SELECT subscribed_svc_id, subscribed_item_id, status, segment1 AS item_number, description, primary_unit_of_measure, quantity, support_quantity, service_duration_period_code
FROM ahm_party_sub_items_v
WHERE subscribed_svc_id = :p_service_id
ORDER BY subscribed_item_id;

Sample aggregate query summarizing quantities by duration period:

SELECT service_duration_period_code, COUNT(*) AS subscription_count, SUM(quantity) AS total_quantity
FROM ahm_party_sub_items_v
GROUP BY service_duration_period_code;

Because the metadata states the view is not implemented in the documented database and the AHM module is obsolete, availability should be verified in the target instance (for example, via ALL_VIEWS) before relying on it in custom code or reports.