Results for “pa_fp_planning_transaction_pub”

50+ results




Overview
Explore in AI Chat

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PA_FP_PLANNING_TRANSACTION_PUB is a public PL/SQL package in the APPS schema that forms part of the Oracle Project Financial Planning (PA_FP) application programming interface layer. It provides the business logic used to manage planning transactions — the rows of financial plan data that describe planned amounts, quantities, resources, tasks, and related attributes within a project's financial plan. Planning transactions are the granular working-level records that, once summarized, produce budget or forecast versions of a project plan. This package exposes the transaction-level operations that other planning modules (financial plan elements, task assignments, WebADI-based plan uploads, and copy-from utilities) rely on to insert, update, duplicate, refresh, and delete plan transactions consistently, enforcing the validation and derivation rules defined in the underlying tables.

It is classified as a PUB package in the ETRM 12.2.2 metadata, indicating it is intended as a supported entry point for other modules and custom extensions rather than an internal helper. The package owner is APPS and its compiled status is VALID in both the 12.1.1 and 12.2.2 releases. The overall design follows the standard EBS pattern: a public package wraps more granular private logic (for example, PA_FIN_PLAN_PVT and PA_TASK_ASSIGNMENTS_PVT), coordinating validation, defaulting, and persistence of planning transaction records.

Key Procedures and Functions

The ETRM documentation lists eleven procedures and functions for this package. Their purposes are as follows:

  • UPDATE_PLANNING_TRANSACTIONS — Updates existing planning transaction rows, applying validated changes supplied by the caller.
  • COPY_PLANNING_TRANSACTIONS — Duplicates planning transactions, typically when copying a plan version or plan structure to a new version.
  • DELETE_PLANNING_TRANSACTIONS — Removes planning transactions, respecting referential integrity and plan status rules.
  • REFRESH_PLAN_TXNS — Regenerates or re-derives plan transactions so that stored values reflect the current plan definition, resource lists, or settings.
  • CREATE_DEFAULT_TASK_PLAN_TXNS — Creates default planning transactions for project tasks, populating baseline rows for planning when no transactions exist.
  • REFRESH_WP_SETTINGS — Refreshes workplan-related settings associated with planning transactions so the plan stays synchronized with workplan structure.
  • REFRESH_RBS_FOR_VERSIONS — Refreshes resource breakdown structure (RBS) associations for one or more plan versions.
  • NAME — A function that returns the identifier or name associated with the package, commonly used for diagnostics or logging.
  • DUP_EXISTS — A function that tests whether a duplicate planning transaction already exists, supporting de-duplication checks before insert or copy.

No parameter lists are documented in the supplied metadata, so the exact signatures should be confirmed from the package specification in the database.

Tables Accessed

The package reads and writes several core Project Accounting tables via APPS synonyms. PA_BUDGET_VERSIONS defines the plan or budget versions that planning transactions belong to. PA_PROJECTS_ALL identifies the owning project. PA_PROJ_ELEMENT_VERSIONS and PA_TASKS supply the structure and task context for the transactions. PA_RESOURCE_LIST_MEMBERS provides the valid resource list against which planning resources are validated. Planning detail and currency rows are held in PA_BUDGET_LINES, PA_FP_TXN_CURRENCIES, and PA_FP_TXN_CURRENCIES_S. Supporting lookups include MTL_SYSTEM_ITEMS_B and MTL_UNITS_OF_MEASURE for item and UOM validation, PA_EXPENDITURE_TYPES, PA_FIN_PLAN_TYPES_B, PA_ALTERNATE_TASKS, PA_ASGMT_PLAN_CHANGE_T, and the temporary table PA_FP_RA_MAP_TMP. The package also uses the collection types PA_DATE_TBL_TYPE, PA_NUM_TBL_TYPE, and various PA_VARCHAR2_*_TBL_TYPE types for bulk parameter passing.

Usage Notes

This package is typically invoked indirectly through higher-level planning APIs and utilities rather than directly by end users. It is referenced by eighteen other packages, including PA_FIN_PLAN_PUB, PA_FIN_PLAN_PVT, PA_FP_ELEMENTS_PUB, PA_FP_COPY_FROM_PKG, PA_FP_WEBADI_PKG, PA_BUDGET_PUB, PA_ASSIGNMENTS_PVT, PA_TASK_ASSIGNMENTS_PUB, PA_TASK_ASSIGNMENTS_PVT, PA_TASK_PUB1, PA_TASK_PVT1, PA_PROJ_TASK_STRUC_PUB, PA_PROJECT_STRUCTURE_PVT1, PA_TASK_ASSIGNMENT_UTILS, PA_PLANNING_ELEMENT_UTILS, and PA_FP_PLANNING_TRANSACTION_PUB itself. Developers writing custom planning integrations should use these documented procedures to ensure validation and derivation logic is applied, and should confirm exact parameter signatures from the package specification before coding against it.