Search Results fp_cols




Overview
Explore in AI Chat

Overview

APPS.PA_PROJ_FP_OPTIONS_PUB is the public PL/SQL API package that governs the Financial Planning Options of a project in Oracle Projects. Financial Planning Options define the default behavior and structural boundaries applied when a project manager creates and maintains financial plan versions — for example, the financial plan start and end dates, the amount sets used for cost, revenue, and all-plan types, the planning level, the time-phasing code, the resource list, and the currency treatment applied to the plan.

The package exposes a controlled interface for creating, retrieving, defaulting, and validating these option records in PA_PROJ_FP_OPTIONS, shielding calling code from the underlying table structure. It also supports the management of amount type configurations through a dedicated set of APIs, and it provides synchronization and derivation utilities used by the Financial Planning engine and by other Oracle Projects modules. Because the options determine the effective context under which plan versions are built, this package is foundational to both baseline planning and change-management workflows.

Key Procedures and Functions

  • CREATE_FP_OPTION — Creates a new Financial Planning Options record for a project, thereby establishing the planning framework.
  • GET_FP_OPTIONS — Retrieves the current Financial Planning Options for a project, typically returning the values into the FP_COLS record structure.
  • GET_DEFAULT_FP_OPTIONS — Returns the default set of options that apply when an options record has not yet been explicitly created, based on setup and implementation defaults.
  • GET_FP_OPTION_ID — Returns the unique identifier of the FP options record for a project.
  • GET_PARENT_FP_OPTION_ID — Returns the parent FP options identifier, supporting inheritance of planning characteristics.
  • GET_FP_PROJ_MC_OPTIONS — Retrieves project-level multi-currency planning options.
  • GET_FP_PLAN_TYPE_MC_OPTIONS — Retrieves multi-currency options specific to a financial plan type.
  • SYNCHRONIZE_BUDGET_VERSION — Synchronizes a budget version with its associated financial plan version.
  • GEN_SRC_PLAN_VERSION_ID — Generates or derives the source plan version identifier used in planning flows.
  • GEN_SRC_WP_VERSION_ID — Generates or derives the source workplan version identifier.
  • CREATE_AMT_TYPES — Creates amount type configurations for financial planning.
  • COPY_AMT_TYPES — Copies existing amount type configurations to a target context.
  • UPDATE_AMT_TYPES — Updates existing amount type configurations.

Tables Accessed

The package reads and writes PA_PROJ_FP_OPTIONS, the primary store of planning options. Project context is validated against PA_PROJECTS_ALL, while PA_IMPLEMENTATIONS_ALL and PA_FIN_PLAN_TYPES_B supply implementation-level and plan-type defaults. Planning level, time-phasing, and resource list values are validated against PA_RESOURCE_LISTS_ALL_BG, PA_RBS_HEADERS_B, PA_RBS_HEADERS_TL, and PA_RBS_VERSIONS_B. Amount set definitions are drawn from PA_FIN_PLAN_AMOUNT_SETS, and amount type configurations from PA_FP_PROJ_XL_AMT_TYPES. Calendar and period validation uses GL_PERIODS and PA_PERIODS_ALL. Version and structure handling references PA_BUDGET_VERSIONS and PA_PROJ_ELEM_VER_STRUCTURE. PLITBLM is used as a PL/SQL index-by table type for bulk processing.

Usage Notes

This package is classified as a public API and is invoked by Oracle Projects forms, concurrent programs, and the Financial Planning business logic, and it is referenced by eight other packages. The FP_COLS record is the focal structure for the "fp_cols" search: it consolidates the most frequently used PA_PROJ_FP_OPTIONS columns into a single typed record used as an input or output parameter across the APIs. Custom code should call GET_FP_OPTIONS to read options rather than querying the table directly, and should use CREATE_FP_OPTION to establish options before creating plan versions. Multi-currency planning environments must use the MC-specific retrieval functions. Because the header notes later patched definitions of selected numeric columns, integrators should treat those fields as NUMBER rather than relying on column-anchored types.