SOX requirements and WF-Batch SAP_ALL, SAP_NEW Profile

[Kjetil Kilhavn]

Since I have been ordered to not badmouth my company in public I can't tell you my opinion on how it was handled here. I tried the same argument, it is a non-dialog user with a password that no-one knows. It felt a bit like discussing with the Monolith (http://www.traveladventures.org/continents/europe/vigeland09.shtml)
 
WF-BATCH has a copy of SAP_ALL and SAP_NEW. At least it creates employment opportunities...
-- 
Kjetil Kilhavn, Statoil ØFT KTJ BAS DEV SAP


________________________________

	From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of Shahram Shadmani
	Sent: 12. mai 2006 16:21
	To: sap-wug at mit.edu
	Subject: SOX requirements and WF-Batch SAP_ALL, SAP_NEW Profile
	
	
	Hi there,
	 
	Our SAP security team is attending to remove the SAP_ALL and SAP_NEW profile from WF-Batch user due to SOX requirements.
	We (SAP Workflow Team) know that this will cause lot of problems and are pointing to the type of this user which is "system" and not a dialog user. However, I was wondering if other people / companies have or had the same problem and how they resolved it.
	 
	Thanks a lot for your response in advance,
	 
	Shahram Shadmani
	 



-------------------------------------------------------------------
The information contained in this message may be CONFIDENTIAL and is
intended for the addressee only. Any unauthorised use, dissemination of the
information or copying of this message is prohibited. If you are not the
addressee, please notify the sender immediately by return e-mail and delete
this message.
Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20060512/50afc618/attachment.htm