topic Re: internal tables as input and output for Function modules.. in Application Development and Automation Discussions

internal tables as input and output for Function modules..

Former Member — Wed, 28 May 2008 20:58:04 GMT

Hi,

I have to write a function module which will accept a list of numbers as input and return 3 internal tables of output.

I do the follwoing, pl let me know if i am right.

1. i create 4 structures, which represent the data for each of the internal tables.

2. in se37, i create a FM and in the tables tab, i enter these structures, here itab1 is the one which will receive the values from the calling program.

so when i call this FM with input as an itab with list of values, will it be autmatically passed to the itab1 ?

should i use itab1 in the "import " tab section or is it good enough in "tables" ? basically i deal only with internal tables as inputs and outputs.

thks

Re: internal tables as input and output for Function modules..

Sm1tje — Wed, 28 May 2008 21:02:28 GMT

Sounds OK.

You can pass internal tables using the TABLES tab (more or less outdated), but you can also pass them with import and export. However, in this case (import / export), you will have to define table types based on the structures you created for them.

Re: internal tables as input and output for Function modules..

Former Member — Wed, 28 May 2008 21:02:41 GMT

Hi,

" so when i call this FM with input as an itab with list of values, will it be autmatically passed to the itab1 ? "

Yes the values will be passed automatically to itab1.

" should i use itab1 in the "import " tab section or is it good enough in "tables" ? basically i deal only with internal tables as inputs and outputs. "

You should use your itab1 in the tables tab, and not in import. Import are for flat import parameters.

Hope it helps.

Regards,

Gilberto Li

Re: internal tables as input and output for Function modules..

Former Member — Wed, 28 May 2008 21:04:12 GMT

Thanks to all.