Search Results create_versions_init

Overview

PA_FIN_PLAN_CREATE_VER_GLOBAL is a global PL/SQL package body owned by APPS and classified under API classification OTHER within Oracle E-Business Suite. It provides supporting server-side logic for the Organization Forecast: Create Versions page, which is the interface used by project managers and planners to generate financial plan versions (budgets and forecasts) against a project. The package is not a business transaction API in the conventional sense; rather, it is a controller-style utility package that caches session context values, resolves lookup meanings and descriptive names, derives GL and Project Accounting period ranges, and initializes the version creation process. The header comment identifies the package purpose succinctly as "API's for Org Forecast: Create Versions Page." The version string in the header ($Header: PAFPCVGB.pls 120.2) and the 2005 timestamp indicate this object has remained stable across the 11i and R12 code lines, and it is present in both 12.1.1 and 12.2.2 environments. Two other packages reference this package, meaning it participates in a small dependency chain rather than standing alone.

Key Procedures and Functions

The package exposes sixteen documented procedures and functions, which fall into three logical groups.

• Global value setters and getters: SET_PROJECT_ID, SET_FIN_PLAN_TYPE_ID, and SET_BUDGET_VERSION_ID store the three core context identifiers, while GET_PROJECT_ID, GET_FIN_PLAN_TYPE_ID, and GET_BUDGET_VERSION_ID return them. These are backed by package-level globals (G_PROJECT_ID, G_FIN_PLAN_TYPE_ID, G_BUDGET_VERSION_ID) declared in the package body. SET_GLOBAL_VALUES is the composite entry point — the object the user searched for — that assigns all three context values in a single call, allowing a calling form or program to prime the package state before further processing.
• Lookup and descriptive name resolvers: GET_LOOKUP_PLANNING_LEVEL translates a planning level code from the BUDGET ENTRY LEVEL lookup type into its display meaning; GET_LOOKUP_TIME_PHASE translates a time-phased code from the BUDGET TIME PHASED TYPE lookup type; GET_RESOURCE_LIST_NAME returns the translated name of a resource list from PA_RESOURCE_LISTS_TL.
• Period and initialization routines: GET_GL_CURRENT_START_PERIOD, GET_GL_CURRENT_END_PERIOD, GET_PA_CURRENT_START_PERIOD, GET_PA_CURRENT_END_PERIOD, and GET_START_END_PERIOD derive current accounting period boundaries from the GL and Project Accounting calendars respectively. CREATE_VERSIONS_INIT performs initialization for the version creation flow.

Tables Accessed

The package reads configuration and reference data from ten documented tables. PA_PROJ_FP_OPTIONS and PA_FORECASTING_OPTIONS_ALL supply the financial plan option settings, including the planning level and time-phased codes that the lookup functions translate. PA_BUDGET_VERSIONS and PA_FIN_PLAN_TYPES_B hold the version and plan type definitions used when a version is created. PA_PROJECTS_ALL and PA_PROJECT_TYPES_ALL provide project and project type context. PA_RESOURCE_LISTS_TL supplies translated resource list names. GL_PERIODS and PA_PROJ_PERIOD_PROFILES are used by the period derivation functions to determine the current GL period and the Project Accounting period profile boundaries. PA_IMPLEMENTATIONS_ALL is consulted for installation-level settings. The documented operations are predominantly reads, consistent with a page-support package whose write activity is confined to the version creation initialization.

Usage Notes

This package is invoked from the Organization Forecast Create Versions page in the Projects forms module, where SET_GLOBAL_VALUES is called first to populate project, plan type, and version context, and the getter functions subsequently retrieve those values for display and validation. The lookup functions populate descriptive flexfield-style display fields on the page, converting stored codes into user-readable meanings. The period functions establish default start and end periods for the version being created. Because the package relies on package-level global state, it is not re-entrant across concurrent sessions in the same database session context; callers should invoke SET_GLOBAL_VALUES immediately before the dependent operations. Custom code extending the Create Versions flow may call the getters and lookup resolvers directly, but should treat the package as an internal support object rather than a supported public API, since it carries no formal API documentation and is classified as OTHER.