Search Results pa_proj_progress_attr_pkg




Overview
Explore in AI Chat

Overview

The APPS.PA_PROJ_PROGRESS_ATTR_PKG package is a low-level data maintenance package within the Oracle E-Business Suite Projects (PA) module. It manages the persistent attributes that govern how project progress is captured, calculated, and reported for a given project or project structure element. These attributes include the assigned progress cycle, the enabling flags for Work Quantity (WQ), remaining effort, and percent complete, the task weight basis, the next progress update date, and configuration options such as collaborative progress entry and physical percent complete overrides. In effect, the package provides the CRUD (create, update, delete) surface for the PA_PROJ_PROGRESS_ATTR entity, which drives Progress Reporting behavior for capital, contract, and internal projects across Release 12.1.1 and 12.2.2.

The package is classified as an OTHER API, meaning it is not a formally published public API. It backs the progress attribute maintenance logic used internally by the Progress Reporting and Project Management functionality, and it is referenced by two other packages, indicating that it sits beneath higher-level business logic rather than at the application boundary.

Key Procedures and Functions

The package exposes three documented procedures:

  • INSERT_ROW — Creates a new project progress attribute record. It accepts the project identifier, object type, object identifier, audit columns, progress cycle, the various enable flags, next progress update date, task weight basis, collaborative entry and override flags, and structure type. The primary key X_PROJ_PROGRESS_ATTR_ID is passed as an IN OUT NOCOPY parameter, allowing the sequence-generated identifier to be returned to the caller.
  • UPDATE_ROW — Modifies an existing progress attribute record identified by X_PROJ_PROGRESS_ATTR_ID. It updates the configurable attributes, the progress cycle, the enable flags, the next update date, the task weight basis, and the collaborative/override options. It also carries X_RECORD_VERSION_NUMBER, supporting optimistic locking so that concurrent updates are detected. Unlike INSERT_ROW, it does not take the creation audit columns.
  • DELETE_ROW — Removes a progress attribute row. It is keyed by p_row_id (a VARCHAR2 row identifier) rather than the numeric primary key, a convention common to EBS multi-org/rowid-based delete logic.

No public functions are documented beyond these three procedures.

Tables Accessed

The package operates against the following objects, referenced through APPS synonyms:

  • PA_PROJ_PROGRESS_ATTR — The primary transactional table storing project progress attribute definitions. INSERT_ROW, UPDATE_ROW, and DELETE_ROW all write to it.
  • PA_PROJ_PROGRESS_ATTR_S — The corresponding _S (shadow/audit) table, populated for DDL/audit and multi-language or audit trail purposes consistent with Oracle's _S table conventions.
  • DUAL — Used for single-row operations such as sequence retrieval or existence checks.

Usage Notes

Because this package is classified as OTHER and is not a published API, it is normally invoked indirectly by Oracle forms, concurrent programs, and higher-level PL/SQL packages that maintain project progress settings, rather than being called directly by customer extensions. The two packages documented as referencing it depend on this CRUD layer to persist progress configuration.

Custom code should avoid calling these procedures directly to preserve data integrity across the base table and the _S table, and because the interface is subject to change without notice. When extending progress reporting functionality, developers should use the supported Progress Reporting APIs or the standard forms instead. Where direct access is unavoidable, callers must supply all audit columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN) and honor the record version number to maintain concurrency integrity.