Results for “pa_adw_srvc_types_v”

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

Overview

PA_ADW_SRVC_TYPES_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the Projects (PA) product family. The view presents the set of service type values that populate the service dimension used in Oracle Projects reporting and analytics. In ETRM documentation the object is classified as a VIEW with VALID status, present in both the 12.1.1 and 12.2.2 releases. Its description states simply: "Values for service types on the service dimension."

The "ADW" prefix in the name follows Oracle's convention for objects that support the Applications Data Warehouse and associated dimensional reporting structures (for example, Oracle Projects Intelligence and Project Performance reporting). Rather than exposing transactional project data, the view functions as a reference or dimension source: it enumerates the valid service types and their associated user-defined descriptive columns so that downstream reporting queries can join fact data to a clean, consistent list of service type codes and descriptions.

Underlying Base Objects

The documented view text is a direct projection from a single base view:

• PA_ADW_SRVC_TYPES_B_V — the underlying view that supplies all thirteen columns exposed by PA_ADW_SRVC_TYPES_V.
• FND_GLOBAL — the standard Oracle Applications package referenced by the view hierarchy, typically used to resolve session context values such as USER_ID, RESP_ID, and ORG_ID for security or profile-driven filtering.

Because PA_ADW_SRVC_TYPES_V merely re-selects every column from PA_ADW_SRVC_TYPES_B_V without additional joins, filters, or transformations, it behaves as a stable public interface layer over the "B" (base) view. Any row-level restriction or lookup logic resides in PA_ADW_SRVC_TYPES_B_V or the tables it in turn references. In practice, this layering isolates report definitions from changes to the underlying base view while preserving the documented column list.

Key Columns

The view exposes thirteen columns, all passed through unchanged from the base view:

• SERVICE_TYPE_CODE — the code identifying the service type; this is the key value used to join to fact or transaction data on the service dimension.
• SERVICE_TYPE — the descriptive name or translated value associated with the code, suitable for display in reports.
• ALL_SERVICE_TYPES — a flag or aggregate indicator used to denote a "total/all" member of the dimension, commonly applied in warehouse-style rollups.
• USER_COL1 through USER_COL10 — ten generic, user-defined attribute columns. These allow implementation-specific descriptive or grouping information to be attached to each service type without schema modification, and are typically populated through descriptive flexfield or configuration setups.

Common Use Cases and Queries

Typical usage is to drive prompts, value sets, and lookup joins in Projects reporting, or to enumerate service types for data warehouse load validation. A representative query lists all available service types for a report parameter:

• SELECT service_type_code, service_type FROM apps.pa_adw_srvc_types_v ORDER BY service_type;
• SELECT service_type_code, service_type, all_service_types FROM apps.pa_adw_srvc_types_v WHERE all_service_types = 'Y'; — to isolate the "all services" rollup member.
• SELECT v.service_type_code, v.service_type, v.user_col1 FROM apps.pa_adw_srvc_types_v v WHERE v.service_type_code = :service_type; — a lookup for a specific code, for example when resolving a value stored on a project fact row.

Because the view is a read-only projection, it is safe for ad hoc queries, custom Concurrent Program parameters, and BI Publisher data templates. Reports should reference this view rather than the private "B" view to remain aligned with the documented, supported interface.