Search Results last_shipped_by
Overview
RLM_CUM_SHIP_DETAILS_V is an APPS-owned reporting and integration view in the Oracle E-Business Suite Release Management (RLM) module. It presents cumulative shipment detail records associated with customer item cumulative keys, joining shipment line information from Order Management with the cumulative key header and user audit data. The view is a denormalized projection intended for consumption by downstream Release Management processes, custom reports, and interface programs that require shipment-level quantities and destination/organization context keyed by a customer item cumulative key.
The view exposes both transactional shipment metrics — quantity, unit of measure, transaction date, and shipment number — and the full set of DFF attribute columns carried from the underlying order line. It is typically queried by planners, shipping analysts, and integration routines reconciling cumulative shipped quantities against customer item cumulative agreements.
Underlying Base Objects
The view is defined over three documented base objects:
- RLM_CUST_ITEM_CUM_KEYS (aliased CKEYS) — the cumulative key header, providing CUM_KEY_ID. This is the driving record for customer item cumulative tracking.
- OE_ORDER_LINES_ALL (aliased LINES) — the order/shipment line source. It supplies organizational context (SHIP_FROM_ORG_ID, SHIP_TO_ORG_ID, INVOICE_TO_ORG_ID, INTMED_SHIP_TO_ORG_ID), quantities, dates, DFF attributes, and the VEH_CUS_ITEM_CUM_KEY_ID foreign key linking back to the cumulative key.
- FND_USER (aliased FUSER) — joined on USER_ID = LINES.LAST_UPDATED_BY to resolve the user name of the last shipper.
The join condition is CKEYS.CUM_KEY_ID = LINES.VEH_CUS_ITEM_CUM_KEY_ID AND FUSER.USER_ID = LINES.LAST_UPDATED_BY, so only order lines carrying a cumulative key reference are returned. Because the view references OE_ORDER_LINES_ALL, it inherits the multi-org (operating unit) nature of that table; the *_ORG_ID columns identify the shipping, receiving, invoicing, and intermediate ship-to organizations.
Key Columns
- CUM_KEY_ID — identifier of the customer item cumulative key (from LINES.VEH_CUS_ITEM_CUM_KEY_ID).
- INTMED_SHIP_TO_ORG_ID — intermediate ship-to organization identifier, mapped directly from OE_ORDER_LINES. Callers searching on this column use it to filter shipments routed through a specific intermediate destination.
- SHIP_FROM_ORG_ID / SHIP_TO_ORG_ID / INVOICE_TO_ORG_ID — the originating warehouse, final ship-to, and invoice-to organizations.
- CUM_QUANTITY — cumulative quantity, sourced from INDUSTRY_ATTRIBUTE7 of the order line.
- TXN_DATE / TXN_QUANTITY / QUANTITY_UOM — actual shipment date, shipped quantity, and its unit of measure (SHIPPING_QUANTITY_UOM).
- SHIPMENT_NUMBER, LINE_ID, INVENTORY_ITEM_ID — shipment identifier, order line identifier, and inventory item.
- LAST_SHIPPED_BY — FND_USER.USER_NAME of the last updater.
- ATTRIBUTE1..15 — descriptive flexfield attributes passed through from the order line; ATTRIBUTE_CATEGORY and the TP_ATTRIBUTE* columns are exposed as NULL.
- Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE.
Common Use Cases and Queries
Typical uses include reconciling shipped quantities per cumulative key, reporting shipments by intermediate ship-to organization, and feeding interfaces that need audit and DFF context alongside shipment facts.
Query cumulative shipments for a specific cumulative key:
SELECT cum_key_id, shipment_number, txn_date, txn_quantity,
quantity_uom, ship_from_org_id, ship_to_org_id
FROM apps.rlm_cum_ship_details_v
WHERE cum_key_id = :p_cum_key_id
ORDER BY txn_date;
Query by intermediate ship-to organization (matching the user's search on intmed_ship_to_org_id):
SELECT cum_key_id, shipment_number, txn_date, txn_quantity,
ship_to_org_id, intmed_ship_to_org_id, last_shipped_by
FROM apps.rlm_cum_ship_details_v
WHERE intmed_ship_to_org_id = :p_intmed_ship_to_org_id;
Aggregate shipped quantity by cumulative key and item:
SELECT cum_key_id, inventory_item_id, quantity_uom,
SUM(txn_quantity) total_shipped, MAX(txn_date) last_ship_date
FROM apps.rlm_cum_ship_details_v
GROUP BY cum_key_id, inventory_item_id, quantity_uom;
-
View: RLM_CUM_SHIP_DETAILS_V
12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:RLM.RLM_CUM_SHIP_DETAILS_V, object_name:RLM_CUM_SHIP_DETAILS_V, status:VALID, product: RLM - Release Management , implementation_dba_data: APPS.RLM_CUM_SHIP_DETAILS_V ,
-
View: RLM_CUST_ITEM_CUM_DETAILS_V
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:RLM.RLM_CUST_ITEM_CUM_DETAILS_V, object_name:RLM_CUST_ITEM_CUM_DETAILS_V, status:VALID, product: RLM - Release Management , implementation_dba_data: APPS.RLM_CUST_ITEM_CUM_DETAILS_V ,
-
VIEW: APPS.RLM_CUST_ITEM_CUM_DETAILS_V
12.1.1
-
View: RLM_CUST_ITEM_CUM_DETAILS_V
12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:RLM.RLM_CUST_ITEM_CUM_DETAILS_V, object_name:RLM_CUST_ITEM_CUM_DETAILS_V, status:VALID, product: RLM - Release Management , implementation_dba_data: APPS.RLM_CUST_ITEM_CUM_DETAILS_V ,
-
VIEW: APPS.RLM_CUST_ITEM_CUM_DETAILS_V
12.2.2
-
View: RLM_CUM_SHIP_DETAILS_V
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:RLM.RLM_CUM_SHIP_DETAILS_V, object_name:RLM_CUM_SHIP_DETAILS_V, status:VALID, product: RLM - Release Management , implementation_dba_data: APPS.RLM_CUM_SHIP_DETAILS_V ,
-
VIEW: APPS.RLM_CUST_ITEM_CUM_DETAILS_V
12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:RLM.RLM_CUST_ITEM_CUM_DETAILS_V, object_name:RLM_CUST_ITEM_CUM_DETAILS_V, status:VALID,
-
VIEW: APPS.RLM_CUST_ITEM_CUM_DETAILS_V
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:RLM.RLM_CUST_ITEM_CUM_DETAILS_V, object_name:RLM_CUST_ITEM_CUM_DETAILS_V, status:VALID,
-
VIEW: APPS.RLM_CUM_SHIP_DETAILS_V
12.2.2
-
VIEW: APPS.RLM_CUM_SHIP_DETAILS_V
12.1.1
-
VIEW: APPS.RLM_CUM_SHIP_DETAILS_V
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:RLM.RLM_CUM_SHIP_DETAILS_V, object_name:RLM_CUM_SHIP_DETAILS_V, status:VALID,
-
VIEW: APPS.RLM_CUM_SHIP_DETAILS_V
12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:RLM.RLM_CUM_SHIP_DETAILS_V, object_name:RLM_CUM_SHIP_DETAILS_V, status:VALID,
-
eTRM - RLM Tables and Views
12.2.2
description: This table stores the details of Query Criteria for each of the Query in RLM_UI_QUERIES ,
-
eTRM - RLM Tables and Views
12.1.1
description: This table stores the details of Query Criteria for each of the Query in RLM_UI_QUERIES ,