! Disclaimer ! This blog only replicates the information from the SAP Note 67739 as of March 9th, 2018 - further updates may apply.
SAP defines the priorities for incidents (reported problems/issues/bugs/inquiries/etc.) as follows:
1. Very high:
An incident should be categorized with the priority "very high" if the problem has very serious consequences for normal business processes or IT processes related to core business processes. Urgent work cannot be performed.
This is generally caused by the following circumstances:
- A productive system is completely down.
- The imminent system go-live or upgrade of a production system can't be completed.
- The customer's core business processes are seriously affected.
- And for each circumstance a workaround is not available.
The incident requires immediate processing because the malfunction may cause serious losses.
In case of a go-live or upgrade, the reason to delay the go-live or upgrade must be one that would cause serious losses if not resolved before go-live.
What the customer must do to ensure prompt processing of incidents with the priority "very high":
- Remote access to the relevant system must be ensured.
- A contact person must be designated for opening the system who must be available and can provide the required logon data.
- A contact person must be available to provide information about the problem.
- The problem should be described in as much detail as possible: the incident should contain instructions about how to simulate the problem.
- To ensure 24/7 processing, the incident must be written in English.
2. High:
An incident should be categorized with the priority "high" if normal business processes are seriously affected. Necessary tasks cannot be performed. This is caused by incorrect or inoperable functions in the SAP system that are required immediately. For example; users cannot access the system, a go-live cannot be completed, users complete data is not accessible, etc.
The incident is to be processed as quickly as possible because a continuing malfunction can seriously disrupt the entire productive business flow.
3. Medium:
An incident should be categorized with the priority "medium" if normal business processes are affected. The problem is caused by incorrect or inoperable functions in the SAP system.
4. Low:
An incident should be categorized with the priority "low" if the problem has little or no effect on normal business processes. The problem is caused by incorrect or inoperable functions in the SAP system that are not required daily, or are rarely used.
Further interesting information may be found
here.
