Results for “rlx_interface_details_v”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

RLX_INTERFACE_DETAILS_V is a reporting and integration view documented within the Oracle E-Business Suite Release Management (RLM) module. Its purpose is to expose release-line or supply/demand interface detail rows in a denormalized, consumer-friendly format suitable for downstream interfaces, concurrent program extracts, and ad hoc reporting. The view aggregates scheduling information from Oracle Advanced Supply Chain Planning data structures and presents it against a release plan header, producing one summarized row per plan and start date combination.

The view is listed as not implemented in the referencing database, which is a common notation in ETRM metadata indicating that the object exists in the documentation set and in certain product installations, but is not seeded or created in every environment. Verification of the object in a specific instance through ALL_VIEWS, DBA_VIEWS, or ALL_OBJECTS is therefore advisable before constructing dependent logic.

Underlying Base Objects

The view definition references two base tables: MSC_SUP_DEM_ENTRIES and MSC_PLANS. The join condition links MP.PLAN_ID to MSD.PLAN_ID and restricts results to MP.PLAN_TYPE = 4. In Oracle Advanced Supply Chain Planning, MSC_PLANS stores plan definitions, and PLAN_TYPE = 4 corresponds to a specific plan category relevant to release management processing. MSC_SUP_DEM_ENTRIES holds supply and demand entry records associated with those plans, including a PRODUCTION_SEQUENCE value and a START_DATE.

The view performs a GROUP BY on MP.PLAN_ID and MSD.START_DATE, collapsing multiple supply/demand entry rows into a single summarized row per plan and start date. No additional documented base objects, such as organization or item master tables, are referenced in the excerpt.

Key Columns

• HEADER_ID — Exposed as MP.PLAN_ID, serving as the header-level identifier for the plan and functioning as the foreign key linking to the plan record.
• START_DATE — The start date from MSC_SUP_DEM_ENTRIES, used as the second grouping dimension.
• STARTDATE_ATTVALUE — A literal value of 'REQUIRED', indicating that the start date attribute is mandatory for the interface context.
• PROD_SEQ_NUM_START — The minimum PRODUCTION_SEQUENCE value across the grouped rows, representing the lowest production sequence in the set.
• PROD_SEQ_NUM_END — The maximum PRODUCTION_SEQUENCE value, representing the highest production sequence in the set.

Common Use Cases and Queries

The view is typically used to feed release management interfaces that require summarized production sequence ranges per plan and start date, or to validate that required start date attributes are populated for interface processing. A representative query retrieves plan headers with their sequence ranges:

• SELECT HEADER_ID, START_DATE, STARTDATE_ATTVALUE, PROD_SEQ_NUM_START, PROD_SEQ_NUM_END FROM RLX_INTERFACE_DETAILS_V;
• Filter by plan: SELECT * FROM RLX_INTERFACE_DETAILS_V WHERE HEADER_ID = :plan_id;
• Filter by date range: SELECT * FROM RLX_INTERFACE_DETAILS_V WHERE START_DATE BETWEEN :from_date AND :to_date;

Because the view relies on MSC_SUP_DEM_ENTRIES and MSC_PLANS, query performance is governed by indexing on PLAN_ID and START_DATE in those base tables. The user search term "msc_sup_dem_entries" reflects this dependency, as the view is one of several RLM objects that surface supply and demand entry data for release planning purposes.