Is there any way to maintain TST03 table.

[Former Member]

Hi

We are using report RSPO1043 for controlling the growth of  TST03 table with the following criteria

Delete old write locks --checked

only list inconsistencies--Unchecked

Delete after runs --06

Can we consider to implement RSPO1041  also ? There is no standard archiving object for this? Can we do custom archiving for TST03?

Thank You

[Laszlo_B · Accepted solution]

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

[Former Member · Accepted solution]

Hi Laszlo

Thank You for reply. SAP note really helps in understanding.

If  report RSPO1043  is only for inconsistency check then how it is deleting all the entries from TST03 table even if we have not implemented report RSPO1041.

I will do more analysis on this in my system. Thanks again,

btw I have changed the name

Regards

[Laszlo_B · Accepted solution]

Hello Deepak,

nice to see your name

Report RSPO1043 is only responsible for the spool-related TemSe objects. (Also, it uses the KONS TemSe object to keep track of the spool objects-to-be-deleted.)

This means that RSPO1043 should not be responsible for deleting all TST03 contents. This issue sounds like several other TemSe-housekeeping reports are running, and their result can be seen as deleted TST03 entries.

So I would say that other (automatically) scheduled batch jobs are processing in the background.

If your database contains a program / script which records which TST03 entry has been deleted by which program, then it could show further information what are exactly deleting the TST03 records.

Best regards,

Laszlo

[Former Member · Accepted solution]

Thank You Laszlo

It really helps in my further investigation.

[former_member190120]

Hello,

I am not sure why you would want to create a custom archive object for this table?  Here is information from the SAP Data Management Guide for maintain table TST03:

Report RSPO1043 enables continuous monitoring of inconsistent spool objects (example: no entries in TST01 but entries in TST03 for a selected spool are available). Just as in RSPO0043, the write locks are analyzed and, if necessary, deleted. In contrast to report RSPO0043, report RSPO1043 can run parallel to the other activities in the background. To do this, the report must run daily. See also SAP Notes:    98065 (SAP_APPL 40A - 604): Spool consistency check with RSPO1043 as of 4.0A    1748033 (SAP_BASIS 46C – 740): RSPO1043 does not delete all inconsistencies Important recommendation: Please ensure that report RSPO1043 is replacing the former report RSPO0043. Please makes sure that you reschedule your jobs with the new report name.

Hope this helps. Best Regards, Karin Tillotson

[Former Member]

Hi Karin

Thank You for replying. I referred Data management guide 6.9 before posting here.

We have already implemented report RSPO1043 which runs everyday and deletes data older than 7 days.

I checked in TAANA and it is working fine and we have only latest entries (7 days).

But those 7 days entries are huge. So I just wanted to understand if we should implement RSPO1041  also. May be that can help.