BDC?

[Former Member]

Can anyone tell me which is best method in BDC and what are the diffrences?

For ex. IF I am given a chance to create a BDC either in using session method or Call transaction, which one should be preferred? and Y?

Please answer, points are assured!!!!!

[Former Member]

hi,

If the number of records r so high then its better to go with session method because call transaction method will not be preferable with the so many records

call transaction doesnot have logfile concept where as session method will have by default, in call transaction u have to desgn that explicitly

[jayanthi_jayaraman]

Hi,

If the no. of records is low,you can go for BDC call transaction.Here you need to handle errors explicitly using function modules.

If more records are to be inserted,you can use session method.Error log will be created.

[Former Member]

hi,

CALL TRANSACTION.

1. Synchronous Processing

2. Synchronous and Asynchronous

Database Update

3. Transfer form individual transaction,

each time the CALL Transaction is

called.

4. Separate LUW for the transaction.

5. System executes commit immediately

before and after CALL TRANSACTION

USING statement.

6. No batch input processing log is

generated.

SESSION METHOD.

1. Asynchronous processing

2. Only Synchronous Database update (During

processing, no transaction is started until the

previous transaction has been written to the

database.)

3. Transfers data for multiple transactions.

4. Sessions cannot be generated in parallel.

5. Supports playback for correcting sessions that

contains errors.

6. A batch input processing Detailed Log is

generated for each session.

(Prgg opens a session in queue before data transfer)

Both hav advan & disadvan ,but in The CALL TRANSACTION method allows only a single transaction tobe processed by SAP.therefore i prefer Session method.

shan

[former_member69765]

Both have its own advantages and disadvantages.

I will list down the differences so that u can judge urself according to ur situation when to use which method.

<b><u>BDC Session</u></b>

When the program is executed, the data is not updated in the table . A session is created that has to be processed seperately. This is done thru SM35. The processing can be automated also and can be done immedieately without going to SM35 by calling the Program - RSBDCSUB

The error logs are automatically captured in this method.

The errored records can be changed and processed.

<b><u>Call Transaction</u></b>

A session is not created. The records are processed instantly. So when the program is executed .. the records are updated in system.

Error capturing is not possible automatically. It has to be handled by coding. U can use the extension - messages into <itab> to do that.

So it all depends what is the scenario and which method to use. If you are doing some data transfer from legacy sytem to SAP .. in general the call transaction method is used more.

Hope this helped you. Feel free to ask is some this is un answered.

[Former Member]

hi,

please reward helpful answers with the points already assured by you!!

[Former Member]

call transaction is online and session is offline.

Session is allways recommonded, Bz we can run the session with huge data in non performing hours like night times and week ends, to reduce the database hits.

Also we can set the time for session execution.

In call transaction the updation is immediate. Network traffic will be more.

Cheers.

[Former Member]

hi, this is prakash

call transaction is mainly used when u want u update the database using asynchrouns method.

but in context of session method the method of updating is synchrouns, large amount of data is required, so huge database is required. so finally using the call transaction method