Asynchronous RFC adapter

how to use RFC adapter asynchronous way.......jena

Hi Jena,
Go Through this blogs..
Hope useful to you..
/people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit
/people/swaroopa.vishwanath/blog/2006/12/28/send-rfc-to-sap-xi-150-asynchronous
Reward Points If it is useful
Thanks,
Satya
Edited by: SATYA KUMAR AKKARABOYANA on Apr 3, 2008 5:44 PM

Similar Messages

Error in RFC adapter

Hello All,
I am working on File to RFC Asynchronous Scenario. I am getting Error in M receiver RFC adapter. It is displaying in Adapter Monitoring as
- Error: 2007-10-03 05:28:38 EDT: Message processed for interface BAPI_CUSTOMER_CREATEFROMDATA1: com.sap.aii.af.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: functiontemplate from repository was
Can any help how to resolve this.
Regards

Hi,
The RfcAdapter trys to find a Sender Agreement for this RFC call but the lookup failes. The values used for this lookup are:
 Sender Party/Sender Service: The values from Party and Service belonging to the sender channel.
 Sender Interface: The name of the RFC function module.
 Sender Namespace: The fix RFC namespace urn:sap-com:document:sap:rfc:functions
 Receiver Party/Receiver Service: These fields are empty. This will match the wildcard '*'.
Chilla

Error with Asynchronous RFC call to JDBC

Hi all,
We are working on a scenarion where in we have to make an asynchronous RFC call to JDBC.
We have configured RFC sender adapter following this weblog
/people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step
We have created data types only for the database as RFC does not require any data types.
And also we have created message types,message interfaces accordingly.
In Message Mappping,we mapped the export parameters of RFC to the access fields of database message type.
Also we have created sender agreement,interface determinations etc.... accordingly
And for sending RFC request asynchronously we followed this weblog
/people/swaroopa.vishwanath/blog/2006/12/28/send-rfc-to-sap-xi-150-asynchronous
Once done with all the above steps we could able to trigger the RFC call and caught with the following errors in SXMB_MONI and no errors are seen in communication monitoring
SOAP Error:
+<?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="">
<SAP:Category>Application</SAP:Category>
<SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
<SAP:P1>com/sap/xi/tf/_curr_exg_mm2_</SAP:P1>
<SAP:P2>com.sap.aii.utilxi.misc.api.BaseRuntimeException</SAP:P2>
<SAP:P3>RuntimeException in Message-Mapping transformatio~</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" /> <SAP:Stack>com.sap.aii.utilxi.misc.api.BaseRuntimeException thrown during application mapping com/sap/xi/tf/_curr_exg_mm2_: RuntimeException in Message-Mapping transformatio~</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Also trace shows the following error thogh the interface determinations are properly configured
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="T">--start sender interface action determination</Trace>
<Trace level="1" type="T">select interface BAPI_EXCHRATE_GETCURRENTRATES*</Trace>
<Trace level="1" type="T">select interface namespace urn:sap-com:document:sap:rfc:functions</Trace>
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">--start receiver interface action determination</Trace>
<Trace level="1" type="T">Loop 0000000001</Trace>
<Trace level="1" type="T">select interface *</Trace>
<Trace level="1" type="T">select interface namespace</Trace>
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">--no sender or receiver interface definition found</Trace>
<Trace level="1" type="T">Hence set action to DEL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- 
<Trace level="1" type="T">----</Trace>
<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
the above errors are shown as part of request mapping..
Can any one please let me know what other configurations do we need to do?
I did not map the RFC import parameters,do we need to do that
Any help in this regard is really appreciated
Rgds,
Santhosh

Hi,
I am really happy to hear that the problem with mapping is resolved.
Now as per your requirment It needs to be aynschornous RFC--> XI ---> JDBC call. In XI you should map the RFC Export parameters to the traget structure of JDBC.
then the question is to how to trigger the RFC Function Module in R/3 to XI.
Plesae follow below steps to trigger it from SAP R/3
1. Create a RFC in the R/3 system
2. Configure the SM59 and Sender Communication channle as given in the Michal's blog. Also test if it is succesful.
/people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step
3. Import the RFC in XI
4. Do the mapping to the target strucutre
5. Configure the JDBC receiver adapter
/people/sameer.shadab/blog/2005/10/24/connecting-to-ms-access-using-receiver-jdbc-adapter-without-dsn
6. You can trigger the RFC from R/3 sytem by using
Async Call - in ABAP program use below syntax to call RFC. Here the export parameters will be passed on to XI which further have mapped to JDBC.
CALL Function "RFC Name" IN BACKGROUND TASK destination <sm59 destination>
COMMIT WORK.
Sync Call
CALL Function "RFC Name" destination <sm59 destination>
Thanks
Swarup
Edited by: Swarup Sawant on Jan 27, 2008 9:14 AM

Sender RFC Adapter - Data to be sent from R/3

I am working on a scenario where I have to send data from an RFC-enabled function module from R/3 to a file server via XI. The entire scenario is asynchronous.
Sender: RFC Adapter
Receiver: File Adapter
I have done all design and the configuration. Both communication channels are working. I have the RFC destination also set up correctly in R/3.
However, when I run my ABAP program where the RFC-enabled function module is called, I get a shortdump with the message "senderAgreement not found: lookup of binding via CPA-cache failed for".
Plus: " The error occurred during an RFC call to another system."
Could someone kidly help?

Hi,
Follow these steps :
1. import the ECC_ Server into ID if not done
2. Refresh Cache : Tcode SXI_CACHE
3. Please check for Sender agreement config
4. Check out the parameters when R/3 calls back XI, it passes the SYS-ID and client number and checks the same in the Integration Configuration Under Business System Service-> Adapter Specific Identifiers. The R/3 System ID and the client Number
Also check out these blogs..
/people/shabarish.vijayakumar/blog/2008/01/08/troubleshooting--rfc-and-soap-scenarios-updated-on-20042009
/people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step
/people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step
regards
Aashish Sinha
PS : Reward points if helpful

File to JDBC Using RFC Adapter.

Hi All,
I've been trying to find out a scenario which is like a File-to-Database where RFC is the sender and JDBC is at Receiver end.
Kindly guide me in:
1) What are the steps I need to do when I use a RFC Adapter to pick a file from FTP?
2) Are the steps same for the JDBC Adapter as we do normally in a JDBC Receiver Adapter?
3) Is there any other configuration required for this type of scenario?
4) If I import the RFC only I wanted to know how would the file be picked from FTP Server? Is it likewhile create a RFC we import the File from FTP server.
My Plan of Action to do the scenario is:
1) Import the RFC from R/3.
2) Create the data types for target.
3) Map them both.
4) Use JDBC Adapter on the Receiver end.
These are the steps which I think should be done, if there are any other steps which I need to do, please do tell me.
Please do let me know the steps if all the are wrong as I'm doing this type of scenario for the 1st time.
Regards,
Sreedhar.

Hi,
Though i am not very sure about your interface requirement/design but would suggest you the following links :
Sender RFC :
/people/swaroopa.vishwanath/blog/2006/12/28/send-rfc-to-sap-xi-150-asynchronous
/people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step
/people/shabarish.vijayakumar/blog/2008/01/08/troubleshooting--rfc-and-soap-scenarios-updated-on-20042009
Reciever JDBC:
JDBC Stored Procedures:
/people/siva.maranani/blog/2005/05/21/jdbc-stored-procedures
JDBC Receiver Adapter -- Synchronous Select u2013 Step by Step
/people/bhavesh.kantilal/blog/2006/07/03/jdbc-receiver-adapter--synchronous-select-150-step-by-step
/people/siva.maranani/blog/2005/09/16/xi-how-to-on-jdbc-receiver-response - XI: How-to
on JDBC receiver response

RFC Adapter not getting data

Hi experts!
I am developing a RFC to File scenario on PI 7.1 EHP1 and ECC 6.0 which is synchronous. Following the Help page Setting Up an RFC Destination for the RFC Adapter I created two destinations. The fist one is a TCP/IP, name RFCDE1COMPANY2, program id BAPI_COMPANY_GETLIST and corresponding gateway host and service I found at SMGW (Parameters). The second one is a Logical with name RFCDE1and reference entry RFCDE1COMPANY2.
At my RFC Sender Adapter I configured the same gateway info and the same program id. After that I tested both destinations and it worked. I created the following report to call the bapi on that destinations::
REPORT ZREP_BAPI_COMPANY_GETLIST.
DATA: company_list TYPE STANDARD TABLE OF BAPI0014_1.
CALL FUNCTION 'BAPI_COMPANY_GETLIST'
IN BACKGROUND TASK
DESTINATION 'RFCDE1'
TABLES
COMPANY_LIST = company_list.
COMMIT WORK.
At SXMB_MONI the request message was processed and the output file generated, but it has only the root tag. At moni the inbound message has no data (company data).
I tested the BAPI_COMPANY_GETLIST at SE37 and there are 149 entries. When I executed this same BAPI with RFC target sys configured to my destination, it didn´t show any data and has an exception called SYSTEM_FAILURE. I think probably the error is on RFC destinations but I can´t figure it out what is wrong.
Best Regards,
Gabriela

Hi experts,
Thank you all for your quick response.
At the TCP/IP Destination there is a button "Unicode Test", according to this test my target system is unicode (character size 2). I changed the option at MDPM&Unicode on that TCP/IP Destination like Madhusudana described. I also selected the checkbutton "Unicode" on sender RFC communication channel.
About the sync/async, I will not use sync async bridge because this scenario can be async. One think that I realized is that when I call my report, I am implicitly calling PI asynchronously and when I call the BAPI directly by the test tool, I am implicitly calling PI synchronously. That is why most part of my tests did not work before.
Now I can see on SXMB_MONI that the scenario worked and the file was generated. But the data are still not being showed on inbound payload. I think something is wrong with my destinations but I can´t figure it out what is.
Ps.: I would prefer to use XI proxies, but this scenario will be configured (not now) on a XI 3.0 with ERP 4.6 C. Now I´m just learning how to handle with RFC Adapter.
Any ideia?
(Points granted)
Thank you and best regards,
Gabriela

RFC ADAPTER destination hangs

To All
I am working on a XI 7.0 system SP5 for netweaver 2004s and am having problems with the RFC adapter.
Steps as follows:-
1.Configure SM59 tcp ip destination on r/3(4.6C) sender system using Xi system host and gateway service
2. step 2 - configure communication channel on my scenario in Integration directory. Activate channel
3. Send Asynchronous message via prgram from R/3 sender
this delivers successfully to BW target ssytem via asynchronous RFC
My problem is when I repeat steps 3 to send more my rfc destination fails with the following in the trace log:-
Trace file opened at 20060303 160158 WST, REL 46D,0,1984, VER 3
======> CPIC-CALL: 'ThSAPECMINIT'
Transaction program not registered
Error RFCIO_ERROR_SYSERROR in abrfcpic.c : 1356
CPIC-CALL: 'ThSAPECMINIT'
Transaction program not registered
DEST =ZSCEN2_XI
HOST =%%RFCSERVER%%
PROG =ZBWIP24_19
GWHOST =ux0800
GWSERV =sapgw53
If I repeat setps 1 to 3 above with a new transaction program it will again work but only once.
Any help would be greatly appreciated and I will award points.
Regards
Liz Porter
PS the adaptor monitor periodically gives the following message:-
Sender Channel 'RFC_INDE4' for Party '', Service 'ERP_WATERCORP_SAPR3_D' (Internal Name 'RfcServer[RFC_INDE4]')
Server data: {jco.server.gwhost=ux0800, jco.server.progid=ZBWIP24_19, jco.server.gwserv=sapgw53, jco.server.unicode=0}
Repository data: {jco.client.lang=en, jco.client.snc_mode=0, jco.client.client=100, jco.client.passwd=******, jco.webas.ignore_jdsr_error=1, jco.client.user=portere0, jco.client.sysnr=81, jco.client.ashost=sapdev}
Current pool size: 1, max pool size : 50
RFC_HISTORY
- Error: 2006-03-03 16:49:27 WST:
RfcException:
message: CPIC-CALL: SAP_CMACCPTP3
no SAP ErrInfo available
Return code: RFC_SYS_EXCEPTION(3)
error group: 102
key: RFC_ERROR_COMMUNICATION

To All
The call from to the RFC destination is attempted as tRFC
see below:-
PARAMETERS:P_TPLNR LIKE IFLOT-TPLNR,
           P_DESTN LIKE TRFCQOUT-DEST DEFAULT 'ZSCEN2_XI'.
CALL FUNCTION 'ZBWIP_FUNCTIONAL_LOCN_OUT'
   IN BACKGROUND TASK
    DESTINATION P_DESTN
     TABLES
       FUNCT_LOC_MAIN       = T_TABLE.
IF SY-SUBRC = 0.
    COMMIT WORK.
    WRITE:/ 'So far so good check XI'.
ELSE.
    WRITE:/ 'Error ', SY-SUBRC.
ENDIF.
The SM59 parameters on R/3 4.6C as set as
Connection type T     TCP/IP connection
Activation Type: registration
Program ID   ZBWIP24_28
Gateway:-
Type                 T TCP/IP connection
Gateway host    ux0800
Gateway service sapgw53
and finally tRFC:-
Connection attempts up to task        2
Time betw. 2 tries [mins]             10
In the XI integration directory:-
Adapter type RFc sender
Application Server(gateway) ux0800
Application service(gateway) sapgw53
Program id                    ZBWIP24_28
Initial Connections           1
Maximum connections           50
Advanced Mode   Maximum reconnection delay 3
A bit more information from our XI system. In SMGW on XI our program shows as "connected" and on drill-down shows status receive data/send. If however we configure a SM59 TCP-IP connection on XI to our XI gateway(ie connect to myself) I get the same CPIC message about 677 timeout for registered program.
Regards
Liz

RFC-Adapter, order not put in

Hi,
my scenario File -> XI -> R/3-Backend will be precessed successful. The Response Payload have the items and in detail of messages appears succes status
"RFC adapter received an asynchronous message. Attempting to send tRFC for BAPI_PO_CREATE with TID XIfr1OyAQS4Td..."
But in R/3 the order ísn't put on.
Does one of you have an idea why???????
Thanks
Hüsniye

Try this code. This works perfectly for us:
CALL FUNCTION 'BAPI_SALESORDER_CREATEFROMDAT2'
EXPORTING
 SALESDOCUMENTIN = SALESDOCUMENTIN
 ORDER_HEADER_IN = ORDER_HEADER_IN
 ORDER_HEADER_INX = ORDER_HEADER_INX
 SENDER = SENDER
 BINARY_RELATIONSHIPTYPE = BINARY_RELATIONSHIPTYPE
 INT_NUMBER_ASSIGNMENT = INT_NUMBER_ASSIGNMENT
 BEHAVE_WHEN_ERROR = BEHAVE_WHEN_ERROR
 LOGIC_SWITCH = LOGIC_SWITCH
 TESTRUN = TESTRUN
 CONVERT = CONVERT
IMPORTING
 SALESDOCUMENT = SALESDOCUMENT
TABLES
 RETURN = RETURN
 ORDER_ITEMS_IN = ORDER_ITEMS_IN
 ORDER_ITEMS_INX = ORDER_ITEMS_INX
 ORDER_PARTNERS = ORDER_PARTNERS
 ORDER_SCHEDULES_IN = ORDER_SCHEDULES_IN
 ORDER_SCHEDULES_INX = ORDER_SCHEDULES_INX
 ORDER_CONDITIONS_IN = ORDER_CONDITIONS_IN
 ORDER_CONDITIONS_INX = ORDER_CONDITIONS_INX
 ORDER_CFGS_REF = ORDER_CFGS_REF
 ORDER_CFGS_INST = ORDER_CFGS_INST
 ORDER_CFGS_PART_OF = ORDER_CFGS_PART_OF
 ORDER_CFGS_VALUE = ORDER_CFGS_VALUE
 ORDER_CFGS_BLOB = ORDER_CFGS_BLOB
 ORDER_CFGS_VK = ORDER_CFGS_VK
 ORDER_CFGS_REFINST = ORDER_CFGS_REFINST
 ORDER_CCARD = ORDER_CCARD
 ORDER_TEXT = ORDER_TEXT
 ORDER_KEYS = ORDER_KEYS
 EXTENSIONIN = EXTENSIONIN
 PARTNERADDRESSES = PARTNERADDRESSES
**checking if the BAPI returned some errors*****
LOOP AT return ASSIGNING <bapiret>.
 IF <bapiret>-type = 'E' OR <bapiret>-type = 'A'.
 success = space.
 EXIT.
 ENDIF.
ENDLOOP.
IF success = 'X'.
****in case of success commit the BAPI*********
 CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
 EXPORTING
 wait = 'X'
 IMPORTING
 return = wa_bapiret.
ELSE.
 ROLLBACK WORK.
 ENDIF.
Also you need to pass on the information for "inx" structures. What I mean is , if you are sending data to field REF_1 in header_in, then ref_1 in header_inx needs to be passed witha value of 'X'.
The update flag in inx structure needs to be 'C' for create.
If have items in your sales order, then you have to pass the values for item_in and item_inx. Additionally you need to pass values for schedule lines also.
Hope this helps.
Thanks,
Bhaskar

RFC Adapter - program ID

Hi Gurus,
I like to know in RFC sender adapter we have given a program id,( a function module )
1) Is this function module in R/3 or in XI.
2) Is it possible to give BAPI in Program ID of sender RFC Adapter
Regards
Manan

Hi,
An RFC server program registers itself under a program ID to an SAP gateway (not for a specific SAP system) If an RFC call is passed on from any SAP system to this SAP gateway with the option Connection with a registered program (with the same program ID), the connection takes place with the corresponding JCo server program.
http://help.sap.com/saphelp_nw04/helpdata/en/09/c88442a07b0e53e10000000a155106/content.htm
/people/michal.krawczyk2/blog/2005/05/09/how-to-call-a-bapi-asynchronously-from-xi--with-qrfc
Regards
Agasthuri Doss

Multiple BAPI calls in RFC Adapter

Hi, Dear Friends!
I have asynchronous scenario File to RFC(BAPI).
File contains raws. For each raw I need to execute BAPI.
With the help of each raw I need to construct one document in R/3 database with the help of BAPI.
But now my scenario provide only one document (only one BAPI is executed).
I read file to xml structure. This structure contains elements. The elements represent raws of file. But BAPI is executed only for the first element.
How to explain to XI that I want it impement BAPI N times - as number of raws in file (or elements in xml structure).
So how to implement multiple BAPI calls. Have you any idea?
Thank you in advance.
Natalia Maslova.

Hi Natalia
have a look on these links
http://help.sap.com/saphelp_nw04/helpdata/en/43/b46c4253c111d395fa00a0c94260a5/frameset.htm
Best Design : for a SOAP -XI - BAPI ( Multiple )
Re: RFC adapter...How it handles multiple calls...
Re: Multiple BAPIs and COMMIT in BPM
Re: Is it possible to compose XML in BPM from responses of multiple BAPI calls?
Multiple BAPI calls in RFC Adapter
may be helpful
Thanks !!!

Why is the RFC Adapter so unstable

Hi all,
I have a scenario where an IDOC is sent from the sender system and an RFC enabled Function Module is called on the target system. Sometimes I get an error in the Adapter for no aparent reason. I check the RFC adapter trace file but none of the exceptions was raised and I am not able to see what was the problem.
But, if I restart the RFC Adapter and send the IDOC again, everything's allright. Why? Is there any other trace avilable somewhere? Is there any way to restart the RFC Adapter periodically and automatically?
Thanks and regards,
Nuno

This sounds like a bizarre scenario. Why would a Idoc (asynchronous) be calling an RFC (synchronous)?
Unless the RFC is doing update? Then you have more problems. You are mixing your QoS from EO to BE. The delivery is no longer guaranteed. The posting to the RFC could work but XI may not get the acknowledgement - RFC adapter does not do commit so you must have a commit in the remote function. If no acknowledgement is received, do you resend and risk duplicate updates? How do you guarantee EO delivery? The sender system is right in expecting EO for it's outbound Idoc.
In all the training material RFC is intended for data retrieval, not data posting. This is consistently done with Idoc (EO, or EOIO).
I would consider changing the scenario to Idoc->xi->Idoc.

XI and RFC adapter

Hi
The RFC Adapter configuration has been done successfully and the adapter starts up successfully.
In our scenario, we attempt to receive an xml message from my local machine through a file adapter, and pass this along to the RFC Outbound adapter to execute a RFC on the CRM box.
The following error message is encountered in the XI monitoring tool.
==============================================================================================================
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:ErrorHeader xmlns:SAP="http://sap.com/exchange/MessageFormat">
<SAP:Context />
<SAP:Code p1="connection closed (no data)" p2="" p3="" p4="">RFC_ADAPTER.SYSTEM_FAILURE_OUTBOUND</SAP:Code>
<SAP:Text language="EN">System error when calling the outbound RFC adapter (connection closed (no data))</SAP:Text>
</SAP:ErrorHeader>
===================================================================================================
I then stop the RFC adapter and attempt the scenario again. I get the following error message in XI monitoring tool.
================================================================================================================
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:ErrorHeader xmlns:SAP="http://sap.com/exchange/MessageFormat">
<SAP:Context />
<SAP:Code p1="Exception in handleRequest of server Xmb2RfcService: java.lang.Exception: Bean n" p2="" p3="" p4="">RFC_ADAPTER.SYSTEM_FAILURE_OUTBOUND</SAP:Code>
<SAP:Text language="EN">System error when calling the outbound RFC adapter (Exception in handleRequest of server Xmb2RfcService: java.lang.Exception: Bean n)</SAP:Text>
</SAP:ErrorHeader>
==================================================================================================================

Hi Eduardo ,
Please check wether the following steps are done in BPM:
1.Async Recieve
A.Properties :
Please set the following
Message:Message 1
Mode:asynchronous
B.Container Data :
Declare Message 1 as asynchronous abstract interface with message type of outbound interface(File Structure).
2.Sync Send
Pre-Requisite:
Copy the inbound Syncronous Interface to Sync_interface_abstract by changing the direction in the message interface of Interface object in the Integration Repository.
A.Properties
Mode:Synchronous
Request:Message 1
Response:Message 2
Syncronous Interface:Sync_interface_abstract
Recievers From :Send Context
B.Container Data:
Message 2 should be declared as the asynchronous message interface with Response message type in inbound interface(Rec Syst Interface).
3.Async send
A.Properties:
Mode:Asynchronous
Message:Message 2
Acknowledgment:None
Recievers From :Send Context
Integration directory has to be configured to send data forth and back to BPM.
1.Send MESSAGE From Outbound interface to BPM.
OutBound and Abstract Interface needs to be mapped in the interface determination and Abstract interface has to be binded to Business Process Name in the repository.
Outbound->Your OutBound Interface(File Interface)
Abstract->Message 1
Reciever Service-> Your Business Process Name
2.Send MESSAGE From BPM to Inbound interface.
Abstract and Inbound interface needs to be mapped in the interface determination and Abstract Interface has to be binded to the Receiver Service/Business System.
Abstract->Message 1
Inbound->Your Inbound Interface(RFC)
Reciever Service-> RFC SYSTEM(SAP)
These are the general steps to follow for Async/sync pattern.
Please let me know if all the steps are configured.

Using RFC adapter as TRFC call

Hi Folks,
 My requirement is to use the RFC adapter as a TRFC call. Can anyone guide me how to do that ?
Regards,
 Santosh

Hi,
 Is your RFC at the sender side or at the receiving side?
If it is at sender side, you can call the rfc function module in UPADTE task .
Sample Code:
CALL FUNCTION <FM Name> IN UPDATE TASK EXPORTING ......
If it is at receiver side, you can specify the QoS as EO(Exactly once in the sender adapter)
Re: How to make an asynchronous RFC call using the receiver RFC adapter?
Regards,
Ravi Kanth Talagana

Configuring receiver RFC adapter to use RFC destination

Hello,
   I have been doing some digging, but I can't find a solid answer on how to configuring a receiver RFC adapter to use an existing RFC destination to call a 4/6C R/3 backend system... Our scenario is to WS --> SOAP --> RFC which is up and running in production just fine on NW 7.0, SP12.
   I ask this question because we, as a company, do not like to maintain passwords in multiple systems. That is necessary when we use the receiver RFC adapter now since SNC is a distant pipe dream for us and we would like to use an existing RFC destination that is set up to call the backend system using a logon ticket.
   I checked the relevant links I could find below, but I can not resolve the answer from them. Has anyone set this up successfully? This link (RFC Destination type RFC Receiver Adapter?) mentions it briefly, but it does not go into any length on how to set it up.
Thanks!
John
http://help.sap.com/saphelp_srm40/helpdata/fr/33/c6e63b60c25767e10000000a11402f/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/33/c6e63b60c25767e10000000a11402f/content.htm
Re: Asynchronous RFC call

Hi John !!
I suggest you to create a new user, without dialog access in your ECC system to be used exclusively by the XI system to access ECC. And then, always use this user in all RFC receiver adapter communication channels.
Regards,
Matias.

RFC adapter receive queue performance

We currently using XI 3.0 on NetWeaver 6.40 with a lot of asynchronous interfaces from JDBC <-> RFC.
After some load we experience that message received in RFC adapter queue are processed after a long time. The messages has status "To Be Delivered" and XI is processing other messages the same time.
2010-01-07 15:25:28 Success Message successfully received by messaging system. Profile: XI URL: http://mlrxiprod:50000/MessagingSystem/receive/AFW/XI Credential (User): XIISUSER
2010-01-07 15:25:28 Success Using connection RFC_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.
2010-01-07 15:25:28 Success Message successfully put into the queue.
after 1 1/2 hour ...
2010-01-07 17:01:10 Success The message was successfully retrieved from the receive queue.
2010-01-07 17:01:10 Success The message status set to DLNG.
2010-01-07 17:01:10 Success Delivering to channel: NAV_FICANCEL_RFC_RECEIVER
2010-01-07 17:01:10 Success RFC adapter received an asynchronous message. Attempting to send tRFC for ZXI_FI_CANCEL_WRAP with TID XIps}UGFk94TwD}G0O}ZGR2m
2010-01-07 17:02:32 Success The message was successfully delivered to the application using connection RFC_http://sap.com/xi/XI/System.
2010-01-07 17:02:32 Success The message status set to DLVD.
Can you explain why it takes so long the message to picked up and processed from the queue. All messages will be processed but the performance is unacceptable. No errors are found in SMQ2.

Hi,
It looks like msgs take very long time to be picked up from the queue(s) ! Is there enough threads allocated (according to SAP recommendations, which I can't remember) ?
How many system & application threads have been allocated ?
Rgds
Chris

Asynchronous RFC adapter

Similar Messages

Maybe you are looking for