Is RFC synch or asynch?

Hi
I want to know that if an RFC is synchronous or asynchronous processing?
Thank You

Hi subhash,
1. IT can be both,
 (depending upon how we call the RFC function
 in abap code)
2. If we call simply
CALL FUNCTION 'XYZ'
DESTINATION 'D'
(Then it is synchronous,
 it will wait, till the FM is completed)
3. BUT
 if we call in this way
CALL FUNCTION 'XYZ'
DESTINATION 'D'
 STARTING NEW TASK
then it will be asynchronous.
(it will get executed in a separate process,
independently)
and our program execution will continue forward.
regards,
amit m.

Similar Messages

BPM RFC synch send step

Hi
I am using RFC synch send step with in parforeach block in BPM. do I need to activate correlation to correlate synchronous request and synchronous response for RFC synch send step ?
Please let me know if you have any ideas on this.
Thanks
Anand

Hi Michal,
Thanks for the reply.
In SAP help I found the statement made below.
Activating a Correlation
An asynchronous or synchronous send step can activate correlations. This can be useful in the following cases:
· Synchronous send step
A synchronous send step waits for a reply message to be received. On receipt of this reply message,
correlations can be activated to correlate additional messages.**********************************Any idea on highlighted sentence...
Thanks
Anand

RFC synch/asynch

Hi,
RFCs are synchronous by default. So they use BE as QoS.
How to make them Asynchronous so that they will use EO QoS?
In Asynch case will the RFC response be persisted or only request to RFC will be persisted?
thanks in advance,
KP

Hi,
transactional RFC (tRFC) and queued RFC (qRFC) are both asynchronous. But the RFC Adapter only supports tRFC, which only uses an outbound buffer (it's not a queue) and matches the QoS EO. On the sending system you can use the transaction SM58 to monitor the outgoing messages. The messages are buffered in the adapter framework, if the target system is not available.
As said above, on SAP releases prior to 6.20, SAP IDOCs are the only way to use EOIO.
A tRFC is called by using the additional line 'in background task'.
In the SAP System, there is no different definition for synchronous and asynchronous RFCs. The asynchronous just only use the importing parameters.
Regards,
Christian

RFC-XI-FILE Asynch Scenario

Hi All,
i am working RfcXiFile Asynch. Scenario by using Proxy. i created ABAP proxy in R/3 system and exececuted in XI server. it's working fine. All design and Configuration in IR, ID over. i tested the configuration, it's fine. But the problem is file is not created in the receiver.
and no messages will be displayed in SXMB_Moni. Anybody came across this situation, Please let me know the solution asap.
Thanks & Regards,
Nagarjuna.

Hi Sarvesh,
What i have done exactly is:
After completeting the design part in IR, i created a proxy class in R/3 by using the SPROXY tcode. There, the following objects are generated, they are
Class ZSRCO_RFC_RESP_MI Proxy Class (Generated)
Structure ZSRRFC_RESP_DT1 Proxy Structure (Generated)
Structure ZSRRFC_RESP_MT1 Message type for RFC Response
then i create report in R/3 by using SE38,
there i called the function module and my internal table gets populated.
in the same report i created the object for my proxy class and called the proxy also.And i declared the data for proxy class & structure.
The same report i executed in XI server, the data is displayed.
but in SXMB_MONI, no messages are displayed.
i am sure that i configured receiver communication channel properly.
For this scenario, sender communication channel is not required, becuase instead of that we are using the Proxy right?
So, please try to under stand my scenario and get back to me with proper solution.
Thanks,
Nagarjuna.

Mixing Synch with Asynch

Need some validation here.
 The requirement is as follows :
 Receive an HTTP request (request for data) through a servlet in Weblogic
 6.1, forward the request as a JMS message via a bridge to MQ. Workflows in
 MQSI get the message and reach into the mainframe legacy system to scoop
 some data and send it back to Weblogic via a bridge. The only catch here is
 the trading partner needs a synchronous response (the data that came from
 the legacy system) which means the Servlet will have to wait for the data.
 Obviously I could have the Servlet create a temporary queue, stick the queue
 name in the JMSReplyTo header field and push it through the bridge. On the
 back-end I could have the MQ workflow replicate the ReplyTo string in the
 response message before pushing it back through the bridge. Finally, I
 could have the bridge publish back to the temporary queue so that the
 Servlet gets it and sends a response to the partner. The only issue here is
 , I am not comfortable with the notion of creating a temporary queue for
 every HTTP request that I receive. Is there an alternative to achieving
 this in a simpler manner ? The business requirement absolutely necessitates
 a synchronous response back to the trading partner. Unfortunately, since
 the data is sitting inside a legacy system we cannot interface in synch
 mode with the legacy data store. So essentially we want a synch front end
 with an asynch back end (not my favorite cocktail!).
 Any ideas and/or suggestions are welcome.
 Regards,
 Adarsh


 Adarsh Dattani wrote:
 > You are right. We have a web server that load balances the WLS instances.
 > So once a connection is created with a Servlet, there is no fail-over in the
 > picture.
 > However, this is getting a little tricky. Let's say I have a cluster with
 > two managed servers. The web-app is clustered and the web server routes an
 > http request to a Servlet in Managed Server A. How do I configure the
 > response destination ?
 One dest per server. Each with the same JNDI name. Set "JNDINameReplicated"
 to false on
 queue (6.1SP2 new setting). Client or MDB looks up jndi queue name, will
 always receive
 local javax.jms.Queue. Passes this in the "ReplyTo". Cluster OK, as
 "JNDINameReplicated" is false,
 destinations are not "visible" past their local server.
 > I can't have a distributed destination in WLS 6.1.
 > Do I create a response destination on both servers ? If so, what if the
 > response message lands up in Managed Server B ? Will the servlet
 > transparently connect to the destination in Managed Server B ? Or should I
 > forget about clustering and deploy both my web-app and JMS-Server to a
 > specific managed server ?
 > As far as using MDBs to cache the response, I am really debating on that
 > approach versus doing timed blocks against a response topic. I am gonna
 > have to hold a thread in either scenario. I am not clearly on any other
 > benefit one approach offers against the other.
 I'm not either.
 >
 > Adarsh
 >
 > "Tom Barnes" <[email protected]> wrote in message
 > news:[email protected]...
 > >
 > >
 > > Adarsh Dattani wrote:
 > >
 > > > Raja/Tom,
 > > > Thanks for the suggestions. I liked the caching approach. However, I
 > do
 > > > see a couple of minor issues there. First, I would need a cluster-aware
 > > > cache if I wanted to deploy my web-app to the cluster. I guess I could
 > > > simply target it to the managed server to start with as clustering is
 > not
 > > > imperative here.
 > >
 > > If web-app fail-over is not an issue (fail-over of a running servlet),
 > > You could create a "NonReplicated" destination. This allows the
 > > same destination JNDI name on several servers. A lookup of this name
 > only
 > > returns
 > > what is on the same local server as the running servlet, even if server is
 > > in a cluster. (This is a flag added in 6.1SP2 or something like that.)
 > >
 > > >
 > > > The second issue is slightly tricky. I will need a fail-safe cache if I
 > am
 > > > going to cache the message from my MDB.
 > >
 > > > Perhaps I could bring JDBC into the
 > > > picture to work-around that.
 > >
 > > Why do you need to persist the response message? Are you anticipating
 > having
 > > the running servlet
 > > fail-over capable? I'm not that familiar with servlets. Is this even
 > possible?
 > >
 > > Is making the response queue persistent enough? You could make the MDB
 > > transaction required, and actually have the MDB block until the servlet
 > > successfully
 > > completes and rollback if it doesn't.
 > >
 > >
 > > > Raja's suggestion on setting up filter based
 > > > durable subsribers chew off a topic is good too. But Raja, I am still
 > not
 > > > clear about how the durable subscriber would pass the response message
 > back
 > > > to the servlet ? Did you imply caching there ?
 > > > Thanks,
 > > > Adarsh
 > > >
 > > > "Adarsh Dattani" <[email protected]> wrote in message
 > > > news:[email protected]...
 > > > > Need some validation here.
 > > > > The requirement is as follows :
 > > > > Receive an HTTP request (request for data) through a servlet in
 > Weblogic
 > > > > 6.1, forward the request as a JMS message via a bridge to MQ.
 > Workflows in
 > > > > MQSI get the message and reach into the mainframe legacy system to
 > scoop
 > > > > some data and send it back to Weblogic via a bridge. The only catch
 > here
 > > > is
 > > > > the trading partner needs a synchronous response (the data that came
 > from
 > > > > the legacy system) which means the Servlet will have to wait for the
 > data.
 > > > > Obviously I could have the Servlet create a temporary queue, stick the
 > > > queue
 > > > > name in the JMSReplyTo header field and push it through the bridge. On
 > the
 > > > > back-end I could have the MQ workflow replicate the ReplyTo string in
 > the
 > > > > response message before pushing it back through the bridge. Finally,
 > I
 > > > > could have the bridge publish back to the temporary queue so that the
 > > > > Servlet gets it and sends a response to the partner. The only issue
 > here
 > > > is
 > > > > , I am not comfortable with the notion of creating a temporary queue
 > for
 > > > > every HTTP request that I receive. Is there an alternative to
 > achieving
 > > > > this in a simpler manner ? The business requirement absolutely
 > > > necessitates
 > > > > a synchronous response back to the trading partner. Unfortunately,
 > since
 > > > > the data is sitting inside a legacy system we cannot interface in
 > synch
 > > > > mode with the legacy data store. So essentially we want a synch front
 > end
 > > > > with an asynch back end (not my favorite cocktail!).
 > > > > Any ideas and/or suggestions are welcome.
 > > > > --
 > > > > Regards,
 > > > > Adarsh
 > > > >
 > > > >
 > >

JDBC to RFC synch RFC call not executing.

Hi,
I am working on the synchronous JDBC to RFC without BPM. After completing design and config when I test the complete scenario the data from databse is not getting updated in R/3. And I do not see any errors in MONI. But when compared the moni logs I observed the following between the working scenario and not working scenario.
Working scenario log in MONI:
<SAP:Receiver>
<SAP:Party agency="" scheme="" />
<SAP:Service>ECS300</SAP:Service>
<SAP:Interface namespace="http://sap.com/xi/XI/System">InterfaceCollection</SAP:Interface>
- <SAP:Mapping notRequired="S">
<SAP:ObjectId>YYgNVKC9PTCW4JlMapfxZQ==</SAP:ObjectId>
<SAP:SWCV>IrmTYNPLEdqKItGjlusuXw==</SAP:SWCV>
Not working log from the MONI:
++++++++++++++++++++++++
<SAP:Receiver>
<SAP:Party agency="" scheme="" />
<SAP:Service>ECS300</SAP:Service>
<SAP:Interface namespace="http://my_Own_namespace">JDBC_Rfc_Synch_MI</SAP:Interface>
- <SAP:Mapping notRequired="M">
<SAP:ObjectId>28ZZbGggOw6UcnigDXMD7A==</SAP:ObjectId>
<SAP:SWCV>IrmTYNPLEdqKItGjlusuXw==</SAP:SWCV>
<SAP:SP>-1</SAP:SP>
</SAP:Mapping>
Could some body point me where I am doing wrong ?
Thaks
Steve.

Hi Steve,
I think the error is because your database table is expecting some kind of input and the input you are passing has some error in it.Just cross check the table using DESCRIBE <tablename> with the data you are trying to enter.
Also Just look at Query SQL Statement part ubnder this link,
http://help.sap.com/saphelp_nw04/helpdata/en/7e/5df96381ec72468a00815dd80f8b63/content.htm
Regards,
abhy

BPM synchronous send step - Fault message extraction

Hello Experts,
I am developing a BPM with Asynch RFC -> synch Webservice -> Asynch RFC scenario.
I have defined fault message in the synchronous interface used in the send step for web service, and also defined
exception branch where an alert is thrown.
In the alert, i want to send the fault text from the fault message. How can i do that??
Thanks

Hi Mona,
SOAP adapter doesnt support fault messages.
check stephan's reply @ How catch the SOAP Fault Message ?
> SOAP adapter does not support fault message.
> Any fault is treated as error.
> fault messages are only supported for XI messages (ABAP or Java proxies) and RFCs.
Fault message handling is not possible inside BPM.

R3 (RFC Asynch) -- XI --- SOAP (webservice Synch)

Hi Experts,
 My scenario is :R3 (RFC Asynch) > XI <-> SOAP(webservice is synch)
Step1:- R3 sends the data webservie(SOAP) via XI.
Step2:- Webservice returns the response to XI, But R3(RFC) does not need the resoponse.
how to handle the webservice response in XI.
do i need to use BPM as this scenario is R3(RFC synch) > XI <--> Webservice(soap, synch). Can anybody help me out how to design this scenario.
Thanks,
Siva

So then all u need is to create a async inbound MI. Also the WS should be configured in a way that it sends a HTTP 200 with a SOAP envelope with an empty content for successful delivery.
Refer the below from the SOAP adapter FAQ;
Receiver Asynchronous Calls
Q: What are the correct receiver options for asynchronous calls?
 A: The processing mode of the receiver is determined by the message that reaches the receiver. If you are sending a message with some quality of service, to provide this service of quality to the server, your must make sure two things. First, your receiver channel must be configured to pass the XI message ID to the server. Second, your web service must check duplicates using this message ID.
Q: What should my web service return to the adapter for asynchronous calls?
 A: Currently, the receiver adapter expects an HTTP 200 with a SOAP envelope with an empty content for successful delivery. Any other response will result in a XI system error and triggers retries of the message. When you want to check duplicates, you should configure your receiver channel to pass the XI message header information to the server.
 Prior to SP11, a SOAP fault resulted in the application or system error, depending on whether the SOAP fault contained a detail child element or not. This behavior contradicted the communication model. Therefore, it has been changed so that the adapter generates the system error for any SOAP fault in asynchronous calls.
 When you want to check duplicates in your web service, you should configure your receiver channel to pass the XI message header information to the server. When your web service indeed find a duplicate, assuming that the previous message was simply lost, your web service should return an HTTP 200 with an empty SOAP envelope.

Synch RFC

Hello,
I am doing an interface - R3-XI-File. The R3 RFC is called synchronously. I am checking if the file is posted at the receiver side or not by using Transport ackin BPM. In exception handling, deadline handling - I am returning the response to R3.
These are the steps I did,
1. I have rfc dest of type TCP/IP - in R3 - used that program id and defined RFC sender adapter in XI. - checked if rfc dest works - works fine. I have used the same rfc desc for Asynch process which works fine.
2. I have called the RFC inside a fm like this
call function 'ZFM_RFC_SYNCH'
 destination 'XIRFC'
 tables
 FT_table1 = ITWA_table1
 FT_BAPIRET2 = FT_BAPIRET2.
3. I am getting the following error in the sxmb_moni
SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="BPE_ADAPTER">SYNCHONOUS_MESSAGE</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>This process does not support the specified synchronous interface or does not support any synchronous messages The exception occurred (program: SAPMHTTP, include , line: 0)</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
4. Audit log shows me this
Success RFC adapter received sRFC for 'ZFM_RFC_SYNCH' from R3/010. Attempting to send message synchronously
Success - Application attempting to send an XI message synchronously using connection AFW.
Success - Trying to put the message into the call queue.
Success - Message successfully put into the queue.
Success - The message was successfully retrieved from the call queue.
Success - The message status set to DLNG.
Error - Received XI System Error. ErrorCode: SYNCHONOUS_MESSAGE ErrorText: ErrorStack: This process does not support the specified synchronous interface or does not support any synchronous messages The exception occurred (program: SAPMHTTP, include , line: 0)
Error - Returning synchronous error notification to calling application: XIAdapter:SYNCHONOUS_MESSAGE:.
Error - Transmitting the message using connection http://host:port/sap/xi/engine?type=entry failed, due to: XIAdapter:SYNCHONOUS_MESSAGE:.
Error - The message status set to FAIL.
Anyone knows where the problem is exactly???
My BPM has receive step - opens SA bridge - then mapping to file message type - block with send step to file adapter - which has deadline and exception handling - for transport ack - and then send step to RFC resp - close SA bridge...
Anyhelp is greatly appreciated.
Thanks
Thilothama

I found what I missed. The BPM had a wrong interface in Config side. Previously I had async scenario and changed to sync..so didnt change to sync interface....Now its working.
I have one more question...For File transport ack - can we check the particular return message and do the processing?? instead of deadline and exception branches??
If the transport is successful, I see this message
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

<SAP:Manifest xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="wsuid-manifest-5CABE13F5C59AB7FE10000000A1551F7
If its negative, I get
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.MessagingException: Channel 'File_Receiver', Service 'File', Party '': File Adapter configuration not activated: com.sap.aii.af.ra.ms.api.RecoverableException: Channel 'File_Receiver', Service 'File', Party '': File Adapter configuration not activated</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
the reason is, for negative ack I use the exception brach and send the resp to R3 - saying the file was not processed. But if its success..I shold have another dummy mapping which should say successful....which I am not very much happy to do...is there any other way you can think of?? or worked on???
Thank you for all your great suggestions...

MessageExpiredException error in JDBC - RFC scenario using BPM.

Scenario: JDBC( Asynch)- RFC( Synch)- JDBC (Asyc)
We are using XI to read oracle table records to insert the records in R/3 and after the insert in R/3 we return a sap code to update in oracle db.
When we try to process 10 or less rows from db, the process is successfully running, but when we try processing more records we are getting the following error. We tried increase the timeout setting in RFC adapter as per the SAP note and forum.
Detailed error: 
com.sap.aii.af.ra.ms.api.MessageExpiredException: Message 443jdjsd-e432-2ec8-e100-000046eb2e5f(INBOUND) expired.
If I use correlation in asynchronous RFC instead of synchronous RFC, will this solve the problem or is there any better solution for this ?
Any useful steps to change the synchronous RFC to asynchronous RFC in BPM would be great.
Thanks
Steve

Hi,
1. Any suggestions to meet this requirement in XI ?
>>>One option is using ABAP Proxy . Instead of calling Sync. RFC, call synchronous Proxy. So your client proxy, should receive all 200-300 rows at a time, and inside the proxy, and call the RFC. Once all the reocrds are processed, send the response back to BPM
You can try out this.
I think, probably you may require to do looping for each Row.i.e For each row the call the RFC.. As of now try to go with Proxy.
Also try to findout, why the RFC is taking that much of time.. So check for the provision of tuning in the RFC side..
Hope this helps,
regards,
Moorthy
Message was edited by: Krishna Moorthy P

Doubt on FILE to RFC & PROXYS

Hi everybody,
 I'm able to solve most of my doubts by this forum, thankz to everybody who assisted me.Here are some simple doubts plz give solutions to them as many as possible
 1.In my FILE to RFC scenario I'm using BPM & i should send response back to SENDER so what steps should i include in it ? I'm using BAPI_GOODS_MVT_CREATE bapi?
 2.In my FILE to RFC scenario I'm maintaining single SLD for DEV,CONS,PROD ,so can i configure my file sender service directly in ID as a BUSSINESS SERVICE?
 3.Can any one give some information In which case we have to go for
PROXY & in which case for IDOC?exluding this reason " if syst config is >6.20 or else go for IDOC or RFC for an sap system?
 Plz kindly answer to this questions & valuable answers are rewarded.
 Regards,
 Vinod.

1.In my FILE to RFC scenario I'm using BPM & i should send response back to SENDER so what steps should i include in it ? I'm using BAPI_GOODS_MVT_CREATE bapi?
>>>
Ref: /people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit
Else in case you have SP19 then ref this abstract from an earlier post !!
All,
Just thought I'd add a quick note here.
From SP 19 on XI 3.0 and SP 10 on PI 7.0, a File - RFC - File ( Asynch - Synch ) scenario can be done without a BPM.
Steps:
Integration Repository
The Integration Repository will be similar to any Synchronous Scenario ( say HTTP - RFC ) . 1 Outbound Synch message Interface and 1 Inbound Synch Message Interface.
Integration Directory
This is where a few differences lie, so let me take some time.
1. The Receiver Determination , Interface Determination will be the same as in HTTP - RFC synch scenario. Create the Sender File Adapter, Receiver RFC Adapter and Receiver File Adapter.
2. Sender Agreement will be for the Sender File Adapter. Sender Agreement uses the Synch Outbound Message Interface.
3. Receiver Agreement will be for the Receiver RFC adapter. Receievr Agreement will use the RFC as thge Inbound Message Interface.
4. We need to add a few modules in the Sender File Adapter.
Go to the Modules Tab of the Sender File Adater, and add the following modules in the same sequence,
Number - ModuleName - Type - ModuleKey
1- AF_Modules/RequestResponseBean - Local Enterprise Bean - 1
2- CallSapAdapter-Local Enterprise Bean - 2
3-AF_Modules/ResponseOnewayBean-3
Parameters
ModuleKey - ParameterName - ParameterValue
1 - passThrough - true
3-receiverChannel - Receiver File Adapter Name
3-receiverService - Receiver Business Service/ System
With this configuration, you can now handle the requirement without a BPM
This feature been already blogged for JMS Adapters in these blogs ,
Sync/Async communication in JMS adapter without BPM (SP19)
Async/Sync Communication using JMS adapter without BPM (SP 19)
Dynamic Configuration is also possible,and this as well as many other options are discussed in the How To guide - "How To Realize a sync-async and async-sync
bridge within the Adapter Framework" available on the Service Market Place.

In my FILE to RFC scenario I'm maintaining single SLD for DEV,CONS,PROD ,so can i configure my file sender service directly in ID as a BUSSINESS SERVICE?
>>
you can use Business service !!!
3.Can any one give some information In which case we have to go for
PROXY & in which case for IDOC?exluding this reason " if syst config is >6.20 or else go for IDOC or RFC for an sap system?
>>>
Advantage of Proxy over RFC, IDOC
/people/ravikumar.allampallam/blog/2005/08/14/choose-the-right-adapter-to-integrate-with-sap-systems

QoS - EOIO in RFC and http/SOAP adapters

Hi all,
I need to have the QoS as EOIO in my interface where I am using RFC Sender adapter and HTTP/SOAP receiver adapter and using BPM Integration process.
I have seen in the adapter attributes that these 2 adapters support the EOIO. I don't know how to specify this service in the adapters.
Is there any special way of specifying this?
Any help in this regard is highly appreciated.
My interface is async and we are at SP 14.
Thanks
Kalyan

Hi Kalyana,
Check these..
2 scenarios with 1 Rfc-queue does it work ??
RFC synch/asynch
Queues for RFC-Destination
cheers,
Prashanth
P.S Please mark helpful answers

Step by step File to RFC Scenario with BPM

hi
for the following scenario i m following the webblog
/people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit
i have successfully created the design phase
in the configuration stage
i need to create a business system or business service will do to create the communication channel
i have not created the systems so i feel i should not create the business systems
i would like to create the business service
so in only one business service can i assign all the communication channel
useful answers will be rewarded
Regards
JM

There are 3 parts of communication: Sender service to Integration Process (Asynch.), Integration Process to RFC (Synch.), Integration Process to Receiver Service (Asynch.)
The configurations should be like as follows:
Sender Service to IP
Receiver determination:
Sender Service->Request Outbound Message Interface->Integration Processs.
Interface Determination:
Sender Service->request Outbound Message Interface->Integration Process->Request Outbound Abstract Interface. (No interface Mapping is required as the interfaces share the same structure.)
Sender Agreement:
Sender Service->request Outbound Message Interface->Integration Process->Request Outbound Abstract Interface>FileRFC_Send
IP to RFC
Receiver determination:
Integration Process->Request Outbound Abstract Interface->Business service.
Interface Determination:
Integration Process->Request Outbound Abstract Interface->Business service->RFC Structure->Corresponding Interface Mapping between file structure and RFC structure.
Receiver Agreement:
Integration Process->Request Outbound Abstract Interface->Business service->RFC_Receiver
IP to Receiver Service:
Receiver determination:
Integration Process->Response Inbound Abstract Interface->Business service.
Interface Determination:
Integration Process->Response Inbound Abstract Interface->Business service->Response Inbound Message Interface. (No interface Mapping is required as the interfaces share the same structure)
Receiver Agreement:
Integration Process->Response Inbound Abstract Interface->Business service->FileRFC_Receive.
Hope you find this useful.
Regards,
Amitabha

How many routes shoud i create for synch senario ?

Hello expert!
When i try to create a synch senario with receiver rfc ( file ---> rfc ), how many communication channle i need? shoud i creat a back route for the message get from rfc ?
if i need to create a rfc sender cc to trnsfer the exporting value get from the rfc to send back to the file dir?
i'm really confused about the synch senario, any help is appreciated !
thanks !!
BR,
ShengJun

Could not get the link...
From SP 19 on XI 3.0 and SP 10 on PI 7.0, a File - RFC - File ( Asynch - Synch ) scenario can be done without a BPM.
Steps:
Integration Repository
The Integration Repository will be similar to any Synchronous Scenario ( say HTTP - RFC ) . 1 Outbound Synch message Interface and 1 Inbound Synch Message Interface.
Integration Directory
This is where a few differences lie, so let me take some time.
1. The Receiver Determination , Interface Determination will be the same as in HTTP - RFC synch scenario. Create the Sender File Adapter, Receiver RFC Adapter and Receiver File Adapter.
2. Sender Agreement will be for the Sender File Adapter. Sender Agreement uses the Synch Outbound Message Interface.
3. Receiver Agreement will be for the Receiver RFC adapter. Receievr Agreement will use the RFC as thge Inbound Message Interface.
4. We need to add a few modules in the Sender File Adapter.
Go to the Modules Tab of the Sender File Adater, and add the following modules in the same sequence,
Number - ModuleName - Type - ModuleKey
1- AF_Modules/RequestResponseBean - Local Enterprise Bean - 1
2- CallSapAdapter-Local Enterprise Bean - 2
3-AF_Modules/ResponseOnewayBean-3
Parameters
ModuleKey - ParameterName - ParameterValue
1 - passThrough - true
3-receiverChannel - Receiver File Adapter Name
3-receiverService - Receiver Business Service/ System
This is from one of the posts the Bhavesh has posted some time back.
VJ

BPM: RFC (SYNC) - BPM- HTTP client

All XI Experts
My scenario is RFC synchonous to XI (BPM) to HTTP Client.
I correctly configured all my messages interfaces and mapping programs.
I have defined the following:-
Sync Abstract message interface for the RFC structure
Async Abstract MI for RFC sent data
Async Abstrcat MI for the RFC response data.
At this stage I have NOT set up the full scenario. My BPM consists of the following steps:
Receive- Opens an Sync/Async brige
Send - Closes the S/A brigde
I have also set up all the sender agreements and RFC destinations, so there is no issues with that side of things.
When I execute the RFC (se37) and stipulate the RFC Destination, the message is logged in XI but has the following error:
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code Area="BPE_ADAPTER">SYNCHONOUS_MESSAGE</SAP:Code>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>This process does not support the specified synchronous interface or does not support any synchronous messages The exception occurred (program: SAPMHTTP, include , line: 0)</SAP:Stack>
Has anyone come across this issue?
Interestingly, when I execute the RFC in the background, then XI processes it fine?
Is this how XI works? Is RFC Sync communication with BMP not supported?
Any help would be greatly appreciated.
Yackeen

Hi Yackeen,
Have you resolved this problem? I have working on the similar design. Need your input on this one.
My scenario is RFC>bpm>HTTP (asynch)
I have one Receive and one send step with one block, deadline branch and a control step in dead line branch.
Thanks
Kalyan

Is RFC synch or asynch?

Similar Messages

Maybe you are looking for