<?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: service level aggrement in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/service-level-aggrement/m-p/3316935#M794513</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;An SLA is an agreement between the business (the end users) and the support group what the response times for a certain issue are.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It defines how much time support needs (at the most) to react on a problem, and to resolve the problem. It aslo defines what the different priorities of the problems are and the time frames for each priority.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Usually whenever a user reports a problem a 'ticket' is created to track process and resolution.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;e.g. If you are creating an OSS message reporting to SAP that you found a product bug, this would be one ticket.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In regard to timeframes this usually differs from SLA to SLA, e.g. if you raise a VERY HIGH OSS message SAP is supposed to react (start working) on that OSS within one hour.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Usually the higher the priority the smaller the reaction time and also maximum processing time to resolve the problem is.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You would solve a ticket by analyzing the problem e.g. through debugging the example and once you identified the problem making the appropriate coding changes to correct the issue.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope that explains it,&lt;/P&gt;&lt;P&gt;Michael&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 24 Jan 2008 20:31:08 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2008-01-24T20:31:08Z</dc:date>
    <item>
      <title>service level aggrement</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/service-level-aggrement/m-p/3316934#M794512</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi frds&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; i want to know what is SLA  and what r the &lt;/P&gt;&lt;P&gt;high , medium ,  and  low  priorities.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;what is  ticket?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;give me one example  how to solve a ticket.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;plz mail me to  sudhakarbabu786@rediffmail.com&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 24 Jan 2008 09:56:36 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/service-level-aggrement/m-p/3316934#M794512</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-01-24T09:56:36Z</dc:date>
    </item>
    <item>
      <title>Re: service level aggrement</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/service-level-aggrement/m-p/3316935#M794513</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;An SLA is an agreement between the business (the end users) and the support group what the response times for a certain issue are.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It defines how much time support needs (at the most) to react on a problem, and to resolve the problem. It aslo defines what the different priorities of the problems are and the time frames for each priority.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Usually whenever a user reports a problem a 'ticket' is created to track process and resolution.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;e.g. If you are creating an OSS message reporting to SAP that you found a product bug, this would be one ticket.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In regard to timeframes this usually differs from SLA to SLA, e.g. if you raise a VERY HIGH OSS message SAP is supposed to react (start working) on that OSS within one hour.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Usually the higher the priority the smaller the reaction time and also maximum processing time to resolve the problem is.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You would solve a ticket by analyzing the problem e.g. through debugging the example and once you identified the problem making the appropriate coding changes to correct the issue.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope that explains it,&lt;/P&gt;&lt;P&gt;Michael&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 24 Jan 2008 20:31:08 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/service-level-aggrement/m-p/3316935#M794513</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-01-24T20:31:08Z</dc:date>
    </item>
  </channel>
</rss>

