Search Results ar_rdr_items_v




Overview
Explore in AI Chat

Overview

AR_RDR_ITEMS_V is a read-only view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the Oracle Receivables (AR) product family and presents a de-duplicated list of inventory items drawn from the master item definition, resolved to a single representative organization. The view exists to support Receivables reporting and integration scenarios in which a caller requires one clean row per inventory item — an item identifier, its concatenated flexfield segments, its description, and a single organization context — without having to reconcile the multiple organization-level rows that exist in the underlying item master.

Because the item master in Oracle EBS is maintained at the organization level, the same inventory item typically appears many times in MTL_SYSTEM_ITEMS_VL, once for each organization in which it is defined. AR_RDR_ITEMS_V collapses those repetitions, returning the row associated with the minimum ROWID for each INVENTORY_ITEM_ID. This makes the view suitable as a lookup source for users and integrators who require a unique, stable name for an item rather than a full multi-organization item listing.

Underlying Base Objects

The view text documents two referenced objects: MTL_SYSTEM_ITEMS_VL and HR_ALL_ORGANIZATION_UNITS. Both are referenced through synonyms in the APPS schema. MTL_SYSTEM_ITEMS_VL is itself a view supplied by Oracle Inventory (INV) and is the multi-organization, translated item master; it carries the organization-scoped item attributes used here — INVENTORY_ITEM_ID, CONCATENATED_SEGMENTS, DESCRIPTION, and ORGANIZATION_ID. HR_ALL_ORGANIZATION_UNITS is the Oracle HR organization definition table, used as the organization master to constrain items to valid organization units.

The defining query projects four columns from MTL_SYSTEM_ITEMS_VL and filters with an inline view that joins MTL_SYSTEM_ITEMS_VL SI to HR_ALL_ORGANIZATION_UNITS OU on ORGANIZATION_ID, groups by INVENTORY_ITEM_ID, and selects MIN(SI.ROWID). The outer predicate restricts rows to those whose INVENTORY_ITEM_ID and ROWID pair appears in that grouped result, guaranteeing one row per item.

Key Columns

  • INVENTORY_ITEM_ID — The unique system identifier for the item, independent of organization. This is the join key back to MTL_SYSTEM_ITEMS and related INV tables.
  • CONCATENATED_SEGMENTS — The concatenated key flexfield segments forming the user-visible item number (for example, the segment-separated item name produced by the item key flexfield).
  • DESCRIPTION — The item description as stored on the selected master row, in the session language, since the source is a translated (_VL) view.
  • ORGANIZATION_ID — The organization of the representative row chosen by the MIN(ROWID) rule. Because the choice is arbitrary among organizations, this column should not be interpreted as a controlled "master organization" identifier.

Common Use Cases and Queries

The view is typically used as a lightweight item lookup in Receivables contexts, such as resolving an item name for a transaction line, validating item existence during an interface load, or populating an LOV where one row per item is required. A basic retrieval by item number follows:

  • SELECT inventory_item_id, concatenated_segments, description, organization_id FROM apps.ar_rdr_items_v WHERE concatenated_segments = :item_number;
  • SELECT inventory_item_id, concatenated_segments, description FROM apps.ar_rdr_items_v WHERE inventory_item_id = :item_id;
  • SELECT inventory_item_id, concatenated_segments, description FROM apps.ar_rdr_items_v ORDER BY concatenated_segments;

Where the caller requires organization-qualified item data — order management pricing, shipping, or on-hand inquiry — query MTL_SYSTEM_ITEMS_VL directly with an explicit ORGANIZATION_ID predicate rather than relying on this view, since the organization returned here is not deterministic. Integrators should also note that the ROWID-based de-duplication is efficient for point lookups but is not intended for high-volume joins across large item populations.