Search Results pa_object_page_layouts_n3

Overview

PA.PA_OBJECT_PAGE_LAYOUTS is an operational table in the Oracle E-Business Suite Projects (PA) schema that stores the association between page layouts and project objects. An "object" in this context is typically a project or a task, and the table records which progress-reporting layout, reporting cycle, approval behavior, and progress status configuration applies to that object. It is central to the Progress Workbench and related Project Management functionality in EBS 12.1.1 and 12.2.2, where it drives how progress reports are generated, offset, approved through Workflow, and rolled up across the project hierarchy.

The documented primary key is PA_OBJECT_PAGE_LAYOUTS_PK on OBJECT_PAGE_LAYOUT_ID. Based on the foreign key structure and the nature of the columns, the ETRM heuristic classifies this object as satellite-leaning in a Data Vault model. This is a modeling suggestion rather than a physical EBS construct: the table behaves primarily as a descriptive satellite attached to the object and layout it references, with business keys carried by the unique indexes rather than a single natural hub key.

Key Information Stored

The table holds 26 documented columns. The most significant are:

• OBJECT_PAGE_LAYOUT_ID — surrogate primary key (unique index PA_OBJECT_PAGE_LAYOUTS_U2).
• OBJECT_ID, OBJECT_TYPE, PAGE_TYPE_CODE, REPORT_TYPE_ID — the composite business key enforced by unique index PA_OBJECT_PAGE_LAYOUTS_U1. OBJECT_TYPE identifies the object class such as PA_PROJECTS, while PAGE_TYPE_CODE identifies the page type such as PPR or PH.
• PAGE_ID — identifier of the page layout, indexed by PA_OBJECT_PAGE_LAYOUTS_N1.
• REPORTING_CYCLE_ID — reporting cycle used by the project, indexed by PA_OBJECT_PAGE_LAYOUTS_N3.
• APPROVAL_REQUIRED — flag indicating whether Workflow approval is required for the progress report.
• REPORT_OFFSET_DAYS, NEXT_REPORTING_DATE, REMINDER_DAYS, REMINDER_DAYS_TYPE — scheduling and reminder controls, including whether weekdays or business days are used for reminder computation.
• INITIAL_PROGRESS_STATUS, FINAL_PROGRESS_STATUS, ROLLUP_PROGRESS_STATUS — progress lifecycle state values.
• EFFECTIVE_FROM, EFFECTIVE_TO — date-ranged validity of the layout assignment.
• RECORD_VERSION_NUMBER — optimistic locking for self-service applications.
• LAST_UPDATED_BY, CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns.

Common Use Cases and Queries

Typical uses include identifying the configured layout for a given project or task, reporting on reporting cycles and next report dates, and auditing approval and reminder settings.

• Retrieve layouts for a specific project: SELECT * FROM pa_object_page_layouts WHERE object_id = :project_id AND object_type = 'PA_PROJECTS';
• List objects requiring Workflow approval: SELECT object_id, page_type_code, report_type_id FROM pa_object_page_layouts WHERE approval_required = 'Y';
• Find layouts by reporting cycle using index N3: SELECT object_id, next_reporting_date FROM pa_object_page_layouts WHERE reporting_cycle_id = :cycle_id;
• Filter by effective dates for point-in-time reporting: WHERE :as_of_date BETWEEN effective_from AND NVL(effective_to, :as_of_date);

Related Objects

• PA_REPORT_TYPES — referenced via REPORT_TYPE_ID; defines the report type applied to the layout.
• FND_FORM_FUNCTIONS — referenced via PERS_FUNCTION_NAME, tying the layout to a personalized function.
• PA_PROJECTS / PA_TASKS — implied referenced objects identified through OBJECT_ID and OBJECT_TYPE.
• PA_REPORTING_CYCLES — source of REPORTING_CYCLE_ID values.
• PA_PAGE_LAYOUTS — source of PAGE_ID values.
• PA_OBJECT_PAGE_LAYOUTS_PK, _U1, _U2, _N1–_N3 — indexes supporting access paths and uniqueness.