Search Results rlm_hrz_schedule_lines_v




Overview
Explore in AI Chat

Overview

RLM_HRZ_SCHEDULE_LINES_V is an APPS-owned database view within the Oracle E-Business Suite Release Management (RLM) module. Its name reflects its purpose: it presents a horizontal, date-normalized projection of scheduling interface data. The view is classified as VALID and is available in both EBS 12.1.1 and 12.2.2 environments. In reporting and integration contexts, it serves as a consolidated read layer over schedule line records, aggregating item detail quantities by a stripped-down date key. Unlike transactional tables that store full timestamps, this view deliberately reduces START_DATE_TIME to a day-level granularity, making it suited for daily, period-based, or batch-level schedule reporting rather than time-of-day-sensitive processing.

Underlying Base Objects

The documented base object is a single referenced view: RLM_SCHEDULE_INTERFACE_LINES_V, itself owned by APPS. RLM_HRZ_SCHEDULE_LINES_V selects from this interface view and applies three transformations:

  • A date truncation expression — TO_DATE(TO_CHAR(START_DATE_TIME, 'DD-MON-RR')) — which discards the time component of the source timestamp.
  • A filter restricting rows to ITEM_DETAIL_TYPE IN ('0','1','2'), limiting output to specific item detail classifications.
  • A GROUP BY across all non-aggregated columns, with SUM(ITEM_DETAIL_QUANTITY) as the single aggregate.

The result set is ordered by the normalized START_DATE_TIME. Because both the projection and the filter are expressed over the interface view, the effective lineage passes through RLM_SCHEDULE_INTERFACE_LINES_V back to the underlying schedule interface data maintained by the Release Management module.

Key Columns

  • HEADER_ID — Identifier linking each line back to its schedule interface header.
  • CUSTOMER_ITEM_ID — Customer-facing item identifier for the scheduled line.
  • SHIP_TO_ADDRESS_ID and SHIP_FROM_ORG_ID — Destination address and source inventory organization.
  • CUST_SHIP_FROM_ORG_EXT, CUST_SHIP_TO_EXT, CUSTOMER_ITEM_EXT — External/attribute extension values for organization, address, and customer item respectively.
  • ITEM_DETAIL_TYPE and ITEM_DETAIL_SUBTYPE — Classification of the item detail; only types '0', '1', and '2' are returned.
  • START_DATE_TIME — The date-normalized scheduling start, converted to a day boundary and used as the ordering and grouping key.
  • ITEM_DETAIL_QUANTITY — Summed quantity of item detail across grouped rows.
  • QTY_TYPE_CODE and UOM_CODE — Quantity type and unit of measure governing the aggregated quantity.
  • ORIGIN_TABLE — Indicates the source table from which the interface line originated, useful for traceability.

Common Use Cases and Queries

Because the user search focused on start_date_time, the most common access patterns filter or order by that column. Typical scenarios include daily shipment or release schedule reporting, reconciliation against demand forecasts, and interfaces that need a summarized line population per day.

  • Retrieving schedule lines for a specific day:
    SELECT header_id, customer_item_id, item_detail_quantity
    FROM apps.rlm_hrz_schedule_lines_v
    WHERE start_date_time = TO_DATE('01-JAN-2024','DD-MON-RRRR');
  • Producing a date-ordered extract of aggregated quantities:
    SELECT start_date_time, sum(item_detail_quantity)
    FROM apps.rlm_hrz_schedule_lines_v
    GROUP BY start_date_time
    ORDER BY start_date_time;
  • Filtering by ship-from organization and customer item for planning analysis, joining HEADER_ID to the schedule interface header for contextual detail.

Note that quantities and groupings reflect the view's normalization rules, so consumers requiring exact timestamps or item detail types outside '0','1','2' must query the underlying RLM_SCHEDULE_INTERFACE_LINES_V directly.