Results for “pa_page_layouts”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PA_PAGE_LAYOUTS is a Projects (PA) module configuration table in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the page layouts that define the structure and presentation of Projects-related web pages, one row for each layout created per page type. The seeded page types delivered by Oracle are Project Home and Project Status Report, which are used by the Project Manager Dashboard and related self-service pages. Administrators can define additional page layouts to control which regions, function references, and content blocks appear for a given page type and audience.

From a data modeling perspective, the FK structure of this object is hub-leaning: PA_PAGE_LAYOUTS acts as a central parent record referenced by dependent region and configuration tables, rather than as a transactional or link entity. It functions as a definition or setup hub within the Projects configuration schema.

Key Information Stored

The table contains 15 documented columns, of which the following carry the most functional weight:

• PAGE_ID — the surrogate primary key defined by PA_PAGE_LAYOUTS_PK. It uniquely identifies each page layout and is the join column used by all dependent tables.
• PAGE_NAME — the user-facing name of the layout, and part of the business-key candidate PA_PAGE_LAYOUTS_U2 (PAGE_TYPE_CODE, PAGE_NAME, ZD_EDITION_NAME).
• PAGE_TYPE_CODE — identifies the page category, such as Project Home or Project Status Report, qualifying the layout's purpose and forming the leading column of U2.
• DESCRIPTION — free-text description of the layout's intent or usage.
• START_DATE_ACTIVE / END_DATE_ACTIVE — effective dating that controls the window during which the layout is selectable.
• PERS_FUNCTION_NAME — a foreign key to FND_FORM_FUNCTIONS, binding the layout to the personalized function that renders or grants access to it.
• SHORTCUT_MENU_ID — reference to the shortcut menu presented with the page.
• RECORD_VERSION_NUMBER — optimistic-locking counter used by the applications to detect concurrent updates.
• ZD_EDITION_NAME — the editioning column introduced for Online Patching in 12.2; it participates in both unique indexes (PA_PAGE_LAYOUTS_U1 on PAGE_ID and ZD_EDITION_NAME, and U2).
• Standard audit columns CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN record who inserted or changed the row and when.

Common Use Cases and Queries

Typical usage centers on inventorying layouts and tracing dependencies. To list the active layouts by page type:

• SELECT page_id, page_name, page_type_code, pers_function_name FROM pa.pa_page_layouts WHERE page_type_code = 'PROJECT_HOME' AND (end_date_active IS NULL OR end_date_active > SYSDATE);

To locate the regions belonging to a specific layout, join through PA_PAGE_LAYOUT_REGIONS on PAGE_ID. To determine which task types or project elements use a given progress-entry page, query PA_TASK_TYPES or PA_PROJ_ELEMENTS by TASK_PROGRESS_ENTRY_PAGE_ID. Reporting scenarios include auditing which personalized functions back which layouts, verifying effective-date coverage before upgrades, and isolating custom layouts by comparing CREATED_BY against Oracle-seeded rows. Because ZD_EDITION_NAME is part of the unique keys, queries in 12.2 environments should normally filter or group on the edition to avoid returning duplicate row versions.

Related Objects

The following objects are the most significant dependents and references, per the documented key relationships:

• PA_PAGE_LAYOUT_REGIONS — child table; its PAGE_ID column references PA_PAGE_LAYOUTS, holding the individual regions rendered on each layout.
• FND_FORM_FUNCTIONS — referenced by PA_PAGE_LAYOUTS.PERS_FUNCTION_NAME; identifies the personalized function tied to the layout for security and rendering.
• PA_TASK_TYPES — references PA_PAGE_LAYOUTS via TASK_PROGRESS_ENTRY_PAGE_ID, indicating the layout used for task progress entry.
• PA_PROJ_ELEMENTS — references PA_PAGE_LAYOUTS via TASK_PROGRESS_ENTRY_PAGE_ID for project element progress entry.
• PA_PAGE_LAYOUTS_PK, PA_PAGE_LAYOUTS_U1, PA_PAGE_LAYOUTS_U2 — the primary key and unique constraints that enforce identity, including the edition-aware uniqueness in 12.2.

Together these confirm PA_PAGE_LAYOUTS as the hub that governs page composition and routing for Projects web pages across both 12.1.1 and 12.2.2.