For testing purposes I need my ABAP program to wait for few seconds. How can this be done?
4 Answers
2 solutions:
1) Either use WAIT UP TO ... SECONDS.
WAIT UP TO 42 SECONDS.
WAIT UP TO '0.5' SECONDS. " decimals are possible since ABAP 7.40 SP 8
- Does a roll-out and releases the work process to the listener
- Does an implicit Database commit
Use it when CPU processes are at a premium and when the implicit commit will not corrupt your data or cause a short dump because of an open database cursor.
2) Or use the function module ENQUE_SLEEP
:
CALL FUNCTION 'ENQUE_SLEEP'
EXPORTING
seconds = 42.
- Does not release the work process
- Does not cause an implicit Database commit
Use it when you cannot afford an implicit commit, and the system can handle the work process(es) being tied up for the duration of the SLEEP command.

- 11,934
- 5
- 22
- 48

- 3,677
- 8
- 35
- 57
-
2So simple. And I couldn't find it on this thing called internet. Thanks! – Igal Serban Dec 29 '08 at 06:18
ABAP WAIT UP TO SAP Documentation
WAIT statement has an implicit COMMIT which is something that should be avoided.
-
I don't think that it should be down voted. There are cases were it is the desired effect. And many that it does not matter ( which is my case). Thanks for the addition. – Igal Serban Jan 06 '09 at 21:56
Do you really need it to pause? You could trace through it by entering /h into the transaction field before you execute the program or by setting a breakpoint in the code.

- 4,286
- 5
- 36
- 45
the best way is use wait up: WAIT UP TO x SECONDS. where x is amount of seconds.
if you use an API or, a bapi, you could use it until you get response

- 5
- 2