Search Results submit_project_aw

Overview

PA_PJP_PVT is a private (PVT-classified) PL/SQL package body owned by APPS in Oracle E-Business Suite, sitting within the Projects (PA/FPA) application family. Its naming and header lineage (PARPJPVB.pls, version 120.0) indicate it is an internal wrapper package used to bridge the public Projects API layer with the underlying processing engine, Fpa_Process_Pvt. The package encapsulates project-related submission and scorecard logic, exposing a thin, standardized API surface that conforms to Oracle's API conventions: an api_version input, an initialization flag, a commit flag, and the standard out parameters for return status, message count, and message data.

The "PVT" suffix denotes a private API classification. Such packages are not intended for direct customer invocation; they exist to shelter the public API contract from internal implementation changes and to consolidate logging behavior. PA_PJP_PVT delegates its real work to Fpa_Process_Pvt through dynamic PL/SQL (EXECUTE IMMEDIATE), meaning the actual business logic resides in Fpa_Process_Pvt while PA_PJP_PVT provides the entry point, signature stability, and diagnostic instrumentation.

Key Procedures and Functions

• Submit_Project_Aw — The principal documented procedure. It accepts the standard API parameter set (p_api_version, p_init_msg_list, p_commit, p_project_id) and returns x_return_status, x_msg_count, and x_msg_data. Its body wraps the private Fpa_Process_Pvt.Submit_Project_Aw routine via EXECUTE IMMEDIATE, passing the project identifier and returning the standard status outputs. This is the procedure most relevant to the user's search term "submit_project_aw."
• proj_scorecard_link_enabled — A function that takes a function name and project ID and returns a VARCHAR2 flag (defaulting internally to 'F'). It dynamically invokes Fpa_Process_Pvt.proj_scorecard_link_enabled to determine whether a project scorecard link should be enabled for the given context.

Both routines are heavily instrumented with FND_LOG calls at LEVEL_PROCEDURE and LEVEL_ERROR, emitting entry/exit trace messages and capturing SQLERRM in the WHEN OTHERS handler. This logging pattern is characteristic of Oracle's diagnostic framework and supports runtime troubleshooting.

Tables Accessed

The ETRM metadata for this package does not document any direct table references via APPS synonyms. All data access is indirect: Submit_Project_Aw and proj_scorecard_link_enabled delegate to Fpa_Process_Pvt, which performs the actual inserts, updates, and queries against the Projects schema. As a result, the effective tables touched—project, scorecard, and related transactional structures—are governed by Fpa_Process_Pvt rather than by PA_PJP_PVT itself. No direct DML or SELECT statements against named tables are present in the wrapper body.

Usage Notes

PA_PJP_PVT is referenced by two other packages within the APPS schema, confirming its role as an internal dependency rather than a standalone public entry point. It is typically invoked indirectly—from a public Projects API or a higher-level processing package—during project submission and scorecard evaluation flows. Because the EXECUTE IMMEDIATE delegation pattern couples it tightly to Fpa_Process_Pvt, both packages must remain synchronized in signature and behavior.

Custom code should not call PA_PJP_PVT directly; the private classification indicates the interface may change without notice. When troubleshooting a "submit_project_aw" issue, developers should trace from the public API into this wrapper and then into Fpa_Process_Pvt, using FND_LOG output to isolate failures. The commit flag (p_commit) and initialization flag (p_init_msg_list) determine transaction control and message stack behavior, so callers should pass them deliberately.