Search Results get_pd_sd_amt_in_pc_pfc




Overview
Explore in AI Chat

Overview

APPS.PA_FP_EDIT_LINE_PKG is an Oracle E-Business Suite PL/SQL package that supports the financial planning line-editing infrastructure within Oracle Projects. In EBS 12.1.1 and 12.2.2, financial plans store budget and forecast amounts at the resource, task, and period level. This package provides the server-side logic that lets a user modify individual plan lines — changing resource assignments, redistributing amounts across periods, or splitting amounts between project and task — while preserving the integrity of the underlying plan version, period profile, and amount-set structures.

The package is classified as OTHER under the ETRM API classification scheme, meaning it is primarily an internal implementation component rather than a formally published public API. Its core responsibility is to prepare, validate, and process modified financial plan lines, including rollup support, period eligibility determination, and client extension hooks. It is referenced by PA_FP_VIEW_PLANS_TXN_PUB, the public transaction layer used by the Financial Plan viewing and editing forms, confirming its role as a subordinate engine behind the user-facing plan maintenance pages.

Key Procedures and Functions

  • POPULATE_ROLLUP_TMP — Populates the temporary rollup structure that aggregates plan line amounts for hierarchical review and processing.
  • DERIVE_PD_SD_START_END_DATES — Derives start and end dates for the project date (PD) and sub-period date (SD) ranges used in period-based amount distribution.
  • PROCESS_MODIFIED_LINES — Applies the user's line-level edits, validating and persisting changes against the financial plan structures.
  • GET_ELEMENT_AMOUNT_INFO — Retrieves amount information for a plan element such as a resource assignment or task.
  • CALL_CLIENT_EXTENSIONS — Invokes registered client extension hooks so customers can add validation or defaulting logic during line editing.
  • POPULATE_ELIGIBLE_PERIODS — Determines which GL or project periods are eligible for the plan lines based on the plan's period profile.
  • GET_PRECEDING_SUCCEEDING_AMT — Calculates amounts for the periods immediately preceding and following a given period, supporting spread and redistribution.
  • GET_IS_FN_SECURITY_AVAILABLE — Checks whether function security is available and enabled for the current user's operation.
  • FIND_DUP_ROWS_IN_ROLLUP_TMP — Detects duplicate rows in the rollup temporary table to prevent double counting.
  • GET_PD_SD_AMT_IN_PC_PFC — Returns project-date and sub-period-date amounts expressed in project currency and project functional currency.
  • PROCESS_BDGTLINES_FOR_VERSION — Processes budget lines associated with a specified budget version, linking plan edits back to the budget line records.

Tables Accessed

The package reads and writes a broad set of Oracle Projects planning tables. Plan structure is sourced from PA_BUDGET_LINES, PA_BUDGET_VERSIONS, PA_FIN_PLAN_AMOUNT_SETS, PA_PROJ_FP_OPTIONS, PA_PROJ_PERIOD_PROFILES, and PA_PROJ_PERIODS_DENORM, which define versions, amount sets, financial plan options, and period profiles. PA_PROJECTS_ALL, PA_TASKS, PA_RESOURCES, PA_RESOURCE_ASSIGNMENTS, PA_RESOURCE_LISTS, and PA_RESOURCE_LIST_MEMBERS supply project, task, and resource context, including which resources are available for planning. The package also references FND_NEW_MESSAGES for message retrieval, GL_PERIOD_STATUSES for period-open validation, PA_BUDGET_LINES_S for budget line sequencing, and PA_FP_CPY_PERIODS_TMP for temporary period copy processing. It uses the PL/SQL collection types PA_DATE_TBL_TYPE, PA_NUM_TBL_TYPE, and PA_VARCHAR2_30_TBL_TYPE for bulk date, numeric, and string processing.

Usage Notes

PA_FP_EDIT_LINE_PKG is not intended for direct invocation by end users or typical custom code. It is invoked indirectly through the Financial Plan editing pages, which call PA_FP_VIEW_PLANS_TXN_PUB; that public layer in turn delegates line-modification work to this package. Typical triggers include editing or copying financial plan lines, redistributing amounts across periods, and validating resource assignments against plan options. Because the package is also referenced by itself (recursive internal calls), it should be treated as internal infrastructure. Customizations requiring changes to plan line behavior should preferably hook into CALL_CLIENT_EXTENSIONS or interact through PA_FP_VIEW_PLANS_TXN_PUB rather than calling PA_FP_EDIT_LINE_PKG directly, since the API classification is OTHER and signatures are not guaranteed across releases.