Search Results fpa_scenario_s

Overview

FPA_SCENARIO_PVT is a private PL/SQL package body in the APPS schema that implements the core scenario-management logic for Oracle Enterprise Planning and Budgeting / Enterprise Resource Planning (EPB) within Oracle E-Business Suite 12.1.1 and 12.2.2. In Oracle EBS the "_PVT" suffix denotes a private API package, meaning it is not intended for direct invocation by external integrators or custom code. Rather, it underpins the public-facing scenario APIs and the relevant application forms and concurrent programs. A "scenario" in this context represents a named budgeting or planning container within which project, funding, and cost data are modelled, compared, and approved. The package coordinates scenario creation and duplication, locking and approval workflow transitions, discount-rate and funds-availability configuration, working/initial/recommendation flag maintenance, and project-level ranking and calculation. The object is documented as VALID in the ETRM repository and is referenced internally by two other database objects while itself depending on the FND_API, FND_MSG_PUB, FND_LOG, DBMS_AW (OLAP analytic workspace), and several FPA views and tables.

Key Procedures and Functions

The documented package exposes fifteen procedures that fall into four functional groupings.

• Scenario lifecycle: CREATE_SCENARIO (instantiates a new scenario record), CHECK_SCENARIO_NAME (validates uniqueness and naming rules), LOCK_SCENARIO (locks a scenario against further modification), and CALC_SCENARIO_DATA (executes the scenario calculation engine).
• Data duplication: COPY_SCENARIO_DATA (clones scenario-level data) and COPY_SCE_PROJECT_DATA (clones associated project data), supporting "copy from" style planning workflows.
• Flag and configuration updates: UPDATE_SCEN_APPROVED_FLAG, UPDATE_SCENARIO_INITIAL_FLAG, UPDATE_SCENARIO_WORKING_FLAG, UPDATE_SCENARIO_RECCOM_FLAG, UPDATE_SCENARIO_RECCOM_STATUS, UPDATE_SCENARIO_DISC_RATE, and UPDATE_SCENARIO_FUNDS_AVAIL collectively govern the approval state, the initial/working/recommendation designations, discount-rate parameters, and the funds-availability setting of a scenario.
• Project association and ranking: REMOVE_PROJECT_FROM_SCENARIO and UPDATE_PROJ_USER_RANKS manage which projects belong to a scenario and how users have ranked them.

Because this is a private package, parameter signatures are not published in the ETRM excerpt; integrators should target the corresponding public API rather than call these procedures directly.

Tables Accessed

Via APPS synonyms, the package reads and writes the following documented objects:

• FPA_SCENARIO_S — the base scenario definition table; the primary read/write target for the scenario lifecycle procedures.
• FPA_OBJECTS_TL — the translated names/descriptions table providing language-specific labels for scenario-related objects.
• FND_LANGUAGES and NLS_SESSION_PARAMETERS — used to resolve the current session language for translation lookups.
• DBMS_AW and DUAL — DBMS_AW is the Oracle OLAP analytic workspace PL/SQL package, invoked for dimension/analytic calculations; DUAL supports control-of-flow queries.
• PLITBLM — the PL/SQL integer table type used for in-memory collections during processing.

The dependency listing also references FPA_AW_SCES_V, FPA_AW_SCE_INFO_V, FPA_AW_PC_DISC_FUNDS_V, FPA_SCES_VL, and the FPA_SCEN_PROJ_USERRANK_TBL/OBJ structures, which supply the analytic-workspace and user-ranking data consumed during calculation and copy operations.

Usage Notes

FPA_SCENARIO_PVT is an internal implementation package and is not referenced by any external database object in the ETRM metadata. It is invoked indirectly from the EPB scenario setup and administration forms, from scenario copy and calculation concurrent programs, and from the public scenario API wrappers that share its namespace. Calls are normally made within the FND_API error-handling and FND_MSG_PUB messaging framework, so callers should expect standard EBS API semantics (message stack population and FND_LOG diagnostics). Custom developers requiring scenario functionality should use the supported public APIs rather than this _PVT body, since private packages are subject to change without notice across 12.1.1 and 12.2.2 patch levels.