Search Results pa_object_page_layouts_pk

Overview

PA_OBJECT_PAGE_LAYOUTS is a Projects (PA) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the associations between page layouts and business objects such as Project or Task. Each row links an object instance to the layout and reporting configuration that governs how status reporting, progress tracking, and approval cycles are presented and processed for that object. The table is owned by the PA schema and holds 26 documented columns.

From a dimensional modeling perspective, the documented foreign key structure suggests a satellite-leaning classification. Because the table's key relationships point outward to reference and function definitions while carrying descriptive and effective-dated attributes about an object's page layout assignment, it functions best as a satellite describing a parent business entity rather than as an independent hub or a pure many-to-many link.

Key Information Stored

The surrogate primary key is OBJECT_PAGE_LAYOUT_ID, enforced through PA_OBJECT_PAGE_LAYOUTS_PK and mirrored by the unique index PA_OBJECT_PAGE_LAYOUTS_U2. The business-key candidate is defined by the composite unique index PA_OBJECT_PAGE_LAYOUTS_U1 over OBJECT_ID, OBJECT_TYPE, PAGE_TYPE_CODE, and REPORT_TYPE_ID, which together identify a layout assignment for a given object and page/report context.

• OBJECT_ID and OBJECT_TYPE — identify the associated business object (for example, a Project or Task) and its type.
• PAGE_TYPE_CODE and PAGE_ID — identify the specific page layout assigned.
• REPORT_TYPE_ID — foreign key to PA_REPORT_TYPES, defining the reporting configuration.
• REPORTING_CYCLE_ID, REPORT_OFFSET_DAYS, NEXT_REPORTING_DATE — drive periodic reporting schedules.
• REMINDER_DAYS and REMINDER_DAYS_TYPE — control reminder timing before reporting deadlines.
• APPROVAL_REQUIRED, APPROVER_SOURCE_ID, APPROVER_SOURCE_TYPE — govern approval routing requirements.
• INITIAL_PROGRESS_STATUS, FINAL_PROGRESS_STATUS, ROLLUP_PROGRESS_STATUS — define progress status mappings.
• EFFECTIVE_FROM and EFFECTIVE_TO — provide effective-dated validity windows.
• PERS_FUNCTION_NAME — foreign key to FND_FORM_FUNCTIONS, linking personalization or function-based behavior.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, and RECORD_VERSION_NUMBER support concurrency and audit tracking.

Common Use Cases and Queries

Typical usage includes determining which layout and reporting cycle applies to a project, auditing approval requirements by object, and reporting on upcoming reporting deadlines. A representative query joins the table to PA_REPORT_TYPES and FND_FORM_FUNCTIONS:

• SELECT p.OBJECT_ID, p.OBJECT_TYPE, p.PAGE_TYPE_CODE, p.NEXT_REPORTING_DATE FROM PA_OBJECT_PAGE_LAYOUTS p WHERE p.OBJECT_TYPE = 'PROJECT' AND SYSDATE BETWEEN p.EFFECTIVE_FROM AND NVL(p.EFFECTIVE_TO, SYSDATE + 1);
• Joining on REPORT_TYPE_ID to PA_REPORT_TYPES to resolve report type descriptions.
• Joining PERS_FUNCTION_NAME to FND_FORM_FUNCTIONS to resolve function metadata.
• Filtering on APPROVAL_REQUIRED to identify objects requiring approval routing.
• Using REMINDER_DAYS and REMINDER_DAYS_TYPE to build notification and reminder reports.

Related Objects

The most significant related objects, based on documented foreign keys and key structure, include:

• FND_FORM_FUNCTIONS — joined via PA_OBJECT_PAGE_LAYOUTS.PERS_FUNCTION_NAME.
• PA_REPORT_TYPES — joined via PA_OBJECT_PAGE_LAYOUTS.REPORT_TYPE_ID.
• PA_PROJECTS_ALL / project entities — referenced through OBJECT_ID when OBJECT_TYPE denotes a project.
• PA_TASKS — referenced through OBJECT_ID when OBJECT_TYPE denotes a task.
• FND_APPLICATION / FND_CURRENCY reference context supporting function and reporting metadata.

Together these relationships establish the page layout assignment as a configurable, effective-dated attribute attached to project and task objects within the Projects reporting framework.