[LIKELY JUNK]RE: Automatic Workflow Customizing (SWU3) and Central User Management

Dart, Jocelyn jocelyn.dart at sap.com
Wed Feb 11 17:37:52 EST 2009


Hi folks, 
Another thing we have done at one site is to include the system and client in the footer of every email - but that involves changing every task of course. 
You could also try using the BAPIs to modify USER and see if you get further that way. 
Regards,
Jocelyn 

________________________________

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of John Wiese
Sent: Saturday, 7 February 2009 8:33 AM
To: SAP Workflow Users' Group
Subject: [LIKELY JUNK]RE: Automatic Workflow Customizing (SWU3) and Central User Management



Sorry, I hit SEND before I had completed my thought.

 

Within the Workflow, we also determine the SYSTEM the Workflow is running in,

and incorporate logic to identify that system in any messages / e-mails generated.

 

So, my simple answer is not pertinent when CUA comes into play.   Therefore,

we took the above approach to remedy.

 

John of ESRI

 

________________________________

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of John Wiese
Sent: Friday, February 06, 2009 1:24 PM
To: SAP Workflow Users' Group
Subject: RE: Automatic Workflow Customizing (SWU3) and Central User Management

 

Actually, this problem is not that difficult to resolve.

 

Since WF-BATCH is an userid, you can go into SU01 and change the e-mail address

to a unique e-mail.    For example:

 

DEV system ==>  WF-BATCH-DEV at xxxxx.com

 

QA   system ==>  WF-BATCH-QA at xxxxx.com

 

PRD system ==>  WF-BATCH-PRD at xxxxx.com

 

Yours,

John of ESRI

 

________________________________

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of Mike Pokraka
Sent: Friday, February 06, 2009 1:13 PM
To: 'SAP Workflow Users' Group'
Subject: RE: Automatic Workflow Customizing (SWU3) and Central User Management

 

Actually I've recently run into this as well: The client insisted that they use CUA to maintain names and email address, thus there was no way to tell where any mails came from since WF-BATCH looked the same in all systems. Usually I can ask basis to assign different names in different systems and that appears as the "From" address. Not this time.

 

So I'd also be interested in any opinions on this... 

 

Cheers, 

Mike

 

 

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of Wegert, Volker
Sent: 16 January 2009 11:17
To: SAP Workflow Users' Group
Subject: AW: Automatic Workflow Customizing (SWU3) and Central User Management

 

Hi,

 

unfortunately it's not that easy... For example, you can set the CUA to allow changes to some properties in the central system only (transaction SCUM). If this is the case, not even the super users are allowed to change the values in any connected system. I don't have a current issue to resolve, I'm just curious if there's any standard procedure that covers all possibilities or if I have to write my own...

 

  Volker 

________________________________

Von: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] Im Auftrag von akshay.bhagwat at wipro.com
Gesendet: Donnerstag, 15. Januar 2009 20:23
An: sap-wug at mit.edu
Betreff: RE: Automatic Workflow Customizing (SWU3) and Central User Management

Hi,

 

I think you can use a user who has super /admin rights to execute the Automatic workflow customizing i.e. SWU3 , and the automatic workflow customizing will do the required things for you.

Some of the activities like setting up prefix no. etc you will have to do manually.

 

Regards

Akshay Bhagwat

 

 

________________________________

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of Wegert, Volker
Sent: Thursday, January 15, 2009 2:46 AM
To: SAP Workflow Users' Group
Subject: Automatic Workflow Customizing (SWU3) and Central User Management

Hi all, 

Do you know of any official SAP statement about how to use the SWU3 activities to create the WF-BATCH user and assign the necessary privileges in an system landscape where central user managemen (ZBV) is enabled? We've had some issues that required special treatment - for example, we had to create the user centrally, have it distributed to the systems but then had to "touch" it with SWU3 again to ensure that all properties were set correctly. Is there an official "guidde" for this? What are your personal recommendations?

Thanks in advance! 

Volker Wegert 

Siemens Medical Solutions GSD GmbH 
H IM HS GSD Projektentwicklung 
Riedemannweg 59 
13627 Berlin, Deutschland 
Tel.: +49 (30) 38370-227 
mailto:volker.wegert at siemens.com <mailto:volker.wegert at siemens.com>  

Siemens Medical Solutions GSD GmbH: Geschäftsführer: Stefan Thomas Herm, Anne Rethmann; Sitz der Gesellschaft: 13627 Berlin; Registergericht: Berlin-Charlottenburg, HRB 16583; Ust.-IdNr. DE 129274202; Steuer-Nr. Trägergesellschaft 14310370216

Wichtiger Hinweis: Diese E-Mail und etwaige Anlagen enthalten firmenvertrauliche Informationen. Sollten Sie diese E-Mail irrtümlich erhalten haben, benachrichtigen Sie uns bitte durch Antwort-Mail und löschen Sie diese E-Mail nebst Anlagen von Ihrem System. Vielen Dank.

Please do not print this email unless it is absolutely necessary. 

The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. 

WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. 

www.wipro.com 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20090212/400e4ab9/attachment.htm


More information about the SAP-WUG mailing list