Search Results cust_ship_to_ext




Overview
Explore in AI Chat

Overview

The APPS.RLM_HRZ_SCHEDULE_LINES_V view is a reporting and integration artifact within the Oracle E-Business Suite Release Management (RLM) module, which supports high-volume, demand-driven supply chain and fulfillment scheduling. In EBS 12.1.1 and 12.2.2, this view acts as a consolidated projection of schedule interface data, presenting item-level schedule lines at a summarized grain suitable for downstream consumption by planning, order management, and external integration processes. It reads from RLM_SCHEDULE_INTERFACE_LINES_V and restricts the result set to schedule lines whose ITEM_DETAIL_TYPE is one of the values '0', '1', or '2', thereby excluding line records that do not represent qualifying item detail categories. The view aggregates quantities and normalizes date values, producing a stable, deduplicated dataset that reporting layers and interfaces can query without re-implementing the grouping logic on the interface view itself.

Underlying Base Objects

The view is defined exclusively over a single documented base object: the view RLM_SCHEDULE_INTERFACE_LINES_V, owned by APPS. It contains no references to base tables directly. This dependency means the lineage of RLM_HRZ_SCHEDULE_LINES_V is one level removed from the physical interface tables and inherits whatever filters, joins, and security predicates are applied within RLM_SCHEDULE_INTERFACE_LINES_V. The parent view is itself an interface layer, so RLM_HRZ_SCHEDULE_LINES_V should be treated as a read-only, derived reporting structure rather than a transactional entity. Because it aggregates over the interface view, the row-count and grain of the parent differ from those of this view; a single schedule header may collapse into fewer rows here depending on the grouping keys.

Key Columns

  • HEADER_ID — Identifier of the schedule header to which the line belongs, a primary grouping key.
  • CUSTOMER_ITEM_ID, CUSTOMER_ITEM_EXT — Internal and external identifiers for the customer-facing item.
  • ITEM_DETAIL_TYPE, ITEM_DETAIL_SUBTYPE — Classification of the item detail line. The search term item_detail_subtype corresponds directly to this column, which participates in the GROUP BY and refines the granularity of each summarized line. Both columns are exposed verbatim from the interface view.
  • SHIP_TO_ADDRESS_ID, SHIP_FROM_ORG_ID, CUST_SHIP_FROM_ORG_EXT, CUST_SHIP_TO_EXT — Ship-to and ship-from identifiers in internal and external forms.
  • START_DATE_TIME — The schedule line date, truncated to day precision via TO_DATE(TO_CHAR(...,'DD-MM-RRRR'),'DD-MM-RRRR'); this conversion supports day-level aggregation and drives the ORDER BY clause.
  • ITEM_DETAIL_QUANTITY — The SUM of item detail quantities across rows sharing the same grouping keys.
  • QTY_TYPE_CODE, UOM_CODE — Quantity type and unit of measure associated with the summed quantity.
  • ORIGIN_TABLE, ORG_ID — Source table indicator and the operating unit / organization context, which is also a grouping key.

Common Use Cases and Queries

Typical consumers use this view to obtain daily aggregated schedule quantities by item, addresses, and organization. A representative query filters on the searched column to isolate a specific detail subtype, for example:

  • SELECT header_id, customer_item_ext, item_detail_type, item_detail_subtype, start_date_time, SUM(item_detail_quantity) FROM apps.rlm_hrz_schedule_lines_v WHERE item_detail_subtype = :subtype GROUP BY header_id, customer_item_ext, item_detail_type, item_detail_subtype, start_date_time;
  • Feeding planning or fulfillment dashboards with day-bucketed demand quantities per ship-to organization.
  • Reconciling interface-extracted schedule lines against upstream planning data by HEADER_ID and START_DATE_TIME.
  • Building extracts for external systems that require normalized, day-truncated schedule dates and summed quantities.

Because the view is pre-aggregated, additional summation logic is only required when consumers regroup by columns outside the documented GROUP BY keys.