Search Results pa_proj_status_reports

Overview

APPS.PA_PROGRESS_REPORT_SETUP_V is a reporting and integration view in Oracle EBS Projects (PA) that consolidates the configuration of progress report page layouts, their associated report types, approval requirements, approver sourcing, and reporting cycle definitions. It is defined in the APPS schema and is available in both 12.1.1 and 12.2.2. The view joins object-level page layout definitions with report type master data, page definitions, lookup meanings, and billing cycles, producing a single denormalized row per object page layout configuration.

The user search term "pa_progress_apprvl_type" corresponds directly to the lookup type used inside the view. The view joins PA_LOOKUPS on LOOKUP_TYPE = 'PA_PROGRESS_APPRVL_TYPE' and matches LOOKUP_CODE to OPL.APPROVAL_REQUIRED, translating the approval-required code into a descriptive APPROVAL_DESCRIPTION. This makes the view the canonical source for interpreting progress report approval settings without requiring callers to decode the lookup separately.

Underlying Base Objects

The ETRM metadata documents the following referenced base objects:

• PA_OBJECT_PAGE_LAYOUTS (synonym) — the primary driver table holding object-level page layout configuration, including approval, approver, and reporting cycle attributes.
• PA_REPORT_TYPES (synonym) — supplies report type name, override behavior, and generation method.
• PA_PAGE_LAYOUTS (synonym) — supplies page identifier and page name.
• PA_LOOKUPS (view) — resolves the PA_PROGRESS_APPRVL_TYPE lookup code to a description.
• PA_BILLING_CYCLES (synonym) — supplies reporting/billing cycle name; joined with an outer join (+) on REPORTING_CYCLE_ID.
• PA_RESOURCE_UTILS (package) — function GET_RES_NAME_FROM_TYPE resolves the approver name from approver source type and ID.
• PA_ACTION_SET_UTILS (package) — function GET_ACTION_SET_ID returns the action set identifier for the PA_PROJ_STATUS_REPORT / PA_PROJ_STATUS_REPORTS flow keyed by OBJECT_PAGE_LAYOUT_ID.

Key Columns

• OBJECT_PAGE_LAYOUT_ID, OBJECT_ID, OBJECT_TYPE — identity of the underlying layout and its owning object.
• REPORT_TYPE_ID, NAME, OVERRIDE_PAGE_LAYOUT, GENERATION_METHOD — report type attributes.
• PAGE_ID, PAGE_NAME, PAGE_TYPE_CODE — page configuration attributes.
• APPROVAL_REQUIRED — the lookup code matched against PA_PROGRESS_APPRVL_TYPE.
• APPROVAL_DESCRIPTION — decoded meaning of the approval code.
• APPROVER_SOURCE_ID, APPROVER_SOURCE_TYPE, and the derived approver name from PA_RESOURCE_UTILS.GET_RES_NAME_FROM_TYPE.
• REPORTING_CYCLE_ID, BILLING_CYCLE_ID, BILLING_CYCLE_NAME — reporting cycle context.
• REPORT_OFFSET_DAYS, NEXT_REPORTING_DATE, REMINDER_DAYS, REMINDER_DAYS_TYPE — scheduling attributes.
• EFFECTIVE_FROM, EFFECTIVE_TO, RECORD_VERSION_NUMBER — dating and concurrency control.
• ACTION_SET_ID — derived workflow action set for the status report flow.

Common Use Cases and Queries

Typical uses include reporting on configured progress report layouts, identifying which layouts require approval, and validating approver assignments and reporting cycles. A representative query listing approval configuration is:

SELECT object_page_layout_id, name report_type, page_name, approval_required, approval_description, approver_source_id, reporting_cycle_id FROM apps.pa_progress_report_setup_v WHERE approval_required IS NOT NULL ORDER BY name;

To isolate layouts tied to a specific report type and cycle:

SELECT v.object_page_layout_id, v.name, v.billing_cycle_name, v.next_reporting_date FROM apps.pa_progress_report_setup_v v WHERE v.report_type_id = :report_type_id AND v.reporting_cycle_id = :cycle_id;

Because the view exposes the decoded PA_PROGRESS_APPRVL_TYPE lookup and the resolved approver name, it eliminates the need to re-join PA_LOOKUPS and invoke PA_RESOURCE_UTILS in ad hoc reporting queries, making it an efficient integration point for downstream status reporting and workflow validation.