BDC stands for Batch Data Communication which is used for transfering the data from Non-SAP system to R/3 system.
Types of BDC (Batch Data Communication)
- CLASSICAL BATCH INPUT (Session Method)
- CALL TRANSACTION
CLASSICAL BATCH INPUT (Session Method)
This method is also called as ‘CLASSICAL METHOD’.
- Asynchronous processing.
- Synchronous Processing in database update.
- Transfer data for more than one transaction.
- Batch input processing log will be generated.
- During processing, no transaction is started until the previous transaction has been written to the database.
CALL TRANSACTION METHOD :
This is another method to transfer data from the legacy system.
- Synchronous processing. The system performs a database commit immediately before and after the CALL TRANSACTION USING statement.
- Updating the database can be either synchronous or asynchronous. The program specifies the update type.
- Transfer data for a single transaction.
- Transfers data for a sequence of dialog screens.
- No batch input processing log is generated.
How to transfer data into your R/3 System from a legacy system?
To transfer data into your R/3 System from a legacy system or from another R/3 System you can use the batch input (BI), call transaction (CT) and direct input (DI) methods.
There are two methods to transfer data:
Standard transfer programs:
For many standard transfers, there are already standard data transfer programs in the R/3 System. You do not need to write your own batch input program. You need only to ensure that the data is available in the format specified by SAP.
Customer transfer programs:
Here you can create your own data transfer program. You can also determine the structure of the data.
The method used to transfer data determines the actual conversion of the data, as this decision establishes the structure of the SAP format