TEMSE cleanup trick

We once had a bad TemSe entry in table TST03. There was one entry that repeated itself literally hundereds of times.

Whenever we tried cleaning this up in normal SAP fashion (SPAD/SP12) the process would consume all of our database locks due to the bad entry. The normal SAP TemSe cleanup processes don't do commits like they should; thus, the large number of database locks (that have to rollback once the process fails -- aghh!).

Anyway, after looking an SAP notes 48400 and 11070, SAP sent us a "secret" abap that did the trick.

If you find yourself in this position ask your OSS rep to send you a copy of the top secret abap RSTS9803. This will prompt you for the bad entry number and will do commits while it removes it out of ALL the TemSe tables.

Watch the size of those table go down after running this tasty abap!

    Requires Free Membership to View

This was first published in February 2002

There are Comments. Add yours.

TIP: Want to include a code block in your comment? Use <pre> or <code> tags around the desired text. Ex: <code>insert code</code>

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
Sort by: OldestNewest

Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to:

Disclaimer: Our Tips Exchange is a forum for you to share technical advice and expertise with your peers and to learn from other enterprise IT professionals. TechTarget provides the infrastructure to facilitate this sharing of information. However, we cannot guarantee the accuracy or validity of the material submitted. You agree that your use of the Ask The Expert services and your reliance on any questions, answers, information or other materials received through this Web site is at your own risk.