Skip to Content
author's profile photo Former Member
Former Member


difference between session and call transaction?

thanks in advance

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

3 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Jan 29, 2008 at 08:28 AM



    1) The Session method agenerates a log.

    2) we can use call trasaction to update in Synchronous and

    Asynchronous modes. But in session database updation is always syncronous.

    we guarantee the database integrity in session method.

    3)session method run in background mode.

    If we have data with less no.of error records we go for session method.Otherwise we go for Call transaction method.

    4) using Call transaction we need to interact three servers,

    presentation , application and production. But with using

    session method these three servers not required.

    If it is hepful rewards points.



    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jan 29, 2008 at 08:39 AM


    check this.


    About Data Transfer In R/3 System

    When a company decides to implement the SAP R/3 to manage business-critical data, it usually does not start from a no-data situation. Normally, a SAP R/3 project comes into replace or complement existing application.

    In the process of replacing current applications and transferring application data, two situations might occur:

    • The first is when application data to be replaced is transferred at once, and only once.

    • The second situation is to transfer data periodically from external systems to SAP and vice versa.

    • There is a period of time when information has to be transferred from existing application, to SAP R/3, and often this process will be repetitive.

    The SAP system offers two primary methods for transferring data into SAP systems. From non-SAP systems or legacy system. These two methods are collectively called “batch input” or “batch data communication”.




    Advantages offered by BATCH INPUT method:

    1. Can process large data volumes in batch.

    2. Can be planned and submitted in the background.

    3. No manual interaction is required when data is transferred.

    4. Data integrity is maintained as whatever data is transferred to the table is through transaction. Hence batch input data is submitted to all the checks and validations.

    To implement one of the supported data transfers, you must often write the program that exports the data from your non-SAP system. This program, known as a “data transfer” program must map the data from the external system into the data structure required by the SAP batch input program.

    The batch input program must build all of the input to execute the SAP transaction.

    Two main steps are required:

    • To build an internal table containing every screen and every field to be filled in during the execution of an SAP transaction.

    • To pass the table to SAP for processing.

    Prerequisite for Data Transfer Program

    Writing a Data Transfer Program involves following prerequisites:

    Analyzing data from local file

    Analyzing transaction

    Analyzing transaction involves following steps:

    • The transaction code, if you do not already know it.

    • Which fields require input i.e., mandatory.

    • Which fields can you allow to default to standard values.

    • The names, types, and lengths of the fields that are used by a transaction.

    • Screen number and Name of module pool program behind a particular transaction.

    To analyze a transaction::

    • Start the transaction by menu or by entering the transaction code in the command box.

    (You can determine the transaction name by choosing System – Status.)

    • Step through the transaction, entering the data will be required for processing your batch input data.

    • On each screen, note the program name and screen (dynpro) number.

    (dynpro = dyn + pro. Dyn = screen, pro = number)

    • Display these by choosing System – Status. The relevant fields are Program (dynpro) and Dynpro number. If pop-up windows occur during execution, you can get the program name and screen number by pressing F1 on any field or button on the screen.

    The technical info pop-up shows not only the field information but also the program and screen.

    • For each field, check box, and radio button on each screen, press F1 (help) and then choose Technical Info.

    Note the following information:

    - The field name for batch input, which you’ll find in its own box.

    - The length and data type of the field. You can display this information by double clicking on the Data Element field.

    • Find out the identification code for each function (button or menu) that you must execute to process the batch-input data (or to go to new screen).

    Place the cursor on the button or menu entry while holding down the left mouse button. Then press F1.

    In the pop-up window that follows, choose Technical info and note the code that is shown in the Function field.

    You can also run any function that is assigned to a function key by way of the function key number. To display the list of available function keys, click on the right mouse button. Note the key number that is assigned to the functions you want to run.

    Once you have program name, screen number, field name (screen field name), you can start writing.

    DATA TRANSFER program.

    Declaring internal table

    First Integral Table similar to structure like local file.

    Declaring internal table like BDCDATA

    The data from internal table is not transferred directly to database table, it has to go through transaction. You need to pass data to particular screen and to particular screen-field. Data is passed to transaction in particular format, hence there is a need for batch input structure.

    The batch input structure stores the data that is to be entered into SAP system and the actions that are necessary to process the data. The batch input structure is used by all of the batch input methods. You can use the same structure for all types of batch input, regardless of whether you are creating a session in the batch input queue or using CALL TRANSACTION.

    This structure is BDCDATA, which can contain the batch input data for only a single run of a transaction. The typical processing loop in a program is as follows:

    • Create a BDCDATA structure

    • Write the structure out to a session or process it with CALL TRANSACTION USING; and then

    • Create a BDCDATA structure for the next transaction that is to be processed.

    Within a BDCDATA structure, organize the data of screens in a transaction. Each screen that is processed in the course of a transaction must be identified with a BDCDATA record. This record uses the Program, Dynpro, and Dynbegin fields of the structure.

    The screen identifier record is followed by a separate BDCDATA record for each value, to be entered into a field. These records use the FNAM and FVAL fields of the BDCDATA structure. Values to be entered in a field can be any of the following:

    • Data that is entered into screen fields.

    • Function codes that are entered into the command field. Such function codes execute functions in a transaction, such as Save or Enter.

    The BDCDATA structure contains the following fields:

    • PROGRAM: Name of module pool program associated with the screen. Set this field only for the first record for the screen.

    • DYNPRO: Screen Number. Set this field only in the first record for the screen.

    • DYNBEGIN: Indicates the first record for the screen. Set this field to X, only for the first record for the screen. (Reset to ‘ ‘ (blank) for all other records.)

    • FNAM: Field Name. The FNAM field is not case-sensitive.

    • FVAL: Value for the field named in FNAM. The FVAL field is case-sensitive. Values assigned to this field are always padded on the right, if they are less than 132 characters. Values must be in character format.

    Transferring data from local file to internal table

    Data is uploaded to internal table by UPLOAD of WS_UPLOAD function.

    Population of BDCDATA

    For each record of internal table, you need to populate Internal table, which is similar to BDCDATA structure.

    All these five initial steps are necessary for any type of BDC interface.

    DATA TRANSFER program can call SESSION METHOD or CALL TRANSACTION. The initial steps for both the methods are same.

    First step for both the methods is to upload the data to internal table. From Internal Table, the data is transferred to database table by two ways i.e., Session method and Call transaction.


    About Session method

    In this method you transfer data from internal table to database table through sessions.

    In this method, an ABAP/4 program reads the external data that is to be entered in the SAP System and stores the data in session. A session stores the actions that are required to enter your data using normal SAP transaction i.e., Data is transferred to session which in turn transfers data to database table.

    Session is intermediate step between internal table and database table. Data along with its action is stored in session i.e., data for screen fields, to which screen it is passed, the program name behind it, and how the next screen is processed.

    When the program has finished generating the session, you can run the session to execute the SAP transactions in it. You can either explicitly start and monitor a session or have the session run in the background processing system.

    Unless session is processed, the data is not transferred to database table.


    You create the session through program by BDC_OPEN_GROUP function.

    Parameters to this function are:

    • User Name: User name

    • Group: Name of the session

    • Lock Date: The date on which you want to process the session.

    • Keep: This parameter is passed as ‘X’ when you want to retain session after

    processing it or ‘ ‘ to delete it after processing.


    This function creates the session & data is transferred to Session.

    Parameters to this function are:

    • Tcode: Transaction Name

    • Dynprotab: BDC Data


    This function closes the BDC Group. No Parameters.

    Some additional information for session processing

    When the session is generated using the KEEP option within the BDC_OPEN_GROUP, the system always keeps the sessions in the queue, whether it has been processed successfully or not.

    However, if the session is processed, you have to delete it manually. When session processing is completed successfully while KEEP option was not set, it will be removed automatically from the session queue. Log is not removed for that session.

    If the batch-input session is terminated with errors, then it appears in the list of INCORRECT session and it can be processed again. To correct incorrect session, you can analyze the session. The Analysis function allows to determine which screen and value has produced the error. If you find small errors in data, you can correct them interactively, otherwise you need to modify batch input program, which has generated the session or many times even the data file.



    A technique similar to SESSION method, while batch input is a two-step procedure, Call Transaction does both steps online, one after the other. In this method, you call a transaction from your program by

    Call transaction <tcode> using <BDCTAB>

    Mode <A/N/E>

    Update <S/A>

    Messages into <MSGTAB>.

    Parameter – 1 is transaction code.

    Parameter – 2 is name of BDCTAB table.

    Parameter – 3 here you are specifying mode in which you execute transaction

    A is all screen mode. All the screen of transaction are displayed.

    N is no screen mode. No screen is displayed when you execute the transaction.

    E is error screen. Only those screens are displayed wherein you have error record.

    Parameter – 4 here you are specifying update type by which database table is updated.

    S is for Synchronous update in which if you change data of one table then all the related Tables gets updated. And sy-subrc is returned i.e., sy-subrc is returned for once and all.

    A is for Asynchronous update. When you change data of one table, the sy-subrc is returned. And then updating of other affected tables takes place. So if system fails to update other tables, still sy-subrc returned is 0 (i.e., when first table gets updated).

    Parameter – 5 when you update database table, operation is either successful or unsuccessful or operation is successful with some warning. These messages are stored in internal table, which you specify along with MESSAGE statement. This internal table should be declared like BDCMSGCOLL, a structure available in ABAP/4. It contains the following fields:

    1. Tcode: Transaction code

    2. Dyname: Batch point module name

    3. Dynumb: Batch input Dyn number

    4. Msgtyp: Batch input message type (A/E/W/I/S)

    5. Msgspra: Batch input Lang, id of message

    6. Msgid: Message id

    7. MsgvN: Message variables (N = 1 - 4)

    For each entry, which is updated in database, table message is available in BDCMSGCOLL. As BDCMSGCOLL is structure, you need to declare a internal table which can contain multiple records (unlike structure).

    Steps for CALL TRANSACTION method

    1. Internal table for the data (structure similar to your local file)

    2. BDCTAB like BDCDATA

    3. UPLOAD or WS_UPLOAD function to upload the data from local file to itab. (Considering file is local file)

    4. Loop at itab.

    Populate BDCTAB table.

    Call transaction <tcode> using <BDCTAB>

    Mode <A/N/E>

    Update <S/A>.

    Refresh BDCTAB.


    (To populate BDCTAB, You need to transfer each and every field)

    The major differences between Session method and Call transaction are as follows:


    1. Data is not updated in database table unless Session is processed. Immediate updation in database table.

    2. No sy-subrc is returned. Sy-subrc is returned.

    3. Error log is created for error records. Errors need to be handled explicitly

    4. Updation in database table is always synchronous Updation in database table can be synchronous Or Asynchronous.

    Error Handling in CALL TRANSACTION

    When Session Method updates the records in database table, error records are stored in the log file. In Call transaction there is no such log file available and error record is lost unless handled. Usually you need to give report of all the error records i.e., records which are not inserted or updated in the database table. This can be done by the following method:

    Steps for the error handling in CALL TRANSACTION

    1. Internal table for the data (structure similar to your local file)

    2. BDCTAB like BDCDATA

    3. Internal table BDCMSG like BDCMSGCOLL

    4. Internal table similar to Ist internal table

    (Third and fourth steps are for error handling)

    5. UPLOAD or WS_UPLOAD function to upload the data from the local file to itab. (Considering file is local file)

    6. Loop at itab.

    Populate BDCTAB table.

    Call transaction <tr.code> using <Bdctab>

    Mode <A/N/E>

    Update <S/A>

    Messages <BDCMSG>.

    Perform check.

    Refresh BDCTAB.


    7 Form check.

    IF sy-subrc <> 0. (Call transaction returns the sy-subrc if updating is not successful).

    Call function Format_message.

    (This function is called to store the message given by system and to display it along with record)

    Append itab2.

    Display the record and message.


    About Direct Input

    In contrast to batch input, this technique does not create sessions, but stores the data directly. It does not simulate the online transaction. To enter the data into the corresponding database tables directly, the system calls a number of function modules that execute any necessary checks. In case of errors, the direct input technique provides a restart mechanism. However, to be able to activate the restart mechanism, direct input programs must be executed in the background only. Direct input checks the data thoroughly and then updates the database directly.

    You can start a Direct Input program in two ways;

    Start the program directly

    This is the quickest way to see if the program works with your flat file. This option is possible with all direct input programs. If the program ends abnormally, you will not have any logs telling you what has or has not been posted. To minimize the chance of this happening, always use the check file option for the first run with your flat file. This allows you to detect format errors before transfer.

    Starting the program via the DI administration transaction

    This transaction restarts the processing, if the data transfer program aborts. Since DI document are immediately posted into the SAP D/B, the restart option prevents the duplicate document posting that occurs during a program restart (i.e., without adjusting your flat file).

    Direct input is usually done for standard data like material master, FI accounting document, SD sales order and Classification for which SAP has provided standard programs.

    First time you work with the Direct Input administration program, you will need to do some preparation before you can transfer data:

    - Create variant

    - Define job

    - Start job

    - Restart job

    Common batch input errors

    - The batch input BDCDATA structure tries to assign values to fields which do not exist in the current transaction screen.

    - The screen in the BDCDATA structure does not match the right sequence, or an intermediate screen is missing.

    - On exceptional occasions, the logic flow of batch input session does not exactly match that of manual online processing. Testing the sessions online can discover by this.

    - The BDCDATA structure contains fields, which are longer than the actual definition.

    - Authorization problems.


    A B recording allows you to record a R/3 transaction and generate a program that contains all screens and field information in the required BDC-DATA format.

    You can either use SHDB transaction for recording or


    And from here click recording.

    Enter name for the recording.

    (Dates are optional)

    Click recording.

    Enter transaction code.


    Click Save button.

    You finally come to a screen where, you have all the information for each screen including BDC_OKCODE.

    • Click Get Transaction.

    • Return to BI.

    • Click overview.

    • Position the cursor on the just recorded entry and click generate program.

    • Enter program name.

    • Click enter

    The program is generated for the particular transaction.


    Need for Background processing

    When a large volume of data is involved, usually all batch inputs are done in background.

    The R/3 system includes functions that allow users to work non-interactively or offline. The background processing systems handle these functions.

    Non-interactively means that instead of executing the ABAP/4 programs and waiting for an answer, user can submit those programs for execution at a more convenient planned time.

    There are several reasons to submit programs for background execution.

    • The maximum time allowed for online execution should not exceed 300 seconds. User gets TIMEOUT error and an aborted transaction, if time for execution exceeds 300 seconds. To avoid these types of error, you can submit jobs for background processing.

    • You can use the system while your program is executing.

    This does not mean that interactive or online work is not useful. Both type of processing have their own purposes. Online work is the most common one entering business data, displaying information, printing small reports, managing the system and so on. Background jobs are mainly used for the following tasks; to process large amount of data, to execute periodic jobs without human intervention, to run program at a more convenient, planned time other than during normal working hours i.e., Nights or weekends.

    The transaction for background processing is SM36.


    Tools ? Administration ? Jobs ? Define jobs


    System ? services ? Jobs

    Components of the background jobs

    A job in Background processing is a series of steps that can be scheduled and step is a program for background processing.

    • Job name. Define the name of assigned to the job. It identifies the job. You can specify up to 32 characters for the name.

    • Job class. Indicates the type of background processing priority assigned to the job.

    The job class determines the priority of a job. The background system admits three types of job classes: A B & C, which correspond to job priority.

    • Job steps. Parameters to be passed for this screen are as follows:

    Program name.

    Variant if it is report program

    Start criteria for the job: Option available for this are as follows:

    Immediate - allows you to start a job immediately.

    Date/Time - allows you to start a job at a specific name.

    After job - you can start a job after a particular job.

    After event - allows you to start a job after a particular event.

    At operation mode - allows you to start a job when the system switches to a particular operation mode.

    Defining Background jobs

    It is two step process: Firstly, you define the job and then release it.

    When users define a job and save it, they are actually scheduling the report i.e., specifying the job components, the steps, the start time.

    When users schedule program for background processing, they are instructing the system to execute an ABAP/4 report or an external program in the background. Scheduled jobs are not executed until they are released. When jobs are released, they are sent for execution to the background processing system at the specified start time. Both scheduling and releasing of jobs require authorizations.


    Many times in transaction pop up screen appears and for this screen you don’t pass any record but some indication to system telling it to proceed further. For example: The following screen

    To handle such screen, system has provided a variable called BDC_CURSOR. You pass this variable to BDCDATA and process the screen.

    Usually such screen appears in many transactions, in this case you are just passing information, that YES you want to save the information, that means YES should be clicked. So you are transferring this information to BDCDATA i.e., field name of YES which is usually SPOT_OPTION. Instead of BDC_OKCODE, you are passing BDC_CURSOR.

    BDC_CURSOR is also used to place cursor on particular field.


    Following program demonstrates how data is passed from flat file to SAP transaction and further to database table by using SESSION method.

    The transaction is TFBA (to change customer).

    A simple transaction where you are entering customer number on first screen and on next screen data is displayed for the particular customer number. Field, which we are changing here, are name and city. When you click on save, the changed record gets saved.

    Prerequisite to write this BDC interface as indicated earlier is:

    1. To find screen number

    2. To find screen field names, type of the field and length of the field.

    3. To find BDC_OKCODE for each screen

    4. Create flat file.

    Flat file can be created in your hard disk as follows:

    1 Vinod Hyderabad

    2 Kavitha Secunderabad

    3 Kishore Hyderabad

    (Where 1st character field is Customer number, 2nd field is Customer name and 3rd field is City.)

    To transfer this data to database table SCUSTOM following interface can be used.


    • Following internal table is to upload flat file.






    *Following internal table BDCDATA is to pass date from internal table to session.


    • Variables

    DATA: DATE1 LIKE SY-DATUM. DATE1 = SY-DATUM - 1. “ This is for Hold Date

    • To upload flat file to internal table.











    NO_BATCH = 4


    OTHERS = 6.

    If sy-subrc = 0.

    • Calling Function to Create a Session






    KEEP = ‘X’










    RUNNING = 8



    OTHERS = 11.

    If sy-subrc = 0.


    MAIN Logic--





    TCODE = ‘TFBA’





    NOT_OPEN = 2





    OTHERS = 7.



    • Calling function to close the session



    NOT_OPEN = 1


    OTHERS = 3.






    • Create BDC Data



    • Passing information for 1st screen on BDCDATA


    BDCTAX-DYNPRO = 100.



    • Passing field information to BDCDATA




    • Passing BDC_OKCODE to BDCDATA


    BDCTAB-FVAL = ‘/5’.


    • Passing screen information for next screen to BDCDATA


    BDCTAB-DYNPRO = 200.



    • Passing screen information to BDCDATA




    • Passing screen information to BDCDATA




    • Passing BDC_OKCODE to BDCDATA






    Same steps to be repeated for CALL TRANSACTION

    The only difference between the two types of interface is in Session method, you create session and store information about screen and data into session. When session is processed the data is transferred to database. While in CALL TRANSACTION, data is transferred directly to database table.


    • Follow above Code till MAIN Logic. Even the Subroutine should be copied



    Call transaction ‘TFBA’ using BCDDATA Mode ‘A’ Update ‘S’.





    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jan 29, 2008 at 08:41 AM


    Batch Input and CALL TRANSACTION are both data transfer methods. Batch Input usually are used to transfer large amount of data. For example you are implementing a new SAP project, and of course you will need some data transfer from legacy system to SAP system. If there is no standard batch input program, direct input program, you would need to write your own data transfer program and it is going to be batch input program. CALL TRANSACTION methods is real-time method, whenever you run the program CALL TRANSACTION can be triggered. CALL TRANSACTION is used especially for integration actions between two SAP systems or between different modules. Users sometimes wish to do something like that click a button or an item then SAP would inserts or changes data automatically. Here CALL TRANSACTION should be considered. You use CALL TRANSACTION and you do everything automatically, collect necessary data, call transaction and so do database update. If any error occurs, show the user them.

    Batch Input

    With the Batch Input method, an ABAP program reads the external data that is to be entered in the R/3 System and stores the data in a “batch input session”. The session records the actions that are required to transfer data into the system using normal SAP transactions.

    When the program has generated the session, you can run the session to execute the SAP transactions in it. You can explicitly start and monitor a session with the batch input management function (by choosing System - Services - Batch Input), or have the session run in the background processing session.

    It offers management of sessions, support for playing back and correcting sessions that contain errors, and detailed logging. Your program prepares the data and stores it in a batch input session. A session is a collection of transaction data for one or more transactions. Batch input sessions are maintained by the system in the batch input queue. You can process batch input sessions in the background processing system.

    Your program must open a session in the queue before transferring data to it, and must close it again afterwards. All of these operations are performed by making function modules calls from the ABAP program.

    The most important aspects of the session interface are:

    Asynchronous processing

    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.


    In the second method, your program uses the ABAP statement CALL TRANSACTION USING to run an SAP transaction. External data doesn’t have to be deposited in a session for later processing. Instead, the entire batch input process takes place inline in your program. With CALL TRANSACTION USING, the system process the data more quickly than with batch input sessions. Unlike batch input sessions, CALL TRANSACTION USING does not automatically support interactive correction or logging functions.

    Your program prepares the data and then calls the corresponding transaction that is then processed immediately.

    The most important features of CALL TRANSACTION USING are:

    Synchronous processing

    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

    Session method.

    1) Assynchronous 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) Synchronous processing

    2) can transfer small amount of data

    3) processing is faster.

    4) errors need to be handled explicitly

    5) data is updated automatically

    The most important aspects of the CALL TRANSACTION is - Asynchronous processing - Transfers data for a single transaction -

    While for session method -It does not update transaction figures until the session has been processed.

    Processing batch input data with CALL TRANSACTION USING is the faster of the two recommended data transfer methods. In this method, legacy data is processed inline in your data transfer program.

    Call Transaction method makes an immediate call on the transaction and upload starts immediately.,

    Session method only creates a session of the whole recording including all the values that have to be inserted,it does not insert values into the system. This session can be invoked anytime to upload values

    In short call transaction is immediates

    session is not immediate

    Synchronous is simoultaneous upload






    MODE ‘N’

    UPDATE ‘S’.

    IF SY-SUBRC 0.

    WRITE: /‘ERROR’.



    With synchronous updating, we can check SY-SUBRC to determine the success of the transaction and the actual update to the database.

    Asynchornous is non-simultaneous upload






    MODE ‘N’

    UPDATE ‘A’.

    IF SY-SUBRC 0.

    WRITE: /‘ERROR’.



    With asynchronous updating, we can check SY-SUBRC to determine the success of the transaction only, not the actual update to the database.

    Reward if usefull

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.