Search Results scheduled_shipment_date




Overview
Explore in AI Chat

Overview

In Oracle E-Business Suite 12.1.1 and 12.2.2, SO_LINES_INTERFACE (owner: APPS, status: VALID, product: OE – Order Entry) is a view that surfaces the staging area used by Order Management to import order lines into Oracle Order Entry. The view is the externally visible face of the underlying interface table SO_LINES_INTERFACE_ALL (referenced through an APPS synonym), and it exposes the full set of columns that Order Import reads when converting staged records into live sales order lines. It is used both by the Order Import concurrent program and by custom reporting/extraction routines that need to inspect or stage order-line data before or after import.

Underlying Base Objects

The documented ETRM metadata lists a single referenced base object: SO_LINES_INTERFACE_ALL, accessed via a synonym in the APPS schema. The view is therefore a projection over the multi-org interface table, exposing the columns defined by that table. Because SO_LINES_INTERFACE_ALL is an _ALL table, it carries ORG_ID among its columns, which is included explicitly in the view text. This multi-org design allows a single staging table/view to serve every operating unit, and the ORG_ID column is the mechanism that lets Order Import and custom queries filter records by business unit. In ETRM 12.2.2 the view metadata reports the synonym as the sole dependency, but at runtime the synonym resolves to the interface table in the OE schema.

Key Columns

The view text reveals a broad set of columns grouped by functional area. Notable identifiers include OPERATION_CODE, COMMITMENT_ID, and the reference columns LINK_TO_LINE_REF, PARENT_LINE_REF, SHIPMENT_SCHEDULE_LINE_REF, and SERVICE_PARENT_LINE_REF, which establish hierarchical and related-line relationships during import. Pricing and financial columns include LIST_PRICE, SELLING_PRICE, LIST_PERCENT, SELLING_PERCENT, PERCENT_BASE_PRICE, PRICING_DATE, PRICE_LIST_ID, and the pricing attributes PRICING_ATTRIBUTE9 through PRICING_ATTRIBUTE15, together with PRICING_CONTEXT and PRICING_METHOD_CODE. Shipping and logistics columns cover SHIP_TO_CUSTOMER, SHIP_TO_CUSTOMER_ID, SHIP_TO_SITE_USE_ID, SHIP_TO_CONTACT_ID, SHIP_METHOD_CODE, SHIPMENT_PRIORITY_CODE, SHIP_SET_NUMBER, WAREHOUSE_ID, and DEMAND_CLASS_CODE. Ordered and shipped quantities appear as ORDERED_QUANTITY and SHIPPED_QUANTITY. Two sets of twenty flexfield segments — INVENTORY_ITEM_SEGMENT1–20 and SERVICED_SEGMENT1–20 — are exposed to allow flexible item and serviced-item keying, alongside INVENTORY_ITEM_ID and SERVICED_ITEM_ID. Date columns include LATEST_ACCEPTABLE_DATE, PROMISE_DATE, DATE_REQUESTED_CURRENT, and SCHEDULED_SHIPMENT_DATE. Terms, tax, and service columns close out the list with TERMS_ID, TAX_CODE, INVOICING_RULE, and the service flags SERVICE_COTERMINATE_FLAG and SERVICE_PERIOD_CONVERSION_RATE.

Note: the column customer_dock_code is not present in the documented view text. In Oracle Order Management, customer dock/planning-related attributes are typically carried on the order-line DFF or on header-level interface fields rather than in this view; users searching for customer_dock_code should verify it against SO_LINES_INTERFACE_ALL and any attribute columns exposed there, or against the corresponding order-line base table.

Common Use Cases and Queries

  • Validating staged order lines before running Order Import, checking that required identifiers such as SHIP_TO_CUSTOMER_ID, INVENTORY_ITEM_ID, and ORDERED_QUANTITY are populated.
  • Auditing failed imports by extracting lines where OPERATION_CODE and reference columns indicate incomplete relationships.
  • Reconciling interfaced pricing and quantities against source systems.
  • Reporting on multi-org data by grouping on ORG_ID.

Sample query:

SELECT ORG_ID, INVENTORY_ITEM_ID, SHIP_TO_CUSTOMER_ID,
       ORDERED_QUANTITY, SELLING_PRICE, PROMISE_DATE
FROM   APPS.SO_LINES_INTERFACE
WHERE  ORG_ID = :p_org_id;