Can 'Table' still be used in Function Module?

[Former Member]

It seems that 'Table' is obsoleted. Changing is the one which replaces Table.

But some BAPIs are still using Table parameter even if they are standard BAPIs.

[Former Member]

Hi,

Why you say it`s obsoleted? In my mind, i still using this parameter when i create FM.

Okkkk, refer this thread,http://scn.sap.com/thread/1031768

regards,

Archer

[Former Member]

You can still use some obsoleted syntax, but you might get some warnings.

[SuhaSaha]

But some BAPIs are still using Table parameter even if they are standard BAPIs.

Almost all BAPIs use the TABLEs parameter. That is because the old RFC protocol had performance issues while handling params which referred to table (read: "deep") types, hence the usage of TABLEs.

But that is only limited to RFCs, for normal FMs you should not be using the TABLEs params.

PS - I just checked the SAP documentation and it says that you can use the basXML protocol (ABAP Release > 702) to overcome the performance issue. Further read - long text of the message FL(397)

[Former Member]

So what's the conclusion.

Do you mean we should use Tables in BAPIs while use Changing in normal FM?

[SuhaSaha]

Ming Yu wrote:

So what's the conclusion.
Do you mean we should use Tables in BAPIs while use Changing in normal FM?

To correct you, it's not just BAPIs it applies to RFMs as well

I think i have clearly stated what is the problem with using table-type params in RFMs.

[Former Member]

Thanks a lot：）