Search Results customer_product_quantity

Overview

SO_LINE_SERVICE_DETAILS_V is a reporting view in the Oracle E-Business Suite Order Entry (OE) module. It exposes service detail records associated with order lines, presenting denormalized service, system, transaction type, customer product, and contact information in a single queryable object. The view is defined over the SO_LINE_SERVICE_DETAILS base table (aliased LSD) and joins to several reference and master tables to resolve codes into descriptive values.

Because the view resolves foreign-key identifiers into human-readable names — transaction type, system name, customer product type, system type, contact names, and customer address details — it is well suited for reporting, extract, and integration scenarios where consumers require descriptive service-line context rather than raw identifiers. The user search term "system_type" maps directly to the SYSTEM_TYPE column exposed by this view, which is populated from the SYSTEM_TYPE_CODE lookup and resolved through a lookup join.

Underlying Base Objects

The view text reveals the following referenced objects:

• SO_LINE_SERVICE_DETAILS (LSD) — the primary base table holding line service detail rows.
• Transaction Type (TT) — resolves TRANSACTION_TYPE_ID to a name and revision flag.
• CS Lookups (CSLK, CSLK1) — resolve customer product type and system type codes to their meaning text.
• System table (SYS) — resolves SYSTEM_ID to SYSTEM_NAME.
• Contact table (CON, CON1) — resolves technical and service contact identifiers to formatted names.
• RA_CUSTOMERS / RA_SITE_USE / RA_ADDRESSES (RACST, RASIT, RAADR) — supply customer name, number, site, and concatenated address fields.

The view is documented as "Not implemented in this database," meaning it may not be seeded by default in every instance and may require validation against the target environment's source tables.

Key Columns

• LINE_SERVICE_DETAIL_ID — primary key of the service detail record.
• LINE_ID — links the detail to the parent order line.
• SYSTEM_TYPE — the descriptive meaning of SYSTEM_TYPE_CODE, resolved via lookup; this is the column most relevant to a search on "system_type."
• SYSTEM_TYPE_CODE — the stored code value.
• SYSTEM_NAME — resolved system name from the System table.
• TRANSACTION_TYPE and REVISION_FLAG — descriptive transaction classification.
• CUSTOMER_PRODUCT_TYPE and CP_QUANTITY — product classification and quantity.
• TECHNICAL_CONTACT and SERVICE_CONTACT_NAME — formatted contact names.
• CUSTOMER_NAME / CUSTOMER_NUMBER / LOCATION / ADDRESS fields — concatenated customer and site descriptors.
• ATTRIBUTE1–15 and CONTEXT — descriptive flexfield columns for extensibility.

Common Use Cases and Queries

Typical uses include service-line reporting, order-line enrichment for downstream systems, and auditing of system and transaction type assignments.

Example query filtering on system type:

SELECT line_id, transaction_type, system_name, system_type,
customer_product_type, cp_quantity, technical_contact, service_contact_name
FROM so_line_service_details_v
WHERE system_type = :p_system_type;

Example by order line:

SELECT line_service_detail_id, line_id, transaction_type, system_name, system_type
FROM so_line_service_details_v
WHERE line_id = :p_line_id;

Because the view performs multiple outer joins to resolve codes, queries benefit from filtering on indexed columns of the base table, such as LINE_ID, and from avoiding unfiltered full scans where the customer and address joins return large result sets.