BDC stands for Batch Data communication. The core of the BDC lies in Batch Input which facilitates either data transfer from non-SAP system to SAP system or from one SAP system to another by means of screens. This is very important to understand – the data is directly applied/transferred to transaction screens.
What does that mean? Using Batch Input, the session carries out the required SAP transactions with the available data the same way a user will perform them. This is an automatic process and can be used as a part of a program which eliminates the need of having a user. It is especially a helpful tool in case of a large volume of data transfer.
There are two methods to implement BDC –
- Classical Batch Input Method
- BIM is an asynchronous process with synchronous database update
- It facilitates transfer of data for multiple transactions
- Input processing log is generated
- Call Transaction Method
- CTM is a synchronous process
- It facilitates transfer of data for only one transaction at a time
- It doesn’t generate any input processing log
Call Transaction Method is better in terms of performance.
When data is transferred between SAP systems, there is some control on the data type, however, in the case of non-SAP systems, the data comes in form of flat files. Hence, it is important to properly convert the data accordingly so that it can be consumed by screens.
Last point, this transfer of data is always inbound to SAP from SAP/non-SAP systems and never outbound to a non-SAP system from SAP system.