Search Results pick_one_code_only_flag1

Overview

PA_CLASS_CATEGORIES_V is an APPS-owned reporting view in the Oracle E-Business Suite Projects (PA) module, validated across releases 12.1.1 and 12.2.2. It presents the project class categories defined in PA_CLASS_CATEGORIES together with a display-oriented indicator derived from the PICK_ONE_CODE_ONLY_FLAG column. The view restricts output to class categories that are currently active, based on START_DATE_ACTIVE and END_DATE_ACTIVE, so it always reflects the date-effective state of the category set at query time.

Its principal role is to support descriptive Flexfield / value-set definition screens and lookup integrations where a class category must be shown with a visual marker indicating whether only one class code may be selected. The user search term "pick_one_code_only_flag" maps directly to the underlying column of the same name and to the derived column PICK_ONE_CODE_ONLY_FLAG1, which converts the raw Y/N value into a display character. This makes the view particularly relevant when diagnosing why certain class categories appear with an asterisk in Projects setup forms.

Underlying Base Objects

The view is defined over two base objects, both exposed through APPS synonyms:

• PA_CLASS_CATEGORIES — the primary source, supplying CLASS_CATEGORY, DESCRIPTION, START_DATE_ACTIVE, END_DATE_ACTIVE, MANDATORY_FLAG, AUTOACCOUNTING_FLAG, PICK_ONE_CODE_ONLY_FLAG, OBJECT_TYPE, ALLOW_PERCENT_FLAG, TOTAL_100_PERCENT_FLAG, and ALL_TYPES_VALID_FLAG.
• PA_PROJECT_CLASSES — joined with an outer join condition (PPC.CLASS_CATEGORY(+) = PCC.CLASS_CATEGORY), meaning every qualifying class category is returned even when no project class assignment exists.

The join is a correlated outer join, and the WHERE clause applies TRUNC(SYSDATE) BETWEEN PCC.START_DATE_ACTIVE AND NVL(PCC.END_DATE_ACTIVE, SYSDATE), enforcing date-effectiveness. A GROUP BY clause consolidates duplicate rows arising from the outer join, and the ORDER BY clause sorts first by MANDATORY_FLAG descending and then by CLASS_CATEGORY, so mandatory categories are presented at the top of any result set.

Key Columns

• CLASS_CATEGORY — the unique identifier of the class category; primary grouping and ordering key.
• DESCRIPTION — the user-facing name of the category.
• PICK_ONE_CODE_ONLY_FLAG1 — a derived display column produced by DECODE(PCC.PICK_ONE_CODE_ONLY_FLAG, 'Y', ' * ', 'N', ' ', ' '). It renders as a space-padded asterisk when the flag is Y, and as a blank when N or null.
• PICK_ONE_CODE_ONLY_FLAG — the raw Y/N flag indicating that only one class code may be chosen for the category.
• AUTOACCOUNTING_FLAG — controls whether class codes participate in automatic accounting.
• OBJECT_TYPE — identifies the object type to which the category applies.
• ALLOW_PERCENT_FLAG and TOTAL_100_PERCENT_FLAG — govern percentage allocation behavior for class codes.
• ALL_TYPES_VALID_FLAG — indicates whether all object types are valid for the category.

Common Use Cases and Queries

The view is typically queried to populate LOVs, validate setup data, or report on class category configuration. A common diagnostic query isolates the pick-one behavior:

• SELECT class_category, description, pick_one_code_only_flag, pick_one_code_only_flag1 FROM pa_class_categories_v ORDER BY class_category;
• SELECT class_category, description FROM pa_class_categories_v WHERE pick_one_code_only_flag = 'Y';
• SELECT class_category, object_type, allow_percent_flag, total_100_percent_flag FROM pa_class_categories_v WHERE all_types_valid_flag = 'N';

Because the view enforces date-effectiveness and suppresses expired categories, it is preferred over direct queries against PA_CLASS_CATEGORIES when current configuration is required. Integration developers should note that PICK_ONE_CODE_ONLY_FLAG1 is a formatted presentation column and should not be used for logic; comparisons must use PICK_ONE_CODE_ONLY_FLAG with its Y/N domain.