Search Results service_item_flag

Overview

AHM_SVC_MTL_ITEMS_V is a database view associated with the AHM – Hosting Manager product family, a module classified as obsolete in Oracle EBS 12.1.1 and 12.2.2. The view exposes a filtered list of service-oriented inventory items, presenting the essential descriptive attributes of each item such as its name, unit of measure, and the inventory organization to which it belongs. In the context of service coverage processing, the view functions as a convenience layer that isolates the subset of item master records that are genuinely usable as service items, thereby sparing downstream reports and integrations from repeatedly encoding the same filtering logic.

The view is particularly relevant to environments or customizations that still reference AHM-era service coverage functionality. Because AHM is documented as obsolete, the view is not implemented in a standard database, and any dependency upon it should be treated as a legacy construct. Nevertheless, where it exists, it serves reporting and integration consumers that need a narrow, pre-qualified set of service items.

Underlying Base Objects

The view is defined over a single base table, MTL_SYSTEM_ITEMS_B, the core item master table in Oracle Inventory. No additional base objects are documented in the ETRM metadata; the referenced base object list is recorded as none, and the implementation status is noted as not implemented in the database.

The view applies a compound WHERE clause against MTL_SYSTEM_ITEMS_B. It requires ENABLED_FLAG = 'Y', an effective date window bounded by START_DATE_ACTIVE and END_DATE_ACTIVE (defaulting to SYSDATE when null), CUSTOMER_ORDER_FLAG = 'Y', SERVICE_ITEM_FLAG = 'Y', CUSTOMER_ORDER_ENABLED_FLAG = 'Y', INVENTORY_ITEM_STATUS_CODE = 'ACTIVE', ORDERABLE_ON_WEB_FLAG = 'Y', and CONTRACT_ITEM_TYPE_CODE = 'SERVICE'. The combined effect is that only active, orderable, web-enabled service items eligible for customer orders are surfaced. Note that the SELECT list and the documented column list diverge in naming: the query projects ORGANIZATION_ID and PRIMARY_UNIT_OF_MEASURE, while the metadata columns are named INV_ORG_ID and UOM_CODE, suggesting an alias mapping in the deployed definition.

Key Columns

• INVENTORY_ITEM_ID — The unique surrogate key of the item in MTL_SYSTEM_ITEMS_B; the primary join key for downstream references.
• SEGMENT1 — The user-facing item number or concatenated segment value used to identify the item.
• DESCRIPTION — The item's descriptive text as maintained in the item master.
• ORGANIZATION_ID (INV_ORG_ID) — The inventory organization that owns the item record, since MTL_SYSTEM_ITEMS_B is organization-specific.
• PRIMARY_UNIT_OF_MEASURE (UOM_CODE) — The item's primary unit of measure, relevant to service quantities and pricing.

The metadata column list also references NAME and UOM_CODE, which map conceptually to the item number and the primary UOM respectively. No other attributes are exposed; the view is deliberately minimal.

Common Use Cases and Queries

Typical usage centers on service coverage and service order flows that must present only valid service items. A representative query retrieving all service items in a given organization is:

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

Because SERVICE_ITEM_FLAG = 'Y' is enforced internally, callers searching on the "service_item_flag" concept need not add that predicate themselves; the view guarantees it. A join to MTL_SYSTEM_ITEMS_TL for translated descriptions, or to MTL_ITEM_CATEGORIES for classification, is a common extension. Given the obsolete status of AHM, the recommended long-term practice is to replicate the view's filtering directly against MTL_SYSTEM_ITEMS_B in supported custom code.