Results for “rlm_schedule_order_v”
4 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
RLM_SCHEDULE_ORDER_V is a reporting and integration view within the Oracle Release Management (RLM) module. It presents the intersection between scheduling agreements managed through Release Management and the underlying order lines stored in Oracle Order Management. Specifically, the view exposes order lines that were created from a scheduling source document, as identified by the SOURCE_DOCUMENT_TYPE_ID value of 5 in the OE_ORDER_LINES table. In Oracle EBS 12.1.1 and 12.2.2, this view serves as a lightweight access layer that allows Release Management logic, concurrent programs, and custom reports to retrieve schedule-relevant order line data without querying the base order line table directly.
The view performs column aliasing rather than data transformation, mapping order line identifiers into schedule-oriented column names. This makes it convenient for RLM reporting where the semantic meaning of the data is expressed in scheduling terms rather than order management terms.
According to the ETRM metadata, this view is listed as "Not implemented in this database," meaning its presence and availability may vary depending on whether the RLM module and related patch levels are installed. In practical EBS 12.1.1 and 12.2.2 environments where RLM is licensed and deployed, the view is expected to be present and queryable.
Underlying Base Objects
The view is defined over a single base table: OE_ORDER_LINES. No additional base objects are documented in the ETRM metadata. The view definition selects a subset of columns from OE_ORDER_LINES and applies a filter condition: WHERE SOURCE_DOCUMENT_TYPE_ID = 5. This predicate restricts the result set to order lines that originated from a scheduling agreement source document, which is the defining characteristic of the data exposed by this view.
Because the view draws exclusively from OE_ORDER_LINES, all data integrity, validation, and relationships inherent to the Order Management line entity apply. There is no aggregation, join, or union in the view text, so it is a straightforward projection with a restrictive filter.
Key Columns
- LINE_ID — The primary identifier of the order line in OE_ORDER_LINES. This is the natural key for each row returned by the view.
- SCHEDULE_LINE_ID — An alias for SOURCE_DOCUMENT_LINE_ID. It identifies the corresponding line on the scheduling agreement or schedule document from which the order line was derived.
- SCHEDULE_HEADER_ID — An alias for SOURCE_DOCUMENT_ID. This column is the primary reference linking the order line back to its originating schedule header. This is the column most commonly targeted by searches for "source_document_id" in RLM reporting contexts.
- ORDER_HEADER_ID — An alias for HEADER_ID. It identifies the order header to which the line belongs.
- LAST_UPDATE_DATE, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard Oracle EBS audit columns tracking creation and modification metadata.
- REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — Concurrent program context columns indicating which concurrent request and program last updated the row.
Common Use Cases and Queries
This view is typically used to reconcile scheduling agreements with the order lines they generated, to report on schedule-driven demand, or to trace an order line back to its originating schedule document ID.
A common query retrieves all schedule-linked order lines and their originating schedule headers:
SELECT schedule_line_id, schedule_header_id, order_header_id, creation_date FROM rlm_schedule_order_v WHERE schedule_header_id = :p_schedule_header_id;
Another frequent pattern joins the view to OE_ORDER_HEADERS_ALL or OE_ORDER_LINES_ALL to enrich the schedule data with order details. Because the view is filtered to SOURCE_DOCUMENT_TYPE_ID = 5, users searching for "source_document_id" in the context of Release Management should understand that SCHEDULE_HEADER_ID is the exposed representation of that identifier. This view therefore acts as the canonical RLM-facing access point for order lines linked to scheduling source documents in Oracle EBS 12.1.1 and 12.2.2.
-
View: RLM_SCHEDULE_ORDER_V 12.1.1
Not implemented in this database·Explore RLM module →
-
View: RLM_SCHEDULE_ORDER_V 12.2.2
Not implemented in this database·Explore RLM module →
-
12.1.1 FND Design Data 12.1.1
-
12.2.2 FND Design Data 12.2.2