二维码

[bdc] BDC中Call Transaction和session区别

Twilight发表于 2015-01-20 11:33zhongguomao 最后回复于 2017-08-03 14:14 [复制链接] 1199 1

SHDB  Transaction Recorder:recording overview
SM35  Batch Input:session overview
Call Transaction method Classical or session method
In this method, the ABAP/4 program uses the call transaction <T-code > using <bdc_tab> mode <mode> update <update >  method. In this method, ABAP/4 program read the external data that is to be entered to the SAP system and stores the data in the batch input session.
When the prgm has finished creating the session, we can run the session thro the TC SM35. This method involves FM like BDC_OPEN,BDC_INSERT,BDC_CLOSE
In ‘Call Transaction’, the transactions are triggered at the time of processing itself and so the ABAP program must do the error handlingWhereas in Batch Input Sessions, the ABAP program creates a session with all the transactional data, and this session can be viewed, scheduled and processed (using Transaction SM35) at a later time. The latter technique has a built-in error processing mechanism too.
Synchronous ProcessingAsynchronous Processing
We can update the database both synchronously and asynchronously. We can specify the mode in the program.Synchronous Database update.
During processing, no transaction is started until the previous transaction has been written to the database.
No batch input processing logDetailed Log will be generated for all the sessions
While execution it starts from the first.While executing it wont start from the first. It will start from the place where it ends with error.
Faster than session methodNot as fast as call transaction method

Session:
1)同步处理
2)上传大量的数据
3)速度慢
4)错误可以被创建
5)生成Session后,数据才可以被更新

Transaction:
1 )异步处理
2)上传少量数据
3)速度快
4)错误需要外部处理
5)数据自动更新
回复

使用道具 举报

zhongguomao
速度发啊啊啊啊啊啊啊啊啊啊啊
回复 支持 反对

使用道具 举报

快速回帖

本版积分规则
您需要登录后才可以回帖 登录 | 注册有礼

快速回复 返回顶部 返回列表