BPM synchronous RFC calls

I have two messages, one coming from SOAP and second one from JDBC adapter. I want to map this two messages to Single BAPI call. How do I go about doing this using BPM.

SSG,
1. You will have a fork with 2 branches with 2 receiver steps. One for the SOAP request and the other the JDBC sender adapter.
<a href="http://help.sap.com/saphelp_nw04/helpdata/en/24/e2283f2bbad036e10000000a114084/content.htm">Step Type - FORK</a>
<a href="http://help.sap.com/saphelp_nw04/helpdata/en/cb/15163ff8519a06e10000000a114084/content.htm">Multiple Start Process Receiver Steps</a>
2. Transformation Step -- N:1 mapping where the 2 source messages are mapped to the Single BAPI message.
3. Send Synchronous Step -- You will be sending the BAPI request message and getting the Response message.
You can use the <a href="/people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit - File to RFC">File - RFC - File</a> blog as a template to see how synchronous RFC calls are made and then , you can get the RFC response and do the needful as per requirements.
Regards,
Bhavesh

Similar Messages

How to Use synchronous RFC calls during test run for remote accesses

there is a Setting for the usage of RFC accesses from a tested system
using eCATT.
'X' - Use asynchronous RFC calls during test run for remote accesses
' ' - Use synchronous RFC calls during test run for remote accesses
I developed an eCATT as following :
SAPGUI ( SAPGUI_1 , Target_system_1 ).
SAPGUI ( SAPGUI_2 , Target_system_2 ).
My question is how to run the eCATT in a synchronous RFC calls
PS: I do not want to change the Target_system to the same one in the
above script of ecatt.Because I need to run it in 2 different Target
systems sometime.
for example, I give a Target_system_3 when run this eCATT
I want the SAPGUI_1 and SAPGUI_2 run the Target_system_3 but not the
Target_system_1 or Target_system_2 .
Could you please tell me how to make it without the changes in script?
Edited by: Weitong Liu on Mar 24, 2011 9:44 AM

Hi Liu,
Weitong Liu wrote:
> ' ' - Use synchronous RFC calls during test run for remote accesses
This is the standard option value. Asynchronous are not the standard way and used only for very special purposes.
Weitong Liu wrote:
> I developed an eCATT as following :
> SAPGUI ( SAPGUI_1 , Target_system_1 ).
> SAPGUI ( SAPGUI_2 , Target_system_2 ).
> My question is how to run the eCATT in a synchronous RFC calls
The commands will be executed in sequence. So each call will be synchronously replayed against TS1 and TS2.
What is you issue with this standard procedure?
Kind regards,
Christoph

"No Receiver Determined" in BPM Sync RFC Call

My scenario is xml file -> XI BPM -> RFC1 -> RFC2 (will call RFC2 if RFC1 is successful).
I am still just trying to get the RFC1 call working properly. I have been using blogs 1822, 1403 and 1926. I have also used some related BPM threads. It seems to be making the RFC call properly, but failing on the response.
<SAP:Code area="RCVR_DETERMINATION">NO_RECEIVER_CASE_BE
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>No receiver could be determined</SAP:Stack>
These docs show my IB Repository and Directory setups. Can anyone look at them and tell me what is missing? Thanks in advance!
http://webpages.charter.net/kpwendel2/bsmDir.jpg
http://webpages.charter.net/kpwendel2/bsmRep.jpg

Keith,
the problem is quite clear.
In your BPM, you have a synchronous interface in your sync send step.
However, in configuration, you have configured two asynchronous interfaces.
To be able to use sync send step in BPM, your RFC needs to be able to send a response back. Then you need to have two message mappings (one for bpm->rfc messages, and other for rfc_response -> bpm_response messages) and a interface mapping between the 2 sync interfaces (bpm_sync_int -> rfc_sync_int) using these 2 message mappings.
Also, some hints:
1. Don't do these mappings in BPM transformation step. You can execute them outside of BPM. Doing this, you will get better performance and also won't need to create abstract interfaces for RFC messages.
2. Use configuration wizard in Integration Directory (first, remove and reimport your BPM in Integration Directory). This way, you avoid different interfaces errors.
Regards,
Henrique.

How to loop through single XML File and send multiple RFC calls?

I am looking for the best approach to use for making multiple RFC calls (can be sequential) using a single XML file of data. I have been attempting to get a BPM loop working, but to no avail. My RFC only accepts a single set of delivery input and I have been told to try to work with it as is.
input xml sample:
<?xml version="1.0" encoding="UTF-8"?>
<ProofOfDelivery>
   <POD>
      <delivery_number>1</delivery_number>
      <carrier_name>UPS</carrier_name>
   </POD>
   <POD>
      <delivery_number>2</delivery_number>
      <carrier_name>UPS</carrier_name>
   </POD>
</ProofOfDelivery>
I need to make a synchronous RFC call for each set of POD data.
Thanks in advance!

Thanks for the inputs.
I tried with a BPM and multi-mapping transformation before a ForEach block. I am getting this error:
Work item 000000028028: Object FLOWITEM method EXECUTE cannot be executed
Error during result processing of work item 000000028029
com/sap/xi/tf/_ProofOfDeliveryMultiMapping_com.sap.aii.utilxi.misc.api.BaseRuntimeExceptionRuntim
Error: Exception CX_MERGE_SPLIT occurred (program: CL_MERGE_SPLIT_SERVICE========CP, include: CL_
Probably because I am not making/using the container objects properly. Here is a screenshot of my BPM. Can anyone spot my issue or point me to an example on this sort of container use?
[http://kdwendel.brinkster.net/images/bpm.jpg|http://kdwendel.brinkster.net/images/bpm.jpg]
Thanks

Synch. RFC call error - No Sender Found

Hi,
once execute the synchronous RFC call from BPM, rfc response message returns as following;
<SAP:Code area="RCVR_DETERMINATION">MESSAGE_INCOMPLETE</SAP:Code>
<SAP:Stack>Message is incomplete. No Sender found</SAP:Stack>
i've tried adding header mappings at receiver aggreement for bpm's name as sender service and target sap system name as receiver service. Same error.
Any help is greatly appreciated. Thanks

Hi,
>>>>i've tried adding header mappings at receiver aggreement for bpm's name as sender service and target sap system name as receiver service. Same error.
no need for any header mapping in that case
just configure the routing correctly - via directory wizard
and everything will work
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

Performance in a sync-rfc -- xi -- rfc-call

hi,
we are designing an web application where several systems are involved. A portal application (webdynpro) calls via jco in a sap system (sysA). sysA is connected to other sap systems (FI, HR, ...).
My question: Is it advisable to put the XI between sysA and the other backend systems for synchronous calls? sysA calls through rfc in the other systems. Don't I have performance problems?
Example scenario: A user puts some data in the portal application and he clicks on the save-button. Now the data are passed to sysA (JCO), then a synchronous rfc-call, over the XI, stores them in the backend-systems and returns a return-message. The return-message is then displayed to the user (webfrontend).
We have to decide wheter to use the XI or not, and havn't the time to make a performance analysis. For this I hope in your help!
Regards,
Thomas

Hi Thomas,
no, i dont expect significant performance damage. Of coz requesting application has to wait 4 answer, but it has wait anyway 4 sap response, the XI part of processing time will be less than 10% (my experience).
I would see
advantage XI: better monitoring, better error handling, central repository and so on. The usual XI advantages.
handicap XI: You have a working system. If you are pleasured - why invest money?
Regards,
Udo

XI Scenario synchronous RFC (ABAP program) over XI to C program Receiver

Hi experts,
I have a synchronous RFC-Call between an SAP System (Sender) and an C-programm (Receiver). But now XI should become a part of this scenario.
Regarding this I have a few problems to include XI.
1. SENDER:
I have an abap application which calls a function module and send the data over synchronous RFC to XI.
e. g. call function 'FM_XYZ' DESTINATION 'RFC_SENDER'
        exporting PARAMETERS
        importing PARAMETERS
        changing TABLES.
Whis this part I have had no problems. But I have problems on my receiver side.
2. RECEIVER:
As receiver I have a server, where only a C-program starts a process and register the RFC Program on server side. The program is now waiting for requests. How can be called this C-Program on XI side.
So could anybody help me. Thank you.
Regards
Mario

Hi Ravi,
thanks for your fast reply.
In our current RFC Szenario (without XI)
1. In SAP side we have configured a TCP/IP connection
2. On C program side we start the C-program as follows:
We start a File which contains the name of c-program.exe RFC-Program-ID gateway. Then the RFC destination is registered on external Server side.
By using the Testing connection feature on SAP RFC (SM59) the RFC-connection works fine.
3. But now this scenario should be displaced by the XI scenario. Is it possible to use on receiver side a RFC-ADAPTER which calls an external RFC server.
Regards
Mario
Message was edited by:
        Mario Bauer

RFC call From BPM

Hi,
I have a scenario where I need to access a Function Module from BPM for certain business validations. My FM is in XI and I need to invoke that FM from BPM. How can we do that ? I am trying an RFC call but it gives me an error "No identifier defined for the system".
Pl advise, where am I wrong OR if there is a better way to do that.
Thanks,
Sid

This doesn't look like an issue for BPM. Please check whether the connection is working fine by testing a call to the RFC in a simple scenario(file to RFC or whatever).
In BPM all you need to do is a synchronous send step with abstract message type defined for both request and response structures of the FM . And in ID a receiver determination+channel and all for this step.
Best of luck...

Synchronous SOAP call from XI without BPM....

Hi All,
Is it possible to use the (File - XI - SOAP) Synchronous SOAP call from XI with out BPM. to trace the error messages. If yes then how it can be achived in XI.
Thanks,
Jane

Hi,
You will get either a system error/application error raised if there is a problem processing the SOAP request without the need for BPM.
You can then raise an alert from the RWB if this occurs.
If all is OK with processing, you will get the standard chequered flag.
Cheers
Colin.

Trigger an RFC call to ECC from PI using BPM

HEllo Experts,
This is my first time in ccBPM and require your expertise in gaining some insights onto calling an RFC FM using ccBPM.
I am typically implementing the scenario as it is mentioned in this blog: /people/mitesh.parekh/blog/2008/12/01/receiving-aleaud-as-acknowledgment-in-ccbpm in order to generate acknowledgements from ECC.
I have created the IR and ID and I am successfully able to exceute the BPM till step2. Step 3 is the ABAP mapping part for which i have specified teh required properties and Operation mapping too.
My concern is that how do i proceed from Step 4 i,e how do i trigger this RFC call to ECC and receive it in BPM again?
Thanks in advance,
Elizabeth.

I am developing a scenario which looks like this MDM ->PI ( BPM) -> ECC.
Now the Integration process that I am developing is with reference to blog http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/12249. [original link is broken] [original link is broken] [original link is broken]
I am posting MATMAS from MDM which is received in first step(receive step) of this BPM.
2nd step (Send step - BPM) will send this MATMAS05 Idoc to ECC and Pi will have a message id generated for this message.
3rd step of BPM (ABAP mapping) - which will read the actual PI Idoc number from system tables based on the message id from step 2.
4th step: Idoc number retrieved is to be sent in the requset message of RFC ZALEAUD4XI.
5th step: Response of ZALEAUD4XI RFC is to be received in PI and sent for further processing.
Do i need a mapping between the requset output of ABAP mapping and the input RFC requset message of step4?
Thanks,
Elizabeth

Sync RFC call from BPM - message expired

Hi guys,
I have a scenario with BPM where I'm doing a sync RFC call to ECC and then I want to process the result. However, the processing of BAPI take approx 5 minutes and my messages get expired after 3 minutes.
How to resolve this issue?
Thanks a lot,
Olian

Hello,
Problem might be at BAPI end. Please check BAPI by executing with your set of inputs. If BAPI goes for exception for yoru set of input values.. you may not get response from R3. So you might have error..
secondly.. Please post the error in the communication channel and errro in the SXMB_Moni as well.
Thanks,
subbu

Problem with RFC-Call within BPM

Hello Experts,
I am developing a scenario in which I call an rfc-function-module for saving information from an incoming xml which will be transmitted as Idoc to another SAP System.
The Idoc transmission is doing properly. But the RFC-Call I try to do always ends with a red flag. Error-Message: message has error status on outbd. side at the Process-Engine.
Can someone help solving that problem?
Thanks in advance.
Regards, Alexander

Hi Rajhans,
1) The user mentioned in the RFC communication channel is having the authorization.
Yes, he have the authorizations.
2) Go to Communication channel monitoring and check what error you are getting for the communication channel is showing.
There is an error about the FileSenderChannel. Error: java.lang.NullPointerException.
3) Check whether the RFC created at abap stack is remote enabled or not.
The function module is remote enabled.

It is possible to get a response of a asynchronous RFC call thru wait loop

Hi Experts,
The requirement is that i queue up all the requests from a web services ( One queue per plant for example) which i set in the HTTP sender URL ( i mean the queue name ). and i am posting the records thru a RFC call.
1. Let the RFC call be synchronous and in case the R/3 system is done.. Will the XI queue keep the Call and keep on retrying it till the R/3 system is up.
2. Otherwise if the RFC call be asynchronous, is it possible to introduce a wait loop in BPM to listen to the RFC till i get some response ( i think this is not possible).
Need your suggestion on the same...
The requirement demands that no single request from the web service should be lost.. in case of failure of R/3 they should be queued up and re tried.. Forget about the error because of exception in RFC this will be taken care manually..
Thanks for your response in advance.

Hi Rajesh,
you can queue and restart only asynchronous messages. I think you can build a Business Process, where you repeat sending a message til you have success or maximum number of tries is reached. But no good idea, coz you will get timeout at HTTP sender. Aynchronous messages dont have a response.
May be, XI can solve your task in the standard: In transaction SMQR you can just configure what you describe. All asynchronous messages will be queued and restartet in case of receiver not reachable. You can configure no of retries and intervall between.
Regards,
Udo

RFC calls with SAP table insert - lock tables

Hi,
I have an external server program, which is calling a rfc function many times the same time with different transaction types. There are transaction types, which are downloading information from SAP (only send data back to the caller), and there are transaction types which are uploading data to SAP (inserting/updating data on SAP).
The function calls are synchronous as the server needs to get feedback directly. The parallel work processes for RFC calls are limited, so a system overload can´t happen.
The problem now is, if the server is down for while and going to be restarted, it´s opening parallel threads and calls the function in SAP at nearly the same time. That means, it will call the function with upload requests (table must be locked), and download requests the same time.
In the upload requests, the table has to be locked, that it can´t occur that we get wrong entries...
I can only enqueue the table with just two fields... I know, that is almost like locking the whole table, but it´s not possible to lock it in a different way.
I tried to use the enqueue function with the parameter WAIT, but it didn´t help, as there where too many parallel calls and after some seconds, they were ending up with an error (Because the table has been locked by another call).
It seems that it´s trying to lock the table again for all parallel calls at exactly the same time....
The calls has to be synchronous, as the server needs to get the feedback directly. Any ideas how top solve this, that it handles all incoming calls parallel and waits for the table is unlocked again?
Thank you for your help!

Hi,
thank you for your answer!
I have investigated something new yesterday:
I thought at the beginning, that the problem just occurs, when the system work processes are reached. The system has for example set up 15 dialog processes and the external server is calling the function 20 times in parallel. Then we normally need 5 dialog processes more. The system is taking then all 15 dialog processes and the locks got stucked.
That means, that I´ll maybe only get 4 or 5 uploads, which have really been updated the tables. All the others couldn´t get the table locked for their process.
But if I now let the server call the function just about 13 times in parallel, nearly all uploads have been updated the table!
From my point of view, the lock from SAP gets stucked, when the limit of dialog processes is reached. It´s not working in the right way anymore...
The same is happening, when you set up in the system, that only 10 work proecesses can be used by RFC. If I have more than 10, it´s going to be critical with the locks....
WEIRD!
Can anybody help me out of trouble?
Thank you!

XI RFC call failing

Hello,
   I am setting up a very simple scenario where I am making a sychronous RFC call to a BAPI in R/3 (Version 4.6c) from an XI Sandbox (Version 7.0).
   I have the RFC Communication channel properly configured, or so I think, and have verified everything else as well. I initiate the message from the Runtime Workbench and it shows with status "Successful" in the Message Monitoring section. However, when I look in SXMB_MONI transaction I am unable to find a response message from the BAPI coming back in the payload. I notice that even though the scenario is synchronous, the "Type" column in the SXMB_MONI transaction results shows it as "Asynchronous". Also, in the message details there is a Payload (which I am sending when I create and send the message from the RWB), in every step, until the Call Adapter step. After that there is no payload in the Call Adapter or the Response steps, just the SOAP Body with the Manifest.
   In the message details I see that the <SAP:Processing Mode> entry is set to "Asynchronous" rather than "Synchronous".
   Does anyone have any idea why this is so?
Thanks,
Murtaza.
Message was edited by:
        Murtaza Madraswala

Hi Amitabha,
   I looked in the location you suggested and got a list of "Success" messages. These are listed below for you to look at:
Time Stamp Status Description
2007-06-18 15:17:54 Success Message successfully received by messaging system. Profile: XI URL: http://camapox1:50100/MessagingSystem/receive/AFW/XI Credential (User): XIISUSER
2007-06-18 15:17:54 Success Using connection RFC_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.
2007-06-18 15:17:54 Success Message successfully put into the queue.
2007-06-18 15:17:54 Success The message was successfully retrieved from the receive queue.
2007-06-18 15:17:54 Success The message status set to DLNG.
2007-06-18 15:17:54 Success Delivering to channel: GeneratedReceiverChannel_RFC
2007-06-18 15:17:54 Success MP: entering
2007-06-18 15:17:54 Success MP: processing local module localejbs/RfcAFBean
2007-06-18 15:17:54 Success RFC adapter received an asynchronous message. Attempting to send tRFC for Z_SD_RFC_ATP_WRAPPER with TID XIlc32S1tf4Togkm0mRWaHRG
2007-06-18 15:17:55 Success MP: leaving
2007-06-18 15:17:55 Success The message was successfully delivered to the application using connection RFC_http://sap.com/xi/XI/System.
2007-06-18 15:17:55 Success The message status set to DLVD.
   The problem that I am seeing is that this is posted under the list of Asychronous Received Messages. Thats something I am just unable to understand. I have a Synchronous Outbound Interface defined and an RFC Communication Channel, which is Synchronous as far as I know. So why is the processing mode for the message being chosen as Asynch? Which config setting have I missed that is causing this problem? I am just unable to find the answer so far.
   I appreciate your help. Please let me know if you have any clues.
Thanks,
Murtaza.

BPM synchronous RFC calls

Similar Messages

Maybe you are looking for