Results for “customer_item_desc”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The RLM_CUM_SHIPFR_CUST_ITEMS_V view is a Release Management (RLM) dictionary object owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents a filtered, reporting-ready projection of customer item definitions that participate in cumulative shipment and receipt processing at the ship-from (ship-to address) level. Rather than exposing every row of the underlying customer item master, the view restricts its result set to those customer items that possess at least one qualifying cumulative key record tied to a specific ship-to address. This makes the view a focused integration and reporting surface for RLM functionality that depends on cumulative shipped quantities per customer item and destination.

The view is commonly referenced by release management logic, shipping reports, and custom extensions that must resolve a customer item number, its description, and address context for cumulative tracking. Because it is a view rather than a base table, it carries no independent storage and always reflects the current state of its underlying tables.

Underlying Base Objects

Per the documented ETRM 12.2.2 metadata, the view is defined over two base objects, both exposed through APPS synonyms:

• MTL_CUSTOMER_ITEMS — the primary source of customer item attributes, aliased as MTL in the view definition.
• RLM_CUST_ITEM_CUM_KEYS — the cumulative keys table that drives the correlation between a customer item and its ship-to address.

The join is implemented with an EXISTS subquery. A row from MTL_CUSTOMER_ITEMS is returned only when a matching CUSTOMER_ITEM_ID exists in RLM_CUST_ITEM_CUM_KEYS, and the cumulative key's SHIP_TO_ADDRESS_ID either equals the item's ADDRESS_ID (using NVL to handle null addresses) or is itself null. Additionally, the view filters on MTL.INACTIVE_FLAG = 'N', excluding inactive customer items from the result set.

Key Columns

• CUSTOMER_ITEM_ID — Primary identifier of the customer item; also the join key to RLM_CUST_ITEM_CUM_KEYS.
• CUSTOMER_ID — The customer that owns the item definition.
• CUSTOMER_ITEM_NUMBER and CUSTOMER_ITEM_DESC — The customer-facing item number and description.
• ADDRESS_ID — The ship-to address associated with the customer item; matched against SHIP_TO_ADDRESS_ID in the cumulative keys table.
• ITEM_DEFINITION_LEVEL and CUSTOMER_CATEGORY_CODE — Classification attributes controlling how the customer item is defined and grouped.
• Standard WHO columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE, supporting audit and concurrent program traceability.

Common Use Cases and Queries

Typical scenarios include identifying customer items eligible for cumulative shipment processing per ship-to location, and validating that a customer item has an associated cumulative key before release or shipping transactions are executed.

To list all active customer items with cumulative ship-from keys:

• SELECT customer_item_id, customer_item_number, customer_item_desc, address_id FROM rlm_cum_shipfr_cust_items_v;

To retrieve the item definition for a specific customer and address:

• SELECT customer_item_number, customer_item_desc FROM rlm_cum_shipfr_cust_items_v WHERE customer_id = :p_customer_id AND NVL(address_id, -1) = NVL(:p_address_id, -1);

Because the view already applies the INACTIVE_FLAG and cumulative-key filters, queries against it need not repeat those predicates, simplifying custom reports and integration extracts within the RLM module.