Which method should use? Call Transaction or Session Method?

[Former Member]

I need to upload 1,00,000 records then which method i need to use? Either session or call transaction?

[bpawanchand]

Hi

Use Session METHOD of BDC

check the below thread for reasons

Regards

Pavan

[Former Member]

Session Method

[GauthamV]

hi,

use session method.

u can track errors in seperate session using session method.

[Former Member]

This message was moderated.

[Former Member]

Hi,

Session method:

1. It can handle small amount of data as well as large

amount of data.

2. It can handle multiple applications simultaneously.

3. This method by default has log files. Log files is used

to store error records.

4. It can process the data fore ground and back ground

because it can handle small amount of data as well as large

amount of data.

5. It processes the database Asynchronously and updates the

database synchronously.

Call-transaction Method:

1. With this method we can process the data in fore ground

only.

2. This method compatible small amount of data only. user

can create log file explicitly using BDCMSGCOLL structure.

3. It processes the data and updates synchronously.

4. It can handle one application at a time.

For ur case it is better to go for BDC Session method.

Regards,

Prem

[naveen_inuganti2]

Hi.....

A (asynchronous updating) The called transaction does not wait until the database has been

updated, it simply forward the updates to the SAP update service. This usually speeds up the CT

program. This processing mode is NOT recommended for large data sets as the called transaction

does not receive a completion message from the update module.

The calling CT program therefore cannot tell if the transaction has been successfully completed. You

should use the updating administration function (transaction SM13) to determine whether updating

was terminated early. The error analysis /correction functions for are less helpful than with

synchronous updating.

S (synchronous updating) With synchronous updating the called transaction waits until all the

updates have been completed. So processing is slower than with synchronous updating. The called

transaction can however report any updating errors to the program, which makes error

analysis/correction easier.

And

Unlike the classical batch input processing with sessions CALL TRANSACTION does not offer any

special processing procedures for transactions containing errors. There are no restart functions for

transactions that contain errors or that cause updating terminations.

Now you decide which one is best...

For large amount of data Sessions method is the better.

Thanks,

Naveen.I

[Former Member]

Hi ,

Better to use Session Method for more date

if u r doing bdc with less data u can use call transaction method

[Former Member]

Hi ,

Use session method and run in the back ground process as there is no need to enter the ENTER button as many times for each record and also you can track the errors in this method.

For mass uploading of data session method is the best.

Regards,

Santhosh A.

[Former Member]

Hello Praveen.

I would like to suggest my opinion,

Call transaction is faster than session method.

while updating the Database it just checks the success of updation.

Session Method provides better transfer of data as well as large data records.

While updating the database it checks for success of the updation as well as of the transaction.

Hence, It takes more time.

If Synchronous updation is required and error free data transfer is also required. Session method provides more reliablity by Automatic error logging.

Hope that'll be fine.

Good Luck & Regards.

Harsh Dave