<?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: Transaction SOST performance issue in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/transaction-sost-performance-issue/m-p/886775#M52671</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;This is a similar question to above....in our QA system there are alot of email generated and in status waiting. We don't want all these emails to be sent. Is there away to schedule a job that will delete the mails with waiting status older than a certain date.&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Jim&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 20 May 2005 01:15:14 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2005-05-20T01:15:14Z</dc:date>
    <item>
      <title>Transaction SOST performance issue</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/transaction-sost-performance-issue/m-p/886773#M52669</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The execution of SOST tcode raises performance issue as it takes up too long time to generate the report.&lt;/P&gt;&lt;P&gt;I guess deletion of unwanted records from SOST tabel will help to improve.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Before deleting it I need to know what are the data that populates this table.Is it system generated messages,mails,faxes or any other types.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If it is SAP mails, then there are few standard Inbox reorg programs which can be used to delete data from relevant tables including SOST table.But even this does not helping.As there are still records left out in SOST table.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If user were to distinguish the types of data and then delete ,it how it can be done?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please  come up with your valuable suggestion&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Priya&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 11 May 2005 12:49:06 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/transaction-sost-performance-issue/m-p/886773#M52669</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2005-05-11T12:49:06Z</dc:date>
    </item>
    <item>
      <title>Re: Transaction SOST performance issue</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/transaction-sost-performance-issue/m-p/886774#M52670</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If you look at the code, SOST is nothing but a big select statement with a bunch of joins accross the tables SOOS, SOES, SOOD, SOST and SOSC.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The data that is there in these tables pertain to messages that need to go out of the SAP environment to external systems/applications. Communication method tells you all the different types of data that it selects.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SAP mails per se doesn't have to be here unless it involves sending mails out to internet(ie outside of SAP). So even if the users delete it from their inboxes it is not going to help.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would imagine you don't need to keep the successfully sent ones in the system anymore. Similarly you may not want to keep any messages that are say a year or more older. The best way to deal with it is to archive the data. You can schedule a job to do that for the program RSSOSOOS.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Srinivas&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PS; I think you accidentally created two posts with the same title. Please close the other one.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 11 May 2005 15:38:36 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/transaction-sost-performance-issue/m-p/886774#M52670</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2005-05-11T15:38:36Z</dc:date>
    </item>
    <item>
      <title>Re: Transaction SOST performance issue</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/transaction-sost-performance-issue/m-p/886775#M52671</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;This is a similar question to above....in our QA system there are alot of email generated and in status waiting. We don't want all these emails to be sent. Is there away to schedule a job that will delete the mails with waiting status older than a certain date.&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Jim&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 20 May 2005 01:15:14 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/transaction-sost-performance-issue/m-p/886775#M52671</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2005-05-20T01:15:14Z</dc:date>
    </item>
  </channel>
</rss>

