Search Results master_enabled_flag

Overview

PA_LEAD_CLASSIFICATIONS_V is an Oracle EBS Projects (PA) view owned by the APPS schema and validated in both release 12.1.1 and 12.2.2. It exposes the set of lead classifications — the classification values that can be assigned to projects in the role of a leading or primary classification. The view is a curated, denormalized projection over the interest type and interest code reference data maintained in the Oracle Advanced Pricing / order capture interest type model (AS_INTEREST_TYPES_V and AS_INTEREST_CODES_V), restricted to records where the master-enabled flag and lead-classification flag are both set.

Its practical function is to flatten a three-level hierarchy — interest type, parent interest code, and child interest code — into a single, orderly list of selectable classification values. Because it is defined as a UNION of three SELECT statements, the view returns classifications at each level of the hierarchy, each represented as a slash-delimited compound identifier. This makes it a convenient source for project classification LOVs, reporting, and integration payloads that need a flat list of valid lead classifications rather than a recursive tree.

Underlying Base Objects

The documented base objects referenced by the view are two views in the same schema: AS_INTEREST_CODES_V and AS_INTEREST_TYPES_V. These in turn resolve to the underlying interest type and interest code reference tables, but the ETRM metadata records the view-level dependencies.

The definition is built from three UNION branches:

• Level 1 (type): selects from AS_INTEREST_TYPES_V where MASTER_ENABLED_FLAG = 'Y' and LEAD_CLASSIFICATION_FLAG = 'Y'. The identifier is the interest type ID as a character string.
• Level 2 (parent code): joins AS_INTEREST_TYPES_V to AS_INTEREST_CODES_V on the interest type ID, filtered to child codes where PARENT_INTEREST_CODE_ID IS NULL. The identifier concatenates the interest type ID and interest code ID with a slash.
• Level 3 (child code): joins AS_INTEREST_TYPES_V to a parent and a child instance of AS_INTEREST_CODES_V, resolving the grandchild relationship where the child's parent code ID equals the parent's interest code ID. All three levels must have MASTER_ENABLED_FLAG = 'Y'; the type must additionally satisfy LEAD_CLASSIFICATION_FLAG = 'Y'.

The final result set is ordered by the second column. The dependence on MASTER_ENABLED_FLAG throughout means the view is a master-data filter: only classifications that are active masters in the interest type model are surfaced as lead classifications.

Key Columns

The view exposes three columns as documented:

• CLASSIFICATION_ID — A character representation of the classification key. Depending on the hierarchy level, this is either the interest type ID alone, or the interest type ID concatenated with the parent interest code ID, or the interest type ID concatenated with both parent and child interest code IDs, each separated by a slash (for example, 10, 10/25, 10/25/47).
• CLASSIFICATION_CODE — The user-facing classification name. It is the interest type name, or a slash-delimited combination of the type name and the parent code, or the type name with parent and child codes, mirrored in the same structure as CLASSIFICATION_ID.
• DESCRIPTION — The description of the corresponding interest type or interest code record. For child-level rows the description is taken from the child code; for parent-level rows from the parent code; for type-level rows from the interest type.

Because CLASSIFICATION_ID and CLASSIFICATION_CODE are synthetically derived through TO_CHAR and concatenation, they are not foreign keys to a single table; they encode a path through the classification hierarchy.

Common Use Cases and Queries

Typical uses include populating project setup lists of values, validating inbound classifications during conversion, and driving reports that group projects or tasks (departments, cost centers, or deliverable codes) by lead classification.

A representative query lists all available lead classifications in the standard display order:

• SELECT classification_id, classification_code, description FROM apps.pa_lead_classifications_v ORDER BY classification_code;

Restricting to only the top-level classifications (type-level rows, where the identifier contains no slash) is useful when building a picklist of major classification groups:

• SELECT classification_code FROM apps.pa_lead_classifications_v WHERE classification_id NOT LIKE '%/%';

Recovering the type and code components for a given value is achieved by splitting on the slash character when CLASSIFICATION_ID contains a compound key:

• SELECT classification_id, SUBSTR(classification_id, 1, INSTR(classification_id, '/') - 1) AS type_id FROM apps.pa_lead_classifications_v WHERE classification_id LIKE '%/%;

Because only master-enabled records are exposed, the view automatically excludes disabled or non-master interest types and codes, so callers need not add MASTER_ENABLED_FLAG or LEAD_CLASSIFICATION_FLAG predicates themselves. Any application or interface that previously queried the base interest views directly and filtered on master_enabled_flag can instead query PA_LEAD_CLASSIFICATIONS_V to obtain the same result with the lead-classification restriction applied.