Search Results pa_valid_categories_v




Overview
Explore in AI Chat

Overview

PA_VALID_CATEGORIES_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, defined within the Projects (PA) product family. It presents the set of class categories that are valid for a given project type, resolving the intersection between the class category master definitions held in PA_CLASS_CATEGORIES and the type-specific applicability rules stored in PA_VALID_CATEGORIES. The view is documented as VALID in ETRM for both 12.1.1 and 12.2.2. Its primary role is to expose, in a single flattened result set, the category attributes — such as mandatory status, autoaccounting behaviour, percentage handling, and date-range activity — that drive project setup validation, category assignment, and dependent reporting logic. Subledger and project accounting reports routinely reference this view rather than re-implementing the multi-table join logic that determines category validity.

Underlying Base Objects

The view is defined over three documented base objects, all referenced through APPS synonyms:

The view definition uses a UNION of two branches. The first returns categories that are explicitly associated with a project type via PA_VALID_CATEGORIES. The second returns categories where OBJECT_TYPE is 'PA_PROJECTS' and ALL_TYPES_VALID_FLAG is 'Y' — that is, categories valid for all project types — but only where no explicit association already exists for that project type (enforced by a NOT EXISTS subquery against PA_VALID_CATEGORIES). This prevents duplication between the two branches. Both branches filter on SYSDATE being between START_DATE_ACTIVE and NVL(END_DATE_ACTIVE, SYSDATE), so only currently active categories are returned.

Key Columns

  • CLASS_CATEGORY — the category identifier; the natural key joining to category code definitions.
  • OBJECT_TYPE — the owning object type (for example, PA_PROJECTS) indicating the context in which the category applies.
  • OBJECT_TYPE_ID — the project type identifier the row is valid for; carries the PROJECT_TYPE_ID in the first branch and PPTA.PROJECT_TYPE_ID in the second.
  • MANDATORY_FLAG — indicates whether the category must be assigned for that context.
  • AUTOACCOUNTING_FLAG — determines whether accounting is generated automatically for the category.
  • PICK_ONE_CODE_ONLY_FLAG — restricts selection to a single category code.
  • ALLOW_PERCENT_FLAG and TOTAL_100_PERCENT_FLAG — govern percentage-based allocation and whether percentages must total 100.
  • START_DATE_ACTIVE / END_DATE_ACTIVE — the effective date window; the view already filters to the active window at query time.
  • DESCRIPTION — the descriptive text of the class category.

Common Use Cases and Queries

Typical uses include validating which categories a given project type permits, driving LOVs during project creation, and reconciling mandatory category assignments. Because the view already applies the date filter, callers need not repeat it.

List all valid categories for a specific project type:

SELECT class_category, mandatory_flag, description
FROM   pa_valid_categories_v
WHERE  object_type_id = :project_type_id;

Identify mandatory categories not yet configured for a project type:

SELECT class_category
FROM   pa_valid_categories_v
WHERE  object_type_id = :project_type_id
AND    mandatory_flag = 'Y';

Inspect percentage-controlled categories:

SELECT class_category, allow_percent_flag, total_100_percent_flag
FROM   pa_valid_categories_v
WHERE  object_type_id = :project_type_id
AND    (allow_percent_flag = 'Y' OR total_100_percent_flag = 'Y');

These patterns support project setup validation and reporting without re-deriving the underlying validity logic.