Search Results change_management_baseline




Overview
Explore in AI Chat

Overview

PA_BASELINE_FUNDING_PKG is a public PL/SQL package owned by APPS in the Oracle E-Business Suite Projects (PA) module. Its central business function is the creation and management of budget baselines and funding baselines for projects. In Oracle Projects terminology, a baseline is an approved, frozen snapshot of a project's budget or funding plan against which subsequent changes, revisions, and actual costs are measured. Baselining locks a version of the budget or funding so that performance and variance reporting can be produced reliably while the project continues to evolve.

The package is declared with AUTHID CURRENT_USER, meaning that its procedures execute with the privileges of the calling schema rather than the package owner. This is consistent with EBS standards for API packages that must enforce the invoker's security context on the underlying project and funding data. The documented source header dates from 2005, and the package forms part of the long-standing Projects baseline infrastructure that persists into release 12.1.1 and 12.2.2. It exposes five documented procedures: CREATE_DRAFT, CREATE_LINE, CREATE_BUDGET_BASELINE, PROJ_AGREEMENT_BASELINE, and CHANGE_MANAGEMENT_BASELINE. It is referenced by three other packages, indicating it is a dependency for higher-level project budgeting and funding functionality rather than an end-user entry point.

Key Procedures and Functions

  • CREATE_DRAFT — Creates a draft budget or funding version for a project over a specified date range and resource list. It returns a version identifier along with error code and status outputs, providing the working version that later steps in the baseline flow can populate.
  • CREATE_LINE — Creates an individual budget or funding line for a project, associated with a specific resource list member and budget version, across a defined date range. It supports line-by-line construction of the version prepared by CREATE_DRAFT.
  • CREATE_BUDGET_BASELINE — The procedure most closely associated with the user's search term. It establishes the budget baseline for a given project, promoting the approved budget version into a baselined state. It accepts a project identifier and returns error code and status outputs.
  • PROJ_AGREEMENT_BASELINE — Baselined only the funding lines belonging to a specified project agreement. This procedure was introduced from the FP_M release onward and operates at the agreement level rather than the whole-project level.
  • CHANGE_MANAGEMENT_BASELINE — Baselined only the funding lines created through the change order management page. It accepts a project identifier and a table of change instruction identifiers, allowing selective baselining of change-driven funding entries.

Tables Accessed

The package reads and writes several core Projects tables through APPS synonyms. PA_PROJECTS_ALL and PA_TASKS supply project and task context. PA_BUDGET_VERSIONS stores the budget version records created and baselined by the package. PA_RESOURCE_LIST_MEMBERS identifies the resource list members used when constructing budget or funding lines. PA_PROJECT_FUNDINGS holds the funding line records that PROJ_AGREEMENT_BASELINE and CHANGE_MANAGEMENT_BASELINE baseline. PA_PROJ_FP_OPTIONS and PA_IMPLEMENTATIONS provide project-level and installation-level configuration that governs baseline behavior. PLITBLM is the standard Oracle PL/SQL table type used to pass identifier collections such as the change instruction table accepted by CHANGE_MANAGEMENT_BASELINE.

Usage Notes

PA_BASELINE_FUNDING_PKG is an internal Projects API package. It is not typically invoked directly by end users; instead it is called by Oracle Projects forms, concurrent programs, and other packages that drive the budget and funding baseline workflow. The dependence of three other packages on this one confirms its role as a shared service layer. Customizations and extensions that need to baseline project budgets or funding should call these documented procedures rather than writing directly to PA_BUDGET_VERSIONS or PA_PROJECT_FUNDINGS, since the procedures enforce the validation, status handling, and integration logic required for consistent results. Callers should always inspect the returned error code and status values, and should run baselining within the appropriate project security context given the package's AUTHID CURRENT_USER declaration.