ABAP OO objects as BOR method parameters.
Florin Wach
florin.wach at gmx.net
Tue Jul 21 03:42:10 EDT 2009
Hi Sharath,
1) ... hm... didn't realize that OO-Workflow works on 4.7 already (stable).
Try using ABAP reference type SIBFLPOR
2) If you cannot define the parameter as CL -Object, the macro will try to convert the runtime-reference of a BO to a persistent reference of the BO, which has to fail for obvious reasons. If using the ABAP-Dic-Reference, then it won't be a problem
3) Yes, the workflow cannot store OO-Object in the container, unless you've fully implemented the interface
....
Anyhow, from my perspective it looks like you should keep using a new business object implementation and not using the OO-part for the moment. Maybe you give some explanation of how and why you like to use this kind of container/implementation.
Best wishes,
Florin
-------- Original-Nachricht --------
> Datum: Mon, 20 Jul 2009 15:48:58 -0700 (PDT)
> Von: Sharath K <ksharath77 at yahoo.com>
> An: "SAP Workflow Users\' Group" <sap-wug at mit.edu>
> Betreff: ABAP OO objects as BOR method parameters.
> Hi all, Here I am repostig the issue(seems my emails are ending in Junk
> folder).
> I am trying to return a class object from business
> object method to workflow container. I am not using this is class object
> in any
> of my tasks, using just as parameter..
>
>
>
>
>
>
>
> Issue-1: I am unable to class object as BOR method parameter, I cant see
> any options to choose ABAP class
> type..the only two options are (i)ABAP Dictionary, (ii) Object type.. Is
> it a version issue..the client is on R/3 4.7.
>
>
>
>
>
>
>
>
>
>
> Issue-2: Object reference is not passed to task
> container with SWC_SET_ELEMENT CONTAINER macro from BOT method.
>
>
>
> Issue-3: I have not implemented IF_WORKFLOW methods in the class..Do I
> need to
> implement the interface methods irrespective of its use in task?
>
>
>
>
>
> Thanks for all your input.
>
>
> Regards,
>
> Sharath.
>
>
>
More information about the SAP-WUG
mailing list