Over the years SAP has made huge investment in the Service Operations area of Solution Manager and the new version which is 7.1 today provides flexibility to all SAP customers to implement IT Service Management for entire SAP and non SAP landscape.
In my experience, this is a journey and we should not jump on it doing everything at the same time but rather go step by step to implement the various capabilities of IT Service Management in Solution Manager 7.1.
During several implementations for IT Service Management in SAP Solution Manager 7.1, we have come across a common requirement to have multiple SLA or Service Level Agreements for support.
This blog series will focus on detailed configuration or implementation steps for setting up multiple SLA based upon Multilevel categorization(MLC) or the different type of incident.
Basic concept of SLA
Service Level Agreements (SLA) are typically agreed by SAP Customer with vendors who provide support or services adhering to their requirements
Typically there can be various criteria for having different SLA requirements. For every customer SLAs can be different based upon business conditions or support requirements i.e. either service basis or for specific product basis etc.
Service Level Agreements (SLA) in Solution Manager works upon two main concepts of:
The basic concept are already explained in detail over wiki on below link
SLA Management - SAP IT Service Management on SAP Solution Manager - SCN Wiki
Just to add further over Service and Response Profile
Thus, based upon the actual situation, if we don’t see the incident IRT and MPT meeting then it is called as SLA breach or violation.
This has severe impacts based upon the contract between customer and vendor. We can build reports in Solution Manager to see the entire list of incident which are breaching IRT or MPT etc in SM_CRM transaction.
Typically, in my organization, we have seen several SAP customer’s going for a 24*7 ( i.e. 24 hours and 7 days working) support model or 12*5 (i.e. 12 hours and 5 days a week) support model based upon their specific support requirements with respect to region wise, SAP/ non SAP incidents i.e. category of incident or SAP Module wise like SD, MM, FI, etc. Therefore, it is very much possible to have a one customer who would like to have multiple SLA which means separate SLA for SAP tickets and other one for Non SAP Tickets.
Basically, the minimum is to have a properly copied transaction type (ZMIN/YMIN) which is having the relevant status profile and other configurations with master data in place.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
7 | |
5 | |
5 | |
5 | |
4 | |
4 | |
4 | |
4 | |
3 | |
3 |