Skip to Content

how to reprocess an interface with a RFC problem


I have a simple scenario File->RFC->FILE

In the BPM that i use, i send some data vía RFC to a R3 Backend and retrieve it. FInally, i create a file with the result.

The send step that sends the data to R3 backend has been defined with a transport confirmation.

My problem is that the BPM has send the info to R3, has received the ACK and at this time, the R3 has crashed.

Now R3 is back again and the Receive Step of the BPM is waiting for the answer. I've checked Sm58 in R3 Backend but no entries in it.

How can i send once more the RFC now that R3 is ready?



Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

3 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Sep 21, 2006 at 02:34 PM

    Hi Inigo,

    design a exception branch for system errors.

    In this branch design a wait step for a special time you have to decide.

    After that wait step make a new send step (maybe in a loop )

    Regards Mario

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Sep 21, 2006 at 02:42 PM


    What is the RFC all about? Is it just fetching some data and giving you back or it is updtaing something in R3.



    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Sep 21, 2006 at 02:50 PM


    RFC is of synch type. no need of Send step with Transport Acknowledgement.

    So send the RFC req with Synchronous mode and map the file input into RFC request outside the BPM and get the response back into File.

    Have a look into this blog-




    Add a comment
    10|10000 characters needed characters exceeded

    • If so it is like of 2 scenarios. You need to have 2 receiver determinations

      1) Sender File to RFC in R/3

      2) R/3 to File

      But if you want to execute these 2 separate scenarios in sequence then the current design should have these BPM steps

      1) Receive File data

      2) Transofrmation step ( InputFile to RFC1)

      3) Send the RFC data

      4) Receive the RFC2 data

      5) Transformation Step (RFC2 to OutputFile)

      6) Send this to file

      You can avoid transformation steps inside the BPM. for this you need to do mapping outside the BPM



Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.