Search Results schedule_source

Overview

RLM_SCHEDULE_INTERFACE_HDR_V is a view in the APPS schema belonging to the Release Management (RLM) product within Oracle E-Business Suite. It exposes schedule header records that have not yet been moved into the interface staging area, presenting them in the format expected by the downstream schedule interface. The view is intended to feed interface processing and reporting logic within the Release Management scheduling flow, allowing header-level schedule data to be consumed by EDI or other external integration points before it is formally staged in RLM_INTERFACE_HEADERS. Because it filters on the absence of a corresponding interface header record, the view effectively represents the "pending" schedule headers awaiting interface generation.

Underlying Base Objects

The view is defined primarily over RLM_SCHEDULE_HEADERS, which supplies the core schedule header columns. The WHERE clause uses a NOT EXISTS subquery against RLM_INTERFACE_HEADERS (documented with its _ALL variant; both appear as synonyms in the referenced objects list), ensuring only schedule headers lacking an interface header record are returned. The literal 'SCHEDULE' is projected as ORIGIN_TABLE, and INTERFACE_HEADER_ID is selected from the interface header context. Referenced base objects include RLM_INTERFACE_HEADERS (synonym), RLM_INTERFACE_HEADERS_ALL (synonym), and RLM_SCHEDULE_HEADERS (synonym).

Key Columns

• HEADER_ID, CUSTOMER_ID, SCHEDULE_TYPE: Core schedule identifier, customer, and schedule classification.
• SCHED_HORIZON_START_DATE / END_DATE: Bounds of the schedule horizon.
• SCHEDULE_SOURCE, SCHEDULE_PURPOSE, SCHEDULE_REFERENCE_NUM: Contextual schedule attributes; extended variants such as SCHEDULE_TYPE_EXT and SCHEDULE_PURPOSE_EXT carry interface-specific values.
• CUSTOMER_EXT and CUST_* columns: External customer name and address components (address lines, city, state, province, country, postal code, county).
• ECE_* columns: Trading partner location and translator attributes, including ECE_PRIMARY_ADDRESS_ID, ECE_TP_LOCATION_CODE_EXT, and ECE_TP_TRANSLATOR_CODE.
• EDI_CONTROL_NUM_1 through _3, EDI_TEST_INDICATOR: EDI control and test indicators for transmission handling.
• HEADER_CONTACT_CODE/VALUE, HEADER_REF_CODE/VALUE, HEADER_NOTE_TEXT: Contact, reference, and note details.
• PROCESS_STATUS, REQUEST_ID, PROGRAM_ID: Concurrent request and processing context.
• ATTRIBUTE_CATEGORY, ATTRIBUTE1-15, TP_ATTRIBUTE1-15, TP_ATTRIBUTE_CATEGORY: Descriptive flexfield and trading-partner flexfield segments.
• LAST_UPDATE_DATE, CREATED_BY, and audit columns: Standard WHO columns.
• ORIGIN_TABLE, INTERFACE_HEADER_ID: Derived identifiers used during interface staging.

Common Use Cases and Queries

The view is commonly used to identify schedule headers that have not yet been interfaced, to report external address and EDI attributes, and to validate records before interface generation. A typical query lists pending headers with customer and horizon details:

SELECT header_id, customer_id, schedule_type, sched_horizon_start_date, sched_horizon_end_date, schedule_source, schedule_purpose FROM apps.rlm_schedule_interface_hdr_v WHERE process_status = <status> ORDER BY sched_horizon_start_date;

Another common pattern joins the view to external customer attributes for EDI reporting, selecting CUSTOMER_EXT, EDI_CONTROL_NUM_1, and ECE_TP_TRANSLATOR_CODE. Because the view already excludes headers with existing interface records, it supports reconciliation queries that confirm the completeness of schedule interface generation within Release Management.