Search Results sched_horizon_end_date




Overview
Explore in AI Chat

Overview

RLX_INTERFACE_HEADERS_V is a Release Management (RLM) view within Oracle E-Business Suite, defined as a header-level extraction view for interface processing. It consolidates supplier scheduling data drawn from Advanced Supply Chain Planning (ASCP) plan definitions and cross-reference records, and projects that data into a normalized header structure intended for downstream interface consumption. The view presents a distinct set of planning and scheduling attributes — including schedule reference numbers, scheduling horizons, customer and supplier identity fields, and attribute-value placeholders — and is therefore best understood as a data transformation layer rather than a transactional entity. In the ETRM metadata for 12.2.2, the object is documented but explicitly noted as "Not implemented in this database," meaning it exists as a shipped definition rather than a populated runtime object in the reference environment. The presence of literal constants in the SELECT list (such as 'SCHSTART', 'SCHEND', and 'Y') indicates that the view was designed to satisfy a fixed interface format rather than to serve as a general-purpose reporting source.

Underlying Base Objects

The view is defined over five base objects, all of which participate in an inner join through the WHERE clause. MSC_PLANS supplies the plan header, including PLAN_ID, COMPILE_DESIGNATOR, PLAN_START_DATE, CUTOFF_DATE, PLAN_TYPE, and SR_INSTANCE_ID. MSC_SUP_DEM_ENTRIES provides the supplier and publisher organization identifiers and links to the plan through both PLAN_ID and SR_INSTANCE_ID. HZ_PARTIES resolves the publisher organization to a party name for the customer name column. ECT_XREF_DTL supplies the supplier name through XREF_EXT_VALUE and enforces an outbound direction filter (DIRECTION = 'OUT'). POM_OPERATOR_PARAMETERS is referenced in the FROM clause; the documented join conditions do not constrain it, so it functions as a supporting reference in the original definition. Critically, the plan type is restricted to 4, which limits the view to a specific class of planning records and explains the narrow, interface-specific projection.

Key Columns

Common Use Cases and Queries

Typical usage centers on supplier scheduling interfaces that publish plan horizons to external trading partners. Because SCHED_HORIZON_END_DATE reflects the plan cutoff date, it is frequently used to bound the window of a published schedule or to validate that a schedule was generated within an acceptable period. A representative query follows:

SELECT header_id,
       schedule_reference_num,
       sched_horizon_start_date,
       sched_horizon_end_date,
       customer_name,
       supplier_name
  FROM rlx_interface_headers_v
 WHERE sched_horizon_end_date >= SYSDATE - 30;

Analysts also use the view to reconcile customer and supplier site pairings emitted by the interface, or to confirm that acknowledgement flags and document attribute values align with expected interface conventions. Because the object is documented as not implemented, queries should be validated against the actual deployment before being relied upon in production reporting.