Container element of type BAPIRETURN does not get set

[Dan Stoicof]

No it's not.  I tried SWC_SET_TABLE and it won't take it.

Having fun,

Dan

>>> Mark Pyc <mark.pyc at gmail.com> 8/1/2007 9:54 AM >>>
Is your Return element multi-line? Just checking if it should be an
SWC_SET_TABLE.

Have fun,
Mark

On 8/1/07, Dan Stoicof <dstoico1 at jhmi.edu> wrote:
>
> I tried, as suggested, a different name . . . same result: both container
> and parameter are blank after execution.
>
> Regards,
>
> Dan
>
> >>> Mike Pokraka <asap at workflowconnections.com> 8/1/2007 6:16 AM >>>
> Just a shot in the dark, but try naming it something else. "Return" is too
> close to having other meanings.
>
> On Tue, July 31, 2007 11:28 pm, Dan Stoicof wrote:
> > Hello,
> >
> > I have defined a container element, "Return", of type BAPIRETURN.  Also,
> I
> > created an export parameter with the same name and type.
> >
> > In my code I set it like this:
> >
> >   SWC_SET_ELEMENT CONTAINER 'Return' ls_return
> >
> >  . . . where ls_return is of the same type, BAPIRETURN.
> >
> > When I debug the code, ls_return has data in it (so technically my
> > container element should get the same value), but after execution, the
> > parameter and the container element are blank.
> >
> > Is there something about BAPIRETURN that the SWC_SET_ELEMENT does not
> > like?
> >
> > Thanks!
> >
> > Dan Stoicof
> > HopkinsOne Project
> >
> > _______________________________________________
> > SAP-WUG mailing list
> > SAP-WUG at mit.edu 
> > http://mailman.mit.edu/mailman/listinfo/sap-wug 
> >
>
>
> --
> Mike Pokraka
> Senior Consultant
> Workflow Connections
> Mobile: +44(0)7786 910855
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu 
> http://mailman.mit.edu/mailman/listinfo/sap-wug 
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu 
> http://mailman.mit.edu/mailman/listinfo/sap-wug 
>