Search Results get_fp_options




Overview
Explore in AI Chat

Overview

PA_PROJ_FP_OPTIONS_PUB is an Oracle EBS public PL/SQL package body (owner APPS, classification PUB) that manages financial plan options for projects within the Project Management (PA) module. Its central responsibility is the creation, retrieval, synchronization, and maintenance of FP (Financial Plan) option records, which govern how financial plan types, budget versions, amount types, and multicurrency behavior are configured for a given project. The package abstracts the underlying table-handler logic so that callers — forms, concurrent programs, and other PL/SQL packages — interact with a stable public API rather than directly manipulating PA_PROJ_FP_OPTIONS and related tables. A debug flag, P_PA_DEBUG_MODE, is initialized from the PA_DEBUG_MODE profile option, and the module identifier l_module_name is used for logging and error context.

Key Procedures and Functions

The package exposes thirteen documented routines. The most significant is CREATE_FP_OPTION, an insert/update procedure operating across three tables based on the Source and Target FP Option details supplied. Its behavior is conditional: when both Source and Target are passed, the Target FP Option is updated with Source details (used during edit plan type, copy from an existing version, adding a plan type to a project, or copying from an existing project). When only Source is passed, a new Target FP Option is created from Source details. When only Target is passed, details are derived from the Parent where one exists, otherwise from default option details keyed by the Target Preference Code. When neither is passed, Parent details are resolved via the Option Level Code or defaults via the Target Preference Code. Two historical fixes are embedded in this routine: Bug 2625872 set the multicurrency flag to 'Y' when project currency differs from project functional currency, and Bug 2920954 added new columns to the insert/update table handlers.

Supporting query routines include GET_FP_OPTIONS, GET_FP_OPTION_ID, GET_PARENT_FP_OPTION_ID, GET_DEFAULT_FP_OPTIONS, GET_FP_PROJ_MC_OPTIONS, and GET_FP_PLAN_TYPE_MC_OPTIONS, which retrieve option records, identifiers, defaults, and multicurrency-specific configurations. SYNCHRONIZE_BUDGET_VERSION aligns budget version data with FP options. GEN_SRC_PLAN_VERSION_ID and GEN_SRC_WP_VERSION_ID generate source plan and workplan version identifiers. The amount-type operations — CREATE_AMT_TYPES, COPY_AMT_TYPES, and UPDATE_AMT_TYPES — maintain entries in the financial plan amount type structures.

Tables Accessed

The package references a broad set of APPS synonyms. PA_PROJ_FP_OPTIONS is the primary table written by CREATE_FP_OPTION and read by the GET routines. PA_FIN_PLAN_TYPES_B and PA_FIN_PLAN_AMOUNT_SETS supply plan type and amount set definitions. PA_BUDGET_VERSIONS supports version synchronization. PA_PROJECTS_ALL and PA_IMPLEMENTATIONS_ALL provide project and installation context. PA_PERIODS_ALL and GL_PERIODS resolve accounting period data, while PA_FP_PROJ_XL_AMT_TYPES stores project amount types. Resource and structure information comes from PA_RESOURCE_LISTS_ALL_BG, PA_PROJ_ELEM_VER_STRUCTURE, PA_RBS_HEADERS_B, PA_RBS_HEADERS_TL, and PA_RBS_VERSIONS_B. PLITBLM is used as a PL/SQL index-by table type for bulk processing.

Usage Notes

PA_PROJ_FP_OPTIONS_PUB is invoked by eight other packages and is the designated entry point for financial plan option maintenance. It is typically called from the Project Management forms when users create or edit plan types, copy versions or projects, or add plan types to projects, and from concurrent programs that synchronize budget versions. Custom extensions should call CREATE_FP_OPTION rather than writing directly to PA_PROJ_FP_OPTIONS to preserve the conditional Source/Target semantics and multicurrency handling. Because the API classification is PUB, Oracle supports direct invocation by customer code, and the embedded bug-fix logic ensures consistent flag population across EBS 12.1.1 and 12.2.2. Callers should honor the documented Source/Target combinations to obtain predictable insert-versus-update behavior and parent/default fallback resolution.