topic Re: why tRFC is stated as asynchronous processing type in Application Development and Automation Discussions

why tRFC is stated as asynchronous processing type

Former Member — Fri, 15 Dec 2006 12:20:04 GMT

why tRFC is stated as asynchronous processing type?

Re: why tRFC is stated as asynchronous processing type

sourabhshah — Fri, 15 Dec 2006 13:23:38 GMT

hi,

While with synchronous and asynchronous RFC each call makes a single logical unit of work (LUW) in the remote system,you can group several RFCs into one LUW for transactional RFCs.

you can use the addition IN BACKGROUND TASK which you must specify before the DESTINATION entry.if you write a COMMIT WORK statement all the previous RFCs are bundled into one LUW and transmitted through tRFC

Thus it is asynchronous

Regards,

Sourabh

Re: why tRFC is stated as asynchronous processing type

Former Member — Fri, 15 Dec 2006 13:42:04 GMT

Hi max,

1. The concept and architecture of rTFC

is such that,

even if the other server is DOWN, at the time of making the call,

the r/3 system will ensure,

that wehenver the other system is UP,

it will connect and do the rfc call.

2. This processing happens INDEPENDENTLY

of the calling program.

The callling program, can CONTINUE after the tRFC call is made.

It NEED NOT WAIT, after calling the FM.

Hence, it is asynchrous.

regards,

amit m.