admin管理员组文章数量:1351984
Even though I am sorting the internal table LT_DATA by the FKDAT field, the POSNR field is still being sorted in an unexpected order. For example, in the original data of the internal table, POSNR value '1' appears first, followed by POSNR value '2'. However, after sorting by FKDAT, the order of POSNR changes as well, which I didn’t expect. Please refer to the highlighted section of the image for clarification.
I'm trying to understand the internal logic behind how the sorting is being handled.
When I modify the code to: SORT lt_data BY fkdat vbeln posnr.
I get the desired output.
Can you help explain why POSNR is being sorted in the first case, and how the sorting logic works internally?
TYPES: BEGIN OF lty_data,
fkdat TYPE vbrk-fkdat,
vbeln TYPE vbrk-vbeln,
posnr TYPE vbrp-posnr,
END OF lty_data.`
DATA: lt_data TYPE STANDARD TABLE OF lty_data.
lt_data = VALUE #( ( vbeln = '1203002977' posnr = '000001' fkdat = '20240407' )
( vbeln = '1203002977' posnr = '000002' fkdat = '20240407' )
( vbeln = '1203002977' posnr = '000003' fkdat = '20240407' )
( vbeln = '1203002977' posnr = '000004' fkdat = '20240407' )
( vbeln = '1203003080' posnr = '000001' fkdat = '20240515' )
( vbeln = '1203003080' posnr = '000002' fkdat = '20240515' )
( vbeln = '1203003080' posnr = '000003' fkdat = '20240515' )
( vbeln = '1203003080' posnr = '000004' fkdat = '20240515' )
( vbeln = '1205010163' posnr = '000001' fkdat = '20240406' )
( vbeln = '1205010163' posnr = '000002' fkdat = '20240406' )
( vbeln = '1205010254' posnr = '000001' fkdat = '20240424' )
( vbeln = '1205010254' posnr = '000002' fkdat = '20240424' )
( vbeln = '1205010254' posnr = '000003' fkdat = '20240424' )
( vbeln = '1301012394' posnr = '000001' fkdat = '20240429' )
( vbeln = '1301012394' posnr = '000002' fkdat = '20240429' )
( vbeln = '1323000956' posnr = '000001' fkdat = '20240510' )
( vbeln = '1323000956' posnr = '000002' fkdat = '20240510' )
( vbeln = '1323000967' posnr = '000001' fkdat = '20240513' )
( vbeln = '1323000967' posnr = '000002' fkdat = '20240513' )
( vbeln = '1323000982' posnr = '000003' fkdat = '20240516' )
( vbeln = '1323000982' posnr = '000004' fkdat = '20240516' )
( vbeln = '1323000982' posnr = '000005' fkdat = '20240516' )
( vbeln = '1323001014' posnr = '000001' fkdat = '20240527' )
( vbeln = '1323001025' posnr = '000001' fkdat = '20240606' ) ).
SORT lt_data BY fkdat.
Output:
Even though I am sorting the internal table LT_DATA by the FKDAT field, the POSNR field is still being sorted in an unexpected order. For example, in the original data of the internal table, POSNR value '1' appears first, followed by POSNR value '2'. However, after sorting by FKDAT, the order of POSNR changes as well, which I didn’t expect. Please refer to the highlighted section of the image for clarification.
I'm trying to understand the internal logic behind how the sorting is being handled.
When I modify the code to: SORT lt_data BY fkdat vbeln posnr.
I get the desired output.
Can you help explain why POSNR is being sorted in the first case, and how the sorting logic works internally?
TYPES: BEGIN OF lty_data,
fkdat TYPE vbrk-fkdat,
vbeln TYPE vbrk-vbeln,
posnr TYPE vbrp-posnr,
END OF lty_data.`
DATA: lt_data TYPE STANDARD TABLE OF lty_data.
lt_data = VALUE #( ( vbeln = '1203002977' posnr = '000001' fkdat = '20240407' )
( vbeln = '1203002977' posnr = '000002' fkdat = '20240407' )
( vbeln = '1203002977' posnr = '000003' fkdat = '20240407' )
( vbeln = '1203002977' posnr = '000004' fkdat = '20240407' )
( vbeln = '1203003080' posnr = '000001' fkdat = '20240515' )
( vbeln = '1203003080' posnr = '000002' fkdat = '20240515' )
( vbeln = '1203003080' posnr = '000003' fkdat = '20240515' )
( vbeln = '1203003080' posnr = '000004' fkdat = '20240515' )
( vbeln = '1205010163' posnr = '000001' fkdat = '20240406' )
( vbeln = '1205010163' posnr = '000002' fkdat = '20240406' )
( vbeln = '1205010254' posnr = '000001' fkdat = '20240424' )
( vbeln = '1205010254' posnr = '000002' fkdat = '20240424' )
( vbeln = '1205010254' posnr = '000003' fkdat = '20240424' )
( vbeln = '1301012394' posnr = '000001' fkdat = '20240429' )
( vbeln = '1301012394' posnr = '000002' fkdat = '20240429' )
( vbeln = '1323000956' posnr = '000001' fkdat = '20240510' )
( vbeln = '1323000956' posnr = '000002' fkdat = '20240510' )
( vbeln = '1323000967' posnr = '000001' fkdat = '20240513' )
( vbeln = '1323000967' posnr = '000002' fkdat = '20240513' )
( vbeln = '1323000982' posnr = '000003' fkdat = '20240516' )
( vbeln = '1323000982' posnr = '000004' fkdat = '20240516' )
( vbeln = '1323000982' posnr = '000005' fkdat = '20240516' )
( vbeln = '1323001014' posnr = '000001' fkdat = '20240527' )
( vbeln = '1323001025' posnr = '000001' fkdat = '20240606' ) ).
SORT lt_data BY fkdat.
Output:
Share Improve this question edited Apr 1 at 19:15 Sandra Rossi 13.8k6 gold badges25 silver badges56 bronze badges asked Apr 1 at 5:11 Prabhand ReddyPrabhand Reddy 754 bronze badges 1 |2 Answers
Reset to default 3https://help.sap/doc/abapdocu_752_index_htm/7.52/en-US/abapsort_itab.htm
What you miss:
"Sorting is unstable by default, which means that the relative order of rows that do not have different sort keys is not preserved when they are sorted. The order can be different depending on the platform or when sorted multiple times."
This simply means, if you sort by one field only (fkdat), the rest will be random and could vary.
Sorting isn't stable by default. But you can use the STABLE addition.
This should work:
SORT lt_data STABLE BY fkdat.
本文标签： sortingSORT Issue in SAP ABAPStack Overflow
版权声明：本文标题：sorting - SORT Issue in SAP ABAP - Stack Overflow 内容由网友自发贡献，该文观点仅代表作者本人， 转载请联系作者并注明出处：http://www.betaflare.com/web/1743907922a2559843.html， 本站仅提供信息存储空间服务，不拥有所有权，不承担相关法律责任。如发现本站有涉嫌抄袭侵权/违法违规的内容，一经查实，本站将立刻删除。
STABLEif one column can be used to order the lines, because it's always best to be explicit in the code. Also, I would recommend using SORTED or HASHED tables instead of STANDARD, hence no SORT needed anymore. – Sandra Rossi Commented Apr 2 at 11:02