Search Results rlm_schedule_lines_all

Overview

RLM_SCHEDULE_LINES_ALL is the line-level transaction table within the Oracle E-Business Suite Release Management (RLM) module. It stores item and item-detail level information associated with customer planning, shipping, or production sequenced schedules. For production sequence schedules, the item stored in this table represents the feature rather than the finished configuration, which allows the application to model sequenced build requirements at a granular attribute level.

The table is owned by the RLM schema and is documented as VALID in both Oracle EBS 12.1.1 and 12.2.2. Its physical definition is substantial, comprising 314 documented columns. The primary key is defined by the SCHEDULE_LINE_ID_PK constraint, enforced on the LINE_ID column. From a dimensional modeling perspective, the heuristic data-vault classification for this object is standalone, meaning it does not function as a classic hub, link, or satellite in the mined foreign-key structure. The only documented foreign-key relationship is from CUSTOMER_ITEM_ID to MTL_CUSTOMER_ITEMS, so the table is best treated as a self-contained transaction detail entity rather than a component of a normalized hub-and-satellite model.

Key Information Stored

The table blends scheduling keys, item identifiers, quantity and UOM information, address data, and a large set of trading-partner extension attributes. The most significant columns include:

• LINE_ID — the surrogate primary key (SCHEDULE_LINE_ID_PK) that uniquely identifies each schedule line record.
• HEADER_ID — the parent schedule header reference linking the line to its controlling schedule.
• ORDER_HEADER_ID and LINE_NUMBER — the associated order header and the human-readable line sequence.
• INVENTORY_ITEM_ID — the internal inventory item identifier; for production sequence schedules this represents the feature.
• CUSTOMER_ITEM_ID — the foreign key to MTL_CUSTOMER_ITEMS, linking to the customer's own item definition.
• CUSTOMER_ITEM_EXT and CUSTOMER_ITEM_REVISION — the customer-facing item number and revision.
• PRIMARY_QUANTITY, PRIMARY_UOM_CODE, ITEM_DETAIL_QUANTITY, SUBLINE_QUANTITY, SUBLINE_UOM_CODE — scheduled and detail-level quantities with their units of measure.
• START_DATE_TIME and END_DATE_TIME — the effective window for the scheduled line.
• PROCESS_STATUS and LINE_SOURCE — processing state and the origin of the line record.
• CUST_PRODUCTION_SEQ_NUM, along with CUST_PRODUCTION_SEQ_NUM_BEG and CUST_PRODUCTION_SEQ_NUM_END — production sequence numbering used for sequenced schedules.
• ORG_ID — the operating unit that owns the line, central to multi-org reporting.
• CUST_PO_NUMBER, CUST_PO_LINE_NUM, and CUST_PO_DATE — the customer purchase order reference used in demand matching.

Business-key candidates are not separately documented as unique indexes beyond the LINE_ID surrogate, so LINE_ID should be treated as the definitive unique identifier. The remaining columns function as descriptive and qualifying attributes.

Common Use Cases and Queries

Typical reporting and integration scenarios involve extracting scheduled line detail for a given schedule header, joining to inventory and customer item master tables, and aggregating quantities by item, operating unit, or date window.

• Schedule line detail report for a specific header:

SELECT line_id, line_number, inventory_item_id, customer_item_id,
       primary_quantity, primary_uom_code, process_status
FROM   rlm.rlm_schedule_lines_all
WHERE  header_id = :p_header_id
ORDER  BY line_number;

• Open production sequence lines by operating unit:

SELECT cust_production_seq_num, inventory_item_id,
       cust_production_seq_num_beg, cust_production_seq_num_end
FROM   rlm.rlm_schedule_lines_all
WHERE  org_id = :p_org_id
AND    process_status = :p_status;

• Customer item reconciliation, joining to the documented foreign key:

SELECT l.line_id, l.customer_item_id, m.customer_item_number
FROM   rlm.rlm_schedule_lines_all l,
       mtl_customer_items m
WHERE  l.customer_item_id = m.customer_item_id;

These patterns support demand visibility, ship-schedule generation, and discrepancy analysis between scheduled quantities and released orders.

Related Objects

The documented relationship data identifies MTL_CUSTOMER_ITEMS as the table referenced by the CUSTOMER_ITEM_ID foreign key. Beyond that, the most significant related objects based on the column semantics are:

• MTL_CUSTOMER_ITEMS — joined via CUSTOMER_ITEM_ID; supplies the customer item cross-reference.
• RLM_SCHEDULE_HEADERS_ALL — the parent header joined via HEADER_ID.
• OE_ORDER_HEADERS_ALL — joined via ORDER_HEADER_ID for associated sales order context.
• MTL_SYSTEM_ITEMS_B — joined via INVENTORY_ITEM_ID for item master attributes.
• HR_ALL_ORGANIZATION_UNITS — joined via ORG_ID for operating unit resolution.
• MTL_CUSTOMER_ITEM_RELATIONS — supporting customer-item-to-inventory-item mapping.
• RLM_INTERFACE_LINES — linked conceptually through INTERFACE_LINE_ID for inbound processing.

Because the documented FK structure is limited to a single reference, integration design should rely on the semantic join keys above rather than assuming additional enforced constraints.