Skip to Content

ALV: how to save context space for large tables ?

Dear collegues,

We are displaying an ALV table that is quite large. Therefore, the corrsponding DDIC structure and the WD context is large. This has an impact on performance and the load size of the program. Now we will enhance the ALV table again.

Example: for an icon and its explaining tooltip that are displayed in the ALV: there is are context fields required like "SOURCE_FIELDNAME" for the tooltip as well as for for the icon. They need a lot of characters for each tooltip and icon).

Question: do you have an idea, how to save context space for those ALV fields ?

Best regards,

Christian

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Oct 08, 2008 at 02:03 PM

    >We are displaying an ALV table that is quite large.

    Do you mean quite large as in a large number of columns or as in a large number of rows (or both)? I assume that the problem is probably more related to a large number of rows. For very large tables, you should consider using the table instead of the ALV. For very large tables you can even use a technique called context paging to keep only a subset of the data in the context memory at a time. Here is a recent blog that I created on the topic with demonstrations of different techniques for table sharing, shared memory, and context paging when dealing with large tables in Web Dynpro ABAP:

    Web Dynpro ABAP: How Fast Can You Consume 1 Million Rows?

    Add comment
    10|10000 characters needed characters exceeded

  • Oct 15, 2008 at 01:46 PM

    Hi Thomas,

    thank you for your hints. Unfortunately, we can not change our application from ALV to WD table (because the application is too huge and we need a lot of ALV features).

    My Question is whether your "context paging" can also be used for ALVs ?

    By the way:

    do you have experience with big Load Sizes (2 MB) of WDA Component ?

    (SE80 -> context menu on WD component -> Check -> Generation limit->Load Size)

    Best regards,

    Christian

    Add comment
    10|10000 characters needed characters exceeded

    • >My Question is whether your "context paging" can also be used for ALVs ?

      No, sorry. It can only be used with the native Table UI element.

      >do you have experience with big Load Sizes (2 MB) of WDA Component ?

      That is a sign your component is too large and should be split into small components.