SAP Timing & Harm to Code Flow

[Donnovan]

Hi,

I have experience automating a IBM terminal, and the father of all problems on it was the random time the terminal takes to respond to some comands. Since i dont know how much time IBM terminal will take to do the task, i dont know how much time the script needs to wait until send the next task.

This was solved looking at the staturbar and getting from it the terminal state, if it is "thinking/processing" or if it is ready for the next commands.

Now with SAP, i believe to have the same problem because there is no info on status bar to tell me if its processing something or ready to new imputs.

Anyone have presenced any timing problems in SAP automation? Or it seens to respond in a realtime behavior causing no harm to the code flow?

I'm using COM access to SAP, using a group of functions found on this forum.

Thanks.

[water]

Did you have a look at the SAP UDF which can be found

[Donnovan]

This UDF is what i mencioned here "I'm using COM access to SAP, using a group of functions found on this forum". Thanks for the link.

I also use IE UDF that comes with Autoit, it have a function called "_IELoadWait" that prevent you from sending commands while IE is loading.

I see no "LoadingWait" function on the SAP UDF, so i believe we will need to deal with that on the code we wrote or, may be, its not necessary for SAP UDF.

There is no need for a "_SAPLoadWait" function on SAP UDF?

Edited September 19, 2011 by Donnovan

[water]

Unfortunately I have used the SAP UDF for a very small test script only.

I suspect that waiting for the "load" is done by the functions. The examples provided have the Sleep statements included so users can see what is going on.