Search Results pc_conversion_rate_type_m

Overview

APPS.FPA_AW_PC_INFO_V is a reporting view in the Oracle E-Business Suite Enterprise Resource Planning and Treasury / Enterprise Treasury Management (ETRM) application family. It exposes planning-cycle portfolio information held in the Oracle OLAP analytic workspace maintained by the ETRM funds planning infrastructure. Rather than selecting directly from a relational table, the view resolves its rows through a call to the OLAP_TABLE function, which materializes a two-dimensional result set from an analytic workspace query. The view therefore acts as the presentation layer between the multidimensional planning-cycle and scenario data stored in the OLAP workspace and conventional relational SQL consumers such as concurrent programs, BI Publisher reports, Oracle Reports, and OBIEE or Discoverer queries.

Because the view is owned by APPS and is defined over packaged OLAP access logic, it is intended primarily for read-only reporting. The scenario_count column, which users frequently search for, is derived within the analytic workspace rather than stored in a base planning table.

Underlying Base Objects

ETRM documentation records two referenced base objects for this view:

• FPA_UTILITIES_PVT (package) — provides the AW_SPACE_NAME constant, which is concatenated with the literal string ' duration query' to form the runtime name of the OLAP analytic workspace query.
• OLAP_TABLE (synonym) — the standard Oracle OLAP_TABLE function used to pivot analytic workspace data into rows and columns.

The OLAP_TABLE call references the target table type FPA_PC_INFO_TBL and maps workspace dimensions and measures to view columns. Dimensions include PLANNING_CYCLE (from PLANNING_CYCLE_D), PORTFOLIO, PC_STATUS, CALENDAR_NAME, PERIOD_TYPE, CAL_PERIOD_TYPE, SUBMISSION_DUE_DATE, and INITIATE_DATE. Measures include funding period dates, currency code, conversion rate type, PC category, and the scenario and approval flags. Notably, SCENARIO_COUNT is defined as the measure expression AW_EXPR statlen(limit(scenario_d to planning_cycle_scenario_r eq planning_cycle_d)), which counts the scenarios related to each planning cycle dimension member.

Key Columns

• PLANNING_CYCLE — the primary dimension member identifying the funds planning cycle.
• PORTFOLIO — portfolio attribute associated with the planning cycle.
• PC_STATUS — status of the planning cycle (for example, open, submitted, or approved).
• SCENARIO_COUNT — the number of scenarios related to the planning cycle, computed via the AW_EXPR statlen(limit(...)) construct. This is the column most often queried when users require a count of scenarios per cycle.
• CALENDAR_NAME, PERIOD_TYPE, CAL_PERIOD_TYPE — calendar and period attributes governing the cycle.
• SUBMISSION_DUE_DATE, INITIATE_DATE — dates controlling cycle timing.
• FUNDING_PERIOD_FROM, FUNDING_PERIOD_TO, EFFECTIVE_PERIOD_TO — funding horizon boundaries.
• CURRENCY_CODE, CONVERSION_RATE_TYPE, CONVERSION_RATE_DATE — currency and conversion parameters.
• PC_CATEGORY — classification of the planning cycle.
• LAST_APPROVED_FLAG, LAST_FLAG — indicators marking the latest approved and latest cycle records.

Common Use Cases and Queries

Typical usage includes listing active planning cycles with their scenario counts, identifying cycles awaiting submission based on SUBMISSION_DUE_DATE, and reconciling currency and funding period attributes for reporting.

• Count scenarios per cycle:
  SELECT planning_cycle, scenario_count FROM apps.fpa_aw_pc_info_v ORDER BY planning_cycle;
• List open cycles with due dates:
  SELECT planning_cycle, pc_status, submission_due_date FROM apps.fpa_aw_pc_info_v WHERE pc_status = 'OPEN';
• Retrieve only the latest approved cycles:
  SELECT planning_cycle, portfolio, last_approved_flag FROM apps.fpa_aw_pc_info_v WHERE last_approved_flag = 'Y';

Because the view delegates to OLAP_TABLE, performance depends on the analytic workspace being attached and available to the APPS session; queries will fail if the workspace query referenced by FPA_UTILITIES_PVT.AW_SPACE_NAME cannot be resolved.