Search Results delete_object_page_layouts

Overview

PA_PROGRESS_REPORT_PKG is an internal PL/SQL package in the APPS schema that supports the Oracle Projects progress reporting feature set. Progress reports in Oracle EBS allow project managers to capture period-based project status, including physical percent complete, financial and schedule performance narratives, and structured reporting data used for earned value and project performance analysis. The package functions as a low-level data access and maintenance layer, providing the transaction-level operations that create, modify, and remove progress report records and their associated page layout configuration.

The package is classified as an "OTHER" API type within the ETRM metadata, indicating that it is not a published, supported public API intended for direct customer invocation. It is instead a worker package whose procedures are called by higher-level packages and forms that orchestrate progress report maintenance. Its business role is to encapsulate the mechanical insert, update, and delete operations against the progress report version, value, and page layout tables, thereby centralising persistence logic for progress reporting data.

The package carries the VALID status under the APPS schema, confirming that it is compiled and deployed in both Oracle EBS 12.1.1 and 12.2.2 environments as part of the Oracle Projects (PA) product family.

Key Procedures and Functions

The documented interface comprises eleven procedures, organised into three logical groups.

• Version maintenance — INSERT_PROGRESS_REPORT_VER_ROW, UPDATE_PROGRESS_REPORT_VER_ROW, and DELETE_PROGRESS_REPORT_VER_ROW manage individual rows in the progress report version structure. Versions represent successive revisions of a progress report, and these routines handle their creation, amendment, and removal.
• Value maintenance — INSERT_PROGRESS_REPORT_VAL_ROW and UPDATE_PROGRESS_REPORT_VAL_ROW create and modify the individual reported values (such as percent complete figures or narrative entries) associated with a progress report. DELETE_PROGRESS_REPORT_VALS removes value rows, typically in a set for a given report context.
• Page layout maintenance — INSERT_OBJECT_PAGE_LAYOUT_ROW, UPDATE_OBJECT_PAGE_LAYOUT_ROW, and DELETE_OBJECT_PAGE_LAYOUTS manage the configurable page layout definitions that govern how progress report information is presented. DELETE_PROGRESS_REPORT_REGION removes a defined region from the progress report layout configuration.

Each procedure performs a narrowly scoped persistence operation; parameter lists are not published in the ETRM extract and should not be assumed.

Tables Accessed

The package operates on five documented base tables, all reached through APPS synonyms, plus DUAL for lightweight SQL support.

• PA_PROGRESS_REPORT_VERS and PA_PROGRESS_REPORT_VERS_S — the progress report version header and its translation (TL) table, holding version definitions and associated descriptive attributes.
• PA_PROGRESS_REPORT_VALS — the detail table storing individual progress report values and entries linked to a version.
• PA_OBJECT_PAGE_LAYOUTS and PA_OBJECT_PAGE_LAYOUTS_S — the page layout and translation tables that define how progress report content is arranged in the reporting user interface.
• DUAL — used for scalar expressions and sequence-related lookups within the PL/SQL logic.

Usage Notes

PA_PROGRESS_REPORT_PKG is an internal dependency rather than a public API. The ETRM metadata records that it is referenced by four other packages: PA_PAGE_LAYOUT_UTILS, PA_PROGRESS_REPORT_PVT, PA_PROGRESS_REPORT_UTILS, and PA_PROGRESS_UTILS, with PA_PROGRESS_REPORT_PVT acting as the primary private-layer consumer. It is invoked indirectly by the Oracle Projects progress report forms and by any concurrent processing or utility routines that create or maintain progress reports.

Custom code should not call this package directly; Oracle does not guarantee its signature across patches or upgrades. Integrations requiring progress report creation should use the supported Oracle Projects public APIs, and direct DML against the underlying tables should be avoided in favour of the packaged logic that this module encapsulates.