Search Results ent_ly_end




Overview
Explore in AI Chat

Overview

FII_TIME_WH_API is an Oracle E-Business Suite PL/SQL API owned by the APPS schema that provides centralized warehouse and enterprise calendar calculations for the FII (Financial Intelligence) product family. Its core business function is to return standardized date boundaries and period keys — such as current quarter start, prior-year quarter start, current year-to-date start, and comparable end dates — for use in financial reporting, warehouse (WH) analytics, and period-over-period comparisons. Because financial reporting requires consistent, repeatable answers to questions like "when did this quarter begin?" or "what is the same date one year ago?", this package encapsulates those computations so that every consumer derives identical values rather than recalculating them independently. It is a read-only utility API: it does not create, update, or delete transactional data, and its only table interaction is querying the EDW time dimension tables.

Key Procedures and Functions

The documented interface exposes 25 procedures and functions, dominated by date-boundary accessors and primary-key resolvers. The

  • ENT_* boundary functions — ENT_CYCQ_START and ENT_CYCQ_END return the start and end dates of the current calendar quarter; ENT_LYCQ_START and ENT_LYCQ_END return the equivalent boundaries for the last year's calendar quarter, enabling year-over-year quarter comparison. ENT_CY_START, ENT_CY_END, ENT_LY_START, and ENT_LY_END provide the analogous boundaries for the current year and last year. ENT_LYCQ_TODAY1, ENT_LYCQ_TODAY2, and ENT_TODAY return day-level values tied to the current date within these periods.
  • TODAY / TODAYTIME — return the current date and the current date with time component respectively, acting as the single authoritative clock reference for the API.
  • GET_FQTR_START / GET_FQTR_END — fiscal quarter start and end resolution, allowing the fiscal calendar to differ from the natural calendar.
  • GET_CURR_EQTR_START / GET_CURR_EQTR_END — current equivalent quarter boundaries, used to align a comparison period to the present reporting cycle.
  • GET_CYCQ_PK_KEY / GET_CYCM_PK_KEY — resolve the surrogate primary keys for the current-year calendar quarter and current-year calendar month in the EDW time dimension, which downstream queries use as join keys.
  • FIS_CYCQ_START — returns the current-year calendar quarter start as used by the FIS (Financial Intelligence Suite) reporting layer.
The remaining documented signatures follow these same naming conventions and serve the same boundary/key-resolution purpose. No parameter lists are asserted here; callers should obtain exact signatures from the deployed source.

Tables Accessed

All table access is read-only and occurs through APPS synonyms referencing the Enterprise Data Warehouse time dimension:

  • EDW_TIME_M — the primary EDW time dimension, supplying day-, month-, and quarter-level attributes and the surrogate keys resolved by GET_CYCQ_PK_KEY and GET_CYCM_PK_KEY.
  • EDW_TIME_MONTH_LTC — a month-level local-time-calendar view or table used for monthly period boundaries and fiscal-month alignment.
  • EDW_TIME_EP_CAL_QTR_LTC — an enterprise-calendar quarter local-time-calendar structure used for quarter start/end and corresponding-quarter resolution.
No inserts, updates, or deletes are documented.

Usage Notes

FII_TIME_WH_API is a foundational dependency rather than an end-user entry point. It is referenced by 26 other database objects and does not itself reference or call other application APIs, so it sits near the bottom of the FII call hierarchy. It is typically invoked from FII reporting packages, concurrent programs that generate period-over-period financial extracts, and custom PL/SQL that needs a consistent EBS date boundary. Because the package is compiled as VALID in the APPS schema, developers should call it directly (for example, as APPS.FII_TIME_WH_API.ENT_CYCQ_START) rather than reimplementing calendar logic. The dependency on EDW time tables means its correctness depends on the EDW calendar being populated and current; if the time dimension is stale, returned boundaries and keys will be stale as well. Behavior is identical across Oracle EBS 12.1.1 and 12.2.2, as the object is unchanged by the 12.2 online patching architecture.