Search Results rlm_lines_interface_u1

Overview

RLM.RLM_INTERFACE_LINES_ALL is the Release Management (RLM) Lines Interface table within Oracle E-Business Suite, present and valid in both 12.1.1 and 12.2.2. It stores the item and item-detail level information associated with customer planning, shipping, or production sequenced schedules. For production sequence schedules, the item recorded at this level represents the feature rather than the finished configuration. The table holds all details for scheduled items, including dated demand, authorizations, and customer shipment or receipt information, and it maintains a child relationship to RLM_INTERFACE_HEADERS.

Functionally, the object serves as a staging interface that captures inbound schedule data, typically received through EDI or bulk load processes, before it is validated and consumed by downstream release management logic. The table is owned by the RLM schema, carries FND design data reference RLM.RLM_INTERFACE_LINES_ALL, has public scope, active lifecycle, and stores its data in the APPS_TS_TX_DATA tablespace with a PCT Free of 10. The documented physical schema contains 340 columns. From a heuristic Data Vault modeling perspective, this table is best classified as a standalone structure; its mined foreign-key footprint is minimal, and its principal relationships are expressed through surrogate keys rather than a dense set of hub or link references.

Key Information Stored

The table's documented surrogate primary key is LINE_ID, defined by the index LINE_ID_PK. Competing business-key candidates are captured by the unique index RLM_LINES_INTERFACE_U1, which spans LINE_ID and HEADER_ID, confirming that a line is uniquely identified within the context of its parent header. The most significant columns include:

• LINE_ID — sequence-generated unique identifier and primary key.
• HEADER_ID — sequence-generated unique identifier and foreign key to RLM_INTERFACE_HEADERS_ALL, linking each line to its parent schedule.
• CUSTOMER_ITEM_ID — foreign key to MTL_CUSTOMER_ITEMS, identifying the customer-defined item.
• INVENTORY_ITEM_ID — the internal inventory item reference for the scheduled line.
• ITEM_DETAIL_TYPE / ITEM_DETAIL_SUBTYPE — classify the granularity and nature of the item detail being interfaced.
• SCHEDULE_DATE / REQUEST_DATE / DATE_TYPE_CODE — the dated demand details that drive scheduling.
• AUTHORIZATION_CODE_EXT — captures the customer authorization associated with the line.
• CUST_PRODUCTION_SEQ_NUM / CUST_PRODUCTION_SEQ_NUM_BEG / CUST_PRODUCTION_SEQ_NUM_END — production sequence positioning.
• AGREEMENT_ID — foreign key to RA_AGREEMENTS for the agreement behind the customer purchase order.
• CUST_PO_NUMBER, CUST_PO_LINE_NUM, CUST_PO_DATE, CUST_PO_RELEASE_NUM — customer purchase order identity and release data.
• ORDER_HEADER_ID — links the interface line to its originating order header.
• ORG_ID — the operating unit context for the transaction.
• CUSTOMER_ITEM_EXT, SUBLINE_CUST_ITEM_EXT, CUST_MODEL_NUMBER_EXT — customer-facing item identifiers supplied on the interface feed.
• PROCESS_STATUS — tracks the processing state of the interface record.

Common Use Cases and Queries

Typical usage centers on validating and staging inbound schedule data. A common reporting query retrieves lines for a header and joins to the parent interface table by HEADER_ID, using the unique index RLM_LINES_INTERFACE_U1 to isolate a specific line when both LINE_ID and HEADER_ID are known. Standard supporting access paths are RLM_INTERFACE_LINES_N1 (HEADER_ID, CUSTOMER_ITEM_ID, ITEM_DETAIL_SUBTYPE), RLM_INTERFACE_LINES_N2 (HEADER_ID, INVENTORY_ITEM_ID), and RLM_INTERFACE_LINES_N3 (HEADER_ID, CUSTOMER_ITEM_EXT).

• Extracting lines in a given PROCESS_STATUS to monitor interface processing progress.
• Reconciling customer purchase order numbers against received schedule lines.
• Reporting demand by SCHEDULE_DATE for capacity and commit planning.
• Joining CUSTOMER_ITEM_ID to MTL_CUSTOMER_ITEMS to resolve customer item descriptions.
• Auditing production sequence boundaries via CUST_PRODUCTION_SEQ_NUM_BEG and CUST_PRODUCTION_SEQ_NUM_END.

Related Objects

The most significant dependencies on RLM_INTERFACE_LINES_ALL are:

• RLM.RLM_INTERFACE_HEADERS_ALL — parent table, joined on HEADER_ID.
• MTL_CUSTOMER_ITEMS — referenced via CUSTOMER_ITEM_ID.
• RA_AGREEMENTS — referenced via AGREEMENT_ID.
• RLM_SCHEDULE / RLM_SCHEDULE_LINES — consumed by processing logic using the RLM_SCHEDULE business entity category.
• FND_LOOKUPS — validation of ATO_DATA_TYPE against LOOKUP_TYPE RLM_ITEM_METHOD_TYPE.
• MTL_SYSTEM_ITEMS_B — resolved through INVENTORY_ITEM_ID for internal item detail.