For all entries in
2017-11-14 17:29
267 查看
Today I read about a blog explaining very detailedly on how to correctly use the key words FOR ALL ENTRIES IN.
The link is : http://www.cnblogs.com/panjun-Donet/archive/2010/10/20/1857100.html.
Recollection: this keywords feature is used when two tables can't be joined to fetch data, such as a cluster table BSEG and a transparent table BSIS, which two are in a sense intersected. Therefore, if we want to fetch data from BSEG and BSIS, we can first put the BSIS data into an internal table called IT_BSIS, then we use SELECT statements to get data from BSEG by using FOR ALL ENTRIES IN IT_BSIS where BUKRS = IT_BSIS-BUKRS and ...
In above situation, we successfully completed the manipulation of fetching data from two intersected tables (Specificly refer to BSEG and BSIS).
Using FOR ALL ENTRIES IN feature is kind of disturbing, or rather wasting memory, sometimes. Especially when there are a large amount of data in the IT_BSIS table, and in this case the actual manipulation is getting all the conditions together and separating them with OR, and the whole condition will seem too abundant. It is better to consider if vital before we directly use this feature.
A necessary reminder is that Check the IT_BSIS table before we use this feature, or else the system might go dumped due to high load of data processing.
The link is : http://www.cnblogs.com/panjun-Donet/archive/2010/10/20/1857100.html.
Recollection: this keywords feature is used when two tables can't be joined to fetch data, such as a cluster table BSEG and a transparent table BSIS, which two are in a sense intersected. Therefore, if we want to fetch data from BSEG and BSIS, we can first put the BSIS data into an internal table called IT_BSIS, then we use SELECT statements to get data from BSEG by using FOR ALL ENTRIES IN IT_BSIS where BUKRS = IT_BSIS-BUKRS and ...
In above situation, we successfully completed the manipulation of fetching data from two intersected tables (Specificly refer to BSEG and BSIS).
Using FOR ALL ENTRIES IN feature is kind of disturbing, or rather wasting memory, sometimes. Especially when there are a large amount of data in the IT_BSIS table, and in this case the actual manipulation is getting all the conditions together and separating them with OR, and the whole condition will seem too abundant. It is better to consider if vital before we directly use this feature.
A necessary reminder is that Check the IT_BSIS table before we use this feature, or else the system might go dumped due to high load of data processing.
相关文章推荐
- 对于不能join的表,使用for all entries in语句将该表与内表串联。
- FOR ALL ENTRIES IN 的删除重复功能
- FOR ALL ENTRIES IN内表排序、排重对性能的影响
- ABAP "FOR ALL ENTRIES IN"
- ABAP中FOR ALL ENTRIES IN 运用
- Some tips for grammar 'For all Entries' in the ABAP
- FOR ALL ENTRIES IN的用法
- ABAP "FOR ALL ENTRIES IN" 使用指南
- ABAP "FOR ALL ENTRIES IN"
- FOR ALL ENTRIES IN注意事项
- FOR ALL ENTRIES IN 使用指南
- FOR ALL ENTRIES IN
- ABAP "FOR ALL ENTRIES IN" 使用指南
- ABAP "FOR ALL ENTRIES IN"
- ABAP FOR ALL ENTRIES IN用法
- ABAP "FOR ALL ENTRIES IN"
- for all entries in语句
- ABAP "FOR ALL ENTRIES IN" 使用指南
- ABAP "FOR ALL ENTRIES IN" 使用指南
- ABAP-FOR ALL ENTRIES IN 注意点