topic Re: GRID environment. in Application Development and Automation Discussions

GRID environment.

Former Member — Tue, 26 Feb 2008 09:28:15 GMT

Hi,

Using ALV LIST Function Modules, I can write directly at th TOP_OF_PAGE event, using a "write" statement, in addition to o instead of using the funtion: 'REUSE_ALV_COMMENTARY_WRITE'. placed to "write" statement inside the TOP_OF_PAGE subroutine. I used the "write" statement because it allows me to prin longer lines at TOP_OF_PAGE than I can have wit 'REUSE_ALV_COMMENTARY_WRITE'

This approach does not seem to work using GRID function modul 'REUSE_ALV_GRID_DISPLAY' with 'REUSE_ALV_COMMENTARY_WRITE'

Does anyone know how I can can print long lines (130 characters in the header area of an ALV report created with GRI functions.

Here is the function:

CALL FUNCTION 'REUSE_ALV_LIST_DISPLAY'

EXPORTING

I_CALLBACK_PROGRAM = G_REPID

I_CALLBACK_USER_COMMAND = 'USER_COMMAND'

i_structure_name =

IS_LAYOUT = GS_LAYOUT

IT_FIELDCAT = GT_FIELDCAT[]

IT_EXCLUDING =

IT_SPECIAL_GROUPS = GT_SP_GROUP[]

IT_SORT = GT_SORT[]

it_filter =
IS_SEL_HIDE =

I_DEFAULT = G_DEFAULT

I_SAVE = G_SAVE

IS_VARIANT = G_VARIANT

IT_EVENTS = GT_EVENTS[]

IT_EVENT_EXIT =

IS_PRINT = GS_PRINT

I_SCREEN_START_COLUMN = 0
I_SCREEN_START_LINE = 0
I_SCREEN_END_COLUMN = 0
I_SCREEN_END_LINE = 0
IMPORTING
E_EXIT_CAUSED_BY_CALLER =

TABLES

T_OUTTAB = I_EXTRACT.

Here is the function:

form top_of_page.

write:/ 'Top of page ', 70 'Page'.

call function 'REUSE_ALV_COMMENTARY_WRITE'

EXPORTING

it_list_commentary = gt_list_top_of_page.

ENDFORM. "top_of_page

This prints the line with the write statement, followed b whatever is in the table gt_list_top_of_page.

I want to be able to do the same thing under a GRID environment.

Thanks,

Re: GRID environment.

sreelatha_gullapalli — Tue, 26 Feb 2008 09:55:18 GMT

check the following program

Sample programs on ALV Grid

report zbnstest.

TABLES AND DATA DECLARATION.

*TABLES: mara,makt.",marc.

data syrepid like sy-repid.

data sydatum(10). " LIKE sy-datum.

data sypagno(3) type n.

WHEN USING MORE THAN ONE TABLE IN ALV WE NEEED TO DECLARE THE TYPE
GROUP (TYPE-POOLS--------->SLIS)

type-pools : slis.

INTERNAL TABLE DECLARATION.

INTERNAL TABLE TO HOLD THE VALUES FROM THE MARA TABLE

data: begin of t_mara occurs 0,

matnr like mara-matnr,

meins like mara-meins,

mtart like mara-mtart,

matkl like mara-matkl,

end of t_mara.

INTERNAL TABLE TO HOLD THE CONTENTS FROM THE EKKO TABLE

data : begin of t_marc occurs 0,

matnr like mara-matnr,

werks like marc-werks,

minbe like marc-minbe.

data: end of t_marc.

INTERNAL TABLE TO HOLD THE VALUES FROM MAKT TABLE.

data : begin of t_makt occurs 0,

matnr like mara-matnr,

maktx like makt-maktx,

spras like makt-spras,

end of t_makt.

INTERNAL TABLE WHICH ACTUALLY MERGES ALL THE OTHER INTERNAL TABLES.

data: begin of itab1 occurs 0,

matnr like mara-matnr,

meins like mara-meins,

maktx like makt-maktx,

spras like makt-spras,

werks like marc-werks,

minbe like marc-minbe,

end of itab1.

THE FOLLOWING DECLARATION IS USED FOR DEFINING THE FIELDCAT
AND THE LAYOUT FOR THE ALV.
HERE AS slis_t_fieldcat_alv IS A INTERNAL TABLE WITHOUT A HEADER LINE
WE EXPLICITELY DEFINE AN INTERNAL TABLE OF THE SAME STRUCTURE AS THAT
OF slis_t_fieldcat_alv BUT WITH A HEADER LINE IN THE DEFINITION.
THIS IS DONE TO MAKE THE CODE SIMPLER.
OTHERWISE WE MAY HAVE TO DEFINE THE STRUCTURE AS IN THE NORMAL SAP
PROGRAMS.
IN THE FIELDCATALOG TABLE WE ACTUALLY PASS THE FIELDS FROM ONE OR
MORE TABLES AND CREATE A STRUCTURE
IN THE LAYOUT STRUCTURE WE BASICALLY DEFINE THE FORMATTING OPTIONS
LIKE DISPLAY IN THE ZEBRA PATTERN ,THE HOTSPOT OPTIONS ETC.

data: fieldcatalog type slis_t_fieldcat_alv with header line,

fieldlayout type slis_layout_alv.

DECLARING THE EVENTTABLE INTERNL TABLE FOR USING EVENTS LIKE
TOP-OF-PAGE ETC.

data : eventstab type slis_t_event with header line.

DECLARING AN INTERNAL TABLE TO HOLD THE DATA FOR THE TOP-OF-PAGE

data : heading type slis_t_listheader with header line.

data : heading1 type slis_t_listheader with header line.

data : heading2 type slis_t_listheader with header line.

data : heading3 type slis_t_listheader with header line.

data : heading4 type slis_t_listheader with header line.

data : heading5 type slis_t_listheader with header line.

data : heading6 type slis_t_listheader with header line.

data : heading7 type slis_t_listheader with header line.

data : heading8 type slis_t_listheader with header line.

STRUCTURE TO PASS THE COLOR ATTRIBUTES FOR DISPLAY.

data : colorstruct type slis_coltypes.

INITIALIZATION. *

initialization.

syrepid = sy-repid.

sypagno = sy-pagno.

clear fieldcatalog.

START-OF-SELECTION. *

start-of-selection.

SUBROUTINE TO POPULATE THE COLORSTRUCT

perform fill_colorstruct using colorstruct.

SUBROUTINE TO POPULATE THE FIELDS OF THE FIELD CATALOGUE

perform populate_fieldcatalog.

SUBROUTINE TO SELECT DATA FROM VARIOUS TABLES AND POPULATE IT IN THE
INTERNAL TABLE.

perform selectdata_and_sort.

SUBROUTINE TO POPULATE THE LAYOUT STRUCTURE.

perform populate_layout using fieldlayout.

SUBROUTINE TO CALL THE FUNCTION MERGE TO ENSURE PROPER DISPLAY.

perform merge_fieldcatalog.

SUBROUTINE TO POPULATE THE EVENTSTAB.

perform fill_eventstab tables eventstab.

SUBROUTINE TO POPULATE THE HEADING TABLES.

perform fill_headingtable tables heading using 'HEADING'.

perform fill_headingtable tables heading1 using 'HEADING1'.

perform fill_headingtable tables heading2 using 'HEADING2'.

perform fill_headingtable tables heading3 using 'HEADING3'.

perform fill_headingtable tables heading4 using 'HEADING4'.

perform fill_headingtable tables heading5 using 'HEADING5'.

perform fill_headingtable tables heading6 using 'HEADING6'.

perform fill_headingtable tables heading7 using 'HEADING7'.

perform fill_headingtable tables heading8 using 'HEADING8'.

SUBROUTINE TO DISPLAY THE LIST.

perform display_alv_list.

FORMS

IN THIS SUBROUTINE WE POPULATE THE FIELDCATALOG TABLE WITH THE NAMES
OF THE TABLE,FIELDNAME,WHETHER IT IS KEY FIELD OR NOT,HEADING AND
COLUMN JUSTIFICATION.

form populate_fieldcatalog.

perform fill_fields_of_fieldcatalog tables fieldcatalog

using 'ITAB1' 'MATNR' 'X' .

perform fill_fields_of_fieldcatalog tables fieldcatalog

using 'ITAB1' 'MEINS' ' '.

perform fill_fields_of_fieldcatalog tables fieldcatalog

using 'ITAB1' 'MAKTX' ' ' .

perform fill_fields_of_fieldcatalog tables fieldcatalog

using 'ITAB1' 'MTART' ' ' .

perform fill_fields_of_fieldcatalog tables fieldcatalog

using 'ITAB1' 'MATKL' ' ' .

perform fill_fields_of_fieldcatalog tables fieldcatalog

using 'ITAB1' 'SPRAS' ' ' .

perform fill_fields_of_fieldcatalog tables fieldcatalog

using 'ITAB1' 'WERKS' ' ' .

perform fill_fields_of_fieldcatalog tables fieldcatalog

using 'ITAB1' 'MINBE' ' ' .

endform. " POPULATE_FIELDCATALOG

----

FORM FILL_FIELDS_OF_FIELDCATALOG *

----

........ *

----

--> FIELDCATALOG *
--> P_TABNAME *
--> P_FIELDNAME *
--> P_KEY *
--> P_KEY *

----

form fill_fields_of_fieldcatalog tables fieldcatalog

structure fieldcatalog

using p_tabname

p_fieldname

p_key.

p_no_out.

fieldcatalog-tabname = p_tabname.

fieldcatalog-fieldname = p_fieldname.

fieldcatalog-key = p_key.

fieldcatalog-emphasize = '1234'.

*fieldcatalog-no_out = p_no_out.

append fieldcatalog.

endform. " FILL_FIELDSOFFIELDCATALOG

----

FORM POPULATE_LAYOUT *

----

........ *

----

--> FIELDLAYOUT *

----

form populate_layout using fieldlayout type slis_layout_alv.

fieldlayout-f2code = '&ETA' .

fieldlayout-zebra = 'X'.

FOR THE WINDOW TITLE.

fieldlayout-window_titlebar = 'ALV with Events'.

fieldlayout-colwidth_optimize = 'X'.

fieldlayout-no_vline = ' '.

*fieldlayout-no_input = 'X'.

fieldlayout-confirmation_prompt = ''.

fieldlayout-key_hotspot = 'X'.

This removes the column headings if the flag is set to 'X'

fieldlayout-no_colhead = ' '.

*fieldlayout-hotspot_fieldname = 'MAKTX'.

fieldlayout-detail_popup = 'X'.

fieldlayout-coltab_fieldname = 'X'.

endform. " POPULATE_LAYOUT

----

FORM SELECTDATA_AND_SORT *

----

........ *

----

form selectdata_and_sort.

select matnr meins mtart matkl from mara

into corresponding fields of t_mara

up to 500 rows .

select matnr maktx spras from makt

into corresponding fields of t_makt

where matnr = t_mara-matnr and

spras = sy-langu.

select matnr werks minbe from marc

into corresponding fields of t_marc

where matnr = t_mara-matnr.

append t_marc.

endselect.

append t_makt.

endselect.

append t_mara.

endselect.

perform populate_itab1.

sort itab1 by matnr.

endform. " SELECTDATA_AND_SORT

----

FORM MERGE_FIELDCATALOG *

----

........ *

----

form merge_fieldcatalog.

call function 'REUSE_ALV_FIELDCATALOG_MERGE'

exporting

i_program_name = syrepid

i_internal_tabname = 'ITAB1'

i_structure_name = 'COLORSTRUCT'
I_CLIENT_NEVER_DISPLAY = 'X'

i_inclname = syrepid

changing

ct_fieldcat = fieldcatalog[]

exceptions

inconsistent_interface = 1

program_error = 2

others = 3.

endform. " MERGE_FIELDCATALOG

IN THIS FUNCTION THE MINIMUM PARAMETERS THAT WE NEED TO PASS IS AS
FOLLOWS:-
i_callback_program --> CALLING PROGRAM NAME
i_structure_name --> STRUCTURE NAME.
is_layout --> LAYOUT NAME.
it_fieldcat ---> BODY OF THE FIELD CATALOGUE INTERNAL TABLE

form display_alv_list.

call function 'REUSE_ALV_LIST_DISPLAY'

exporting

I_INTERFACE_CHECK = ' '

i_callback_program = syrepid

I_CALLBACK_PF_STATUS_SET = ' '
I_CALLBACK_USER_COMMAND = ' '

i_structure_name = 'ITAB1'

is_layout = fieldlayout

it_fieldcat = fieldcatalog[]

IT_EXCLUDING =
IT_SPECIAL_GROUPS =
IT_SORT =
IT_FILTER =
IS_SEL_HIDE =
I_DEFAULT = 'X'
THE FOLLOWING PARAMETER IS SET AS 'A' INORDER TO DISPLAY THE STANDARD
TOOL BAR

i_save = 'A'

IS_VARIANT = ' '

it_events = eventstab[]

IT_EVENT_EXIT =
IS_PRINT =
I_SCREEN_START_COLUMN = 0
I_SCREEN_START_LINE = 0
I_SCREEN_END_COLUMN = 0
I_SCREEN_END_LINE = 0
IMPORTING
E_EXIT_CAUSED_BY_CALLER =
ES_EXIT_CAUSED_BY_USER =

tables

t_outtab = itab1

exceptions

program_error = 1

others = 2.

endform. " DISPLAY_ALV_LIST

&----

*& Form POPULATE_ITAB1

&----

text

----

--> p1 text
<-- p2 text

----

form populate_itab1.

loop at t_mara.

loop at t_makt where matnr = t_mara-matnr.

loop at t_marc where matnr = t_mara-matnr.

move-corresponding t_mara to itab1.

move-corresponding t_makt to itab1.

move-corresponding t_marc to itab1.

append itab1.

endloop.

endform. " POPULATE_ITAB1

&----

*& Form FILL_EVENTSTAB

&----

text

----

-->P_EVENTSTAB text *

----

form fill_eventstab tables p_eventstab structure eventstab.

WHEN THE FOLLOWING FUNCTION IS CALLED THE SYSTEM POPULATES THE
INTERNAL TABLE EVENTSTAB WITH A LIST OF EVENTS NAME.
AS SHOWN BELOW WHEN USING I_LIST_TYPE = 0 THE FUNCTION RETURNS 14
EVENTS NAME.

call function 'REUSE_ALV_EVENTS_GET'

exporting

i_list_type = 0

importing

et_events = p_eventstab[]

exceptions

list_type_wrong = 1

others = 2.

BY CALLING THE ABOVE FUNCTION WE FIRST POPULATE THE EVENTSTAB WITH
THE PREDEFINED EVENTS AND THEN WE MOVE THE FORM NAME AS SHOWN BELOW.
WE ASSIGN A FORM NAME TO THE EVENT AS REQUIRED BY THE USER.
FORM NAME CAN BE ANYTHING.THE PERFORM STATEMENT FOR THIS FORM
IS DYNAMICALY CALLED.

read table p_eventstab with key name = slis_ev_top_of_page.

if sy-subrc = 0 .

move 'TOP_OF_PAGE' to p_eventstab-form.

append p_eventstab.

endif.

read table p_eventstab with key name = slis_ev_top_of_coverpage.

if sy-subrc = 0 .

move 'TOP_OF_COVERPAGE' to p_eventstab-form.

append p_eventstab.

endif.

read table p_eventstab with key name = slis_ev_end_of_coverpage .

if sy-subrc = 0 .

move 'END_OF_COVERPAGE' to p_eventstab-form.

append p_eventstab.

endif.

read table p_eventstab with key name = slis_ev_foreign_top_of_page.

if sy-subrc = 0 .

move 'FOREIGN_TOP_OF_PAGE' to p_eventstab-form.

append p_eventstab.

endif.

read table p_eventstab with key name = slis_ev_foreign_end_of_page.

if sy-subrc = 0 .

move 'FOREIGN_END_OF_PAGE' to p_eventstab-form.

append p_eventstab.

endif.

read table p_eventstab with key name = slis_ev_list_modify.

if sy-subrc = 0 .

move 'LIST_MODIFY' to p_eventstab-form.

append p_eventstab.

endif.

read table p_eventstab with key name = slis_ev_top_of_list.

if sy-subrc = 0 .

move 'TOP_OF_LIST' to p_eventstab-form.

append p_eventstab.

endif.

read table p_eventstab with key name = slis_ev_end_of_page.

if sy-subrc = 0 .

move 'END_OF_PAGE' to p_eventstab-form.

append p_eventstab.

endif.

read table p_eventstab with key name = slis_ev_end_of_list .

if sy-subrc = 0 .

move 'END_OF_LIST' to p_eventstab-form.

append p_eventstab.

endif.

endform. " FILL_EVENTSTAB

&----

*& Form FILL_HEADINGTABLE

&----

text

----

-->P_HEADING text *

----

form fill_headingtable tables p_heading structure heading

using tablename.

case tablename.

when 'HEADING'.

p_heading-typ = 'H'.

concatenate

' REPORT NAME:-' syrepid

' ABB Industry Pte Ltd' into p_heading-info.

append p_heading.

write sy-datum using edit mask '__/__/____' to sydatum.

concatenate

' DATE:-' sydatum ' USER: ' sy-uname 'PAGE NO:' sypagno

into p_heading-info.

append p_heading.

when 'HEADING1'.

p_heading-typ = 'H'.

p_heading-info = 'TOP-OF-COVER-PAGE'.

append p_heading.

when 'HEADING2'.

p_heading-typ = 'H'.

p_heading-info = 'END-OF-COVER-PAGE'.

append p_heading.

when 'HEADING3'.

p_heading-typ = 'H'.

p_heading-info = 'FOREIGN-TOP-OF-PAGE'.

append p_heading.

when 'HEADING4'.

p_heading-typ = 'H'.

p_heading-info = 'FOREIGN-END-OF-PAGE'.

append p_heading.

WHEN 'HEADING5'.
P_HEADING-TYP = 'H'.
P_HEADING-INFO = 'LIST-MODIFY'.
APPEND P_HEADING.

when 'HEADING6'.

p_heading-typ = 'H'.

p_heading-info = 'END-OF-PAGE'.

append p_heading.

when 'HEADING7'.

p_heading-typ = 'H'.

p_heading-info = 'END-OF-LIST'.

append p_heading.

when 'HEADING8'.

p_heading-typ = 'H'.

p_heading-info = 'TOP-OF-LIST'.

append p_heading.

endcase.

endform. " FILL_HEADINGTABLE

----

FORM TOP_OF_PAGE *

----

........ *

----

form top_of_page.

call function 'REUSE_ALV_COMMENTARY_WRITE'

exporting

it_list_commentary = heading[]

exceptions

others = 1.

endform.

&----

*& Form FILL_COLORSTRUCT

&----

text

----

-->P_COLORSTRUCT text *

----

form fill_colorstruct using p_colorstruct type slis_coltypes .

p_colorstruct-heacolfir-col = 6.

p_colorstruct-heacolfir-int = 1.

p_colorstruct-heacolfir-inv = 1.

endform. " FILL_COLORSTRUCT

----

FORM TOP_OF_COVERPAGE *

----

........ *

----

form top_of_coverpage.

call function 'REUSE_ALV_COMMENTARY_WRITE'

exporting

it_list_commentary = heading1[]

exceptions

others = 1.

endform.

----

FORM END_OF_COVERPAGE *

----

........ *

----

form end_of_coverpage.

call function 'REUSE_ALV_COMMENTARY_WRITE'

exporting

it_list_commentary = heading2[]

exceptions

others = 1.

endform.

----

FORM FOREIGN_TOP_OF_PAGE *

----

........ *

----

form foreign_top_of_page.

call function 'REUSE_ALV_COMMENTARY_WRITE'

exporting

it_list_commentary = heading3[]

exceptions

others = 1.

endform.

----

FORM FOREIGN_END_OF_PAGE *

----

........ *

----

form foreign_end_of_page.

call function 'REUSE_ALV_COMMENTARY_WRITE'

exporting

it_list_commentary = heading4[]

exceptions

others = 1.

endform.

----

FORM LIST_MODIFY *

----

........ *

----

*FORM LIST_MODIFY.

CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
EXPORTING
IT_LIST_COMMENTARY = HEADING5[]
EXCEPTIONS
OTHERS = 1.

*ENDFORM.

----

FORM END_OF_PAGE *

----

........ *

----

form end_of_page.

call function 'REUSE_ALV_COMMENTARY_WRITE'

exporting

it_list_commentary = heading6[]

exceptions

others = 1.

endform.

----

FORM END_OF_LIST *

----

........ *

----

form end_of_list.

call function 'REUSE_ALV_COMMENTARY_WRITE'

exporting

it_list_commentary = heading7[]

exceptions

others = 1.

endform.

----

FORM TOP_OF_LIST *

----

........ *

----

form top_of_list.

call function 'REUSE_ALV_COMMENTARY_WRITE'

exporting

it_list_commentary = heading8[]

exceptions

others = 1.

endform.

*--- End of Program

Do you have a ABAP Question?

hope it will help you

regards

sreelatha gullapalli

Re: GRID environment.

Former Member — Tue, 26 Feb 2008 10:33:05 GMT

good

in your declarations, add these:

DATA: gt_list_end_of_list TYPE slis_t_listheader,

gt_list_top_of_page TYPE slis_t_listheader,

it_events TYPE slis_t_event.

then i suggest you make one major subroutine say, FORM build_events_table_for_alv then call that before you display your ALV by REUSE_ALV_GRID_DISPLAY or REUSE_ALV_LIST_DISPLAY.

in the subroutine you put these lines of codes:

FORM build_events_table_for_alv .

CONSTANTS: lcon_top(11) TYPE c VALUE 'TOP_OF_PAGE',

lcon_eol(11) TYPE c VALUE 'END_OF_LIST'.

CLEAR: wa_events.

REFRESH: it_events.

wa_events-name = lcon_top.

wa_events-form = lcon_top.

APPEND wa_events TO it_events.

CLEAR: wa_events.

wa_events-name = lcon_eol.

wa_events-form = lcon_eol.

APPEND wa_events TO it_events.

ENDFORM. " build_events_table_for_alv

then another two subroutines:

FORM top_of_page.

DATA: it_listhead TYPE slis_t_listheader,

lw_listhead LIKE LINE OF it_listhead.

DATA: l_text TYPE string.

CLEAR lw_listhead.

lw_listhead-typ = 'H'.

lw_listhead-info = 'Title of Your Header'. " place your text header here or a VARIABLE you have to pass

APPEND lw_listhead TO it_listhead.

CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'

EXPORTING

it_list_commentary = it_listhead.

ENDFORM. "TOP_OF_PAGE

&----

*& Form END_OF_LIST

&----

FORM end_of_list.

this can be blank.

ENDFORM. "end_of_list

finally in your REUSE_ALV_GRID_DISPLAY or REUSE_ALV_LIST_DISPLAY, in the parameter it_events, pass it_events[] like:

CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'

EXPORTING

i_callback_program = callback_repid

i_bypassing_buffer = 'X'

i_structure_name = l_struct

is_layout = is_layout

it_fieldcat = it_fieldcat[]

it_sort = it_sort[]

i_save = 'X'

it_events = it_events[]

TABLES

t_outtab = i_wrongzz[]

EXCEPTIONS

program_error = 1

OTHERS = 2.

thanks

mrutyun^

Re: GRID environment.

Former Member — Tue, 26 Feb 2008 11:08:44 GMT

simplest way is to split the tezt in multiple lines and write the lines in TOP OF PAGE.

Re: GRID environment.

Former Member — Wed, 27 Feb 2008 05:11:06 GMT

but I think that

there is no way to do lines longer than 65 characters with ALV Grid

and the REUSE FMs.

Sorry I couldn't be more positive.

Re: GRID environment.

Former Member — Thu, 28 Feb 2008 05:11:48 GMT

Hi Mukesh ,

Hope this will help you.

Normally in ALV grid TOP_OF_PAGE, we cannot display information of more than 60 characters long. This is due to the limitation of the FM REUSE_ALV_COMMENTARY_WRITE. Usually we call this FM from the subroutine that is linked with TOP_OF_PAGE event.

CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'

EXPORTING

it_list_commentary =

i_logo =

i_end_of_list_grid =

.*"----

""Lokale Schnittstelle:

*" IMPORTING

*" VALUE(IT_LIST_COMMENTARY) TYPE SLIS_T_LISTHEADER

*" REFERENCE(I_LOGO) OPTIONAL

*" REFERENCE(I_END_OF_LIST_GRID) OPTIONAL

*"----

In this above FM, exporting parameter ‘IT_LIST_COMMENTARY’ contains a field ‘INFO’ that is only 60 characters long. And it is responsible for displaying the information in the TOP_OF_PAGE area.

Solution:

To overcome this limitation we can use dynamic document, which can be implemented through the class CL_DD_DOCUMENT. As dynamic documents use HTML viewer control so instead of triggering the TOP_OF_PAGE event we should trigger event of HTML TOP_OF_PAGE.

First create a subroutine for top of page in HTML format and send that name in I_CALLBACK_HTML_TOP_OF_PAGE parameter of ALV function module. The input parameter for this subroutine will be a variable of class CL_DD_DOCUMENT.

----

FORM html_top_of_page *

----

FORM html_top_of_page USING top TYPE REF TO cl_dd_document.

data: l_text(255) type c.

do 180 times. l_text+sy-index(1) = '*'.

enddo. CALL METHOD top->add_text EXPORTING text = 'Hello world '

sap_style = 'heading' .

CALL METHOD top->add_gap EXPORTING width = 200.

CALL METHOD top->add_picture EXPORTING picture_id = 'ENJOYSAP_LOGO'.

CALL METHOD top->NEW_LINE( ).

CALL METHOD top->add_text EXPORTING

text = l_text.ENDFORM.* Display ALV grid

CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'

EXPORTING

i_callback_html_top_of_page = 'HTML_TOP_OF_PAGE'

i_callback_program = g_repid

i_structure_name = 'SFLIGHT'

TABLES

t_outtab = gt_outtab.Output:

Limitations:

As dynamic documents use SAP HTML Viewer control internally, so whatever limitations exist for SAP HTML Viewer, same limitations hold true for dynamic documents also.

Reward if helpful.

Regards,

Sreekar.Kadiri