Search Results data_level_int_name

Overview

PA_PROJ_PAGE_REGIONS_V is an APPS-owned, VALID Oracle E-Business Suite view within the Projects (PA) product family. It belongs to a class of ETRM-registered objects intended to expose Projects data to extension and personalization frameworks, specifically the page and region configuration infrastructure consumed by EGO (Oracle E-Business Suite Extensions) pages. The view links Projects entities to dynamically configured page regions by joining project definition data against the EGO_PAGES_V view, which holds the published page metadata.

The view derives its significance from the DATA_LEVEL_INT_NAME column, which carries the internal name of the data level associated with a given page region. This column, together with DATA_LEVEL_DISP_NAME, enables administrators and developers to determine which page regions apply to a specific project, project type, class category, or class code, and to identify the data level context in which those regions execute. This makes the view a useful reference when diagnosing why a particular region appears (or does not appear) on a Projects-related page for a given project configuration.

Because the view is defined with a UNION ALL of three separate SELECT branches, it presents a normalized result set in which each row represents one page region applicable to one project, tagged by a driver type that indicates the routing logic that produced it.

Underlying Base Objects

ETRM documents the following referenced base objects for this view: EGO_PAGES_V (VIEW), PA_CLASS_CATEGORIES (SYNONYM), PA_CLASS_CODES (SYNONYM), PA_PROJECTS_ALL (SYNONYM), PA_PROJECT_CLASSES (SYNONYM), and PA_PROJECT_TYPES (SYNONYM). Each branch of the UNION ALL draws on a distinct subset of these objects.

• PROJECT_TYPE branch: Joins PA_PROJECTS_ALL to PA_PROJECT_TYPES on PROJECT_TYPE and ORG_ID, then to EGO_PAGES_V where the classification code matches 'PROJECT_TYPE:' || PPT.PROJECT_TYPE_ID.
• CLASS_CATEGORY branch: Joins PA_PROJECTS_ALL to PA_PROJECT_CLASSES on PROJECT_ID, then to PA_CLASS_CATEGORIES on CLASS_CATEGORY, then to EGO_PAGES_V where the classification code matches 'CLASS_CATEGORY:' || PCC.CLASS_CATEGORY_ID.
• CLASS_CODE branch: Extends the class category join to PA_CLASS_CODES, matching on both CLASS_CATEGORY and CLASS_CODE, then to EGO_PAGES_V where the classification code matches 'CLASS_CODE:' || PCC.CLASS_CODE_ID.

All three branches return identical column lists, enabling the UNION ALL to assemble a single, consistent shape. The CLASS_CATEGORY branch includes DISTINCT, reflecting the possibility of multiple project class rows resolving to the same category-level page region.

Key Columns

• ORG_ID — Operating unit identifier, propagated from PA_PROJECTS_ALL and PA_PROJECT_TYPES. Supports multi-org filtering and security.
• PROJECT_ID — The project to which the page region applies. This is the primary correlation key back to PA_PROJECTS_ALL.
• DRIVER_TYPE — The literal value emitted by each UNION ALL branch: PROJECT_TYPE, CLASS_CATEGORY, or CLASS_CODE. Identifies the routing basis for the row.
• PAGE_ID, CLASSIFICATION_CODE, INTERNAL_NAME, DISPLAY_NAME, SEQUENCE — Page and region attributes sourced from EGO_PAGES_V. SEQUENCE supports display ordering.
• DATA_LEVEL_INT_NAME — The internal name of the data level associated with the region; this is the column most commonly referenced in targeted searches.
• DATA_LEVEL_DISP_NAME — The user-facing display name corresponding to the data level.

Common Use Cases and Queries

The view is typically used for diagnostics and metadata inspection rather than transactional reporting. A representative query retrieves all page regions for a given project, filtering by data level:

• Identify which regions apply to a project: SELECT PROJECT_ID, DRIVER_TYPE, INTERNAL_NAME, DATA_LEVEL_INT_NAME FROM APPS.PA_PROJ_PAGE_REGIONS_V WHERE PROJECT_ID = :project_id;
• Trace regions by driver type: SELECT DRIVER_TYPE, COUNT(*) FROM APPS.PA_PROJ_PAGE_REGIONS_V WHERE ORG_ID = :org_id GROUP BY DRIVER_TYPE;
• Resolve a data level to its display name: SELECT DISTINCT DATA_LEVEL_INT_NAME, DATA_LEVEL_DISP_NAME FROM APPS.PA_PROJ_PAGE_REGIONS_V;

These queries support troubleshooting of region visibility, extension planning, and validation of Projects page configuration against project classification hierarchies.