0question regarding bdc

[Former Member]

hi all

out of call transaction or session method which is the best. how we make a decision.

in real time whic data transfer method is using

tino

[Former Member]

Both of them are equally efficient. Usually if you want the system to log the errors you use the BDC session method so that you can look at the errors in SM35.

However, if you use CALL TRANSACTION method, you will have to handle the errors yourself and also write the log.

Usually you use BDC session method, and run these sessions at the off peak period.

Regards,

Ravi

Note :Please mark the helpful answers

[abdul_hakim]

Hi Tino,

Use Session Method for bulk transfer.

Use Call transaction for small amount of data.

Cheers,

Abdul Hakim

Mark all useful answers..

[Former Member]

Hi Tino,

Here is the detailed comparison of both the methods.

<b>CALL TRANSACTION METHOD</b>

<b>1.</b>In this method, the <b>transactions</b> are <b>triggered at the time of processing</b> itself and so the <b>ABAP program must do the error handling.</b>

<b>2.</b>In this method, the ABAP program uses the call <b>transaction <T-code > using <bdc_tab> mode <mode> update <update > method.</b>

<b>3.Synchronous Processing</b>

<b>4.No batch input processing log</b>

<b>5 Synchronous and Asynchronous Database Update</b>

We can update the database both synchronously and asynchronously. We can specify the mode in the program.

<b>6 Faster in Execution</b>

While execution it starts from the first hence, Faster than session method

<b>CLASSICAL OR SESSION METHOD</b>

1.Whereas in Batch Input Sessions, <b>the ABAP program creates a session with all the transactional data</b>, and this session can be viewed, scheduled and processed using Transaction SM35 at a later time. <b>This technique has a built-in error processing mechanism too.</b>

<b>2.</b>In this method, ABAP program <b>reads the external data</b> that is to be entered to the SAP system and <b>stores the data in the batch input session.</b>This method involves Function modules Modules like <b>BDC_OPEN,

BDC_INSERT,

BDC_CLOSE</b>

When the program has finished creating the session, we can run the session through the Transaction code SM35.

<b>3.Asynchronous Processing</b>

<b>4.Detailed Log will be generated</b> for all the sessions

While executing it wont start from the first. It will start from the place where it ends with error.

<b>

5.Synchronous Database update.</b>

During processing, no transaction is started until the previous transaction has been written to the database.

<b>6.Slower As Compared to Call Transaction Method</b>

Not as fast as call transaction method because While executing, as it does not start from starting.

<b>Clasical or Session Method is recommended if you are having problems getting data entered into your SAP System quickly enough .

The Playback,interactive correction,and logging facilities are offered for batch input sessions that are not available for CALL TRANSACTION USING Method.</b>

Both the above method need acommon data structurefor storing the instructions and data for SAP Transactions.This structure is defined as BDCDATA in the dictionary.

Now you decide which method is best for your scenario.

Thanks And Regards

Pawan P.Khilari

<b>*Please Mark Useful Answers</b>

Message was edited by: Pawan Khilari

[Manohar2u]

Tino

Refer to the link for differences between call transaction and batch input method

<a href="http://help.sap.com/saphelp_47x200/helpdata/en/fa/097015543b11d1898e0000e8322d00/frameset.htm">Batch input & & Call Transaction differences</a>

Regds

Manohar

[dani_mn]

Both methods have some benefits and you decide according to requirments you have.

Like Call Transaction is 2 to 3 times faster than batch input.

and if you don't want to process the session using sm35 and want to do upload directly call transaction is good option.

on the other hand if you are interested in Log and error handling session method is nice.

Regards,

Wasim Ahmed