Search Results validate_header_info

Overview

PA_FP_CALC_PLAN_PUB is a public PL/SQL package body owned by APPS in Oracle E-Business Suite, classified as a PUB (public) API. It belongs to the Project Accounting (PA) module, specifically the financial planning (FP) calculation area. Its principal role is to provide an Application Programming Interface (API) for recalculating cost rates and currency conversion rates across planning data in bulk. The package operates within the Project Management and budgeting workflows used by Oracle Project Costing and Oracle Project Management, allowing budget planners to refresh the rates applied to planning resources without manually editing individual assignment records.

The package supports both Workplan and Financial plan structures. Depending on the input parameters, it can refresh rates for all planning resources in an entire budget version or restrict the operation to a specific set of planning resources. The REFRESH_RATES procedure performs validation and security checks before committing any rate updates, which preserves data integrity and enforces access controls within multi-organization and project security setups.

Key Procedures and Functions

The documented public API exposes a single procedure:

• REFRESH_RATES — An AMG public API that refreshes cost rates or conversion rates in bulk. It accepts parameters identifying the project (by project ID or project reference), the plan type to update (either WORKPLAN or FINPLAN), and the associated structure or budget version identifiers. For Workplan updates a structure version identifier is required; for Financial plan updates, budget version number, version type, and either a financial plan type ID or name must be supplied. An optional table parameter allows the caller to limit the refresh to specific resource class codes. The procedure validates inputs, applies security checks, and then recalculates the applicable rates for the targeted planning resources.

All packages, procedures, and functions are declared as public and are intended for external invocation from forms, concurrent programs, and custom extensions. Internal helper logic is not exposed, keeping the supported interface limited to the documented REFRESH_RATES entry point.

Tables Accessed

The package references its data through APPS synonyms. The documented tables are:

• PA_BUDGET_VERSIONS — Stores budget version definitions used to resolve and validate the plan version being updated.
• PA_BUDGET_LINES — Holds the budget line detail whose planning amounts and rates are refreshed during a Financial plan calculation.
• PA_RESOURCE_ASSIGNMENTS — Contains the planning resource assignments for which cost and conversion rates are recalculated, including Workplan resources.
• DUAL — Used for scalar lookups, default value resolution, and simple PL/SQL expressions.
• PLITBLM — The PL/SQL table (index-by table) used to hold and pass the collection of resource class codes supplied through the optional table parameter.

These tables collectively supply the version context, the planning resource scope, and the line-level amounts required for a bulk rate refresh.

Usage Notes

PA_FP_CALC_PLAN_PUB.REFRESH_RATES is typically invoked from Oracle Project Management and Project Costing planning pages when a user requests a rate refresh, and from concurrent programs that process rate recalculation in the background. It is also a supported integration point for custom code and extensions that need to programmatically refresh cost or conversion rates for a project plan.

Regarding the search term "check_edit_task_ok": no procedure, function, or internal routine of that name is documented in the ETRM metadata for this package, and the package's documented public surface consists solely of REFRESH_RATES. The name may originate from an internal or site-specific validation routine within the broader PA financial planning codebase rather than from this package. Because the package is a public API, callers should limit interaction to REFRESH_RATES and should not depend on undocumented internal procedures, whose behavior and signatures may change between releases. As with other public AMG APIs, all mandatory parameters must be validated by the caller, and security checks are enforced internally before updates are applied.