Skip to Content

Scenario – data transfer from system ‘B’ to system ‘A’ on request of system ‘A’

Steps:

1. System A makes a remote function call to ‘B’ using synchronous RFC function

2. an asynchronous RFC function call from ‘B’ to ‘A’ using destination ‘BACK’ with a small size of data written back to ‘A’, continuing data collection in ‘B’

Example:

CALL FUNCTION ‘ZRFC_A_TO_B’

      DESTINATION ‘B’.

Pseudo code for ZRFC_A_TO_B

  from table IM_ITAB.

Advantages:

1.     BACK refers to the calling FM the same path as the called

2.     The process need not be required to start from the beginning in case of communication failure during the runtime, as database commit occurs at each Remote function call

3.     The processing time to write the data back to receiver system can be reduced

This blog attempts to take the idea presented in the blog on  Parallel Processing – An Introduction one step further. Typically in case of any mass-processing activity (posting IDocs, for example), It is possible to leverage the processing power of multiple application servers. Since the processing of each record is usually independent of the processing of another, we can trigger multiple jobs on various application servers, each of the jobs processing only a part of the total records.

To report this post you need to login first.

3 Comments

You must be Logged on to comment or reply to a post.

    1. Hello Sravya,
      Sorry for the delayed response.

      Here are a couple of pointers which I hope resolve your question –
      1.Comments (by none other than Horst Keller) to the weblog on Parallel Processing.
      2.F1 Documentation in the ABAP Workbench for the CALL FUNCTION…STARTING NEW TASK addition.

      I had made a mention about it here to just hint at the possibilities for achieving increased throughput for critical but time consuming programs.

      Regards,
      Kinshuk.

      (0) 

Leave a Reply