Results for “pa_res_types_b”

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

Overview

PA_RES_TYPES_B is the base table in the Oracle Projects (PA) module that stores resource type definitions. In Oracle EBS 12.1.1 and 12.2.2, a "resource type" is a classification that determines how project resources — such as people, organizations, or non-labor assets — are grouped, costed, and reported. Each row in PA_RES_TYPES_B represents a single resource type available for assignment within the Projects application. The table acts as a foundational master data object referenced by resource breakdown structures (RBS), resource formats, and translated resource type descriptions.

From a Data Vault modeling perspective, the mined heuristic classification for this table is hub-leaning. This suggests PA_RES_TYPES_B functions primarily as a central hub of stable business keys (resource types), surrounded by satellites and links that carry descriptive and transactional detail. This classification should be treated as a modeling suggestion rather than an authoritative statement of design intent.

Key Information Stored

The table is owned by the PA schema and, per the documented physical schema for 12.2.2, contains 9 columns. The most significant columns are listed below.

• RES_TYPE_ID — The surrogate primary key, defined by the PA_RES_TYPES_B_PK constraint. It uniquely identifies each resource type row and is the column referenced by all foreign keys pointing to this table.
• RES_TYPE_CODE — A business-key candidate that holds the user-meaningful code for the resource type. Together with ZD_EDITION_NAME, it forms the unique index PA_RES_TYPES_B_U1.
• ENABLED_FLAG — Indicates whether the resource type is currently active and selectable in projects transactions.
• ZD_EDITION_NAME — Part of the unique index PA_RES_TYPES_B_U1 (RES_TYPE_ID, ZD_EDITION_NAME), supporting the editioning framework used in EBS 12.2.x.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard audit columns recording when and by whom the row was last modified.
• CREATION_DATE, CREATED_BY — Standard audit columns recording row creation metadata.

Translations of the resource type name and description are not stored in this base table; they reside in PA_RES_TYPES_TL, linked through RES_TYPE_ID.

Common Use Cases and Queries

PA_RES_TYPES_B is queried whenever resource types must be validated, listed, or joined to RBS structures and resource formats. A typical reporting pattern retrieves the enabled resource types with their translated descriptions:

• Listing active resource types: SELECT RES_TYPE_ID, RES_TYPE_CODE FROM PA_RES_TYPES_B WHERE ENABLED_FLAG = 'Y';
• Joining to translations: SELECT B.RES_TYPE_ID, B.RES_TYPE_CODE, T.NAME FROM PA_RES_TYPES_B B, PA_RES_TYPES_TL T WHERE B.RES_TYPE_ID = T.RES_TYPE_ID AND T.LANGUAGE = USERENV('LANG');
• Locating RBS elements that use a given resource type: SELECT E.* FROM PA_RBS_ELEMENTS E, PA_RES_TYPES_B B WHERE E.RESOURCE_TYPE_ID = B.RES_TYPE_ID AND B.RES_TYPE_CODE = :code;
• Identifying resource formats per resource type: SELECT F.* FROM PA_RES_FORMATS_B F, PA_RES_TYPES_B B WHERE F.RES_TYPE_ID = B.RES_TYPE_ID;

These queries support operational setup validation, access to resource breakdown structures, and reporting on how resource types are configured across a project implementation.

Related Objects

The following objects depend on or reference PA_RES_TYPES_B through documented foreign keys.

• PA_RES_TYPES_TL — Translation table joined on RES_TYPE_ID, storing language-specific names and descriptions.
• PA_RBS_ELEMENTS — References resource types through RESOURCE_TYPE_ID, defining resource breakdown structure elements.
• PA_RES_FORMATS_B — References resource types through RES_TYPE_ID, defining resource formats associated with each type.

Together these relationships establish PA_RES_TYPES_B as the central hub for resource type master data, with dependent tables supplying translations, RBS usage, and format configuration.