Search Results so_line_service_details




Overview
Explore in AI Chat

Overview

SO_LINE_SERVICE_DETAILS is an Oracle Order Entry (OE) schema table that stores installation details associated with order lines. In Oracle EBS 12.1.1 and 12.2.2, this table supports service and subscription-oriented order flows, capturing the technical and customer-product context required when an order line represents an installation, service activation, or equipment placement. The table is owned by the OE schema and is documented as VALID in the ETRM repository, with 47 columns in the 12.2.2 physical schema.

The primary key is SO_LINE_SERVICE_DETAILS_PK, defined on the LINE_SERVICE_DETAIL_ID column. A unique index, SO_LINE_SERVICE_DETAILS_U1, also exists on LINE_SERVICE_DETAIL_ID. The heuristic Data Vault classification derived from the foreign-key structure is "standalone," suggesting the table functions as an independent entity rather than a strict hub, link, or satellite in a Data Vault sense. From a modeling perspective, it is best treated as a detail or child table whose parent context is supplied through the LINE_ID column rather than through enforced foreign keys.

Key Information Stored

The most significant columns include:

Many columns carry a corresponding SVRID column, which stores the surrogate identifier used by the service reference data model for the associated value.

Common Use Cases and Queries

Typical uses include installation reporting, service activation tracking, and return-date monitoring. A common query pattern joins the table to the order line entity using LINE_ID:

  • Retrieve all installation details for an order line: SELECT * FROM OE.SO_LINE_SERVICE_DETAILS WHERE LINE_ID = :line_id;
  • List details by customer product: SELECT LINE_SERVICE_DETAIL_ID, LINE_ID, CUSTOMER_PRODUCT_ID FROM OE.SO_LINE_SERVICE_DETAILS WHERE CUSTOMER_PRODUCT_ID = :cp_id;
  • Identify items approaching return-by dates: SELECT LINE_SERVICE_DETAIL_ID, LINE_ID, NEW_CP_RETURN_BY_DATE FROM OE.SO_LINE_SERVICE_DETAILS WHERE NEW_CP_RETURN_BY_DATE BETWEEN :start_date AND :end_date;
  • Trace copied details: SELECT * FROM OE.SO_LINE_SERVICE_DETAILS WHERE SOURCE_LINE_SERVICE_DETAIL_ID = :source_id;

These patterns support operational dashboards and reconciliation between order lines and their installation records.

Related Objects

The following objects are most relevant based on the documented structure and standard OE relationships:

  • OE.ORDER_LINES_ALL — joined via LINE_ID; the parent order line for each installation detail.
  • OE.SO_LINE_SERVICE_DETAILS_PK and SO_LINE_SERVICE_DETAILS_U1 — the primary key constraint and unique index on LINE_SERVICE_DETAIL_ID.
  • OE.ORDER_HEADERS_ALL — reached through the order line for header-level reporting.
  • OE.TRANSACTION_TYPES — referenced by TRANSACTION_TYPE_ID.
  • OE.CUSTOMER_PRODUCTS — referenced by CUSTOMER_PRODUCT_ID.
  • AR.HZ_CUST_SITE_USES_ALL — referenced by INSTALLATION_SITE_USE_ID.
  • OE.ORDER_MANAGEMENT and the Order Management public APIs — the primary application interfaces that create and maintain installation detail records.

Because the table is classified as standalone, joins are best driven through LINE_ID rather than relying on enforced foreign keys.