Search Results rlm_schedule_headers_u1

Overview

RLM.RLM_SCHEDULE_HEADERS_ALL is the primary header-level table in Oracle E-Business Suite Release Management (RLM), the module responsible for processing customer demand schedules received through EDI or entered manually. The table records one row per demand schedule header, capturing the customer, ship-to information, schedule type and purpose, horizon dates, and the raw EDI envelope segments (N1, N3, N4, REF, PER, and similar) that accompanied the transaction. The Release Management Demand Processor reads and writes this table to maintain a current picture of demand schedule headers as inbound 830, 862, 866, DELFOR, and MANUAL transactions are consumed.

Physically the table resides in the APPS_TS_TX_DATA tablespace with PCTFREE 10, while its indexes are held in APPS_TS_TX_IDX. The documented schema carries 152 columns, reflecting the broad payload of an EDI planning schedule. From a Data Vault modeling perspective, the heuristic classification derived from the foreign-key structure is standalone, meaning it does not behave as a conventional hub, link, or satellite. This is a modeling suggestion only; the table is best treated as an operational staging and master-header store rather than a normalized dimensional entity.

Key Information Stored

The surrogate primary key is HEADER_ID, enforced by RLM_SCHEDULE_HEADERS_U1 (NORMAL, UNIQUE, columns: HEADER_ID). Note that a second constraint, SCHEDULE_HEADER_ID_PK, is documented on the same column. HEADER_ID is the only documented unique index; there is no separate composite business key, although SCHEDULE_REFERENCE_NUM plus CUSTOMER_ID effectively identifies a schedule in business terms and is indexed non-uniquely through RLM_SCHEDULE_HEADERS_N1 and RLM_SCHEDULE_HEADERS_N2.

• HEADER_ID — schedule unique identifier; primary key and unique index column.
• CUSTOMER_ID — ship-to customer identifier, foreign key to RA_CUSTOMERS; indexed via RLM_SCHEDULE_HEADERS_N2.
• SCHEDULE_REFERENCE_NUM — customer-assigned schedule or release number; indexed via RLM_SCHEDULE_HEADERS_N1.
• SCHEDULE_TYPE — Planning, Shipping, or Sequenced; validated against FND_LOOKUPS.LOOKUP_TYPE = RLM_SCHEDULE_TYPE.
• SCHEDULE_PURPOSE — Original, Replace, Cancellation; validated against RLM_SCHEDULE_PURPOSE.
• SCHED_HORIZON_START_DATE / SCHED_HORIZON_END_DATE — the horizon window covered by the schedule.
• SCHEDULE_SOURCE — transaction source such as 830, 862, 866, DELFOR, or MANUAL.
• ORG_ID — operating unit, enabling multi-org filtering.
• ECE_TP_LOCATION_CODE_EXT and CUST_NAME_EXT — trading-partner location and customer name; both carry dedicated non-unique indexes (N3, N4).
• PROCESS_STATUS, INTERFACE_HEADER_ID, REQUEST_ID — processing and traceability columns linking the row to the concurrent request and interface that created it.
• Standard WHO columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY.
• Descriptive flexfield columns ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15.

Common Use Cases and Queries

The most frequent reporting need is locating a schedule by its customer reference or by ship-to. The indexed columns support these access paths efficiently.

• Retrieve a schedule header by reference number: SELECT header_id, customer_id, schedule_type, schedule_reference_num FROM rlm.rlm_schedule_headers_all WHERE schedule_reference_num = :p_ref;
• List active schedules for a customer within a horizon window: SELECT header_id, sched_horizon_start_date, sched_horizon_end_date FROM rlm.rlm_schedule_headers_all WHERE customer_id = :p_cust AND schedule_type = 'Planning' ORDER BY sched_horizon_start_date;
• Monitor inbound EDI processing by source and status: SELECT schedule_source, process_status, COUNT(*) FROM rlm.rlm_schedule_headers_all GROUP BY schedule_source, process_status;
• Troubleshoot failed loads using REQUEST_ID and INTERFACE_HEADER_ID to trace back to the concurrent program that populated the row.
• Reporting over trading-partner locations using the ECE_TP_LOCATION_CODE_EXT index (N3) or customer name using CUST_NAME_EXT (N4).

Because the table is the header parent, most analytical queries join it to the corresponding detail lines table to obtain individual schedule line quantities and dates.

Related Objects

• RLM.RLM_SCHEDULE_LINES_ALL — detail lines joined to the header on HEADER_ID; the principal child of this table.
• RA_CUSTOMERS — referenced through CUSTOMER_ID for ship-to customer information.
• FND_LOOKUPS — validation source for SCHEDULE_TYPE (RLM_SCHEDULE_TYPE) and SCHEDULE_PURPOSE (RLM_SCHEDULE_PURPOSE).
• Release Management Demand Processor concurrent programs — populate and maintain rows in this table from inbound EDI and manual entry.
• ECE trading partner and location tables — referenced through ECE_TP_LOCATION_CODE_EXT, ECE_TP_TRANSLATOR_CODE, and ECE_PRIMARY_ADDRESS_ID.
• RLM_SCHEDULE_HEADERS_U1 and companion indexes N1–N4 — the supporting access structures in APPS_TS_TX_IDX.