SAP systems have some custom transactions which are created by the companies to mask the sap transactions or create new transactions.  These custom transactions will miss the Segregation duties matrix (SOD) since they have to be manually updated. When we run the SOD analysis it will miss the transaction and will not flag them a risk. These transactions should be part of SOD matrix.  Since it not part of SAP defined SOD matrix.  For example if you are copying transaction XK02 and create transaction ZXK02 to mask some of the fields in the screen.  This transaction has same functionality as update vendor master but is hiding as custom transaction. You could do this with transaction variants or create a custom screens. The transaction can perform the same functionality. The SOD analysis will miss this transaction since the custom transaction is not in SOD matrix.  The best way to update this transaction is find the similar transaction or transaction which has similar functionality. Then update the functional group with this custom transaction.  In addition to updating the transaction also update the SU24 with the relevant objects and object values for the custom transaction.

OneAccess-UserManager also helps you manage the complex documenting, testing, process control, and sign-off requirements mandated by Sarbanes-Oxley sections 302, 404, and 409

Selva Kumar

Vice President- SAP Practice

OneAccess-UserManager for SAP

SAP Certified-Powered by Netweaver

http://www.softsquare.biz/oneaccess/

selva@softsquare.biz

Phone: 1 877 717 5487

Automate and Meditate

VN:F [1.9.13_1145]
Rating: 1.0/5 (1 vote cast)
SAP GRC –Updating SOD Matrix with any custom transactions and custom object level changes, 1.0 out of 5 based on 1 rating