topic RFC-Call using dynamic Parameters in Application Development and Automation Discussions

RFC-Call using dynamic Parameters

weltspion — Thu, 14 Feb 2008 17:32:46 GMT

Dear Forum!

I'd like to call a RFC function module using a dynamic parameter list.

I can either call

CALL FUNCTION bapiname DESTINATION fsystem.

CALL FUNCTION bapiname
        PARAMETER-TABLE lt_param
        EXCEPTION-TABLE lt_excep.

but not both combined!

The ABAP docu says, both should work together. If using DESTINATION the same options as for standard FM calls are allowed... (seen at: Transaction ABAPHELP, search for CALL FUNCTION, choose topic 4 for RFC)

Who is wrong? The docu or me? How can I combine both?

Cheers

Torsten

Re: RFC-Call using dynamic Parameters

Former Member — Fri, 15 Feb 2008 05:55:54 GMT

Hi Torsten,

Its not possible to call a RFC specifying parameter table.

For calling a remote enabled FM, it needs to be released which means the parameters would be fixed and thus the RFC layer does not allow using parameter table in such cases.

So I think both cannot be used together.

Best regards,

Abir

Edited by: Abir Raychaudhuri on Feb 15, 2008 6:56 AM

Re: RFC-Call using dynamic Parameters

weltspion — Fri, 15 Feb 2008 12:13:21 GMT

Hi Abir,

thanks for your helpful answer.

But I don't understand this:

For calling a remote enabled FM, it needs to be released which means the parameters would be fixed and thus the RFC layer does not allow using parameter table in such cases.

The FM resides on a remote system. It does not matter me, whether the FM is released, fixed or done with something other. As long it is reachable, I'm fine.

I am wondering about the fact, that I can call a local FM dynamically, but cannot do so for a remote call.

In the online documentation you can read, that a remote call function (with parameter destination ) has the same options like a standard call function. Actually this statement seems to be wrong. Right?

Best regards

Torsten

Re: RFC-Call using dynamic Parameters

weltspion — Wed, 06 Aug 2008 07:16:04 GMT

No more answers, so it seems that the SAP documentation is inaccurate at this point.