Wrapper

[Former Member]

When do we create wrapper for RFC or BAPI ? Do we ever create it for Idoc ?

Radhika

[santhosh_kumarv · Accepted solution]

In case of BAPI call, we get an error "Parameter RETURN has type "BAPIRETURN1" which is unknown" in the BAPI response, this is becuse BAPIRETURN1 will not be parsed by the RFC adapter.

Hence we create a wrapper i.e. copy the BAPI to a ZRFC by chaging the return type "BAPIREUTURN1" to "BAPIRETURN".

check the below thread..

~SaNv...

Edited by: Santhosh Kumar V on Jan 29, 2010 8:03 PM

[former_member200962]

A wrapper means Message/ Service Interface (or even the WSDL file) .... so when do you create a Message/ Service Interface?

[Former Member]

So when we import RFC to be used as Message Interface, are they all used with wrappers ?

I have seen many threads in forum involving RFC but never saw anything like wrappers in that. So was wondering is it used only with BAPI

[former_member200962]

Wrapper is the term used to denote the Message/ Service Interface and is mostly used by non-technical folks; hence we have not seen any post about enclosing some message in a wrapper.....RFC does not need a Message/ Service Interface....and hence no need to wrap it. especially unless you are exposing the RFC as webservice (hosted by XI/ PI) where you generate the WSDL out of this RFC (directly)