Search Results rlm_cust_item_cum_keys




Overview
Explore in AI Chat

Overview

The view APPS.RLM_CUM_SHIPFR_CUST_ITEMS_V is a reporting and integration object within the Oracle E-Business Suite (EBS) Release 12.1.1 and 12.2.2 environments. It exposes customer item definitions that are eligible for cumulative shipment processing, filtered to only those customer item and ship-to address combinations that have been registered as cumulative keys. The view is primarily significant to Oracle's Return Material Authorization and logistics flows, where cumulative shipment tracking against customer items, ship-to addresses, and dates is required for contract compliance, pricing, or consignment reconciliation.

Functionally, the view answers the question: "Which active customer items have valid cumulative tracking keys defined?" This makes it a convenient data source for reports, concurrent programs, and integration interfaces that must resolve valid customer-item/ship-to combinations without performing the multi-table join themselves. The view presents each qualifying customer item once per matching CUSTOMER_ITEM_ID, resolving the address match through an EXISTS subquery against RLM_CUST_ITEM_CUM_KEYS.

Underlying Base Objects

According to the ETRM 12.2.2 metadata, the view is defined over two documented objects, both referenced through APPS synonyms:

  • MTL_CUSTOMER_ITEMS — the base table supplying customer item attributes. This is the driving table in the FROM clause (aliased MTL).
  • RLM_CUST_ITEM_CUM_KEYS — the cumulative keys table referenced in the correlated EXISTS subquery. This table stores the customer item / ship-to address combinations that participate in cumulative shipment processing.

The join condition links RLM_CUST_ITEM_CUM_KEYS.CUSTOMER_ITEM_ID to MTL_CUSTOMER_ITEMS.CUSTOMER_ITEM_ID. The address matching logic is expressed as:

SHIP_TO_ADDRESS_ID = NVL(MTL.ADDRESS_ID, SHIP_TO_ADDRESS_ID) OR SHIP_TO_ADDRESS_ID IS NULL

This permits a cumulative key with a NULL ship-to address to act as a wildcard matching any address on the customer item, while a populated ship-to address must match the item's ADDRESS_ID. Only rows where MTL.INACTIVE_FLAG = 'N' are returned, excluding inactive customer items.

Key Columns

Common Use Cases and Queries

Typical uses include validating customer items against cumulative key setup, driving shipment or RMA reports, and populating LOVs. A representative query listing active items for a given customer is:

SELECT customer_item_id, customer_item_number, address_id, customer_category_code
FROM apps.rlm_cum_shipfr_cust_items_v
WHERE customer_id = :p_customer_id;

To find items covered by a wildcard cumulative key (NULL ship-to), filter on rows whose cumulative key has a null ship-to address via the underlying table:

SELECT v.customer_item_id, v.customer_item_number
FROM apps.rlm_cum_shipfr_cust_items_v v
WHERE EXISTS (SELECT 1 FROM apps.rlm_cust_item_cum_keys k
WHERE k.customer_item_id = v.customer_item_id
AND k.ship_to_address_id IS NULL);

Because the view already enforces cleanliness rules, it is generally preferable to query it directly rather than reconstructing the underlying joins.