Results for “pa_res_types_vl”

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

Overview

PA_RES_TYPES_VL is a seeded, language-dependent (VL) view in the Oracle E-Business Suite Projects (PA) module, owned by the APPS schema. It exposes the set of resource types that Oracle Projects uses to classify the resources assigned to project work — for example labor resources, expense or expenditure items, and other billable or non-billable resource categories. Because resource types drive how costs, budgets, and billing are identified and processed across Oracle Projects, this view is a foundational reference object for reporting, validation, and integration.

The "_VL" suffix indicates a view that joins a base (non-translated) table with its translated (_TL) table, so that user-facing attributes such as NAME and DESCRIPTION are returned in the session language. The view is documented in ETRM with a status of VALID and contains only required columns — no descriptive flexfield segments. This makes it convenient for LOVs, validation queries, and lightweight lookups: consumers retrieve a stable RES_TYPE_ID and RES_TYPE_CODE alongside language-specific text.

Underlying Base Objects

The view is defined over two documented synonyms:

• PA_RES_TYPES_B — the base table holding non-translatable, operational attributes of each resource type, including the primary key RES_TYPE_ID, the RES_TYPE_CODE, and the ENABLED_FLAG that controls whether the resource type is active.
• PA_RES_TYPES_TL — the translation table holding the language-specific NAME and DESCRIPTION, keyed by RES_TYPE_ID and LANGUAGE.

Per the documented view text, the join is expressed as B.RES_TYPE_ID = T.RES_TYPE_ID AND T.LANGUAGE = USERENV('LANG'), so only rows matching the current session language are returned. The base table provides the RES_TYPE_ID used as the foreign key from other Projects tables, while the translated table supplies the descriptions. The view selects all its operational columns from the base table and only NAME and DESCRIPTION from the translated table.

Key Columns

• ROW_ID — the base table ROWID, exposed for row-level identification.
• RES_TYPE_ID — the internal primary key for a resource type; the value stored as a foreign key on Projects resource, expenditure, and billing records.
• RES_TYPE_CODE — the short, language-independent code (for example, a labor or expense resource code) used in logic and integration.
• ENABLED_FLAG — indicates whether the resource type is active and selectable; typically filter on this column in lookups.
• NAME — the translated, user-facing name of the resource type.
• DESCRIPTION — the translated long description.
• Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN, carried from the base table for change tracking.

Common Use Cases and Queries

Typical uses include LOV population, reporting, data extracts, and validating a stored RES_TYPE_ID before insertion into project records. A simple lookup of active resource types is:

SELECT res_type_id, res_type_code, name
FROM apps.pa_res_types_vl
WHERE enabled_flag = 'Y'
ORDER BY name;

To resolve the resource type on expenditure or assignment records, join on RES_TYPE_ID:

SELECT prt.name, d.expenditure_item_date, d.billable_flag
FROM apps.pa_expenditure_items_all d, apps.pa_res_types_vl prt
WHERE d.res_type_id = prt.res_type_id
AND d.expenditure_item_date >= :p_from_date;

Because the view already restricts to the session language, it returns single-language rows without requiring the caller to join the _TL table manually. Integration routines should reference RES_TYPE_CODE for stable matching and use RES_TYPE_ID for foreign-key storage, always filtering ENABLED_FLAG where only selectable types are valid.