In addition, in RSA3 you can check the box Debug Mode, execute the extractor and it will stop at predefined points.
As for the endless loop, there are still times when this is very helpful. For example, logistics applications put entries in the logistics queue (or BW delta queue if configured for direct update) when the transactions are saved. Debugging the extractor doesn't do you much good in that case. Even running setup and debugging that doesn't always help since setup works differently than live transactions. For that the endless loop technique is very helpful. When the user clicks save the update function is usually called asynchronously in the update task. You can't debug that the normal way, and even using update debugging is difficult because you have to wade through whatever other functions were called before the one you're interested in. So if you can, put a piece of code like the below where you want to debug, save a document, then in SM50 debug your process. I usually make sure the loop exits after 30 seconds rather than being endless just to be safe.
DATA: l_exit TYPE abap_bool.
DO 30 TIMES.
IF l_exit = abap_true. EXIT. ENDIF.
CALL FUNCTION 'RZL_SLEEP'.
ENDDO.
If you have the SAP_BW component installed in the source system (common with ECC) then you can also leverage function RSSM_SLEEP_DEBUG instead to make it even more dynamic.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.