Search Results validate_changes
Overview
PA_PROJECT_WF is an Oracle Application Object Library (APPS) PL/SQL package in Oracle E-Business Suite that supports the Oracle Workflow integration for the Project Management module. Its central responsibility is to drive workflow-based routing and status handling for project approval and project lifecycle events within Oracle Projects. The package name reflects its role as the workflow bridge for the PA (Projects) schema: it starts workflow processes, resolves approvers, validates status transitions, and translates workflow outcomes into project status updates.
Within Oracle Projects, projects move through defined statuses (such as Submitted, Approved, and Rejected). When a project is submitted for approval, the application determines the appropriate approver, launches an Oracle Workflow process, and waits for the outcome. PA_PROJECT_WF encapsulates this logic so that the calling forms and public APIs do not embed workflow-specific PL/SQL directly. The package is documented as VALID in the ETRM metadata for both 12.1.1 and 12.2.2, and is classified as an OTHER API, meaning it is not a formally published open interface but is a supporting internal package.
Key Procedures and Functions
The documented package exposes eight procedures and functions:
- SELECT_PROJECT_APPROVER — Determines and returns the approver for a given project approval request, typically by resolving the appropriate user from the approval hierarchy or project setup.
- START_PROJECT_WF — Initiates the Oracle Workflow process associated with project approval or status change, passing the relevant project context to the workflow engine.
- SET_SUCCESS_STATUS — Sets the outcome of a workflow interaction to success, updating the project or status tracking record accordingly.
- SET_FAILURE_STATUS — Sets the outcome of a workflow interaction to failure, recording the unsuccessful result for the project.
- VERIFY_STATUS_CHANGE_RULES — Applies the business rules governing whether a requested project status transition is permitted.
- WF_STATUS_FAILURE — Handles a failure condition arising from the workflow process, ensuring the project is not left in an inconsistent state.
- GET_PROJ_STATUS_ATTRIBUTES — Retrieves the attributes associated with a project status, used to drive workflow decisions and validations.
- VALIDATE_CHANGES — Validates proposed changes to a project before they are committed, guarding against invalid status or data transitions.
Tables Accessed
The package references the following tables through APPS synonyms:
- PA_PROJECTS_ALL — The base project table; read for project attributes and updated to reflect status changes.
- PA_PROJECT_STATUSES — Defines valid project statuses and their characteristics; read when validating transitions.
- PA_OBJ_STATUS_CHANGES_S — The status change tracking table; used to record and review project status history.
- FND_USER — Used to resolve user identity, for example the designated approver.
- DUAL — Used for single-row evaluations in PL/SQL expressions.
Usage Notes
PA_PROJECT_WF is referenced by five other packages, including PA_PROJECTS_MAINT_PUB, PA_PROJECTS_MAINT_PVT, PA_PROJECT_CORE1, PA_PROJECT_PUB, and PJM_SEIBAN_PKG. It is therefore invoked indirectly whenever projects are created, maintained, submitted for approval, or undergo status changes through the standard Oracle Projects forms and public APIs. It is not intended for direct ad hoc invocation; custom code should call the supported public APIs (such as PA_PROJECT_PUB) which in turn delegate to this package. The presence of START_PROJECT_WF and the status helper routines confirms that project approval is workflow-driven, with the Workflow engine notifying this package of success or failure outcomes.
-
PACKAGE: APPS.PA_PROJECT_WF
12.1.1
-
PACKAGE: APPS.PA_PROJECT_WF
12.2.2
-
PACKAGE BODY: APPS.PA_PROJECT_WF
12.1.1
-
PACKAGE BODY: APPS.PA_PROJECT_WF
12.2.2
-
PACKAGE BODY: APPS.PO_RCO_VALIDATION_PVT
12.1.1
-
APPS.PA_PROJECT_WF dependencies on PA_PROJECT_WF
12.2.2
-
PACKAGE BODY: APPS.PO_RCO_VALIDATION_PVT
12.2.2
-
APPS.PA_PROJECT_WF dependencies on PA_PROJECT_WF
12.1.1
-
APPS.PA_PROJECT_WF dependencies on WF_CORE
12.1.1
-
APPS.PA_PROJECT_WF dependencies on WF_CORE
12.2.2
-
APPS.PO_RCO_VALIDATION_PVT dependencies on PO_REQ_CHANGE_ERR_TABLE
12.1.1
-
APPS.PO_RCO_VALIDATION_PVT dependencies on PO_REQ_CHANGE_ERR_TABLE
12.2.2
-
APPS.PO_RCO_VALIDATION_PVT dependencies on POS_CHG_REC_TBL
12.2.2
-
APPS.PO_RCO_VALIDATION_PVT dependencies on POS_CHG_REC
12.2.2
-
PACKAGE BODY: APPS.PO_DOCUMENT_UPDATE_PVT
12.1.1
-
APPS.PO_RCO_VALIDATION_PVT dependencies on POS_CHG_REC
12.1.1
-
PACKAGE BODY: APPS.PO_DOCUMENT_UPDATE_PVT
12.2.2
-
APPS.PO_RCO_VALIDATION_PVT dependencies on POS_CHG_REC_TBL
12.1.1
-
APPS.PO_DOCUMENT_UPDATE_PVT dependencies on PO_CHANGES_REC_TYPE
12.1.1
-
APPS.PO_DOCUMENT_UPDATE_PVT dependencies on PO_CHANGES_REC_TYPE
12.2.2
-
APPS.PO_RCO_VALIDATION_PVT dependencies on FND_API
12.1.1
-
APPS.PO_RCO_VALIDATION_PVT dependencies on FND_API
12.2.2
-
APPS.PO_DOCUMENT_UPDATE_PVT dependencies on PO_DEBUG
12.1.1
-
APPS.PO_DOCUMENT_UPDATE_PVT dependencies on PO_DEBUG
12.2.2
-
APPS.PO_RCO_VALIDATION_PVT dependencies on FND_LOG
12.2.2
-
APPS.PO_DOCUMENT_UPDATE_PVT dependencies on FND_API
12.1.1
-
APPS.PO_RCO_VALIDATION_PVT dependencies on FND_LOG
12.1.1
-
APPS.PO_RCO_VALIDATION_PVT dependencies on PO_CHANGE_REQUESTS
12.1.1
-
APPS.PO_DOCUMENT_UPDATE_PVT dependencies on FND_API
12.2.2
-
APPS.PO_RCO_VALIDATION_PVT dependencies on PO_CHANGE_REQUESTS
12.2.2