Search Results get_period_start_date5

Overview

PA_FIN_PLAN_VIEW_GLOBAL is a global PL/SQL specification package in the Oracle E-Business Suite Projects (PA) module, owned by the APPS schema. It serves as the session-level state container for the Financial Plan "view by" functionality, which allows users to define and display project financial plans such as budgets, forecasts, and revenue plans across configurable time periods. The package is classified as OTHER within the ETRM documentation for 12.1.1 and 12.2.2.

Rather than storing values in a persistent table, the package holds global variables (prefixed G_FP_) that represent the current financial plan context: organization ID, view version ID, plan type, resource assignment, amount type code, adjustment reason code, currency code and type, period type, plan dates, and thirteen distinct period start and end dates. These globals are populated upstream — typically by an Oracle Forms session — and then read by other program units to drive queries, insertions, and updates against the financial plan tables. The package also encapsulates the logic that translates the view-by selection into table updates and navigation period handling.

Key Procedures and Functions

The documented API surface contains 30 procedures and functions. The setters write session state: PA_FP_SET_ORGFCST_VERSION_ID establishes the financial plan version context, PA_FP_SET_ADJ_REASON_CODE sets the adjustment reason used for revenue and adjustment lines, and PA_FP_VIEWBY_SET_GLOBALS applies a broader "view by" configuration across the global variables in a single call. PA_FP_SET_PERIODS and PA_FP_SET_PERIODS_NAV populate the period start and end date variables, the latter supporting period navigation logic. PA_FP_UPDATE_TABLES performs the persistence work implied by the current globals, and PA_FP_GET_BUDGET_STATUS_CODE derives a budget status code for display or validation.

The getter functions mirror the globals and constitute the read interface consumed by other packages: GET_VERSION_ID, GET_ORG_ID, GET_PLAN_TYPE_ID, GET_RESOURCE_ASSIGNMENT_ID, GET_AMOUNT_TYPE_CODE, GET_ADJ_REASON_CODE, GET_CURRENCY_CODE, GET_CURRENCY_TYPE, and GET_PERIOD_START_DATE1 through GET_PERIOD_START_DATE5. Of these, GET_AMOUNT_TYPE_CODE is the accessor most frequently referenced by callers, because the amount type code — COST, REVENUE, and similar values — determines which financial plan amounts are retrieved and displayed. Additional accessors for later period dates are documented in the full 30-member API list.

Tables Accessed

Through APPS synonyms the package references PA_BUDGET_LINES and PA_BUDGET_VERSIONS, the baseline budget structures that supply and receive plan amounts against a named version. PA_FIN_PLAN_ADJ_LINES and PA_FP_ADJ_ELEMENTS support adjustment line processing driven by the amount type and adjustment reason globals. PA_PROJ_FP_OPTIONS stores financial plan configuration at the project level, while PA_PROJ_PERIOD_PROFILES and PA_PROJ_PERIODS_DENORM provide the period definitions and denormalized period data used to resolve the view start and end dates. PA_PROJECTS_ALL supplies project-level attributes, and PA_RESOURCE_ASSIGNMENTS identifies the resource context for plans restricted to a specific assignment. DBMS_SQL indicates dynamic SQL construction, and NLS_SESSION_PARAMETERS supports environment-aware formatting of dates and currency values.

Usage Notes

The package is invoked primarily from the Financial Plan and Budget entry forms of the Projects application, where form-level triggers call the setters on query and navigation and the getters on display and validation. Because the globals are session-scoped, callers must ensure the appropriate setter runs before any dependent getter; a stale G_FP_VIEW_VERSION_ID or G_FP_AMOUNT_TYPE_CODE will produce incorrect plan data. PA_FP_UPDATE_TABLES is normally executed as part of the form save cycle rather than from concurrent programs. Custom extensions that call this package should follow the same pattern as the seeded forms. The ETRM metadata records that the package is referenced by 14 other packages, confirming it as a shared context provider rather than a standalone utility.