topic Re: Dynamic Transporting fields in Modify Internal table in Application Development and Automation Discussions

Dynamic Transporting fields in Modify Internal table

Former Member — Tue, 30 Jan 2018 06:36:03 GMT

Hi,

Need to modify an internal table by transporting many fields but in dynamic way. As of now it is working good for one field. When I tried with multiple fields it is throwing error.

Below code is working fine for one field.

DATA lv_fields TYPE string.
lv_fields = 'BSART'.
MODIFY lt_data FROM lw_data TRANSPORTING (lv_fields) WHERE ebeln = lw_temp-ebeln.

Below code is throwing error as two fields are used.

DATA lv_fields TYPE string.
lv_fields = 'BSART BSTYP'.
MODIFY lt_data FROM lw_data TRANSPORTING (lv_fields) WHERE ebeln = lw_temp-ebeln.

Please provide a suggestion to use dynamic transporting with multiple fields.

Thanks in advance.

Regards,

Senthil kumar K

Re: Dynamic Transporting fields in Modify Internal table

retired_member — Tue, 30 Jan 2018 06:42:34 GMT

DATA lv_field1 TYPE string.
DATA lv_field2 TYPE string.
lv_field1 = 'BSART'.
lv_field2 = 'BSTYP'.
MODIFY lt_data FROM lw_data TRANSPORTING (lv_field1) (lv_field2) WHERE ebeln = lw_temp-ebeln.

Re: Dynamic Transporting fields in Modify Internal table

former_member196331 — Tue, 30 Jan 2018 06:48:06 GMT

What is the error.?

Re: Dynamic Transporting fields in Modify Internal table

Former Member — Tue, 30 Jan 2018 07:55:36 GMT

Getting error as ITAB_ILLEGAL_COMPONENT

Re: Dynamic Transporting fields in Modify Internal table

Former Member — Tue, 30 Jan 2018 08:18:41 GMT

Hi Horst,

Thanks for your quick response. Very much appreciated.

So for each field we need to declare separate data object.

Thought there will be an option to have only one data object for N fields. So in that case it will become fully dynamic thus helping developer not to consider number of data objects to be declared even if the fields count are varying.

Thanks and Regards,

Senthil kumar K

Re: Dynamic Transporting fields in Modify Internal table

retired_member — Tue, 30 Jan 2018 08:27:07 GMT

Yep, as documented. No internal table solution here, as we have it for SORT.

You have to prepare a set of fields and leave those empty, which you don't need.