Search Results rlm_schedule_line_cum_v




Overview
Explore in AI Chat

Overview

RLM_SCHEDULE_LINE_CUM_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite Release Management (RLM). Its status is documented as VALID in both 12.1.1 and 12.2.2. The view consolidates scheduling and cumulative (CUM) quantity information for customer item schedules, presenting a flattened, reporting-friendly projection of the schedule line data held in the transactional base tables.

In the RLM model, schedule headers and schedule lines store the raw demand and shipping instructions transmitted by customers, while customer item cumulative keys (held in RLM_CUST_ITEM_CUM_KEYS) define the business rules that determine how cumulative quantities are grouped and reset. This view joins those datasets so that cumulative start dates, cumulative keys, schedule references, and detail quantities can be presented together. Because the logic is encapsulated in the view definition rather than exposed in each report, it provides a consistent interpretation of cumulative demand across RLM reporting and integration surfaces.

Underlying Base Objects

The ETRM metadata documents three referenced base objects, all exposed through APPS synonyms:

  • RLM_CUST_ITEM_CUM_KEYS — supplies CUM_KEY_ID and CUM_START_DATE, the grouping keys used to associate schedule detail with a cumulative period.
  • RLM_SCHEDULE_HEADERS_ALL — supplies the header-level schedule reference and schedule generation date used to qualify active CUM windows.
  • RLM_SCHEDULE_LINES_ALL — supplies the schedule line detail (item subtype, date type, quantities, UOM, ship-from/ship-to organizations, customer item). The view references this table twice, aliased as A and D, to distinguish demand/detail rows (ITEM_DETAIL_TYPE = '3') from CUM rows (ITEM_DETAIL_TYPE = '4', ITEM_DETAIL_SUBTYPE = 'CUM').

The view text also includes a correlated subquery that selects MAX(ITEM_DETAIL_QUANTITY) across the same joined set, ensuring that the reported cumulative quantity reflects the highest qualifying detail quantity for the CUM key.

Key Columns

  • CUM_START_DATE — the cumulative period start date, derived from the schedule line start date.
  • CUM_KEY_ID — identifier of the applicable cumulative key from RLM_CUST_ITEM_CUM_KEYS.
  • SCHEDULE_REFERENCE_NUM — the customer-facing schedule reference from the header.
  • ITEM_DETAIL_SUBTYPE — indicates the nature of the line; 'CUM' identifies cumulative records.
  • DATE_TYPE_CODE, START_DATE_TIME, END_DATE_TIME — the scheduling window for the detail line.
  • QTY_TYPE_CODE, ITEM_DETAIL_QUANTITY, UOM_CODE — quantity semantics, the quantity value, and unit of measure.
  • SHIP_FROM_ORG_ID, SHIP_TO_ORG_ID, CUSTOMER_ITEM_ID — the organizational and item context used to match CUM keys to schedule lines.

The join predicates apply NVL defaults across ship-from, ship-to, bill-to, intermediate ship-to, customer PO number, and industry attribute (customer record year) so that CUM keys defined with partial qualifiers still match their corresponding schedule lines.

Common Use Cases and Queries

Typical uses include cumulative demand reporting, reconciliation of transmitted CUM values against internal schedule lines, and feeding downstream integration or planning processes. A representative query is:

  • SELECT CUM_KEY_ID, SCHEDULE_REFERENCE_NUM, CUM_START_DATE, ITEM_DETAIL_QUANTITY, UOM_CODE FROM APPS.RLM_SCHEDULE_LINE_CUM_V WHERE CUSTOMER_ITEM_ID = :customer_item_id ORDER BY CUM_START_DATE;
  • Filter by SHIP_FROM_ORG_ID and SHIP_TO_ORG_ID to isolate a single customer ship-to relationship when reconciling cumulative balances.
  • Join to item master or customer item views using CUSTOMER_ITEM_ID to enrich cumulative quantities with descriptive attributes.

Because the view is owned by APPS, reporting responsibilities and integrations should query it as APPS.RLM_SCHEDULE_LINE_CUM_V and avoid assumptions about row-level security or org-specific partitioning.