What is bdc in sap

Last updated: April 1, 2026

Quick Answer: BDC in SAP stands for Batch Data Communication, a method for transferring large volumes of data into SAP systems without manual data entry. BDC automates the process of filling screen fields and executing transactions as if a user were manually entering the data.

Key Facts

Overview

Batch Data Communication (BDC) is a traditional SAP data transfer mechanism that allows organizations to load data into SAP systems in batch mode. Instead of manually entering data through SAP screens, BDC automates the process by recording transaction steps and replaying them for multiple data records. This method simulates user interaction with SAP transactions, filling screens and executing business logic as if a user were performing the actions manually.

How BDC Works

BDC operates by creating a batch input session containing a series of transaction steps. Each step includes the transaction code and the field values to be entered. When the batch is processed, SAP reads the session data and:

Creating BDC Sessions

BDC sessions are typically created using ABAP programming language through the CALL TRANSACTION statement combined with batch input parameters. Developers can also use SAP's transaction recording function (SM35) to record user actions and convert them into batch input. The session data is stored in SAP tables and can be executed immediately or scheduled for later processing. Error handling is crucial, as incorrect data or validation failures are logged for manual correction.

Advantages and Limitations

BDC advantages include compatibility with any SAP transaction, ability to validate business logic through screen processing, and comprehensive error logging. However, BDC is slower than direct database updates and can only process one transaction at a time. The method depends on stable transaction screens, making it vulnerable to SAP version updates. For large-scale data migrations, modern alternatives like LSMW (Legacy System Migration Workbench) or direct database inserts using ABAP OOP are often preferred for better performance.

Modern Alternatives

Contemporary SAP implementations often use LSMW for simpler migrations, direct ABAP database inserts for performance-critical loads, or APIs and web services for external data integration. However, BDC remains valuable for complex transaction logic that requires full business rule validation and error handling through SAP screens.

Related Questions

What is the difference between BDC and LSMW in SAP?

BDC is a lower-level ABAP technique requiring programming knowledge, while LSMW (Legacy System Migration Workbench) is a GUI-based tool that generates BDC sessions. LSMW is easier to use for non-technical users but less flexible, whereas BDC offers more control for complex scenarios.

How do you handle errors in BDC batch input?

Errors in BDC sessions are logged and the session can be configured to stop on errors or skip them. Failed records are recorded in the batch input session log, allowing administrators to review issues and reprocess corrected data separately.

What is SM35 in SAP and how does it relate to BDC?

SM35 is the SAP transaction for maintaining and executing batch input sessions created through BDC. It allows users to view recorded sessions, execute them, check logs, and manage batch processing. SM35 is the primary interface for BDC session management and troubleshooting.

Sources

  1. Wikipedia - SAP ERP CC-BY-SA-4.0
  2. SAP Help Portal proprietary