Search Results set_pc_approved_flag

Overview

FPA_PLANNINGCYCLE_PVT is a private PL/SQL package in the APPS schema that encapsulates the business logic for creating and maintaining Planning Cycles within the Oracle E-Business Suite Enterprise Planning and Budgeting (EPB) / Financial Planning application. A planning cycle represents a discrete planning period — for example a fiscal year or a budget round — under which planning objects, financial targets, investment criteria, calendars and discount rates are grouped and subsequently approved. The package name suffix "PVT" indicates that it is an internal implementation package rather than a published public API; the public wrapper packages and the EPB forms layer call into it. The header comment identifies the source file as FPAVPCPS.pls and records the package as shipped under version 120.2 (November 2005), which is consistent with its presence in both EBS 12.1.1 and 12.2.2 environments. The package is referenced by two other packages, reflecting its role as a shared service layer for planning-cycle maintenance.

Key Procedures and Functions

The documented interface exposes nineteen procedures, each focused on a single aspect of planning-cycle state. Notable examples include:

• CREATE_PC — the primary creation routine invoked when a user or process establishes a new planning cycle; it accepts an API version and a planning-cycle all-object structure and returns the generated planning cycle identifier together with the standard return status, message data and message count.
• UPDATE_PC_INVEST_MIX — updates the investment mix matrix associated with a cycle.
• UPDATE_PC_FIN_TARGETS — maintains the financial targets table for the cycle.
• UPDATE_PC_INV_CRITERIA_DATA — refreshes investment criteria rows that drive plan evaluation.
• UPDATE_PC_DESC_FIELDS — updates the descriptive (translatable) attributes of the planning cycle.
• UPDATE_PC_CLASS_CATEGORY — associates a class category with a planning cycle by identifier.
• UPDATE_PC_CALENDAR — adjusts the calendar definition used for period mapping.
• UPDATE_PC_CURRENCY and UPDATE_PC_SUB_DUE_DATE — maintain currency and submission due-date attributes.
• SET_PC_STATUS, SET_PC_INITIATE_DATE, SET_PC_APPROVED_FLAG and SET_PC_LAST_FLAG — state-transition helpers controlling cycle lifecycle, initiation, approval and the designation of the current/last cycle.
• UPDATE_PC_DISCOUNT_FUNDS and UPDATE_PC_ANNUAL_DISC_RATES — maintain discount funding and annual discount rate information.
• CHECK_PC_NAME — validation routine confirming uniqueness of a requested planning-cycle name.
• PA_DISTRB_LISTS_INSERT_ROW and PA_DIST_LIST_ITEMS_UPDATE_ROW — distribution-list maintenance helpers bridged into the planning-cycle flow.
• SET_PC_INVESTMENT_CRITERIA — establishes the investment criteria set for the cycle.

Consistent with Oracle's PVT coding standards, mutating procedures follow the (p_api_version, …payload…, x_return_status, x_msg_data, x_msg_count) signature convention.

Tables Accessed

The package reads and writes a small, focused set of tables accessed through APPS synonyms. FPA_PLANNING_CYCLE_S is the primary planning-cycle base table where cycle records are created and updated. FPA_OBJECTS_TL stores translatable planning object names and descriptions, supporting the descriptive-field and translation logic. PA_OBJECT_DIST_LISTS holds distribution lists used to route planning cycle output and access control, explaining the two PA_DIST* helper procedures. FND_LANGUAGES, NLS_SESSION_PARAMETERS and DUAL are referenced for language handling and NLS-dependent evaluation. DBMS_AW and PLITBLM appear as supporting utilities for analytic workspace and PL/SQL table operations.

Usage Notes

As a PVT package, FPA_PLANNINGCYCLE_PVT is not intended for direct customer invocation. It is normally called from the Enterprise Planning and Budgeting administrative forms when a planner creates or edits a planning cycle, and from concurrent programs that batch-update cycle status, financial targets or investment criteria. Because CREATE_PC is the entry point surfaced by the user's "create_pc" search, custom integrations requiring programmatic cycle creation should prefer the officially published EPB API wrapper rather than calling this package directly. Any direct call must supply a valid API version, the correctly populated fpa_pc_all_obj structure, and must inspect x_return_status for 'S', 'E' or 'U' before committing, since the package signals errors through the standard message stack rather than raising exceptions.