Which is better Synchronous or asynchronous transports

Hi gurus,
I've never got a straight answer on this and would like to understand it better.
What are the pros and cons of Synchronous vs. Asynchronous transports.
Please provide examples on where one mode would be better than the other.
Seems to be something all of us uses everyday and nobody seems to really understand what it's for exactly.
BTW, I know what the text book definition is for those terms. What I would like is to understand when one of them is preferable to the other.
Thanks
Stephane
Edited by: Stephane Lamarche on Oct 27, 2011 9:40 AM

Theoretically, asynchronous mode is better, this is what I think.
For e.g. When I support a small client (fairly new or small business, small landscape, very few number of concurrent users etc.), I move the transports in 'synchronous' mode because I don't care if an 'SAP process' would remain engaged until 'tp OS process' ends, as I have a plenty of 'SAP Processes' available just for my basis activity - to move the transports.
Other way round for bigger clients (more n more number of concurrent users working at a moment).
Depends on the fact whether you are moving the transports in business hours or business off hours too.
This is just one opinion, considering the number of work processes. Other technical opinions are also there I think.
Rest other colleagues will share their thoughts.
Thanks

Similar Messages

  • 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

  • In bdc sessoin method which one is preferred synchronous or asynchronous..?

    hi could anybody tel me
    sessoin method which one is preferred synchronous or asynchronous..?
    what ll happen if we do other method..?
    foreground or background which one ll prefer..?
    what ll happen if we do otehr method..?
    thanx
    kals.

    Dear Kals,
    Synchronous or Asynchronous:
    If you need to process dependent transactions one after the other go for synchronous. Else, go for asynchronous.
    Asynchronous will have better performance.
    Ex:
    If you would like to process F.02. If it is successful process one more transaction using.
    Go for synchronous
    call transaction F.02 ........
    if successful.
       process one more dependent transaction.
    endif.
    If you just need to process F.02
    Go for Asynchronous.
    Background or Foreground:
    If there is a huge volume of data or no manual intevention is needed for background. If you would need manual intervention go for foreground.
    Performance would be better in Background.
    Visit the following thread:
    Re: sap general
    Hope this will help.
    Regards,
    Naveen.

  • In bdc call transaction method which one ll prefer synchronous or asynchron

    hi could anybody tel me
    call transaction method which one is preferred synchronous or asynchronous..?
    what ll happen if we do other method..?
    foreground or background which one ll prefer..?
    what ll happen if we do otehr method..?
    on which condition we have to use synchronous and asynchronous
    on which condition we have to use foreground and background
    thanx
    kals.

    Hi,
    if you haven't done yet please visit for general information:
    http://help.sap.com/saphelp_nw70/helpdata/en/d2/f8f3393bef4604e10000000a11402f/frameset.htm
    for further information:
    http://help.sap.com/saphelp_nw70/helpdata/en/69/c2501a4ba111d189750000e8322d00/frameset.htm
    This will hopefully answer your question.
    Regards
    Bernd

  • When in transport, which is better have the MBP shut down or sleep mode?

    when in transport, which is better have the MBP shut down or in sleep mode?

    Read the user manual that came w/your computer.  Personally, I shut down when transporting.  
    It all comes down to personal preference.  "Different Strokes For Different Folks"

  • In session and call tansaction methods, which is better . why?

    hi
    in session and call tansaction methods, which is better . why?

    see the link:
    <a href="http://www.itcserver.com/blog/2006/06/30/batch-input-vs-call-transaction/">batch inpunt VS call transaction</a>
    "The most important aspects of the session interface are:
    <b>Asynchronous processing</b>
    Transfer data for multiple transactions
    Synchronous database update. During processing, no transaction is started until the previous transaction has been written to the database.
    A batch input processing log is generated for each session
    Sessions cannot be generated in parallel. The batch input program must not open a session until it has closed the preceding session.
    The most important features of CALL TRANSACTION USING are:
    <b>Synchronous processing</b>
    Transfer of data from an individual transaction each time the statement CALL TRANSACTION USING is called
    You can update the database both synchronously and asynchronously. The program specifies the update type.
    Separate LUW (Logical Units of Work) for the transaction. The system executes a database commit immediately before and after the CALL TRANSACTION USING statement.
    No batch input processing log"
    I hope I have been able to help you.
    cordial greetings.

  • User exits-- also ---synchronous and asynchronous struc..

    dear all
    pls. let me know the basics of user exits. i have gone thro williams iam unable to follow. does it require abap knowledge. i sincerely request one and all (experts) to let me know about user exits. it seems very imp as per interviews.
    also what is synchronous and asynchronous structures whats the difference. can anybody share knowledge on this.
    thanks in advance
    regards

    Dear Sekhar,
    Please find the info regarding User-Exit's in the following links:
    http://help.sap.com/saphelp_nw04/helpdata/en/bf/ec07a25db911d295ae0000e82de14a/frameset.htm
    http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
    Re: doubt on user exits
    user exits and Badis
    User exits is the enhancements provided by SAP
    You can use them in transactions. Each transaction will have user exits.
    If you want to use your own requirements by making your coding while the transaction is run you can use user exits.
    For example if you want to run the MRP in MD02 specific to MRP controller you can user exit.
    Please also refer the document below.
    USEREXIT
    Userxits allow us to add our own functionality to SAP standard program
    without modifying it . These are implemented in the form of subroutines and hence are also known as FORM EXITs. The userexits are generally collected in includes and attached to the standard program by the SAP.
    All Userexits start with the word USEREXIT_...
    FORM USEREXIT_..
    z..
    ENDFORM.
    The problem lies in finding the correct userexit and how to find it if one exists for the purpose. Once the correct userexit is found the necessary customer code is inserted in the customer include starting with the z.. in the form routine.
    e.g. USEREXIT_SAVE_DOCUMENT_PREPARE
    Certain application like SD still provide this form of enhancement using userexit but this practice is no longer being followed for newer extensions instead they are using EXITs which come bundeled in enhancement packages . Neverthiless existing USEREXITS will be supported by SAP an all the newer versions of SAP.
    HOW TO FIND USEREXITS
    Userexits can be found in number of ways:
    1) To find userexits in SD module , goto object navigator(SE80) and select
    development class from the list and enter VMOD in it. All of the userexits in SD are contained in the development class VMOD. Press enter and you will find all the includes which contain userexits in SD for different functions like PRICING, ORDER PROCESSING etc. Select the userexit according to the requirement and read the comment inserted in it and start coding .
    Some examples of userexits in SD(SALES & DISTRIBUTION ) are:
    1)ADDING OF NEW FIELDS IN PRICING
    In Pricing in SD the fields on the basis of which pricing is done are derived from the FIELD CATALOG which is a structure KOMG .This structure is used to transfer transaction data to the pricing procedure in SD and is also known as communication structure.This structure KOMG consists of two tables KOMK for Header related fields and KOMP for item related fields. The fields which are not in either of the two tables KOMK and KOMP cannot be used in pricing .Sometimes a need arises when the pricing is to be based on some other criteria which is not present in the form of fields in either of the two tables. This problem can be solved by using USEREXITS which are provided for pricing in SD. Pricing takes place both when the SALES ORDER ( Transaction VA01) is created as well as when INVOICING ( Transaction VF01) is done.Hence SAP provides 2 userexits ,one for sales order processing which is
    USEREXIT_PRICING_PREPARE_TKOMP or
    USEREXIT_PRICING_PREPARE_TKOMK
    Depending upon which table (KOMK or KOMP) the new fields were inserted we use either of the above two userexits.These userexits are found in include MV45AFZZ of the standard SAP sales order creation program SAPMV45A.
    In the case of userexit which will be called when invoicing is done ,these
    are provided in the include RY60AFZZ which is in the standard SAP program SAPMV45A. The name of the userexits are same. i.e
    USEREXIT_PRICING_PREPARE_TKOMP or
    USEREXIT_PRICING_PREPARE_TKOMK
    These userexits are used for passing the data from the communication structure to the pricing procedure, for this we have to fill the newely created field in the communication structure KOMG for this we fill the code in the above userexit using the MOVE statement after the data that has to be passed is taken from the database table by using the SELECT statement. The actual structure which is visible in these userexits and which is to be filled for that particular field is TKOMP or TKOMK.
    Before the coding for these userexits is done ,it is necessary to create a new field in either of the two tables KOMK or KOMP .For this purpose includes are provided in each of them .
    To create the field in header data(KOMK) the include provided is KOMKAZ
    and to create the field in item data(KOMP) the include provided is KOMPAZ.
    One possible example for the need of creating new fields can be e.g. Frieght to be based upon transportation zone ,for this no field is available in field catalog and hence it can be created in KOMK and then above userexits can be used to fill the transportation data to it.
    2)The other method of finding userexit is to find the word USEREXIT in the
    associated program of the transaction for which we want to determine userexit using SE38.
    3)The other method of finding userexits is to find the include in case of SD/MM applications where the userexits are located ,this can be found in the SAP reference IMG generally in the subfolder under SYSTEM MODIFICATION.
    Some other examples of userexits in SD are:
    USEREXIT_NUMBER_RANGE
    This userexit is used to assign a different internal document number to the
    sales order(VA01) when it is created depending on some criteria like a different SALES ORGANIZAION(VKORG) .
    USEREXIT_SAVE_DOCUMENT_PREPARE
    This userexit is used to insert the ABAP code which will be called when
    the document (sales order VA01) is just about to be saved.This userexit is used generally for custom checks on different fields , to display some information before the order will be saved or for making changes to certain fields before the sales order will be saved.
    Exits & Enhancements
    There are mainly six types of EXITs in sap which have been collected in the form of enhancement packages and attached to standard code in SAP.
    These are different from USEREXIT in the way that they are implemented
    in the form of FUNCTIONs while in USEREXITS we use form routines for their implementation. These are also sometimes known as function exits .
    These start from the word EXIT_ followed by the program name and then followed by a three digit number.
    e.g. EXIT_SAPMV45A_002
    This exit is found in SD in enhancement V45A0002.
    TYPES OF EXITS
    1)MENU EXITS
    2)FUNCTION EXITS
    3)TABLE EXITS
    4)SCREEN EXITS
    5)KEYWORD EXITS
    6)FIELD EXITS
    We use SAP transactions CMOD and SMOD to manage exits. Before implementing an exit , it is required to create the project by using CMOD
    selecting the enhancement e.g. V45A0002 and selecting the component
    (one which fulfills our need) i.e the exit which will be implemented in SMOD and after coding has been done the project has to be activated.
    An exit can be coded only once.
    FUNCTION EXITS
    These are used to add functionality through ABAP code . These start from the word EXIT_programname_NNN ending in a 3 digit number. No access code is required to implement any tupe of exit including function exits.
    The function exits are called from the standard SAP program in the form
    of ABAP statement
    CALL CUSTOMER-FUNCTION 'NNN'
    This is in contrast to USEREXITs where PERFORM statement is used to call
    the required userexit.
    To implement the FUNCTION EXITs first of all the project is created and a suitable enhancement package is selected and from its compnents the function exit to be implemented is selected and on double clicking it the exit code will appear in ABAP EDITOR(se38) where a Z include will be found and the customer code should be entered in this include.
    e.g.
    ADDING A DEFAULT SOLD-TO-PARTY in Sales Order Creation
    To show a default sold-to-party in this field when the user creates a sales order (VA01) we can use a function exit .This function exit is located in enhancement no V45A0002 . Before we can choose the exit we have to create a project in CMOD after that enter V45A0002 in the enhancement field and click on the components . In the components you will see the exit EXIT_SAPMV45A_002 . This exit is used for our purpose.
    Double clicking on this exit will takes us to function builder (SE37) . This
    function exit has one exporting parameters and two importing parameters, we are interested in exporting parameter which is E_KUNNR of type KNA1-KUNNR i.e if we move the desired customer name to this structure(E_KUNNR) it will be shown in the field as the default value when we create the sales order. This function also contains a customer include ZXVVA04 . This include will be used to write our custom code .
    Double clicking on this include and it will prompt us that this include does not exists do you want to create this object ,select yes and the include will be created .In this include we can write our own code that will fill the field E_KUNNR.
    e.g. E_KUNNR = 301.
    Activate the include and Activate the project. Now when ever the SALES ORDER will be created , sold-to-party field will come up with a predefined customer .
    FIELD EXITS
    The field exits are managed,created,activated through program RSMODPRF. The field exit is associated with a data element existing in ABAP dictionary and hence to the screen field using that data element.
    The format of field exit is :
    FIELD_EXIT_dataelement_A-Z or 0-9
    If a particular screen and program name is not specified than the field exit will effect all the screens containing that data element.
    The function module associated with field exit shows two parameters
    INPUT and OUTPUT. Input parameter contains the data passed to the field exit when the field exit was invoked by the R/3 , We can write our own code to change the output parameter depending upon our requirements.
    Before the field exit can have any effect the system profile parameter
    ABAP/FIELDEXIT in all the application servers should be set to YES
    ABAP/FIELDEXIT = YES.
    Regards
    Naveen.

  • 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)

  • Synchronous and Asynchronous streams

    Hey,
    I have an application middle ware that communicates with (a local or alternatively remote ) backend via streams. Atleast that is how I am planning it right now. Nothing implemented yet, only thinking over the design. There is a requirement of communication between the middleware and the backend to have synchronous or asynchronous msgs.
    The synchronous msgs I get. I send a msg and keep the stream listening for a reponse. But some msgs can be asynchronous, if I ask the stream to listen for them that will pull out all resources. What would be the solution for such asynchronous msgs.
    So is this a solution to the problem that I have a single stream (wrapped in a thread), it sends msgs, irrespective of the knowledge whether the response will be syn. or asyn. , and it sleeps after doing so. A question here would be that : Are the wait() methods of streams to this effect that I desire. Is this the solution. Would it pull resources or something.
    Is there a better solution that someone knows off.

    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.

  • Synchronous and asynchronous transformations in SSIS

    Hi Can someone pls tell, when and in what scenarios it is better to use synchronous and asynchronous transformations in SSIS. And what are the pros and cons of using transformations that falls under above mentioned category.

    A good and well documented resource is available at Technet Library which will determine better about your concern. Please check this :
    http://technet.microsoft.com/en-us/library/aa337074.aspx

  • Which is better  option SAP XI vs webservices to interact with Biztalk

    HI everyone,
    We have biztalk as integration tool. I would like to know is it feasible to implement Biztalk with SAP XI to communicate with our SAP ECC server. I heard it will be over weight to use both Biztalk and SAP XI coz each will have its own message box and leads to more process time. So we are planning to use Biztalk with SAP webservices. So please let me know which is better as cost wise and work wise biztalk with SAP XI or Biztalk with SAP Web services.
    SAP Guys please take some time to provide some useful information. it will be much appreciated.
    cheers
    ram

    SAP XI and BizTalk both offer a tight integration of Web Services into the engine and development tools. Using the SAP XI SOAP Adapter enables the consumption and publication of Web Services based on the SOAP 1.1 protocol according to the WS-Basic Profile 1.0.
    The BizTalk SOAP Adapter also offers Web Services support based on SOAP 1.1
    support and Basic Profile 1.0 capabilities.
    Anyway XI and Biztalk can interoperate, you should evaluate the scenario you are going to implement.
    Based on transactionality, trhroughtput, communication etc, the following scenarios are in focus:
    Synchronous and non-transactional communication
    Synchronous and transactional communication
    Asynchronous and non-transactional communication
    Asynchronous and transactional communication
    This leads to eight scenarios overall, as both hubs may act as the initiating starting point of the communication. The choice of communication types for a certain integration process depends on business needs, technical needs and performance considerations.
    if it may be useful rewards point are appreciated

  • Synchronous and asynchronous processes communication in WLI 8.1

    Hi all,
    I'm using workshop with WL 8.1 to design by business processes.
    I have created one process which is invoked synchronously via a client request
    with return.
    Than I call this process in web flow. The process publishes message in the MB,
    which creates
    another process asynchronously. My question is how can I communicate
    from the first process with the second one ? e.g. In some cases I need to wait
    when the second
    process riches some state, or e.g. how to check if the everything’s went ok in
    the second one ?
    I tried to manage it by another MB channel, but when I add the proper controls
    to first process
    it becomes asynchronous and I can not use such process in the flow (there is no
    way to handle
    callback methods in the flow) and I need to have return somehow.
    Do you have any suggestion how to design (or redesign) my workflow ?
    Best regards
    Jan

    "Jan Mrzyglod" <[email protected]> wrote in message
    news:[email protected]...
    >
    Hi all,
    I'm using workshop with WL 8.1 to design by business processes.
    I have created one process which is invoked synchronously via a clientrequest
    with return.That's fine so far.
    Than I call this process in web flow. The process publishes message in theMB,
    which creates
    another process asynchronously. My question is how can I communicate
    from the first process with the second one ? e.g. In some cases I need towait
    when the second
    process riches some state, or e.g. how to check if the everything's wentok in
    the second one ?Communicating between JPD processes is preferably done with Process Controls
    (Add Control / Integration Control / Process). A Process control needs a jcx
    file belonging to a process. To generate a Process Control jcx file to a
    process, click right on the JPD file in the project tree, and select
    Generate Process Control.
    If the page-flow calling on the first process also has to wait for the
    second process to reach some state, then you need to have
    synchronous invocation between the first and the second process.
    That can be done only with adding a message path to the start node of the
    second process (the circle), and putting a Client Request with Return in it.
    Everything in the Client Request with Return node is invoked synchronously,
    meaning that the first process will wait for the return, and gets the return
    value, and receives any exceptions thrown and everything takes place in the
    same transaction. However this way you have no modelling information on
    where the process flow currently is, so you have to keep track of that in a
    variable in the JPD, if you need to know that.
    You also have to put at least one stateful (waiting) node to the normal
    process flow, so that the process does not terminate right after starting
    (Workshop warns about this as well).
    Now regenerate the process control jcx for the second process, and you will
    see a method on it belonging to the message path Client Request with Return.
    This can be invoked synchronously on the process control in the first
    process.
    I presume however, that you are aware of the fact, that the HTTP request can
    time out, and in that case I am not sure, whether additional steps in the
    page flow are evaluated or not. Possibly not. Typically I would expect, that
    forwards and includes do not.
    Regards,
    Robert Varga

  • Which is better, many PXI cards or fewer PXI cards with more SCXI cards?

    I have a pretty basic question.  Which is "better", using multiple PXI cards for analog inputs or a single PXI card and multiple SCXI cards?  For example, if I have say 100 channels to sample (all at the same rate), I could use 2 6225s at 80 ch each.  Or I could use 1 6220 and 4 SCXI 1100s (32 ch each).  What are the pros and cons with either approach?  Keep in mind sample rate probably isn't an issue (less than 1 kHz) but it is the same for all channels.
    Thanks.

    The pros/cons will depend on your application now and in the future.  I recommend contacting your local NI sales representative.  Synchronizing across a PXI system is easy to do via the backplane.  There are PXI/SCXI combo chassis available, you could use PXI multifunction DAQ cards and then SCC for signal conditioning for thermocouples for additional functionality later.  There are many possibilities that may be best discussed with your sales representative.
    Regards,
    h_baker
    National Instruments
    Applications Engineer
    Digital Multimeter Resources

  • Which is better, Double Buffering 1, or Double Buffering 2??

    Hi,
    I came across a book that uses a completely different approach to double buffering. I use this method:
    private Graphics dbg;
    private Image dbImage;
    public void update() {
      if (dbImage == null) {
        dbImage = createImage(this.getSize().width, this.getSize().height);
        dbg = dbImage.getGraphics();
      dbg.setColor(this.getBackground());
      dbg.fillRect(0, 0, this.getSize().width, this.getSize().height);
      dbg.setColor(this.getForeground());
      paint(dbg);
      g.drawImage(dbImage, 0, 0, this);
    }that was my method for double buffering, and this is the books method:
    import java.awt.*;
    public class DB extends Canvas {
         private Image[] backing = new Image[2];
         private int imageToDraw = 0;
         private int imageNotDraw = 1;
         public void update(Graphics g) {
              paint(g);
         public synchronized void paint(Graphics g) {
              g.drawImage(backing[imageToDraw], 0, 0, this);
         public void addNotify() {
              super.addNotify();
              backing[0] = createImage(400, 400);
              backing[1] = createImage(400, 400);
              setSize(400, 400);
              new Thread(
                   new Runnable() {
                        private int direction = 1;
                        private int position = 0;
                        public void run() {
                             while (true) {
                                  try {
                                       Thread.sleep(10);
                                  }catch (InterruptedException ex) {
                                  Graphics g = backing[imageNotDraw].getGraphics();
                                  g.clearRect(0, 0, 400, 400);
                                                    g.setColor(Color.black);
                                  g.drawOval(position, 200 - position, 400 - (2 * position), 72 * position);
                                  synchronized (DB.this) {
                                       int temp = imageNotDraw;
                                       imageNotDraw = imageToDraw;
                                       imageToDraw = temp;
                                  position += direction;
                                  if (position > 199) {
                                       direction = -1;
                                  }else if (position < 1) {
                                       direction = 1;
                                  repaint();
              ).start();
         public static void main(String args[]) {
              Frame f = new Frame("Double Buffering");
              f.add(new DB(), BorderLayout.CENTER);
              f.pack();
              f.show();
    }which is better? I noticed smoother animation with the later method.
    Is there no difference? Or is it just a figment of my imagination??

    To be fair if you download an applet all the class files are stored in your .jpi_cache, and depending on how that game requests its graphics sometimes they are stored there to, so really if you have to download an applet game twice, blame the programmer (I've probably got that dead wrong :B ).
    But, what's wrong with Jars. They offer so much more.
    No offence meant by this Malohkan but if you can't organize your downloaded files the internet must really be a landmine for you :)
    Personally I'd be happy if I never seen another applet again, it seems java is tied to this legacy, and to the average computer user it seems that is all java is capable of.
    Admitidly there are some very funky applets out here using lots of way over my head funky pixel tricks, but they would look so much better running full screen and offline.

  • 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.

Maybe you are looking for