Search Results intrmd_ship_to_id




Overview
Explore in AI Chat

Overview

RLM_CUST_ITEM_CUM_KEYS_ALL is a transactional table in the Oracle Release Management (RLM) module, owned by the RLM schema. It stores the cumulative (CUM) key values associated with a particular ship-to/ship-from/item combination, according to the CUM Management rules defined for trading partners supported in Oracle Release Management. In the automotive and high-volume manufacturing supply chain context, CUM management tracks cumulative quantities shipped and received against a customer's authorization, so that shipped quantities can be reconciled against authorized release quantities on a running basis.

Each row in this table represents a distinct CUM accumulation key — a unique combination of customer item, ship-to and ship-from addresses, intermediate ship-to, bill-to, and supporting context such as CUM start date, record year, and purchase order number. This is the parent record for which individual CUM adjustments are captured elsewhere. The table is an _ALL table, indicating it stores data across multiple operating units (multi-org), partitioned logically by ORG_ID.

From a heuristic Data Vault classification derived from the foreign key structure, this object behaves as a standalone hub: it has a surrogate primary key (CUM_KEY_ID) that anchors the business concept of a CUM accumulation key, with descriptive and state-bearing attributes living on the same row. Deployments using Data Vault modeling may therefore treat it as the hub for the CUM key business entity.

Key Information Stored

The business key is captured by the unique index RLM_CUST_ITEM_CUM_KEYS_U1, composed of CUM_KEY_ID, SHIP_FROM_ORG_ID, SHIP_TO_ADDRESS_ID, BILL_TO_ADDRESS_ID, INTRMD_SHIP_TO_ID, CUSTOMER_ITEM_ID, CUM_START_DATE, CUST_RECORD_YEAR, and PURCHASE_ORDER_NUMBER.

Common Use Cases and Queries

The most frequent use of this table is CUM quantity reconciliation reporting. Supply chain and order management analysts query it to determine the accumulated shipped quantity for a customer item combination and to compare that against the incoming release or forecast authorization.

A typical join retrieves CUM keys alongside the customer item definition:

SELECT k.CUM_KEY_ID, k.CUM_START_DATE, k.CUST_RECORD_YEAR, k.CUM_QTY, ci.SEGMENT1
FROM RLM.RLM_CUST_ITEM_CUM_KEYS_ALL k, MTL_CUSTOMER_ITEMS ci
WHERE k.CUSTOMER_ITEM_ID = ci.CUSTOMER_ITEM_ID
AND k.ORG_ID = :p_org_id
AND k.INACTIVE_FLAG = 'N';

Because CUM adjustments are stored in the child table RLM_CUST_ITEM_CUM_ADJ_ALL, a rollup report joins parent to child on CUM_KEY_ID and sums the adjustment quantities to validate the parent CUM_QTY. Exception reporting typically filters on rows where CUM_QTY_TO_BE_ACCUMULATED is non-zero, or where LAST_CUM_QTY_UPDATE_DATE is older than the current release cycle, to surface stale accumulations. Audit queries use REQUEST_ID and PROGRAM_ID to trace which concurrent program recalculated a given CUM key.

Related Objects

  • RLM_CUST_ITEM_CUM_ADJ_ALL — the primary child table; individual CUM adjustments reference the parent through RLM_CUST_ITEM_CUM_ADJ_ALL.CUM_KEY_ID → RLM_CUST_ITEM_CUM_KEYS_ALL.CUM_KEY_ID.
  • MTL_CUSTOMER_ITEMS — referenced through CUSTOMER_ITEM_ID; provides the customer item number and item cross-reference.
  • MTL_SYSTEM_ITEMS_B — reached indirectly through the customer item to obtain internal item attributes.
  • HR_OPERATING_UNITS / ORG_ORGANIZATION_DEFINITIONS — resolve SHIP_FROM_ORG_ID and ORG_ID to organization names.
  • HZ_CUST_ACCOUNTS / HZ_LOCATIONS — resolve ship-to, bill-to, and intermediate ship-to address identifiers to customer locations.
  • RLM_CUM_MANAGEMENT_RULES / trading partner setup tables — define the CUM Management rules under which each key is established.
  • FND_CONCURRENT_REQUESTS — linked through REQUEST_ID for traceability of the batch process that last updated a CUM key.

Because the schema is dated and module-specific, integrators should confirm column-level semantics against the RLM 12.1.1 / 12.2.2 ETRM listing before building reporting or interface logic against this table.