"simulating" return table elsewhere than in Update

Question: Hi guys, I find this one tricky but perhaps would you find it easy.

I have a standard extractor for master data. The master data contains a status that can vary in the time. The extractor is only able to provide me the last(current) status. In BW I need the history of statuses.

I put the status as time dependent in master date of BW, and by loading each day the current status, I can trace the changes from now on. But I miss the history of statuses (I mean, the changes occured in the past).

I found a table in the source system where the history of statuses is stored, so I am thinking about using this history to recreate the history in BW.

IF I was on version 3, I would use the flexible update possibilities and would
1) load the history (record key, date from, status) separately in an ODS
2) create a return table, adding as many entries to the master data as there are entries in the ODS for the given record

BUT, as I am on version 2, I don't know how I could do it ?

I was thinking about creating additional entries in the C_T_DATA (or call it E_T_DATA if you like) at user-exit time, but I am not sure wether this is the best possible solution.

Your thoughts would be read with great attention.

Ch

Answer:
Something to try.
As this will be a once off process, Use the ODS to build the data as it is suposed to look. dump it to flat file and do a flat file upload for your history data on the object.

Answer:
Was a nice idea, but as I am better at abap than at xls merging, I did it in the user-exit.
Problem being that if I load two different status and period for the same record without having an activation of master data between, it fail with error about overlapping.
But solved by loading one status at a time with activation between, so seems to be ok now.
Thx
Copyright ?2007 - 2008 www.jt77.com