Results for “res_type_id”

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

Overview

PA_RES_TYPES_AMG_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, registered under the Projects (PA) product family. It exposes a curated, denormalized projection of resource type data. In Oracle Projects, a "resource type" classifies the kinds of resources that can be assigned to project work and charged against project budgets and expenditures — for example, an employee, a contingent worker, or a specific expenditure category such as "Consultant" or "Subcontractor." Because resource type is a foundational classification that drives cost rates, billing rates, and effort tracking, its identifier (RES_TYPE_ID) and code (RES_TYPE_CODE) are referenced across a wide range of Projects and related subledger objects.

The AMG suffix in the view name follows the Oracle Applications multitenancy / compatibility naming convention used for Application Management Group (AMG) views; these views exist to provide a stable, migration-safe interface layer that stays consistent across releases. In EBS 12.1.1 and 12.2.2, PA_RES_TYPES_AMG_V retains a VALID status and is documented in ETRM (the E-Business Suite Technical Reference Manual) with the four-column projection listed below. It provides no additional derived logic or filtering; it is a simple pass-through that standardizes column naming for downstream consumers.

Underlying Base Objects

The view is defined over a single documented base object: PA_RES_TYPES_VL, a translation (VL = "view, language") view in the Projects schema. The full documented view text is a plain SELECT from that source:

SELECT TYP.RES_TYPE_ID,
       TYP.RES_TYPE_CODE,
       TYP.NAME,
       TYP.DESCRIPTION
FROM   PA_RES_TYPES_VL TYP

Because PA_RES_TYPES_VL is the language-specific layer over the underlying resource type base table, it returns translated NAME and DESCRIPTION values based on the session's language setting. The AMG view therefore inherits the translation-aware behavior of its parent without altering it. No joins, unions, or filters are applied, so the row cardinality of PA_RES_TYPES_AMG_V matches the set of resource types visible through PA_RES_TYPES_VL for the current language.

Key Columns

• RES_TYPE_ID — The numeric primary key of the resource type. This is the value most commonly sought by users searching for "res_type_id," and it is the foreign key referenced from project resource assignments, rate schedules, and expenditure records.
• RES_TYPE_CODE — A short, unique alphanumeric code that identifies the resource type in configurations, interfaces, and seeded data loads. Codes are language-neutral and stable across releases.
• NAME — The translated, user-facing name of the resource type, suitable for display on reports and LOVs.
• DESCRIPTION — The translated long description providing additional context about the resource type's intended use.

Common Use Cases and Queries

Typical uses include: resolving a stored RES_TYPE_ID back to its display name in expenditure and utilization reports; populating a validation LOV in a custom concurrent program or OAF page; and joining resource-type attributes onto project staffing or cost analysis extracts. A standard lookup by ID follows:

SELECT res_type_id,
       res_type_code,
       name,
       description
FROM   apps.pa_res_types_amg_v
WHERE  res_type_id = :p_res_type_id;

To enumerate all resource types for a picklist, order by NAME:

SELECT res_type_id, res_type_code, name
FROM   apps.pa_res_types_amg_v
ORDER  BY name;

A commonly used integration query resolves code to ID where interfaced data carries only the code value:

SELECT res_type_id
FROM   apps.pa_res_types_amg_v
WHERE  res_type_code = :p_res_type_code;

Because the view is unfiltered and non-aggregated, it is safe to join directly to transactional Projects tables on RES_TYPE_ID without fear of duplicate or synthetic rows. Access is governed by the standard APPS schema grants; custom reporting should be granted SELECT explicitly rather than relying on broad APPS privileges.