topic BDC Session Method in Application Development and Automation Discussions

BDC Session Method

Former Member — Tue, 26 Feb 2008 23:44:06 GMT

Hi,

When do we choose BDC Session method?

Thanks in advance

Ramesh

Re: BDC Session Method

Former Member — Wed, 27 Feb 2008 01:43:30 GMT

For Bulk amount of data we will use SESSION METHOD in BDC

Error handling is the advantage of session method..

System provide by default logfile for handling error records.We don't have to code anything for processing them or writing the logs.

Check these threads.

Re: BDC Session Method

Former Member — Wed, 27 Feb 2008 04:08:59 GMT

hi,

SESSION METHOD

About Session method

In this method you transfer data from internal table to database table through sessions.

In this method, an ABAP/4 program reads the external data that is to be entered in the SAP System and stores the data in session. A session stores the actions that are required to enter your data using normal SAP transaction i.e., Data is transferred to session which in turn transfers data to database table.

Session is intermediate step between internal table and database table. Data along with its action is stored in session i.e., data for screen fields, to which screen it is passed, the program name behind it, and how the next screen is processed.

When the program has finished generating the session, you can run the session to execute the SAP transactions in it. You can either explicitly start and monitor a session or have the session run in the background processing system.

Unless session is processed, the data is not transferred to database table.

Also a session log is created in this BDC session method.

Regards,

Arunsri

Re: BDC Session Method

Former Member — Wed, 27 Feb 2008 04:16:08 GMT

hey dude.....

Typically the input comes in the form of a flat file. The ABAP program reads this file and formats the input data screen by screen into an internal table (BDCDATA). The transaction is then started using this internal table as the input and executed in the background.

In ‘Call Transaction’, the transactions are triggered at the time of processing itself and so the ABAP program must do the error handling. It can also be used for real-time interfaces and custom error handling & logging features. Whereas in

Batch Input Sessions, the ABAP program creates a session with all the transactional data, and this session can be viewed, scheduled and processed (using Transaction SM35) at a later time. The latter technique has a built-in error processing mechanism too.

Batch Input (BI) programs still use the classical BDC approach but doesn’t require an ABAP program to be written to format the BDCDATA. The user has to format the data using predefined structures and store it in a flat file. The BI program then reads this and invokes the transaction mentioned in the header record of the file.

Direct Input (DI) programs work exactly similar to BI programs. But the only difference is, instead of processing screens they validate fields and directly load the data into tables using standard function modules. For this reason, DI programs are much faster (RMDATIND - Material Master DI program works at least 5 times faster) than the BDC counterpart and so ideally suited for loading large volume data. DI programs are not available for all application areas.

Edited by: subbu1011 subbu on Feb 27, 2008 5:20 AM