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

Distinction between "Session"&"call Transaction" in BDC Program

Hi,

I encountered a difficulty when creating BDC program.

First,I recorded the Transaction MM01,and then generate the default program.As you know,if we run

the program directly,we will see "generate session" area on the left and "Call Transaction" on the right of

selection screen. And my problem is regarding "Session" area.

I just keyed in a string in the field SESSION,and the program does not work.

Have the session already created or not? Can the function "BDC_OOPEN_GROUP" generate a new

session?

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 31, 2008 at 11:28 AM

    Hi,

    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

    Hope this helps.

    Regards,

    Renjith Michael

    Add a comment
    10|10000 characters needed characters exceeded

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

    Hi,

    Call transaction:

    1.Synchronous Processing

    2.You can update the database both synchronously and asynchrounously.

    3.Transfer of data for individual transaction

    4.No batch input session is created.

    5.Faster than other batch input techniques.

    6.No automatic error log and restart capability is available here.

    7.Not recommended for bulk data transfer

    Session.

    1.Asynchronous Processing

    2.Synchronous database updates

    3.Transfer of data for multiple transaction

    4.Batch input sesssion is created here.

    5.Automatic error handling and efficient restart capability incase of error transaction.

    6.SAP's standard approach for data transfer

    7.Highly recommended for Bulk data transfer.

    8.Execution is slower than CALL TRANSACTION.

    Direct Input

    1.No screen are processed

    2.No session is created

    3.Data is transferred using standard FM

    4.Restart capability is available incase of error provided that the transaction is executed in background.

    Regards,

    Satish

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jan 31, 2008 at 01:09 PM

    Did you get a specific error message?

    Were there any transactions to process?

    You can check via SM35 if a session was created or not.

    To check if it was an authorisation error: Execute transaction SU53 just after running your program.

    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.