ABAP OO and Workflow (Events, Get a handle etc)

Wed May 10 06:11:33 EDT 2006

Hi

Is there any good help documentation on the 'OO' world rather than the BOR 
world.

Thanks

John

----------------------------------------------------------------------------------------
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.
----------------------------------------------------------------------------------------

"Dart, Jocelyn" <jocelyn.dart
@sap.com>
Sent by: sap-wug-bounces
10/05/2006 08:26
Please respond to "SAP Workflow Users' Group"

        To:     "SAP Workflow Users' Group" <sap-wug at mit.edu>
        cc: 
        Subject:        RE: ABAP OO and Workflow (Events, Get a handle 
etc)

Restrictions in 6.20 are:
* No functional methods (which is sad but you'll live)
* Some small changes in persistent object handling (again sad but 
liveable). 

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. 

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. 

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. 

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. 
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. 

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf 
Of Markus Klein
Sent: Wednesday, 10 May 2006 4:51 PM
To: SAP Workflow Users' Group
Subject: ABAP OO and Workflow (Events, Get a handle etc)

Hello all,

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).
I do facing some problems and need some ideas:
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.

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?

thanks :)

regards,
Markus

______________________________________

ABS Team GmbH
SAP-Consulting, Human Capital Management
Muehlenweg 65
37120 Bovenden
Markus Klein
SAP Consultant
eMail:   klein at abs-team.de
Tel.:      +49 551 820 33 0
Mobil:   +49 151 126 23 047
Fax:      +49 551 820 33 99
            www.abs-team.com
 _______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20060510/017c3963/attachment.htm