|
12. Limited security access
I have seen SAP testing efforts come to a halt because the testers
did not have the necessary privileges and permissions to execute
certain SAP transactions or the necessary roles to submit electronic
approvals. This problem is exacerbated when testers are executing
test cases at odd hours or during weekend hours and there is no
Basis support to augment the tester’s security role.
Successful execution of certain test cases in SAP whether manually
or with automated test tools will require the test team members to
have super user access. This is of utmost importance when conducting
positive and negative testing for security roles. The testing team
should coordinate and plan with the Basis team the necessary roles
and permissions for developing test cases and for executing test
cases in the designated QA environment or test bed.
Conclusion:
In this article we have covered 12 very important lessons learned
when it comes to testing your SAP implementation. I hope you have
found it useful. Feel free to post your questions
on the
messageboard.
My strong suggestion is that you document these lessons learned as part of your test plan
to mitigate the risk of repeating these blunders in your SAP
installations.
Please note:
All contents hereby presented are copyrighted material from Jose
Fajardo.  Copyrighted 2002. All rights reserved. Must obtain
permission from Jose Fajardo to reproduce, disseminate or publish
this article. Email:
jfajardo@octanesystems.net
|
