ABAP OO and Workflow

[Dart, Jocelyn]

Please whinge all you like to the developers about the highly
unnecessary marking of workflow capable classes as final or private so
we can't create subtypes.  This is shortsighted and annoying. 

Yes you can create a BOR link - I am trying to get back to the blogs but
its a struggle at the moment.  You need to create an attribute in your
class of data type SIBFLPOR and fill up the object category, type and
key (instance id) - that gets you a runtime link.  To get a design time
link set up constants, e.g. via a type pool, so that you can assign a
constant containing object category and type to your BOR attribute and
then you can reference attribute of the object throughout your workflow
template as well. 


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 Gavin Mooney
Sent: Tuesday, 14 November 2006 10:53 PM
To: SAP Workflow Users' Group
Subject: Re: ABAP OO and Workflow

Dude,

Did you get any replies to this or did you log it with OSS? Right now
I would like to implement some OO and I see from various ABAP OO posts
that Jocelyn heartily recommends using OO instead of the BOR now.

But the question is - if there's already a BOR object and SAP doesn't
provide an OO one, and perhaps you want to use events that the system
already raises on the BOR object, why would you spend the extra effort
creating an OO class?

One thing I did see is Jocelyn said you could create your OO class and
then add the BOR object as an attribute (not sure at the moment what
the means but guess I can figure it out) which I guess would give you
access to the attributes of the BOR object (but not the methods?).

Also - I see that now a lot of the standard code is calling class
methods, etc. But if you're still using FMs (like ISU_S_etc) then is
it acceptable to call a FM from a class method?

Hope all's good,
Gav

2006/9/25, Alon Raskin <araskin at 3i-consulting.com>:
> Version: SAP ECC 6.0
>
> Well I have finally found myself in a position to implement some
Workflow using ABAP OO. One thing I did notice is that many of the
'business classes' delivered by SAP are marked as Private instantiation.
Problem with this is that I can not create a sub-type of this class to
add the IF_WORKFLOW interface.
>
> I suppose one way around this is rather then inheritance I can simply
create my own class which has an instance of the business class. I
really don't like this as it messes up my model and reduces the reuse I
can gain by using OO. Does anyone think I should log this as an OSS (to
see if SAP will agree to change the instantiation scope)? Has anyone
successfully (or unsuccessfully) tried this?
>
> Alon
>
> _______________________________________________
> 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