Search Results pa_budget_core




Overview
Explore in AI Chat

Overview

APPS.PA_BUDGET_CORE is a core PL/SQL package within the Oracle Projects (PA) module of Oracle E-Business Suite, present in both the 12.1.1 and 12.2.2 releases. It encapsulates the low-level business logic that governs project budget versions and budget lines throughout their lifecycle. Rather than exposing a user-facing interface, PA_BUDGET_CORE provides the shared procedural foundation on which higher-level budget APIs and concurrent programs depend.

The package is classified as an "OTHER" API, meaning it is not published as a formally supported public interface but is instead consumed internally by Oracle's own budget-related packages. Its documented status is VALID in the APPS schema, and it comprises both a package specification and a package body. Its principal responsibilities include establishing budget baselines, copying budget structures and lines between versions, verifying budget integrity, shifting budget amounts across accounting periods, and resolving the period ranges applicable to a given project budget.

Key Procedures and Functions

The documented interface exposes seven procedures and functions:

  • BASELINE — Establishes a budget version as the baseline, marking it as the approved reference against which subsequent revisions are compared.
  • COPY — Duplicates an existing budget version, including its associated structure and lines, to create a new working version.
  • COPY_WITHOUT_DELETE — Performs a copy operation while preserving the source records rather than removing them, allowing non-destructive duplication of budget data.
  • COPY_LINES — Copies only the individual budget line records, typically used when the version header already exists or is managed separately.
  • VERIFY — Validates budget data for consistency and completeness, ensuring that versions and lines conform to expected project and period relationships.
  • SHIFT_PERIODS — Repositions budget amounts from one set of accounting periods to another, supporting rollover and rephasing requirements.
  • GET_PERIODS — Retrieves the applicable period ranges for a budget, drawing on project and implementation settings.

Tables Accessed

PA_BUDGET_CORE reads and writes a defined set of tables through APPS synonyms. Budget versions and their secure counterparts are managed via PA_BUDGET_VERSIONS and PA_BUDGET_VERSIONS_S, while the line-level detail resides in PA_BUDGET_LINES and PA_BUDGET_LINES_S. Entry method configuration is drawn from PA_BUDGET_ENTRY_METHODS. Period logic relies on PA_PERIODS and GL_PERIOD_STATUSES, with temporary working storage provided by PA_FP_CPY_PERIODS_TMP and PA_FP_BL_MAP_TMP. Project and resource context comes from PA_PROJECTS_ALL, PA_PROJECT_TYPES_ALL, PA_RESOURCE_ASSIGNMENTS, PA_RESOURCE_ASSIGNMENTS_S, and the PA_IMPLEMENTATIONS / PA_IMPLEMENTATIONS_ALL configuration tables.

Usage Notes

This package is not intended for direct invocation by end users or typical customizations. It is referenced by six other packages, including PA_BASELINE_FUNDING_PKG, PA_BUDGET_PUB, PA_BUDGET_UTILS, PA_FP_COPY_FROM_PKG, PA_FP_ORG_FCST_GEN_PUB, and PA_YEAR_END_ROLLOVER_PKG, and is also self-referenced internally. These consumers drive budget baseline, copy, forecast generation, and year-end rollover operations from Oracle Projects forms and concurrent programs. Developers extending budget functionality should generally call the public wrappers (such as PA_BUDGET_PUB) rather than PA_BUDGET_CORE directly, since the package is documented as an internal, unsupported interface whose signature may change across patches.