Results for “pa_fp_gen_amount_utils”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PA_FP_GEN_AMOUNT_UTILS is an Oracle Applications (APPS) PL/SQL package body that belongs to the Project Financial Planning (PA_FP) family of modules within Oracle Projects. Its role is to provide the core utility routines that support the generation and manipulation of financial plan amounts — budgets, forecasts, and commitment-related figures — within the Oracle E-Business Suite 12.1.1 and 12.2.2 releases. The package is classified as an internal "OTHER" API rather than a public interface, meaning it is intended for consumption by other Oracle Projects packages and concurrent programs rather than by customer-developed APIs. Its dependency list confirms an extensive reliance on sibling financial-planning packages such as PA_FP_GEN_FCST_PG_PKG, PA_FP_WP_GEN_AMT_UTILS, PA_FIN_PLAN_UTILS, PA_FP_CONSTANTS_PKG, and PA_WORKPLAN_ATTR_UTILS, along with common framework utilities (FND_API, FND_MSG_PUB, FND_PROFILE, PA_DEBUG, PA_UTILS). The object is VALID and is referenced by 35 other database objects, underscoring its central position in the financial-plan generation architecture.

Key Procedures and Functions

The documented interface exposes sixteen procedures and functions that address plan-version handling, currency validation, resource-class resolution, and forecast date derivation:

• GET_PLAN_VERSION_DTLS — retrieves plan version details for a given financial plan.
• CHK_CMT_TXN_CURRENCY — validates the currency associated with commitment transactions.
• GET_CURR_ORIGINAL_VERSION_INFO — obtains information about the current and original plan versions.
• VALIDATE_PLAN_VERSION — verifies that a plan version is valid for the requested operation.
• GET_VALUES_FOR_PLANNING_RATE — supplies the values needed to derive planning rates.
• FP_DEBUG — a debugging helper used to emit diagnostic output during financial-plan processing.
• GET_ETC_START_DATE — determines the start date for estimate-to-complete (ETC) calculations.
• GET_ACTUALS_THRU_DATE — returns the date through which actual costs are considered.
• GET_RL_UNCATEGORIZED_FLAG — indicates whether a resource list is uncategorized.
• GET_UC_RES_LIST_RLM_ID — resolves the resource-list member identifier for uncategorized resource lists.
• GET_RLM_ID — retrieves a resource list member identifier.
• VALIDATE_SUPPORT_CASES — performs validation of supported planning scenarios.
• DEFAULT_BDGT_SRC_VER — determines the default budget source version.
• GET_SRC_RESOURCE_CLASS_FLAG — returns the resource-class flag for the source side of a plan comparison.
• GET_RESOURCE_CLASS_FLAG_FR_BDG — derives the resource-class flag from budget data.
• GET_TRG_RESOURCE_CLASS_FLAG — returns the resource-class flag for the target side.

Tables Accessed

The package reads and writes the foundational financial-planning and project-structure tables, primarily through APPS synonyms. Planning and budget data reside in PA_BUDGET_VERSIONS, PA_BUDGET_LINES, PA_FIN_PLAN_AMOUNT_SETS, PA_FIN_PLAN_TYPES_B and PA_FIN_PLAN_TYPES_VL. Forecast and commitment figures are drawn from PA_FORECAST_ITEMS and PA_COMMITMENT_TXNS. Resource and workplan information is sourced from PA_RESOURCE_ASSIGNMENTS, PA_RESOURCE_LISTS, PA_RESOURCE_LIST_MEMBERS, PA_RESOURCE_LISTS_ALL_BG, and PA_PROJ_WORKPLAN_ATTR. Project and task context comes from PA_PROJECTS_ALL and PA_TASKS, while configuration and implementation settings are read from PA_PROJ_FP_OPTIONS and PA_IMPLEMENTATIONS_ALL. DUAL is referenced for single-row scalar operations.

Usage Notes

Because PA_FP_GEN_AMOUNT_UTILS is an internal package body, it is typically invoked indirectly. Financial-plan generation concurrent programs, forecast generation wrappers (PA_FP_GEN_FCST_PG_PKG), workplan amount utilities, and Oracle Projects forms that manipulate budgets and forecasts call these routines during plan creation, version selection, currency and resource-class checks, and ETC/actuals date determination. Custom code should avoid calling the package directly where a public API exists; instead, administrators and developers should treat it as supporting infrastructure whose behaviour surfaces through the standard Project Financial Planning UI and Concurrent Manager processes. Its heavy use of FND_API and FND_MSG_PUB indicates that errors are propagated through the standard EBS message stack, so any diagnostic work should begin with PA_DEBUG output and the FND message log.