Search Results fii_time_rpt_struct_v




Overview
Explore in AI Chat

Overview

FII_TIME_RPT_STRUCT_V is an internal Oracle E-Business Suite view belonging to the FII (Financial Intelligence) product family, which is documented in ETRM as obsolete in Release 12.1.1 and 12.2.2. The view exists to support Time Dimension roll-up functionality within DBI (Daily Business Intelligence), the predecessor reporting framework that fed aggregated financial and operational data into summary dashboards. In the EBS reporting and integration stack, this view does not represent a public API or a user-facing reporting object; rather, it is a filtered projection over an underlying structure table that constrains the rows returned to those relevant for time-hierarchy aggregation.

The view is documented in ETRM as "Not implemented in this database," meaning the object is not instantiated in the standard EBS schema delivered with the release. Its presence in the documentation reflects a legacy or product-specific configuration rather than a universally available database object. Consequently, queries against this view are only meaningful in environments where the FII/DBI Time Dimension structures have been deployed.

Underlying Base Objects

The documented view text defines the object entirely over a single base table:

  • FII_TIME_RPT_STRUCT — the physical structure table holding calendar, time, and period-type rows with the aggregation attributes required for time roll-up.

The view selects all listed columns from this table without joins, unions, or transformations, applying only a restrictive predicate on RECORD_TYPE_ID. ETRM documents no other referenced base objects for this view, and no foreign-key or lookup relationships are exposed at the view level. Because the view is defined over one table and performs only row filtering, it inherits the storage and partitioning characteristics of FII_TIME_RPT_STRUCT directly.

Key Columns

The view projects eleven columns from the base table:

  • CALENDAR_ID — identifier of the calendar (for example, the accounting or reporting calendar) to which the time structure belongs.
  • CALENDAR_TYPE — classification of the calendar, distinguishing calendar variants used in time aggregation.
  • REPORT_DATE — the reporting date associated with the structure row.
  • TIME_ID — identifier of the time dimension member.
  • PERIOD_TYPE_ID — identifier of the period type (day, week, month, quarter, year, and similar granularities).
  • RECORD_TYPE_ID — the discriminator that determines which rows are eligible for the roll-up; the view restricts this column to the values 1, 2, 4, 8, 16, 32, 64, and 1024.
  • CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, LAST_UPDATE_LOGIN — standard EBS audit columns recording insert and update identity and timestamps.

The RECORD_TYPE_ID predicate is the defining characteristic of the view. The selected values correspond to a bitmask-style set of record categories, indicating that only specific structural record classes participate in the time roll-up exposed through this view.

Common Use Cases and Queries

Because the view is an internal DBI artifact, its primary consumer is the Time Dimension roll-up process and any dependent DBI summary programs. Analysts or support engineers may query it to inspect which time-structure rows are eligible for aggregation, or to diagnose discrepancies in time-hierarchy summaries. A typical query is:

  • Inspect eligible roll-up rows: SELECT calendar_id, report_date, time_id, period_type_id, record_type_id FROM fii_time_rpt_struct_v WHERE calendar_id = :p_calendar_id ORDER BY report_date;
  • List distinct record categories present: SELECT record_type_id, COUNT(*) FROM fii_time_rpt_struct_v GROUP BY record_type_id;
  • Compare view output with the base table: SELECT COUNT(*) FROM fii_time_rpt_struct WHERE record_type_id IN (1,2,4,8,16,32,64,1024) MINUS SELECT COUNT(*) FROM fii_time_rpt_struct_v;

Since FII is documented as obsolete, these queries are relevant only for legacy DBI environments. In current 12.1.1 and 12.2.2 implementations the object is generally absent, and equivalent functionality is delivered through later BI Publisher and Oracle BI Enterprise Edition data models rather than through FII time-structure views.