Search Results service_duration




Overview
Explore in AI Chat

Overview

AS_DOSSIER_SERVTOTALS_V is a reporting view in the Oracle E-Business Suite Sales Foundation (AS) product family. It exposes order history service totals, aggregating the value of service-type order lines by order header. Its purpose is to provide a summarized "total service value" figure per order so that order history and dossier-style reporting can present the aggregate worth of services attached to an order without requiring the report author to reconstruct the calculation from individual lines.

The view is read-only and purely analytical; it holds no persistent data and is defined entirely by a single SELECT statement over transactional order lines. Because the order history service total is derived at query time, the view always reflects the current state of the underlying order line data at the moment it is queried.

Underlying Base Objects

The only documented base object referenced by AS_DOSSIER_SERVTOTALS_V is the SO_LINES table, which stores individual order lines including pricing, quantities, line type, and item type attributes. According to the ETRM metadata, no additional base objects are documented, and the view is not implemented as a stored object in the reference database.

The view filters SO_LINES to lines meeting three conditions: the line type code must be either 'DETAIL' or 'REGULAR', the item type code must be 'SERVICE', and the rows are grouped by HEADER_ID. In effect, it isolates service lines belonging to standard detail or regular order lines and rolls their computed value up to the order header level.

Key Columns

  • HEADER_ID — The order header identifier. This is the grouping key and the join column to the order header entity (for example OE_ORDER_HEADERS_ALL).
  • TOTAL_SERVICE_VALUE — The aggregated service value for the header, computed as the sum over qualifying service lines of SELLING_PRICE multiplied by SERVICE_DURATION multiplied by the net ordered quantity.

The calculation of TOTAL_SERVICE_VALUE applies defensive NVL handling throughout: a null SELLING_PRICE is treated as 0, a null SERVICE_DURATION is treated as 1, and the net quantity (ORDERED_QUANTITY minus CANCELLED_QUANTITY) is treated as 0 when null. The final sum is wrapped in a further NVL that returns 0 where no qualifying rows contribute. This makes SERVICE_DURATION a first-class multiplier in the service valuation, which is significant for users searching on "service_duration": the duration term directly scales the line value rather than being informational only.

Common Use Cases and Queries

The view is typically used in order history reporting and integration interfaces that need a per-order service value figure, such as dossier summaries that separate service revenue from product revenue. A representative query retrieves the service total for a specific order:

SELECT HEADER_ID, TOTAL_SERVICE_VALUE
FROM AS_DOSSIER_SERVTOTALS_V
WHERE HEADER_ID = :p_header_id;

To rank orders by service value, order history analysts may aggregate or sort on the exposed column:

SELECT HEADER_ID, TOTAL_SERVICE_VALUE
FROM AS_DOSSIER_SERVTOTALS_V
ORDER BY TOTAL_SERVICE_VALUE DESC;

Because the view returns only headers with at least one qualifying service line, absent headers simply do not appear rather than returning a zero row. Reports requiring a full order listing should therefore outer-join the header table to this view. When troubleshooting unexpected totals, the correct approach is to inspect SO_LINES directly, confirming LINE_TYPE_CODE ('DETAIL' or 'REGULAR'), ITEM_TYPE_CODE ('SERVICE'), and verifying SELLING_PRICE, SERVICE_DURATION, ORDERED_QUANTITY, and CANCELLED_QUANTITY for each contributing line, since each of these inputs materially affects the aggregated result.