<br><font size=2 face="sans-serif">Hi Martijn -</font>
<br>
<br><font size=2 face="sans-serif">We use RSWUWFML2 to send work item attachments
via email. Alon is correct in his assumption. When the user
launches the attachment, the initial screen of SWNWIEX is skipped and the
user is taken directly into the work item. I can save the attachment
and open it in notepad to see the 'code' behind it: The command line
is probably the important line.</font>
<br>
<br><font size=2 face="sans-serif">[System]</font>
<br><font size=2 face="sans-serif">Name=DR8</font>
<br><font size=2 face="sans-serif">Description=</font>
<br><font size=2 face="sans-serif">Client=100</font>
<br><font size=2 face="sans-serif">[User]</font>
<br><font size=2 face="sans-serif">Name=USERID</font>
<br><font size=2 face="sans-serif">Language=EN</font>
<br><font size=2 face="sans-serif">[Function]</font>
<br><font size=2 face="sans-serif">Title=</font>
<br><font size=2 face="sans-serif">Command=*swnwiex p_action=EXECUTE; p_wi_id=000000505156;
DYNP_OKCODE=ONLI</font>
<br><font size=2 face="sans-serif">Type=Transaction</font>
<br><font size=2 face="sans-serif">[Configuration]</font>
<br><font size=2 face="sans-serif">GuiSize=Normal window</font>
<br><font size=2 face="sans-serif">[Workflow]</font>
<br><font size=2 face="sans-serif">Email=userid@mail.com</font>
<br>
<br><font size=2 face="sans-serif">Matt Krebs<br>
NACD e-Business<br>
100 N.E. Adams Street<br>
Peoria, IL 61629-2320<br>
309-675-1351</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>sap-wug-request@mit.edu</b>
</font>
<br><font size=1 face="sans-serif">Sent by: sap-wug-bounces@mit.edu</font>
<p><font size=1 face="sans-serif">12/01/2005 09:55 AM</font>
<table border>
<tr valign=top>
<td bgcolor=white>
<div align=center><font size=1 face="sans-serif">Please respond to<br>
sap-wug@mit.edu</font></div></table>
<br>
<td width=59%>
<br>
<table width=100%>
<tr>
<td>
<div align=right><font size=1 face="sans-serif">To</font>
<br><font size=1 face="sans-serif"><u>To</u></font></div>
<td valign=top><font size=1 face="sans-serif">sap-wug@mit.edu</font>
<tr>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td valign=top>
<br>
<br></table>
<br>
<table width=100%>
<tr>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td valign=top><font size=1 face="sans-serif">SAP-WUG Digest, Vol 13, Issue
4</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<p><font size=1 face="sans-serif">Caterpillar: Confidential Green
Retain Until: 12/31/2005
Retention Category: G90 - General Matters/Administration</font>
<br>
<br>
<br><font size=2><tt>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>
Today's Topics:<br>
<br>
1. RE: How do CREATED terminating events link to task?<br>
(Breslavets Sergey)<br>
2. Executing URL from work item (Hill, Anna)<br>
3. Re: SRM Shopping Cart Status (Raju Omkaram)<br>
4. RE: E-mail notifications with shortcut: SWNWIEX (Alon Raskin)<br>
</tt></font><font size=2 color=#800080 face="sans-serif"><br>
----- Message from "Breslavets Sergey" <sergey.breslavets@volvo.com>
on Thu, 1 Dec 2005 09:42:40 -0500 -----</font>
<table width=100%>
<tr>
<td width=14%>
<div align=right><font size=3><b>To:</b></font></div>
<td width=85%><font size=3>"SAP Workflow Users' Group" <sap-wug@mit.edu></font>
<tr>
<td>
<div align=right><font size=3><b>Subject:</b></font></div>
<td><font size=3>RE: How do CREATED terminating events link to task?</font></table>
<br><font size=2><tt>Hi Mike, <br>
I'm sorry i might've confuse you specifically mentioning the 'CREATED'
event. In fact, the linkage is created for whatever event you have defined
as the terminating event for the task.<br>
<br>
Sergey<br>
<br>
<br>
-----Original Message-----<br>
From: sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu]On Behalf<br>
Of Mike Pokraka<br>
Sent: Thursday, December 01, 2005 3:58 AM<br>
To: SAP Workflow Users' Group<br>
Subject: RE: How do CREATED terminating events link to task?<br>
<br>
<br>
Thanks Sergey and Jocelyn, <br>
<br>
That makes perfect sense - I dug around the code for SW..._FOR_UPDATE and
can<br>
see how it all fits together. However being a bit of a custom tweak does
still<br>
mean that the application has to specifically make provision for it - in
other<br>
words it won't work for a zChanged event triggered off a change doc. <br>
At least I am happy to rely on it - the question came up because I have
a<br>
process where it's critical that the document is created from the task.<br>
<br>
I might have consulted the Bible (and will do so tomorrow), unfortunately
my<br>
copy is currently 2500km away where it is of absolutely no use to me<br>
whatsoever, even at the speed of an unladen swallow.<br>
<br>
Cheers<br>
Mike<br>
<br>
--- Breslavets Sergey <sergey.breslavets@volvo.com> wrote:<br>
<br>
> Hi Mike, <br>
> <br>
> it's simple really.<br>
> <br>
> When u execute the workitem, the WF manager exports the Workitem ID
to the<br>
> memory and creates a special case of an instance linkage record (SWEINST)
for<br>
> that particular workitem and event 'CREATED' (object key is '*').
When the<br>
> event 'Created' for that object type is raised (e.g. you posted an
invoice) -<br>
> WF manager will check the memory for the exported WI id, and then
check the<br>
> instance linkage for that ID number - if exists, it'll link the created<br>
> object id to the workitem and completes the task. <br>
> <br>
> So that, ONLY if you create the object by executing the workitem you
will<br>
> have the WI ID exported and linkage record created, all other "CREATED"
event<br>
> will be ignored.<br>
> <br>
> Regards,<br>
> SB<br>
> <br>
> <br>
> -----Original Message-----<br>
> From: sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu]On Behalf<br>
> Of Mike Pokraka<br>
> Sent: Wednesday, November 30, 2005 3:19 AM<br>
> To: SAP Workflow User Group<br>
> Subject: How do CREATED terminating events link to task?<br>
> <br>
> <br>
> Hi all, <br>
> <br>
> I'm curious as to how terminating events link to async tasks, and
in<br>
> particular<br>
> what makes CREATED events 'special': <br>
> <br>
> If I my terminating event is DOCUMENT.FUBAR, anyone can fubar the
document<br>
> outside of workflow and it will complete the task. This is a good
thing.<br>
> <br>
> So the logical conclusion is that an async CREATE method with a CREATED<br>
> terminating event will terminate itself when *anyone* creates a document
of<br>
> that type. Not so, if I use CREATED, *only* a document created by
executing<br>
> that task will terminate the task. This is a good thing, but how is
this<br>
> accomplished? I mean, even if I excecute the WI which takes me to
a<br>
> transaction<br>
> and I do a '/nwhatever' to restart the same transaction in the same
session<br>
> and<br>
> then create a document, the CREATED event gets raised but won't terminate
my<br>
> task. How? Why?<br>
> <br>
> Any insight appreciated, <br>
> Cheers<br>
> Mike<br>
> <br>
> _______________________________________________<br>
> SAP-WUG mailing list<br>
> SAP-WUG@mit.edu<br>
> http://mailman.mit.edu/mailman/listinfo/sap-wug<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>
</tt></font><font size=2 color=#800080 face="sans-serif"><br>
----- Message from "Hill, Anna" <anna.hill@sap.com> on
Thu, 1 Dec 2005 16:02:46 +0100 -----</font>
<table width=100%>
<tr>
<td width=23%>
<div align=right><font size=3><b>To:</b></font></div>
<td width=76%><font size=3><sap-wug@mit.edu></font>
<tr>
<td>
<div align=right><font size=3><b>Subject:</b></font></div>
<td><font size=3>Executing URL from work item</font></table>
<br><font size=2 face="Arial">Hello WUGers</font>
<br><font size=2 face="Arial"> </font>
<br><font size=2 face="Arial">I have a problem here which is slowly driving
me insane so I’m hoping someone else has also experienced this and can
help…. I’ve searched the archives but haven’t managed to find anything
(although I recall similar things have been posted?). Anyway… </font>
<br><font size=2 face="Arial"> </font>
<br><font size=2 face="Arial">I’m including a URL to call a BSP in the
task description of my work item but when this is called, somewhere along
the way, some extra characters are added to the string and the BSP is not
called correctly. I’m splitting my url container into 2 components, url1
and url2 (this worked perfectly when my url’s were a bit shorter) and
calling them as follows (using a SAPscript comment line /*):</font>
<br><font size=2 face="Arial"> </font>
<br><font size=1 face="Arial monospaced for SAP"><A HREF ="&URL1&&URL2&"
TARGET="_blank"> Display Form </A></font>
<br><font size=2 face="Arial"> </font>
<br><font size=2 face="Arial">Say url1 = https://ipd.wdf.sap.corp/sap/bc/bsp/sap/zbsp_shs_c_fine/</font>
<br><font size=2 face="Arial">And url2 = 123456789ABCDEFGHIJK</font>
<br><font size=2 face="Arial"> </font>
<br><font size=2 face="Arial">When the link is executed, the url ends up
as </font>
<br><font size=2 face="Arial">https://ipd.wdf.sap.corp/sap/bc/bsp/sap/zbsp_shs_c_fine/123456789<b>%20%20</&/></b>ABCDEFGHIJK</font>
<br><font size=2 face="Arial">where <b>%20%20</&/> </b>has been
added due to a truncation. If display the work item (technical view), I
can see:</font>
<br><font size=2 face="Arial"><A HREF ="</font>
<br><font size=2 face="Arial">HTTPS://IPD.WDF.SAP.CORP/SAP/BC/BSP/SAP/ZBSP_SHS_C_FINE/12345</font>
<br><font size=2 face="Arial">6789AB</font>
<br><font size=2 face="Arial">CDEFGHIJK" TARGET="_blank">
Display Fine</font>
<br><font size=2 face="Arial"> </font>
<br><font size=2 face="Arial">So the problem is occurring between B and
C (note NOT between the end of url1 and the beginning of url2), so I think
it’s something to do with the lengths of how the string is stored in the
work item at run time, as when the BSP is being called, it’s filling what
it sees as gaps with %20%20 etc. </font>
<br><font size=2 face="Arial"> </font>
<br><font size=2 face="Arial">Does anyone know how to prevent this from
happening?</font>
<br><font size=2 face="Arial">Many thanks</font>
<br><font size=3 face="Times New Roman"> </font>
<p><font size=1 color=#000080 face="Arial"><b>Anna Hill</b></font><font size=1 color=#808080 face="Arial"><br>
SAP Netweaver Technology</font><font size=3 face="Times New Roman"> </font>
<p><font size=1 color=#808080 face="Arial Black">SAP (UK) Ltd</font><font size=1 color=#808080 face="Arial"><br>
Clockhouse Place,</font><font size=1 face="Arial"> </font><font size=1 color=#808080 face="Arial">Bedfont
Road,<br>
Feltham, Middlesex TW14 8HD</font><font size=3 face="Times New Roman">
</font>
<p><font size=1 color=#000080 face="Arial Black">T</font><font size=1 face="Arial Black">
</font><font size=3 face="Times New Roman"> </font><font size=1 color=#808080 face="Arial">+44
(0)20 8917 6125</font><font size=1 color=#000080 face="Arial Black"><br>
F</font><font size=1 face="Arial Black"> </font><font size=3 face="Times New Roman">
</font><font size=1 color=#808080 face="Arial">+44 (0)20 8917 6461</font><font size=1 color=#000080 face="Arial Black"><br>
M</font><font size=1 face="Arial Black"> </font><font size=3 face="Times New Roman"> </font><font size=1 color=#808080 face="Arial">+44
(0)7966 975125</font><font size=1 color=#000080 face="Arial Black"><br>
E</font><font size=1 face="Arial Black"> </font><font size=3 face="Times New Roman"> </font><a href=mailto:anna.hill@sap.com><font size=1 color=blue face="Arial"><u>anna.hill@sap.com</u></font></a><font size=3 face="Times New Roman">
</font>
<br><font size=3 face="Times New Roman"> </font><font size=2 color=#800080 face="sans-serif"><br>
----- Message from Raju Omkaram <romkaram@gmail.com> on Thu, 1 Dec
2005 10:40:31 -0500 -----</font>
<table width=100%>
<tr>
<td width=15%>
<div align=right><font size=3><b>To:</b></font></div>
<td width=84%><font size=3>"SAP Workflow Users' Group" <sap-wug@mit.edu></font>
<tr>
<td>
<div align=right><font size=3><b>Subject:</b></font></div>
<td><font size=3>Re: SRM Shopping Cart Status</font></table>
<br><font size=3>Sue,</font>
<br><font size=3> </font>
<br><font size=3>Once shopping cart is approved it means that all the approvals
have been done. I had exactly same requirement as yours with a small twist
though. In std EBP, upon final approval of the cart, the WF status is set
to 'Approved' and a backend document is created in R/3 and the SC is available
for view in sourcing cockpit. The requirement we had was that the status
of workflow must be approved but no backend document should be created.
A buyer in the sourcing cockpit ( we use a shoppingg cart monitor for buyers
to review the SCs) will decide which line items of the different SCs need
to be converted into PO. </font>
<br><font size=3> </font>
<br><font size=3>I developed a custom workflow to avoid using BBP_PD_SC_STATUS_CHANGE_WF
instead a used custom code to set the Workflow status to 'Approved' from
'Awaiting Approval'. In shopping cart monitor when converting to PO we
cloned REQ REQ functionality to create backend document. </font>
<br><font size=3> </font>
<br><font size=3>I ensured that I never set workflow status to 'Released'
since the REQREQ job will create yet another backend document.</font>
<br><font size=3> </font>
<br><font size=3>I had to this because in 3.5 we do not have line item
conversion to PO. I used all ebp FMs in the workflow to avoid any core
mods. If we upgrade I would change the start conditions to the SAP released
workflow.<br>
<br>
Hope this helps.</font>
<br><font size=3> </font>
<br><font size=3>Raju</font>
<br><font size=3> </font>
<br><font size=3>On 11/29/05, <b>Susan R. Keohan</b> <</font><a href=mailto:keohan@ll.mit.edu><font size=3 color=blue><u>keohan@ll.mit.edu</u></font></a><font size=3>>
wrote: </font>
<br><font size=3>Hello all,<br>
<br>
Silly question to follow...<br>
<br>
Is it possible to change the status of a Shopping Cart from Approved (1)
to Resubmitted (10) ? <br>
<br>
The function module BBP_PD_SC_STATUS_CHANGE_WF doesn't want to do
this, so I am guessing this is<br>
not do-able without a mod. Unless there is a config change to allow
this ?<br>
<br>
The reason for asking is to allow shopping carts of a certain type to go
to the sourcing cockpit, <br>
which means they have been approved and released, but when the buyer sees
it in the sourcing<br>
cockpit, if the cart requires changes, they want to send it back.<br>
<br>
Happy WF-ing,<br>
Sue<br>
<br>
--<br>
Susan R. Keohan <br>
SAP Workflow Developer<br>
MIT Lincoln Laboratory<br>
244 Wood Street<br>
LI-200<br>
Lexington, MA. 02420<br>
781-981-3561</font><font size=3 color=blue><u><br>
</u></font><a href=mailto:keohan@ll.mit.edu><font size=3 color=blue><u>keohan@ll.mit.edu</u></font></a><font size=3><br>
<br>
_______________________________________________ <br>
SAP-WUG mailing list</font><font size=3 color=blue><u><br>
</u></font><a href="mailto:SAP-WUG@mit.edu"><font size=3 color=blue><u>SAP-WUG@mit.edu</u></font></a><font size=3 color=blue><u><br>
</u></font><a href="http://mailman.mit.edu/mailman/listinfo/sap-wug"><font size=3 color=blue><u>http://mailman.mit.edu/mailman/listinfo/sap-wug</u></font></a>
<br><font size=2 color=#800080 face="sans-serif"><br>
----- Message from "Alon Raskin" <araskin@3i-consulting.com>
on Thu, 1 Dec 2005 10:39:29 -0500 -----</font>
<table width=100%>
<tr>
<td width=15%>
<div align=right><font size=3><b>To:</b></font></div>
<td width=84%><font size=3>"SAP Workflow Users' Group" <sap-wug@mit.edu></font>
<tr>
<td>
<div align=right><font size=3><b>Subject:</b></font></div>
<td><font size=3>RE: E-mail notifications with shortcut: SWNWIEX</font></table>
<br><font size=2><tt>Hi Martijn,<br>
<br>
We dont use the RSWUWFML2 here so I am not speaking from experience. But
I would have assumed that the user is taken past the first screen when
they click on the shortcut. Is that not the case?<br>
<br>
Alon Raskin<br>
e: araskin@3i-consulting.com <mailto:araskin@3i-consulting.com> <br>
p: +1 207 409 4983 (please note new number)<br>
f: +61 3 8610 1239 <br>
w: http://www.3i-consulting.com<br>
<br>
________________________________<br>
<br>
From: sap-wug-bounces@mit.edu on behalf of Martijn Wever<br>
Sent: Thu 12/1/2005 06:29<br>
To: SAP-WUG@MITVMA.MIT.EDU<br>
Subject: E-mail notifications with shortcut: SWNWIEX<br>
<br>
<br>
<br>
Dear workflow experts,<br>
<br>
In our release 4.6c we have activated the improved RSWUWFML2 program and
are using it to attach a shortcut that will execute the work item. This
shortcut uses transaction SWNWIEX to execute the work item. However, with
this transaction the user can execute almost ANY work item just by entering
the WI id. The transaction does not check if the work item is actually
in the users inbox; just if he/she is a possible agent. I would think this
could be a security issue but since I haven't seen any postings regarding
this point I might be overlooking something (besides creating seperate
tasks/possible agent assignments per approver group - in our case 70 company
codes X 3 release levels)?<br>
<br>
Any comments would be welcomed.<br>
<br>
<br>
<br>
Regards,<br>
<br>
Martijn Wever<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>
[attachment "winmail.dat" deleted by Matt D. Krebs/0A/Caterpillar]
_______________________________________________<br>
SAP-WUG mailing list<br>
SAP-WUG@mit.edu<br>
http://mailman.mit.edu/mailman/listinfo/sap-wug<br>
</tt></font>
<br>