Search Results txn_quantity




Overview
Explore in AI Chat

Overview

RLM_CUST_ITEM_CUM_DETAILS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite Release Management (RLM). It presents a consolidated, transaction-level ledger of customer item cumulative (CUM) activity, combining cumulative adjustments entered manually with shipment-driven cumulative movements. The view is defined as a UNION of two logically distinct transaction streams and classifies each row through a literal discriminator column, TXN_TYPE. This column is the object's defining feature: it takes the value ADJUSTMENT for cumulative adjustment records and SHIPMENT for customer item shipment lines, allowing downstream reports and integrations to consume a single homogeneous result set while still distinguishing the source and nature of each movement.

The view exists in both 12.1.1 and 12.2.2; in 12.2.2 the documented base objects are unchanged, confirming stability of the interface across the upgrade boundary. Its principal role is to support cumulative quantity tracking against customer items — quantities shipped to, adjusted for, or consumed at a customer location — which is essential in environments operating customer-owned or consignment inventory, vendor-managed inventory arrangements, and cumulative-based billing agreements where amounts invoiced depend on net cumulative movement rather than discrete orders.

Underlying Base Objects

The view is defined over the following documented objects:

  • RLM_CUST_ITEM_CUM_ADJ_ALL — cumulative adjustment records; supplies the ADJUSTMENT branch of the UNION.
  • RLM_CUST_ITEM_CUM_KEYS — the cumulative key master, joining organizations to customer item cumulative definitions.
  • OE_ORDER_LINES_ALL — order lines providing shipment activity, shipment numbers, and shipped quantities for the SHIPMENT branch.
  • ORG_ORGANIZATION_DEFINITIONS — resolves ship-from organization identifiers to organization codes and names.
  • HZ_CUST_SITE_USES_ALL — supplies ship-to, deliver-to, and bill-to site locations.
  • FND_USER — resolves the last updated (adjustment) or last shipped user to a user name.
  • HR_GENERAL / HR_SECURITY — packaged functions used for organization security filtering.

In the ADJUSTMENT branch, the view joins organization definitions and cumulative keys, then links to adjustment rows through CUM_KEY_ID, and finally to FND_USER. In the SHIPMENT branch, order lines are keyed to the cumulative key, with organization, site use, and user lookups applied for descriptive context.

Key Columns

Common Use Cases and Queries

Typical uses include cumulative balance reconciliation, adjustment audit reporting, shipment-versus-adjustment variance analysis, and feeds into billing or customer-portal extracts. A common pattern filters on TXN_TYPE to isolate a single stream:

  • Adjustment audit: SELECT cum_key_id, txn_date, txn_quantity, adjustment_reason, last_adjusted_by FROM rlm_cust_item_cum_details_v WHERE txn_type = 'ADJUSTMENT' ORDER BY txn_date DESC;
  • Shipment history for a cumulative key: SELECT shipment_number, txn_date, txn_quantity, quantity_uom, ship_to FROM rlm_cust_item_cum_details_v WHERE txn_type = 'SHIPMENT' AND cum_key_id = :cum_key_id;
  • Net cumulative movement: SELECT cum_key_id, txn_type, SUM(txn_quantity) FROM rlm_cust_item_cum_details_v GROUP BY cum_key_id, txn_type;

Because the view performs organization security filtering through HR_SECURITY, query results are naturally restricted to the organizations accessible to the operating user, making it suitable for concurrent-program-based extracts and BI Publisher reports without additional security predicates.