SOX requirements and WF-Batch SAP_ALL, SAP_NEW Profile

[Sue Keohan]

Jocelyn,

You are spot on, as usual.  There has been some discussion at 
yesterday's ASUG sessions on this very topic.  Hopefully, all can 
benefit, as usual, from your wisdom!
Best regards,
Sue

Dart, Jocelyn wrote:

>  
> 1. Explain logically and sensibly why this is so. 
> 2. Compare WF-BATCH with other system users such as background users 
> for running jobs, DDIC, SAP*, et al.
> 3. Explain logically and sensibly *** with quiet but firm emphasis *** 
> why this is so. 
> 4. Paint a picture of the sort of problems they are likely to cause 
> the company by doing this - use lots of black and red. 
> 5. Explain logically and sensibly *** with VOLUME and 
> manic punctuation marks!!! *** why this is so. 
> 6. Illustrate the workload/pain likely to fall upon them with monster 
> dump trucks and lots of lead bullets.
> 7. Explain logically and sensibly *** using baseball bat to beat the 
> sense into them *** why this is so.
> 8. Write 
> washing-my-hands-on-your-own-heads-be-it-I-told-you-so document and 
> get the guilty parties to sign.
> 9. Leave company citing nervous strain.
>  
> ;-)
>  
>
> Regards,
> *Jocelyn Dart*
> Senior Consultant
> *SAP Australia Pty Ltd.*
> Level 1/168 Walker St.
> North Sydney
> NSW, 2060
> Australia
> T   +61 412 390 267
> M   + 61 412 390 267
> E   jocelyn.dart at sap.com
> http://www.sap.com <http://www.sap.com/>
>
> The information contained in or attached to this electronic 
> transmission is confidential and may be legally privileged. It is 
> intended only for the person or entity to which it is addressed. If 
> you are not the intended recipient, you are hereby notified that any 
> distribution, copying, review, retransmission, dissemination or other 
> use of this electronic transmission or the information contained in it 
> is strictly prohibited. If you have received this electronic 
> transmission in error, please immediately contact the sender to 
> arrange for the return of the original documents.
>
> Electronic transmission cannot be guaranteed to be secure and 
> accordingly, the sender does not accept liability for any such data 
> corruption, interception, unauthorized amendment, viruses, delays or 
> the consequences thereof.
>
> Any views expressed in this electronic transmission are those of the 
> individual sender, except where the message states otherwise and the 
> sender is authorized to state them to be the views of SAP AG or any of 
> its subsidiaries. SAP AG, its subsidiaries, and their directors, 
> officers and employees make no representation nor accept any liability 
> for the accuracy or completeness of the views or information contained 
> herein. Please be aware that the furnishing of any pricing 
> information/ business proposal herein is indicative only, is subject 
> to change and shall not be construed as an offer or as constituting a 
> binding agreement on the part of SAP AG or any of its subsidiaries to 
> enter into any relationship, unless otherwise expressly stated.
>
>  
>
> ------------------------------------------------------------------------
> *From:* sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] *On 
> Behalf Of *Kjetil Kilhavn
> *Sent:* Saturday, 13 May 2006 12:54 AM
> *To:* SAP Workflow Users' Group
> *Subject:* RE: SOX requirements and WF-Batch SAP_ALL, SAP_NEW Profile
>
> 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.
>
>------------------------------------------------------------------------
>
>_______________________________________________
>SAP-WUG mailing list
>SAP-WUG at mit.edu
>http://mailman.mit.edu/mailman/listinfo/sap-wug
>  
>