Search Results int_ext_code

Overview

RLM_CUST_INV_ITEM_V is a consolidated reporting view owned by the APPS schema in Oracle E-Business Suite Release Management (RLM). Its purpose is to present a unified list of inventory items and customer items in a single result set, distinguishing each row by an internal/external indicator. The view merges internal inventory items sourced from the item master flexfield structure with externally defined customer items defined in the customer items table.

Users searching for MTL_CUSTOMER_ITEMS frequently encounter this view because it exposes customer item records alongside their internal inventory item counterparts. The view is read-only and is intended for inquiry, reporting, and integration scenarios where both internal and customer-facing identifiers must be reconciled in one place. In Release Management contexts this supports activities such as order release processing and item cross-referencing, where customer item numbers must be mapped to internal inventory item identifiers.

Underlying Base Objects

According to the documented ETRM metadata, RLM_CUST_INV_ITEM_V is defined over two referenced base objects:

• MTL_ITEM_FLEXFIELDS (VIEW) — provides the internal (master) item rows. It supplies the item number, description, and organization context for internal inventory items.
• MTL_CUSTOMER_ITEMS (SYNONYM) — provides the external customer item rows. It supplies the customer item number, customer item description, and the customer identifier.

The two sources are combined with a UNION. The internal branch selects from MTL_ITEM_FLEXFIELDS and hard-codes CUSTOMER_ID to 0 and INT_EXT_CODE to 'INTERNAL'. The external branch selects DISTINCT rows from MTL_CUSTOMER_ITEMS and hard-codes ORGANIZATION_ID to 0 and INT_EXT_CODE to 'EXTERNAL'. Because the two branches are structurally aligned, downstream consumers can treat the output as one homogenous item list.

Key Columns

• ITEM_NUMBER — For internal rows, the inventory item number from the item flexfield. For external rows, the customer item number.
• ITEM_ID — Aliased from INVENTORY_ITEM_ID for internal rows and from CUSTOMER_ITEM_ID for external rows. The meaning of this identifier therefore depends on INT_EXT_CODE.
• DESCRIPTION — The item description for internal rows or the customer item description for external rows.
• CUSTOMER_ID — The customer identifier for external rows; set to 0 for internal rows.
• ORGANIZATION_ID — The inventory organization identifier for internal rows; set to 0 for external rows.
• INT_EXT_CODE — The discriminator column, valued 'INTERNAL' or 'EXTERNAL', indicating the origin and semantics of the row.

Common Use Cases and Queries

The view is typically used to retrieve a combined item listing, to isolate internal or external items, or to locate customer item definitions. A simple listing follows:

• SELECT ITEM_NUMBER, ITEM_ID, DESCRIPTION, CUSTOMER_ID, ORGANIZATION_ID, INT_EXT_CODE FROM APPS.RLM_CUST_INV_ITEM_V;
• Internal inventory items only: add WHERE INT_EXT_CODE = 'INTERNAL'.
• Customer (external) items only: add WHERE INT_EXT_CODE = 'EXTERNAL', optionally filtered by CUSTOMER_ID.
• Lookup by item number: WHERE ITEM_NUMBER = :item_number.

Because ITEM_ID carries different semantics across the two branches, queries joining this view to other tables should always constrain on INT_EXT_CODE to avoid ambiguous matches. The view does not itself enforce referential joins, so consumers must apply the appropriate organization or customer context when interpreting results.