Mixing BOR objects and OO Classes in WF

[Mike Pokraka]

Ahhhhhh, a light has been switched on!

One question though: I'm trying to implement a class as an attribute to 
a BOR object (multiline ZCL_FIPP_ITEMS as attribute of FIPP) and failing 
miserably (ver.640). The best way I could find is to pass the BO to an 
instance-independent method of the class which returns instances of 
itself (thus requiring a step in a WF to instantiate).

I've tried all permutations of using structures with LPOR types and 
things - I got as far as getting it to show the little class icon in the 
BO test screen, but WF builder will have none of it when I try to do an 
assignment: "An object compatible with blah was expected...". I can 
instantiate the whole thing as a private attribute, but can't get it out 
into the workflow... so close yet so far.

By the way, I found some obscure reference in the NW2004S help hinting 
that there will be some kind of migration tool for BO to CL in the 
future....

Thanks a stack for the useful pointers,
Cheers
Mike

Dart, Jocelyn wrote:
> Hi Mike, 
> Yes you can convert between the two - I didn't focus on it particularly,
> but there are some hints given in the SAP Library Help.   You need to
> set up an attribute with a particular type, and also use the include
> programs <cntn03> as described, on the ABAP Class side at least. 
> 
> Regards,
> Jocelyn Dart
> Senior Consultant
> SAP Australia Pty Ltd.
> Level 1/168 Walker St.
> North Sydney 
> NSW, 2060
> Australia
> T   +61 412 390 267
> M   + 61 412 390 267
> E   jocelyn.dart at sap.com
> http://www.sap.com
> 
> The information contained in or attached to this electronic transmission
> is confidential and may be legally privileged. It is intended only for
> the person or entity to which it is addressed. If you are not the
> intended recipient, you are hereby notified that any distribution,
> copying, review, retransmission, dissemination or other use of this
> electronic transmission or the information contained in it is strictly
> prohibited. If you have received this electronic transmission in error,
> please immediately contact the sender to arrange for the return of the
> original documents. 
> Electronic transmission cannot be guaranteed to be secure and
> accordingly, the sender does not accept liability for any such data
> corruption, interception, unauthorized amendment, viruses, delays or the
> consequences thereof.
> Any views expressed in this electronic transmission are those of the
> individual sender, except where the message states otherwise and the
> sender is authorized to state them to be the views of SAP AG or any of
> its subsidiaries. SAP AG, its subsidiaries, and their directors,
> officers and employees make no representation nor accept any liability
> for the accuracy or completeness of the views or information contained
> herein. Please be aware that the furnishing of any pricing information/
> business proposal herein is indicative only, is subject to change and
> shall not be construed as an offer or as constituting a binding
> agreement on the part of SAP AG or any of its subsidiaries to enter into
> any relationship, unless otherwise expressly stated. 
> 
> 
> -----Original Message-----
> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
> Of Mike Pokraka
> Sent: Monday, 05 December 2005 5:57 PM
> To: sap-wug at mit.edu
> Subject: Mixing BOR objects and OO Classes in WF
> 
> Hi folks,
> 
> It seems to me that one of the stumbling blocks to plunging head first
> into OO classes for use in workflow is the interoperability between the
> two technologies, at least that's what's keeping me only occasionally
> dipping my feet into it here and there - especially on my current 620
> system.
> 
> I'm talking about being able to do things like
> Z_CL_WF_APPROVER.EMPLOYEET.EMAIL
> or conversely, being able to create a class-type attribute to a BOR
> object:
> BUS2032.Z_CL_WF_WHATEVER
> 
> There's the option of creating wrapper classes for any BOR objects, but
> that's too much work. Or has anyone come up with any ideas or
> workarounds?
> Thanks to Jocelyn's handy hints, I've got a far better grip how/where to
> use supply methods and such so it plays nicely with WF in 6.20, but
> mixing
> BOR into it still seems impossibly painful.
> 
> At the risk of sounding backwards, one might say that by creating
> classes
> we lose all the nice OO functionality we have with BOR Objects :-)
> 
> Any thoughts?
> 
> Cheers
> Mike
> 
> 
> 
> _______________________________________________
> 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