Results for “user_col4”

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

Overview

PA_ADW_SRVC_TYPES_B_V is a Projects (PA) module view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It is documented in the E-Business Suite Technical Reference Manual (ETRM) with the description "Retrofitted", indicating that the object was carried forward into the 12.2.x release architecture, most likely originating from the earlier Oracle Projects Data Warehouse (ADW) schema and now published within APPS as a compatibility view for external reporting and integration consumers.

The view exposes a normalized list of service types used for Projects reporting and analytics, together with an "all service types" placeholder. Its role is to feed dimensional lookups — service type codes, display names, and an aggregate/unknown resource label — into reporting layers, data warehouse extracts, and third-party integrations that need a stable, queryable service-type dimension without directly joining the underlying PA lookup infrastructure.

Underlying Base Objects

The ETRM metadata records that the view references PA_LOOKUPS (VIEW), PA_LOOKUP_TYPES (VIEW), and the FND_GLOBAL package. The view text confirms that PA_LOOKUPS is joined to itself and to PA_LOOKUP_TYPES on LOOKUP_TYPE, and it draws on the 'SERVICE TYPE', 'ADW DIM LEVEL NAME', and 'ADW RESOURCE NAME' lookup types. In the APPS data model these views ultimately resolve to the PA_LOOKUPS_B / PA_LOOKUPS_TL and PA_LOOKUP_TYPES_B / PA_LOOKUP_TYPES_TL base tables, which store the lookup code, the translated meaning, and the lookup type definition. Because the view is defined over lookups, its content is driven by the seeded and user-maintained lookup values rather than by transactional Projects data.

Key Columns

• SERVICE_TYPE_CODE — the lookup code from the 'SERVICE TYPE' lookup type; in the first UNION branch this is sourced from PL.LOOKUP_CODE.
• SERVICE_TYPE — for valid service types, the translated meaning (PLA.MEANING); for the 'UNKNOWN' row from the second UNION branch, the resource meaning (PLU.MEANING) is returned here as well as in SERVICE_TYPE_CODE.
• ALL_SERVICE_TYPES — the meaning of the 'ADW DIM LEVEL NAME' lookup with code 'ALL_SRVC_TYPES', providing an aggregate "all" label for the dimension.
• USER_COL1 through USER_COL10 — placeholder columns. In the documented view text every one of these is selected as NULL; they exist to reserve the standard ADW column shape (code, name, level, plus user-defined extension slots) for downstream consumers, rather than to expose additional lookup attributes.

Common Use Cases and Queries

This view is typically consumed by Projects reporting and extract processes that need to enumerate service types. A simple listing retrieves the dimension values:

SELECT SERVICE_TYPE_CODE, SERVICE_TYPE, ALL_SERVICE_TYPES FROM APPS.PA_ADW_SRVC_TYPES_B_V;

To exclude the aggregate/unknown row and list only real service types:

SELECT SERVICE_TYPE_CODE, SERVICE_TYPE FROM APPS.PA_ADW_SRVC_TYPES_B_V WHERE SERVICE_TYPE_CODE <> SERVICE_TYPE;

For validation and cross-checking against the source lookups:

SELECT v.SERVICE_TYPE_CODE, l.MEANING FROM APPS.PA_ADW_SRVC_TYPES_B_V v, APPS.PA_LOOKUPS l WHERE l.LOOKUP_TYPE = 'SERVICE TYPE' AND l.LOOKUP_CODE = v.SERVICE_TYPE_CODE;

Because the view references FND_GLOBAL, consumers should be aware that MLR/translation context can affect the returned meanings; queries are therefore best executed in the intended language environment when localized labels are required.