2007 Jul 05 6:22 AM
2007 Jul 05 6:26 AM
Hi Riya
In order to achieve the Page Breaks, we need to fill in the sort catalog structure, LVC_S_SORT, as follows:
FS_SORT-SPOS = '1'. Sort order position
FS_SORT-FIELDNAME = 'CARRID'. Field name on which page break need to be triggered. Whenever this field changes, page break will trigger
FS_SORT-GROUP = ''. This has 2 options. for page breaks and U for underlines.
FS_SORT-OBLIGATORY = 'UL'. If you need to retail these page breaks through out, we need to set this as obligatory. Otherwise, if the end user selects any other field and presses SORT, then page breaks would disappear.
APPEND FS_SORT TO T_SORT.
Hi Riya
In order to achieve the Page Breaks, we need to fill in the sort catalog structure, LVC_S_SORT, as follows:
FS_SORT-SPOS = '1'. Sort order position
FS_SORT-FIELDNAME = 'CARRID'. Field name on which page break need to be triggered. Whenever this field changes, page break will trigger
FS_SORT-GROUP = ''. This has 2 options. for page breaks and U for underlines.
FS_SORT-OBLIGATORY = 'UL'. If you need to retail these page breaks through out, we need to set this as obligatory. Otherwise, if the end user selects any other field and presses SORT, then page breaks would disappear.
APPEND FS_SORT TO T_SORT.
2007 Jul 05 6:26 AM
Hi Riya
In order to achieve the Page Breaks, we need to fill in the sort catalog structure, LVC_S_SORT, as follows:
FS_SORT-SPOS = '1'. Sort order position
FS_SORT-FIELDNAME = 'CARRID'. Field name on which page break need to be triggered. Whenever this field changes, page break will trigger
FS_SORT-GROUP = ''. This has 2 options. for page breaks and U for underlines.
FS_SORT-OBLIGATORY = 'UL'. If you need to retail these page breaks through out, we need to set this as obligatory. Otherwise, if the end user selects any other field and presses SORT, then page breaks would disappear.
APPEND FS_SORT TO T_SORT.
| User | Count |
|---|---|
| 3 | |
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |