Results for “time_id”

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

Overview

FII_SRS_ALL_TIME_PERIODS_V is an Oracle EBS Financial Intelligence (FII) view owned by the APPS schema. In EBS 12.1.1 and 12.2.2, its primary role is to supply the list of values (LOV) for time period selection within the FII Integrator. The FII Integrator is the component that assembles and submits Financial Intelligence reporting requests, and it must present users with a consolidated, consistent picklist of the time periods available for a report parameter.

The view produces a normalized, uniform result set spanning three distinct time granularities — period, quarter, and year — plus a special literal entry that represents an undefined or not-applicable selection. Downstream FII report definitions and parameter pages query this view rather than each underlying time entity table individually, ensuring that a single LOV query returns every selectable time value regardless of granularity. The TIME_ID column acts as the returned value of the LOV, while NAME supplies the display text, and PERIOD_TYPE_ID and PERIOD carry the classification needed to interpret what kind of time value was chosen.

Underlying Base Objects

The documented view text identifies three FII time entity tables and one lookup source:

• FII_TIME_ENT_PERIOD — the period-level time entity; contributes rows with PERIOD_TYPE_ID = 32 and PERIOD = 'P'.
• FII_TIME_ENT_QTR — the quarter-level time entity; contributes rows with PERIOD_TYPE_ID = 64 and PERIOD = 'Q'.
• FII_TIME_ENT_YEAR — the year-level time entity; contributes rows with PERIOD_TYPE_ID = 128 and PERIOD = 'Y'.
• FND_LOOKUP_VALUES — the Oracle Application Object Library lookup table, used here to supply the literal 'N/A' entry from lookup type FII_LITERAL.

Each entity table contributes its NAME column as the display value and its own entity identifier (ENT_PERIOD_ID, ENT_QTR_ID, ENT_YEAR_ID) as TIME_ID. The four branches are combined with UNION (not UNION ALL), so any duplicate NAME/TIME_ID combinations across branches are suppressed. The lookup branch is filtered by LOOKUP_TYPE = 'FII_LITERAL', LOOKUP_CODE = 'N/A', LANGUAGE = USERENV('LANG'), VIEW_APPLICATION_ID = 450, and a SECURITY_GROUP_ID obtained from FND_GLOBAL.LOOKUP_SECURITY_GROUP. This enforces language sensitivity and respects Oracle's lookup security grouping.

No intermediate views or additional FII base objects are documented beyond these four sources.

Key Columns

• NAME — display text for the LOV entry. Sourced from the NAME column of the relevant time entity table, or from LK.MEANING for the 'N/A' literal. This is what the user sees in the picklist.
• TIME_ID — the LOV return value. Equal to ENT_PERIOD_ID for period rows, ENT_QTR_ID for quarter rows, ENT_YEAR_ID for year rows, and -1 for the 'N/A' literal. Consumers must interpret TIME_ID together with PERIOD_TYPE_ID, because the same numeric value may be meaningful in only one granularity.
• PERIOD_TYPE_ID — numeric discriminator: 32 = period, 64 = quarter, 128 = year, -1 = not applicable. These constants correspond to FII period-type semantics and are used by the integrator to route the selected value.
• PERIOD — single-character granularity indicator: 'P', 'Q', 'Y', or 'N/A'. Convenient for filtering and for readable output.

Common Use Cases and Queries

The most common use is driving the time period LOV parameter in the FII Integrator, but the view is equally suitable for ad hoc reporting, validation, and joins. Practical examples:

• Populate an LOV or parameter listbox:
  SELECT name, time_id, period_type_id, period FROM fii_srs_all_time_periods_v ORDER BY period_type_id, name;
• List only year-level values:
  SELECT name, time_id FROM fii_srs_all_time_periods_v WHERE period = 'Y';
• Look up the display name for a known TIME_ID:
  SELECT name, period FROM fii_srs_all_time_periods_v WHERE time_id = :p_time_id;
• Drive a parameter form with the period type:
  SELECT time_id, name FROM fii_srs_all_time_periods_v WHERE period_type_id = 32;

Because the view is an APPS-owned dictionary object with a documented column list, it can be referenced directly by custom concurrent programs, OAF pages, and Oracle Reports in 12.1.1 and 12.2.2 without needing to re-derive the period union logic. Note that the LANGUAGE predicate and lookup security filter mean the 'N/A' row is returned only for the session's language, so results can vary by NLS configuration. When used as an LOV, always return TIME_ID while displaying NAME, and retain PERIOD_TYPE_ID or PERIOD in the record group so the integrator can determine which FII time entity the selection came from.