This never was an issue. At least, your post is first one that has such complains.
Please describe your data structure used as table source -- cardinality, existence of child nodes, supply function code/data source (i.e. Adaptive RFC, WS, etc)
I never haven't this problem but I think that the navigation performance you have depends on data load contained into the table, so you probably must consider a buffering of that table.
The buffering concept that I mean concearn the loading of the table data in blocks of pre-fixed dimension.
If your table is, for example, the output of a RFC with a great order of data, you could modify the business logic of that RFC making possible to reach out the table elements at block of 100 (i.e.) records at time.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.