Search Results start_date_period_r

Overview

APPS.FPA_AW_PERIOD_ATTS_V is a reporting view in the Oracle EBS Enterprise Performance Foundation / Financial Analytics (FPA) schema. It exposes calendar period attributes for the analytical workspace (AW) maintained by the FPA utilities package, presenting period hierarchy, identifier, and date boundary information in a relational, query-friendly form. The view is not a conventional join of base tables; instead it is defined over a table function that materializes period attributes from an Oracle OLAP analytic workspace at query time. This makes it a bridge between the multidimensional OLAP representation of time and standard SQL consumers such as concurrent programs, BI Publisher reports, and custom integrations.

Its principal role is to serve as a single, centralized source of period attributes so that dependent reporting objects and applications do not need to query the OLAP workspace directly. Reference to the "time_d" search term reflects the underlying OLAP dimension named TIME_D, from which the view's PERIOD column is projected.

Underlying Base Objects

The documented metadata identifies two referenced base objects:

• FPA_UTILITIES_PVT (PL/SQL package) — supplies the AW_SPACE_NAME constant used to build the OLAP workspace name, and contains the LMT_PERIOD_PRG program referenced in the view's OLAP_TABLE invocation.
• OLAP_TABLE (public synonym to the OLAP_TABLE SQL function) — the mechanism that converts OLAP workspace objects into rows and columns for relational consumption.

The view text invokes OLAP_TABLE with four arguments: the workspace name (concatenated with ' DURATION QUERY'), the target table FPA_PERIOD_TBL, the OLAP DML program CALL LMT_PERIOD_PRG('PERIOD'), and a dimension/attribute mapping string. The mapping declares dimensions CAL_HIER (from CAL_PERIOD_TYPE_D), PERIOD (from TIME_D WITH HIERARCHY), and PERIOD_PARENT (from CALENDAR_HIERARCHY_H), plus attributes PERIOD_NUMBER, START_DATE, and END_DATE drawn from the TIME_TIME_IDENTIFIER_R, START_DATE_PERIOD_R, and END_DATE_PERIOD_R relations respectively. Because these constructs reside in the OLAP workspace, the view is dependent on the workspace being built and current; if the workspace has not been refreshed, the view returns the stale or absent period set.

Key Columns

• CAL_HIER — The calendar hierarchy to which the period belongs (for example, a standard calendar vs. a fiscal or reporting calendar).
• PERIOD — The period member sourced from the TIME_D dimension; this is the primary identification of a period and is the column most relevant to a "time_d" style search.
• PERIOD_PARENT — The parent of the period within the hierarchy (for example, a quarter or year consolidating the period).
• PERIOD_NUMBER — A numeric identifier for the period (period sequence or time identifier), useful for ordering and arithmetic comparisons.
• START_DATE — The start date of the period.
• END_DATE — The end date of the period.

Collectively, these columns provide both the hierarchical context and the date boundaries needed to align transactions and balances to reporting periods.

Common Use Cases and Queries

Typical uses include validating period membership when loading or reconciling data, deriving period start and end dates for date-range filtering, and driving period prompts in reports.

Listing all periods in a hierarchy:

• SELECT cal_hier, period, period_number, start_date, end_date FROM apps.fpa_aw_period_atts_v ORDER BY cal_hier, start_date;

Resolving a specific period's boundaries:

• SELECT period, period_parent, start_date, end_date FROM apps.fpa_aw_period_atts_v WHERE period = :period_name;

Filtering transaction data to a period date range:

• SELECT t.* FROM my_transactions t, apps.fpa_aw_period_atts_v p WHERE p.period = :period_name AND t.trx_date BETWEEN p.start_date AND p.end_date;

Because the view is workspace-backed, users should confirm the AW is refreshed before relying on results, and joins should be qualified by CAL_HIER where multiple hierarchies exist.