7.9.6.1 Financial Analytics - JDE - Extract Dates question

Question

Hi all,
Implementation of 7.9.6.1 Financial Analytics + Procurement and Spend Analytics
OLTP: JDE E9
OLAP DB: Oracle 11g
We were trying to adjust the # of prune days for an incremental load, when we discovered the change was having no effect.
Our situation - JDE*
Looking at the parameters in DAC, we found that the incremental condition in the SDEs is:
date >= *$$LAST_EXTRACT_JDEDATE*
In DAC, this parameter expands to:
TO_NUMBER(TO_CHAR(TO_DATE('@DAC_$$TGT_REFRESH_DATE'), 'DDD'))+(TO_NUMBER(TO_CHAR(TO_DATE('@DAC_$$TGT_REFRESH_DATE'), 'YYYY')) -1900) * 1000
If one keeps digging,
+$$TGT_REFRESH_DATE = @DAC_TARGET_REFRESH_TIMESTAMP in custom format, MM/DD/YYYY+
Compared to EBS*
Now, if I look at the *$$LAST_EXTRACT_DATE* parameter (used in EBS SDEs)
It expands to:
+@DAC_SOURCE_PRUNE_REFRESH_TIMESTAMP in custom format, MM/DD/YYYY+
Conclusion and question*
Obviously the Julian date conversion is required in $$LAST_EXTRACT_JDEDATE, but apparently the prune days are being considered in $$LAST_EXTRACT_DATE and not in $$LAST_EXTRACT_JDEDATE.
An obvious fix is to use @DAC_SOURCE_PRUNE_REFRESH_TIMESTAMP in $$LAST_EXTRACT_JDEDATE, but I don't know if that would have any side effects. I'll test it.
I'll raise a SR with Oracle, but wanted to check if you guys had seen this before.
Thanks, regards.-
Alex.-
Edited by: Alejandro Rosales on Feb 22, 2011 5:57 PM

Answer 1

Hi Alejandro,
Maybe this has been updated/correct in 7.9.6.2. Later today I will be in the office and can check in a VM image.
I'll update the thread as soon as soon as I have checked this out.
Regards,
Marco Siliakus