Results for “pa_fp_pd_startdates_v”

16 results




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

Overview

The PA_FP_PD_STARTDATES_V view resides in the APPS schema and belongs to the Oracle Projects (PA) product family. According to its documented description, it is created specifically to drive the "start period" poplist within the Project Financial Planning and forecasting (FP) functionality. In Oracle EBS 12.1.1 and 12.2.2, poplists provide the list of valid values a user can select in a form or page field; this view supplies the set of eligible accounting periods that a planner may choose as a plan's start period.

Rather than exposing a physical table, the view presents a filtered, context-sensitive slice of period data. Its output is constrained dynamically at runtime by two package functions, PA_FP_VIEW_PLANS_PUB.GET_PLAN_START_DATE() and PA_FP_VIEW_PLANS_PUB.GET_PLAN_END_DATE(), which return the effective start and end boundaries of the plan currently in context. The result is a view whose row set changes depending on the active planning session. It is a read-only, presentation-oriented object rather than a transactional one, and it does not store data.

Underlying Base Objects

The view is defined over two documented dependencies:

  • PA_FP_PERIODS_TMP_V (VIEW) — the immediate source of the period rows. This underlying view supplies the period type, year, name, and date boundaries that PA_FP_PD_STARTDATES_V selects and then further filters.
  • PA_FP_VIEW_PLANS_PUB (PACKAGE) — a public API package whose functions provide the plan start and end dates used in the WHERE clause. The view calls these functions to restrict the returned periods to those falling within the active plan's range.

Because the dependency chain terminates in another view rather than a base table, the object is layered: PA_FP_PD_STARTDATES_V filters PA_FP_PERIODS_TMP_V, which in turn derives its own data from the period definitions stored elsewhere in the Applications schema. This layered design keeps the poplist logic isolated and avoids duplicating period derivation logic at each point of use.

Key Columns

The view text exposes five columns, each projecting directly from the source view:

  • PERIOD_TYPE — the accounting period type (for example, a monthly or weekly calendar), used to distinguish different period sets.
  • PERIOD_YEAR — the fiscal or calendar year to which the period belongs.
  • PERIOD_NAME — the user-facing name of the period, typically the value returned to the poplist as the selectable label.
  • START_DATE — the first date of the period; used both for display and for the dynamic range filter.
  • END_DATE — the last date of the period; used to enforce that the period closes within the plan's end boundary.

The filter applies START_DATE >= plan start and END_DATE <= plan end, ensuring only periods wholly contained within the active plan window are offered.

Common Use Cases and Queries

The primary use case is driving the start-period list of values in forecast and plan entry. Understanding the view is also useful when diagnosing why a particular period is missing from the poplist, since the answer usually lies in the plan start/end boundaries returned by the package. A typical query to inspect available start periods is:

  • SELECT period_type, period_year, period_name, start_date, end_date FROM apps.pa_fp_pd_startdates_v ORDER BY start_date;

To filter for a specific period type or year, add predicates on the projected columns. Because the WHERE clause invokes package functions, results depend on the caller's session context; in SQL*Plus or a reporting tool outside a planning session, the returned range may default or return no rows. For this reason the view is best treated as a form-support object rather than a general reporting source, and customization should avoid altering its filter logic.