Search Results pa_lead_categories_v
Overview
PA_LEAD_CATEGORIES_V is an Oracle Applications (APPS) view within the Projects (PA) product family. It is documented as a VALID object owned by the APPS schema and is classified as a reporting and integration view rather than a transactional entity. Its purpose is to expose lead categorization data—specifically the category identifier, the concatenated hierarchical parentage of a category, and its descriptive text—so that reporting tools, concurrent programs, and integration interfaces can retrieve a flattened, human-readable representation of category hierarchies without navigating recursive parent/child relationships at runtime.
Because the view is defined with a concise projection (CATEGORY_ID, CONCAT_CAT_PARENTAGE, CATEGORY_DESC), it functions as a lightweight access layer. Users searching on "category_desc" typically encounter this view when building inquiries or extract queries that require the descriptive name of a category alongside its hierarchical path, which is common in project costing, expenditure categorization, and hierarchical reporting across the Projects module.
Underlying Base Objects
The documented view text defines PA_LEAD_CATEGORIES_V as a simple SELECT over a single referenced base object:
SELECT CATEGORY_ID, CONCAT_CAT_PARENTAGE, CATEGORY_DESC FROM ENI_PROD_DEN_HRCHY_PARENTS_V
The only documented base object is the view ENI_PROD_DEN_HRCHY_PARENTS_V, also residing in the APPS schema. There are no documented joins to transactional tables, staging tables, or synonyms within the view definition; the relationship is a direct, one-to-one passthrough of the columns exposed by the hierarchy parents view. This design means that PA_LEAD_CATEGORIES_V inherits the filtering and hierarchy logic implemented in ENI_PROD_DEN_HRCHY_PARENTS_V while presenting a narrower column list oriented toward category description lookups.
Key Columns
- CATEGORY_ID — The unique identifier of the category. This is the primary key used to join the view back to category-related entities elsewhere in the Projects data model.
- CONCAT_CAT_PARENTAGE — The concatenated parentage string representing the hierarchical path of the category. It allows consumers to display or filter by ancestor chains without recursive queries.
- CATEGORY_DESC — The descriptive text of the category. This is the column most frequently referenced by users searching for "category_desc", as it supplies the readable name associated with a given CATEGORY_ID.
A further column, CATEGORY, appears in the documented column listing and accompanies the identifier as part of the view's exposed structure.
Common Use Cases and Queries
Typical scenarios include resolving a category ID to its description, filtering categories by hierarchy path, and feeding pick lists or LOV-style result sets in custom reports.
SELECT CATEGORY_ID, CATEGORY_DESC FROM APPS.PA_LEAD_CATEGORIES_V WHERE CATEGORY_DESC LIKE :category_desc;
SELECT CATEGORY_ID,
CONCAT_CAT_PARENTAGE,
CATEGORY_DESC
FROM APPS.PA_LEAD_CATEGORIES_V
ORDER BY CONCAT_CAT_PARENTAGE, CATEGORY_DESC;
Because the view is a passthrough over ENI_PROD_DEN_HRCHY_PARENTS_V, query performance and result consistency depend directly on that underlying hierarchy view, and callers should grant appropriate APPS-schema access when exposing these columns through custom reporting or integration layers.
-
View: PA_LEAD_CATEGORIES_V
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:PA.PA_LEAD_CATEGORIES_V, object_name:PA_LEAD_CATEGORIES_V, status:VALID, product: PA - Projects , implementation_dba_data: APPS.PA_LEAD_CATEGORIES_V ,
-
View: PA_LEAD_CATEGORIES_V
12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:PA.PA_LEAD_CATEGORIES_V, object_name:PA_LEAD_CATEGORIES_V, status:VALID, product: PA - Projects , implementation_dba_data: APPS.PA_LEAD_CATEGORIES_V ,
-
VIEW: APPS.PA_LEAD_CATEGORIES_V
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:PA.PA_LEAD_CATEGORIES_V, object_name:PA_LEAD_CATEGORIES_V, status:VALID,
-
VIEW: APPS.PA_LEAD_CATEGORIES_V
12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:PA.PA_LEAD_CATEGORIES_V, object_name:PA_LEAD_CATEGORIES_V, status:VALID,
-
VIEW: APPS.ENI_PROD_DEN_HRCHY_PARENTS_V
12.2.2
owner:APPS, object_type:VIEW, object_name:ENI_PROD_DEN_HRCHY_PARENTS_V, status:VALID,
-
VIEW: APPS.ENI_PROD_DEN_HRCHY_PARENTS_V
12.1.1
owner:APPS, object_type:VIEW, object_name:ENI_PROD_DEN_HRCHY_PARENTS_V, status:VALID,
-
12.1.1 DBA Data
12.1.1
-
12.2.2 DBA Data
12.2.2
-
12.2.2 FND Design Data
12.2.2
-
12.1.1 FND Design Data
12.1.1
-
APPS.PA_PROJECT_REQUEST_PVT dependencies on PA_PROJECT_STATUSES
12.1.1
-
APPS.PA_PROJECT_REQUEST_PVT dependencies on PA_PROJECT_STATUSES
12.2.2
-
APPS.PA_PROJECT_REQUEST_PVT dependencies on AS_LEADS
12.1.1
-
APPS.PA_PROJECT_REQUEST_PVT dependencies on AS_LEADS
12.2.2
-
APPS.PA_PROJECT_REQUEST_PVT dependencies on PA_OBJECT_RELATIONSHIPS
12.2.2
-
APPS.PA_PROJECT_REQUEST_PVT dependencies on PA_OBJECT_RELATIONSHIPS
12.1.1
-
APPS.PA_PROJECT_REQUEST_PVT dependencies on PA_LOOKUPS
12.1.1
-
APPS.PA_PROJECT_REQUEST_PVT dependencies on PA_LOOKUPS
12.2.2
-
APPS.PA_PROJECT_REQUEST_PVT dependencies on PA_PROJECT_REQUESTS
12.2.2
-
APPS.PA_PROJECT_REQUEST_PVT dependencies on PA_PROJECT_REQUESTS
12.1.1
-
PACKAGE BODY: APPS.PA_PROJECT_REQUEST_PVT
12.2.2
-
PACKAGE BODY: APPS.PA_PROJECT_REQUEST_PVT
12.1.1
-
12.2.2 DBA Data
12.2.2
-
12.1.1 DBA Data
12.1.1
-
eTRM - PA Tables and Views
12.1.1
-
eTRM - PA Tables and Views
12.2.2
-
eTRM - PA Tables and Views
12.1.1
-
eTRM - PA Tables and Views
12.2.2