topic Is it Advisable to use wait in program ? in Application Development and Automation Discussions

Is it Advisable to use wait in program ?

Former Member — Wed, 01 Nov 2006 21:35:06 GMT

Is is advisable to use 'wait' in programs ? I need to do a select on a table , that i just wrote ....If i dont do a wait in the program , the select returns blank...!!

Does this make a major performance setback in a program ?

clear bkpf.

clear bkpf2.

wait up to 2 seconds.

select single * from bkpf into bkpf where

belnr = belnr1 and bukrs = messtab-msgv2 .

if sy-subrc = 0.

if dist >= 2.

select single * from bkpf into bkpf2 where

bvorg = bkpf-bvorg and belnr <> belnr1 and gjahr = bkpf-gjahr.

if sy-subrc = 0.

write 😕 Cross Company doc num: ' , bkpf-bvorg color 5.

write 😕 'Posted In Company Code : ' , bkpf-bukrs color 5.

uline.

Re: Is it Advisable to use wait in program ?

Former Member — Wed, 01 Nov 2006 21:42:54 GMT

Hi,

I don't think wait up to 2 seconds will cause major performance while waiting messtab-msgv2 value.

Is this inside loop statement?

Regards,

Ferry Lianto

Re: Is it Advisable to use wait in program ?

vyende — Wed, 01 Nov 2006 22:06:17 GMT

It is really your discretion. Are you trying to read a record that has "just" been added to the database? If so, the record may still be in the buffer (and not physically in the database) and the wait is justbuying you time. The problem is this may not work all the time (depending on the load and system timings). I would opt for Commit and Wait before Wait.

Re: Is it Advisable to use wait in program ?

Former Member — Wed, 01 Nov 2006 23:14:53 GMT

There are other better ways than WAIT.

Rob