Search Results concat_cat_parentage
Overview
APPS.PA_LEAD_CATEGORIES_V is a lightweight reporting view in Oracle E-Business Suite that exposes a hierarchical listing of lead (parent) project and resource categories. It is defined in the APPS schema and referenced under the Projects (PA) module naming convention, but its actual data is drawn entirely from the underlying view ENI_PROD_DEN_HRCHY_PARENTS_V. The view presents three columns: CATEGORY_ID, CONCAT_CAT_PARENTAGE, and CATEGORY_DESC. Its principal value lies in the CONCAT_CAT_PARENTAGE column, which delivers a concatenated, human-readable path describing a category's position within its parentage hierarchy.
Because it is a simple pass-through view over another view, PA_LEAD_CATEGORIES_V carries no independent storage, no materialized copy of data, and no trigger or package logic. Its role is therefore purely presentational: it provides a stable, project-namespace alias through which report writers, concurrent program queries, and integration extracts can retrieve category hierarchy paths without referencing the lower-level ENI_DEN/ENI_PROD_DEN objects directly. This behavior is consistent between EBS 12.1.1 and 12.2.2, since the object is a view rather than a schema-level table whose definition changed across those releases.
Underlying Base Objects
The ETRM metadata documents exactly one referenced base object:
- ENI_PROD_DEN_HRCHY_PARENTS_V (VIEW) — the sole source of all three selected columns.
The view definition is a direct SELECT over that object with no joins, filters, grouping, or DISTINCT clause, so its cardinality and row content are identical to those of ENI_PROD_DEN_HRCHY_PARENTS_V. Column names and data types are inherited unchanged. As a consequence, any restriction, security predicate, or denormalization present in the parent view flows through to PA_LEAD_CATEGORIES_V automatically. The ENI_PREFIX naming indicates the object belongs to the Extensible Network Infrastructure / hierarchy utility family rather than to the canonical PA_CATEGORIES or PA_CATEGORY_SETS tables; the parentage results it exposes are therefore the output of that hierarchy utility rather than a direct read of the project category setup tables.
Key Columns
- CATEGORY_ID — the numeric identifier of the category or category set member. It is the join key back to category definition tables and is the column most often used in correlated subqueries or lookup joins.
- CONCAT_CAT_PARENTAGE — the delimited concatenation of ancestor category names (or identifiers) forming the full parentage path for the current node. This is the column users target when they search for "concat_cat_parentage": it allows a single-row read of an entire hierarchy branch without a recursive CONNECT BY query.
- CATEGORY_DESC — the descriptive text for the category itself, suitable for display in reports, list-of-values, and extract files.
Note that no FLEX_VALUE, enabled-flag, or effective-date columns are exposed, so filtering by status or date range must be applied either in the parent view or against the underlying category tables.
Common Use Cases and Queries
Typical scenarios include producing parentage-level rollups for project cost or resource reporting, feeding descriptive hierarchy paths into BI Publisher layouts, and validating that category parentage has been built correctly before period close.
Simple listing of all categories with their parentage path:
SELECT category_id, concat_cat_parentage, category_desc FROM apps.pa_lead_categories_v;
Resolving the parentage for a specific category:
SELECT concat_cat_parentage, category_desc FROM apps.pa_lead_categories_v WHERE category_id = :p_category_id;
Because the view is unindexed and unfiltered, broad queries against it in 12.1.1 or 12.2.2 will scan the full output of ENI_PROD_DEN_HRCHY_PARENTS_V. Where the parent view is expensive to evaluate, consider materializing the result into a custom table refreshed on a schedule, and always qualify the object with its APPS schema owner when querying from a non-APPS login.
-
VIEW: APPS.PA_LEAD_CATEGORIES_V
12.2.2
-
VIEW: ENI.ENI_DENORM_HRCHY_PARENTS#
12.2.2
-
VIEW: APPS.PA_LEAD_CATEGORIES_V
12.1.1
-
TABLE: ENI.ENI_DENORM_HRCHY_PARENTS
12.1.1
owner:ENI, object_type:TABLE, object_name:ENI_DENORM_HRCHY_PARENTS, status:VALID,
-
TABLE: ENI.ENI_DENORM_HRCHY_PARENTS
12.2.2
owner:ENI, object_type:TABLE, object_name:ENI_DENORM_HRCHY_PARENTS, status:VALID,
-
VIEW: ENI.ENI_DENORM_HRCHY_PARENTS#
12.2.2
owner:ENI, object_type:VIEW, object_name:ENI_DENORM_HRCHY_PARENTS#, status:VALID,
-
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: 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: 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,
-
View: AMS_DS_ORDERS_V
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:AMS.AMS_DS_ORDERS_V, object_name:AMS_DS_ORDERS_V, status:VALID, product: AMS - Marketing , implementation_dba_data: APPS.AMS_DS_ORDERS_V ,
-
View: AMS_DS_INSTALL_BASE_V
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:AMS.AMS_DS_INSTALL_BASE_V, object_name:AMS_DS_INSTALL_BASE_V, status:VALID, product: AMS - Marketing , implementation_dba_data: APPS.AMS_DS_INSTALL_BASE_V ,
-
View: AMS_DS_SALES_LEADS_V
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:AMS.AMS_DS_SALES_LEADS_V, object_name:AMS_DS_SALES_LEADS_V, status:VALID, product: AMS - Marketing , implementation_dba_data: APPS.AMS_DS_SALES_LEADS_V ,
-
PACKAGE: APPS.AS_SCN_FORECAST_PUB
12.2.2
-
PACKAGE: APPS.AS_SCN_FORECAST_PUB
12.1.1
-
APPS.ENI_DENORM_HRCHY SQL Statements
12.2.2
-
APPS.QP_PRICE_BOOK_UTIL SQL Statements
12.1.1
-
APPS.ENI_DENORM_HRCHY SQL Statements
12.1.1
-
APPS.IBC_UTILITIES_PVT SQL Statements
12.1.1
-
APPS.QP_PRICE_BOOK_UTIL SQL Statements
12.2.2
-
APPS.AS_INT_TYP_COD_MIGRATION SQL Statements
12.1.1
-
APPS.IBC_UTILITIES_PVT SQL Statements
12.2.2
-
APPS.AS_INT_TYP_COD_MIGRATION SQL Statements
12.2.2
-
APPS.QP_PRICE_BOOK_UTIL dependencies on ENI_PROD_DEN_HRCHY_PARENTS_V
12.1.1
-
APPS.QP_PRICE_BOOK_UTIL dependencies on ENI_PROD_DEN_HRCHY_PARENTS_V
12.2.2
-
PACKAGE BODY: APPS.ENI_DENORM_HRCHY
12.2.2
-
PACKAGE BODY: APPS.ENI_DENORM_HRCHY
12.1.1
-
PACKAGE BODY: APPS.IBC_UTILITIES_PVT
12.1.1
-
PACKAGE BODY: APPS.IBC_UTILITIES_PVT
12.2.2
-
APPS.AS_INT_TYP_COD_MIGRATION dependencies on ENI_PROD_DEN_HRCHY_PARENTS_V
12.1.1
-
APPS.AS_INT_TYP_COD_MIGRATION dependencies on ENI_PROD_DEN_HRCHY_PARENTS_V
12.2.2
-
APPS.QP_PRICE_BOOK_UTIL dependencies on MTL_CATEGORIES_KFV
12.2.2
-
APPS.QP_PRICE_BOOK_UTIL dependencies on MTL_CATEGORIES_KFV
12.1.1
-
APPS.ENI_DENORM_HRCHY dependencies on ENI_DENORM_HRCHY_PARENTS
12.1.1
-
APPS.ENI_DENORM_HRCHY dependencies on ENI_DENORM_HRCHY_PARENTS
12.2.2
-
PACKAGE BODY: APPS.QP_PRICE_BOOK_UTIL
12.1.1
-
PACKAGE BODY: APPS.QP_PRICE_BOOK_UTIL
12.2.2
-
PACKAGE BODY: APPS.AS_INT_TYP_COD_MIGRATION
12.2.2
-
PACKAGE BODY: APPS.AS_INT_TYP_COD_MIGRATION
12.1.1
-
APPS.IBC_UTILITIES_PVT dependencies on FND_API
12.1.1
-
APPS.IBC_UTILITIES_PVT dependencies on FND_API
12.2.2
-
APPS.ENI_DENORM_HRCHY dependencies on ENI_DENORM_HRCHY
12.2.2
-
APPS.ENI_DENORM_HRCHY dependencies on ENI_DENORM_HRCHY
12.1.1