Dear Basis Team,
The table JEST (as well as JCDS JSTO,...) belongs to the status management area. The mentioned tables contain information of objects and their assigned status - like for example for production orders, WBS, elements,...
Unfortunately tables JCDS, JEST, JSTO,... cannot be archived directly, there is no archiving object for it. That is because, as mentioned, the status information in tables JSTO and JEST is only a logical appendix of various master data objects like internal orders, production orders, WBS elements and many others. To reduce the data on table JEST etc., it is necessary to find out what leading objects they belong to and then archive them using the respective leading archiving object.
To get an overview of how data in JEST (and hence JSTO and JCDS as subsequent tables) is distributed across the objects I would recommend to use transaction TAANA with the table analysis for table JSTO because only table JSTO has a field OBTYP which describes what object the record refers to (object type can be decoded using transaction BS13 or table TJ03). So an analysis for table JSTO , field OBTYP would be a good start to see where data archiving could help to reduce the size of status related data base tables like JCDS.
By archiving these leading objects, the status management tables as JCDS should get archived too.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.