Question:
Hi, I have been loading a time-dependant attribute for some time using the current date as the from date and 12/31/9999 as the to date. I found out that this is wrong and should be 01/01/1000 to 12/31/9999. Will I have any problems? Has anyone run into this situation?
08/01/2003
01/01/1000 07/30/2003
08/01/2003 12/31/9999
08/02/2003
01/01/1000 07/30/2003
08/01/2003 08/01/2003
08/02/2003 12/31/9999
08/03/2003
01/01/1000 07/30/2003
08/01/2003 08/01/2003
08/02/2003 08/02/2003
08/03/2003 12/31/9999
08/04/2003
01/01/1000 12/31/9999 ??????????
Answer:
what you did is correct;
by default, the validity is from 01/01/1000 till 31/12/9999;
but then if you want to track the changes, you have to put the from date at today, sothat the record is split in
previous value 01/01/1000 today
new value today 31/12/9999
if you use 01/01/1000 as from date, then you would receive
new value 01/01/1000 31/12/9999
and you loose track of the previous value and the changes
if you do it, it's no longer necessary to have it time dependent...
Ch
_________________
_
There are only 10 types of people in the world :
those who understand binary and those who don't.
Answer:
Using the current date is going to blow up your masterdata tables significantly as you are creating a new record each day, dont you have a change date coming through on your datasource that you can rather use?
Answer:
good point avanie, I was assuming you were loading DELTA's
Ch
_________________
_
There are only 10 types of people in the world :
those who understand binary and those who don't.
Answer:
OK, I was on the right track. Thanks for the confirmation. As far as the large number of time-dependant records this is not an issue. We do not have a change date available from our datasource!
When you do a Master Data Reorg in Process Chains it compresses these time-dependant records for you. If you need to do it outside of a process chain the only way to do it is to use the Function Module RSDMD_REORG_P_Q_T_TABLE. Not sure if this exists in 2.1 though.
Thanks again...