CODEWITHSUNDEEP
abapalvrtts
icbytes
icbytes

Reputation: 1851

Any ALV-specifics with itab created by RTTS?

I create internal table by two steps, both refer to the RTTS-techniques. The first step loads and parses a tab-delimited file into a table. The second step reads this table by RTTI, then, hardcoded, adds some other columns in front of the old columns from the file and, finally adds the old fields back again, the table now has about 12 new hardcoded columns, in front of those from the file. The RTTS helps to create the final table, which then is passed as the data source to the ALV grid.

My former requirement did not take into account that the ALV-grid-toolbar-functions will ever be needed by the end-user, however, as always, this has changed. I enabled the toolbar functions, the default ones, without any custom button.

So, now the user can remove some columns from the display or add them back again, she/he can also change their order. Everything is fine but I never encountered this situation with a table, which is created during runtime.

Are there special culprits I need to be aware of ?

Upvotes: 0

Views: 364

Answers (2)

Denis
Denis

Reputation: 31

From my experience, ALV column maximum size is 120 characters. So if your file could have more than that, you could have a problem. Otherwise, do not expect any major thing.

Upvotes: -1

stack overflow user
stack overflow user

Reputation: 94

<ITAB> created using RTTS functionality is fully supported either by the REUSE_ALV_LIST_DISPLAY or one of ALV OOPS technologies. All the layouts should work fine. In fact I think in the cl_salv_table=>factory RTTS is responsible for automatic creation of the field catalog of the ITAB since it do not need field catalog passed by the parameter. The only thing that I heard is lost pointers of the <ITAB> ant this leads to refresh problems and so on but this is different story.

Upvotes: 1

Related Questions