<br><font size=2 face="sans-serif">Hi</font>
<br>
<br><font size=2 face="sans-serif">Is there any good help documentation
on the 'OO' world rather than the BOR world.</font>
<br>
<br><font size=2 face="sans-serif">Thanks</font>
<br>
<br><font size=2 face="sans-serif">John<br>
<br>
<br>
----------------------------------------------------------------------------------------<br>
This is a PRIVATE message. If you are not the intended recipient, please
delete without copying and kindly advise us by e-mail of the mistake in
delivery. NOTE: Regardless of content, this e-mail shall not operate to
bind CSC to any order or other contract unless pursuant to explicit written
agreement or government initiative expressly permitting the use of e-mail
for such purpose.<br>
----------------------------------------------------------------------------------------<br>
</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td>
<td><font size=1 face="sans-serif"><b>"Dart, Jocelyn" <jocelyn.dart<br>
@sap.com></b></font>
<br><font size=1 face="sans-serif">Sent by: sap-wug-bounces</font>
<p><font size=1 face="sans-serif">10/05/2006 08:26</font>
<br><font size=1 face="sans-serif">Please respond to "SAP Workflow
Users' Group"</font>
<td><font size=1 face="Arial"> </font>
<br><font size=1 face="sans-serif"> To:
"SAP Workflow Users' Group"
<sap-wug@mit.edu></font>
<br><font size=1 face="sans-serif"> cc:
</font>
<br><font size=1 face="sans-serif"> Subject:
RE: ABAP OO and Workflow (Events, Get
a handle etc)</font></table>
<br>
<br>
<br><font size=2 color=blue face="Arial">Restrictions in 6.20 are:</font>
<br><font size=2 color=blue face="Arial">* No functional methods (which
is sad but you'll live)</font>
<br><font size=2 color=blue face="Arial">* Some small changes in persistent
object handling (again sad but liveable). </font>
<br><font size=3> </font>
<br><font size=2 color=blue face="Arial">1. Always add a CREATEINSTANCE
static method to your ABAP OO object. This method should accept in
your object key, do a create object step, and catch any exceptions (e.g.
object does not exist) and return the object in a returning parameter.
You can then call the CREATEINSTANCE step in a task. Double
check your binding - I often find it easier to bind directly to the returning
parameter rather than use the _WI_Object element. </font>
<br><font size=3> </font>
<br><font size=2 color=blue face="Arial">Note: You are not permitted to
call the Constructor method directly in a task, and likewise leave all
the LPOR stuff alone -that's for internal use by the workflow engine only.
In NW04s you don't even get to choose those methods when you create
a task so best not to touch them at all. </font>
<br><font size=3> </font>
<br><font size=2 color=blue face="Arial">2. Absolutely use ABAP OO Events.
You should only use BOR events if you have an SAP provided BOR object
and no way of raising an OO event due to the way that applications config
works. </font>
<br><font size=3> </font>
<br><font size=2 color=blue face="Arial">Change documents let you raise
ABAP OO events without any problems at all... and of course you can always
raise ABAP OO events from user exits, BADIs, custom programs, etc. </font>
<p><font size=1 face="Arial">Regards,</font><font size=3> </font><font size=1 color=#000080 face="Arial"><b><br>
Jocelyn Dart</b></font><font size=3> </font><font size=1 color=#808080 face="Arial"><br>
Senior Consultant</font><font size=3> </font><font size=1 color=#808080 face="Arial"><b><br>
SAP Australia Pty Ltd.</b></font><font size=3> </font><font size=1 color=#808080 face="Arial"><br>
Level 1/168 Walker St.</font><font size=3> </font><font size=1 color=#808080 face="Arial"><br>
North Sydney <br>
NSW, 2060</font><font size=3> </font><font size=1 color=#808080 face="Arial"><br>
Australia</font><font size=3> </font><font size=1 color=#808080 face="Arial"><br>
T +61 412 390 267</font><font size=3> </font><font size=1 color=#808080 face="Arial"><br>
M + 61 412 390 267</font><font size=3> </font><font size=1 color=#808080 face="Arial"><br>
E jocelyn.dart@sap.com</font><font size=3> </font><font size=1 color=blue face="Arial"><u><br>
</u></font><a href=http://www.sap.com/><font size=1 color=blue face="Arial"><u>http://www.sap.com</u></font></a><font size=3>
</font>
<p><font size=1 color=red face="Times New Roman">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. </font>
<p><font size=1 color=red face="Times New Roman">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.</font>
<p><font size=1 color=red face="Times New Roman">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. </font>
<p><font size=3> </font>
<br>
<br>
<hr><font size=2 face="Tahoma"><b>From:</b> sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu]
<b>On Behalf Of </b>Markus Klein<b><br>
Sent:</b> Wednesday, 10 May 2006 4:51 PM<b><br>
To:</b> SAP Workflow Users' Group<b><br>
Subject:</b> ABAP OO and Workflow (Events, Get a handle etc)</font><font size=3><br>
</font>
<br><font size=2 face="Arial">Hello all,</font>
<br><font size=3> </font>
<br><font size=2 face="Arial">i am currently implementing Workflows baseing
on ABAP OO in a 6.20 System (yes i know there are some restrictions, just
dont know much about these restrictions, as i havent yet found any valuable
infos).</font>
<br><font size=2 face="Arial">I do facing some problems and need some ideas:</font>
<br><font size=2 face="Arial">1. How do i get a handle of a ABAP OO class
(included the IF_WORKFLOW as well as implementation of the respective Methods
(find~by~lpor etc)) in my workflow container at runtime?. I do start the
workflow with the WAPI-FB to start a workflow. So far i have tried to wrapp
the find~by~lpor method in another static method which is called from my
workflow. I do pass a key to the task which implements the wrapper method.
The task passes the key to the method and the method should return a handle
which will then passed back to the workflow. Everthing on the data-level
is fine, meaning the key is a valid key (did run the class in testmode
and called the wrapper method with that key and i do get a valied handle
back) . Unfortuantelly the container element of the workflow which should
hold the returned handle is always empty.</font>
<br><font size=3> </font>
<br><font size=2 face="Arial">2. Is it recommend to use EVENTS as part
of ABAP OO to control workflows or should i better go with a BOR implementation
for that matter?</font>
<br><font size=3> </font>
<br><font size=2 face="Arial">thanks :)</font>
<br><font size=3> </font>
<br><font size=2 face="Arial">regards,</font>
<br><font size=2 face="Arial">Markus</font>
<br><font size=3> </font>
<p><font size=2 face="Arial">______________________________________<br>
<b><br>
ABS Team GmbH</b><br>
SAP-Consulting, Human Capital Management<br>
Muehlenweg 65<br>
37120 Bovenden</font>
<p><font size=2 face="Arial">Markus Klein<br>
SAP Consultant<br>
eMail: klein@abs-team.de<br>
Tel.: +49 551 820 33 0<br>
Mobil: +49 151 126 23 047<br>
Fax: +49 551 820 33 99<br>
</font><a href="http://www.abs-team.com/"><font size=2 color=blue face="Arial"><u>www.abs-team.com</u></font></a>
<p><font size=3> </font><font size=2><tt>_______________________________________________<br>
SAP-WUG mailing list<br>
SAP-WUG@mit.edu<br>
http://mailman.mit.edu/mailman/listinfo/sap-wug<br>
</tt></font>
<p>