SAP TemSe consistency check is to check wether entries in the TemSe data store are consistent. The TemSe consistency checks the header entry in table TST01 (TemSe objects) and object associated with the header entry; it can be stored in the file system or in the database table TST03 (TemSe data of the object).
You can determine TemSe inconsistencies in dialog and delete them using the appropriate pushbuttons in transaction SP12. You can also use report RSTS0020 to determine inconsistencies in the background and delete them in dialog with report RSTS0030.
TemSe Consistency Check via Transaction SP12
1. Execute transaction SP12. Go to TemSe Data Storage > Consistency check. This will take a while.
TemSe Consistency Check via report RSTS0020/RSTS0030
1. Execute transaction SE38. Run report RSTS0020 in the background. The result is a list of inconsistencies.
2. Execute the report at least once more after an interval of around 30 minutes. You must determine the exact interval based on the length of the running jobs.
3. Compare the results. It is possible that there is an entry in the first run that is marked as inconsistent, but no longer appears in the second run. This is a temporary inconsistency.
Note:
Temporary inconsistencies are not actual inconsistencies and must not be deleted. Temporary inconsistencies may occur, for example, if a user is writing data to the TemSe during the consistency check. A check must be performed more than once to ensure that the inconsistency is not merely temporary.Inconsistencies that appear in multiple logs are actual inconsistencies and should be deleted. However, you cannot delete TemSe inconsistencies in the background.
4. To perform the deletion, start report RSTS0030 in dialog for the subareas of TemSe, in which the consistency check found inconsistent objects.
5. Select TST01 and TST03 for the check.
6. As soon as the report has generated the object list, you can delete either all or the selected inconsistencies. You can only specify the names generically using place holders and not as an area with a lower and an upper limit.
