No idea of the specific BIApps your talking about as you're not specifying any version, source system or the likes. How to Ask Questions in Developer Community Spaces
In general when a record has no start date and is initiate inserted into an SCD2 you can put 01/01/0001 as a start date so that any date range joins will pick it up as valid.
As of the next insert you will update it with an end date as usual and deactivate that row.
Sorry for not being through.
BI Apps 188.8.131.52.1; source Oracle E-Business Suite 11.5.10.
Right now when the START_DATE_ACTIVE is null we seed it with a low date a you noted. However as columns change that are flagged as SCD2 both START_DATE_ACTIVE and END_DATE_ACTIVE are null on the source side. Then it simply does and update to the row instead of creating a new row.
Appreciate you feedback.
That's again a different scenario than what you described above. I guess this case wasn't forseen when the data flow was designed or this situation shouldn't arrive in the source data(?) to begin with.
- raise an SR and ask Oracle for clarification
- change things in ODI yourself to ensure proper behaviour