Scribd
Upload
174 views

Difference Between Batch Input and Session Call Transaction

There are two main methods for batch data processing in SAP BDC: batch input and call transaction. Batch input uses session-based, synchronous processing which allows transferring large amounts of data but is slower, while call transaction uses asynchronous, real-time processing which is faster but requires explicit error handling. Batch input creates sessions that can be scheduled for later processing with built-in error handling, while call transaction updates data immediately.

Uploaded by

seventhhemanth
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
174 views

Difference Between Batch Input and Session Call Transaction

There are two main methods for batch data processing in SAP BDC: batch input and call transaction. Batch input uses session-based, synchronous processing which allows transferring large amounts of data but is slower, while call transaction uses asynchronous, real-time processing which is faster but requires explicit error handling. Batch input creates sessions that can be scheduled for later processing with built-in error handling, while call transaction updates data immediately.

Uploaded by

seventhhemanth
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
You are on page 1/ 1

http://www.sap-img.com/abap/difference-between-batch-input-and-call-transactionin-bdc.

htm Difference Between Batch Input and Call Transaction in BDC What is the 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 ABAP Tips by : Nagaraj Muniyappa Batch Data Communication (BDC) is the oldest batch interfacing technique that SA P provided since the early versions of R/3. BDC is not a typical integration t ool, in the sense that, it can be only be used for uploading data into R/3 and s o it is not bi-directional. BDC works on the principle of simulating user input for transactional screen, vi a an ABAP program. Typically the input comes in the form of a flat file. The ABAP program reads thi s file and formats the input data screen by screen into an internal table (BDCDA TA). 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 itse lf 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 transactio nal data, and this session can be viewed, scheduled and processed (using Transac tion 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 th en 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 dif ference is, instead of processing screens they validate fields and directly load the data into tables using standard function modules. For this reason, DI progr ams are much faster (RMDATIND - Material Master DI program works at least 5 time s faster) than the BDC counterpart and so ideally suited for loading large volum e data. DI programs are not available for all application areas.

You might also like