Search Results change_report_status

Overview

APPS.PA_PROGRESS_REPORT_PUB is the public PL/SQL API for the Oracle Projects progress report feature in Oracle E-Business Suite. In the Progress Reporting business flow, project managers, team members, and executives capture structured status information against a project or task over time. The progress report consists of a header (identifying the project, reporting period, and status) plus one or more report regions — parameterized, reusable content blocks that determine what data the report displays and how it is laid out. This package is the single supported entry point for creating and maintaining that reporting structure programmatically, so it is the recommended interface for integrations, extensions, and batch processes rather than direct DML against the underlying Projects tables. The package is declared AUTHID CURRENT_USER, meaning it executes with the privileges of the calling schema, and it follows the standard Oracle EBS API conventions for message handling, validation-only execution, and commit control. The source header identifies the file as PAPRRPPS.pls (version 120.1), confirming this as the Progress Reporting public package delivered in the APPS schema.

Key Procedures and Functions

The package exposes fourteen documented procedures spanning three functional areas.

• Region definition: CREATE_REPORT_REGION creates a new report region, accepting a region source type (defaulting to 'STD'), region code, record sequence, a set of generic attributes, and a user-defined attribute category with associated UDS attributes. UPDATE_REPORT_REGION modifies an existing region definition, and DELETE_REPORT_REGION removes one.
• Report lifecycle: CREATE_REPORT and DELETE_REPORT manage the report header record. UPDATE_REPORT_DETAILS and DEFINE_PROGRESS_REPORT_SETUP support report content and setup configuration.
• Workflow and status: SUBMIT_REPORT, APPROVE_REPORT, REJECT_REPORT, REWORK_REPORT, CANCEL_REPORT, PUBLISH_REPORT, and CHANGE_REPORT_STATUS drive the report through its approval and publishing states, exercising the standard validation and message-queue pattern used across Oracle Projects public APIs.

All procedures are invoked as named API calls; callers are expected to supply the standard control parameters (API version, initialization of the message list, commit flag, validation-only flag, and maximum message count) where applicable.

Tables Accessed

The package operates against the Progress Reporting tables owned by Oracle Projects and accessed through APPS synonyms, principally the progress report header and report region tables, together with their associated user-defined attribute columns. CREATE_REPORT_REGION and its update/delete counterparts write the region definition rows; CREATE_REPORT, UPDATE_REPORT_DETAILS, and DEFINE_PROGRESS_REPORT_SETUP maintain the report header and its setup attributes; and the status-transition procedures update the report status column and related approval data. Because the API validates region codes, source types, and attribute combinations before writing, direct inserts into these tables bypass validation logic and can produce reports that will not render correctly.

Usage Notes

This package is normally invoked from the Oracle Projects Progress Reporting forms, from concurrent programs that generate or publish reports in bulk, and from the workflow background processes that handle submit, approve, and publish transitions. Custom code should call the public procedures only, passing p_validate_only = FND_API.g_true for pre-validation and p_commit = FND_API.g_false when the caller must control transaction boundaries across multiple API calls. The package is referenced by two other packages, indicating that some Progress Reporting processing is layered on top of this API rather than duplicating its logic. Because the source is unchanged since 2005 while the API remains documented at 12.2.2, customers should treat the interface as stable and rely on supported entry points for all extensions.