Search Results related_uom_code

Overview

APPS.ASO_PVT_RELATED_ITEMS_BALI_V is an internal Oracle E-Business Suite view owned by the APPS schema and registered under FND Design Data as ASO.ASO_PVT_RELATED_ITEMS_BALI_V. It exposes related-item relationships for inventory items within a given organization, presenting data attributes such as unit of measure, unit price, availability, request and ship dates, service attributes, and returnability flags. The view is classified as "Internal" view type and carries the standard Oracle warning that it is for Oracle Internal Use Only; Oracle Corporation does not support direct access to applications data through this object except from standard Oracle Applications programs.

In the context of Oracle EBS 12.1.1 and 12.2.2, the view is part of the Oracle Advanced Supply Chain / Order Management related-item infrastructure. It is a technical (private) view used by Oracle's own application code rather than a public, customer-facing query surface. Despite the "BALI" suffix (commonly denoting a business-activity/library-level interface within Oracle naming conventions), the object behaves as a standard read-only view whose columns mirror the structure of the related-items data model exposed elsewhere in the application.

Underlying Base Objects

The documented view metadata identifies three referenced base objects: MTL_RELATED_ITEMS_VIEW, MTL_SYSTEM_ITEMS_VL, and MFG_LOOKUPS, all exposed through the APPS schema.

• MTL_RELATED_ITEMS_VIEW — supplies the core relationship rows: organization, inventory item, related item, relationship type identifier, and reciprocal flag. This is the primary driver of the view's grain.
• MTL_SYSTEM_ITEMS_VL — provides item-defining attributes such as the concatenated key flexfield segments, description, unit of measure, item type, BOM item type, and service-related flags for the related item.
• MFG_LOOKUPS — resolves relationship type identifiers into lookup meanings (the RELATIONSHIP_TYPE and related coded columns), following standard Oracle lookup conventions.

The object dependency listing also references APPS.ASO_PV, indicating the view participates within the ASO private view family. Because it is a view, no storage is allocated to it; all data originates from the underlying base objects, and any change to those objects' definitions flows through automatically.

Key Columns

The view exposes twenty-three columns. The following are the most significant for interpretation and querying:

• ORGANIZATION_ID — organization context for the relationship.
• INVENTORY_ITEM_ID / RELATED_ITEM_ID — the base item and the related item participating in the relationship.
• RELATIONSHIP_TYPE_ID / RELATIONSHIP_TYPE — the relationship identifier and its decoded lookup meaning.
• RECIPROCAL_FLAG — indicates whether the relationship applies in both directions.
• RELATED_ITEM / RELATED_ITEM_DESCRIPTION — the concatenated flexfield key and description of the related item.
• RELATED_UOM_CODE — the unit of measure code associated with the related item; this is the column most commonly associated with the search term "related_uom_code". It carries the purchasing or stocking UOM for the related item.
• RELATED_UNIT_PRICE — price of the related item, where populated.
• REQUEST_DATE, SHIP_DATE, AVAILABLE_QUANTITY, REQUEST_DATE_QUANTITY — dated demand and availability attributes.
• BOM_ITEM_TYPE, SERVICE_ITEM_FLAG, VENDOR_WARRANTY_FLAG, CUSTOMER_ORDER_ENABLED_FLAG, RETURNABLE_FLAG — item behavior flags for the related item.
• SERVICE_DURATION / SERVICE_PERIOD — service interval attributes for service-type related items.

Common Use Cases and Queries

Typical usage involves related-item recommendation, service and warranty attachment, and kit or configuration scenarios in Oracle Order Management and Advanced Supply Chain. A representative query retrieving related items and their UOM is:

SELECT organization_id, inventory_item_id, related_item, related_item_description, relationship_type, related_uom_code, related_unit_price FROM apps.aso_pvt_related_items_bali_v WHERE inventory_item_id = :item_id AND organization_id = :org_id;

For availability-oriented reporting, callers filter on AVAILABLE_QUANTITY and REQUEST_DATE_QUANTITY. Because the object is flagged Internal, direct SQL access should be treated as diagnostic only; production integrations should rely on supported Oracle APIs and public views rather than querying this view directly.