Results for “class_category_id”

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

Overview

PA_CLASS_CATEGORIES is an Oracle Projects (PA) implementation table that defines the set of user-defined category groups used to classify projects and project-related transactions. Each row in the table establishes a class category — for example, Project Type, Project Status, Service Type, or a customer-specific grouping — and controls how the corresponding values behave during project entry, project classification, and related business processes.

The table sits in the PA schema and is documented as VALID in ETRM 12.2.2, with 35 physical columns. Two unique indexes are documented: PA_CLASS_CATEGORIES_U1 on CLASS_CATEGORY and PA_CLASS_CATEGORIES_U2 on CLASS_CATEGORY_ID. The primary key is PA_CLASS_CATEGORIES_PK on CLASS_CATEGORY. Because CLASS_CATEGORY is captured as both the primary key and a unique business-key candidate, CLASS_CATEGORY_ID functions as an alternate unique surrogate-style identifier.

From a Data Vault modeling perspective, the heuristic classification is hub-leaning. PA_CLASS_CATEGORIES behaves as a stable, business-keyed entity that other tables reference, which aligns naturally with a hub pattern. The descriptive and control-flag attributes reinforce this hub with satellite-like detail, but the core identity remains the CLASS_CATEGORY business key.

Key Information Stored

The most significant columns fall into three groups: identity, behavioral control, and descriptive attributes.

• CLASS_CATEGORY — The business-key identifier and primary key (PA_CLASS_CATEGORIES_PK); the implementation-defined category name.
• CLASS_CATEGORY_ID — Alternate unique identifier (PA_CLASS_CATEGORIES_U2); the surrogate used by many foreign-key references.
• MANDATORY_FLAG — Indicates whether a class code must be chosen for the category.
• PICK_ONE_CODE_ONLY_FLAG — Restricts selection to a single class code.
• ALLOW_PERCENT_FLAG and TOTAL_100_PERCENT_FLAG — Govern percentage-based class code allocation and whether percentages must total 100.
• AUTOACCOUNTING_FLAG — Determines whether the category drives automatic accounting behavior.
• START_DATE_ACTIVE / END_DATE_ACTIVE — Date-range enablement for the category.
• ADW_NOTIFY_FLAG, ALL_TYPES_VALID_FLAG, INCLUDE_IN_PJI_FLAG — Control notification, valid-type scope, and inclusion in Project/Contract invoicing logic.
• OBJECT_TYPE — Identifies the associated object type.
• DESCRIPTION — Free-text description of the category.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — Flexfield descriptive columns for extensibility.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns.

Common Use Cases and Queries

Typical usage includes validating implementation setup, driving project-entry validation, and reporting on classification configuration.

• List active categories and their key control flags:

  SELECT class_category, description, mandatory_flag,
         start_date_active, end_date_active
  FROM   pa_class_categories
  WHERE  SYSDATE BETWEEN start_date_active
         AND NVL(end_date_active, SYSDATE + 1);
  

• Find mandatory, single-select categories:

  SELECT class_category
  FROM   pa_class_categories
  WHERE  mandatory_flag = 'Y'
  AND    pick_one_code_only_flag = 'Y';
  

• Join to class codes to enumerate allowed values for a category:

  SELECT c.class_category, k.class_code, k.description
  FROM   pa_class_categories c,
         pa_class_codes      k
  WHERE  c.class_category = k.class_category;
  

Related Objects

The documented foreign-key relationships identify the principal dependent objects.

• PA_CLASS_CODES — References PA_CLASS_CATEGORIES via CLASS_CATEGORY; stores the individual codes assignable within each category.
• PA_CI_TYPES_B — References PA_CLASS_CATEGORIES via REASON_CATEGORY; links Credit/Invoicing types to a reason category.

Because PA_CLASS_CATEGORIES is a hub-leaning entity, additional project classification tables and project definition forms in the PA module frequently reference its CLASS_CATEGORY or CLASS_CATEGORY_ID values when validating classifications.