Results for “get_src_resource_class_flag”

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

Overview

PA_FP_GEN_AMOUNT_UTILS is a public PL/SQL package in the Oracle EBS Projects (PA) application, owned by APPS and declared with AUTHID CURRENT_USER. It provides shared utility logic for the financial planning and budgeting engine, specifically the generation and manipulation of plan amounts for projects and top tasks. The package centralizes the resolution of planning context — financial plan type, plan version, amount set, planning level, time-phasing, resource lists, and rate schedules — so that other planning packages, concurrent programs, and forms do not duplicate that logic.

The package exposes a record type, FP_COLS, whose fields are anchored to columns of PA_PROJ_FP_OPTIONS and PA_BUDGET_VERSIONS. It carries identifiers such as X_PROJECT_ID, X_BUDGET_VERSION_ID, X_PROJ_FP_OPTIONS_ID, X_FIN_PLAN_TYPE_ID, X_PROJ_FP_OPTIONS_ID, cost and revenue employee, job, non-labor resource and resource class rate schedule identifiers, the burden rate schedule, the current planning period, and the period mask. This record is the standard vehicle through which callers pass plan configuration into the amount generation routines. The phrase the user searched for, validate_plan_version, corresponds to the documented procedure VALIDATE_PLAN_VERSION.

Key Procedures and Functions

• VALIDATE_PLAN_VERSION — validates that the plan version supplied by a caller is valid and consistent with the project, financial plan type, and planning options before amount generation proceeds.
• GET_PLAN_VERSION_DTLS — retrieves the descriptive and configuration details of a plan version, supplying the values required to populate the FP_COLS record.
• GET_CURR_ORIGINAL_VERSION_INFO — returns information about the current and original plan versions, supporting comparison and copy behaviour during replanning.
• DEFAULT_BDGT_SRC_VER — resolves the default source budget version used when generating a plan from an existing budget or forecast.
• GET_ETC_START_DATE and GET_ACTUALS_THRU_DATE — determine the boundaries between actual costs and estimate-to-complete, driving how amount rows are split between actuals and plan.
• GET_VALUES_FOR_PLANNING_RATE — returns the rate-related values applied when amounts are generated at a given planning level.
• CHK_CMT_TXN_CURRENCY — checks commitment transaction currency, ensuring commitment amounts are handled in the correct currency context.
• GET_RESOURCE_CLASS_FLAG_FR_BDG, GET_TRG_RESOURCE_CLASS_FLAG and GET_SRC_RESOURCE_CLASS_FLAG — return source and target resource class flags for budget-based planning.
• GET_RL_UNCATEGORIZED_FLAG and GET_UC_RES_LIST_RLM_ID, GET_RLM_ID — resolve resource list membership, including the uncategorized resource list handling.
• VALIDATE_SUPPORT_CASES — performs support-case related validation within the plan generation flow.
• FP_DEBUG — writes diagnostic output used during development and troubleshooting of the planning engine.

Tables Accessed

All tables are referenced through APPS synonyms. PA_PROJ_FP_OPTIONS is the central configuration table, supplying plan level, time-phasing, resource list and rate schedule columns that feed FP_COLS. PA_BUDGET_VERSIONS and PA_BUDGET_LINES provide budget version identity and line amounts for source versions. PA_FIN_PLAN_AMOUNT_SETS and PA_FIN_PLAN_TYPES_B define the amount set and financial plan type context, while PA_RESOURCE_LISTS_ALL_BG, PA_RESOURCE_LIST_MEMBERS and PA_RESOURCE_ASSIGNMENTS resolve resource list membership and assignments. PA_PROJECTS_ALL and PA_TASKS provide project and task verification. PA_COMMITMENT_TXNS supports commitment currency and amount checks, PA_FORECAST_ITEMS supports forecast-side amount processing, PA_PROJ_WORKPLAN_ATTR supplies workplan attributes used in planning level resolution, PA_IMPLEMENTATIONS_ALL is read for installation-level settings, and DUAL supports scalar expressions.

Usage Notes

The package is not intended for direct end-user invocation. It is called by the financial planning engine during plan generation, budget and forecast copy, and version validation, and it is referenced by 35 other packages in the Projects schema, confirming its role as a shared internal utility layer. Callers should populate the FP_COLS record from PA_PROJ_FP_OPTIONS and PA_BUDGET_VERSIONS, then invoke VALIDATE_PLAN_VERSION before requesting version details or generated amounts. In Oracle EBS 12.1.1 and 12.2.2 the package is invoked from concurrent programs that create and update financial plans, from the Project Financial Planning forms, and from extension code that must respect the same validation and defaulting rules. The header signature indicates the source was last shipped at version 120.9 (February 2012). Custom code should treat the package as a supported internal API and avoid hard-coded assumptions about parameter ordering.