cancel
Showing results for 
Search instead for 
Did you mean: 

Processing type

Former Member
0 Kudos

Hi everyone,

I'm a little confused about the new functionality processing type in JRA and JCO action block. What does asynchronous processing and synchronous processing mean? Under what circumstances should they be used?

Thank you!

BR,

Elena

Accepted Solutions (1)

Accepted Solutions (1)

jcgood25
Active Contributor
0 Kudos
Former Member
0 Kudos

Hi Jeremy,

I know about the help document, but I have some difficulty in understanding it. It says "The BAPI/RFC is always executed in the background. The transaction continues without waiting for a response." about Asynchronous Processing.

Does it mean the transaction will keep trying to call the BAPI until it receives a successful response, and it will stop trying after certain attempts?

And there is another field mentioned: RFC Type. I don't quite understand it. I thought the RFC type is set in the ECC system, why do we need a RFC type in the JCO action block. If we try to call a BAPI in ECC with RFC type sRFC, but the connection in ECC is set up as tRFC, would the call fail? Or if it succeeds, which RFC type it is using during the BAPI call?

Thanks.

BR,

Elena

abesh
Contributor
0 Kudos

Hello Elena,

The basic difference between Synchronous and Asynchronous modes is the way both are executed.

In the synchronous mode the system waits for a response back from the request, just like when executing lines of code in a computer program where each line of code is executed one after the other, the program waits for the previous line to finish executing and return results, if any, before moving on to the next line.

In case of the asynchronous mode, it sort of resorts to the fire and forget mechanism. The line of code is executed and the program moves on to the following lines without waiting for the previous line to finish executing.

If the asynchronous call is expected to return any data, it is commonly implemented using a callback mechanism. A function/method is specified during the asynchronous call which will automatically be invoked later when the asynchronous call returns and passes on the data returned, if any, to the callback function/method as a parameter.

Answers (0)