Search Results rlm_item_method_type

Overview

RLM.RLM_SCHEDULE_LINES_ALL is the item-level detail table of the Oracle E-Business Suite Advanced Supply Chain Planning / Release Management (RLM) scheduling model. It stores item and item-detail-level information associated with customer planning, shipping, or production-sequenced schedules. For production sequence schedules, the row's item represents the feature rather than the configured assembly, with configuration context carried in the FBO_CONFIGURATION_KEY_1 through _5 columns.

Each row belongs to a parent schedule header (RLM_SCHEDULE_HEADERS via HEADER_ID) and captures dated demand, authorizations, and customer shipment or receipt information. The table is physically large — the documented 12.2.2 schema exposes 314 columns — reflecting the breadth of trading-partner schedule attributes (ship-to, bill-to, intermediate ship-to, carrier, packaging, and industry-specific flex attributes) that the RLM inbound/outbound schedule interfaces must accommodate.

The metadata classifies the object as standalone under a heuristic Data Vault model, meaning the mined foreign-key structure supports treating it as its own hub/satellite combination rather than a pure link. This is a modeling suggestion only; from a functional standpoint the table behaves as a transactional detail entity subordinate to the schedule header.

Key Information Stored

• LINE_ID — system-generated unique identifier and the primary key (SCHEDULE_LINE_ID_PK). This is the surrogate key; it is not a business key and should not be exposed to trading partners.
• HEADER_ID — foreign key to the parent schedule header in RLM_SCHEDULE_HEADERS, forming the master-detail relationship.
• INVENTORY_ITEM_ID — the internal inventory item (FK to MTL_SYSTEM_ITEMS) being scheduled.
• CUSTOMER_ITEM_ID / CUSTOMER_ITEM_EXT — the customer's item identifier and its external (as-received) representation. CUSTOMER_ITEM_ID carries a documented foreign key to MTL_CUSTOMER_ITEMS.
• ITEM_DETAIL_TYPE / ITEM_DETAIL_SUBTYPE — classify each detail row: 0 = Past Due Firm, 1 = Firm Demand, 2 = Forecast Demand, 3 = Authorization, 4 = Shipment/Receipt Info, 5 = Other. The subtype further qualifies the row (e.g., bucket type for demand, authorization type, cumulative vs. last for shipment/receipt). Both are validated against FND_LOOKUPS.
• DATE_TYPE_CODE / QTY_TYPE_CODE — indicate whether the start/end date represents ship, deliver, pull signal, or cumulative dates, and the corresponding quantity basis.
• START_DATE_TIME / END_DATE_TIME — the effective window for the demand, authorization, or shipment line.
• ITEM_DETAIL_QUANTITY / PRIMARY_QUANTITY / UOM_CODE / PRIMARY_UOM_CODE — scheduled quantities and their units of measure.
• SHIP_FROM_ORG_ID / SHIP_TO_ORG_ID / INTRMD_SHIP_TO_ID — the source, destination, and intermediate ship-to organizations, which form the basis of the RLM_SCHEDULE_LINE_N2 index.
• SUBLINE_CUST_ITEM_ID / SUBLINE_CUST_ITEM_EXT / SUBLINE_QUANTITY — component or sub-line information used for ATO/configured or sequenced content.
• PROCESS_STATUS — interface processing state of the line during inbound or outbound schedule handling.
• INTERFACE_LINE_ID — correlates the row back to the staging interface record; combined with HEADER_ID in index RLM_SCHEDULE_LINE_N1.
• ORG_ID — multi-org operating unit discriminator.
• CUST_PO_NUMBER / CUST_PO_LINE_NUM / CUST_PO_DATE — customer purchase-order references carried through the schedule.
• WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY) — standard audit and concurrency information.

LINE_ID is the documented unique index (RLM_SCHEDULE_LINE_U1, marked non-unique in the index metadata but paired with the primary key constraint). Business-key candidates are composite, typically HEADER_ID plus LINE_NUMBER plus INVENTORY_ITEM_ID plus ITEM_DETAIL_TYPE.

Common Use Cases and Queries

Typical usage centers on reviewing schedule demand by item, tracing interface errors, and reconciling transmitted schedules against accepted demand.

• Retrieving all firm and forecast demand for a header, filtered by detail type: SELECT line_id, inventory_item_id, item_detail_type, item_detail_quantity, start_date_time FROM rlm_schedule_lines_all WHERE header_id = :p_header AND item_detail_type IN ('1','2') ORDER BY inventory_item_id, start_date_time;
• Identifying unprocessed interface lines: SELECT header_id, interface_line_id, process_status FROM rlm_schedule_lines_all WHERE process_status = 'ERROR';
• Rolling up scheduled quantities by ship-to organization using the N2 index columns (SHIP_FROM_ORG_ID, SHIP_TO_ORG_ID, CUSTOMER_ITEM_ID) for shipping-schedule reports.
• Diagnosing authorization versus shipment detail by inspecting ITEM_DETAIL_SUBTYPE in conjunction with DATE_TYPE_CODE.
• Joining to MTL_CUSTOMER_ITEMS on CUSTOMER_ITEM_ID to map customer part numbers to internal items for cross-reference reporting.

Because of the 314-column width, queries should always project explicit columns rather than SELECT *.

Related Objects

• RLM.RLM_SCHEDULE_HEADERS — parent table; join on RLM_SCHEDULE_LINES_ALL.HEADER_ID = RLM_SCHEDULE_HEADERS.HEADER_ID.
• MTL_CUSTOMER_ITEMS — referenced via CUSTOMER_ITEM_ID for customer item cross-reference.
• MTL_SYSTEM_ITEMS_B — referenced via INVENTORY_ITEM_ID for item master attributes.
• FND_LOOKUPS — supplies validation values for ITEM_DETAIL_TYPE, ITEM_DETAIL_SUBTYPE, DATE_TYPE_CODE, and QTY_TYPE_CODE.
• RLM interface staging tables — correlated through INTERFACE_LINE_ID and the N1 index.
• RLM inbound/outbound schedule processing APIs and concurrent programs — consume PROCESS_STATUS and PROGRAM_ID/PROGRAM_APPLICATION_ID columns during schedule import and release.