<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: check SOD conflicts in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/check-sod-conflicts/m-p/6938936#M1487017</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;RSUSR008_009_NEW is one option that will cost you the configuration time.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Some other vendors offering SOD checking in no particular order &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SAP (BOBJ GRC Access Controls Risk Analysis &amp;amp; Remediation)&lt;/P&gt;&lt;P&gt;CSI (Authorization Auditor)&lt;/P&gt;&lt;P&gt;Alert Enterprise&lt;/P&gt;&lt;P&gt;SecurityWeaver&lt;/P&gt;&lt;P&gt;Control Panel GRC&lt;/P&gt;&lt;P&gt;Xpandion&lt;/P&gt;&lt;P&gt;Approva&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 11 May 2010 18:06:51 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2010-05-11T18:06:51Z</dc:date>
    <item>
      <title>check SOD conflicts</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/check-sod-conflicts/m-p/6938935#M1487016</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I am doing SAP testing using QTP...here i need to automate the SOD As the Authorisation models are improved/amended/completed continuously for going live, it will be necessary for us to implement and formalise a procedure for SOD check, so plz guys can u help me on how to automate this process.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I thought of using the RSUSR008_009_NEW program....will you let me know is this the way...r plzz can u help me other soolution....&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Venkat&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 11 May 2010 17:30:55 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/check-sod-conflicts/m-p/6938935#M1487016</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2010-05-11T17:30:55Z</dc:date>
    </item>
    <item>
      <title>Re: check SOD conflicts</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/check-sod-conflicts/m-p/6938936#M1487017</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;RSUSR008_009_NEW is one option that will cost you the configuration time.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Some other vendors offering SOD checking in no particular order &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SAP (BOBJ GRC Access Controls Risk Analysis &amp;amp; Remediation)&lt;/P&gt;&lt;P&gt;CSI (Authorization Auditor)&lt;/P&gt;&lt;P&gt;Alert Enterprise&lt;/P&gt;&lt;P&gt;SecurityWeaver&lt;/P&gt;&lt;P&gt;Control Panel GRC&lt;/P&gt;&lt;P&gt;Xpandion&lt;/P&gt;&lt;P&gt;Approva&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 11 May 2010 18:06:51 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/check-sod-conflicts/m-p/6938936#M1487017</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2010-05-11T18:06:51Z</dc:date>
    </item>
  </channel>
</rss>

