‎2013 Jul 03 11:20 AM
Hi!
does anyone have any suggestions /experience about archiving with object BC_E071K.
How many years should stay in the database?
What is the best practice?
In which periods have you organized the archiving with BC_E071K?
Are there any preconditions?
thanks for your input
Florian
‎2013 Jul 03 11:39 AM
Hi Florian,
E071K looks like the table of details about transport request.
There is no rules about that, just requirement of your functionnal team
did you try to check witch kind of data use the most of space ? (trans. TAANA)
maybe developpers didn't care about that
Regards
Fred
‎2013 Jul 03 11:39 AM
Hi Florian,
E071K looks like the table of details about transport request.
There is no rules about that, just requirement of your functionnal team
did you try to check witch kind of data use the most of space ? (trans. TAANA)
maybe developpers didn't care about that
Regards
Fred
‎2013 Jul 03 11:51 AM
Hi Frederic,
well at the moment we have more than 12.000.000 records in table E071K.
One result is that transaction SNOTE is really slow.
I am not sure until which date I can archive E071K.
How many years/ monthes should I have E071K records in my database?
thanks and regards
florian
‎2013 Jul 03 12:25 PM
It really depends of your functionnal teams
for me one year is enough
I used E071K to find, who have modify a customizing key (after a bug)
Have a look to the trans. TAANA to analyse what kind of data you have in E071K (on the OBJECT)
(that will made a GROUP BY .. COUNT ..)
regards
Fred