BDC or Batch Data Communication and Call Transaction are methods of interfacing strategy. One can run over numerous contrasts between BDC and Call Transaction. The handling is delayed in Batch Data Communication when contrasted with the preparing speed in call transactions. When managing mistakes, both Batch Data Communication, and Call Transaction have their particulars.
BDC vs Call Transaction
The difference between BDC and Call Transaction is that the BDC interface is Asynchronous i.e. it is processed in batches, on the other hand, the main part of the Call Transaction interface is Synchronous i.e. it takes on a real-time basis.
BDC or Batch Data Communication is a batch interfacing strategy that SAP created. It is for the most part utilized for transferring information into the SAP R/3 framework. BDC works by reproducing the client input from a value-based screen using an ABAP program.
Call Transaction, the exchanges are set off at the hour of preparing itself thus the ABAP program should do the mistake taking care of. It can likewise be utilized for ongoing interfaces and custom mistake taking care of and logging highlights.
Comparison Table Between BDC and Call Transaction
|Parameters of Comparison||BDC||Call Transaction|
|Error Dealing||In BDC, error dealing is finished by the framework by making of mistake log.||In call transactions, error dealing has to be done expressly by the program by utilizing structure BDCMSGCOLL.|
|Measure||It is utilized for an enormous measure of information.||It is ideal for less measure of information.|
|Communication Type||Information handling is Asynchronous.||Information handling is Synchronous.|
|Data Set||Data set updates are coordinated.||Data set updates are coordinated/nonconcurrent.|
|Utilization||Various exchanges can be utilized.||Just a single exchange can be utilized.|
What is BDC?
BDC or batch data communication is a method utilizing heritage information or information stacking into SAP framework which isn’t refreshed in the SAP frameworks. For instance, the organization chooses to adjust its frameworks and techniques to SAP and introduces SAP, it should transfer a gigantic volume of information that is a piece of its inheritance frameworks or old frameworks into the SAP framework. This strategy is done through BDC.
BDC meetings, which are otherwise called Batch Input Sessions, are utilized to stack heritage information into the SAP framework and perform profoundly redundant errands that include information passage. BDC meeting mimics the online section, everything being equal, exchanges, approvals that are remembered for every exchange.
To perform a BDC exchange, a developer needs to physically look at the whole exchange interestingly. He should take note of every field – including subtleties like the field’s name, type, and length. Software engineer needs to compose a bunch input program to arrange the whole approaching information into a BDC table. SAP works on the whole cycle by utilizing BDC Recording. BDC Recording is an element that is remembered for SAP R/3 frameworks. In BDC Recording, a client records an example exchange and Importer Wizard arranges the recording into the construction of type tree. The tree is then utilized in Map Designer which maps the whole information straightforwardly into the BDC table arrangement. This is then prepared altogether by the BDC meeting program.
What is Call Transaction?
Call Transaction is a strategy like meeting strategy, while group input is a two-stage methodology, call transaction does the two stages online one just after the other, we can restart the framework. The main parts of the CALL TRANSACTION USING interface are: – Synchronous preparing – Transfers information for a solitary exchange – Synchronous and offbeat data set refreshing both conceivable. The program indicates which sort of refreshing is wanted. Separate LUW for the exchange the framework plays out a data set submit preceding and after the CALL TRANSACTION USING explanation. – No bunch input preparing log is produced.
In the Call Transaction technique, we call the exchange in the BDC program itself. Assuming we need this program to be executed by another person then we need to open the code to him. Call Transaction Method Works in Foreground. No Display Mode is equivalent to Background Processing in the call transaction technique. Call Transaction Method can deal with just a single application at a time. In Call Transaction Method no Log File of course. We need to configure the Log File by utilizing BDCMSGCOLL. Call Transaction Method Updates the Database Asynchronously. In this method, the information gets refreshed automatically in call transaction.
Main Differences Between BDC and Call Transaction
- The main part of the BDC interface is Asynchronous preparing. Then again, the main part of Call Transaction interface is simultaneous handling.
- In BDC, no new exchange will be begun till the past exchange has been totally kept in touch with the information base. In Call Transaction, the exchanges occur at the hour of handling itself.
- At the point when Batch Data Communication moves enormous measure of information, call transaction just exchanges a limited quantity of information.
- The handling is delayed in Batch Data Communication when contrasted with the preparing speed in call transaction.
- In BDC, information isn’t refreshed as data set tables. In Call Transaction, quick updating in database is excepted in meeting handled table.
When contrasting the two, Batch Data Communication is the most seasoned interfacing procedure. The main part of the BDC interface is Asynchronous preparing. This implies that it is utilized for quite a long time of information. In this strategy, no new exchange will be begun till the past exchange has been kept in touch with the data set. In Batch Data Communication, the meetings don’t begin equal. When managing mistakes, both Batch Data Communication, and call transaction have their particulars. While blunder log is made in Batch Data Communication, the mistakes should be dealt with obviously.
Another distinction that is seen is in the information move. In Batch Data Communication, the information isn’t refreshed except if a meeting is handled. Then again, the information gets naturally refreshed in call transactions.