Search Results seq_id




Overview
Explore in AI Chat

Overview

FII_TANDE_RMNTH_EXP_SUM_V is a database view historically delivered within the Oracle E-Business Suite Financial Intelligence (FII) product family. In the ETRM documentation set for Oracle EBS 12.1.1 and 12.2.2, the object is catalogued under the FII module with an explicit "Obsolete" designation and the implementation note "Not implemented in this database." Consequently, the view is documented as legacy metadata only; it is not created in a standard, current 12.1.1 or 12.2.2 application database.

Where deployed, the view presents a monthly expense summary projection built around a sequence identifier (SEQ_ID), a month label, current-year and prior-year expense measures, and a chain of fourteen hierarchical level keys. Its function was to serve as a reporting read-layer over the underlying summary table, exposing a stable, presentation-friendly column set for period-over-period expense comparison and dimensional drill-down.

Underlying Base Objects

The view text identifies a single direct base object: FII_TANDE_RMNTH_EXP_SUM. The view performs no joins and introduces no aggregate functions or GROUP BY clauses; it is a straight projection with one transformation. The documented view text is:

  • SELECT clause projecting SEQ_ID, MONTH_NAME, CYR_EXP, PYR_EXP, and LEVEL9_KEY through LEVEL15_KEY.
  • MONTH_NAME is passed through SUBSTR(MONTH_NAME, 1, 3), truncating the stored month value to its first three characters.
  • All remaining columns are selected unchanged from FII_TANDE_RMNTH_EXP_SUM.

No referenced base objects beyond FII_TANDE_RMNTH_EXP_SUM are documented in the ETRM metadata. The view therefore inherits its grain, row count, and dimensional semantics entirely from that summary table.

Key Columns

  • SEQ_ID — A sequence identifier carried over from the base table. It provides a unique or near-unique row key for the summarised expense record and is commonly used for ordering, joining, or deduplication logic in extracts.
  • MONTH_NAME — The reporting month, truncated to three characters (for example, JAN, FEB, MAR). This abbreviation supports compact column headers and stable month bucketing in reports.
  • CYR_EXP — Current-year expense amount for the month identified by the row.
  • PYR_EXP — Prior-year expense amount for the same month, enabling period-over-period variance calculation directly in the query.
  • LEVEL9_KEY through LEVEL15_KEY — Seven contiguous hierarchical key columns representing the deepest available levels of the accounting or organisational flexfield dimension set. They permit grouping, filtering, and drill-down at the lowest (level 9 to level 15) summarisation tiers.

Common Use Cases and Queries

Because the object is obsolete and documented as not implemented, the primary practical value is historical reference and migration assessment. Where an installation retains the legacy object, typical usage is monthly expense variance reporting and drill-down to low-level hierarchy keys.

  • Variance analysis: selecting MONTH_NAME with (CYR_EXP - PYR_EXP) to expose month-over-month expense movement.
  • Lowest-level roll-ups: grouping by LEVEL15_KEY (or the deepest populated key) to aggregate expense by the most granular dimension.
  • Ordered extracts: ORDER BY SEQ_ID to produce a stable, reproducible report sequence.

A representative query is:

Before adapting any such query for 12.1.1 or 12.2.2, confirm object existence in the target database, since the ETRM metadata records FII_TANDE_RMNTH_EXP_SUM_V as not implemented.