Search Results load_budget_line

Overview

APPS.PA_BUDGET_PUB is the public PL/SQL API for Oracle Project Budgeting within Oracle E-Business Suite Releases 12.1.1 and 12.2.2. It exposes the budget maintenance and calculation services of the Project Foundation and Project Budgeting modules to external callers, including Oracle subledger and grant-management products. The package wraps the private business logic held in PA_BUDGET_PVT and presents a committed, supported interface for creating draft budgets, populating and maintaining budget lines, baselining approved budgets, and calculating budget amounts. Its API classification as a PUB package confirms that it is intended for direct invocation by customer extensions and by other Oracle applications; private logic remains encapsulated in the corresponding PVT package.

Because PA_BUDGET_PUB is referenced by PA_FIN_PLAN_UTILS, PA_FINPLAN_TYPES_V, PA_FP_WEBADI_PKG, PA_PROJECT_INTEGRATION_PUB, PA_AGREEMENT_PUB, PA_BUDGET_CHECK_PVT, and the Oracle Grants packages GMS_MULTI_FUNDING and GMS_SUMMARIZE_BUDGETS, it functions as the central budget persistence layer for financial-planning workflows. Users searching for PA_FIN_PLAN_UTILS are typically tracing financial-plan budget creation back to this package, since the financial-plan utilities delegate the budget-side operations to PA_BUDGET_PUB.

Key Procedures and Functions

The documented interface comprises 27 procedures and functions. They fall into several logical groups:

• Session context: SET_PROJECT_ID and GET_PROJECT_ID establish and retrieve the project identifier used by subsequent calls within the same session, providing the context against which budget operations are scoped.
• Budget lifecycle: INIT_BUDGET, CREATE_DRAFT_BUDGET, EXECUTE_CREATE_DRAFT_BUDGET, DELETE_DRAFT_BUDGET, BASELINE_BUDGET, UPDATE_BUDGET, EXECUTE_UPDATE_BUDGET, CLEAR_BUDGET, and DELETE_DRAFT_BUDGET manage the creation, modification, clearing, and baselining of budget versions. The EXECUTE_ prefixed entries perform the actual processing step after an INIT_ call has set up the working structures.
• Line maintenance: ADD_BUDGET_LINE, LOAD_BUDGET_LINE, FETCH_BUDGET_LINE, UPDATE_BUDGET_LINE, and DELETE_BUDGET_LINE provide row-level access to budget lines, including bulk loading and iterative retrieval.
• Amount calculation: CALCULATE_AMOUNTS, INIT_CALCULATE_AMOUNTS, EXECUTE_CALCULATE_AMOUNTS, and FETCH_CALCULATE_AMOUNTS drive raw-cost, burdened-cost, and revenue amount computation across the budget structure.
• Utility: the WITH construct supports the internal cursor and record definitions used by the public interface.

No parameter lists are published in the metadata; callers must consult the Oracle Project Budgeting API documentation for argument signatures.

Tables Accessed

PA_BUDGET_PUB reads and writes the core budgeting tables PA_BUDGET_VERSIONS and PA_BUDGET_LINES through APPS synonyms. It references the financial-plan configuration tables PA_FIN_PLAN_TYPES_B, PA_FIN_PLAN_TYPES_TL, PA_FIN_PLAN_TYPES_VL, PA_FIN_PLAN_AMOUNT_SETS, PA_FP_TXN_CURRENCIES, and PA_PROJ_FP_OPTIONS to resolve plan type, currency, and amount-set behavior. Project and task structures are validated against PA_PROJECTS_ALL and PA_TASKS, while resource definitions come from PA_RESOURCES, PA_RESOURCE_ASSIGNMENTS, PA_RESOURCE_LISTS, and PA_RESOURCE_LIST_MEMBERS. GL_LEDGERS supplies the ledger context, and FND_USER and GL_PERIOD_STATUSES provide user and period validation.

Usage Notes

PA_BUDGET_PUB is invoked from the Project Budgeting forms, from concurrent programs that generate or baseline budgets, and from WebADI budget entry through PA_FP_WEBADI_PKG. Custom code should call only the public routines, using the INIT_/EXECUTE_/FETCH_ pattern for multi-row operations and respecting the project-id session context. Because several Grants and financial-plan packages depend on this interface, changes to custom callers should be regression-tested against those dependent programs.