Search Results row_level
Overview
SO_SERVICE_DETAILS is a read-only database view owned by the APPS schema in Oracle E-Business Suite, classified under the Order Entry (OE) product family. It is deployed and valid in both release 12.1.1 and 12.2.2. The view exists to flatten and consolidate service-oriented order line information that is otherwise scattered across order management and field service tables. Specifically, it reconciles three distinct populations onto a single result set: standard order lines linked to inventory items, service detail records attached to ordered lines, and customer product revisions associated with a service-enabled order line. This consolidation makes the view a convenient reporting and integration surface for service contracts, depot repair, and installed-base maintenance reporting where order lines must be tied to customer products and their revisions.
Because the view performs a three-way UNION ALL, each branch of the query contributes rows at a distinct ROW_LEVEL. This design allows a consumer to treat all service-related lines uniformly while still distinguishing the origin of each row through the ROW_LEVEL and ID_COLUMN columns.
Underlying Base Objects
The documented base objects referenced by the view are SO_LINES (synonym to the order line view), SO_LINE_SERVICE_DETAILS, CS_SYSTEMS, CS_CUSTOMER_PRODUCTS, CS_CP_REVISIONS, CS_CUSTOMER_PRODUCT_STATUSES, MTL_SYSTEM_ITEMS, and the FND_PROFILE package. The package CSICUMPI_PUB is also listed among referenced objects, reflecting the installed-base integration dependencies of the underlying customer product structures.
The first UNION branch joins SO_LINES to MTL_SYSTEM_ITEMS, resolving the inventory item description and constraining the organization to the value returned by FND_PROFILE.VALUE('SO_ORGANIZATION_ID'). The second branch joins SO_LINES to SO_LINE_SERVICE_DETAILS, then outer-joins CS_SYSTEMS and CS_CUSTOMER_PRODUCTS, and restricts output to lines having more than one service detail row via a HAVING COUNT(*) > 1 subquery. The third branch handles lines where NVL(L.S25,18) equals 14, joining CS_CP_REVISIONS, CS_CUSTOMER_PRODUCTS, CS_CUSTOMER_PRODUCT_STATUSES, and CS_SYSTEMS to expose revision-level detail. This branching explains the dependency on the CS_CUSTOMER_PRODUCTS object referenced in the user's search.
Key Columns
- LINE_ID — Identifier of the originating order line in SO_LINES.
- OPTION_LINE_NUMBER — Line number when a parent line exists, otherwise blank; useful for option/configuration context.
- PARENT_LINE_ID — Parent line for configured or option items.
- COMPONENT_CODE — Component indicator associated with the line.
- INVENTORY_ITEM_ID — Inventory item on the order line.
- QUANTITY — Ordered quantity in the first branch, customer product quantity in the second, and revision quantity in the third.
- DESCRIPTION — Item description, or a concatenation of system name, serial number, and revision for service product rows.
- ROW_LEVEL — Discriminator indicating the source branch (0, 4, or 5).
- ID_COLUMN — Primary key of the row's origin object (line, service detail, or CP revision).
Common Use Cases and Queries
Typical usage includes reporting service order lines against installed customer products, validating that service-enabled lines carry the expected serialized revisions, and building integration extracts for depot repair or field service systems. The following query lists service detail rows at the customer product level for a given order line set:
SELECT line_id, option_line_number, component_code, inventory_item_id, quantity, description, row_level, id_column FROM apps.so_service_details WHERE row_level IN (4,5) ORDER BY line_id, row_level;
To resolve customer product context for service lines, join the view back to CS_CUSTOMER_PRODUCTS on the CP revision relationship, or filter on ROW_LEVEL = 4 to isolate service detail records enriched with system name and serial number. Because the view aggregates multiple branches, always include ROW_LEVEL in predicates and output to avoid ambiguous interpretation of QUANTITY and DESCRIPTION.
-
View: SO_SERVICE_DETAILS
12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:OE.SO_SERVICE_DETAILS, object_name:SO_SERVICE_DETAILS, status:VALID, product: OE - Order Entry , implementation_dba_data: APPS.SO_SERVICE_DETAILS ,
-
View: SO_SCHEDULE_DETAILS
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:OE.SO_SCHEDULE_DETAILS, object_name:SO_SCHEDULE_DETAILS, status:VALID, product: OE - Order Entry , implementation_dba_data: APPS.SO_SCHEDULE_DETAILS ,
-
View: SO_SCHEDULE_DETAILS
12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:OE.SO_SCHEDULE_DETAILS, object_name:SO_SCHEDULE_DETAILS, status:VALID, product: OE - Order Entry , implementation_dba_data: APPS.SO_SCHEDULE_DETAILS ,
-
View: SO_SERVICE_DETAILS
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:OE.SO_SERVICE_DETAILS, object_name:SO_SERVICE_DETAILS, status:VALID, product: OE - Order Entry , implementation_dba_data: APPS.SO_SERVICE_DETAILS ,