Date Effectivity allows an object's attributes to change over time while retaining records of historical values. For example, the following figure displays the promotion history for an employee named Kath Nash:
Notice that Kath's Employee ID, which is constrained to be unique across employees, remains static over time, while Kath's Job and Grade change over time. The effective date ranges do not overlap and are gapless. Therefore, only one row can be fetched from the object for any given date.
See the Oracle Fusion applications documentation for more information about date effectivity and which business objects support date effectivity.
In general, Transactional Business Intelligence analysis is based on the most current information as contained in the transaction database. For date effectivity enabled dimensions and facts, analysis can be done based on current date or as of a particular date in the past or future. Transactional Business Intelligence logical objects are modeled as date-effective entities when the dimension or fact is sourced from Oracle Fusion applications transaction objects that support date effectivity.
By default, all Transactional Business Intelligence requests fetch data based on the current date. No special setup or configuration is needed to do analysis based on the current date’s data. Advanced users of Transactional Business Intelligence can submit Transactional Business Intelligence requests as of a particular date in the past or in the future. See How to Create As-of Date Analysis.