Search Results pa_budget_core1




Overview
Explore in AI Chat

Overview

PA_BUDGET_CORE1 is an Oracle Projects (PA) budget processing package that provides the core PL/SQL logic for copying, accumulating, and rolling up project budget data in Oracle EBS 12.1.1 and 12.2.2. It acts as a server-side engine invoked by Oracle Projects budget forms, concurrent programs, and dependent packages during budget creation and maintenance. The package encapsulates two broad categories of work: (1) populating budget versions from actuals or from existing draft budget lines, and (2) resolving reporting period information that governs how resource amounts are accumulated and displayed. APPS.PA_BUDGET_CORE1 is classified as an OTHER API rather than a public, supported interface, but it is referenced by two other packages, indicating its role as a shared internal utility. The documented source references revision 120.3.12010000.3 and carries fix markers for several historical bugs, including 4390421 and 4889056, which introduced the accumulation-period function and related record structures.

Key Procedures and Functions

  • COPY_ACTUAL — Copies actual project cost and quantity balances into a target budget version, filtered by budget entry method, resource list, and a range delimited by start and end periods. It returns standard error code, stage, and stack outputs.
  • COPY_DRAFT_LINES — Copies budget lines from a source version to a destination version. Parameters govern the time-phased type, entry level, and a project-manager flag that influences which lines qualify for transfer.
  • GET_FIRST_ACCUM_PERIOD — A function that returns the first accumulation period (as a date) for a given project and budget type. It is documented as a wrapper over PA_ACCUM_UTILS.GET_FIRST_ACCUM_PERIOD and is specifically intended for use in a value set so that users select a valid starting period. This is the object referenced by the search term "get_first_accum_period."
  • COPY_ACTUALS1 — A wrapper procedure over copy_actual designed to be submitted as a concurrent request, using the standard errbuf and retcode signatures.
  • ROLLUP_AMOUNTS_RG — Supports rollup of budget amounts; it appears in the documented procedure list and operates in conjunction with the accumulation and period logic used elsewhere in the package.

Tables Accessed

The package reads and writes a broad set of Projects and General Ledger tables through APPS synonyms. PA_PROJECTS_ALL, PA_BUDGET_VERSIONS, and PA_BUDGET_TYPES supply project and version context. PA_PERIODS_ALL and PA_PERIODS provide the period definitions used to compute the first accumulation period and to filter copies by date range, while GL_PERIOD_STATUSES supplies ledger period status. PA_RESOURCES, PA_RESOURCE_LISTS_ALL_BG, PA_RESOURCE_ASSIGNMENTS, and PA_RESOURCE_ASSIGNMENTS_S define the resource structure for budget lines, with PA_RESOURCE_ACCUM_DETAILS holding accumulated amounts. PA_BUDGET_LINES stores the budget line data being copied, and PA_BUDGET_ENTRY_METHODS determines the entry method applied. PA_FP_BL_MAP_TMP serves as a temporary mapping table during processing, and PA_IMPLEMENTATIONS holds installation-level settings.

Usage Notes

PA_BUDGET_CORE1 is invoked primarily from the Oracle Projects budget entry forms and from concurrent programs that copy actuals into budgets. The get_first_accum_period function is called from an Oracle Forms value set, and the source notes explicitly mention performance-tuning globals (g_project_id, g_budget_type_code, g_start_period_date, and g_calling_mode, which defaults to 'FORM') added to cache values between calls from that value set. Custom code should treat these procedures as internal and unsupported; direct invocation risks conflict with Oracle's own form logic. When integration is required, the concurrent-program wrapper COPY_ACTUALS1 is the safer documented entry point because it follows the standard errbuf/retcode convention.