SET UPDATE TASK LOCAL
2014-03-11 19:34
281 查看
SET
EffectSwitches on the local update task. This means that when you specify CALL FUNCTION ... IN UPDATE TASK , the update data is not stored in the database, but in ABAP/4 Memory. The update works as before. The only difference is that it is not performed in a separate process, but in the same process as the calling program, i.e. when a COMMIT WORK occurs, processing does not continue until all the update requests have been performed. In the standard setting, the normal update task is always active.
The switch status is not passed on from program to program. This means that CALL TRANSACTION and SUBMIT use the standard setting. In contrast to this, a module called with CALL DIALOG inherits the switch setting. This is because CALL TRANSACTION and SUBMIT run in their own LUW, while CALL DIALOG does not.
The switch setting is ignored in the update.
On COMMIT WORK and ROLLBACK WORK , the switch is reset.
Update requests with a delayed start (V2) cannot be processed locally.
Like in the normal update task, all messages apart from type 'S' result in termination and rollback.
Note
Unlike the normal update task, the local update task does not run in its own LUW . If a rollback occurs, any changes made in the dialog part are also reset.
SY-SUBRC = 1:
The local update task could not be switched on because a CALL FUNCTION ... IN UPDATE TASK has already been started. The system continues in the normal update mode.
SET UPDATE TASK LOCAL.
相关文章推荐
- 数据挖掘十大经典算法
- 一切都那么遥远
- node.js初恋
- linux创建交换分区
- this与super的区别
- PHP变量的内存布局、实现方法以及作用域
- 数理统计学:世纪末的回顾与展望(陈希孺)
- C++对象模型
- 视觉测量为什么要考虑畸变
- super、继承
- bat设置windows下ip
- ScrollView中嵌套GridView,Listview的办法
- 在窗口中添加全局热键
- 多文件编程
- 架构:Hexagonal Architecture Guidelines for Rails(转载)
- [LeetCode]Construct Binary Tree from Preorder and Inorder Traversal
- MapReduce研究
- 关于数据挖掘推荐系统实现
- iOS 快速实现Checkbox 效果
- 第 7 章-链接