difference

[Former Member]

difference b/w session and call transaction?

[Former Member]

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

[Former Member]

Hi,

In Batch input many transactions can be executed, where as in Call transcation only one transactioin can be executed.

BI is a background process, Ct can be either background or foreground .

BI is Synchronous process, Ct is both Asynchronous & Synchronous.

BI Sessions cannot be runed parallel.

Log file is generated automaticly in BI, errors can be found through BDCMSGCOLL.

Regards,

Sruthi

[Former Member]

Call transaction :

the transaction will be called immediatly when u run the report and the recording will be done once u execute the program...

Session method:

Session method will create a session ... U can schedule the session at any time so that it runs at the specified time..

Let us suppose that u need to enter some 1000 materials using MM01.. when u run this during normal working hours, it consumes time and server may lose its pace..

to avoid this , u can create a session for this data upload and schedule the session when users are less...say friday night..

In call Transaction u can update the data in synchronous as well as asynchronous.

in session method error log will be there, in call transaction u have to write code manualyy.

In session method u can run multiple transactions at a time, in call transaction only one transaction at a time

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

call transaction gets updated in one step.

session method in two step.

first a session gets created.

later from sm35 you have to run it.

in call transaction first recording is done and only a syntax CALL TRANSACTION <TCODE> USING BDCTAB MODE A/E/N UPDATE S/A MESSAGES INTO BDCMSGCOLL is used...here all the error messages are explicitly seen thru bdcmsgcoll.....once executed the program..process starts...

in session method after recording three fms are called

bdc_open_group

bdc_insert

bdc_close_group

built in error log in sm35 where u can view the errors

hence only when the session is processed in tcode sm35..process starts..in th sense all the data is kept in session and processed

however i suggest u to go thru the general diffrences between these two...

following are few links which can help u to get a better idea

http://www.sap-img.com/abap/bdc-example-using-table-control-in-bdc.htm

http://www.sap-img.com/abap/learning-bdc-programming.htm

Br,

Laxmi