Long runtime for ASSERT if checkpoint group is active

[] [] [] []

Symptom

Within a procedure unit, if you execute the statement
ASSERT ID CONDITION .
repeatedly and the checkpoint group is active and the condition is fulfilled, the runtime of the statement increases continuously.

Reason and Prerequisites

The ASSERT statement can be nested. This occurs if a functional method is called within the condition and this method also contains an ASSERT statement.
To ensure that nested ASSERTs can be handled corrections, you must save the name of the checkpoint group and follow-on actions if the assertion is violated (for example, logging) in a stack.
Due to a program error in the SAP kernel, if several ASSERT statements occur one after the other, the system creates entries in the FORM stack; this is unnecessary. As a result, the FORM stack may increase dramatically and this causes the runtime of the statement to increase.

Solution

The kernel patch eliminates this problem.
See the “SP Patch Level” section for information about the patch level that is valid for your release.

[Slashdot] [Digg] [Reddit] [del.icio.us] [Facebook] [Technorati] [Google] [StumbleUpon]

Leave a Comment