Search Results so_line_details_interface




Overview
Explore in AI Chat

Overview

The SO_LINE_DETAILS_INTERFACE table is a core interface table within the Oracle E-Business Suite (EBS) Order Entry (OE) module, specifically for versions 12.1.1 and 12.2.2. It functions as a staging area for importing detailed schedule information for sales order lines. Its primary role is to facilitate the high-volume, programmatic creation and update of order schedules by serving as the target for data loads from external systems or legacy data conversions. Data populated into this table is subsequently processed by the Order Import concurrent program, which validates the records and creates corresponding transactional data in the base tables of the Order Management module. This interface-based approach ensures data integrity and leverages the application's business logic during the import process.

Key Information Stored

The table stores detailed scheduling attributes for imported sales order lines. While the provided metadata does not list specific columns, based on its description and standard EBS interface patterns, it typically holds data for line-level schedule details. This commonly includes fields such as the schedule quantity, request date, promise date, and ship-to location for each fulfillment line. Crucially, it contains reference columns to link each schedule detail record to its parent header and line in the interface tables. The documented foreign key relationship indicates the presence of an ORIGINAL_SYSTEM_REFERENCE column, which, along with a likely ORIGINAL_SYSTEM_LINE_REFERENCE, ties each schedule record to a specific line in the SO_LINES_INTERFACE_ALL table, maintaining the hierarchical data structure from header to line to schedule.

Common Use Cases and Queries

The principal use case is the batch import of sales order schedules via the Order Import program. A typical implementation involves an external system or data extraction script populating the SO_HEADERS_INTERFACE, SO_LINES_INTERFACE_ALL, and finally SO_LINE_DETAILS_INTERFACE tables in sequence. Common queries involve monitoring the interface for errors or processing status. For example, to identify schedule details that failed to import, one might join this table to the SO_LINES_INTERFACE_ALL table on the ORIGINAL_SYSTEM_REFERENCE and filter for records where the interface line's PROCESS_FLAG = 'ERROR'. Reporting on pending imports can be achieved by querying for records where the corresponding line's PROCESS_FLAG is 'PENDING' or 'PARTIAL', providing visibility into the data awaiting processing.

Related Objects

The table has a direct, documented foreign key relationship with the SO_LINES_INTERFACE_ALL table, which is its primary parent object. The relationship is defined as follows:

  • SO_LINE_DETAILS_INTERFACE references SO_LINES_INTERFACE_ALL via the column SO_LINE_DETAILS_INTERFACE.ORIGINAL_SYSTEM_REFERENCE. This key establishes the link from a schedule detail record to its associated sales order line in the interface.

This relationship is fundamental, as schedule details cannot be processed without a valid parent line in the interface. The table is also intrinsically linked to the Order Import concurrent program and, upon successful processing, its base transactional counterpart, likely the OE_ORDER_LINES table for schedules.