Call Transaction Method
-
Executes the transaction immediately.
-
Data is processed online in the same program run.
-
Uses the ABAP statement:
CALL TRANSACTION ‘MM01’ USING lt_bdcdata MODE ‘N’ UPDATE ‘S’.
-
Error handling: Errors can be captured in the BDCMSGCOLL table.
-
Faster but less reliable for large data volumes.
-
If the system fails, data may be lost (no log saved unless programmed explicitly).
Session Method
-
Creates a batch session (stored in SAP system).
-
Session can be executed later via SM35 (Batch Input: Session Overview).
-
Uses Function Modules:
BDC_OPEN_GROUP,BDC_INSERT,BDC_CLOSE_GROUP. -
Provides detailed error log automatically.
-
More reliable for large volumes of data.
-
Slower than Call Transaction because it records session and processes later.
Main Keyword:
| Feature | Call Transaction | Session Method |
|---|---|---|
| Execution | Immediate (online) | Stored session, run later via SM35 |
| Speed | Faster | Slower (creates and processes session) |
| Error Handling | Must capture manually (BDCMSGCOLL) | Automatic error log in SM35 |
| Reliability | Less reliable for huge data | More reliable for mass data loads |
| Logging | No session log | Full log available in SM35 |
| Use Case | Small/medium data, online processing | Large volume data migration, background |