<?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 S_PROGRAM Impacts in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/s-program-impacts/m-p/9330002#M1729180</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dear Experts,&lt;/P&gt;&lt;P&gt;We got audit observation as Users can bypass S_TCODE via S_PROGRAM with activity as SUBMIT.&lt;/P&gt;&lt;P&gt;But in our case all users are uploading data in SAP from batch input. this process happens with help of some Z reports which are executed from SA38.&lt;/P&gt;&lt;P&gt;Is there any other suggestion which will resolve this issue without affecting users work.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 11 Mar 2013 10:28:08 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2013-03-11T10:28:08Z</dc:date>
    <item>
      <title>S_PROGRAM Impacts</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/s-program-impacts/m-p/9330002#M1729180</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dear Experts,&lt;/P&gt;&lt;P&gt;We got audit observation as Users can bypass S_TCODE via S_PROGRAM with activity as SUBMIT.&lt;/P&gt;&lt;P&gt;But in our case all users are uploading data in SAP from batch input. this process happens with help of some Z reports which are executed from SA38.&lt;/P&gt;&lt;P&gt;Is there any other suggestion which will resolve this issue without affecting users work.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 11 Mar 2013 10:28:08 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/s-program-impacts/m-p/9330002#M1729180</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2013-03-11T10:28:08Z</dc:date>
    </item>
    <item>
      <title>Re: S_PROGRAM Impacts</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/s-program-impacts/m-p/9330003#M1729181</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I believe the easiest way to work around this issue is to create custom transactions (&lt;STRONG&gt;SE93&lt;/STRONG&gt;) for the Z* reports the users currently execute via SA38. &lt;/P&gt;&lt;P&gt;auditors usually don't like the fact that SE/SA38 is handed out to end users because there's little control over which reports a user is allowed to execute.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 11 Mar 2013 12:48:44 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/s-program-impacts/m-p/9330003#M1729181</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2013-03-11T12:48:44Z</dc:date>
    </item>
  </channel>
</rss>

