Search Results get_budget_amount

Overview

APPS.PA_MC_BILLING_PVT is a private (PVT) PL/SQL package body within the Oracle Projects suite of Oracle E-Business Suite. Its principal purpose is to resolve budget amounts associated with a project, task, or billing extension in support of the Multi-Currency Billing (MC Billing) process. The package encapsulates the logic required to identify the correct cost and revenue budget types, locate the applicable baselined budget versions, and return the corresponding monetary totals to the calling program. By centralising this logic, PA_MC_BILLING_PVT ensures that billing routines derive budget figures consistently and in accordance with the budget type configuration defined in Project Billing Extensions.

The package is classified as PVT, meaning it is intended for internal use by other Oracle Projects components rather than being a public, customer-facing API. It is documented as being referenced by one other package, which further confirms its role as a supporting utility within the billing module rather than an entry point.

Key Procedures and Functions

The package exposes six documented procedures and functions, each performing a discrete retrieval step in the budget resolution chain:

• GET_BUDGET_AMOUNT — The central routine, and the one surfaced by the "get_budget_amount" search. It accepts project, task, and set-of-books identifiers together with a billing extension identifier and optional cost and revenue budget type codes, and returns the corresponding revenue and cost amounts along with the resolved budget type codes and standard API return status, message count, and message data outputs. Internally it resolves the budget type codes from the billing extension, validates them, and raises dedicated exceptions for invalid or non-baselined budgets.
• GET_PROJECT_TASK_BUDGET_AMOUNT — Retrieves budget amounts at the project and task level, providing the higher-level aggregation context used by the billing logic.
• GET_COST_AMOUNT — Derives the cost-side budget amount, distinguishing raw and burdened cost totals.
• GET_POT_EVENT_AMOUNT — Resolves amounts associated with potential (POT) events relevant to billing determination.
• GET_LOWEST_AMOUNT_LEFT — Determines the lowest remaining budget balance, supporting threshold and limit checks during billing.
• GET_REVENUE_AMOUNT — Derives the revenue-side budget amount used to compare against cost for billing generation.

Tables Accessed

The package operates against the following tables through APPS synonyms:

• PA_BILLING_EXTENSIONS — The originating source for the cost and revenue budget type codes, as indicated in the inline comment "Get the Cost and Revenue Budget Type code from pa_billing_extensions".
• PA_BUDGET_TYPES — Validates and interprets the budget type codes used to qualify the amounts retrieved.
• PA_BUDGET_VERSIONS — Identifies the baselined budget version from which amounts are drawn; absence of a baselined version triggers the baselining exceptions declared in the body.
• PA_TASKS — Resolves task-level context for the project/task hierarchy used in the amount calculations.
• DUAL — Used for scalar evaluations and simple computational checks within the PL/SQL flow.

Usage Notes

PA_MC_BILLING_PVT is invoked programmatically by other Oracle Projects packages rather than directly from an Oracle Forms screen. Its callers typically operate in the billing and revenue recognition flow, where budget amounts must be validated against baselined versions before billing is generated. Custom extensions that require the same budget resolution should call GET_BUDGET_AMOUNT rather than querying the underlying tables directly, so that budget type resolution, baselining checks, and standard FND_API return status handling remain consistent.

Because the package is classified as PVT and its header reflects a "noship" designation, it should be treated as an internal implementation artefact. Customers and integrators should not assume signature stability across releases; behaviour is governed by the documented budget type configuration in PA_BILLING_EXTENSIONS and the baselining status of the applicable budget versions. Diagnostic work should focus on those two areas when unexpected amounts or return statuses are observed.