topic Re: BDC in Application Development and Automation Discussions

BDC

Former Member — Sat, 25 Aug 2007 04:45:03 GMT

HI Experts,

Can some1 tell me that BDC Threw Recording (SHDB) uses session method or Call Trasaction Method. What is the Diffresnce between these two methods.

THanks.

Khan

Re: BDC

Former Member — Sat, 25 Aug 2007 04:50:32 GMT

Hi,

Check this.

BDC is a sort of recording which is created say for examplr entering the sales order in system through a program,so you create a BDC for it.And whatever input fields to be enetred will be recorded and later on loaded with help of file upload.

call session and batch transaction

With session method a session will be generated that needs to be processed in Transacton SM35 with Foreground, Background, or Errors only mode. You can view and analyze session log after processing the session.

With call transaction you would specify the mode in the program itself. Hence, no session is generated in SM35 in this case.

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

http://www.planetsap.com/bdc_main_page.htm

http://www.sap-img.com/bdc.htm

Rewards points if it is useful.

Re: BDC

Former Member — Sat, 25 Aug 2007 04:54:37 GMT

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

Session method is to populate the data by filling BDC structure

and keep as session to process from SM37 to post in appropriate Transaction.

Call transaction method is to post the data directly into the Transaction from an Executable program.

Session method SAP defined Function modules.

Re: BDC

Former Member — Sat, 25 Aug 2007 04:59:26 GMT

BDC Threw Recording (SHDB) is neither session method nor Call Trasaction Method. Its a manual input of that particular transaction to get the structure of that transaction.

And your second answer is.....

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 method is to post the data directly into the Transaction from an Executable program.

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.

Session method is to populate the data by filling BDC structure

and keep as session to process from SM37 to post in appropriate Transaction.

Call transaction method is to post the data directly into the Transaction from an Executable program.

Re: BDC

varma_narayana — Sat, 25 Aug 2007 05:04:16 GMT

Hi.. Khan..

BDC Recording SHDB is used to Record the Execution of any transaction.

It will give the info to fill the BDCDATA table (program, Screen, Fieldname, FieldValue, Okcodes etc..).

We can use this info to implement either Session method or Call Transaction in our program.

Session method:

1. Data migration is done in two steps .. Generate session and Process session.

So resouces can be used efficiently. good for bulkdata migration.

2. Session method generates error log when u process a session.

3. No SY-SUBRC can be returned after each transaction is called.

4. Provides synchronous Updation only...

Call transaction method:

1. Data migration is done in single steps ..bcoz Transactions are called immediately after filling BDCDATA table. So good for small amount of data.

2. We have to collect error messages using BDCMSGCOLL Table

3. Returns SY-SUBRC ..after each Call Transaction..very useful feature..

4. Supports Asynch or Synch Updation.

<b>Reward if Helpful</b>