SAP ASAP Vs SolMan

ASAP Vs Solution Manager

ASAP methodology and Solution Manager are not one and the same. ASAP is a methodology to implement SAP projects in the earlier years.

Around 3 years ago SAP brought out new product Solution Manager - which is a comprehensive tool for Project implementation, keeping track of documentation, tracking enhancement projects and also for tracking production support issues. It is one place where every thing is kept. And the added advantage of solution manager has got authorization facility, hence all users cannot access the documents. Tracking the changes is made simple. In view of regulatory requirements like SOX audit etc, this is very useful.

The SAP Solution Manager supports you throughout the entire lifecycle of your solutions, from the Business Blueprint thru configuration to production operation. It provides central access to tools methods and preconfigured content, that you can use during the evaluation, implementation, and productive operation of your systems.

AcceleratedSAP (ASAP) is SAP's standard implementation methodology. It contains the Roadmap, a step-by-step guide that incorporates experience from many years of implementing R/3. Along with that, AcceleratedSAP contains a multitude of tools, accelerators and useful information to assist all team members in implementing R/3. Quality checks are incorporated at the end of each phase to easily monitor deliverables and critical success factors. ASAP is delivered as a PC-based package, so that - if required - an implementation project can begin prior to having an R/3 System installed.

AcceleratedSAP (ASAP): A comprehensive solution for the introduction of the R/3 System in your enterprise. ASAP and most of its tools can be used independently of an R/3 installation.

The tools available for AcceleratedSAP are:
The Project Estimator, an internal SAP tool which enables SAP consultants to accurately gauge the required resources, the costs and the time frame of implementation. The Project Estimator takes into account the project scope and several project and risk factors.
The Concept Check Tool, a tool enabling you to carry out quality checks on the project preparation, technical infrastructure and R/3 configuration settings. This is done mainly during the first two implementation phases of the R/3 project. In this way you are alerted to potential data volume and configuration conflicts that could lead to performance issues if not addressed.
The Implementation Assistant: The ASAP navigation tool that accompanies you through the five phases of implementation down to the task level. It includes a description and a detailed "how-to" for each task in the Roadmap. Along with that, many tools, templates and documents are hyperlinked to the task. The Implementation Assistant contains the following elements:
ASAP Implementation Roadmap and Project Plan. The Roadmap contains the five phases, from which you can drill down into work packages, activities and tasks. The Project Plan contains three components, a budget plan, a resource plan and a work plan. These are explained in more detail in the next chapter.

The ASAP Roadmap is the successor of the R/3-based Procedure Model, which was used until Rel. 3.1 in R/3 implementation projects.
Knowledge Corner, containing tips and tricks for configuration from consultants, detailed documentation on SAP’s implementation services, information on technical tools, as well as simplification guidebooks and R/3 Customizing wizards.
Question and Answer Database (Q&Adb). Using the R/3 Reference Model structure, the Q&Adb is used to assist in gathering requirements for business processes, conversions, reports, interfaces, enhancements and authorizations. The database provides useful questionnaires to help you define the process needs and also serves as a repository for all this information. Since it is a database, it allows for flexible reporting. The business requirements generated from the Q&Adb are collectively known as the Business Blueprint.
Business Process Master List, to manage configuration, testing and the creation of end user documentation. The Business Process Master List is linked to pre-written Business Process Procedures (BPPs), detailled end-user documentation for R/3 transactions.
Issues Database: supporting project management, this database supports the entering, monitoring and managing of issues that come up during the project.

What is SAP Solution Manager:

SAP Solution Manager is a tool, which assists in application management as per ITIL (IT Infrastructure Library) environment. The tool supports the entire lifecycle of solutions mainly having six phases – Requirements, Design, Build, Deploy, Operate & Optimize as per ITIL standard.
It runs in a separate central system to which all the other SAP systems are connected. These other systems are called as Satellite Systems.

Latest Version:

SAP Solution Manager 4.0.

Features of SAP Solution Manager:

·         Solution Manager helps in all types of project management like Implementation, Upgrade, Maintenance, Rollout etc. by providing the project specific template.

·         It is in line with SAP’s AcceleratedSAP. And provide Roadmaps for the different types of projects.

·         It has Business Process Repository, which talks about SAP’s best practice of running the business.

·         It has eLearning feature, which offers the training along with feedback over web.

·         It has test management feature, which offers the central storage repository for storing the automated eCATT scripts along with manual scripts. The results of testing are centrally stored and always available.

·         It has its own standard Helpdesk feature, which is both SAPGUI based and web based.

·         The Helpdesk feature is totally linked with Change Request Management, which helps in transport for changes required in production issues.

·         It has Solution Monitoring as well as Diagnostic feature, which helps in Operation Phase of project.

·         Solution Manager has lots of inbuilt reports, which server the different areas of it.

·         It is linked with SAP Service Market Place.

·         It can generate Installation/Upgrade key.

·         It has its own Knowledge Warehouse for central documentation storage.

·         It can integrate with ARIS, a detailed graphical business process modeling tool

·         It can also integrate with Mercury tools like QTP for testing in web based environment.

Template Project Type:

·         In Template project type, only the documentation under Gen. Documentation tab in Business blueprint phase is shared to the rolling out implementation project. The requirement of sharing the Project Documentation tab arises many a times.

SOLAR02 Transaction code: Configuration:

·         The development objects are required to develop first in the satellite system and then only the objects can be linked in solution manager. This option increases the chances of missing the objects for those business scenarios. Also the transport request won't be tracked back in solman.

·         The dropdown of the development object shows only limited type of objects. Ideal expectation is that for all the connected satellite systems, the respective development object types which can be attached to a transport request should be automatically populated in the dropdown.

Test Management:

·         The reporting feature of test management is not so user friendly. Specifically in a scenario where the testing is done successfully and logs are recorded in solution manager with few scripts failed. For the failed scripts one has to drill down a lot in the log till the consultant gets the exact issue. This is more painful if the external tool like Mercury QTP is connected to Solution Manager for web based testing like SRM/CRM.

·         The eCATT logs are not at all user friendly. If there is a functional error like GL account doesn't exist then it will be conveyed very clearly in the log. But if is related to some screen mismatch at the run time for that recorded script the such technical errors are very hard to find out from the logs.

·         The SAPGUI pattern of recording is extremely slow and take too much of time for recording enjoy transactions. It not only takes long time for recording but also long time for execution.

·         eCATT doesn’t serve the web based transactions for testing.

Helpdesk Application:

·         There is a BAPI for creating the helpdesk message but no BAPI is available for modification.

·         One has to follow the transaction for helpdesk ticket changes via BDC or so. e.g. CRM_DNO_MONITOR or CRMD_ORDER transaction can be used to modify the ticket. The problem with these transactions is that BDC of these transactions doesn't work if it is run under workflow/background job.

·         The CRM_DNO_MONITOR transaction has a feature of 'Mine' in the selection screen, which shows the tickets created by logged in user. Here all the tickets created by logged in user for different satellite systems should appear. But it shows only tickets created for only one of the satellite systems, whos external Business Partner(employee type) is linked with solution mananger ID. As per the concept of CRM, only one external Business Partner (employee type) can be connected to solution manager ID. Hence rest other satellite systems external business partner are never connected to Solman ID. So the logged in user can not see all his tickets created in different satellite systems.

·         The web interface for the helpdesk application is not really very user friendly. E.g. selection of Component End users won't be aware about the link between their problem and the relevant SAP Component.

·         There should be easy provision available for linking this helpdesk application to SAP Portal as most of the clients do have portal as a central point of access via their users.

·         Automatic assignment of tickets should happen while creation depending on the skills with consideration of availability on that day & workload. And then the concern person should be informed on different communication channel like emails, pager message etc.

·         The functionality of Solution Manager Helpdesk should be like service marketplace with the provision for customized escalation.

·         Generally the clients have some or other legacy system for helpdesk and end uses are very much used to that. Considering this, the layout of the solution manager helpdesk for ticket creation should be very flexible to give the end users enough comfort level in new helpdesk environment.

·         Linking of External Helpdesk to Solution Manager Helpdesk has lots of problems like status profile synchronization etc if the other system is also SAP Solution Manager. And if the connected system is a legacy system then issues of Sold-to-Party etc fields without any values are assigned to them is also there.

Common concerns:

·         Transaction codes are too long to remember.

·         Lots of configuration settings are available in solution manager. A simple handy guide should be available for the different areas of Solman considering this configuration. Even recorded tutor files in this concern will also help to utilize these features efficiently.

ASAP
ASAP stands for Accelerated SAP. Its purpose is to help design SAP implementation in the most efficient
manner possible. Its goal is to effectively optimize time, people, quality and other resources, using a proven
methodology to implementation.
ASAP focuses on tools and training, wrapped up in a five-phase process oriented roadmap for guiding
implementation.
The road map is composed of five well-known consecutive phases:
• Phase 1 Project Preparation
• Phase 2 Business Blueprint
• Phase 3 Realization
• Phase 4 Final Preparation
• Phase 5 Go-Live and support
In today's post we will discuss the first phase.
Phase 1 : Project Preparation
Phase 1 initiates with a retrieval of information and resources. It is an important time to assemble the
necessary components for the implementation. Some important milestones that need to be accomplished
for phase 1 include
• Obtaining senior-level management/stakeholder support
• identifying clear project objectives
• architecting an efficient decision-making process
• creating an environment suitable for change and re-engineering
• building a qualified and capable project team.
Senior level management support:
One of the most important milestones with phase 1 of ASAP is the full agreement and cooperation of the
important company decision-makers - key stakeholders and others. Their backing and support is crucial for a
successful implementation.
Clear project objectives:
be concise in defining what your objectives and expectations are for this venture. Vague or unclear notions of
what you hope to obtain with SAP will handicap the implementation process. Also make sure that your
expectations are reasonable considering your company's resources. It is essential to have clearly defined
ideas, goals and project plans devised before moving forward.
An efficient decision making process:
One obstacle that often stalls implementation is a poorly constructed decision-making process. Before
embarking on this venture, individuals need to be clearly identified. Decide now who is responsible for
different decisions along the way. From day one, the implementation decision makers and project leaders
from each area must be aware of the onus placed on them to return good decisions quickly.
Environment suitable for change and re engineering:
Your team must be willing to accept that, along with new SAP software, things are going to change, the
business will change, and information technology enabling the business will change as well. By
implementing SAP, you will essentially redesign your current practices to model more efficient or predefined
best business practices as espoused by SAP. Resistance to this change will impede the progress of your
implementation.
Building a qualified project team:
Probably the most important milestone early in assembling a project team for the implementation. If you are
implementing the materials management and plant maintenance modules, you need to include people from
both of these departments. The team should also represent management as well as non management or
"functional" personnel. Sometimes management is less aware of the day-to-day functions of an organization,
including how implementing SAP will tactically influence those function

ASAP- Second Phase- Business Blueprint
SAP has defined a business blueprint phase to help extract pertinent information about your company that is
necessary for implementation. These blueprints are in the form of questionnaires that are designed to probe
for information that uncovers how your company does business. As such, they also serve to document the
implementation. Each business blueprint document essentially outlines your future business processes and
business requirements. The kinds of questions asked are germane to the particular business function, as
seen in the following sample questions:
1) What information do you capture on a purchase order?
2) What information is required to complete a purchase order?
Accelerated SAP question and answer database:
The question and answer database (QADB) is a simple although aging tool designed to facilitate the creation
and maintenance of your business blueprint. This database stores the questions and the answers and
serves as the heart of your blue print. Customers are provided with a customer input template for each
application that collects the data. The question and answer format is standard across applications to
facilitate easier use by the project team.

Issues database:
Another tool used in the blueprinting phase is the issues database. This database stores any open concerns
and pending issues that relate to the implementation. Centrally storing this information assists in gathering
and then managing issues to resolution, so that important matters do not fall through the cracks. You can
then track the issues in database, assign them to team members, and update the database accordingly.

ASAP Phase- 3 - Realization:
With the completion of the business in phase 2, "functional" experts are now ready to begin configuring SAP.
The Realization phase is broken in to two parts.
1) Your SAP consulting team helps you configure your baseline system, called the baseline configuration.
2) Your implementation project team fine-tunes that system to meet all your business and process
requirements as part of the fine tuning configuration.

The initial configuration completed during the base line configuration is based on the information that you
provided in your blueprint document. The remaining approximately 20% of your configuration that was not
tackled during the baseline configuration is completed during the fine tuning configuration. Fine tuning
usually deals with the exceptions that are not covered in baseline configuration. This final bit of tweaking
represents the work necessary to fit your special needs.

Configuration Testing:
With the help of your SAP consulting team, you segregate your business processes into cycles of related
business flows. The cycles serve as independent units that enable you to test specific parts of the business
process. You can also work through configuring the SAP implementation guide (IMG). A tool used to assist
you in configuring your SAP system in a step-by-step manner.

Knowledge Transfer:
As the configuration phase comes to a close, it becomes necessary for the Project team to be self-sufficient
in their knowledge of the configuration of your SAP system. Knowledge transfer to the configuration team
tasked with system maintenance (that is, maintenance of the business processes after Go-live) needs to be
completed at this time.
In addition, the end users tasked with actually using the system for day-to-day business purposes must be
trained.

ASAP Methodology - Phase 4 - Final Preparation:
As phase 3 merges into phase 4, you should find yourselves not only in the midst of SAP
training, but also in the midst of rigorous functional and stress testing. Phase 4 also
concentrates on the fine tuning of your configuration before Go-live and more importantly, the
migration of data from your old system or systems to SAP.
Workload testing (including peak volume, daily load, and other forms of stress testing), and
integration or functional testing are conducted to ensure the accuracy of your data and the
stability of your SAP system. Because you should have begun testing back in phase 2, you do
not have too far to go until Go-live. Now is an important time to perform preventative
maintenance checks to ensure optimal performance at your SAP system.
At the conclusion of phase 4, take time to plan and document a Go-live strategy. Preparation for
Go-live means preparing for your end-users questions as they start actively working on the new
SAP system.

ASAP - Phase 5 - Go-live and Support:
The Go-live milestone is itself is easy to achieve; a smooth and uneventful Go-live is another
matter altogether. Preparation is the key, including attention to what-if scenarios related not only
to the individual business processes deployed but also to the functioning of technology
underpinning these business processes and preparation for ongoing support, including
maintenance contracts and documented processes and procedures are essential

solutionmanager means,
SAP Solution Manager
Purpose

The SAP Solution Manager supports you throughout the entire lifecycle of your solutions, from the Business Blueprint thru configuration to production operation. It provides central access to tools methods and preconfigured content, that you can use during the evaluation, implementation, and productive operation of your systems.

Features

Implementation of the mySAP Business Suite

• All phases of the implementation project (Business Blueprint, Configuration) are performed centrally in the Solution-Manager system.

• Central project documentation repository in the Solution Manager

• Integrated Project Administration allows you to manage planning schedules, human resources and other project data.

Customizing Synchronization

• The Customizing Scout, with which you can compare customizing in various SAP components, e.g. an ERP system with SAP MDM

• The Customizing Distribution, with which you can synchronize customizing in various SAP components.

Test

• You can use the Test Workbench to organize and perform tests at the end of a project phase.

• Reuse of the project structure for process-oriented tests

Global rollout

Integrated authoring environment, with which customers and partners can create their own templates, which they can reuse in subsidiaries, e.g. in a global rollout

E-Learning management

Creation of training material and learning maps (computer-supported self-tuition courses) to train end users after the implementation of new functions

Solution Monitoring

• Central system administration

• Analyze your system landscape with Service Level Reporting

• System monitoring in real time

• Business Process Monitoring

Services

Access to programs and Services, which help you to monitor and optimize the performance and availability of your system landscapes, and minimize your operational system risks

Service Desk

Solution support with workflow to create and handle problem messages

Change Management

Management of change requests, with workflow for the monitoring and audit of changes and transports in your system landscape, with the Change Request Management.

See also:

• Projects

• Solution Monitoring

SAP Solution Manager Roles
Authorization Concept
• Project Authorizations

The following composite roles contain the authorizations required for the tasks to be performed in a project:

○ Project Leader
○ Application Consultant
○ Development Consultant
○ Technical Consultant
There are individual roles for Roadmap administration.

• Production Authorizations

Production authorizations are in individual roles for the functions:

○ Solution Directory
○ Solution Monitoring
○ Service Data Control Center
○ Service Desk
○ Corporate Functionality
○ Solution Manager Diagnostics
○ Solution Reporting
Use
Adjust the SAP Solution Manager roles to your requirements.

Overview of Roles in Solution Manager

If you use trusting-trusted RFC connections, assign the authorization profile S_RFCACL to the user, as well.

Scenario Role
Implementation and Distribution SAP_SOL_PM_COMP
SAP_SOL_AC_COMP
SAP_SOL_BC_COMP
SAP_SOL_TC_COMP
SAP_SOL_RO_COMP
SAP_SOL_RE_COMP
SAP_SOL_LEARNING_MAP_DIS
SAP_DMDDEF_DIS
Implementation and Distribution (Roadmaps) SAP_RMDEF_RMAUTH_EXE
SAP_RMDEF_RMAUTH_DIS
Implementation and Distribution (E-Learning Management) SAP_SOL_TRAINING_EDIT
Service Desk (Service Desk) SAP_SUPPDESK_ADMIN
SAP_SUPPDESK_PROCESS
SAP_SUPPDESK_CREATE
SAP_SUPPDESK_DISPLAY
Service Desk (Corporate Functionality) SAP_SUPPCF_ADMIN
SAP_SUPPCF_CREATE
SAP_SUPPCF_PROCESS
Service Desk (Issue Tracking) SAP_SV_SOLUTION_MANAGER
SAP_SV_SOLUTION_MANAGER_DISP
SAP_SUPPDESK_ADMIN
SAP_SUPPDESK_PROCESS
SAP_SUPPDESK_DISPLAY
Change Request Management (Schedule Manager; Service Desk, cProjects)

SAP_CM_CHANGE_MANAGER
SAP_CM_DEVELOPER_COMP
SAP_CM_TESTER_COMP
SAP_CM_OPERATOR_COMP
SAP_CM_PRODUCTIONMANAGER_COMP
SAP_SOCM_REQUESTER
SAP_CM_ADMINISTRATOR_COMP
Solution Monitoring
(Service Data Control

Center)
SAP_SDCCN_ALL
SAP_SDCCN_DIS
SAP_SDCCN_EXE
Solution Monitoring
(Solution Directory)
SAP_SOLMAN_DIRECTORY_ADMIN
SAP_SOLMAN_DIRECTORY_EDIT
SAP_SOLMAN_DIRECTORY_DISPLAY
Solution Monitoring
(Operations)
SAP_SV_SOLUTION_MANAGER
SAP_SV_SOLUTION_MANAGER_DISP
SAP_SETUP_DSWP
SAP_SETUP_DSWP_SLR
SAP_SETUP_DSWP_SM
SAP_SETUP_DSWP_BPM
SAP_SETUP_DSWP_CSA
SAP_OP_DSWP
SAP_OP_DSWP_SLR
SAP_OP_DSWP_SM
SAP_OP_DSWP_EWA
SAP_OP_DSWP_BPM
SAP_OP_DSWP_CSA
Solution Reporting SAP_SOL_REP_ADMIN
SAP_SOL_REP_DISP
Solution Manager Diagnostics SAP_SMDIAG_WIZARD
SAP_SMDIAG_TEMPLATE

Cf.:

● Overview of Roles and Profiles in Satellite Systems

● SAP Solution Manager 4.0 configuration guide

● SAP note 834534

● SAP note 803142

Overview of Roles and Profiles in the Satellite Systems

Use the profiles below for SAP R/3 Release before SAP Web Application Server 6.10. Use the profiles below from SAP R/3 Release SAP Web Application Server 6.10.

If you use a trusting-trusted RFC connection, assign the authorization profile S_RFCACL to the user, as well.

Scenario Roles (Release > 6.10) Profile (< 6.10) Explanation
Change Request Management SAP_CHANGEMAN_DEVELOPER S_TMW_DEVELO Developer authorization
SAP_CHANGEMAN_PROJECTASSISTANT S_TMW_PRJEC Project Assistant Authorizations
SAP_CHANGEMAN_PROJECTLEAD S_TMW_PRJALL Project Leader Authorization
SAP_CHANGEMAN_OPERATOR S_TMW_OPERA Operational Processing Authorization
SAP_CHANGEMAN_ADMIN S_TMW_ADMIN Administration Authorization
Solution Monitoring
(Service Data Control

Center)
For Basis WebAs 6.20
SAP_SDCCN_ALL
For Basis 4*
S_SDCCN_ALL
Service Data Control Center Administration
For Basis WebAs 6.20
SAP_SDCCN_EXE
For Basis 4*
S_SDCCN_EXE
Using the Service Data Control Center
For Basis WebAs 6.20
SAP_SDCCN_DIS
For Basis 4*
S_SDCCN_DIS
Service Data Control Center display user
Implementation and Distribution (Customizing Distribution and Comparison) SAP_BC_CUS_ADMIN Administration of a customizing project, see SAP note 454898
SAP_BC_CUS_CUSTOMIZER Change customizing settings
S_CUS_CMP See also Online Documentation: SAP Solution Manager -> Projects -> Customizing Distribution and Comparison system settings
Implementation and Distribution (Customizing Scout and System Landscape) SAP_SOLAR_SATELITE_SCOUT Customizing Scout
SAP_SOLAR_SATELITE_SMSY System Landscape
Implementation Distribution (CATT) SAP_BC_CAT_TESTER Test with CATT
SAP_BC_CAT_TESTORGANIZER Test organization with CATT
Implementation and Distribution (eCatt) Cf. SAP note 519858
Implementation and Distribution (Test Workbench) SAP_TWB_TESTER Test with Test Workbench
SAP_TWB_COORDINATOR Coordination with Test Workbench
SAP_TWB_ADMINISTRATOR Administration with Test Workbench
Implementation and Distribution (BC Sets) SAP_BCS_ACTIV Activation of BC Sets; see SAP note 505603
SAP_BCS_CREAT Create BC Sets
SAP_BCS_ADMIN Administration of BC Sets
Service Desk SAP_SOL_SERVTRANS_CREATE

Send messages from satellite system to Solution Manager (function path: Menu ® Help ® Create Support Messages), You need the authorization object S_RFC (profile S_RFC_VERS), with the activity Execute for the object SAPSMO*.

Cf.:

● Overview of Roles in Solution Manager

● SAP Solution Manager 4.0 configuration guide

● SAP note 834534

● SAP note 803142

Profile and Role Overview for Background Users

If you generate RFC connections in the system maintenance (transaction SMSY), the Solution Manager system automatically creates background users for all RFC connection types, and assigns profiles.

If you want to use an existing satellite system user as background user, you must publish it in the Solution Manager, and enter as background user, in the system maintenance (dialog: RFC Generation). In this case, you must assign profiles or roles for the basis release, manually (see table):

WEB Application Server less than 6.10, assign the profiles to the users
WEB Application Server more than 6.10, assign the roles to the users (copy and adjust roles).
Assign the role SAP_D_SOLMAN_RFC (analogous: profile D_SOLMAN_RFC) to the RFC user SOLMAN<satellite system ID><_version in the SAP Solution Manager.

RFC user Roles (Release > 6.10) in the satellite system Profile (< 6.10) in satellite system Reason
SOLMAN<SAP Solution Manager system ID><CLNT> SAP_S_CUS_CMP S_CUS_CMP Data read access
SAP_S_CMSREG S_CMSREG Central system repository data
SAP_S_BDLSM_READ S_BDLSM_READ SDCCN data
SOLTMW<SAP Solution Manager system ID><CLNT> SAP_S_CUS_CMP S_CUS_CMP Data read access
SAP_S_CMSREG S_CMSREG Central system repository data
SAP_S_BDLSM_READ S_BDLSM_READ SDCCN data
SAP_S_TMW_CREATE S_TMW_CREATE Create task in development system
SAP_S_TMW_IMPORT S_TMW_IMPORT Import task into test system
SOLMAN<Satellite system ID><_version> SAP_S_CUS_CMP S_CUS_CMP Data read access
SAP_S_CMSREG S_CMSREG Central system repository data
SAP_S_BDLSM_READ S_BDLSM_READ SDCCN data

Adjust Roles and Profiles
Before you assign SAP standard roles and profiles to users, copy and specify them.

SAP delivers roles and profiles with default values. If they are missing, you must set the values in the authorization objects yourself. Proceed as follows:

...
1. Load the roles/profiles from client 000 into your target client. You can:
○ Transport client 000 into your target client (roles and profiles)
○ Upload und Download (for roles in transaction PFCG)
○ RFC connection in transaction PFCG (for roles; menu path: MENU ® READ FROM OTHER SYSTEM WITH RFC). In this case, you must have set-up the RFC connection (transaction SM59).
2. Copy the roles/profiles into your namespace.
a. Choose Role Maintenance (transaction PFCG).
b. Enter a role name and choose Copy Role.
c. Enter the name of the new role in the To Role field.
d. Choose Copy All.
e. Save.
3. Complete missing values in the authorization objects.
a. Choose the Authorizations tab.
b. Choose ChangeAuthorization Data.
c. Enter your own values for the authorization objects, or double-click on the yellow traffic light.
The authorization objects appear with a green traffic light.

d.
When you double-click on the yellow traffic light, the value “*” appears. This grants full authorization for this field of the authorization object.

e. Save.
f. Generate the authorization profile.
4. Assign the role to users.
a. Choose the Users tab.
b. Enter the user names.
c. Choose User Adjustment.
d. Save.
You can also assign the roles to the users, in the user maintenance (transaction SU01).

e.
Project Authorization

Roles

The roles in the SAP Solution Manager are composite roles, which contain individual roles, which in turn contain authorizations for individual functions, e.g. for the Business Blueprint.

The following composite roles contain the central authorizations which they require for projects, and can be tailored to suit individual projects:

● Project leaders SAP_SOL_PM_COMP are responsible for organizing and planning the project, and monitoring costs and deadlines.

● Application consultants consultants SAP_SOL_AC_COMP are responsible for business content and the documentation of operational activities. This composite role has limited authorization and is intended for project members who need to be adjusted individually.

● Development consultants SAP_SOL_BC_COMP are responsible for the development of customer-specific programs and authorizations.

● Technical consultants SAP_SOL_TC_COMP are responsible for installing systems and providing technical support to users.

● Display user/Read only SAP_SOL_RO_COMP: contains SAP Solution Manager display/read only authorization.

● Read authorization depending on status in Document Management SAP_SOL_RE_COMP: only contains read authorization per status in Knowledge Warehouse Document Management

See also:

● Solution Manager Roles Overview

● Overview of Roles and Profiles in Satellite Systems

● SAP Solution Manager 4.0 configuration guide

● SAP note 834534 (Roles in the Solution Manager)

● SAP note 803142 (Roles in Satellite Systems)

Project Manager
Technical name: SAP_SOL_PM_COMP

Tasks
Project managers are responsible for the realization of the desired project results and the daily management of the project. They anticipate deviations from the project direction and carry out the necessary corrective measures immediately. Project managers should also understand the integration of the business processes within the enterprise.

Project managers are also members of the steering committee. They have decision-making authority in matters concerning the program and budget. He forwards strategic questions to the sponsor in order to make joint decisions.

Activities in SAP Solution Manager
The main responsibilities of the project manager include:

• Organizing the entire project

• Developing strategies and procedures for an efficient SAP implementation

• Developing and maintaining the time schedule for the implementation project

• Finalizing and managing the project scope, budget and deadlines in accordance with the approved plans

• Assigning and managing resources

• Monitoring project progress on a weekly basis

• Carrying out evaluations and analyses

• Carrying out a formal review at the end of each phase

• Clarifying open issues in good time

• Reporting regularly to the review committee on the progress and status of the project

• Representing the project internally and externally

• Giving status updates to the whole project team

Project managers can also copy content from a ValueSAP Edition 2 project into an SAP Solution Manager project. See the migration tool documentation.

Notes on Tailoring
If you require additional authorization, you can use the role SAP_BC_CUS_ADMIN: It contains authorization for the administration of customizing projects in the component systems.

The SAP Solution Manager configuration guide contains further information about authorizations in the component systems.

Integration
The project manager defines the content and the time frame of an implementation project, manages resources and monitors project progress. The application consultant reports to him and supports him in an administrative function.

Application Consultant
Technical name: SAP_SOL_AC_COMP

Tasks
Application consultants are responsible for making sure that the Business Blueprint and software configuration are tailored to the business processes and that analysis and report requirements are fulfilled. They use their knowledge of proven business procedures to support them in these tasks. Application consultants also function as advisers and work closely with the rest of the project team.

They also work in close cooperation with legacy system experts, when extraction of legacy data is necessary.

Activities in SAP Solution Manager
The main responsibilities of the application consultant include:
• Supporting definition and modeling of business processes

• Checking how the business model works with the SAP products

• Configuring the software to suit the required business processes and to meet analysis and report requirements

• Determining the global and local standardization requirements

• Determining requirements for organizational change in the enterprise

• Supporting knowledge transfer to other project team members

• Supporting organization and performance of tests

• Defining requirements for authorization profiles and access authorizations

• Analyzing statistical performance and passing on recommendations for improvement to support

• Creating and developing data solutions and strategies to meet the requirements of the corresponding SAP component (for example, APO, BW, CRM)

• Creating end user training materials for the new functions

The application consultant is not responsible for:
• The technical implementation of the solution

• The programming of interfaces and other developments

• Recurring problems with the quality of data (problems with data quality should be passed on to the project manager)

Notes on Tailoring
This role only contains basic functions. The following roles are available for additional authorizations:

• SAP_BC_CUS_CUSTOMIZER contains authorizations for working with IMG activities.

The following role is useful for the application components:

• SAP_BC_CUS_CUSTOMIZER

Integration
Application consultants are responsible for the development of business content and the documentation of operative activities in accordance with the appropriate standards. The development consultant develops customer-specific programs and their authorizations.

Development Consultant
Technical name: SAP_SOL_BC_COMP

Tasks
Development consultants work with the project manager and the application consultant on the planning and organization of the authorization concept. They also perform developmental tasks and customer-specific developments.

Activities in SAP Solution Manager
The main responsibilities of the development consultant include:

• Organizing authorizations

• Developing ABAP programs, for example, interfaces, forms, or modifications

• Working with the ABAP Workbench

Notes on Tailoring
The following roles are available for additional authorizations:

• SAP_BC_DWB_ABAPDEVELOPER contains authorization for implementing new applications and enhancements and for changing and modifying standard applications using the tools and services provided in the ABAP Workbench.

• SAP_BC_TRANSPORT_ADMINISTRATOR contains all authorizations for the Change and Transport System

Integration
Development consultants work for the project manager and the application consultant and carry out programming tasks, in contrast to technical consultants who act as system administrators and are responsible for installing systems and providing technical support to users.

Technical Consultant
Technical name: SAP_SOL_TC_COMP

Tasks
Technical consultants plan the technical requirements for a project with the project manager and the manager of the technical team and then carry out the required technical tasks in the system.

Depending on the scope and complexity of the implementation, technical consultants may work in several areas, for example, system administration, database administration, network administration, operating system administration, development of cross-application components, or ABAP development.

For international projects, technical consultants also manage consultancy in the following areas:

Country-specific business requirements and country-specific SAP software requirements
Language-specific or codepage-specific requirements
Time-zone issues
Activities in SAP Solution Manager
The main responsibilities of the technical consultant include:

Setting up and installing the system landscape

Managing the system landscape and the corresponding transport landscape

Providing support and advice in all technical questions during an implementation project

Giving daily updates on the technical direction of the project including communicating deviations in the project

Developing and realizing the Cutover Plan before going live

Communicating effectively with the business process team

Transferring knowledge effectively to employees in system administration

In order to be able to carry out these tasks, the technical consultant should meet the following requirements:

A sound knowledge in the areas of databases, networks, programming and Internet technology

A sound knowledge of the SAP solutions

Notes on Tailoring
The following roles are available for additional authorizations:

SAP_BC_RRR_SAA_ADMIN provides the authorization for executing all the tasks in the System Administration Assistant.
Integration
The technical consultant acts as a system administrator and is responsible for installing systems and providing technical support to users, in contrast to the basis consultant who works under the instruction of the project manager and the application consultant and carries out programming tasks.

Read Authorization by Document Status
Technical name: <SAP_SOL_RE_COMP>

Tasks
This role assigns read authorization for documents with a specified status.

Authorization object S_IWB with activity: 33

Activities in <SAP_SOL_RE_COMP>
To use this composite role:

1. Maintain the activity SOLMAN_DOC_STATUS, under: SAP Solution Manager ® Scenario-Specific Settings ® Implementation ® Optional Activities ® Document Management ® Status for Documents, in the IMG (transaction SPRO).
2. Assign the role to the user.
You only see the documents for which you have made the appropriate settings in the IMG activity. If there are document versions, only the contents of the last version are shown. Attributes can always be displayed.

Adjustment
Adjust Roles and Profiles

Roles to Change Roadmaps
Technical name: SAP_RMDEF_RMAUTH_EXE

Technical name: SAP_RMDEF_RMAUTH_DIS

Tasks
The roles allow you to assign authorizations to change Roadmaps.

Activities in SAP_RMDEF_RMAUTH_EXE
This role allows you to change Roadmaps from an administrative perspective.

Activities in SAP_RMDEF_RMAUTH_DIS
With this role, you can display the changes to the Roadmaps.

Adjustment
Adjust the Roles

Operational Processing Authorizations
Definition

The authorization concept for the SAP Solution Manager Operations contains individual roles for specified areas of the SAP Solution Manager Operations. Show specified views of the characteristic tasks in operations.

Use

The roles in the SAP Solution Manager Operations are individual roles which contain the authorizations for individual functions and business roles. The individual roles are classified into:

● Solution Monitoring

● Change Request Management

● Service Data Control Center

● Service Desk

● Solution Directory

● Corporate Functionality

● Solution Reporting

● Solution Manager Diagnostics

Cf.:

● Overview of Roles in Solution Manager

● Overview of Roles and Profiles in the Satellite Systems

● SAP Solution Manager 4.0 configuration guide

● SAP note 834534 (Roles in the Solution Manager)

● SAP note 803142 (Roles in Satellite Systems)

Solution Directory Roles
Technical name:

● SAP_SOLMAN_DIRECTORY_ADMIN

● SAP_SOLMAN_DIRECTORY_EDIT

● SAP_SOLMAN_DIRECTORY_DISP

Definition
The Solution Directory authorization concept contains individual roles to:

● administer

● edit

● display

objects in the Solution Directory.

Activities in <SAP_SOLMAN_DIRECTORY_ADMIN>
Use the specified individual role to:

● edit or display business process scenarios, business processes, etc. of your solution, in the Solution Directory.

● create and change logical components

● create, change or display Solution Directory system data in the system landscape maintenance (transaction SMSY).

● display monitoring sessions

Activities in <SAP_SOLMAN_DIRECTORY_EDIT>
Use the specified individual role to:

● edit or display business process scenarios, business processes steps, etc. of your solution, in the Solution Directory.

● select and display logical components

● display data in the system maintenance (transaction SMSY) in the Solution Directory.

Activities in <SAP_SOLMAN_DIRECTORY_DISP>
Use the specified individual role to:

● display business process scenarios, business processes steps, etc. of your solution, in the Solution Directory.

Integration
Use the Solution Monitoring role SAP_SV_SOLUTION_MONITORING_DISP to display the Solution Directory and sessions in Solution Monitoring.

Adjustment
Adjust Roles and Profiles

Solution Monitoring Roles
Tasks
Authorizations specified for the Solution Monitoring in the SAP Solution Manager:

for the Solution Monitorin sessions, classified by the areas Operations Setup and Operations

general individual role to display all sessions

Display all Sessions SAP_SV_SOLUTION_MANAGER_DISP
general individual role to edit all sessions

Edit all Sessions SAP_SV_SOLUTION_MANAGER

Activities
Authorizations are assigned to the roles. Specify user access to the session. There are the following authorizations:

A The user with the role has full authorization for the transaction or session.
D The user with the role can call the transaction or session in display mode.
N The user with the role has no authorization for the transaction or session.

Operations Setup session authorizations

Individual role Service Level Reporting System Monitoring Central Administration Business Process Monitoring
SAP_SETUP_DSWP A A A A
SAP_SETUP_DSWP_SLR A N N N
SAP_SETUP_DSWP_SM N A N N
SAP_SETUP_DSWP_CSA N N A N
SAP_SETUP_DSWP_BPM N N N A

Operations session authorizations

Individual role Early Watch Alert Service Level Reporting System Monitoring Central Administration Business Process Monitoring
SAP_OP_DSWP A A A A A
SAP_OP_DSWP_EWA A N N N N
SAP_OP_DSWP_SLR D A N N N
SAP_OP_DSWP_SM N N A (1) N N
SAP_OP_DSWP_CSA N N N A (1) N
SAP_OP_DSWP_BPM N N N N A

SAP_SV_SOLUTION_MANAGER_DISP session authorization

Individual role Early Watch Alert Service Level Reporting System Monitoring Central Administration Business Process Monitoring
SAP_SV_SOLUTION_ MANAGER_DISP D D D D D

SAP_SV_SOLUTION_MANAGER session authorization

Individual role Early Watch Alert Service Level Reporting System Monitoring Central Administration Business Process Monitoring
SAP_SV_SOLUTION_ MANAGER A A A A A

(1) – from Release 3.20 SP02
Cf.:

Overview of Roles and Profiles

SAP Solution Manager 3.2configuration guide

SAP note 625773

Notes on Tailoring
You can use and combine the individual Solution Monitoring roles individually, according to your requirements.

Special authorizations for specific checks in individual sessions, are described in the online documentation of the sessions:

See also:

Set-Up Central System Administration
Using business process monitoring
Integration
If you need authorization for specific areas in the SAP Solution Manager, in addition to the authorizations for Solution Monitoring, use the associated individual roles with the specific authorizations:

Change Request Management
Service Desk
Service Data Control Centre
Solution Directory
General Administration and Display Authorization
Technical name: SAP_SV_SOLUTION_MANAGER

Technical name: SAP_SV_SOLUTION_MANAGER_DISP

Tasks
Authorizations are assigned to the roles. Specify user access to the session. The following authorizations are available for your project:

A The user with the role has full authorization for the transaction or session.
D The user with the role can call the transaction or session in display mode.
N The user with the role has no authorization for the transaction or session.

Activities in <SAP_SV_SOLUTION_MANAGER>
The individual role SAP_SV_SOLUTION_MANAGER contains full authorization for the transactions:

● SOLUTION_MANAGER

● SOLMAN_DIRECTORY

● SDCCN (Service Data Control Centre)

The following table contains special authorization objects for this role.

SAP_SV_SOLUTION_MANAGER

Authorization Object Activity Meaning
Transaction: SOLUTION_MANAGER
D_MD_DATA A Contains authorization for the master data
D_SVAS_PRD A Contains authorization for Service Data
S_PROJECT D Authorization for SOLAR_PROJECT_ADMIN Display in Solution Landscape tab ® Project Scoping
D_SOLMAN A SAP Solution Manager transaction call
D_SOLMANBU A Controls the session restrictions (field: bundle ID)
D_SOL_VSBL A Solution restriction
D_SOLUTION A Controls the system restrictions.
● Customer Number

● System ID

● Installation number

D_SOLM_ACT A Activity restrictions in a session
D_SOL_VIEW A Restrictions to the areas Operations and Operations Setup
D_SOL_REP A Solution Reporting

AI_SOL_DIR A Controls maintenance authorizations in the Solution Directory
AI_CVSTD A Authorization to change standard elements (e.g. business partners)
AI_DIAGTRA A Solution Manager Diagnostics data transfer.
Transaction: SDCCN
S_SDCC A Controls data interface
S_SDCC_ADD A Authorization for /bdl/sdcc in Add-On namespace

Activities in <SAP_SV_SOLUTION_MANAGER_DISP>
The individual role SAP_SV_SOLUTION_MANAGER_DISP displays transactions:

● SOLUTION_MANAGER (SAP Solution Manager)

● SDCCN (Service Data Control Centre)

● SOLMAN_DIRECTORY (Solution Directory)

Authorizations for Monitoring Sessions
Technical name: SAP_OP_DSWP<_bundle ID>

Technical name: SAP_SETUP_DSWP<_bundle ID>

Tasks
The format of the functional individual Solution Monitoring roles depends on:

● the Operations or Operations Setup area

● the session type

●

Activities in <SAP_SETUP_DSWP> and <SAP_SETUP_OP>
Both individual roles have full authorization for the sessions in their areas.

If you only assign one of the roles to a user, the system only offers the user this area in the system interface.

They have display authorization for other transactions, according to the requirements of the session types:
SAP_OP_DSWP

■ SDCCN (Service Data Control Centre) for SAP EarlyWatch Alert and Service Level Reporting
■ SOLMAN_DIRECTORY (Solution Directory) for business process monitoring
Special authorization objects

Authorization Object Activity Meaning
D_SOL_VIEW 20 (Operations) Determines which area can be processed and displayed in the SAP Solution Manager.
D_SOLMANBU A (Bundle ID) Restricts processing by sessions.

SAP_SETUP_DSWP

■ SDCCN (Service Data Control Centre) for Service Level Reporting
■ SOLMAN DIRECTORY (Solution Directory) for business process monitoring
Special authorization objects

Authorization Object Activity Meaning
D_SOL_VIEW 10 (Operations Setup) Determines which area can be processed and displayed in the SAP Solution Manager.
D_SOLMANBU A Restricts processing by sessions.

Activities in the session type roles
●

Functional roles

Role Technical name Bundle ID Further explanation
Operations Setup
Service Level Reporting SAP_SETUP_DSWP_SLR EWA_CUST Additional display authorization for the transaction SDCCN (Service Data Control Centre)
System monitoring SAP_ SETUP _DSWP_SM SOL_MON Additional authorization to call the Solution Manager Diagnostics wizard
Central System Administration SAP_ SETUP_DSWP_CSA SOL_CSA Authorization object S_SAA_ADMI controls authorizations for customizing
checks.

Business process monitoring SAP_SETUP_DSWP_BPM BPM_JOBM
CP_BPM

CP_BPM_R

SOL_BPMO
Additional display authorization for the Solution Directory
Operations
SAP EarlyWatch Alert SAP_OP_DSWP_EWA EW_ALERT Additional full authorization for the transaction SDCCN (Service Data Control Centre)
Service Level Reporting SAP_OP_DSWP_SLR EW_CONS Additional display authorization for the transaction SDCCN (Service Data Control Centre)
Central system
administration
SAP_OP_DSWP_CSA SOL_CSA
System
monitoring
SAP_OP_DSWP_SM SOL_MON Additional authorization to call the Solution Manager Diagnostics wizard
Business process
monitoring
SAP_OP_DSWP_BPM BPM_JOBM
CP_BPM_R

SOL_BPMO
Additional display authorization for the Solution Directory
■
Adjustment
You can adjust the roles to your requirements.

If you also need authorization to display the Business Process MONITORING session, as well as the functional role for Service Level reporting in Operations SAP_OP_DSWP_SLR, to check the business processes for the Service Level report, you can:

...
i. copy the authorization object D_SOLMANBU into the role SAP_OP_DSWP_SLR and adjust it to your requirements (activity: 1; bundle ID: BPM_JOBM; CP_BPM_R; SOL_BPMO)
ii. give the user the role SAP_OP_DSWP_BPM and adjust the authorization object D_SOLMANBU to your requirements (activity 1).
Integration
You can combine the functional roles with other roles in the area:

● Service Desk

● Change Management

●

If you want to create a Service Desk message from a Business Process MONITORING session, you need the role for the user in a message system SAP_SOL_SERVRANS_CREATE, as well as the functional role for business process monitoring SAP_OP_DSWP_BPM.

The online documentation for the sessions describes the scenarios in more detail.

Solution Reporting Roles
Technical name: SAP_SOL_REP_ADMIN

Technical name: SAP_SOL_REP_DISP

Tasks
The individual roles administer and display Solution Reporting.

Activities in <SAP_SOL_REP_ADMIN>
This individual role performs administrative activities in Solution Reporting.

Activities in <SAP_SOL_REP_DISP>
This individual role displays in Solution Reporting.

Adjustment
Adjust Roles and Profiles

Service Desk Roles
Tasks
The authorization concept for the Service Desk contains roles for specified groups of persons who perform specified tasks.

Activities
Roles

Persons Role Meaning
Administrator SAP_SUPPDESK_ADMIN Configuration of the Service Desk. This role contains the authorizations for the roles:
SAP_SUPPDESK_PROCESS

SAP_SUPPDESK_DISPLAY

SAP_SUPPDESK_CREATE

Message
processor
SAP_SUPPDESK_PROCESS This role contains the authorizations for the message processing.
Display SAP_SUPPDESK_DISPLAY This role only displays messages.
Creator of support messages SAP_SUPPDESK_CREATE This role allows satellite system and SAP Solution Manager users to create messages.
All users who send messages to the central SAP Solution Manager System via RFC connection, need the authorization object S_RFC.

Cf.:

• Overview of Roles in Solution Manager 3.2

• SAP Solution Manager 3.2 configuration guide

• SAP note 625773 (Roles in Solution Manager)

• SAP note 803142 (Roles in Satellite Systems)

Group Functionality Roles
Technical name: SAP_SUPPCF_CREATE

Technical name: SAP_SUPPCF_PROCESS

Technical name: SAP_SUPPCF_ADMIN

Tasks
The roles allow you to assign group functionality authorization.

Activities in SAP_SUPPCF_CREATE
Authorization to create messages.

Activities in SAP_SUPPCF_PROCESS
Authorization to process messages.

Activities in SAP_SUPPCF_ADMIN
Authorization to administer (create and process) messages.

Adjustment
Adjust the Roles

Integration
The group functionality roles are "delta" roles of the Service Desk Roles

. To use this functionality

:
...
1. Assign the default Service Desk role and the analogous group functionality role, to the user, in the user administration (transaction SU01).
SAP_SUPPDESK_CREATE and

SAP_SUPPCF_CREATE
2. Deactivate the following authorization objects in the Service Desk roles, in the role maintenance (transaction PFCG):
○ B_USERSTAT
○ B_USERST_T
Service Data Control Center Roles and Profiles
Role <SAP_SDCCN_ALL> (SAP Solution Manager); Profile <S_SDCCN_ALL> (satellite system)

Role <SAP_SDCCN_DIS> (SAP Solution Manager); Profile <S_SDCCN_DIS> (satellite system)

Role <SAP_SDCCN_EXE> (SAP Solution Manager); Profile <S_SDCCN_EXE> (satellite system)

Tasks
Activities in <SAP_SDCCN_ALL>; <S_SDCCN_ALL>
You need this role/profile to manage the Service Data Control Center.

Activities in <SAP_SDCCN_DIS>; <S_SDCCN_DIS>
This role/profile displays the Service Data Control Center.

Activities in <SAP_SDCCN_EXE>; <S_SDCCN_EXE>
This role/profile performs everyday tasks in the Service Data Control Center.

Cf.:

• Overview of Roles in Solution Manager

• Overview of Roles and Profiles in the Satellite Systems

• SAP Solution Manager 3.2 configuration guide

• SAP note 625773 (Roles in Solution Manager)

• SAP note 803142 (Roles in Satellite Systems)

Roles for Solution Manager Diagnostics in SAP Solution Manager
Technical name: <SAP_SMDIAG_WIZARD>

Technical name: <SAP_SMDIAG_TEMPLATE>

Tasks
This functional individual role:

● passes data between SAP Solution Manager and Solution Manager Diagnostics, with the Solution Manager Diagnostics Wizard

● maintains Templates

Activities in <SAP_SMDIAG_WIZARD>
The specified individual role transfers data.

Activities in <SAP_SMDIAG_TEMPLATE>
The specified role maintains templates.

Adjustment
Adjust Roles and Profiles

Role for Service Connection
Technical name: <SAP_SERVICE_CONNECT>

Tasks
The specified role sets up service connections to SAP.

Adjustment
Adjust Roles and Profiles


The SAP Solution Manager offers a variety of services to manage production systems during
the operations phase. For example, the Self-Service procedures of the Service Level
Management framework and the SAP EarlyWatch Alert analyze the operational status of
mySAP.com solutions and trigger alerts and messages that reflect the state of the entire

solution. To help anticipate potential problems these Self-Services automatically trigger
recommendations for specific remote services and Self-Services in the SAP Solution
Manager.
The SAP Solution Manager will be the necessary platform for all related SAP Service and
Support issues. All customers who benefit from SAP Global Support offerings (for example,
TeamSAP Support Services, Solution Management Optimization and Solution Management
Review Services) will also benefit from the SAP Solution Manager. The main focus of
development in the SAP Solution Manager will be further enhancement in Business Process
Monitoring such as background job scheduling, and checks for data consistency, process
performance, and throughput

Best Practices for Solution Management
Best Practices for Solution Management are composed and developed by SAP using the
experience of thousands of customer installations and implementation projects. In general,
Best Practices are structured and delivered in different forms:

The SAP Solution Manager is available as technical add-on and is designed to run either on
mySAP Workplace 2.11 (with SAP Basis 4.6D), SAP R/3 4.6C or SAP Web Application
Server 6.10. The SAP Solution Manager will be shipped as one single add-on together with
the SAP Solution Architect for the new SAP Web AS 6.10 at the beginning of 2002.

What are the Benefits of the SAP Solution Manager?
November 8th, 2005

The SAP Solution Manager lowers the cost of ownership of the mySAP.com solution, optimizes system performance and ensures for smooth core business processes and extensive knowledge transfer to the customer through:

• System and Application Management / Monitoring
• Service Level Management / Reporting
• Software Change Management for the entire solution
• Bridging the gap between functional / application and system operations
• Safeguarding and Back office support (expertise on demand)
• Continuous technical improvement (saving costs)
• Optimal SAP Support with integrated Support Desk