Hierarchical List

[Former Member]

hello,

i want to display a hierchical lsit with the function 'REUSE_ALV_HIERSEQ_LIST_DISPLAY'. Per every header line, several item lines shall be put out. This doesn't work, with my trial to declare the key_info...

header01 = attribute

item02 = same attribute (but several lines for the header attribute)

Can you help me, is there more to group??

Many thanks,

Stef

[Former Member]

Hi, me again. Thanks I managed it, but I knew already that example...

Can you perhaps help with this: How do I get column headers into the list?? With setting a layout?

Many thanks.

[Former Member]

Hi,

What you actually mean by "get column headers into the list"?

If you mean columns header text - they are define in field catalog. You know that field catalog is the table. Every line of this table corresponds to the output table column and describe HOW the column will be displayed on.

There are a lot of property for the columns - length, position, icon, hotspot and so on. In particular in field catalog for every columns exist following fields:

<b>seltext_l</b>

<b>seltext_m</b>

<b>seltext_s</b>

They define correspondently long, medium and short text. They are displayed as column headers for.

Also there is field <b>rollname</b>, which define link to the Data Dictionary type. In this element is set in field catalog, then columns header text will be read from Data Dictionary.

Usually these fields are filled during building field catalog using REUSE_ALV_FIELDCATALOG_MERGE. But in some cases you can or have to fill them manually.

Set break-poing before

CALL FUNCTION 'REUSE_ALV_HIERSEQ_LIST_DISPLAY'

in you program and check the field catalog.

If you mean by "get column headers into the list" showing/hiding all columns headers completely, then this is define in layout. The attribute <b>no_colhead</b> is responsible for this.

[Former Member]

Hi Stefanie,

It is very difficult to say what is wrong in your program. Please have a look on example report:

BCALV_TEST_HIERSEQ_LIST in packet SLIS.

Concerning the key_info, I didn't undestand your code sample completely...

My feeling is that you shoudld use something like that:

ls_keyinfo-header01 = 'FIELDNAME1'.

ls_keyinfo-item01 = 'FIELDNAME1'.

ls_keyinfo-header02 = 'FIELDNAME2'.

ls_keyinfo-item02 = 'FIELDNAME2'.

and so on.

and then pass this structure (ls_keyinfo) to the FM

'REUSE_ALV_HIERSEQ_LIST_DISPLAY'

The FIELDNAME1 for example is the columns which present in both - MASTER(header) and SLAVE(items) tables, which you pass to 'REUSE_ALV_HIERSEQ_LIST_DISPLAY'.