Results for “resource_class_seq”

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

Overview

PA_RESOURCE_CLASSES_B is the base (language-independent) table in the Oracle Projects (PA) module that stores resource class definitions. Resource classes are the highest-level grouping mechanism used throughout Oracle Projects to categorize the resources — people, organizations, and roles — that can be assigned to project work. They act as a controlling attribute for reporting rollups, resource list construction, planning defaults, and formatting rules applied to project resources.

The table resides in the PA schema and carries a VALID status in both Oracle EBS 12.1.1 and 12.2.2. Because the business identity of a resource class is code-based and translatable, Oracle EBS implements this entity as a base table paired with a translation table (PA_RESOURCE_CLASSES_TL). The base table holds the Oracle-owned, non-translated columns, while display names are resolved through the translation table at query time.

From a Data Vault modeling perspective, the mined foreign-key structure classifies PA_RESOURCE_CLASSES_B as hub-leaning. In practice, this means the table behaves as a central business entity table: RESOURCE_CLASS_ID is the durable business key referenced by many dependent objects, and the table itself does not merely describe another parent. Any Data Vault implementation would reasonably model RESOURCE_CLASS_ID as a hub key.

Key Information Stored

The table contains 9 documented columns in the 12.2.2 physical schema. The most significant are:

• RESOURCE_CLASS_ID — the surrogate primary key defined by index PA_RESOURCE_CLASSES_B_PK. It is the value propagated to every dependent table as a foreign key and is the single most important column for joins.
• RESOURCE_CLASS_CODE — the user-visible, language-independent identifier for the resource class. Together with RESOURCE_CLASS_ID and ZD_EDITION_NAME it participates in the unique business-key candidate index PA_RESOURCE_CLASSES_B_U1.
• RESOURCE_CLASS_SEQ — the sequence number controlling the display order of resource classes in list-of-values and reporting outputs.
• ZD_EDITION_NAME — the editioning column introduced by the 12.2 online patching architecture. It is part of the U1 unique index and must be accounted for in any query written against a 12.2.2 environment; in 12.1.1 this column does not exist.
• Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN record who created and last modified each resource class, supporting change tracking, data lineage, and troubleshooting.

Note the distinction between the surrogate key (RESOURCE_CLASS_ID) and the business-key candidate (RESOURCE_CLASS_ID, ZD_EDITION_NAME as documented in U1).

Common Use Cases and Queries

Resource classes drive resource list membership, planning resource defaults, and resource formatting. Typical reporting and integration queries resolve codes to translated names and then join outward to dependent tables:

• Validating a resource class before assignment: SELECT resource_class_code FROM pa_resource_classes_b WHERE resource_class_id = :id;
• Populating a list of values with translated names: join PA_RESOURCE_CLASSES_B to PA_RESOURCE_CLASSES_TL on RESOURCE_CLASS_ID and filter on the appropriate LANGUAGE.
• Determining which resource lists contain a given class by joining PA_RESOURCE_LIST_MEMBERS on RESOURCE_CLASS_ID.
• Auditing planning defaults through PA_PLAN_RES_DEFAULTS.RESOURCE_CLASS_ID.
• Reporting on formatting behavior through PA_RES_FORMATS_B.RESOURCE_CLASS_ID.
• Ordering output by RESOURCE_CLASS_SEQ to match the application's LOV ordering.

In 12.2.2 environments, always qualify queries with the edition context, since ZD_EDITION_NAME participates in the unique index.

Related Objects

The FK metadata identifies four direct dependents, all joined on RESOURCE_CLASS_ID:

• PA_RESOURCE_CLASSES_TL — the translation table holding language-specific names, joined on RESOURCE_CLASS_ID.
• PA_RESOURCE_LIST_MEMBERS — associates resource classes with resource lists; joined on RESOURCE_CLASS_ID.
• PA_PLAN_RES_DEFAULTS — planning resource defaults referencing a resource class; joined on RESOURCE_CLASS_ID.
• PA_RES_FORMATS_B — resource formatting definitions; joined on RESOURCE_CLASS_ID.

These four relationships establish PA_RESOURCE_CLASSES_B as a hub-style parent in the Projects resource model, and they are the primary objects to review when tracing impact of changes to resource class data.