Warning: Undefined variable $saptab in /customers/9/5/e/s4hd.com/httpd.www/sap/abap-statements/index.php on line 47
Warning: file_get_contents(/customers/9/5/e/s4hd.com/httpd.www/global/php/adxcode.txt): Failed to open stream: No such file or directory in /customers/9/5/e/s4hd.com/httpd.www/global/php/helpers.php on line 89
Get Example source ABAP code based on a different SAP table
Warning: Undefined variable $prev in /customers/9/5/e/s4hd.com/httpd.www/sap/abap-statements/index.php on line 63
ID WAIT-UPTO • WAIT UP TO ABAP Statement • SECONDS WAIT UP TO
WAIT UP TO> Short Reference >
ABAP_SYNTAX WAIT UP TO sec SECONDS.>
What does it do? This statement interrupts the execution of the program by the number of seconds specified in sec>. sec> is a numeric expression position> of the operand type f> to which positive numbers can be passed, including 0. The unit of the number specified in sec> is seconds and the time resolution is one millisecond. After the specified time has passed, the program execution continues with the statement following WAIT>. When used, this statement always changes the work process>. Return Codes> This statement always sets sy-subrc> to 0.
Latest notes:
Each time this variant of the statement WAIT> is used, a database commit> is triggered (except during updates>). For this reason, WAIT> must not be used between AB-SQL > statements that open or close a database cursor>.
The variants WAIT FOR ASYNCHRONOUS TASKS> >, WAIT FOR MESSAGING CHANNELS>>, and WAIT FOR PUSH CHANNELS>> of this statement are useful only in combination with callback routines in aRFC>, AMC>, or APC>. The variant shown here does not wait for callback routines. ABAP_HINT_END
Example ABAP Coding
The output of the following example should correspond to approximately one million microseconds. ABEXA 00763 ABAP_EXAMPLE_END