Announcement:
wanna exchange links? contact me at sapchatroom@gmail.com.
Posted by
Admin at
It sounds like Virsa is looking at conflicts at a transaction code level only which would be reflected in the high level of SOD's that it is using. You may want to disover the display versions of these transactions and recommend these to the end user. I also recommend to check the configuration for the authorization objects it may look in those transactions causing violations. But either way Virsa is not reflecting the access being given according the authorization object assigned. Another element Virsa may we looking at is these same auth objects within the users entire profile so you may want to discover that as a option. ---------------Original Message--------------- From: Lucas Sent: Friday, June 04, 2010 12:51 PM Subject: SOD High Level Conflicts with VL06 and Sales Order Maintenance > We are using Virsa Compliance Calibrator 5.2 > > Risk Id: S014 > Risk Level: High > Risk Owner: > Risk Description: Cover up shipment by creating a fictitious sales doc > Detailed Description: Cover up unauthorized shipment by creating a fictitious sales documents > Control Objective: > Business Process: Order to Cash > Conflicting Functions: SD02 - Delivery Processing and SD05 - Sales Order Processing | __.____._ Copyright © 2010 Toolbox.com and message author. Toolbox.com 4343 N. Scottsdale Road Suite 280, Scottsdale, AZ 85251 | | _.____.__ |