Search Results budget_lines_record




Overview
Explore in AI Chat

Overview

PA_FP_ORG_FCST_GEN_PUB is a public PL/SQL package in the Oracle EBS Projects (PA) application that supports organization-level forecasting within the Oracle Financials and Project Management integration. Its principal business function is to generate organizational forecasts by aggregating financial plan and budget line data across resource assignments, tasks, and organizations. The package belongs to the Financial Planning (FP) family of APIs and is classified as a Public (PUB) interface, meaning it is intended for invocation by other Oracle EBS components and, in some cases, by customer-written extensions.

The package header carries the source control identifier PAFPORGS.pls 120.1, dated 2005/08/19, and comments inside the source indicate that the forecasting logic was previously housed in PAFPCPFS.pls and copied into this package specifically for use in the Organization Forecasting context without functional change. The package therefore represents a consolidation of forecasting logic into an organization-centric API surface.

Key Procedures and Functions

The ETRM documentation identifies four public procedures:

  • GEN_ORG_FCST — The core forecast generation routine. It accepts selection and organizational criteria, an optional starting organization, a budget version identifier, and organizational flags, and returns standard error and return code parameters. The API exists to drive the population of organizational financial forecasts from underlying budget and plan data. It is the entry point for automated forecast generation.
  • CREATE_RES_TASK_MAPS — Creates the mapping between resource assignments and project tasks, establishing the relationship records required for forecast processing.
  • COPY_RESOURCE_ASSIGNMENTS — Copies resource assignment records, typically as part of setting up a new forecast or planning version based on an existing assignment structure. This procedure is directly relevant to the search term "copy_resource_assignments" and represents the primary documented operation for duplicating resource assignment data.
  • COPY_BUDGET_LINES — Copies budget line records, supporting scenarios where a forecast version must inherit or reference budget lines from another plan or version.

Tables Accessed

The package reads from and writes to a substantial set of Projects and HR tables through APPS synonyms. The principal forecast and budget tables include PA_BUDGET_VERSIONS, PA_BUDGET_LINES and PA_BUDGET_LINES_S, PA_FIN_PLAN_LINES_TMP, PA_FIN_PLAN_AMOUNT_SETS, and PA_FIN_PLAN_TYPES_B. These hold version definitions, plan lines, and amount set configurations consumed during forecast generation.

Supporting tables include PA_FORECASTING_OPTIONS_ALL and PA_FORECAST_ITEMS, which drive forecast behavior. Mapping and temporary tables — PA_FP_BL_MAP_TMP and PA_FP_RA_MAP_TMP — are used to stage budget-line and resource-assignment mappings during processing. Organizational context is drawn from HR_ALL_ORGANIZATION_UNITS and HR_ALL_ORGANIZATION_UNITS_TL. Date handling depends on GL_DATE_PERIOD_MAP and GL_PERIODS, while PA_AMOUNT_TYPES_B supplies amount type definitions. The record structures defined in the package header, including BUDGET_LINES_RECORD with fields for quantity, raw cost, burdened cost, revenue, utilization, capacity, and head count, reflect the breadth of financial data manipulated.

Usage Notes

PA_FP_ORG_FCST_GEN_PUB is invoked in organization forecasting workflows, typically from concurrent programs or internal processing that populates forecast versions. The GEN_ORG_FCST procedure is the standard invocation point, with selection criteria and budget version parameters determining scope. COPY_RESOURCE_ASSIGNMENTS and COPY_BUDGET_LINES are used when establishing or refreshing planning structures prior to forecast generation.

The package is referenced by three other packages, indicating it is itself a dependency of higher-level planning flows. Because it is classified PUB, custom code may call its procedures, but developers should note the 2005 vintage of the header and avoid assuming newer features. Implementations on 12.1.1 and 12.2.2 should verify that the referenced version and patch level match the deployed code line, since no significant functional changes are documented in the supplied metadata.