Results for “calendar_name”

50+ results




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

Overview

FPA_AW_CALENDARS_V is a documented Oracle E-Business Suite view owned by the APPS schema and classified under the FPA – Project Portfolio Analysis product. In Oracle EBS 12.1.1 and 12.2.2, its role is to expose calendar metadata from the Project Portfolio Analysis analytical workspace (AW) so that calendars, their period types, and their calendar hierarchy names can be reported on using ordinary SQL. Unlike conventional relational views that join stored tables, this view is defined over an OLAP_TABLE function invocation. It therefore surfaces analytical workspace dimension data — specifically the DURATION dimension members held in the OLAP analytic workspace — as rows and columns consumable by standard EBS reporting, interfaces, and custom extensions.

Users searching for "calendar_name" encounter this view because CALENDAR_NAME is its primary identifying column and the natural filter predicate for calendar-specific queries. The view thus functions as the reporting-side bridge between the OLAP analytic workspace populated for Project Portfolio Analysis and the relational reporting environment.

Underlying Base Objects

The view text is defined over an OLAP_TABLE call rather than over physical base tables. Two objects are documented as referenced:

  • FPA_UTILITIES_PVT (PACKAGE) — supplies AW_SPACE_NAME, the analytic workspace identifier used to construct the query string passed to OLAP_TABLE.
  • OLAP_TABLE (SYNONYM) — the Oracle OLAP API function that maps analytic workspace dimension and measure data into relational rows and columns.

The OLAP_TABLE invocation specifies the DURATION QUERY against the analytic workspace and maps the result into the FPA_CALENDAR_MAIN_TBL table structure using the LMT PERIOD_TYPE_D TO PERIOD_TYPE_CALENDAR_R limit map. Dimension members are extracted via DIMENSION CALENDAR_NAME FROM CALENDAR_D, with PERIOD_TYPE drawn from PERIOD_TYPE_CALENDAR_R and CAL_HIERARCHY_NAME from CAL_HIERARCHY_CAL_PERIOD_TYPE_R. Because the view depends on a populated analytic workspace, its results reflect the state of the Project Portfolio Analysis AW rather than static transaction tables.

Key Columns

  • CALENDAR_NAME — the name of the calendar dimension member exposed from the CALENDAR_D dimension. This is the column most commonly used to identify, filter, and join calendar records.
  • PERIOD_TYPE — the period type associated with the calendar, returned through the PERIOD_TYPE_CALENDAR_R relationship. It indicates the granularity or period classification that the calendar uses for duration-based analysis.
  • CAL_HIERARCHY_NAME — the name of the calendar hierarchy, sourced from the CAL_HIERARCHY_CAL_PERIOD_TYPE_R relationship, which links calendars to the hierarchy in which their periods are organized.

Together, the three columns describe a calendar, its period type, and the hierarchy it participates in. They form the metadata backbone used when analysts and reports need to resolve which calendar drives duration calculations in Project Portfolio Analysis.

Common Use Cases and Queries

Typical uses include validating which calendars are available to Project Portfolio Analysis, driving LOV-style lookups for calendar selection, and reconciling calendar definitions between the analytical workspace and relational reporting.

A basic lookup by name is the most frequent pattern:

SELECT calendar_name, period_type, cal_hierarchy_name
FROM apps.fpa_aw_calendars_v
WHERE calendar_name = :p_calendar_name;

To enumerate all calendars with their period types:

SELECT calendar_name, period_type
FROM apps.fpa_aw_calendars_v
ORDER BY calendar_name;

To list calendars belonging to a specific hierarchy or period type, filter on the corresponding column. Because the view resolves through OLAP_TABLE against the populated analytic workspace, queries should be executed in a session where the FPA analytic workspace is available; otherwise OLAP_TABLE returns no rows or raises an error. This behavior is the principal operational caveat when using FPA_AW_CALENDARS_V for reporting or integration in EBS 12.1.1 and 12.2.2.