How to put the left to right scroll bar

Former Member · ‎09-28-2007

Hi iam new comer to sap, So pls help me. I want to display more than 17 fields from 6 different tables. At the time of display i want to put left to right scroll bar in my report screen. Because in my report screen the records are displayed with merged. So please give your valuable ideas.

Thanks in advance

regards,

Kesav.

Former Member · ‎09-28-2007

Hi

in classical report or intercative report it won't be possible

do in ALV report that can be possible

you can define any number of fieldcatalogs means any number of fields in the output

use in this way

Your own company logo can go here if it has been saved (OAOR)
If the logo is larger than the size of the headings in gt_page,
the window will not show full logo and will have a scroll bar. Thus,
it is a good idea to have a standard ALV header if you are going to
use logos in your top of page.

&----

FORM top_of_page.

CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'

EXPORTING

it_list_commentary = gt_page

i_logo = 'ENJOYSAP_LOGO'.

ENDFORM. "top_of_page

i wil send u my program by seaing that you can find it

&----

*& Report ZTEST_ALV_LOGO

*&

&----

*&

&----

REPORT ztest_alv_logo.

TYPE-POOLS : slis.

*ALV Formatting tables /structures

DATA: gt_fieldcat TYPE slis_t_fieldcat_alv.

DATA: gt_events TYPE slis_t_event.

DATA: gs_layout TYPE slis_layout_alv.

DATA: gt_page TYPE slis_t_listheader.

DATA: gs_page TYPE slis_listheader.

DATA: v_repid LIKE sy-repid.

*ALV Formatting work area

DATA: w_fieldcat TYPE slis_fieldcat_alv.

DATA: w_events TYPE slis_alv_event.

DATA: gt_bsid TYPE TABLE OF bsid WITH HEADER LINE.

INITIALIZATION.

PERFORM build_events.

PERFORM build_page_header.

START-OF-SELECTION.

*perform build_comment. "top_of_page - in initialization at present

SELECT * FROM bsid INTO TABLE gt_bsid UP TO 10 ROWS.

*perform populate_for_fm using '1' '3' 'BUKRS' '8' 'GT_BSID' 'Whee'.

*USING = Row, Column, Field name, display length, table name, heading

*OR

PERFORM build_fieldcat.

gs_layout-zebra = 'X'.

*top of page event does not work without I_callback_program

v_repid = sy-repid.

CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'

EXPORTING

i_callback_program = v_repid

i_structure_name = 'BSID'

i_background_id = 'ALV_BACKGROUND'

i_grid_title = 'This is the grid title'

I_GRID_SETTINGS =

is_layout = gs_layout

it_fieldcat = gt_fieldcat[]

it_events = gt_events[]

TABLES

t_outtab = gt_bsid.

************************************************************************

Form..............: populate_for_fm
Description.......: Populates fields for function module used in ALV

************************************************************************

FORM populate_for_fm USING p_row

p_col

p_fieldname

p_len

p_table

p_desc.

w_fieldcat-row_pos = p_row. "Row Position

w_fieldcat-col_pos = p_col. "Column Position

w_fieldcat-fieldname = p_fieldname. "Field name

w_fieldcat-outputlen = p_len. "Column Lenth

w_fieldcat-tabname = p_table. "Table name

w_fieldcat-reptext_ddic = p_desc. "Field Description

w_fieldcat-input = '1'.

APPEND w_fieldcat TO gt_fieldcat.

CLEAR w_fieldcat.

ENDFORM. " populate_for_fm

&----

*& Form build_events

&----

FORM build_events.

DATA: ls_event TYPE slis_alv_event.

CALL FUNCTION 'REUSE_ALV_EVENTS_GET'

EXPORTING

i_list_type = 0

IMPORTING

et_events = gt_events.

READ TABLE gt_events

WITH KEY name = slis_ev_user_command

INTO ls_event.

IF sy-subrc = 0.

MOVE slis_ev_user_command TO ls_event-form.

APPEND ls_event TO gt_events.

ENDIF.

READ TABLE gt_events

WITH KEY name = slis_ev_top_of_page

INTO ls_event.

IF sy-subrc = 0.

MOVE slis_ev_top_of_page TO ls_event-form.

APPEND ls_event TO gt_events.

ENDIF.

ENDFORM. " build_events

&----

*& Form USER_COMMAND

&----

When user command is called it uses 2 parameters. The itab
passed to the ALV is in whatever order it currently is on screen.
Therefore, you can read table itab index rs_selfield-tabindex to get
all data from the table. You can also check r_ucomm and code
accordingly.

&----

FORM user_command USING r_ucomm LIKE sy-ucomm

rs_selfield TYPE slis_selfield.

READ TABLE gt_bsid INDEX rs_selfield-tabindex.

error checking etc.

SET PARAMETER ID 'KUN' FIELD gt_bsid-kunnr.

CALL TRANSACTION 'XD03' AND SKIP FIRST SCREEN.

ENDFORM. "user_command

&----

*& Form top_of_page

&----

Your own company logo can go here if it has been saved (OAOR)
If the logo is larger than the size of the headings in gt_page,
the window will not show full logo and will have a scroll bar. Thus,
it is a good idea to have a standard ALV header if you are going to
use logos in your top of page.

&----

FORM top_of_page.

CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'

EXPORTING

it_list_commentary = gt_page

i_logo = 'ENJOYSAP_LOGO'.

ENDFORM. "top_of_page

&----

*& Form build_fieldcat

&----

*Many and varied fields are available here. Have a look at documentation

*for FM REUSE_ALV_LIST_DISPLAY and REUSE_ALV_FIELDCATALOG_MERGE

----

FORM build_fieldcat.

w_fieldcat-fieldname = 'BUDAT'.

w_fieldcat-seltext_m = 'Dte pst'.

w_fieldcat-ddictxt(1) = 'M'.

Can change the position of fields if you do not want them in order
of the DDIC or itab

w_fieldcat-row_pos = '1'.
w_fieldcat-col_pos = '10'.

APPEND w_fieldcat TO gt_fieldcat.

CLEAR w_fieldcat.

ENDFORM. " build_fieldcat

&----

*& Form build_page_header

&----

gt_page is used in top of page (ALV subroutine - NOT event)
*H = Header, S = Selection, A = Action

----

FORM build_page_header.

For Headers, Key is not printed and is irrelevant. Will not cause
a syntax error, but is not used.

gs_page-typ = 'H'.

gs_page-info = 'Header 1'.

APPEND gs_page TO gt_page.

gs_page-typ = 'H'.

gs_page-info = 'Header 2'.

APPEND gs_page TO gt_page.

For Selections, the Key is printed (bold). It can be anything up to 20

bytes. It gets printed in order of code here, not by key value.

gs_page-typ = 'S'.

gs_page-key = 'And the winner is:'.

gs_page-info = 'Selection 1'.

APPEND gs_page TO gt_page.

gs_page-typ = 'S'.

gs_page-key = 'Runner up:'.

gs_page-info = 'Selection 2'.

APPEND gs_page TO gt_page.

For Action, Key is also irrelevant.

gs_page-typ = 'A'.

gs_page-info = 'Action goes here'.

APPEND gs_page TO gt_page.

ENDFORM. " build_page_header

REWARD IF USEFULL

Former Member · ‎09-28-2007

Hi

Thanks Naresh, I will workout with your program.

regards

Kesav.

Former Member · ‎09-28-2007

hi,

you dont need to code for the scroll bar, it comes automatically if data exceeds the screen size.

paste your code, so that we can provide more help.

Former Member · ‎09-28-2007

Hi,

This is my sample program, In this there is no problem with display the first 10 fields, after that i have commented the 11th field pls try to remove and excute it.

&----

*& Report ZKB_PO200907 *

*& *

&----

*& *

&----

REPORT ZKB_PO200907.

tables: ekko,

ekpo,

mara,

ekbe,

lfa1.

data : Begin of itab occurs 0,

EBELN like ekko-EBELN, " Purchase Document Number

LIFNR like lfa1-LIFNR, " Account Number of Vendor

NAME1 like lfa1-NAME1, " Vendor Name

EKORG like ekko-EKORG, " Purchase Organization

EKGRP like ekko-EKGRP, " Purchase Group

BUKRS like ekpo-BUKRS, " Company Code

MTART like mara-MTART, " Material Type

MATNR like mara-MATNR, " Material Number

MENGE like ekpo-MENGE, " Purchase Order Quantity

WESBS like ekbe-WESBS, " Goods Receipt blocked stock in order price unit

REEWR like ekbe-REEWR, " Invoice value entered

end of itab.

selection-screen : begin of block a with frame title text-001.

select-options : PO_No for ekko-ebeln.

select-options : PO_Date for ekko-bedat.

select-options : Vend_Co for lfa1-lifnr.

selection-screen : end of block a.

select a_{EBELN a}EKORG a_{EKGRP b}BUKRS b_{MENGE c}LIFNR c_{NAME1 d}MTART d_{MATNR e}WESBS e~REEWR

into corresponding fields of table itab

from ekko as a inner join ekpo as b on a_{ebeln = b}ebeln

inner join lfa1 as c on a_{lifnr = c}lifnr

inner join mara as d on b_{matnr = d}matnr

inner join ekbe as e on a_{ebeln = e}ebeln

where a~EBELN in PO_No

and bedat in PO_Date

and c~lifnr in Vend_Co.

write 2(139) sy-uline .

Loop at itab.

format color 3 intensified off.

write :/2 sy-vline, itab-EBELN,

sy-vline, itab-LIFNR,

24 sy-vline, itab-NAME1,

50 sy-vline, itab-EKORG,

59 sy-vline, itab-EKGRP,

68 sy-vline, itab-BUKRS,

77 sy-vline, itab-MTART,

86 sy-vline, itab-MATNR,

101 sy-vline, itab-MENGE,

120 sy-vline, itab-WESBS,

135 sy-vline, itab-REEWR, " Pls try it with comment and uncomment the field you will find the difference.

140 sy-vline.

Endloop.

write 2(139) sy-uline .

top-of-page.

write 2(139) sy-uline .

format color 5 intensified off.

write :/2 sy-vline, 'PO_Number',

15 sy-vline, 'Ve_Cod',

sy-vline, 'Ve_Name',

50 sy-vline, 'Pur_Or',

sy-vline, 'Pur_Gr',

sy-vline, 'Com_Co',

sy-vline, 'Mat_Ty',

86 sy-vline, 'Mat_No',

101 sy-vline, 'PO_Qty',

120 sy-vline, 'Go_Rct',

136 sy-vline, 'In.Ent', " Pls try it with comment and uncomment the field you will find the difference.

140 sy-vline.

Thanks in advance.

regards,

Kesav.

Former Member · ‎09-28-2007

I have attached my sample program