E-mail notifications with shortcut: SWNWIEX
Martijn Wever
martijn.wever at eozen.com
Thu Dec 1 11:41:05 EST 2005
Hi Matt,
I don,t have a problem with the execution via e-mail but with the fact that the user can also start the transaction manually when logged on to SAP.
Regards,
Martijn
-----Original Message-----
From: "Matt D. Krebs" <Krebs_Matt_D at cat.com>
Date: Thu, 1 Dec 2005 10:07:44
To:sap-wug at mit.edu
Subject: RE: E-mail notifications with shortcut: SWNWIEX
Hi Martijn -
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.
[System]
Name=DR8
Description=
Client=100
[User]
Name=USERID
Language=EN
[Function]
Title=
Command=*swnwiex p_action=EXECUTE; p_wi_id=000000505156; DYNP_OKCODE=ONLI
Type=Transaction
[Configuration]
GuiSize=Normal window
[Workflow]
Email=userid at mail.com
Matt Krebs
NACD e-Business
100 N.E. Adams Street
Peoria, IL 61629-2320
309-675-1351
sap-wug-request at mit.edu
Sent by: sap-wug-bounces at mit.edu
12/01/2005 09:55 AM
Please respond to
sap-wug at mit.edu
To
To sap-wug at mit.edu
cc
Subject SAP-WUG Digest, Vol 13, Issue 4
Caterpillar: Confidential Green Retain Until: 12/31/2005 Retention Category: G90 - General Matters/Administration
Send SAP-WUG mailing list submissions to
sap-wug at mit.edu
To subscribe or unsubscribe via the World Wide Web, visit
http://mailman.mit.edu/mailman/listinfo/sap-wug
or, via email, send a message with subject or body 'help' to
sap-wug-request at mit.edu
You can reach the person managing the list at
sap-wug-owner at mit.edu
When replying, please edit your Subject line so it is more specific
than Re: Contents of SAP-WUG digest...
Today's Topics:
1. RE: How do CREATED terminating events link to task?
(Breslavets Sergey)
2. Executing URL from work item (Hill, Anna)
3. Re: SRM Shopping Cart Status (Raju Omkaram)
4. RE: E-mail notifications with shortcut: SWNWIEX (Alon Raskin)
----- Message from Breslavets Sergey <sergey.breslavets at volvo.com> on Thu, 1 Dec 2005 09:42:40 -0500 -----
To: SAP Workflow Users' Group <sap-wug at mit.edu>
Subject: RE: How do CREATED terminating events link to task?
Hi Mike,
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.
Sergey
-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu]On Behalf
Of Mike Pokraka
Sent: Thursday, December 01, 2005 3:58 AM
To: SAP Workflow Users' Group
Subject: RE: How do CREATED terminating events link to task?
Thanks Sergey and Jocelyn,
That makes perfect sense - I dug around the code for SW..._FOR_UPDATE and can
see how it all fits together. However being a bit of a custom tweak does still
mean that the application has to specifically make provision for it - in other
words it won't work for a zChanged event triggered off a change doc.
At least I am happy to rely on it - the question came up because I have a
process where it's critical that the document is created from the task.
I might have consulted the Bible (and will do so tomorrow), unfortunately my
copy is currently 2500km away where it is of absolutely no use to me
whatsoever, even at the speed of an unladen swallow.
Cheers
Mike
--- Breslavets Sergey <sergey.breslavets at volvo.com> wrote:
> Hi Mike,
>
> it's simple really.
>
> When u execute the workitem, the WF manager exports the Workitem ID to the
> memory and creates a special case of an instance linkage record (SWEINST) for
> that particular workitem and event 'CREATED' (object key is '*'). When the
> event 'Created' for that object type is raised (e.g. you posted an invoice) -
> WF manager will check the memory for the exported WI id, and then check the
> instance linkage for that ID number - if exists, it'll link the created
> object id to the workitem and completes the task.
>
> So that, ONLY if you create the object by executing the workitem you will
> have the WI ID exported and linkage record created, all other CREATED event
> will be ignored.
>
> Regards,
> SB
>
>
> -----Original Message-----
> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu]On Behalf
> Of Mike Pokraka
> Sent: Wednesday, November 30, 2005 3:19 AM
> To: SAP Workflow User Group
> Subject: How do CREATED terminating events link to task?
>
>
> Hi all,
>
> I'm curious as to how terminating events link to async tasks, and in
> particular
> what makes CREATED events 'special':
>
> If I my terminating event is DOCUMENT.FUBAR, anyone can fubar the document
> outside of workflow and it will complete the task. This is a good thing.
>
> So the logical conclusion is that an async CREATE method with a CREATED
> terminating event will terminate itself when *anyone* creates a document of
> that type. Not so, if I use CREATED, *only* a document created by executing
> that task will terminate the task. This is a good thing, but how is this
> accomplished? I mean, even if I excecute the WI which takes me to a
> transaction
> and I do a '/nwhatever' to restart the same transaction in the same session
> and
> then create a document, the CREATED event gets raised but won't terminate my
> task. How? Why?
>
> Any insight appreciated,
> Cheers
> Mike
>
> _______________________________________________
> 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
>
_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug
----- Message from Hill, Anna <anna.hill at sap.com> on Thu, 1 Dec 2005 16:02:46 +0100 -----
To: <sap-wug at mit.edu>
Subject: Executing URL from work item
Hello WUGers
I have a problem here which is slowly driving me insane so Im hoping someone else has also experienced this and can help. Ive searched the archives but havent managed to find anything (although I recall similar things have been posted?). Anyway
Im 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. Im splitting my url container into 2 components, url1 and url2 (this worked perfectly when my urls were a bit shorter) and calling them as follows (using a SAPscript comment line /*):
<A HREF =&URL1&&URL2& TARGET=_blank> Display Form </A>
Say url1 = https://ipd.wdf.sap.corp/sap/bc/bsp/sap/zbsp_shs_c_fine/
And url2 = 123456789ABCDEFGHIJK
When the link is executed, the url ends up as
https://ipd.wdf.sap.corp/sap/bc/bsp/sap/zbsp_shs_c_fine/123456789%20%20</&/>ABCDEFGHIJK
where %20%20</&/> has been added due to a truncation. If display the work item (technical view), I can see:
<A HREF =
HTTPS://IPD.WDF.SAP.CORP/SAP/BC/BSP/SAP/ZBSP_SHS_C_FINE/12345
6789AB
CDEFGHIJK TARGET=_blank> Display Fine
So the problem is occurring between B and C (note NOT between the end of url1 and the beginning of url2), so I think its 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, its filling what it sees as gaps with %20%20 etc.
Does anyone know how to prevent this from happening?
Many thanks
Anna Hill
SAP Netweaver Technology
SAP (UK) Ltd
Clockhouse Place, Bedfont Road,
Feltham, Middlesex TW14 8HD
T +44 (0)20 8917 6125
F +44 (0)20 8917 6461
M +44 (0)7966 975125
E anna.hill at sap.com
----- Message from Raju Omkaram <romkaram at gmail.com> on Thu, 1 Dec 2005 10:40:31 -0500 -----
To: SAP Workflow Users' Group <sap-wug at mit.edu>
Subject: Re: SRM Shopping Cart Status
Sue,
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.
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.
I ensured that I never set workflow status to 'Released' since the REQREQ job will create yet another backend document.
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.
Hope this helps.
Raju
On 11/29/05, Susan R. Keohan <keohan at ll.mit.edu> wrote:
Hello all,
Silly question to follow...
Is it possible to change the status of a Shopping Cart from Approved (1) to Resubmitted (10) ?
The function module BBP_PD_SC_STATUS_CHANGE_WF doesn't want to do this, so I am guessing this is
not do-able without a mod. Unless there is a config change to allow this ?
The reason for asking is to allow shopping carts of a certain type to go to the sourcing cockpit,
which means they have been approved and released, but when the buyer sees it in the sourcing
cockpit, if the cart requires changes, they want to send it back.
Happy WF-ing,
Sue
--
Susan R. Keohan
SAP Workflow Developer
MIT Lincoln Laboratory
244 Wood Street
LI-200
Lexington, MA. 02420
781-981-3561
keohan at ll.mit.edu
_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug
----- Message from Alon Raskin <araskin at 3i-consulting.com> on Thu, 1 Dec 2005 10:39:29 -0500 -----
To: SAP Workflow Users' Group <sap-wug at mit.edu>
Subject: RE: E-mail notifications with shortcut: SWNWIEX
Hi Martijn,
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?
Alon Raskin
e: araskin at 3i-consulting.com <mailto:araskin at 3i-consulting.com>
p: +1 207 409 4983 (please note new number)
f: +61 3 8610 1239
w: http://www.3i-consulting.com
________________________________
From: sap-wug-bounces at mit.edu on behalf of Martijn Wever
Sent: Thu 12/1/2005 06:29
To: SAP-WUG at MITVMA.MIT.EDU
Subject: E-mail notifications with shortcut: SWNWIEX
Dear workflow experts,
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)?
Any comments would be welcomed.
Regards,
Martijn Wever
_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug
[attachment winmail.dat deleted by Matt D. Krebs/0A/Caterpillar] _______________________________________________
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
More information about the SAP-WUG
mailing list