Search Results pa_fin_plan_type_global




Overview
Explore in AI Chat

Overview

PA_FIN_PLAN_TYPE_GLOBAL is an Oracle Application Object Library package body owned by the APPS schema, classified as an "OTHER" API, and validated in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It provides the shared, package-level infrastructure that supports the Financial Plan Types feature within Oracle Projects. A financial plan type defines the structure, element composition, currency handling, and versioning rules that govern how project financial plans (budgets, forecasts, and related planning structures) are created and maintained. Because these rules are applied consistently across many forms and concurrent programs, the package exposes global helper routines that resolve configuration identifiers, translate between plan type metadata and plan class values, and manage the association of plan types to individual projects. The body depends on foundational EBS utilities including FND_API, FND_GLOBAL, FND_MSG_PUB, FND_PROFILE, PA_DEBUG, PA_UTILS, and PA_INTERFACE_UTILS_PUB, which indicates it participates in the standard EBS API conventions: message stack handling, profile option evaluation, session context, and diagnostic logging.

Key Procedures and Functions

The package documents seven procedures and functions, each addressing a discrete element of financial plan type configuration:

  • GET_PROJECT_ID — Returns the project identifier in the current session context. It is the accessor used by the remaining routines to determine which project's financial plan configuration should be evaluated.
  • SET_GLOBAL_VARIABLES — Initializes the package-level global variables that cache session and configuration context. Invoking this routine establishes the working state relied upon by subsequent calls within the same database session.
  • PA_FP_GET_ORGFCST_VERSION_ID — Resolves the version identifier associated with an organization forecast financial plan. This supports forecast plan processing where version identity drives the correct set of planning data.
  • PA_FP_GET_FINPLAN_VERSION_ID — Resolves the version identifier for a financial plan in general, providing the version key needed by downstream budget and forecast logic.
  • DELETE_PLAN_TYPE_FROM_PROJECT — Removes the association between a financial plan type and a project, supporting cleanup and reconfiguration scenarios where a plan type should no longer apply to the project.
  • PLANTYPE_TO_PLANCLASS — Maps a financial plan type to its corresponding plan class, allowing code to branch on the functional category of the plan rather than on individual type definitions.
  • PLANVERSION_TO_PLANCLASS — Performs the equivalent mapping at the version level, deriving a plan class from a specific plan version.

Tables Accessed

The package references a focused set of Oracle Projects tables through APPS synonyms, reflecting its role in reading and maintaining financial plan type configuration:

Usage Notes

PA_FIN_PLAN_TYPE_GLOBAL is not referenced by any database object, confirming its role as a top-level utility invoked by Oracle Projects forms, concurrent programs, and related packages rather than by triggers or dependent PL/SQL units. Seven other packages reference it, which is consistent with a shared helper used across budgeting and forecasting flows. The typical invocation pattern is to call SET_GLOBAL_VARIABLES first to establish session context, followed by GET_PROJECT_ID and the version or classification routines as needed. Custom extensions and integrations that manipulate financial plan types, or that must derive plan class from type or version, should call these documented routines rather than querying the underlying tables directly, preserving compatibility with the standard EBS error handling and profile-driven behavior enforced through FND_API and FND_MSG_PUB.