Results for “pa_valid_categories”

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

Overview

PA_VALID_CATEGORIES is a configuration and validation table within the Oracle Projects (PA) module of Oracle E-Business Suite, present in both release 12.1.1 and 12.2.2. It stores the set of categories that are considered valid for a given object type, effectively acting as a control list that constrains which project categories may be assigned to particular objects. The table is owned by the PA schema and is classified as VALID in the ETRM repository.

Because the table holds reference or setup data rather than transactional movements, its heuristic Data Vault classification is standalone. This suggests it is best modeled as a reference or satellite-style structure rather than as a hub or link. The table has 24 documented columns, which is typical of Oracle EBS seed and setup tables that carry the standard WHO audit columns alongside business attributes.

Key Information Stored

The most important columns documented in the ETRM metadata are:

• CLASS_CATEGORY — the category value itself; part of the composite business key.
• OBJECT_TYPE_ID — foreign key identifying the object type for which the category is valid; the other half of the business key.
• MANDATORY_FLAG — indicates whether the category is required for the associated object type.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit tracking of the most recent change.
• CREATION_DATE, CREATED_BY — who created the row and when.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the flexible DFF (descriptive flexfield) columns for extensible attributes.

The documented unique index PA_VALID_CATEGORIES_U1 spans (CLASS_CATEGORY, OBJECT_TYPE_ID), establishing these two columns as the business-key candidates. No separate surrogate primary key column is listed in the documented column set, implying the unique index functions as the primary uniqueness constraint.

Common Use Cases and Queries

Typical scenarios include validating category assignments during project setup, driving list of values (LOV) behavior in project forms, and auditing which categories are mandatory for a given object type. A representative query returning all valid categories for a specific object type would resemble:

• SELECT CLASS_CATEGORY, MANDATORY_FLAG FROM PA_VALID_CATEGORIES WHERE OBJECT_TYPE_ID = :object_type_id;
• SELECT * FROM PA_VALID_CATEGORIES WHERE MANDATORY_FLAG = 'Y';

Reporting use cases might join this table with category definitions to produce a setup audit, or join to the object type reference to confirm naming. Because the table is small and static, it is generally safe to query directly without performance degradation.

Related Objects

The documented foreign key relationship links this table to the object type reference table. Significant related objects include:

• JTF_PERZ_LF_OBJECT_TYPE — referenced via OBJECT_TYPE_ID → JTF_PERZ_LF_OBJECT_TYPE, supplying the object type definitions.
• PA_CATEGORIES — the master category setup likely referenced by CLASS_CATEGORY.
• PA_PROJECTS — project records whose categories are governed by these validation rules.
• PA_PROJECT_TYPES — project type definitions commonly associated with category validation.
• PA_OBJECT_TYPES or equivalent object-type lookups used by Projects.
• Project setup forms and APIs that enforce MANDATORY_FLAG during category assignment.

Together these objects support the Projects module's category validation framework and should be reviewed jointly during setup and data-migration activities.