Difference between synchronous and asynchronous

Hi, i´m doing a t01 syncbo... what is the difference between synchronous and asynchronous?
What is better for syncbo t01, and for syncbo s01?
Thanks,

Hi
There are two options available:
Synchronus in which the data is exchanged while the mobile is online. The mobile sends the messages to the middleware and gets the response there and then, while it is online.
ASynchronus in which the mobile sends the messages to the middleware and goes offline. The responses are calculated and stored in the outbox. When the mobile again comes online and syncs, it gets the response messages.
The choice depends actually on the type of the syncBO, like if there is an Order being created on the mobile and its approval (which will come from the backend) is needed, most of the time immediately. This SyncBO must be Synchronus.
The other data, to which response is not immediately needed can be made as Syncronus.
The choice has serious performance considerations, So it should be made wisely.
Please ask if you need more information.
Thanks
Ankur
(Award Points if the info is useful)

Similar Messages

Differences between Synchronous and Asynchronous updates

can any one tell me the differences between these updates

Hi
Look at this tread it can help:
https://www.sdn.sap.com/sdn/collaboration.sdn?contenttype=url&content=https%3A//forums.sdn.sap.com/search%21default.jspa%3FforumID%3D131%26threadID%3D67445

Re : what is diffrent Between Synchronies and Asynchronies process

Hi ,
what is diffrent between Synchronies and Asynchronies process in session Method and call Transcation method pls give one Example...
Thanks
Arief .S

Synchronus data processing is that in which the program calling the update task waits for the update work process to finish the update before it continues processing.
In Asynchronus update the callng program does not wait for update work process to finish the update and continues as normal.
A BDC done with sessions is always synchronus.
A BDC with call transaction is by default asynchronus
unless you define it explicitly as
call transaction 'XXXX' ...... update 'S'.
( If you donot define update option it is defaulted to "A" ).
The update method is of importance when one transaction locks data which may be required by a subsequent transaction . The subsequent transaction will fail if data is locked from previous one. An example would be you are creating sales order for same material in succession ( with asynchronus update ). Quite likely that some of transactions would fail due to material locked.
For large volume of data Call Transaction will be faster but you have no restart capability here. Suppose from 1000 transactions 100 fails . You will have to run the BDC program again exclusing the ones which wrere successful. However with session method you have the option to process the error transactions again in SM35 . So if you are sure that errors will not occur use call transaction else use session method.

Synchronous and Asynchronous updating in LIS

Dear experts
What is the difference between
Synchronous and Asynchronous updating in LIS ?
There are three radio buttons for ASYNCHRONOUS UPDATING [1],[2],[3]
What is the significanse of each of them?
Regards
Siddharth

Hi siddarth
Difference between synchronous update & asynchronous update
Synchronous update -Immediate start, i.e., when an event takes place that triggers an update
Asynchronous update - Delayed start, i.e., updating is slightly delayed after an event that triggers an update
Regards
Srinath

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.

Differences between Synchronized methods and blocks

Hi all,
I would like to differences between Synchronized methods and blocks.
- Muni

Well, you'll get so many of right answers in next ten to thirty minutes.
I like to yield :)
Oooo... Ten minutes has passed.
Synchronized block is a toilet room with a lock in a public lavatory.
Only one person(running thread) can have the lock at a time.
And, she/he have to receive the lock from a particular object obj like:
synchronized(obj){.....} // one object has only one lock for this {} toilet and for any other toilets how many there are... *
(*: In other words, while a thread is executing a synchronized(obj){} block, other threads can't enter other synchronized(obj){} blocks.)
Synchronized method is a kind of synchronized block.
This special block is defaulted to have lock from the object on which the method is defined.
public class Foo{public synchronized Method(){}}
use the lock of a Foo object.
Message was edited by:
hiwa
Message was edited by:
hiwa

Difference between idoc and rfc

what is the difference between idoc and rfc? when and where it is used? when there is idoc, why rfc vice versa?

IDoc (for intermediate document) is a standard data structure for electronic data interchange (EDI) between application programs written for the popular SAP business system or between an SAP application and an external program. IDocs serve as the vehicle for data transfer in SAP's Application Link Enabling (ALE) system.
IDocs are used for asynchronous transactions: Each IDoc generated exists as a self-contained text file that can then be transmitted to the requesting workstation without connecting to the central database.
Another SAP mechanism, the Business Application Programming Interface (BAPI) is used for synchronous transactions.
A large enterprise's networked computing environment is likely to connect many geographically distributed computers to the main database. These computers are likely to use different hardware and/or operating system platforms. An IDoc encapsulates data so that it can be exchanged between different systems without conversion from one format to another.
IDoc types define different categories of data, such as purchase orders or invoices, which may then be broken down into more specific categories called message types. Greater specificity means that an IDoc type is capable of storing only the data required for a particular transaction, which increases efficiency and decreases resource demands.
An IDoc can be generated at any point in a transaction process. For example, during a shipping transaction process, an IDoc may be generated that includes the data fields required to print a shipping manifest. After a user performs an SAP transaction, one or more IDocs are generated in the sending database and passed to the ALE communication layer. The communication
layer performs a Remote Function Call (RFC), using the port definition and RFC destination specified by the customer model.
The IDoc is transmitted to the receiver, which may be an R/3, R/2, or some external system
RFC
Remote Function Calls (RFC) and data exchange through IDoc message documents. RFC makes direct and synchronous calls of a program in the remote system. If the caller is an external program it will call an RFC-enabled function in R/3 and if the calling program is the R/3 system it will call an RFC-function in another R/3-system or it will call a non-R/3 program through a gateway-proxy (usually rfcexec.exe). BAPIs are a subset of the RFC-enabled function modules, especially designed as Application Programming Interface (API) to the SAP business object, or in other words: are function modules officially released by SAP to be called from external programs.
note:reward points if solution found helpfull.....
regards
chandrakanth.k

Different bet Synchronous and Asynchronous

Dear all,
I've been searching in forum and this is what i understand:
Asynchronous indicates that the activity is not complete until a terminating event is received .
When asynchronous methods are executed , workflow does not continue to the next step until it
receives an acknowledgement that the method has finished .
I've tested async method with terminating event and it works as what mentioned above.
On the other hand, I've also tested with Synchronous method with terminating event. And i notice the behaviour is same as async. That's my workflow will not proceed futher until i execute the Synchronous method and eventually trigger the terminating event.
So my question is:
1. What is the actual differences between Sync and Async ?
2. When is right time to use terminating event with Sync and Async?
Kindly comment. Thanks in advance.

Hello,
Terminating event is mandatory for asynchronous task to complete while synchronous task can exists with or without terminating events. Terminating event is optional for synchronous task.
E.g. Say you have work item for leave approval.
A. Above task as asynchronous method with terminating event "Leave_approved".
When user clicks on the above task in workflow inbox, task will open where user can approve leave request. This task will be completed only when terminating event occured in the system. Task will not vanished from inbox if terminating event is not raised.
B.Above task as synchronous method without terminating event .
When user clicks on the above task in workflow inbox, task will open where user can approve leave request. Task will vanished from inbox .
Regards,
Sagar

Differences between LSMW and BDC

Hi All
Please can you give me the few points about the differences between LSMW and BDC?
Awaiting for your Responce
Praveen

Hai Check with the following document
GOOD
THERE IS THREE TYPE OF METHOD IN BDC
BDC SESSION
CALL TRANSACTION
CALL DIALOG
What is BDC or batch input
The Batch Input is a SAP technic that allows automating the input in transactions. It lies on a BDC (Batch Data Commands) scenario.
BDC functions:
· BDC_OPEN_GROUP : Opens a session group
· BDC_CLOSE_GROUP : Closes a session
· BDC_INSERT : Insert a BDC scenario in the session
· The ABAP statement "CALL TRANSACTION" is also called to run directly a transaction from its BDC table.
It runs the program RSBDCSUB in order to launch automatically the session. The session management is done through the transaction code SM35.
The object itself is maintanable through the transaction SE24.
BDC methods:
Method
Description
Parameters
OPEN_SESSION
Opens a session
SUBRC (Return Code 0 OK)
SESSIONNAME (Session to be created)
CLOSE_SESSION
Closes a session
None
RESET_BDCDATA
Resets the BDC Internal Table...
None. Normally, for internal purpose
BDC_DYNPRO
Handles a new screen
PROGNAME (Name of the program)
DYNPRONR (Screen Number)
BDC_FIELD
Puts a value on the screen
FIELDNAME (Name of the field)
FIELDVALUE (Value to be passed)
CONSTRUCTOR
Constructor - Initializes NO_DATA
NODATA (No data character). The constructor is called automatically when the object is created.
RUN_SESSION
Launches a session with RSBDCBTC
None
CALL_TRANSACTION
Calls a transaction with the current BDC Data
MODE (Display Mode)
UPDATE (Update Mode)
TCODE (Transaction to be called)
BDC_INSERT
Inserts the BDC scenario in the session
TCODE (Transaction to be called)
BDC techniques used in programs:
1) Building a BDC table and calling a transaction,
2) Building a session and a set of BDC scenarios and keeping the session available in SM35,
3) Building a session and lauching the transaction right after closing the session.
BDC using Call Transaction
BDC using Call transaction involves calling an SAP transaction in back ground from within the ABAP
program. The process involves building an Internal BDC table containing the screen information needed to
execute the required transaction and then passing this to the Call transaction command (See code example).
The full procedure for creating a BDC program is as follows:
What is the difference between batch input and call transaction in BDC?
Session method.
1) synchronous processing.
2) can tranfer large amount of data.
3) processing is slower.
4) error log is created
5) data is not updated until session is processed.
Call transaction.
1) asynchronous processing
2) can transfer small amount of data
3) processing is faster.
4) errors need to be handled explicitly
5) data is updated automatically
BATINPUT/DIRECT INPUT
A: Batch-inputs can not be used to fill the "delivery due list" screen because it is not a dynpro. This is a standard SAP report. A SAP report (check with "System -> Status") may be called using SUBMIT sentence with the appropriate options . It is preferred to call a report than create a Batch-input program.
GO THROUGH THIS LINK
http://www.guidancetech.com/people/holland/sap/abap/zzsni001.htm
The LSM Workbench is an SAP R/3 based tool that supports the one-time or periodic transfer of data from non-SAP systems ("legacy systems") to SAP systems.
The LSM Workbench helps you to organize your data migration project and guides you through the process by using a clear sequence of steps.
The most common conversion rules are predefined. Reusable conversion rules assure consistent data conversion for different data objects.
LSMW vs DX Workbench
The LSM Workbench covers the following steps:
Read the legacy data from one or several files (e.g. spreadsheet tables, sequential files).
Convert the data from source format to target format.
Import the data using standard interfaces (Batch Input, Direct Input, BAPI, IDoc).
Experiences made in successful implementation projects have shown that using the LSM Workbench significantly contributes to accelerating data migration.
SAP provides this tool along with documentation to customers and partners free of charge.
Users of the LSM Workbench receive the usual support via SAP Net - R/3 Frontend (component BC-SRV-DX-LSM).
Releases:
Version 1.7.2 of the LSM Workbench ("LSMW 1.7.2") available
Attention : LSMW 1.7.2 requires an SAP R/3 system with SAP R/3 4.0 or SAP R/3 4.5.
Version 1.8.0 of the LSM Workbench (1.21mb) ("LSMW 1.8.0") available
Attention : LSMW 1.8.0 requires an SAP R/3 system with SAP R/3 4.6.
Version 3.0 of the LSM Workbench (1.89mb) ("LSMW 3.0") available for Web Application Server 6.10
Attention : LSMW 3.0 requires a SAP WAS 6.10. Functionality of version 1.7.2 and 3.0 are identical !
Version 4.0 of the LSM Workbench ("LSMW 4.0") integrated in Web Application Server 6.20
Attention : LSMW 4.0 is an integrated part of SAP WAS 6.20.
Thanks & regards
Sreenivasulu P
Message was edited by: Sreenivasulu Ponnadi

Differences between rfc and ale/idoc.

hi ..
       will u please send the differences between rfc and ale/idoc's.

Hi,
Please reward with points if helpful................
ALE is SAP proprietary technology that enables data communications between two or more SAP R/3 systems and/or R/3 and external systems. There are three layers in ALE system: application services, distribution services, and communication services.
For communication services, ALE performs a Remote Function Call (RFC) using the port definition and RFC destination specified by the customer model. RFC is used to communicate between applications of different systems in the SAP environment includes connections between SAP systems as well as between SAP systems and non-SAP systems. Remote Function Call (RFC) is the standard SAP interface for communication between SAP systems. The RFC calls a function to be executed in a remote system.
Means of creating and operating distributed applications.
The purpose of Application Line Enabling is to guarantee a distributed, but integrated, R/3 installation. This involves business-controlled message exchange with consistent data across loosely linked SAP applications.
Application integration is achieved not via a central database, but via synchronous and asynchronous communication.
Application Link Enabling comprises the following three layers:
application services
distribution services
communication services
Two Development Models
     Distribution using BAPIs
     Distribution using Message type
The programming model "Distribution using message types" contains the definitions of message types and IDoc types and the ABAP code for processing inbound and outbound IDocs.
Defining message types and IDoc types:
If you want to create message type enhancements for master data distribution, you also have to create a new message type for each enhancement.
The ALE interface does not allow you to create different segment data for different IDoc types for the same message type.
Writing ABAP code:
         Outbound Processing
           Inbound Processing
You can find information on other ALE functions under:
                               Master Data Distribution
                              Communicating with Non-R/3 Systems
1. The Remote Function Call facility allows you to call an R/3 Function module on a remote machine.
2. To communicate between two R/3 Systems and also with an External System. External Application program also can call these function module for integration.
3. RFC or sRFC - Synchronous RFC
                 aRFC - Asynchronous RFC
                  tRFC - Transactional RFC
                  qRFC - Queued RFC (I.e. Serialization of tRFC)
Types of RFC Call
Synchronous
CALL FUNCTION Func Destination Dest
CALL FUNCTION func DESTINATION 'NONE' ...
CALL FUNCTION func DESTINATION BACK' ...
Asynchronous
CALL FUNCTION func STARTING NEW TASK taskname
PERFORMING form ON END OF TASK
RECEIVE RESULTS FROM FUNCTION func
Thanks
sivaparvathi

What is the difference between rfc and idoc

hi,
My name is rambabu.can anyone of u please tell me the main differences between idoc and rfc??
Thanks in Advance

hi Ramesh,
Remote Function Calls (RFC) and data exchange through IDoc
message documents. RFC makes direct and synchronous calls of a program in
the remote system. If the caller is an external program it will call an
RFC-enabled function in R/3 and if the calling program is the R/3 system
it will call an RFC-function in another R/3-system or it will call a
non-R/3 program through a gateway-proxy (usually rfcexec.exe). BAPIs are
a subset of the RFC-enabled function modules, especially designed as
Application Programming Interface (API) to the SAP business object, or in
other words: are function modules officially released by SAP to be called
from external programs.
IDocs are text encoded documents with a rigid structure that are used to
exchange data between R/3 and a foreign system. Instead of calling a
program in the destination system directly, the data is first packed into
an IDoc and then sent to the receiving system, where it is analyzed and
properly processed. Therefore an IDoc data exchange is always an
asynchronous process. The significant difference between simple RFC-calls
and IDoc data exchange is the fact, that every action performed on IDocs
are protocolled by R/3 and IDocs can be reprocessed if an error occurred
in one of the message steps.
While IDocs have to be understood as a data exchange protocol, EDI and ALE
are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to
deliver data to the receiving system. ALE is basically the scheduling
mechanism that defines when and between which partners and what kind of
data will be exchanged on a regular or event triggered basis. Such a
set-up is called an ALE-scenario.
Regards
Sreeram.G.Reddy

Synchronous and asynchronous mode

Hi all,
when to use synchronous and asynchronous mode in BDC
cheers

Hi Kumar,
Synchronus data processing is that in which the program calling the update task waits for the update work process to finish the update before it continues processing.
In Asynchronus update the callng program does not wait for update work process to finish the update and continues as normal.
A BDC done with sessions is always synchronus.
A BDC with call transaction is by default asynchronus
unless you define it explicitly as
call transaction 'XXXX' ...... update 'S'.
( If you donot define update option it is defaulted to "A" ).
The update method is of importance when one transaction locks data which may be required by a subsequent transaction . The subsequent transaction will fail if data is locked from previous one. An example would be you are creating sales order for same material in succession ( with asynchronus update ). Quite likely that some of transactions would fail due to material locked.
For large volume of data Call Transaction will be faster but you have no restart capability here. Suppose from 1000 transactions 100 fails . You will have to run the BDC program again exclusing the ones which wrere successful. However with session method you have the option to process the error transactions again in SM35 . So if you are sure that errors will not occur use call transaction else use session method.
Please also check this link for differences between call transaction and batch input method
http://help.sap.com/saphelp_47x200/helpdata/en/fa/097015543b11d1898e0000e8322d00/frameset.htm
Hope this will help.
Regards,
Ferry Lianto
Please reward points if helpful.

Difference between sapscripts and BDCs

what is the difference between sapscripts and BDCs

BDC for data communication between sap to non sap(vice-versa)
where scripts is a business layout(we create)
<b>bdc help</b>
They are the only 3 methods mostly we use in BDC.
Call _Dialog is outdated. it is there in the intial stages of SAP.
BDC:
Batch Data Communication (BDC) is the process of transferring data from one SAP System to another SAP system or from a non-SAP system to SAP System.
Features :
BDC is an automatic procedure.
This method is used to transfer large amount of data that is available in electronic medium.
BDC can be used primarily when installing the SAP system and when transferring data from a legacy system (external system).
BDC uses normal transaction codes to transfer data.
Types of BDC :
CLASSICAL BATCH INPUT (Session Method)
CALL TRANSACTION
BATCH INPUT METHOD:
This method is also called as CLASSICAL METHOD.
Features:
Asynchronous processing.
Synchronous Processing in database update.
Transfer data for more than one transaction.
Batch input processing log will be generated.
During processing, no transaction is started until the previous transaction has been written to the database.
CALL TRANSACTION METHOD :
This is another method to transfer data from the legacy system.
Features:
Synchronous processing. The system performs a database commit immediately before and after the CALL TRANSACTION USING statement.
Updating the database can be either synchronous or asynchronous. The program specifies the update type.
Transfer data for a single transaction.
Transfers data for a sequence of dialog screens.
No batch input processing log is generated.
For BDC:
http://myweb.dal.ca/hchinni/sap/bdc_home.htm
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/bdc&
http://www.sap-img.com/abap/learning-bdc-programming.htm
http://www.sapdevelopment.co.uk/bdc/bdchome.htm
http://www.sap-img.com/abap/difference-between-batch-input-and-call-transaction-in-bdc.htm
http://help.sap.com/saphelp_47x200/helpdata/en/69/c250684ba111d189750000e8322d00/frameset.htm
http://www.sapbrain.com/TUTORIALS/TECHNICAL/BDC_tutorial.html
Check these link:
http://www.sap-img.com/abap/difference-between-batch-input-and-call-transaction-in-bdc.htm
http://www.sap-img.com/abap/question-about-bdc-program.htm
http://www.itcserver.com/blog/2006/06/30/batch-input-vs-call-transaction/
http://www.planetsap.com/bdc_main_page.htm
call Transaction or session method ?
These are the Function modules used for the Session Method.
BDC_OPEN_GROUP
BDC_INSERT
BDC_CLOSE_GROUP
BDC_DELETE_SESSION to create a session
You can schedule the execution of BDC session using the program RSBDCSUB.
another one call transaction
open dataset
close dataset
reward if it helps u
vijay pawar

What is the difference between view and materialized views

Hi
What is the difference between view and materialized view ? can we update the base table using views

can we update the base table using viewsYes:
VIEWS
1. an updatable view is one that lets you perform DML on the underlying table
(see Oracle Database Concepts 10g - 5 Schema Objects)
2. non-updatable view requires INSTEAD OF Triggers
(see Oracle Database Concepts 10g - 22 Triggers)
SNAPSHOTS
You can have updateable (and writeable) snapshots - in updateable (writeable) MV replication.
Oracle uses snapshots (Materialized Views - MV) for two different purposes:
1. replication
2. automated Query Rewrite facility (first introduced in Oracle Discoverer, later included in Oracle database 8i).
Replication types in Oracle are:
a) Basic replication (MV replication)
- transaction based
- row-level
- asynchronous from master table to MV (Materialized View)
- DML replication only
- database 7 / 8.0 / 8i / 9i / 10g
- Standard and Enterprise Edition
1. Read-only MV replication
2. Updateable MV replication:
2.1 asynchronous from MV to master
2.2 synchronous from MV to master
3. Writeable MV replication
b) Multimaster replication
- transaction based
- row-level or procedural
- asynchronous or synchronous
- DML and DDL replication
- database 7 / 8.0 / 8i / 9i / 10g
- Enterprise Edition only
1. row-level asynchronous replication
2. row-level synchronous replication
3. procedural asynchronous replication
4. procedural synchronous replication
c) Streams replication
- (redo) log based
- row-level
- asynchronous
- DML and DDL replication
- database 9i / 10g (10g has Down Streams Capture)
- Enterprise Edition only (Standard Edition 10g can execute Apply process)
Regards,
Zlatko Sirotic

Difference between A2A and B2B scenarios.

hi,
i want to know what is difference between A2A and B2B scenarios.
plz give me some examples if possible.
thanks and regards
vijender

Hi VIJENDER SRIRAMOJU ,
SAP XI is an integration technology and platformu2026
u2026for SAP and non-SAP applications.
u2026for A2A and B2B scenarios.
u2026for asynchronous and synchronous communication.
u2026for cross-component Business Process Management.
The following websites wil answer u'r questions :
SAP Exchange Infrastructure: Process-Centric Collaboration
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/ed49db90-0201-0010-c4a5-c520866a19c7
Application to Application scenarios :
Tutorial: Developing XI Content for A2A Processes
http://help.sap.com/saphelp_nw2004s/helpdata/en/66/58934257a5c96ae10000000a155106/content.htm
Business-to-Business Processes:
Enabling Business-to-Business Processes
http://help.sap.com/saphelp_nw2004s/helpdata/en/7a/c76642804a173be10000000a155106/frameset.htm
Standards Required to Support XML-Based B2B Integration
http://xml.coverpages.org/rosettanetStandardsForIntegration.pdf
B2B and Industry Standards Support
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/00bfe190-0201-0010-5cab-b623ca90e746

Difference between synchronous and asynchronous

Similar Messages

Maybe you are looking for