Search Results copy_overrides




Overview
Explore in AI Chat

Overview

PA_RES_ASG_CURRENCY_PUB is a public PL/SQL package in the Oracle E-Business Suite Projects (PA) module that manages currency data associated with project resource assignments. Its primary business function is to maintain the currency-denominated amounts held against resource assignments across budget, forecast, and planning contexts. The package acts as a controlled entry point for creating, copying, rolling up, and deleting resource assignment currency records, ensuring that all currency-related changes respect versioning, calling-module validation, and override-copying rules.

The package belongs to the PA_FP (Forecast and Planning) family, as evidenced by the header reference to PAFPRBCS.pls and its dependency on FP_COLS structures from PA_FP_GEN_AMOUNT_UTILS. It is classified as a PUB package, meaning it is intended for external invocation by other application modules and integration points rather than purely as internal implementation detail. The documentation confirms it is referenced by 18 other packages, underscoring its central role in the planning data model.

Key Procedures and Functions

The documented interface exposes a single procedure:

  • MAINTAIN_DATA — The sole public procedure. It accepts a record of FP_COLS (the forecast/planning amount column structure) plus a set of control flags and returns status information to the caller. Its parameters govern the calling module context, whether records are to be deleted or copied, the source version from which data is drawn, the copy mode applied to overrides, and whether rollup and version-level behaviors are requested. Output parameters report overall return status, message count, and message data, following standard EBS API error-reporting conventions. The procedure centralizes the maintenance logic so that diverse callers — budget generation, forecast generation, workplan processing, WebADI, change management, plan copying, and upgrades — all funnel through a consistent code path.

The package also defines a series of named constants representing valid calling modules, including BUDGET_GENERATION, FORECAST_GENERATION, CALCULATE_API, UPDATE_PLAN_TRANSACTION, WORKPLAN, AMG_API, WEBADI, CHANGE_MGT, COPY_PLAN, and UPGRADE. It further defines valid copy modes: COPY_ALL and COPY_OVERRIDES. These constants are the mechanism by which the package verifies that a caller is authorized, via the IS_PUBLIC_CALLING_MODULE() function in PAFPRBCB.pls. The searcher's term "amg_api" corresponds directly to the G_AMG_API constant, meaning AMG_API is an explicitly recognized public calling module but not a standalone procedure or parameter.

Tables Accessed

The documented tables fall into three groups. Budget and planning definition tables — PA_BUDGET_VERSIONS and PA_BUDGET_LINES — provide the version context and the line-level planning amounts that drive currency assignment. Resource assignment master data — PA_RESOURCE_ASSIGNMENTS — supplies the assignment records to which currency amounts attach. The currency-specific storage tables — PA_RESOURCE_ASGN_CURR, its shadow table PA_RESOURCE_ASGN_CURR_S, and its temporary/staging table PA_RESOURCE_ASGN_CURR_TMP — hold the currency-denominated values that MAINTAIN_DATA creates, updates, copies, or deletes. PLITBLM is the standard EBS PL/SQL table used for in-memory message collection, supporting the X_MSG_COUNT and X_MSG_DATA outputs.

Usage Notes

This package is typically invoked programmatically by other server-side components rather than directly from a form. Typical entry points include the budget and forecast generation concurrent programs, workplan processing, WebADI uploads, change management transactions, plan copy operations, and upgrade scripts, each passing its own calling-module constant. The AMG_API constant indicates that the Advanced Management Gateway or associated programmatic API layer is an authorized caller. Because the calling module is validated against a fixed allow-list, custom code must either use one of the documented constants or coordinate with the IS_PUBLIC_CALLING_MODULE() logic. Callers should pass a properly populated FP_COLS record and always inspect X_RETURN_STATUS and the message outputs before committing, as the procedure reports all business-rule failures through this channel rather than raising unhandled exceptions.