Search Results header_id_pk

Overview

RLM_INTERFACE_HEADERS_ALL is a Release Management (RLM) interface table in the Oracle E-Business Suite, owned by the RLM schema. It serves as the staging and header-level repository for release schedule information, capturing demand transactions delivered by the EDI Gateway from external trading partners. In Oracle EBS 12.1.1 and 12.2.2, this table holds 152 documented columns and stores schedule-level details together with customer, supplier, and trading-partner information required for downstream release management processing.

The table is populated as part of the EDI inbound flow, where demand signals such as planning schedules and release schedules are received and staged prior to validation and consumption by RLM schedule processing concurrent programs. From a dimensional modeling perspective, the metadata classifies this object heuristically as a standalone structure — neither a classic hub, link, nor satellite — since its foreign key footprint is minimal, with only a single documented reference to AR_CHARGE_SCHEDULE_HDRS. This classification should be treated as a modeling suggestion rather than a prescribed Data Vault construct.

Key Information Stored

Each row represents a single schedule header. The documented surrogate primary key is HEADER_ID, enforced by the unique index HEADER_ID_PK and the business-key candidate index RLM_HEADERS_INTERFACE_U1. The most significant columns include:

• HEADER_ID — surrogate primary key for the interface header record.
• SCHEDULE_HEADER_ID — foreign key linking to AR_CHARGE_SCHEDULE_HDRS, tying the interface row to a charge schedule header.
• SCHEDULE_TYPE / SCHEDULE_TYPE_EXT — internal and external schedule type codes (e.g., planning, shipping, or release).
• SCHEDULE_PURPOSE / SCHEDULE_PURPOSE_EXT — internal and external schedule purpose indicators.
• SCHEDULE_SOURCE, SCHEDULE_REFERENCE_NUM, SCHED_GENERATION_DATE — origin, external reference, and generation timestamp.
• SCHED_HORIZON_START_DATE and SCHED_HORIZON_END_DATE — the planning horizon of the schedule.
• CUSTOMER_ID, CUSTOMER_EXT, CUST_NAME_EXT — customer identification and descriptive data.
• SUPPLIER_ID, SUPPLIER_NAME_EXT, ONE_TIME_SUPPLIER_FLAG_EXT — supplier/trading-partner details.
• PROCESS_STATUS — current processing state of the interface row.
• ORG_ID — operating unit context for multi-org security.
• EDI_CONTROL_NUM_1/2/3, EDI_TEST_INDICATOR — EDI envelope and test-mode markers.
• BUCKET_START_DATE / BUCKET_END_DATE, FLEX_BUCKET_CODE — bucket-level scheduling attributes.
• TP_ATTRIBUTE_CATEGORY and TP_ATTRIBUTE1..15 — trading-partner descriptive flexfield segments.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1..15 — standard descriptive flexfield segments.
• Standard WHO columns: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, plus REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID.

Common Use Cases and Queries

Typical use cases include monitoring inbound EDI demand and validating staged release schedules before RLM processing. A common query examines the processing backlog by status and operating unit:

• SELECT HEADER_ID, CUSTOMER_ID, SCHEDULE_TYPE, PROCESS_STATUS, ORG_ID FROM RLM_INTERFACE_HEADERS_ALL WHERE PROCESS_STATUS = 'PENDING';

To reconcile interface rows against their originating charge schedule header, join on SCHEDULE_HEADER_ID:

• SELECT h.HEADER_ID, h.SCHEDULE_HEADER_ID, a.* FROM RLM_INTERFACE_HEADERS_ALL h JOIN AR_CHARGE_SCHEDULE_HDRS a ON h.SCHEDULE_HEADER_ID = a.SCHEDULE_HEADER_ID;

Reporting scenarios frequently extract schedule horizons and customer/supplier combinations for on-time delivery or forecast analysis, filtering by SCHED_GENERATION_DATE, SCHED_HORIZON_START_DATE, and SCHED_HORIZON_END_DATE. Because the table carries both CUSTOMER_ID and SUPPLIER_ID, it also supports trading-partner activity reporting across demand and supply relationships.

Related Objects

The most significant objects associated with this table include:

• AR_CHARGE_SCHEDULE_HDRS — referenced via SCHEDULE_HEADER_ID; the charge schedule header behind each interface row.
• RLM_INTERFACE_LINES_ALL — companion line-level interface table (typical header/line pairing in RLM staging).
• RLM_SCHEDULE_HEADERS — destination schedule header holding processed schedule data.
• RLM_SCHEDULE_LINES — schedule line detail consumed from the line interface.
• HZ_CUST_ACCOUNTS — customer master referenced by CUSTOMER_ID for validation and enrichment.
• PO_VENDORS / HZ_PARTIES — supplier master referenced by SUPPLIER_ID.
• HR_ALL_OPERATING_UNITS — operating unit behind ORG_ID.
• EDI Gateway inbound/outbound programs — the process interface that populates this staging table.