Receiver ASynchronous RFC

I need to develop an Asynchronous RFC Receiver side? How should I accomplish this?
appreicate your help.

Hi Mohan,
no, you dont call the RFC direcly. You just trigger a message, what ever you like, to XI. The inbound interface - your RFC - will be found by the interface determination of you IB directory. The ABAP call is made by the RFC adapter (you have to configure that RFC communication channel like described in <a href="http://help.sap.com/saphelp_nw04/helpdata/en/33/c6e63b60c25767e10000000a11402f/frameset.htm">SAP library: RFC-Adapter</a>) who translates the XML to DIAG protocol.
Regards,
Udo

Similar Messages

Asynchronous RFC call from R/3

I need to make an asynchronous RFC call from R/3. I receive an error message in R/3 stating that my RFC destination can only be of type I (Internal) or type 3 (R/3 system). In order for it to reach XI I need it to be of type T (TCP/IP). Any help would be appreciated.
Here is the function call.
CALL FUNCTION 'Z_B2B_R3_FUNCTIONAL_ACK' starting new task 'SESSION1'
   destination 'RFC2XMBSERVICE'
      EXPORTING
           MSG_TYPE            = msg_type
           ORDER_HEADER_RETURN = order_header_return
      TABLES
           RETURNCODE          = i_return.
the RFC desitnation RFC2XMBSERVICE is of type TCP/IP which by default makes it synchronous.
Thanks,
Jim

hi,
have you tried:
CALL FUNCTION 'Z_B2B_R3_FUNCTIONAL_ACK'
in background task
destination 'RFC2XMBSERVICE'
EXPORTING
MSG_TYPE = msg_type
ORDER_HEADER_RETURN = order_header_return
TABLES
RETURNCODE = i_return.
commit work.
Regards,
michal

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

Asynchronous RFC calling using BPM

Hi to all,
I have this scenario:
FILE -> XI -> RFC -> XI
I want to use the BPM to do this, thus I have built this BPM:
START -> RECEIVE -> BLOCK1(SEND) -> BLOCK1(RECEIVE) -> STOP
My problem is that I want to use an asynchronous scenario and, thus, when XI sends message to RFC, BPM seems to become inactive and the BPM is not able to receive the RFC Response. How can I solve this problem? How can I mantain BPM active to receive the RFC Response?
Thanks to all!

Hey,
I suppose you are trying to do a similar senario
The scenario must be executed asynchronously, but there needs to be an automatic confirmation that the business data was successfully processed (this would be the equivalent of an applicationacknowledgement). Cross-component BPM (ccBPM) will be used to process the confirmation message.
How To Use BAPI wrappers in asynchronous scenarios with ccBPM
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/59ef6011-0d01-0010-bfb0-b51381e00509
Cheers,
*RAJ*
*REWARD POINTS IF FOUND USEFULL*

TRFC and Asynchronous RFC

Is there any diff between TRFC and ARFC ?
Is TRFC another name for ARFC?

Hi,
Transactional RFC (tRFC) they are previously known as ARFC
Transactional RFC (tRFC, previously known as asynchronous RFC) is an asynchronous communication method that executes the called function module just once in the RFC server. The remote system need not be available at the time when the RFC client program is executing a tRFC. The tRFC component stores the called RFC function, together with the corresponding data, in the SAP database under a unique transaction ID (TID).
If a call is sent, and the receiving system is down, the call remains in the local queue. The calling dialog program can proceed without waiting to see whether the remote call was successful. If the receiving system does not become active within a certain amount of time, the call is scheduled to run in batch.
tRFC is always used if a function is executed as a Logical Unit of Work (LUW). Within a LUW, all calls
·         are executed in the order in which they are called
·         are executed in the same program context in the target system
·         run as a single transaction: they are either committed or rolled back as a unit.
Implementation of tRFC is recommended if you want to maintain the transactional sequence of the calls.
Disadvantages of tRFC
·       tRFC processes all LUWs independently of one another. Due to the amount of activated tRFC processes, this procedure can reduce performance significantly in both the send and the target systems.
·       In addition, the sequence of LUWs defined in the application cannot be kept. It is therefore impossible to guarantee that the transactions will be executed in the sequence dictated by the application. The only thing that can be guaranteed is that all LUWs are transferred sooner or later.
regards
prasanth

Why asynchronous RFC is stated as asnynchronous processing type ?

in help document it stated that ,in r/3 system asynchronous RFC has different meaning...
what is that meaning?
why it stated as asynchronous processing type?

hi,
ARFC:
Asynchronous remote function calls (aRFCs) are similar to transactional RFCs, in that the user
does not have to wait for their completion before continuing the calling dialog. There are three
characteristics, however, that distinguish asynchronous RFCs from transactional RFCs:
When the caller starts an asynchronous RFC, the called server must be available to
accept the request.
The parameters of asynchronous RFCs are not logged to the database, but sent directly
to the server.
Asynchronous RFCs allow the user to carry on an interactive dialog with the remote
system.
The calling program can receive results from the asynchronous RFC.
You can use asynchronous remote function calls whenever you need to establish communication
with a remote system, but do not want to wait for the functions result before continuing
processing. Asynchronous RFCs can also be sent to the same system. In this case, the system
opens a new session (or window) and allows you to switch back and forth between the calling
dialog and the called session.
To start a remote function call asynchronously, use the following syntax:
CALL FUNCTION RemoteFunction STARTING NEW TASK taskname
Destination ...
EXPORTING...
TABLES ...
EXCEPTIONS...
I hope it helps.
regards
Anver

Asynchronous RFC vs synchronous RFC

Hi Experts,
Can you give me what are the differences between asynchronous RFC and synchronous RFC?
thanks.
Moderator message : Not enough re-search before posting. Thread locked.
Edited by: Vinod Kumar on Jul 4, 2011 4:45 PM

Gabriel,
synchronous
the sender sends a request message to the receiver and waits for a response message.
for eg. consider a scenario.. where u have a customer no. and u need customer details.which is stored in R/3...so u can configure a HTTP to R/3 synchronous scenario... a http request will be sent to R/3 having a CUSTOMER NO....and in response u will get details of customer like...cust name,address, etc...
asynchronous
sender send a request message but doesn't wait for response.
for eg consider a file to file scenario .where u need to pick a file from a source location to a destinartion location....so...it will asynchronous interface
hope u r lil bit clear!!.
Regards
Biplab

How to call Asynchronous RFC

Hi Everybody,
 Could yo pls guide me on how to implement asynchronous RFC. When i run my RFC using Report :
CALL FUNCTION 'Z_HR_NO_ALTINN_TX' DESTINATION 'Q3A2X7A'starting new task 'test'
exporting
 PASSWORD = 's'.
I get the error saying :
What happened?
 When executing the asynchronous RFC, the RFC destination "Q3A2X7A" had
 neither an internal (connection type 'I') nor an R/3 communication
 type (connection type '3'.
 Error in ABAP application program.
 The current ABAP program "Z_ALTINN_TEST" had to be terminated because one of
 the
 statements could not be executed.
 This is probably due to an error in the ABAP program.
Error analysis
 A typical cause of error is the
 execution of external programs (RFC destinations of the type
 TCP/IP) via asynchronous Remote Function Call (RFCs with the
 addition 'STARTING NEW TASK taskname').
 RFC destination... "Q3A2X7A"
I would like to know if async RFC call is possible to XI.
Regards,
Raj

Hi,
you need to call the RFC from ERP, R3
with
call function XXXXX
in background
and Commit work.
Regards,
michal

How to receive an RFC message in PI ABAP stack from ECC

Hi mates,
I am involved in a scenario in which we want to receive a message in PI (ABAP stack) from ECC (ABAP stack as well).
We created a RFC destination (3) in sender system (ECC) so both stacks could be linked. However, we do not know how to receive this message once we are in PI Abap stack.
In sender system code, a call destination takes place, an this destination stands for the one destination i noted before.
BUT, as this RFC does not exist in PI, i wonder what steps have to be done in PI in order to be able to get the message from ECC.
Hope you guys can guide me through this. Any help
Thanks a lot in advance and best regards,
david

Hi Anand,
No no, i do not want to create any sender RFC Comm Channel.
What i want is to receive (by means of no PI adapter) a message in PI (abap stack) from ECC (abap stack), just by a RFC connection (type 3) between both systems.
I will try to explain in more detail what i want to achieve:
1) A standard SAP program is executed in ECC, at the end, a call destination is done.
2) This destination call, calls an RFC destination that points to PI (RFC dest in SM59, type 3)
(Until now, nothing is done in PI, there is no sender adapter, we just linked both ABAP stacks)
3) In ABAP stack of PI, we want to receive the message, make any transformations and send the target emssage to PI adapters
4) From that moment on, a ordinary PI integration is done.
So my question is, what kind of stepd so i have to perform to get the message from ECC in PI without creating any object in PI (ESR, ID, i mean). Just as if we wanted to receive a RFC message, lets say, in BI (abap side) from ECC.
Hope you got me this time.
Thanks a lot in advance.
Best regards,
david
Edited by: David de Miguel on Dec 27, 2010 11:48 AM

Asynchronous RFC

Hi,
Im using rfc_abap_install_and_run function module to create abap programs and function modules remotely from non-sap sytem i.e. ( Through JAVA beam).
Here, my requirement is that i want to run this function module paralelly i.e. Asynchronous RFc.
So, how can i use this function module and make it as 'starting new task' or any thing that should execute it parallelly many fm and create the required one..
As of now, it is getting error like user is editing...
I think you understood the problem..
Awaiting your response.
Thanks
raja

Hi,
So a maximum of six sessions can be opened.. so how can a user from JAVA can identify then the next i.e. seventh task should be again reset to first and then process it in a loop of 1 to 6.
Is that pssble from JAVA end..
thanks
rohith

RFC receiver asynchronous

Hi, ive got a problem with an Asynchronous message. The operation goes from an FTP to a RFC. The file adapter converts a flat file into a XML, and the XML is sent to a Remote RFC.
Everything is ok in XI. In the SXMB_MONI and in the RFC adapter monitor we see that the message is correctly sent to the RFC, but the RFC receive nothing.
We have written a short routine in the RFC that just insert an X in a testing table, but nothing happen.
Thanks.

Hi Eduardo,
look as well to XI: SM58 and R/3: ST22 to find out the reason.
Regards,
Udo

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

ABAP Proxy Receiver Asynchronous EOIO

Hi,
Is it possible to Guaranteeing the Sequence of Asynchronous Messages for ABAP Proxy Receiver(EOIO)?
If yes, how can I configure?
Thanks,
Kiara.

Hi Stefan,
Thank you.
One quick question.
In case if I use JMS>PI>RFC(Async) then also no need of maintaining EOIO for RFC Receiver Async?
On JMS sender we are maintaining EOIO.
Reason for this request is currently we are using JMS>PI>RFC Async. We are using EOIO on JMS sender, but some times sequence of messages is missing.
Can you please let us know the cause of this issue.
Thanks,
Kiara.

File Adapter Receiver Asynchronous

Hi ,
I've read a couple of times now that a file adapter which is operated as a receiver is always asynchronous. This means he cannot be used in conjunction with a synchronous RFC.
Is that right ?
I haven't found anything about the asynchronous behavior of the file adapter in any official documentation.
Can please someone provide me with a link ?
Thanks in advance.
Best regards,
Frank

Hello,
You can use it synchronously by choosing "Best effort" in quality management of your sender file adapter.
Or if you want you can define synchronous RFC in a BPM step, independently of your sender interface.
Regards,
Chris

Asynchronous RFC call

I need to Send some information to an RFC and my friend is saying that, I cannot call RFC Asynchronously and I couldnot understand that point, could some one help me please.
Thanks.

Dear Saravana,
Dear Sravya,
I would like to do the following scenario:
SAP/PS --> XI --> JMS
In SAP I call the Bapi: BAPI_NETWORK_MAINTAIN and sends network datas to JMS through XI.
In the design:
I only imported the BAPI to my SWCV. (I don't use any own made Data types/Message types/Message interfaces.)
In the config:
I used this imported BAPI name (BAPI_NETWORK_MAINTAIN) as my interface.
It works, but it sends the message synchronously...
I would like to use this simplicity (only import the BAPI and don't use any own created interfaces,DTs, MTs and BPM neither)
But if I don't create any own Message Interface I can't control the synchronous/asynchronous mode.
Is it feasible that way??
Thank you in advance!
Andras

Receiver ASynchronous RFC

Similar Messages

Maybe you are looking for