Results for “pa_class_codes”

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

Overview

PA_CLASS_CODES is a reference (setup) table in the Oracle Projects (PA) schema that stores implementation-defined classification values used to categorize projects. Each row represents a single valid class code belonging to a class category, forming the controlled vocabulary from which project classifications are drawn. Because projects are segmented along multiple analytical dimensions — such as project type, service offering, industry, or funding source — PA_CLASS_CODES provides the granular pick-list entries that populate those dimensions within Oracle EBS 12.1.1 and 12.2.2.

From a Data Vault modeling perspective, the metadata heuristic classifies this table as satellite-leaning. It is a descriptive reference object keyed by business attributes rather than a pure hub of independent entities, though it also anchors dependent records. This classification is offered as a modeling suggestion, not an authoritative designation.

Key Information Stored

The table holds 28 documented columns, of which the most operationally significant are the classification attributes and the audit/control fields.

• CLASS_CATEGORY — the class category to which the code belongs. It is part of the composite primary key (PA_CLASS_CODES_PK) and a foreign key to PA_CLASS_CATEGORIES.
• CLASS_CODE — the implementation-defined value itself; the second component of the composite primary key.
• CLASS_CODE_ID — a surrogate identifier carrying a unique index (PA_CLASS_CODES_U2), allowing single-column referencing.
• DESCRIPTION — the user-facing name or explanation of the code.
• START_DATE_ACTIVE / END_DATE_ACTIVE — date-range controls governing when the code is selectable.
• ADW_NOTIFY_FLAG — a flag associated with Projects reporting/warehouse notification behavior.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the standard Oracle EBS descriptive flexfield (DFF) columns for capturing client-specific extensions.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN.

A second unique index, PA_CLASS_CODES_U1 (CLASS_CATEGORY, CLASS_CODE), confirms the composite business key, while PA_CLASS_CODES_U2 enforces intra-table uniqueness of the surrogate CLASS_CODE_ID.

Common Use Cases and Queries

The most frequent scenario is resolving the valid codes available for a given category when assigning classifications to a project. A typical query joins the two reference tables:

• SELECT cc.CLASS_CODE, cc.DESCRIPTION FROM PA_CLASS_CODES cc WHERE cc.CLASS_CATEGORY = :category AND TRUNC(SYSDATE) BETWEEN NVL(cc.START_DATE_ACTIVE, SYSDATE) AND NVL(cc.END_DATE_ACTIVE, SYSDATE);
• Reporting the classifications actually applied to projects requires joining to PA_PROJECT_CLASSES on both CLASS_CODE and CLASS_CATEGORY.
• Warehouse or integration extracts often filter on ADW_NOTIFY_FLAG to isolate codes flagged for downstream notification.
• DFF reporting reads ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 to surface client-defined metadata.

Because codes are setup-driven, validation queries typically enforce the active date range to avoid presenting retired values.

Related Objects

• PA_CLASS_CATEGORIES — the parent reference table; PA_CLASS_CODES.CLASS_CATEGORY references the category definition.
• PA_PROJECT_CLASSES — the association table linking projects to their assigned codes; its CLASS_CODE and CLASS_CATEGORY columns reference this table.
• PA_PROJECTS_ALL / PA_PROJECTS — the project master, reached indirectly through PA_PROJECT_CLASSES for classification reporting.
• PA_CLASS_CODES_PK / _U1 / _U2 — the primary and unique indexes enforcing identity and business keys.

Together these objects form the classification model that drives project segmentation, reporting, and downstream Projects analytics within EBS.