Results for “plan_period_type”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The view PA_FP_PERIOD_INFO_V is an APPS-owned database view within the Oracle E-Business Suite Projects (PA) module. Its status is VALID across Oracle EBS 12.1.1 and 12.2.2, and it resides in the APPS schema, making it accessible to any responsibility or concurrent program that operates with APPS-privileged database connections. The object serves a narrowly defined purpose: it stores and exposes period information for financial plan (budget) versions. In practice, the view acts as a thin, context-sensitive lookup that translates the currently selected budget version into its associated period profile attributes, allowing planning forms and reports to determine the period structure, calendar naming, and period count applicable to the plan being viewed.

Because its definition depends on a session-level package function rather than a static join condition, the view is dynamic in nature. It returns data relative not to an arbitrary user-supplied key, but to whichever budget version has been established in the current runtime context by the financial planning framework. This design makes the view a specialized component of the Project Financial Planning (FP) infrastructure rather than a general-purpose reporting object.

Underlying Base Objects

The documented base objects underlying this view are:

• PA_PROJ_PERIOD_PROFILES (referenced as a synonym) — supplies the period profile definition rows, including period type, GL period type, profile identifier, period count, and period set name.
• PA_BUDGET_VERSIONS (referenced as a synonym) — supplies the budget version record, which carries the PERIOD_PROFILE_ID used to join to the period profile table.
• PA_FIN_PLAN_VIEW_GLOBAL (package) — supplies the runtime context through its GET_VERSION_ID() function, which returns the budget version identifier for the current session.

The view text performs an inner join between PA_PROJ_PERIOD_PROFILES and PA_BUDGET_VERSIONS, where the budget version is filtered by the value returned from PA_FIN_PLAN_VIEW_GLOBAL.GET_VERSION_ID(), and the period profile is matched on PERIOD_PROFILE_ID. Consequently, the view yields exactly the period profile attributes corresponding to the budget version currently selected in the planning interface, and returns no rows when no version context is set.

Key Columns

• PLAN_PERIOD_TYPE — identifies the period type used by the plan, distinguishing the planning calendar granularity.
• PERIOD_PROFILE_ID — the unique identifier of the period profile associated with the budget version; this is the join key between the budget version and its period definition.
• GL_PERIOD_TYPE — the General Ledger period type, linking the planning periods to the GL calendar type used for accounting period alignment.
• NUMBER_OF_PERIODS — the count of periods defined within the profile, used to determine the planning horizon span.
• PERIOD_SET_NAME — the name of the accounting period set, indicating which GL period set the plan periods are drawn from.

Together these columns describe the temporal framework within which a budget version operates, enabling downstream logic to render period prompts, validate plan line entry against valid periods, and align plan data with GL accounting calendars.

Common Use Cases and Queries

The view is primarily consumed by financial planning forms and concurrent processes that need to know the period structure of the active plan version without re-deriving it from base tables. A typical query retrieves the period attributes for the session's current version:

• Period Structure Lookup: SELECT plan_period_type, gl_period_type, number_of_periods, period_set_name FROM pa_fp_period_info_v; — returns the profile attributes for the budget version currently set via the FIN_PLAN_VIEW package.
• Planning Horizon Validation: comparing NUMBER_OF_PERIODS against entered plan lines to confirm entries fall within the defined horizon.
• Calendar Alignment: using GL_PERIOD_TYPE and PERIOD_SET_NAME to reconcile plan periods with GL accounting periods during integration or reporting.

Because the result set depends on session context, callers must invoke the view after the version is established by the planning framework; querying it outside that context returns no rows. This behavior should be anticipated in any custom report or data extraction that references PA_FP_PERIOD_INFO_V.