Skip to Content
author's profile photo
Former Member

logo in alv

how to insert a logo in alv ,i know the function module -commentry_get but it need some more thing .please let me knopw

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

3 Answers

  • Best Answer
    author's profile photo
    Former Member
    Posted on Sep 28, 2007 at 07:01 AM

    hi,

    follow the steps:

    FORM eventtab_build USING rt_events TYPE slis_t_event.

    DATA: ls_event TYPE slis_alv_event.

    CALL FUNCTION 'REUSE_ALV_EVENTS_GET'

    EXPORTING

    i_list_type = 0

    IMPORTING

    et_events = rt_events.

    READ TABLE rt_events WITH KEY name = slis_ev_top_of_page

    INTO ls_event.

    IF sy-subrc = 0.

    MOVE g_top_of_page TO ls_event-form.

    APPEND ls_event TO rt_events.

    ENDIF.

    ENDFORM. " eventtab_build

    2.

    FORM top_of_page.

    CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'

    EXPORTING

    i_logo = 'TIMES_LOGO'

    it_list_commentary = gt_list_top_of_page.

    ENDFORM. "top_of_page

    make use of this forms and pass it to call fintion 'reuse_alv_grid_diplay'

    in top_of_page and events parameters.

    Add comment
    10|10000 characters needed characters exceeded

  • Posted on Sep 28, 2007 at 06:56 AM

    Srujana,

    refer to this link...

    logo-in-alv

    also see this

    call function 'REUSE_ALV_COMMENTARY_WRITE'

    exporting

    it_list_commentary = t_header.

    i_logo = 'Z_LOGO'.

    endform.

    Upload Logo for REUSE_ALV_COMMENTARY_WRITE

    For those who wish to upload and use a picture in your ALV abap reports.

    Steps for uploading Logo :-:

    1. Goto the transaction OAER

    2. Enter the class name as 'PICTURES'

    3. Enter the class type as 'OT'

    4. Enter the object key as the name of the logo you wish to give

    5. Execute

    6. Then in the new screen select Standard doc. types in bottom window

    Click on the Screen icon

    Now, it will ask for the file path where you have to upload the logo

    7. Now you can use this logo in REUSE_ALV_COMMENTARY_WRITE

    or

    Import Logo and Background Picture for Reporting

    In this step, you can import a customer-specific logo and a background picture into the R/3 System. These will be displayed in the header area of reports in HR Funds and Position Management.

    From the SPRO:

    HR Funds and Position Management --> Dialog Control --> Customize Reporting Interface --> Import Logo and Background Picture for Reporting.

    Activities

    1. Enter the Name of your logo/background picture as an object key in the initial screen.

    2. Make sure that the class name is PICTURES, and the class type is OT.

    3. Choose Execute.

    4. Double-click the document type Picture on the Create tab page. A dialog box will appear in which you can enter the path in which the logo/background picture can be found.

    5. Enter the path and choose Open. The logo will be uploaded into the current R/3 System. If the logo/background picture is to be transported into other systems as well, choose Transport.

    6. Return to the initial screen and repeat the procedure after having entered the Name of your background picture as an object key.

    Please note that the logo/background picture can only be displayed in ALV-based reports with an HTML header. Manually programmed reports such as business distribution plans are not based on the ALV.

    If you have selected several initial objects, ALV-based reports in HR Funds and Position Management will automatically use a hiearchical-sequential display. A logo is not displayed here either. Note also that the logo cannot be printed (see print preview in program).

    Make sure that the logo does not exceed a height of 100 pixels because it would mean that the header of the report will be scrollable.

    OR

    use OAER Transaction

    Reward points if useful

    Add comment
    10|10000 characters needed characters exceeded

  • author's profile photo
    Former Member
    Posted on Sep 28, 2007 at 08:08 AM

    Hi

    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

    <b>REWARD IF USEFULL</b>

    Add comment
    10|10000 characters needed characters exceeded