Results for “so_line_details_interface”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

SO_LINE_DETAILS_INTERFACE is an Order Entry (OE) interface table in Oracle E-Business Suite, owned by the OE schema. It is classified as VALID and serves as the staging area for imported order line schedule details. When order lines are loaded into EBS through the Order Import process, the schedule-level detail records — those describing demand quantities, requested schedule dates, lot and subinventory assignments, and warehouse fulfillment information for each line — are first written to this interface table. The Order Import concurrent program subsequently validates and processes these records, moving them into the base order management tables.

The table holds 43 documented columns and carries descriptive/transactional attributes rather than a primary key of its own. The ETRM metadata notes that SO_LINE_DETAILS_INTERFACE has a foreign key relationship to SO_LINES_INTERFACE_ALL through two columns: ORIGINAL_SYSTEM_REFERENCE and ORIGINAL_SYSTEM_LINE_REFERENCE. The heuristic Data Vault classification derived from the FK structure is satellite-leaning, suggesting this object behaves as an attribute-bearing dependant of a parent interface entity rather than an independent hub or link.

Key Information Stored

The most significant columns fall into several functional categories:

• Order reference and linkage: ORIGINAL_SYSTEM_REFERENCE and ORIGINAL_SYSTEM_LINE_REFERENCE tie each schedule detail back to its parent line in SO_LINES_INTERFACE_ALL, while ORDER_SOURCE_ID identifies the source system originating the record.
• Item and demand attributes: INVENTORY_ITEM_ID, COMPONENT_SEQUENCE_ID, REVISION, and DEMAND_CLASS_CODE describe the item being ordered and its associated demand characteristics.
• Scheduling data: QUANTITY, SCHEDULE_DATE, SCHEDULE_LEVEL_CODE, and SCHEDULE_STATUS_CODE define how much is to be fulfilled and when, and at what scheduling granularity.
• Fulfillment/lot attributes: LOT_NUMBER, SUBINVENTORY, WAREHOUSE_ID, and CUSTOMER_REQUESTED_LOT_FLAG specify inventory sourcing and lot preference.
• Revenue and status control: REQUIRED_FOR_REVENUE, INTERFACE_STATUS, and ERROR_FLAG govern validation outcomes and downstream processing.
• Audit and concurrency columns: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, PROGRAM_APPLICATION_ID, PROGRAM_ID, REQUEST_ID, and PROGRAM_UPDATE_DATE. A CONTEXT plus ATTRIBUTE1 through ATTRIBUTE15 provide flexfield support.

No surrogate primary key is documented; the ORIGINAL_SYSTEM_REFERENCE / ORIGINAL_SYSTEM_LINE_REFERENCE pair (plus schedule identifiers) functions as the business-key candidate linking to the parent interface table.

Common Use Cases and Queries

Typical scenarios include troubleshooting failed Order Import runs, validating schedule data before submission, and reconciling imported quantities against source systems. A common diagnostic pattern joins this table to its parent interface table to isolate errors:

SELECT d.ORIGINAL_SYSTEM_REFERENCE, d.ORIGINAL_SYSTEM_LINE_REFERENCE, d.INVENTORY_ITEM_ID, d.QUANTITY, d.SCHEDULE_DATE, d.ERROR_FLAG
FROM OE.SO_LINE_DETAILS_INTERFACE d
WHERE d.ERROR_FLAG = 'Y';

Reporting queries frequently filter on INTERFACE_STATUS or SCHEDULE_STATUS_CODE to identify records awaiting processing. Joins to SO_LINES_INTERFACE_ALL on ORIGINAL_SYSTEM_REFERENCE and ORIGINAL_SYSTEM_LINE_REFERENCE are effectively mandatory when the parent line context is required, since the detail table has no standalone identity.

Related Objects

• SO_LINES_INTERFACE_ALL — the documented parent interface table; joined via ORIGINAL_SYSTEM_REFERENCE and ORIGINAL_SYSTEM_LINE_REFERENCE.
• OE_ORDER_LINES_ALL / OE_ORDER_HEADERS_ALL — the base order management tables into which processed schedule details ultimately land.
• Order Import concurrent program (Order Import Manager / OE Order Import) — the process that reads, validates, and consumes these interface rows.
• MTL_SYSTEM_ITEMS_B — referenced via INVENTORY_ITEM_ID for item validation.
• MTL_SECONDARY_INVENTORIES — referenced via SUBINVENTORY for inventory sourcing validation.
• HR_ALL_ORGANIZATION_UNITS / MTL_PARAMETERS — contextualized by WAREHOUSE_ID for warehouse resolution.
• OE_ORDER_SOURCES — referenced via ORDER_SOURCE_ID to identify the originating order source.