Hello,
based on your username I assume you are going more in the archiving direction.
From an archiving point of view several things need to be considered regarding TST03:
- TST03 is the "payload" table of TemSe objects. This means that TST03 is connected to other tables too, so simply archiving TST03 would not be enough.
- Since TemSe objects are stored here, several different kind of objects can be stored here: Spools, Batch Job input data, etc.
- It would be barely useful to archive all of these objects of TST03. For example: the KONS TemSe object is only used for consistency reasons by report RSPO1043. It would be hardly useful "later".
So first please see SAP Note #48400 - "Reorganization of TemSe and spool" for details about TemSe.
After that please plan with Business exactly what kind of TemSe objects are required: since not the entire TST03 should be archived, the business scenarios need to be rechecked for actual objects to be archived.
Best regards,
Laszlo