Search Results maintain_budget_lines




Overview
Explore in AI Chat

Overview

PA_FP_WP_GEN_BUDGET_AMT_PUB is a public PL/SQL API within the Oracle E-Business Suite Projects (PA) module that supports budget generation from workplan resources. Its principal role is to take resource assignments defined in a project workplan and translate them into budget amounts and budget lines against a specified budget version. In effect, the package bridges the planning side of a project (resource assignments, financial plan options, plan types) and the budgetary side (budget versions and budget lines), automating what would otherwise be a manual, error-prone amount derivation process.

The package is classified as a PUB (public) API, meaning it is intended for supported external invocation from forms, concurrent programs, and custom extensions. It interacts primarily with financial plan options (PA_PROJ_FP_OPTIONS) and budget versions (PA_BUDGET_VERSIONS) to determine the source of generation, the target budget version, and related calculation parameters. The "_PUB" suffix and formal OUT parameters (return status, message count, and message data) confirm that it is a designed integration point rather than internal utility code.

Key Procedures and Functions

Three documented program units constitute the public interface:

  • GENERATE_WP_BUDGET_AMT — The central procedure. It generates workplan-derived budget amounts for a given project and budget version using a source code (defaulting to WORKPLAN_RESOURCES), plan class (defaulting to 'Budget'), cost plan type and version, and numerous flags controlling manual amount retention, change documents, billing events, open commitments, commit behavior, and initial messaging. It also exposes ETC (estimate-to-complete) plan type, version, name, and an actuals-through date, allowing the caller to shape how amounts are derived. It returns deleted and generated resource assignment ID tables plus a standard status/message triple.
  • MAINTAIN_BUDGET_LINES — Manages budget line data by copying or reconciling lines from a source budget version to a target budget version. It accepts a calling context and an actuals parameter, supporting workflows where an existing budget baseline must be propagated or refreshed into a new version reflecting the generated amounts.
  • GET_CALC_API_FLAG_PARAMS — A function that retrieves calculation API flag parameters, governing how the calculation engine behaves during generation. It supplies configuration values consumed by the generation and line-maintenance processes.

Tables Accessed

The package reads and writes a tightly scoped set of project and financial plan objects. Budget definition and versioning rely on PA_BUDGET_VERSIONS, PA_BUDGET_LINES, and PA_BUDGET_LINES_S (the base table plus its secondary/audit companion). Plan configuration comes from PA_FIN_PLAN_TYPES_B and PA_PROJ_FP_OPTIONS. Source assignment data is drawn from PA_RESOURCE_ASSIGNMENTS, PA_RESOURCE_ASGN_CURR (current resource assignments), PA_RESOURCE_ASGN_CURR_TMP, and PA_RESOURCE_LISTS_ALL_BG / PA_RESOURCE_LIST_MEMBERS, which define resource lists and their membership.

Working and calculation staging structures include PA_FP_CALC_AMT_TMP2, PA_FP_GEN_RATE_TMP, and PA_FP_RES_ASSIGNMENTS_TMP, used to hold intermediate amounts, generated rates, and assignment snapshots during execution. Period and project context is supplied by PA_PERIODS_ALL (notably for the actuals-through date) and PA_PROJECTS_ALL. All access is via APPS synonyms in the standard EBS schema layout.

Usage Notes

This API is typically invoked from the Project Management and Project Budgeting functionality when a planner selects a "Generate Budget" action, and from concurrent programs that mass-generate budget amounts across projects. Because it is a PUBLIC API, it is also suitable for custom extensions that must replicate budget generation logic consistently. Callers should set P_CALLED_MODE appropriately (default 'SELF_SERVICE'), control commit behavior through P_COMMIT_FLAG, and capture the OUT status and message data for error handling.

The package is referenced by two other database packages, indicating that it participates in a broader generation chain. Two invocation styles dominate: interactive self-service calls from the workplan and batch calls from concurrent processing. Custom code should respect the parameter defaults and avoid writing directly to PA_BUDGET_LINES, relying instead on GENERATE_WP_BUDGET_AMT and MAINTAIN_BUDGET_LINES to preserve data integrity. The header version (120.0) confirms stability across EBS 12.1.1 and 12.2.2.