Entities are marked Date Effective by setting the Effective Date property to True in the Oracle ADF Model layer, which automatically adds the SysEffectiveDate transient variable to the Entity. Examples of effective dated dimensions in HCM are Worker, Job, Position, Department, Location. This entity should already have Effective Start Date and Effective End Date attributes as a part of its composite primary key. The Composite view object API uses these hints to identify an entity as a Date-Effective entity and understands that it must be handled specially. A Date-Effective clause as shown below is automatically added, provided that no other hints are supplied or present for it to be handled in some other way:
WHERE SYSDATE BETWEEN <DateEffective_Entity>.EFFECTIVE_START_DATE AND <DateEffective_Entity>.EFFECTIVE_END_DATE
This feature does not call for any change in the Oracle BI repository. All the configurations mentioned should be done in the Oracle ADF Model layer.