SOX requirements and WF-Batch SAP_ALL, SAP_NEW Profile

[Shahram Shadmani]

Thanks a lot for all your responses! This issue was resolved by explaining
the problem to the SAP security and contacting auditors to confirm our
stand. No more sweating!

Shahram
 

-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of
sap-wug-request at mit.edu
Sent: Tuesday, May 16, 2006 12:05 PM
To: sap-wug at mit.edu
Subject: SAP-WUG Digest, Vol 18, Issue 60

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: SRM 5.0 and my Concurrent Employment Issues (jerry martinek)
   2. RE: SOX requirements and WF-Batch SAP_ALL, SAP_NEW Profile
      (Scheinoha, John)


----------------------------------------------------------------------

Message: 1
Date: Tue, 16 May 2006 08:01:05 -0700
From: jerry martinek <jerry.martinek at shawbiz.ca>
Subject: RE: SRM 5.0 and my Concurrent Employment Issues
To: sap-wug at mit.edu
Message-ID: <adf454adb765.adb765adf454 at prod.shawcable.com>
Content-Type: text/plain; charset="us-ascii"

An HTML attachment was scrubbed...
URL:
http://mailman.mit.edu/pipermail/sap-wug/attachments/20060516/a8f3071f/attac
hment-0001.htm

------------------------------

Message: 2
Date: Tue, 16 May 2006 10:19:24 -0500
From: "Scheinoha, John" <Scheinoha.John at basco.com>
Subject: RE: SOX requirements and WF-Batch SAP_ALL, SAP_NEW Profile
To: <shahram.shadmani at alcatel.com>
Cc: sap-wug at mit.edu
Message-ID:
	<67F5FEE7CA6056408636628880BACDFD325689 at MKE01EXCHVS1.bas.corp.dom>
Content-Type: text/plain;	charset="us-ascii"

Shadmani,

   I have also had this issue presented to me by external auditors and our
own internal SAP Security team.  What I used as documentation is the
documentation from the BC601 class (now BIT601) where it references creating
user WF-BATCH and assign this user the authorization profiles "SAP_ALL" and
"SAP_NEW". This is page 3-7 in the BC601 Participant Handbook.

   If this doesn't work, try page 77-78 of the "Practical Workflow for SAP"
book.  This also describes how and why to set up WF-BATCH with SAP_ALL and
SAP_NEW.  

   If this doesn't work have the auditors discuss this with SAP America.

   If this doesn't work, use Jocelyn Dart's suggestion.

Good Luck,
  John
(414) 256 - 5136  

-----Original Message-----
From: shahram.shadmani at alcatel.com [mailto:shahram.shadmani at alcatel.com]

Sent: Friday, May 12, 2006 9:21 AM
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
 



------------------------------

_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug


End of SAP-WUG Digest, Vol 18, Issue 60
***************************************