Search Results ent_sd_lyr_beg

Overview

FII_TIME_API is a public PL/SQL API owned by the APPS schema within the Oracle E-Business Suite Financial Intelligence (FII) family of products, which underpins Enterprise Performance Management and financial reporting calendars. The package is declared with AUTHID CURRENT_USER and exposes a set of date-manipulation functions that resolve today's date, or any caller-supplied "as of" date, against the enterprise calendar and the standard accounting calendar. Its central purpose is to translate a given date into the equivalent date in a prior or future calendar period, quarter, or year, so that comparative (year-over-year) reporting can be driven consistently across all FII reporting components.

The header comment shows the source was last revised in 2003, and the ETRM repository nevertheless documents it as current for 12.1.1 and 12.2.2, confirming it has remained stable and is still the canonical calendar-arithmetic utility used by the FII stack. The package caches the global start and end dates of the enterprise calendar after initial access, avoiding repeated lookups against the calendar tables. It is heavily reused: the ETRM metadata records 74 dependent packages that reference it, making it one of the more widely consumed calendar utilities in the Financial Intelligence schema.

Key Procedures and Functions

The documented interface contains 51 functions. The most prominent groups are:

• GLOBAL_START_DATE / GLOBAL_END_DATE — return the start and end date of the enterprise calendar, establishing the boundary within which all other calculations operate.
• ENT_SD_LYR_BEG / ENT_SD_LYR_END — return the same day in the previous enterprise year, counted respectively from the year start date and the year end date.
• ENT_SD_LYSQTR_BEG / ENT_SD_LYSQTR_END — the same day in the same quarter of the previous enterprise year.
• ENT_SD_PQTR_BEG / ENT_SD_PQTR_END — the same day in the prior enterprise quarter (immediately preceding period, not prior-year-aligned).
• ENT_SD_LYSPER_BEG / ENT_SD_LYSPER_END — the same day in the same enterprise period of the previous year. ENT_SD_LYSPER_END is the function most relevant to the user's search term.
• ENT_SD_PPER_BEG / ENT_SD_PPER_END — the same day in the immediately preceding enterprise period.
• SD_LYSWK / SD_PWK — the same day in the previous-year week and the prior week respectively.
• ENT_CYR_START / ENT_CYR_END and ENT_PYR_START / ENT_PYR_END — the start and end dates of the current and prior enterprise years.
• ENT_CQTR_START / ENT_CQTR_END — the start and end dates of the current enterprise quarter.

All functions follow a consistent naming convention: "ENT_SD_" denotes an enterprise-calendar same-day mapping, "LYR" preceding year, "LYSQTR" preceding year's quarter, "LYSPER" preceding year's period, "PYR" prior year, and "CYR" current year. Each raises an exception if the underlying SQL fails.

Tables Accessed

The package reads exclusively from FII calendar and time-dimension tables through APPS synonyms, and does not write to any table other than by way of the caching mechanism. The year, quarter, and period hierarchies are sourced from FII_TIME_CAL_YEAR, FII_TIME_CAL_QTR, and FII_TIME_CAL_PERIOD for the standard calendar, and from FII_TIME_ENT_YEAR, FII_TIME_ENT_QTR, and FII_TIME_ENT_PERIOD for the enterprise calendar. Day-level and week-level resolution is provided by FII_TIME_DAY and FII_TIME_WEEK, while FII_TIME_P445 supports the 4-4-5 retail-style period model. DUAL provides simple date arithmetic. These tables collectively define the enterprise calendar boundaries referenced by the API's functions.

Usage Notes

FII_TIME_API is a server-side utility invoked from PL/SQL rather than directly from an Oracle Forms UI. Because it is documented as an API and is referenced by 74 other packages, it is typically called by FII reporting engines, concurrent programs generating period-over-period comparisons, and custom code that needs to derive a prior-year or prior-period date without hard-coding calendar logic. The cached global start and end dates mean the first call in a session pays the lookup cost, and subsequent calls are served from cache. Customizations should always call these functions rather than querying the FII_TIME tables directly, so that results remain consistent with shipped reporting behavior across 12.1.1 and 12.2.2. No parameter lists should be assumed beyond those shown in the package specification; the search term "ent_sd_lysper_end" corresponds to the documented ENT_SD_LYSPER_END function returning the same day in the same enterprise period of the prior year.