Search Results pa_object_page_layouts_s

Overview

PA_PROGRESS_REPORT_PKG is an APPS-owned PL/SQL package body within the Oracle E-Business Suite Projects (PA) module. It encapsulates the core data manipulation logic that underpins the Progress Reporting feature, which allows project managers and administrators to capture, store, and maintain structured progress reports against projects and project templates. These reports consist of a header-level version record and one or more line-level value records, arranged according to configurable page layouts.

The package is classified as an "OTHER" API rather than a public, interface-oriented API, meaning it is intended primarily for internal consumption by the Progress Reporting forms and related EBS components. It centralizes insert, update, and delete operations for progress report versions, progress report values, and object page layouts, ensuring that the associated tables remain internally consistent and that the surrounding metadata (such as the _S sequence-tracking tables) is maintained in step. Because it is not referenced by any other database object, it functions as a terminal dependency driven by the user interface rather than by other packaged code. The dependency footprint includes common utilities such as FND_API, FND_GLOBAL, and PA_UTILS, together with the standard DUAL and STANDARD constructs.

Key Procedures and Functions

The metadata documents eleven procedures grouped by the entity they manipulate:

• INSERT_PROGRESS_REPORT_VER_ROW — Creates a new version (header) row for a progress report.
• UPDATE_PROGRESS_REPORT_VER_ROW — Modifies an existing progress report version row.
• DELETE_PROGRESS_REPORT_VER_ROW — Removes a progress report version row.
• INSERT_PROGRESS_REPORT_VAL_ROW — Inserts an individual line-level value row belonging to a progress report version.
• UPDATE_PROGRESS_REPORT_VAL_ROW — Updates an existing progress report value row.
• DELETE_PROGRESS_REPORT_VAL_ROW — Deletes a single progress report value row.
• INSERT_OBJECT_PAGE_LAYOUT_ROW — Adds a page layout definition used to render progress report content.
• UPDATE_OBJECT_PAGE_LAYOUT_ROW — Modifies an existing object page layout row.
• DELETE_PROGRESS_REPORT_VALS — Performs a bulk removal of all value rows associated with a given report or version.
• DELETE_PROGRESS_REPORT_REGION — Removes a progress report region, supporting regional deletion semantics.
• DELETE_OBJECT_PAGE_LAYOUTS — Performs a bulk deletion of object page layout rows.

The naming convention reflects a standard pattern: singular row-level operations (INSERT/UPDATE/DELETE_*_ROW) handle one record at a time, while the plural procedures (DELETE_PROGRESS_REPORT_VALS, DELETE_OBJECT_PAGE_LAYOUTS) provide set-based cleanup. Parameter lists are not documented in the ETRM excerpt and should be confirmed against the deployed package specification.

Tables Accessed

The package reads and writes the following application tables through APPS synonyms:

• PA_PROGRESS_REPORT_VERS — Stores progress report version (header) records.
• PA_PROGRESS_REPORT_VERS_S — Sequence-tracking companion table that preserves unique version identifiers across updates.
• PA_PROGRESS_REPORT_VALS — Stores the individual line values that make up a progress report.
• PA_OBJECT_PAGE_LAYOUTS — Defines the page layout configuration used to present progress report content.
• PA_OBJECT_PAGE_LAYOUTS_S — Sequence-tracking companion for the object page layouts table; this is the object referenced by the user's search term.
• DUAL — Used for single-row scalar evaluations, typically to obtain sequence values or constants.

The _S tables are referenced because PA uses the "date-tracked" or surrogate-key pattern, requiring the package to update both the base table and the sequence table in tandem.

Usage Notes

PA_PROGRESS_REPORT_PKG is designed for internal invocation, most commonly from the Progress Reporting Oracle Forms UI whenever a user creates, edits, or removes a progress report, its value lines, or a layout. Bulk deletion procedures support form-level actions that clear all lines or regions in a single operation. While the package is not referenced by other database objects, it may be called from custom extensions or concurrent programs that need to programmatically manage progress report data; developers adopting this approach must respect the same base-table and _S-table update sequencing enforced by the forms to avoid data inconsistency.