Results for “service_reference_type”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The ASO_I_SERVICE_TYPES_V view is a reference data view owned by the APPS schema within the ASO (Order Capture) product family of Oracle E-Business Suite. Its documented purpose is to expose the reference information for services supported by Order Management. Rather than storing transactional data, this view surfaces a controlled lookup list — the set of service reference types currently enabled for use in the Order Capture and Order Management flows. Because it is a simple and lightweight view, it is commonly joined to quoting, ordering, and service subscription data to translate internal lookup codes into human-readable descriptions for reporting, integrations, and user-facing inquiries.

The view carries a VALID status in the ETRM metadata for both 12.1.1 and 12.2.2, indicating it is a supported, stable object in these releases. Its role is primarily that of a decoding reference: consumers query it to enumerate valid service reference types or to resolve a stored code into its meaning and description.

Underlying Base Objects

The view is defined over a single documented base object: OE_LOOKUPS, which is itself a view owned by APPS. The definition filters that lookup source by a specific lookup type and by an enablement and date-range condition, so only currently active rows are surfaced. Structurally, the view text is:

• SELECT MEANING SERVICE_REFERENCE_TYPE, LOOKUP_CODE SERVICE_REFERENCE_TYPE_CODE, DESCRIPTION FROM OE_LOOKUPS WHERE LOOKUP_TYPE = 'SERVICE_REFERENCE_TYPE_CODE' AND ENABLED_FLAG = 'Y' AND TRUNC(SYSDATE) BETWEEN NVL(START_DATE_ACTIVE, TRUNC(SYSDATE)) AND NVL(END_DATE_ACTIVE, TRUNC(SYSDATE))

Three filters are applied. First, only rows whose LOOKUP_TYPE equals SERVICE_REFERENCE_TYPE_CODE qualify, restricting the result set to service reference types. Second, only rows with ENABLED_FLAG = 'Y' are included. Third, the current system date must fall within the active date window; the NVL functions default a missing start date to today and a missing end date to today, making the boundary conditions inclusive and tolerant of NULL dates. Through OE_LOOKUPS, the reference values ultimately derive from the Order Management lookup infrastructure.

Key Columns

The view exposes three columns, each renamed from its source:

• SERVICE_REFERENCE_TYPE — mapped from the MEANING column of OE_LOOKUPS. This is the display or translated meaning of the service reference type and is typically the value presented to users in reports and lists of values.
• SERVICE_REFERENCE_TYPE_CODE — mapped from the LOOKUP_CODE column. This is the internal code stored on transactional or setup records and is the key used when joining the view to other data. It is analogous to the reversed lookup name.
• DESCRIPTION — passes through the DESCRIPTION column of OE_LOOKUPS, providing supplementary explanatory text for the reference type.

Common Use Cases and Queries

Typical uses include populating a service reference type list of values, decoding a stored code on order or quote lines, and validating integration payloads. A simple enumeration of valid values follows.

• SELECT service_reference_type_code, service_reference_type, description FROM aso_i_service_types_v ORDER BY service_reference_type;
• SELECT service_reference_type FROM aso_i_service_types_v WHERE service_reference_type_code = :code;

Because the view is restricted to enabled and date-effective rows, results reflect the currently usable service reference types, which makes it suitable for real-time validation and reporting joins without the caller replicating the enablement or date logic.