Results for “pa_class_categories_u1”

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

Overview

PA.PA_CLASS_CATEGORIES is an implementation-level seed table in the Oracle E-Business Suite Projects (PA) schema that stores the class categories used to classify projects, tasks, and related project entities. A class category is a reporting construct: each category groups a set of class codes (for example, "Project Type," "Industry," or "Funding Source"), and the codes within a category are assigned to projects to enable flexible reporting, grouping, and, in one documented case, AutoAccounting. Because the table resides in the APPS_TS_SEED tablespace with a PCT Free of 3, it is treated as reference or setup data rather than transactional data; row counts are small and change infrequently.

The table is registered under FND Design Data as PA.PA_CLASS_CATEGORIES and carries a status of VALID in both Oracle EBS 12.1.1 and 12.2.2. The documented physical schema contains 35 columns. Applying a heuristic Data Vault classification to the foreign-key structure, PA_CLASS_CATEGORIES is hub-leaning: it is the target of foreign keys from PA_CLASS_CODES and PA_CI_TYPES_B, and it is referenced by its own unique business keys rather than being a pure intersection or descriptive satellite. This classification is a modeling suggestion only and should not be mistaken for an official EBS designation.

Key Information Stored

The most significant columns of PA_CLASS_CATEGORIES are outlined below. The surrogate primary key documented for the table is PA_CLASS_CATEGORIES_PK on CLASS_CATEGORY. Two unique indexes provide business-key candidates: PA_CLASS_CATEGORIES_U1 on CLASS_CATEGORY (the same column as the primary key) and PA_CLASS_CATEGORIES_U2 on CLASS_CATEGORY_ID, the internal surrogate identifier. That U2 index is the object most commonly associated with the search term "pa_class_categories_u2."

• CLASS_CATEGORY (VARCHAR2 30) — implementation-defined name that uniquely identifies the category; mandatory.
• CLASS_CATEGORY_ID (NUMBER) — surrogate identifier used by dependent tables and the unique index PA_CLASS_CATEGORIES_U2.
• MANDATORY_FLAG — indicates whether a class code must be entered before a project can be authorized for revenue distribution.
• AUTOACCOUNTING_FLAG — indicates whether the category's class codes may be used as an AutoAccounting parameter; only one category may be enabled for this.
• PICK_ONE_CODE_ONLY_FLAG — restricts a project to a single class code; automatically set to 'Y' when AUTOACCOUNTING_FLAG is 'Y'.
• START_DATE_ACTIVE / END_DATE_ACTIVE — first and last effective dates controlling when the category is usable.
• DESCRIPTION (VARCHAR2 80) — explanation of the category's purpose.
• ADW_NOTIFY_FLAG — indexed flag supporting Applications Desktop (ADW) notification behavior; indexed by PA_CLASS_CATEGORIES_N1.
• OBJECT_TYPE and ALL_TYPES_VALID_FLAG — jointly indexed by PA_CLASS_CATEGORIES_N2 and used to scope the category to specific project object types.
• ALLOW_PERCENT_FLAG, TOTAL_100_PERCENT_FLAG, INCLUDE_IN_PJI_FLAG — control percentage entry, 100 percent validation, and Project Intelligence inclusion.
• Standard Who columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — descriptive flexfield extensibility columns.

Common Use Cases and Queries

Typical use cases include reporting on the defined class category structure, validating setup before project entry, and joining class codes to their parent category for reporting. Because class categories drive reporting groupings, they are frequently joined to PA_CLASS_CODES and to project assignment tables.

Sample queries:

• List active categories: SELECT class_category, description FROM pa_class_categories WHERE SYSDATE BETWEEN NVL(start_date_active, SYSDATE) AND NVL(end_date_active, SYSDATE) ORDER BY class_category;
• Find the AutoAccounting category: SELECT class_category FROM pa_class_categories WHERE autoaccounting_flag = 'Y';
• Join categories to codes: SELECT c.class_category, cc.class_code FROM pa_class_categories c, pa_class_codes cc WHERE c.class_category = cc.class_category;
• Locate the surrogate key: SELECT class_category_id, class_category FROM pa_class_categories WHERE class_category = :name;

Related Objects

The following objects are the most significant references and dependencies documented for PA_CLASS_CATEGORIES:

• PA_CLASS_CODES — child table referencing PA_CLASS_CATEGORIES.CLASS_CATEGORY; holds the individual codes that populate each category.
• PA_CI_TYPES_B — references PA_CLASS_CATEGORIES through REASON_CATEGORY; links capital improvement reason categories to class categories.
• PA_CLASS_CATEGORIES_U1 / _U2 — unique indexes enforcing the class category name and surrogate ID business keys.
• PA_CLASS_CATEGORIES_N1 / _N2 — non-unique indexes on ADW_NOTIFY_FLAG and OBJECT_TYPE/ALL_TYPES_VALID_FLAG supporting query performance.
• Project-level assignments of class codes (for example, PA_PROJECT_CLASSES and related project classification tables) indirectly depend on the category definitions stored here.

In summary, PA_CLASS_CATEGORIES defines the vocabulary by which projects are classified in Oracle Projects, and its two unique indexes—especially PA_CLASS_CATEGORIES_U2 on CLASS_CATEGORY_ID—govern how dependent tables resolve and reference that vocabulary.