Search Results rhx_dp_l_itemorg_v

Overview

RHX_DP_L_ITEMORG_V is a custom Oracle EBS view belonging to the MRP (Master Scheduling/MRP) product family. The view is documented in ETRM as a "retrofitted" object, indicating that it was originally created in an earlier release and subsequently carried forward (re-fitted) into later application releases, including Oracle EBS 12.1.1 and 12.2.2. The "RHX_DP" prefix, combined with references to RHX_DP.GET_PARAMETER, identifies it as part of a customer- or partner-specific extension set rather than a seeded Oracle Application Object Library view.

Functionally, the view presents a list of inventory items together with their owning organization, expressed as a concatenated item-organization descriptor. It is designed to feed downstream reporting, data-pump, or integration processes with a clean, filtered list of valid, enabled, currently effective items that are assigned to a specific item category set. Rather than exposing raw base tables, the view enforces business rules (category set membership, item type, planning code, enablement, and effective dates) so that consumers receive only consistent, reportable records.

Underlying Base Objects

The view is defined over three core inventory tables:

• MTL_SYSTEM_ITEMS_KFV — the key flexfield view over MTL_SYSTEM_ITEMS_B, supplying the concatenated segment string and item attributes.
• MTL_PARAMETERS — the organization definition table, providing the organization code.
• MTL_ITEM_CATEGORIES — the item-to-category assignment table, used to restrict results to a configured category set.

The three tables are joined on INVENTORY_ITEM_ID and ORGANIZATION_ID. The category set identifier is not hard-coded; it is resolved at runtime through RHX_DP.GET_PARAMETER('RHX_DP_P_CATEGORY_SET'), and the item/organization delimiter through RHX_DP.GET_PARAMETER('RHX_DP_P_DELIMITER'). This parameterization makes the view configurable without code changes. Note that the ETRM metadata records "Not implemented in this database" and lists no formally documented base objects, so the relationship above is derived directly from the view text rather than from declared dependencies.

Key Columns

• INVENTORY_ITEM_ID — surrogate key of the item, joined from MTL_SYSTEM_ITEMS_KFV and MTL_ITEM_CATEGORIES.
• ITEM_ORG — a composite display value: the concatenated item segments, the configured delimiter, and the organization code, truncated to 240 characters.
• ITEM — the concatenated key flexfield segments (the item's descriptive identifier).
• ORGANIZATION_ID — the organization in which the item is defined.
• ORGANIZATION_CODE — the three-character (or defined-length) organization code from MTL_PARAMETERS.

Common Use Cases and Queries

The view is typically used to populate LOVs, validation lists, or extract files that require item-organization pairs scoped to a category set. Because filtering is built in, a simple SELECT returns a ready-to-use list:

• Retrieving all reportable item-organization combinations for a category set.
• Feeding integration or data-conversion routines that expect a delimiter-separated item-org key.
• Validating that an item is enabled, effective, and not a planning-code-6 or BOM-type-5 record before downstream processing.

A representative query:

SELECT ITEM_ORG, INVENTORY_ITEM_ID, ORGANIZATION_ID, ORGANIZATION_CODE
FROM RHX_DP_L_ITEMORG_V
ORDER BY ITEM_ORG;

For a single organization:

SELECT ITEM, ORGANIZATION_CODE
FROM RHX_DP_L_ITEMORG_V
WHERE ORGANIZATION_ID = :org_id;

Because the view depends on RHX_DP.GET_PARAMETER, administrators must ensure the function and its parameters (category set and delimiter) are correctly configured in each environment; otherwise the view may return no rows or raise runtime errors.