Search Results pa_valid_categories_u1

Overview

PA.PA_VALID_CATEGORIES is a reference and validation table within the Oracle E-Business Suite Projects (PA) schema. Its documented purpose is to store the valid class categories for a given object type. In practical terms, the table acts as a control list: it defines which class categories are permissible for a particular object type, and it carries a flag indicating whether a category value must be supplied before downstream processing—specifically, before a project can be authorized for revenue distribution—may proceed. Because it governs the acceptability of category assignments rather than recording transactional activity, it functions as a configuration and setup object rather than a transaction table.

From a Data Vault modeling perspective, the supplied heuristic classification is standalone. In other words, the mined foreign key structure does not reveal a classic hub-and-satellite dependency chain; the table is best treated as an independent reference set. Its uniqueness is enforced through a single business-key index rather than a system-generated surrogate primary key, so a Data Vault implementation would most naturally derive a hub business key from the CLASS_CATEGORY and OBJECT_TYPE_ID pair, with a satellite carrying the descriptive and auditable attributes.

Key Information Stored

The table contains 24 documented columns. The most significant are:

• CLASS_CATEGORY (VARCHAR2(30)) — An implementation-defined name that uniquely identifies the category. It is the primary business identifier for the category and participates in the unique key.
• OBJECT_TYPE_ID (NUMBER(15)) — The identifier of the object type to which the category is associated. It is the second business-key column and the only documented foreign key.
• MANDATORY_FLAG (VARCHAR2) — Indicates whether the user must enter a code for the class category before a project can be authorized for revenue distribution. It is the leading column of the non-unique index PA_VALID_CATEGORIES_N1 and drives validation behavior.
• Standard Who Columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN provide audit and concurrency tracking.
• ATTRIBUTE_CATEGORY (VARCHAR2(30)) — The descriptive flexfield structure defining column.
• ATTRIBUTE1 through ATTRIBUTE15 (VARCHAR2(150) each) — Descriptive flexfield segments available for customer-specific extensions.

No surrogate primary key is documented. The unique index PA_VALID_CATEGORIES_U1 on (CLASS_CATEGORY, OBJECT_TYPE_ID) is the business-key candidate, and it is the index most commonly referenced in application and query code. The second index, PA_VALID_CATEGORIES_N1, is non-unique and supports lookups driven by MANDATORY_FLAG.

Common Use Cases and Queries

The principal use case is enforcing and reporting on valid category configuration. Typical scenarios include:

• Setup validation — verifying that a required class category is defined for an object type before enabling project revenue authorization.
• Mandatory-category auditing — identifying which categories are flagged mandatory so that downstream entry forms and interfaces can be tested against expected behavior.
• Configuration reporting — producing inventories of valid categories per object type for implementation documentation and change control.
• Flexfield inspection — extracting ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 values to review customer-defined extensions.

A representative query pattern retrieves mandatory categories for a given object type:

• SELECT CLASS_CATEGORY, MANDATORY_FLAG FROM PA.PA_VALID_CATEGORIES WHERE OBJECT_TYPE_ID = :object_type_id AND MANDATORY_FLAG = 'Y';
• SELECT CLASS_CATEGORY, OBJECT_TYPE_ID, MANDATORY_FLAG FROM PA.PA_VALID_CATEGORIES ORDER BY OBJECT_TYPE_ID, CLASS_CATEGORY;

Because the table is small and configuration-oriented, queries against it are typically joined into broader category-validation views rather than scanned at volume.

Related Objects

The documented foreign key links PA_VALID_CATEGORIES to the object type definition. The significant related objects are:

• JTF_PERZ_LF_OBJECT_TYPE — Referenced through OBJECT_TYPE_ID. This join resolves the numeric object type into its descriptive definition and is the primary parent relationship for the table.
• PA_VALID_CATEGORIES_U1 — The unique index on (CLASS_CATEGORY, OBJECT_TYPE_ID) that enforces the business key; queries and imports should account for its uniqueness constraint.
• PA_VALID_CATEGORIES_N1 — The non-unique index on MANDATORY_FLAG used for filtered lookups.
• PA.PA_CLASS_CATEGORIES — The Projects class category definition table, which supplies the CLASS_CATEGORY values that this table validates.
• Project setup and revenue authorization logic — Application logic that reads MANDATORY_FLAG before permitting revenue distribution authorization for a project.

Together these objects establish PA_VALID_CATEGORIES as the validation bridge between category definitions and the object types they apply to.