Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

ALV Tree Display

Former Member
0 Likes
585

hi I am using this code to display ALV Tree structure

CALL METHOD g_alv_tree->set_table_for_first_display

EXPORTING

is_hierarchy_header = l_hierarchy_header

CHANGING

it_fieldcatalog = gt_fieldcatalog

it_outtab = tbl_final. "table must be empty !

Now my problem is the program gives me syntax error saying that tbl_final is not compatible with it_outtab

tbl_final is a custom internal table with fields from many tables clustered into it

Whereas IT_OUTTAB has STANDARD TABLE as the requirement..

Please let me know what I should do... Points are guaranteed for every helpful answer



DATA: BEGIN OF tbl_final OCCURS 0,
*        ebeln    LIKE ekko-ebeln,
*        belnr    LIKE ekbe-belnr,
      ekorg    LIKE ekko-ekorg,
      ekgrp    LIKE ekko-ekgrp,
      lifnr    LIKE lfa1-lifnr,
      name1    TYPE lfa1-name1,
      werks    LIKE ekbe-werks,
      prctr    LIKE bsik-prctr,
      gjahr    LIKE ekbe-gjahr,
      zterm    LIKE bsik-zterm,
      zbd1t    LIKE bsik-zbd1t,
      zbd2t    LIKE bsik-zbd2t,
      zbd3t    LIKE bsik-zbd3t,
      tot_bal  TYPE bsik-dmbtr,
      am_nt_due TYPE bsik-dmbtr,
      tot_due  TYPE bsik-dmbtr,
      due_rg1  TYPE bsik-dmbtr,
      due_rg2  TYPE bsik-dmbtr,
      due_rg3  TYPE bsik-dmbtr,
      due_rg4  TYPE bsik-dmbtr,
      due_rg5  TYPE bsik-dmbtr,
      due_rg6  TYPE bsik-dmbtr,
      due_rg7  TYPE bsik-dmbtr,
      END OF tbl_final.

hi I am using this code to display ALV Tree structure

CALL METHOD g_alv_tree->set_table_for_first_display

EXPORTING

is_hierarchy_header = l_hierarchy_header

CHANGING

it_fieldcatalog = gt_fieldcatalog

it_outtab = tbl_final. "table must be empty !

Now my problem is the program gives me syntax error saying that tbl_final is not compatible with it_outtab

tbl_final is a custom internal table with fields from many tables clustered into it

Whereas IT_OUTTAB has STANDARD TABLE as the requirement..

Please let me know what I should do... Points are guaranteed for every helpful answer



DATA: BEGIN OF tbl_final OCCURS 0,
*        ebeln    LIKE ekko-ebeln,
*        belnr    LIKE ekbe-belnr,
      ekorg    LIKE ekko-ekorg,
      ekgrp    LIKE ekko-ekgrp,
      lifnr    LIKE lfa1-lifnr,
      name1    TYPE lfa1-name1,
      werks    LIKE ekbe-werks,
      prctr    LIKE bsik-prctr,
      gjahr    LIKE ekbe-gjahr,
      zterm    LIKE bsik-zterm,
      zbd1t    LIKE bsik-zbd1t,
      zbd2t    LIKE bsik-zbd2t,
      zbd3t    LIKE bsik-zbd3t,
      tot_bal  TYPE bsik-dmbtr,
      am_nt_due TYPE bsik-dmbtr,
      tot_due  TYPE bsik-dmbtr,
      due_rg1  TYPE bsik-dmbtr,
      due_rg2  TYPE bsik-dmbtr,
      due_rg3  TYPE bsik-dmbtr,
      due_rg4  TYPE bsik-dmbtr,
      due_rg5  TYPE bsik-dmbtr,
      due_rg6  TYPE bsik-dmbtr,
      due_rg7  TYPE bsik-dmbtr,
      END OF tbl_final.

3 REPLIES 3
Read only

former_member192429
Active Participant
0 Likes
565

Try to give the same type of it_Outtab to tbl_final

-Kriss

Read only

former_member194669
Active Contributor
0 Likes
565

Hi,


CALL METHOD g_alv_tree->set_table_for_first_display
EXPORTING
is_hierarchy_header = l_hierarchy_header
CHANGING
it_fieldcatalog = gt_fieldcatalog
it_outtab = tbl_final[].  "<<<< change this way

aRs

Read only

0 Likes
565

Thanks it solved my issue