Table Values in Export/Import/Tables RFC calls

[IanStubbings]

Hi

I know that using Adaptive RFC, the best practice is to use the Tables section of the function rather than the import/export.

However, in ECC6.0, when creating entries in the Tables section of the FM it tells me that this section is obsolete.

Should I start to use the export/import parameters instead?

Cheers

Ian

[former_member185029]

Hello Ian,

May be the code snippet will help understanding your problem more clearly.

Ashu

[IanStubbings]

Hi Ashu

Thanks for the reply but there is no code snippet. It is a 'best practice' question.

The document <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/11c3b051-0401-0010-fe9a-9eabd9c216de">Effective Web Dynpro - Adaptive RFC</a> details that table values should not be passed in the exporting/importing parameters of the R/3 RFC enabled function module. THey should always be added to the Tables section.

However, in ECC6.0, when adding entries into the Tables section of an R/3 function module, it says that this practice is obsolete.

Therefore, what is the current best practice for Adaptive RFC??

Cheers

Ian