Results for “approval_description”

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

Overview

PA_PROGRESS_REPORT_SETUP_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, belonging to the Projects (PA) product family. It consolidates progress report configuration data spanning report types, page layouts, approval rules, and billing cycles into a single denormalized row per object page layout. Because progress report setup in Oracle Projects is distributed across several configuration entities, this view serves as the primary read interface for reporting on how progress reports are approved, scheduled, and generated. The view is documented as VALID in ETRM 12.2.2 and is available in both 12.1.1 and 12.2.2 environments.

Its most prominent role involves the approval configuration columns. The column APPROVAL_DESCRIPTION is derived from PA_LOOKUPS where LOOKUP_TYPE = 'PA_PROGRESS_APPRVL_TYPE', joined on the APPROVAL_REQUIRED code. This makes the view the authoritative source for resolving the human-readable approval description from the underlying lookup code, a common requirement in reporting and integration.

Underlying Base Objects

The view is defined over five base objects joined in a single SELECT, with two supplementary package references used for derived values:

• PA_REPORT_TYPES (synonym) — report type definition, providing REPORT_TYPE_ID, NAME, OVERRIDE_PAGE_LAYOUT, and GENERATION_METHOD.
• PA_PAGE_LAYOUTS (synonym) — page definition, supplying PAGE_ID and PAGE_NAME.
• PA_LOOKUPS (view) — lookup values for the PA_PROGRESS_APPRVL_TYPE lookup type, which yields APPROVAL_DESCRIPTION.
• PA_OBJECT_PAGE_LAYOUTS (synonym) — the central configuration table, contributing approval, scheduling, and versioning columns.
• PA_BILLING_CYCLES (synonym) — reporting cycle definition, outer-joined (PBC.BILLING_CYCLE_ID(+)) so rows lacking a cycle are retained.
• PA_RESOURCE_UTILS (package) — GET_RES_NAME_FROM_TYPE resolves APPROVER_NAME from the approver source.
• PA_ACTION_SET_UTILS (package) — GET_ACTION_SET_ID resolves the workflow action set for the progress status report.

Key Columns

• OBJECT_PAGE_LAYOUT_ID — primary identifier for the configuration row; also the key passed to GET_ACTION_SET_ID.
• REPORT_TYPE_ID / REPORT_NAME — the associated report type and its name.
• PAGE_ID / PAGE_NAME / PAGE_TYPE_CODE — the page layout the setup applies to.
• APPROVAL_REQUIRED — the lookup code controlling whether approval is required.
• APPROVAL_DESCRIPTION — the decoded lookup meaning for APPROVAL_REQUIRED.
• APPROVER_SOURCE_ID / APPROVER_SOURCE_TYPE / APPROVER_NAME — the approval routing source and resolved approver name.
• REPORTING_CYCLE_ID / BILLING_CYCLE_NAME — reporting cycle and its descriptive name.
• REPORT_OFFSET_DAYS / NEXT_REPORTING_DATE / REMINDER_DAYS / REMINDER_DAYS_TYPE — scheduling attributes.
• ACTION_SET_ID — workflow action set derived for the status report.

Common Use Cases and Queries

Typical uses include reporting on approval routing, auditing scheduling configuration, and integrating progress report setup into external systems. A query to retrieve all approval configurations is:

• SELECT object_page_layout_id, report_name, page_name, approval_required, approval_description, approver_name FROM pa_progress_report_setup_v WHERE approval_required IS NOT NULL;
• SELECT report_name, billing_cycle_name, next_reporting_date, reminder_days FROM pa_progress_report_setup_v ORDER BY next_reporting_date;

Because APPROVAL_DESCRIPTION depends on the PA_PROGRESS_APPRVL_TYPE lookup, any query that filters on a specific approval description relies on that lookup being populated and active in the environment.