Search Results pa_fp_ci_implement_pkg




Overview
Explore in AI Chat

Overview

PA_FP_CI_IMPLEMENT_PKG is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that supports the implementation of Capitalized Interest (CI) processing within the Oracle Projects Foundation and Funding functionality. Capitalized interest refers to the practice of capitalizing interest costs incurred during the construction or development phase of a capital project and adding those costs to the asset value rather than expensing them. This package provides the programmatic infrastructure that allows Oracle Projects to translate a project's funding configuration and budget structures into CI impact funding lines, and to validate plan versions before a CI merge operation is executed. It is classified under Oracle's ETRM (E-Business Suite Technical Reference Manual) as an "OTHER" API, meaning it is not a public, supported extension interface but rather an internal utility used by Oracle Projects' standard seeded components.

Key Procedures and Functions

The ETRM documentation identifies two procedures or functions within this package:

  • CREATE_CI_IMPACT_FUND_LINES — Responsible for generating the funding lines that represent the capitalized interest impact against a project's funding sources. This routine reads the project, agreement, and funding configuration data and produces or adjusts the corresponding rows that record how CI amounts will be attributed across funding sources. It is the core routine that materializes the CI funding impact within the project funding structure.
  • CHK_PLAN_VER_FOR_MERGE — A validation routine that examines the plan version associated with a project to determine whether it is eligible or eligible-consistent for a CI merge operation. This acts as a pre-check guard invoked before merge processing proceeds, ensuring that the plan version meets structural and configuration prerequisites so that downstream merge logic does not operate on unsupported data.

Both routines are internal in nature; the ETRM does not publish a supported parameter list, and callers should treat the signatures as Oracle-controlled.

Tables Accessed

The package references several core Oracle Projects and Purchasing tables (via APPS synonyms):

  • PA_PROJECTS_ALL and PA_TASKS — project and task definition data used to establish the context for CI processing.
  • PA_PROJECT_FUNDINGS and PA_PROJ_FP_OPTIONS — funding definitions and project funding options that drive how CI impact lines are attributed.
  • PA_AGREEMENTS_ALL — agreement and funding source information associated with the project.
  • PA_BUDGET_VERSIONS and PA_BUDGET_LINES — budget version and line data evaluated during plan-version validation and CI line generation.
  • PA_RESOURCE_ASSIGNMENTS — resource assignment data relevant to plan and funding structures.
  • PLITBLM — a PL/SQL table type used for in-memory collection handling during processing.
  • PA_PLSQL_DATATYPES — the shared Oracle Projects datatype package providing common record and table type definitions.

Usage Notes

PA_FP_CI_IMPLEMENT_PKG is an internal, non-public package. The ETRM shows it is referenced by only one other package and does not expose it as a supported API for customer extensions. In practice, it is invoked by Oracle Projects' seeded CI implementation and merge processing — notably alongside PA_FP_CI_MERGE — which handles the merging of capitalized interest impact lines into the project funding structure. Custom code should not call this package directly, as its interface and behavior are Oracle-controlled and may change across patch levels. In Oracle EBS 12.1.1 and 12.2.2, invocation effectively occurs through standard Oracle Projects concurrent programs and forms that drive CI implementation and merge, rather than through user-invoked entry points. Because the package depends on PA_PLSQL_DATATYPES, it inherits the shared Oracle Projects datatype definitions, reinforcing that it is tightly coupled to the internal Oracle Projects data model. Administrators diagnosing CI funding or merge issues should treat this package as a supporting internal component and rely on the standard CI implementation and merge processes rather than direct execution.