Search Results subline_quantity

Overview

The RLM_SCHEDULE_INTERFACE_LINES_V view is an Oracle E-Business Suite Release Management (RLM) database object, owned by the APPS schema and maintained in VALID status. It exposes line-level scheduling interface data used within the Release Management module, which governs order-based and forecast-based shipping schedules flowing into Oracle Order Management and related supply chain processes. The view presents a denormalized, reporting-friendly projection of the schedule interface line records, including item identifiers, quantity type indicators, date and UOM qualifiers, ship-to and ship-from address attributes, customer purchase order references, routing and transit time details, and label information. Rather than functioning as a transactional entry surface, it serves as a read interface for downstream integration and inquiry — allowing concurrent programs, reports, and external systems to retrieve staged scheduling lines in a consistent, resolved shape across both 12.1.1 and 12.2.2 environments.

Underlying Base Objects

Per the documented ETRM metadata, the view is defined over the following APPS synonyms: RLM_INTERFACE_HEADERS, RLM_INTERFACE_HEADERS_ALL, RLM_INTERFACE_LINES, RLM_SCHEDULE_HEADERS, and RLM_SCHEDULE_LINES_ALL. The view text itself selects predominantly from alias A — the interface line entity — joined conceptually to header and schedule structures. RLM_INTERFACE_LINES supplies the primary staging rows that carry the inbound schedule line content; RLM_INTERFACE_HEADERS and RLM_INTERFACE_HEADERS_ALL provide the parent header context (organization, customer, and processing group), while RLM_SCHEDULE_HEADERS and RLM_SCHEDULE_LINES_ALL represent the destination schedule header and line tables into which the interface records are ultimately applied. The view therefore sits at the boundary between the interface/staging layer and the live scheduling tables, which is the architectural reason it is commonly referenced by validation and import-concurrency logic.

Key Columns

• Header and line keys: HEADER_ID, LINE_ID, LINE_NUMBER — parent/child identification and ordering of the interface records.
• Item identification: INVENTORY_ITEM_ID, CUSTOMER_ITEM_ID, CUSTOMER_ITEM_EXT, SCHEDULE_ITEM_NUM, SUPPLIER_ITEM_EXT — internal and customer-facing item references.
• Quantity and UOM: QTY_TYPE_CODE, UOM_CODE, PRIMARY_UOM_CODE — the quantity dimension and unit of measure semantics of the schedule line.
• Dates: START_DATE_TIME and the derived START_DATE (truncated via TO_DATE(TO_CHAR(...,'DD-MON-RR'))), plus DATE_TYPE_CODE and CUST_PO_DATE.
• Ship-to/ship-from: SHIP_TO_ORG_ID, SHIP_TO_ADDRESS_1_EXT through SHIP_TO_ADDRESS_4_EXT, SHIP_FROM_ORG_ID, and address, city, province, postal, and country attributes for both parties.
• Commercial references: CUST_PO_NUMBER, CUST_PO_LINE_NUM, CUST_PO_RELEASE_NUM, CUST_PRODUCTION_SEQ_NUM.
• Logistics attributes: ROUTING_DESC_EXT, ROUTING_SEQ_CODE_EXT, TRANSIT_TIME_EXT, TRANSIT_TIME_QUAL_EXT, SHIP_DEL_RULE_NAME, SHIP_DEL_PATTERN_EXT, SHIP_DEL_TIME_CODE_EXT.
• Label and ATO detail: SHIP_LABEL_INFO_LINE_1 through SHIP_LABEL_INFO_LINE_10, and ATO_DATA_TYPE, ITEM_DETAIL_TYPE, ITEM_DETAIL_SUBTYPE.

Common Use Cases and Queries

Typical uses include diagnosing records that are pending import into the live schedule tables, validating that required shipping and address attributes are populated before submission of the schedule import concurrent program, and building reconciliation reports comparing interface content to RLM_SCHEDULE_LINES_ALL. A representative query retrieves unprocessed interface lines for a header:

SELECT line_id, line_number, inventory_item_id, qty_type_code,
       uom_code, start_date, ship_to_org_id, cust_po_number
FROM   apps.rlm_schedule_interface_lines_v
WHERE  header_id = :p_header_id
ORDER  BY line_number;

Because the view already resolves header context and the header references used by validation logic, it is preferable to querying the staging table directly when header-level attributes are needed. All access should observe standard APPS schema privileges and any organization-level security applied by the calling responsibility.