<html>
<head>
<style>
P
{
margin:0px;
padding:0px
}
body
{
FONT-SIZE: 10pt;
FONT-FAMILY:Tahoma
}
</style>
</head>
<body><P >Hi Miguel </P>
<P > </P>
<P >In the <FONT class="" >workflow</FONT> there is no <FONT class="" >error</FONT> <FONT class="" >at</FONT> all. <FONT class="" >Workflow</FONT> is <FONT class="">completed</FONT> <FONT class="">without</FONT> <FONT class="">error</FONT></P>
<P ><FONT class="" >However</FONT> there is a short dump on the <FONT class="" >WF</FONT>-BATCH ( <FONT class="" >NO_PARTNER_DATA_FOR_USER</FONT> program <FONT class="">SAPLBBP_PDH</FONT>) </P>
<P >the Item <FONT class="" >remains</FONT> in transfer and no PO is <FONT class="" >created</FONT> ( transaction <FONT class=""><FONT class="" >BBP</FONT>_PD</FONT>) </P>
<P ><BR >cheers<BR ></P>
<P>
<HR id=stopSpelling>
</P>
<P>> From: sap-wug-request@mit.edu<BR>> Subject: SAP-WUG Digest, Vol 18, Issue 48<BR>> To: sap-wug@mit.edu<BR>> Date: Fri, 12 May 2006 05:50:11 -0400<BR>> <BR>> Send SAP-WUG mailing list submissions to<BR>> sap-wug@mit.edu<BR>> <BR>> To subscribe or unsubscribe via the World Wide Web, visit<BR>> http://mailman.mit.edu/mailman/listinfo/sap-wug<BR>> or, via email, send a message with subject or body 'help' to<BR>> sap-wug-request@mit.edu<BR>> <BR>> You can reach the person managing the list at<BR>> sap-wug-owner@mit.edu<BR>> <BR>> When replying, please edit your Subject line so it is more specific<BR>> than "Re: Contents of SAP-WUG digest..."<BR>> <BR>> <BR>> Today's Topics:<BR>> <BR>> 1. RE: SRM Shopping Cart BADI Workflow (Adao-Cruz, Miguel)<BR>> <BR>> <BR>> ----------------------------------------------------------------------<BR>> <BR>> Message: 1<BR>> Date: Fri, 12 May 2006 10:48:09 +0100<BR>> From: "Adao-Cruz, Miguel" <miguel.adao-cruz@capgemini.com><BR>> Subject: RE: SRM Shopping Cart BADI Workflow<BR>> To: "SAP Workflow Users' Group" <sap-wug@mit.edu><BR>> Message-ID:<BR>> <77898EE30049594BBC2E2AB2A9A54B2F016B82EC@MISSBHXVS01.uki.capgemini.com><BR>> <BR>> Content-Type: text/plain; charset="iso-8859-1"<BR>> <BR>> Hi,<BR>> <BR>> What's the information you have from the workflow logs: step in error,<BR>> workflow completed, etc.....<BR>> You can see it in SWI6 with objcet type BUS2121 and shopping cart number.<BR>> <BR>> Cheers<BR>> <BR>> ___________________________________________________________________________<BR>> Miguel Adao-Cruz | Capgemini | London<BR>> Technology Services<BR>> SAP Application Architect<BR>> <BR>> T.+44-870-238-2927 | Int.700 2927 | www.capgemini.com<BR>> <file:///C:\Documents%20and%20Settings\madaocru\Application%20Data\Microsoft<BR>> \Signatures\www.capgemini.com,DanaInfo=OWA.UKI.CAPGEMINI.COM+> <BR>> <BR>> Join the Collaborative Business Experience<BR>> ___________________________________________________________________________<BR>> <BR>> ________________________________<BR>> <BR>> From: sap-wug-bounces@mit.edu on behalf of St?phane Bailleul<BR>> Sent: Fri 12/05/2006 09:41<BR>> To: sap-wug@mit.edu<BR>> Subject: SRM Shopping Cart BADI Workflow<BR>> <BR>> <BR>> <BR>> Hi <BR>> <BR>> <BR>> <BR>> On shopping cart we are using the BADI workflow WS14000133, the workflow<BR>> works perfectly but the shopping cart is never transformed into a purchase<BR>> order ( we are using the extended classic scenario so local Purchase Order) <BR>> <BR>> <BR>> <BR>> On the shopping cart the status for awaiting approval is inactive Item in<BR>> transfer process is inactive then there is an error in process<BR>> <BR>> <BR>> <BR>> With the workflow without approver there is no problem the shopping cart are<BR>> transformed into purchase order do you have any idea why ? Is it linked to<BR>> the workflow ?<BR>> <BR>> Best regards<BR>> <BR>> Stephane <BR>> <BR>> <BR>> ________________________________<BR>> <BR>> > From: sap-wug-request@mit.edu<BR>> > Subject: SAP-WUG Digest, Vol 18, Issue 46<BR>> > To: sap-wug@mit.edu<BR>> > Date: Thu, 11 May 2006 22:10:39 -0400<BR>> > <BR>> > Send SAP-WUG mailing list submissions to<BR>> > sap-wug@mit.edu<BR>> > <BR>> > To subscribe or unsubscribe via the World Wide Web, visit<BR>> > http://mailman.mit.edu/mailman/listinfo/sap-wug<BR>> > or, via email, send a message with subject or body 'help' to<BR>> > sap-wug-request@mit.edu<BR>> > <BR>> > You can reach the person managing the list at<BR>> > sap-wug-owner@mit.edu<BR>> > <BR>> > When replying, please edit your Subject line so it is more specific<BR>> > than "Re: Contents of SAP-WUG digest..."<BR>> > <BR>> > <BR>> > Today's Topics:<BR>> > <BR>> > 1. UWL Custom Views (Markus Klein)<BR>> > 2. RE: Printing workflow graphics to gif or jpeg....<BR>> > (Munday,Sherie J.)<BR>> > 3. Preventing attachments to be seen from certain users<BR>> > (SAP_WUG%ACDI-CIDA@acdi-cida.gc.ca)<BR>> > 4. RE: ABAP OO and Workflow (Events, Get a handle etc)<BR>> > (Dart, Jocelyn)<BR>> > <BR>> > <BR>> > ----------------------------------------------------------------------<BR>> > <BR>> > Message: 1<BR>> > Date: Thu, 11 May 2006 19:00:45 +0200<BR>> > From: "Markus Klein" <Klein@abs-team.de><BR>> > Subject: UWL Custom Views<BR>> > To: "SAP Workflow Users' Group" <sap-wug@mit.edu><BR>> > Message-ID:<BR>> > <8806DB63E3516243A433BC49E0ECF6762156B1@abs-sbs.abs-team.de><BR>> > Content-Type: text/plain; charset="us-ascii"<BR>> > <BR>> > Hello again :)<BR>> > <BR>> > i am currently customizing an UWL which will mainly call BSP<BR>> > applications (BOR: WEBSERVICE). Now im thinking of adding custom views<BR>> > for specific tasks. The Doku just mentions ABAP-BOR as a<BR>> > CustomAttributeSource. Arent ABAP Classes supported as well?<BR>> > <BR>> > regards,<BR>> > Markus<BR>> > <BR>> > ______________________________________<BR>> > <BR>> > ABS Team GmbH<BR>> > SAP-Consulting, Human Capital Management<BR>> > Muehlenweg 65<BR>> > 37120 Bovenden<BR>> > <BR>> > 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>> > www.abs-team.com <http://www.abs-team.com/> <BR>> > <BR>> > <BR>> > -------------- next part --------------<BR>> > An HTML attachment was scrubbed...<BR>> > URL:<BR>> http://mailman.mit.edu/pipermail/sap-wug/attachments/20060511/26ea06d6/attac<BR>> hment-0001.htm<BR>> > <BR>> > ------------------------------<BR>> > <BR>> > Message: 2<BR>> > Date: Thu, 11 May 2006 14:00:42 -0400<BR>> > From: "Munday,Sherie J." <MUNDAYSJ@airproducts.com><BR>> > Subject: RE: Printing workflow graphics to gif or jpeg....<BR>> > To: "SAP Workflow Users' Group" <sap-wug@mit.edu><BR>> > Message-ID:<BR>> > <43ADE045B291B240BAA1252FF11E831303E4D815@us0368exmp.america.apci.com><BR>> > Content-Type: text/plain; charset="us-ascii"<BR>> > <BR>> > Thank you Jocelyn,<BR>> > We are on Net Weaver 4, ECC 5.0, and this works for us. Terrific!<BR>> > Cheers,<BR>> > Sherie<BR>> > <BR>> > _____ <BR>> > <BR>> > From: sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu] On Behalf<BR>> > Of Dart, Jocelyn<BR>> > Sent: Tuesday, May 09, 2006 9:28 PM<BR>> > To: sap-wug@mit.edu<BR>> > Subject: Printing workflow graphics to gif or jpeg....<BR>> > <BR>> > <BR>> > <BR>> > Ok, well so maybe I hadn't looked at this for a while but... I'm<BR>> > currently working in a NW04s (7.00) system) and noticed you can now<BR>> > print your workflow graphic to a GIF or JPEG file. <BR>> > <BR>> > Perfect for slotting into documentation. <BR>> > <BR>> > Don't know how far back this goes but you might want to check your<BR>> > releases and see if you can do it to.. <BR>> > >From the workflow builder, print->graphic, set the output option to<BR>> > "File" and check your file type options. <BR>> > <BR>> > Regards, <BR>> > Jocelyn Dart <BR>> > Senior Consultant <BR>> > SAP Australia Pty Ltd. <BR>> > Level 1/168 Walker St. <BR>> > North Sydney <BR>> > NSW, 2060 <BR>> > Australia <BR>> > T +61 412 390 267 <BR>> > M + 61 412 390 267 <BR>> > E jocelyn.dart@sap.com <BR>> > http://www.sap.com <http://www.sap.com> <BR>> > <BR>> > The information contained in or attached to this electronic transmission<BR>> > is confidential and may be legally privileged. It is intended only for<BR>> > the person or entity to which it is addressed. If you are not the<BR>> > intended recipient, you are hereby notified that any distribution,<BR>> > copying, review, retransmission, dissemination or other use of this<BR>> > electronic transmission or the information contained in it is strictly<BR>> > prohibited. If you have received this electronic transmission in error,<BR>> > please immediately contact the sender to arrange for the return of the<BR>> > original documents. <BR>> > <BR>> > Electronic transmission cannot be guaranteed to be secure and<BR>> > accordingly, the sender does not accept liability for any such data<BR>> > corruption, interception, unauthorized amendment, viruses, delays or the<BR>> > consequences thereof.<BR>> > <BR>> > Any views expressed in this electronic transmission are those of the<BR>> > individual sender, except where the message states otherwise and the<BR>> > sender is authorized to state them to be the views of SAP AG or any of<BR>> > its subsidiaries. SAP AG, its subsidiaries, and their directors,<BR>> > officers and employees make no representation nor accept any liability<BR>> > for the accuracy or completeness of the views or information contained<BR>> > herein. Please be aware that the furnishing of any pricing information/<BR>> > business proposal herein is indicative only, is subject to change and<BR>> > shall not be construed as an offer or as constituting a binding<BR>> > agreement on the part of SAP AG or any of its subsidiaries to enter into<BR>> > any relationship, unless otherwise expressly stated. <BR>> > <BR>> > <BR>> > -------------- next part --------------<BR>> > An HTML attachment was scrubbed...<BR>> > URL:<BR>> http://mailman.mit.edu/pipermail/sap-wug/attachments/20060511/ae4ccb12/attac<BR>> hment-0001.htm<BR>> > <BR>> > ------------------------------<BR>> > <BR>> > Message: 3<BR>> > Date: Thu, 11 May 2006 17:38:41 -0400<BR>> > From: SAP_WUG%ACDI-CIDA@acdi-cida.gc.ca<BR>> > Subject: Preventing attachments to be seen from certain users<BR>> > To: "SAP Workflow Users' Group" <sap-wug@mit.edu><BR>> > Message-ID: <06May11.173842edt.119055@gatekeeper.acdi-cida.gc.ca><BR>> > Content-Type: text/plain; charset=ISO-8859-1<BR>> > <BR>> > Hi workflowers,<BR>> > <BR>> > I have developed a workflow implicating many users, one particular user is<BR>> > not suppose to see any attachment if any are created from the other users.<BR>> > However, that user keeps receiving the attachment, eventhough there are NO<BR>> > BINDINGS with _Attach_Objects in all tasks for work items going to this<BR>> > user.<BR>> > <BR>> > We are on 4.7, does anyone knows how to fix this... any comments would be<BR>> > greatly appreciated.<BR>> > <BR>> > Thank you!<BR>> > <BR>> > <BR>> > H?l?ne Paquin<BR>> > 819-994-2249 | helene_paquin@acdi-cida.gc.ca | T?l?copieur/Facsimile:<BR>> > 819-953-6359<BR>> > <BR>> > Technicienne sp?cialis?e principale<BR>> > D?roulement des op?rations SAP et WEB<BR>> > Direction des services et solutions ? la client?le (DSSC)<BR>> > Direction g?n?rale de la gestion de l'information et de la technologie<BR>> > (DGGIT)<BR>> > Agence canadienne de d?veloppement international<BR>> > 200, promenade du Portage, Gatineau (Qu?bec)<BR>> > Canada K1A 0G4<BR>> > <BR>> > Senior Technical Specialist<BR>> > Technical Workflow SAP and WEB<BR>> > Client Services and Solutions Division (CSSD)<BR>> > Information Management and Technology Branch (IMTB)<BR>> > Canadian International Development Agency<BR>> > 200 Promenade du Portage, Gatineau (Quebec)<BR>> > Canada K1A 0G4<BR>> > <BR>> > <BR>> > <BR>> > ------------------------------<BR>> > <BR>> > Message: 4<BR>> > Date: Fri, 12 May 2006 10:10:27 +0800<BR>> > From: "Dart, Jocelyn" <jocelyn.dart@sap.com><BR>> > Subject: RE: ABAP OO and Workflow (Events, Get a handle etc)<BR>> > To: "SAP Workflow Users' Group" <sap-wug@mit.edu><BR>> > Message-ID:<BR>> > <F843AF000027394A9F3D3194109269F4437135@sgsine11.sin.sap.corp><BR>> > Content-Type: text/plain; charset="us-ascii"<BR>> > <BR>> > I'll think about it.... I'd want to update it first and it might be a<BR>> > little while before I have time for that. <BR>> > <BR>> > <BR>> > Regards,<BR>> > Jocelyn Dart<BR>> > Senior Consultant<BR>> > SAP Australia Pty Ltd.<BR>> > Level 1/168 Walker St.<BR>> > North Sydney <BR>> > NSW, 2060<BR>> > Australia<BR>> > T +61 412 390 267<BR>> > M + 61 412 390 267<BR>> > E jocelyn.dart@sap.com<BR>> > http://www.sap.com<BR>> > <BR>> > The information contained in or attached to this electronic transmission<BR>> > is confidential and may be legally privileged. It is intended only for<BR>> > the person or entity to which it is addressed. If you are not the<BR>> > intended recipient, you are hereby notified that any distribution,<BR>> > copying, review, retransmission, dissemination or other use of this<BR>> > electronic transmission or the information contained in it is strictly<BR>> > prohibited. If you have received this electronic transmission in error,<BR>> > please immediately contact the sender to arrange for the return of the<BR>> > original documents. <BR>> > Electronic transmission cannot be guaranteed to be secure and<BR>> > accordingly, the sender does not accept liability for any such data<BR>> > corruption, interception, unauthorized amendment, viruses, delays or the<BR>> > consequences thereof.<BR>> > Any views expressed in this electronic transmission are those of the<BR>> > individual sender, except where the message states otherwise and the<BR>> > sender is authorized to state them to be the views of SAP AG or any of<BR>> > its subsidiaries. SAP AG, its subsidiaries, and their directors,<BR>> > officers and employees make no representation nor accept any liability<BR>> > for the accuracy or completeness of the views or information contained<BR>> > herein. Please be aware that the furnishing of any pricing information/<BR>> > business proposal herein is indicative only, is subject to change and<BR>> > shall not be construed as an offer or as constituting a binding<BR>> > agreement on the part of SAP AG or any of its subsidiaries to enter into<BR>> > any relationship, unless otherwise expressly stated. <BR>> > <BR>> > <BR>> > -----Original Message-----<BR>> > From: sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu] On Behalf<BR>> > Of workflow99@aol.com<BR>> > Sent: Thursday, 11 May 2006 10:49 PM<BR>> > To: sap-wug@mit.edu<BR>> > Subject: Re: ABAP OO and Workflow (Events, Get a handle etc)<BR>> > <BR>> > <BR>> > Jocelyn,<BR>> > <BR>> > Why not put it out on the SDN as a blog?<BR>> > <BR>> > Best Regards,<BR>> > Ramki Maley,<BR>> > WF Developer - US-DOI.<BR>> > <BR>> > <BR>> > -----Original Message-----<BR>> > From: Dart, Jocelyn <jocelyn.dart@sap.com><BR>> > To: SAP Workflow Users' Group <sap-wug@mit.edu><BR>> > Cc: skeohan@mit.edu<BR>> > Sent: Thu, 11 May 2006 08:23:51 +0800<BR>> > Subject: RE: ABAP OO and Workflow (Events, Get a handle etc)<BR>> > <BR>> > I did send a document out several months ago - here it is again.<BR>> > <BR>> > Sue, would you check it goes somewhere handy on the archives please?<BR>> > <BR>> > <BR>> > Regards,<BR>> > Jocelyn Dart<BR>> > Senior Consultant<BR>> > SAP Australia Pty Ltd.<BR>> > Level 1/168 Walker St.<BR>> > North Sydney<BR>> > NSW, 2060<BR>> > Australia<BR>> > T +61 412 390 267<BR>> > M + 61 412 390 267<BR>> > E jocelyn.dart@sap.com<BR>> > http://www.sap.com<BR>> > <BR>> > The information contained in or attached to this electronic <BR>> > transmission is confidential and may be legally privileged. It is <BR>> > intended only for the person or entity to which it is addressed. If you <BR>> > are not the intended recipient, you are hereby notified that any <BR>> > distribution, copying, review, retransmission, dissemination or other <BR>> > use of this electronic transmission or the information contained in it <BR>> > is strictly prohibited. If you have received this electronic <BR>> > transmission in error, please immediately contact the sender to arrange <BR>> > for the return of the original documents.<BR>> > <BR>> > Electronic transmission cannot be guaranteed to be secure and <BR>> > accordingly, the sender does not accept liability for any such data <BR>> > corruption, interception, unauthorized amendment, viruses, delays or <BR>> > the consequences thereof.<BR>> > <BR>> > Any views expressed in this electronic transmission are those of the <BR>> > individual sender, except where the message states otherwise and the <BR>> > sender is authorized to state them to be the views of SAP AG or any of <BR>> > its subsidiaries. SAP AG, its subsidiaries, and their directors, <BR>> > officers and employees make no representation nor accept any liability <BR>> > for the accuracy or completeness of the views or information contained <BR>> > herein. Please be aware that the furnishing of any pricing information/ <BR>> > business proposal herein is indicative only, is subject to change and <BR>> > shall not be construed as an offer or as constituting a binding <BR>> > agreement on the part of SAP AG or any of its subsidiaries to enter <BR>> > into any relationship, unless otherwise expressly stated.<BR>> > <BR>> > <BR>> > <BR>> > --------<BR>> > From: sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu] On <BR>> > Behalf Of John A Haworth<BR>> > Sent: Wednesday, 10 May 2006 8:12 PM<BR>> > To: SAP Workflow Users' Group<BR>> > Subject: RE: ABAP OO and Workflow (Events, Get a handle etc)<BR>> > <BR>> > <BR>> > <BR>> > <BR>> > Hi<BR>> > <BR>> > Is there any good help documentation on the 'OO' world rather than the <BR>> > BOR world.<BR>> > <BR>> > Thanks<BR>> > <BR>> > John<BR>> > <BR>> > <BR>> > ------------------------------------------------------------------------<BR>> > -<BR>> > ---------------<BR>> > This is a PRIVATE message. If you are not the intended recipient, <BR>> > please delete without copying and kindly advise us by e-mail of the <BR>> > mistake in delivery. NOTE: Regardless of content, this e-mail shall not <BR>> > operate to bind CSC to any order or other contract unless pursuant to <BR>> > explicit written agreement or government initiative expressly <BR>> > permitting the use of e-mail for such purpose.<BR>> > ------------------------------------------------------------------------<BR>> > -<BR>> > ---------------<BR>> > <BR>> > <BR>> > <BR>> > "Dart, Jocelyn" <jocelyn.dart<BR>> > @sap.com><BR>> > Sent by: sap-wug-bounces 10/05/2006 08:26<BR>> > Please respond to "SAP Workflow Users' Group"<BR>> > <BR>> > <BR>> > To: "SAP Workflow Users' Group" <sap-wug@mit.edu><BR>> > cc:<BR>> > Subject: RE: ABAP OO and Workflow (Events, Get a handle etc)<BR>> > <BR>> > <BR>> > <BR>> > Restrictions in 6.20 are:<BR>> > * No functional methods (which is sad but you'll live)<BR>> > * Some small changes in persistent object handling (again sad but <BR>> > liveable).<BR>> > <BR>> > 1. Always add a CREATEINSTANCE static method to your ABAP OO object. <BR>> > This method should accept in your object key, do a create object step, <BR>> > and catch any exceptions (e.g. object does not exist) and return the <BR>> > object in a returning parameter. You can then call the CREATEINSTANCE <BR>> > step in a task. Double check your binding - I often find it easier to <BR>> > bind directly to the returning parameter rather than use the _WI_Object <BR>> > element.<BR>> > <BR>> > Note: You are not permitted to call the Constructor method directly in <BR>> > a task, and likewise leave all the LPOR stuff alone -that's for <BR>> > internal use by the workflow engine only. In NW04s you don't even get <BR>> > to choose those methods when you create a task so best not to touch <BR>> > them at all.<BR>> > <BR>> > 2. Absolutely use ABAP OO Events. You should only use BOR events if you <BR>> > have an SAP provided BOR object and no way of raising an OO event due <BR>> > to the way that applications config works.<BR>> > <BR>> > Change documents let you raise ABAP OO events without any problems at <BR>> > all... and of course you can always raise ABAP OO events from user <BR>> > exits, BADIs, custom programs, etc. Regards,<BR>> > Jocelyn Dart<BR>> > Senior Consultant<BR>> > SAP Australia Pty Ltd.<BR>> > Level 1/168 Walker St.<BR>> > North Sydney<BR>> > NSW, 2060<BR>> > Australia<BR>> > T +61 412 390 267<BR>> > M + 61 412 390 267<BR>> > E jocelyn.dart@sap.com<BR>> > http://www.sap.com<BR>> > <BR>> > The information contained in or attached to this electronic <BR>> > transmission is confidential and may be legally privileged. It is <BR>> > intended only for the person or entity to which it is addressed. If you <BR>> > are not the intended recipient, you are hereby notified that any <BR>> > distribution, copying, review, retransmission, dissemination or other <BR>> > use of this electronic transmission or the information contained in it <BR>> > is strictly prohibited. If you have received this electronic <BR>> > transmission in error, please immediately contact the sender to arrange <BR>> > for the return of the original documents.<BR>> > <BR>> > Electronic transmission cannot be guaranteed to be secure and <BR>> > accordingly, the sender does not accept liability for any such data <BR>> > corruption, interception, unauthorized amendment, viruses, delays or <BR>> > the consequences thereof.<BR>> > <BR>> > Any views expressed in this electronic transmission are those of the <BR>> > individual sender, except where the message states otherwise and the <BR>> > sender is authorized to state them to be the views of SAP AG or any of <BR>> > its subsidiaries. SAP AG, its subsidiaries, and their directors, <BR>> > officers and employees make no representation nor accept any liability <BR>> > for the accuracy or completeness of the views or information contained <BR>> > herein. Please be aware that the furnishing of any pricing information/ <BR>> > business proposal herein is indicative only, is subject to change and <BR>> > shall not be construed as an offer or as constituting a binding <BR>> > agreement on the part of SAP AG or any of its subsidiaries to enter <BR>> > into any relationship, unless otherwise expressly stated.<BR>> > <BR>> > <BR>> > <BR>> > <BR>> > <BR>> > --------<BR>> > From: sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu] On <BR>> > Behalf Of Markus Klein<BR>> > Sent: Wednesday, 10 May 2006 4:51 PM<BR>> > To: SAP Workflow Users' Group<BR>> > Subject: ABAP OO and Workflow (Events, Get a handle etc)<BR>> > <BR>> > Hello all,<BR>> > <BR>> > i am currently implementing Workflows baseing on ABAP OO in a 6.20 <BR>> > System (yes i know there are some restrictions, just dont know much <BR>> > about these restrictions, as i havent yet found any valuable infos).<BR>> > I do facing some problems and need some ideas:<BR>> > 1. How do i get a handle of a ABAP OO class (included the IF_WORKFLOW <BR>> > as well as implementation of the respective Methods (find~by~lpor etc)) <BR>> > in my workflow container at runtime?. I do start the workflow with the <BR>> > WAPI-FB to start a workflow. So far i have tried to wrapp the <BR>> > find~by~lpor method in another static method which is called from my <BR>> > workflow. I do pass a key to the task which implements the wrapper <BR>> > method. The task passes the key to the method and the method should <BR>> > return a handle which will then passed back to the workflow. Everthing <BR>> > on the data-level is fine, meaning the key is a valid key (did run the <BR>> > class in testmode and called the wrapper method with that key and i do <BR>> > get a valied handle back) . Unfortuantelly the container element of the <BR>> > workflow which should hold the returned handle is always empty.<BR>> > <BR>> > 2. Is it recommend to use EVENTS as part of ABAP OO to control <BR>> > workflows or should i better go with a BOR implementation for that <BR>> > matter?<BR>> > <BR>> > thanks :)<BR>> > <BR>> > regards,<BR>> > Markus<BR>> > ______________________________________<BR>> > <BR>> > ABS Team GmbH<BR>> > SAP-Consulting, Human Capital Management<BR>> > Muehlenweg 65<BR>> > 37120 Bovenden<BR>> > <BR>> > 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>> > www.abs-team.com<BR>> > <BR>> > _______________________________________________<BR>> > SAP-WUG mailing list<BR>> > SAP-WUG@mit.edu<BR>> > http://mailman.mit.edu/mailman/listinfo/sap-wug<BR>> > <BR>> > <BR>> > <BR>> > <BR>> > <BR>> > _______________________________________________<BR>> > SAP-WUG mailing list<BR>> > SAP-WUG@mit.edu<BR>> > http://mailman.mit.edu/mailman/listinfo/sap-wug<BR>> > <BR>> > <BR>> > _______________________________________________<BR>> > SAP-WUG mailing list<BR>> > SAP-WUG@mit.edu<BR>> > http://mailman.mit.edu/mailman/listinfo/sap-wug<BR>> > <BR>> > <BR>> > <BR>> > ------------------------------<BR>> > <BR>> > _______________________________________________<BR>> > SAP-WUG mailing list<BR>> > SAP-WUG@mit.edu<BR>> > http://mailman.mit.edu/mailman/listinfo/sap-wug<BR>> > <BR>> > <BR>> > End of SAP-WUG Digest, Vol 18, Issue 46<BR>> > ***************************************<BR>> <BR>> <BR>> <BR>> ________________________________<BR>> <BR>> MSN Hotmail : 5 bonnes raisons de l'utiliser en e-mail principal<BR>> <http://www.imagine-msn.com/Hotmail/Post/GettingStarted/PrimaryAccount.aspx><BR>> <BR>> -------------- next part --------------<BR>> A non-text attachment was scrubbed...<BR>> Name: not available<BR>> Type: application/ms-tnef<BR>> Size: 36604 bytes<BR>> Desc: not available<BR>> Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20060512/4536c642/attachment.bin<BR>> -------------- next part --------------<BR>> This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.<BR>> <BR>> ------------------------------<BR>> <BR>> _______________________________________________<BR>> SAP-WUG mailing list<BR>> SAP-WUG@mit.edu<BR>> http://mailman.mit.edu/mailman/listinfo/sap-wug<BR>> <BR>> <BR>> End of SAP-WUG Digest, Vol 18, Issue 48<BR>> ***************************************<BR></P><br /><hr />MSN Hotmail : <a href='http://www.imagine-msn.com/Hotmail/Post/GettingStarted/PrimaryAccount.aspx' target='_new'> 5 bonnes raisons de l'utiliser en e-mail principal</a></body>
</html>