URGENT :Synchronous & Asynchronous communication

Hi,
can anyone tell me what is the exact meaning of asynchronous & synchronous communication in sap SRM. SEND me answers with examples to my mail id.
with kind regards,
srinivas.g

Hi,
Everything is explained here :
/thread/127699 [original link is broken]
Kind regards,
Yann

Similar Messages

Difference between Synchronous & ASynchronous.

Hi All,
I few queries:
1) Difference between Synchronous & ASynchronous communication?
2) How should we decide whether it is a Sync or Async scenario?
Regards,
Sreedhar.

Hi Sreedhar,
Apart from the points already added by experts, i would like to add something.....
Synchronous Communication:
In synchronous communication, thereu2019s nothing like scheduling. Sender application executes a u2018singleu2019 Function call, receiver system immediately processes this function call dispatching the response to sender and then it performs implicit database commit.
However this communication is based on assumption that receiver system is available when function call is made. If this is not the case, the communication is seriously disrupted.
Asynchronous Communication:
Here receiver system is not necessarily required to be active at the time of function call. Instead, the call is placed in outbound queue of the sender system and then this call is repeated at regular intervals until receiver system processes the call.
Also Error handling in Synchronous communication: error messages sent back to sender. In Asynchronous communication: errors made persistent.
So conclusion: Queues play central role in asynchronous communication. Further in asynchronous communication, the calls can be executed either by tRFC (Transactional RFC) or qRFC (Queue RFC).
If business requirement is such that your sender system need to know the successful posting of message in the receiver system then approach for synch communication else asynch communication.
Regds,
Pinangshuk.

Synchronous and asynchronous communication tcp/ip

Hello all:
it is common to make synchronous communication between client and server by socket tcp/ip. But I'm needing now to establish an asynchronous communication. I mean:
0.- The server is a multithread process that has the property to establish one connection for each client that wants to send him messages.
1.-The client process sends message permanently to server.
2.- The server processes the request, but don't have to respond to the client.
3.-Only when the user want it, he sends messages to client by web application reusing the same communications that are opened between client and server process.
I hope to explain my problem.
Regards.

Hello all:
it is common to make synchronous communication
between client and server by socket tcp/ip.A socket tcp/ip can be synchronous or asynchronous or both.
But I'm needing now to establish an asynchronous
communication. I mean:Is this purely asynchronous or can it be either.
0.- The server is a multithread process that has the
property to establish one connection for each client
that wants to send him messages. Fine, any mode would be okay.
1.-The client process sends message permanently to server. By permanently do you mean;
- it is deleted from the client,
- it is store on the server is a write once read many media. i.e. it is permenetly on the server and cannot be deleted/altered.
2.- The server processes the request, but don't have to respond to the client.The server should never have to respond to the client. e.g. the server can go down so the client nees to live with the possibility it won't get a reply.
Synchronous or Asychronous describes how the reply is send. No reply means it is neither.
3.-Only when the user want it, he sends messages to client by web application reusing the same communications that are opened between client and server process.Are you using socket or a web application server ie. HTTP.
You wan to be able to reuse the connection. You can do this in any of the case mentioned so far.
>
I hope to explain my problem.I hope you will explain your problem too.

Is in PI7.1 possible asynchronous communication between SOAP and ABAPProxy?

Hi,
when method execute_asynchronous has disapeared since XI/PI 7.1, is
there still way how to use ABAP proxy in asynchronous way?
We need to build asynchronous connection SOAP->PI->ABAP_Proxy.
In PI, both interfaces are defined as asynchronous (outbound for SOAP and
inbound for ABAP Proxy).
Despite of this fact, when message is sent, it is processed
synchronous way.
I have set breakpoint in my implementation of method for ABAP Proxy
message processing. When message is sent and breakpoint is reached,
whole connection stays open (between SOAP and PI and between PI and
ABAP Proxy) and waits for processing method (the breakpointed one) to
return. Only when processing method returns, is connection finelly
closed.
If i understand it correctly, this is synchronous behavior. In
asynchronous behavior, as i understand it, should be connection
between PI and ABAP Proxy of application server closed immediately
after message has been delivered. This mean before my processing
method is even called.
The same could be said about SOAP and PI communication. Connection
should be closed immediately after PI has received message. From
definition of asynchronous communication of PI is obvious, that PI
should receive message correctly and close connection to sender system
even when receiver is unreachable. It should deliver message later
when, receiver system is back on line. So why it keeps connection to
sender system open while it waits for receiver?
Why is this happening, when both interfaces are defined as
asynchronous? Could be the reason for this, if APPLICATION
ACKNOWLEDGEMENT is set on by default? If so, how can i change it
to SYSTEM ACKNOWLEDGEMENT, or disable it at all?
Or is this kind of asynchronous communication even possible since
XI/PI 7.1 ?
Processing of message we are sending can take some time, so we dont
want connection pending open while waiting for finish of
processing. Thats the reason why we have chose asynchronous model to
use.

Quote from How to Use the J2EE SOAP Adapter:
"If you select Best Effort, the Web service client will receive a response
message in the SOAP body. Otherwise, the Web service client will not receive a
response message if no error occurs."
"if no error occurs" - that is the problem. In either case he still
waits if some error occure or not. I dont want it. Once PI has
received message, I want the connection with sender to be closed. If
there will be error in communication between PI and reciever, I want
to see it only in PI log. That mean no notification to sender to be
send about that error.
Is that possible?

RFC Sender to SOAP receiver through asynchronous communication

Hi all,
I have a requirement where I need send data from SAP HR system(through RFC) to webservice asynchronously. For this I preferred RFC as a sender and SOAP as a receiver. Can anybody tell me whether it could be possible because I have gone throught the blog
/people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step
accordingly I did the configuration and then i gone through the blog
/people/shabarish.vijayakumar/blog/2006/03/23/rfc--xi--webservice--a-complete-walkthrough-part-1
and
/people/shabarish.vijayakumar/blog/2006/03/28/rfc--xi--webservice--a-complete-walkthrough-part-2
in which they are communication synchronously.
But in my case i need to communciation asynchronously. so when i am creating Interface mapping system is not able to pickup my mapping program. I mapped source message as RFC request with Target structure.
Please let me know if asynchronous communication is possible how i have to may between RFC and SOAP.
Regards,
Dhill

Hi Satish,
Thank you very much it is working fine now. But I need some more clarification that for this scenario to execture we need a report from SAP side. Instead is there any other method for XI to receive data. I think it could be possible through proxies if yes can you send some link which would be very useful for me.
Otherwise is there any other way to do it by avoiding to write the code in abap but to call the RFC.
Regards,
Dhil.

Synchronous - asynchronous interface (RFC - XI - jdbc)

hello to everybody!
i want configure a synchronous - asynchronous interface (RFC - PI - jdbc) whit my PI 7.1
This RFC send 2 output tables to PI/XI and i want write it into 2 different tables in a SQL Server Database.
How can i do it?
i tried whit one mapping to a unique outbound datatype...but only header table was insert and not rows.
i tried whit 2 Receiver Interfaces but i have on mapping the follow error:
Multiple inbound interfaces not supported for synchronous calls
so??
other possibility?
BPM?
please help me
Thanks
Alessandro

Hi,
I have a similar problem; I have JMS - PI - RFC synchronous scenario. I will receive message from JMS, and depending on the data received, I should call either of two RFCs (NOT BOTH). The BAPI return message should then be sent back to JMS.
Hence, I have one "Sender/Outbound" Message Interface, one receiver determination for that Message Interface - in which there is "one" receiver (backend SAP system).
In "Interface Determination", I specifed the two BAPIs as two Interfaces, and defined conditions based on "context objects" - since I need to know the Interface Mapping "dynamically"
However, I get the error - "Multiple inbound interfaces not supported for synchronous calls ". any suggestions on how to proceed?
I am posting this question here as it is a related issue. Hope it is fine.
Thanks,
Archana

An exception handler is obligatory for synchronous RFC communication

I am getting the error "An exception handler is obligatory for synchronous RFC communication" when I try to activate an Integration Process. Under a synchronous Send step, under Exceptions, I have System Error and the RFC.Exception Application Error to be handled. For both I have given the same Exception handler block. Is this not allowed? Why am I not able to go to same Exception handler block in case of both System Error as well as Application Error?
Thanks

you are right, it was erroring out due to the next step. Now if there is system error or exception, it will go to the exception branch. Here I need to have the ability to restart the process from this point after being alerted and having fixed the issue. So I am thinking of doing the send step again in the exception branch. But since the application error initially will exist soon after the alert is issued, this step will complete as I cannot handle application error a second time (this is where it was giving that error that exception handler was mandatory).
Is there a way in which I can stop/fail the process after the exception branch gives the alert so that I can restart the failed branch again?

Asynchronous Communication - R/3 - XI

I'd like to get your opinion on the best method of Asynchronous communication between R/3 and XI given the following assumptions:
     ABAP Proxies are not an option. SAP R/3 is version 4.6C with Basis 4.6D
     Standard IDocs are only available for a few of the interfaces (10%)
Options:
1.     Standard IDocs when available and custom IDocs for other interfaces.
Pros
     Guaranteed one-time delivery
     Record of data sent from R/3
     Performance is manageable at multiple stages
     Excellent monitoring, and retry ability
Cons
     Requires creating custom IDocs
2.     Transactional RFCs
Pros
     Guaranteed one-time delivery (with tRFC)
     Faster to implement than custom IDocs
Cons
     No record of data sent from R/3
     Performance isnt as manageable as with IDocs
     Limited ability to monitor and retry
Points will be rewarded...
Thanks,
Jesse

Jesse,
I think the best option is to use RFC adapter for your requirements where the standard IDoc is not available.
The reason for this is, someone needs to develop ABAP function modules for RFC as well as IDocs. If it is a custom IDoc, then you have to create custom IDocs and all of its components (segments, IDoc types, Message types, partners, process codes etc.) to execute a function module which is a custom code. Instead of going through all this hassle, better use RFCs.
In some cases you need to use IDoc where you want to reprocess the data instead of getting it from the source again.
If you need more information let me know.
regards
Shravan

Wat is synchronous, asynchronous & local mode of update in BDC plz help

wat is synchronous, asynchronous & local mode of update in BDC .
plz explain each of them

A Asynchronous updating. In this mode, the called transaction does not wait for any updates it produces to be completed( does not wait till the update in database is complete either it is successful or un successful). It simply passes the updates to the SAP update service. Asynchronous processing therefore usually results in faster execution of your data transfer program.
Asynchronous processing is NOT recommended for processing any larger amount of data. This is because the called transaction receives no completion message from the update module in asynchronous updating. The calling data transfer program, in turn, cannot determine whether a called transaction ended with a successful update of the database or not.
If you use asynchronous updating, then you will need to use the update management facility (Transaction SM12) to check whether updates have been terminated abnormally during session processing. Error analysis and recovery is less convenient than with synchronous updating.
S Synchronous updating. In this mode, the called transaction waits for any updates that it produces to be completed. Execution is slower than with asynchronous updating because called transactions wait for updating to be completed. However, the called transaction is able to return any update error message that occurs to your program. It is much easier for you to analyze and recover from errors.
L Local updating. If you update data locally, the update of the database will not be processed in a separate process, but in the process of the calling program. (See the ABAP keyword documentation on SET UPDATE TASK LOCAL for more information.)
reward if it is helpful..
sai ramesh.

Question on Asynchronous Communication

Hi all,
Tell me which of this is true
In SAP XI in async communication
1. We don't have a response message
2. We have a response message but we don't get it immediately(in that case how to check for this message)
I am asking this question because in normal programming(C#, Delphi etc) usually async communication means that the server will respond after it is done with processing and then throw a event which the client catches it and provides a handler for that event.

Hey Sonia,
your comment totally makes sense, because literally asynchronous means "not at the same time". So, an asynchronous communication should mean a message which is sent but whose response is not sent right away.
Also, strictly speaking, in any EAI-like program, to develop an asynchronous communication means to develop two 1-way communication. Of course, for a server system to send back information to a client system, there must be, in some point of time, an event generated by client system requesting that information (apart for some exceptions, such as the scheduled automatic scenarios, for example).
Hence, in EAI typical vocabulary, the action of developing an asynchronous communication means developing 1-way integrations (1 or more).
Regards,
Henrique.

Difference between BATCH & RUNTIME ,SYNCHRONOUS & ASYNCHRONOUS

REPORT_EXECUTION_MODE has two values BATCH & RUNTIME.
what is the difference ? pls expalin in detail
REPORT_COMM_MODE has two values SYNCHRONOUS & ASYNCHRONOUS
what is the difference ? pls expalin in detail
Thanks in advance

Tony is right.
Anyway
Forms applications calling a report synchronously make the user wait while the
report is processed on the server.
For long-running Reports, it is best that you run the report asynchronously by
setting the REPORT_COMM_MODE property to asynchronous and the
REPORT_EXECUTION_ MODE to batch:
SET_REPORT_OBJECT_PROPERTY(report_id,REPORT_EXECUTION_MODE,BATCH);
SET_REPORT_OBJECT_PROPERTY(report_id,REPORT_COMM_MODE,ASYNCHRONOUS);Regards

Is Function Activity execution synchronous/asynchronous?

Hi,
I would like to know the mode of execution of Function activity, that is whether it is synchronous/asynchronous?
Suppose if I have 2 activities in a process, one is of type PL/SQL and another is of type External Java. When I start the process from a java program, when will the calling program get the control back? will the exceution of each activity is synchronous or asynchronous?
thanks in advance
Regards
honnur

Thanx for the reply.
I find that if the function activity is of type PL/SQL then the calling function(WF Engine) waits till the PL/SQL procedure/function exection is complete. But if the function activity is of type External Java then the calling function(WF Engine) does not wait until the Java function execution is complete. In this case, when External Java Agent finishes the function excution, we have to explicitely invoke background process to complete that activity.
So the Java function activity execution is asynchronous from calling function perspective.
is my understanding right??
TIA
honnur

RFC Asynchronous communication

Hi Experts,
I am doing a scenario in which data is passed using RFC via Proxy to PI and from PI to JMS queue(Target system).
My problem here is i am new to SAP PI 7.1 and i have never worked on RFC before.
Can anyone suggest some blogs so that i can refer and understand the RFC Asynchronous communication process.
Thanks in Advance

Hi,
we cannot suggest blogs as you need to try the search functionality first
but once you get a more detailed question which cannot be answered by using search
come back to us and we will gladly help you ok ?
thank you,
Regards,
Michal Krawczyk

J2EE asynchronous communication protocol

Hi
In my project, im supposed to program software agents and they are suppose to communicate to each other asyncrhonously. I need some directions to it as im quite new to J2EE stuffs and many of the java components.
eg like RMI, JMS, ...
Thanks

JMS (Java Message Service) is a standard for asynchronous communication via a message queue.
See http://java.sun.com/products/jms/index.html
Jesper

Synchronous and asynchronous communication

Hi all
i am very new to jms and java. I have the task of developing an application for communication for a global company. The application must support most if not all of the following features:
-synchronous messages
-Asynchronous ('offline') messages
-Authentication/identification
-Saving a log of all conversations
-Conference rooms
-Secure (encrypted) communication
-User information database (e.g. postal addresses, email addresses, -pictures, etc)
-Sophisticated GUI
-Resilience to network breakdown
-Multimedia messages (styled text, pictures, file attachments)
-Shared document editing
-Shared whiteboard facility
what can I use to develop this application...will JMS be able to do this??
thank you

This appears to be more like a user coomunication application. I would look for the architecture of commonly available instant messaging applications, such as MSN, Yahoo, Jabber.
I would think of JMS to be used for transmitting business messages, like stock quotes, etc. Creating a PTP connection or a Topic in a pub-susb message would be an over-kill for such a usage scenario.

URGENT :Synchronous & Asynchronous communication

Similar Messages

Maybe you are looking for