1 4 5 6 7 8 29 Previous Next

SAP Solution Manager

428 Posts

With Solution Manager 7.1 SP12 Job Monitoring an integration of Job Monitoring with Job Documentation has been achieved. Currently only the Monitored Object created via job monitoring creates a Job Documentation with proper information or vice versa and there is not sync between them.


The following snapshots are used to demonstrate the  integration:


a) Launch Job Monitoring WorkCenter under solman_setup





b) Goto "Define Scope" Step, Step 4 and select the scenario.

define scope.jpg



c) Select scenario and navigate to Step 5.1

     Select "Add Jobs" and select from Managed system from the menu.

A popup opens, search for a job and select it.

add jjobs.jpg


d) Press on Add selected Job as Monitored Object. you can see in the image below that the Job Documentation ID field is empty.

no jobdoc.jpg


e) Press on Save. That will create a new Job Documentation. Internally it looks for an existing job doc with the same parameters as the job, if it exists and is not linked to any other Monitored object, it is assigned or else a new one is created.

jobdoc created.jpg


f) Click on the "Show Job Documentation" link to launch the newly created job document


Lauch Jobdoc.jpg


Hope you liked my blog. Thank you. Part 2 on this link, will cover how is it integrated form the Job Scheduling management Workcenter side.

Hello forum,


Today I see a mail from some "SAP Consultant" asking us why SAP Solution Manager Key don't work on SMSY...


Well, as indicated on the next SAP note, Solution Manager Key is no longed provided trough SMSY transaction, you have to do that using LMDB as indicated on note:


1888840 - How to generate installation keys in Solution Manager 7.1

You can see on the next pictures how to access to that LMDB functionality:


LMDB stat screen




To do that you don't need to finish the managed system setup, you can select any system on LMDB technical systems selection and then click on Generate Installation Key, then on the next screen only fill the fields with the correct information to generate the KEY.


I check SAP notes to see if there is any new update about that, and found the next one interesting:


811923 - SAP Solution Manager Key

"...The SAP Solution Manager Key is no longer required..."

I don't install SAP software but it's curious to see people for Solution Manager Key, and there is a note where SAP indicate that the key is not longer required :-O


Anyone have more information about that last SAP note ?


Best Regards,


As you all know removing a managed system from Solution Manager can be a tedious time consuming process. With SP11, SAP has provided a guided procedure for removing (decommissioning) a system from Solution Manager 7.1. The steps below show you how to access the guided procedure and high level preview of the steps provided.


SAP also added steps for decommissioning in the latest Solution Manager 7.1 SP11 Operations guide. You will need access to the SAP support Portal to access the document. Here is the link to the guide and a screen shot of the location:  https://websmp109.sap-ag.de/~sapidb/011000358700000631992012E.PDF




1. You need the following composite role to run guided procedures

     a. IT Operator  composite role = SAP_TASK_INBOX_ALL_COMP

2. Enter Transaction SOLMAN_WORKCENTER in SAPGUI

3. Select Technical administration Workcenter

  • Select Guided Procedure Management
  • Select the Managed System
  • Select the Guided Procedure browser drop down
  • Select either Start new window or Start Embedded



4. Select the Decommissioning Procedure and select Execute


5. Select Edit

6. Before continuing to the next step you must understand that by decommissioning the system you will lose data on the managed system. Keep in mind all of the steps may not be required.

7. Set the execution status to performed and select next to move on to step 2.


8. Step 2 – Application Clean-up has 2 automatic steps and a number of manual steps.

     a. Automatic activities are completed by selecting execute all

      • Remove Technical Monitoring Templates via SOLMAN_SETUP
      • Delete Session data, Reports, Early Watch Reports, DVM, Service Level Reporting with report “RDSMOPREDUCEDATA”

     b. Complete the manual activities by reading the Documentation for each step and the selecting Start Webdynpro to navigate to the location where the steps need to be completed.

     c. The manual activities are all about removing the scheduled jobs and monitoring that is configured in Solution manager.

     d. When all manual activities are complete set the Execution Status to Performed and select next to move on to the next step.


9. Step 3 – Cross Application Clean-Up

     a. This step has you delete the Extractors, RFC’s, Transport Routes, and uninstalling the Diagnostic agent from the managed system.

     b. This step and the following steps have all Manual Activities. Read the documentation and complete as needed.


10.  Step 4 - Planning Projects and Solutions Clean-up

     a. These manual activities are removing Solutions and deleting logical components from the LMDB and SMSY.


11.  Step 5 – Software Life Cycle Management Clean-up

     a. This step has you remove more product systems and system data from solution manager.


12.  Step 6 – Landscape Management Clean-up

     a. This step has you remove the remaining system data from LMDB and the SLD.


13.  The final step is just an overview displaying the status of the other steps.


14.  That is it, once complete all data on the managed system is completely removed from Solution Manager.

Hello all,


It's been some time since we have the KBA methodology at SAP. I like the idea of being able to release documents for you as quickly as you need them, but we don't get a lot of feedback about them.


I would like to know if you have any issues following a Maintenance Optimizer KBA, because I want to make them as good as I can.


So, don't be shy, and let me know if you have comments about any SV-SMG-MAI KBAs.


I am looking forward to hearing from you!

I was just remembering how I was struggled to understand LMDB in SM 7.1 SP1 in my own sandbox; Those days I don’t have any source for reference except the guide from SAP and the blog #sapadmin:: How to assign Product System in SOLMAN 7.1 & How LMDB, SLD, SMSY and Landscape Verification  work in SOLMAN7…



This blog is the asset for my entire team to know where to start in LMDB.  During that time it was big debate with Tom Cenens in the blog Solution Manager 7.1 Landscape Management Database - A motorcycle or a bike?   about easy usage of LMDB, Later SAP come forward and clarified the road map, need and necessity of LMDB Evolution of Landscape Data Management – What’s better with LMDB?



We might thought it was just a vision,accepted and moved on. but it was not true, that was tremendous effort put on these concept, As promised by Bjoern Goerke in 2012 Teched, LMDB gradually evolved and it was much more mature now.



I was recently asked to give training to some of the functional colleagues on solution manager basic concepts; it was amazing, LMDB now become more self-guided and they done the entire setup without much hurdle. It was automatically guided them to assign the missing technical systems, product systems and logical components.






It was made my job easy!  I was impressed and my entire team was satisfied. Two weeks before I had discussion with Tom, finally was decided to reopen the old poll and to collect the feedback again.



Before that, Thanks to Wolf Hengevoss  for his continuous effort to bring the product much simple and more powerful.



You can check out the recent changes of LMDB in sp10. Evolution of Landscape Data Management – Part II: What’s better with LMDB in SAP Solution Manager 7.1, SPS10?



Now time for you all, let’s evaluate LMDB in SM 7.1 SP10, and how do you all feel? Take few minutes and finish the Poll by June 30th 2014.  SAP Solution Manager 7.1 SP10 LMDB

I will be publishing this as a series of blogs with all the steps required to understand(basic concepts), configure or setup multiple SLAs in IT Service Management based upon Multi Level Categorization in Solution Manager 7.1 which we have recently implemented or configured for a customer.

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.

We can implement or configure multiple Service Level Agreements to satisfy different requirements from support perspective, for multiple customers or a single customer itself. This means we now have got flexibility of easily supporting different deadlines as per customer scenario based upon the variants of configuration possible in the new version of Solution Manager.


Service Level Agreements (SLA) in Solution Manager works upon two main concepts of:

  1. Service Profile and
  2. Response Profile


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

  1. Service Profile – This helps us to define the time period within which the support partner should provide the service. e.g. 24/7 support which means 24 hours each day of a week
  2. Response Profile –  This helps us to define within the time period what is the start date/time and what is the end date/time e.g. based upon criteria say priority what should be expected deadline for start and end


The two major parameters for SLA measurement offered by SAP Solution Manager are mentioned below which are part of Response Profile:

IRT - Initial Response Time

MPT - Maximum Processing Time


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.

Please note: Before proceeding on it further, it is assumed that the system is already configured with Incident Management and custom Transaction Type like ZMIN or YMIN is present in the system as per requirement. Please check the below links for setting up the same.



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.

Further, in our example, let us assume the below 2 different Service & Response criteria for our 2 different category of incidents

  • SAP Tickets – assuming 24/7 support
  • Non SAP Tickets – assuming 12/5 support


Next blog is published now and you can check herehttp://scn.sap.com/community/it-management/alm/solution-manager/blog/2014/06/02/how-to--configure-multiple-sla-based-upon-mlc-in-it-service-management--part2

Taking a cue from Daniyar Kulmanov on possibility of using BRF+ with ChaRM, I tried the automatic Change Manager determination from BRF+ framework. It worked ! and here is the procedure to achieve it;


The standard SUPPORT_TEAM function is copied to Z namespace to adopt the Elements. You can also create your own Z function from scratch if you are familiar with BRF+. I chose to copy the standard;






Right Click > Copy


Name of target application should be 'SOLMAN'



Write down the Function ID of this newly created function from Details tab;



You can see the Signatures inherited from the SUPPORT_TEAM in the copied function (Z_CHANGEMAN_FUNCTION). It contains all relevant elements for the Service Desk.




We will create a 'Change Manager' element which is relevant in our case. To do this follow the procedure shown in screenshots;


Click on Add New data Object and provide the details shown below;



Now add the Change Manager in the Result Data Object replacing the Support Team. You may get following error when you try to Save;



To overcome this error, remove the Change Manager from the Signature screen using Remove Data Object button.




Now you need to create an Application, Ruleset, Decision table as you would create it for Support Team Determination. Instead of Component and Support Team in Decision table, use Category and Change Manager dataset; To configure application follow the steps mentioned in 5. CONFIGURATION IN THE BUSINESS RULE FRAMEWORK PLUS in the following link http://wiki.scn.sap.com/wiki/display/SAPITSM/Support+Team+Determination+via+Business+Rule+Framework+plus





Now we create a Z action in Z(Y)MCR_ACTION action profile for calling this function; this new action is similar to SMIN_STD_FIND_PARTNER_FDT action delivered in SMIN_STD action profile of Service Desk.



In the Processing Parameters provide below information;\




PARTNER_FCT : Partner Function of Change Manager

FUNCTION_ID : is the one which we created in BRF+

APPLICATION_ID: 0050568E6E9A02DE82A4EC0838CD95E5 (alwas constant, refers to Appln SOLMAN  in BRF+


last step is to activate this action in Condition definitions. No need to provide any Start or Schedule condition for this action , just make it 'Green' in Conditions screen





That's all ! now depending on your decision table entries, whenever you select a category in change Request screen, Change Manager is determined automatically upon Saving.



Hello All,


Today I would like to talk about the Introscope Host Adapter (WilyHost application), an application which runs inside the SMDAgent to collect data from the managed systems. I already did a post showing how to check this application, but now I would like to provide some details about how this application works.


As I already mentioned, the Introscope Host Adapter is an application which runs inside the SMDagent, it is also known as SMDAgent agelet or WilyHost agent. The main goal of the WilyHost agent is to collect data from different configurable destinations and push them to the Introscope Enterprise Manager. The following picture provide a big picture of the architecture of the wilyhost agent.


All applications running inside the SMDAgent can be found win the Agent Administration UI. The WilyHost Agent can be found as shown in the below picture.

  1. Agent Administration UI
  2. Application Configuration
  3. com.sap.smd.agent.application.wilyhost

app_config.pngAll resources used by the WilyHost application can be found under the 'Application Resources' node:


N.B.: When using the application configuration take care when performing changes. Do not perform changes in the scope GLOBAL if you do not know exactly what you are doing. The changes in scope global affect ALL SMDAgents connected to the Solution Manager system.


In Solution Manager 7.10, the WilyHost Agent is configured during the activity 'Introscope Host Adapter' of the Managed System Configuration for the target system. The following picture shows the exact location:



When the activity Introscope Host Adapter is performed, the wilyhost agent application is configured to collect data from the managed system that will be monitored. The main files used by the agent are the following:

  • Files create/modified by setup:
    • SAPAgentConfig.xml
      • File created during the Wily host agent setup step. It contains the destinations configuration and the link to actions to be performed for each destination
    • IntroscopeSAPAgent.profile
      • File is created from the IntroscopeSapAgent.profile.template. The host and port of the Enterprise Manager are configured in this file.
  • Files used by application:
    • WilyHostAgentTemplate.xml
      • The is a global template file that defines all the possible actions possible for collecting all the Wily Host Agent data.
    • WilyHost.xsd
      • The is the XML schema file that defines the rules of validation for the WilyHostAgentTemplate.xml file. If you modify the action template it needs to conform to the schema.


N.B.: No manual configuration must be performed to the above files. The activity Introscope Host Adapter will configure the WilyHost application automatically.


The file SAPAgentConfig.xml holds the configuration of the Destinations and the Actions that will be used/performed to collect data from the managed system.


  • Destinations: The destinations will point out where the information will be collected. The destinations are configurable, for example a destination might be a Jco connection to the managed system or the location of a specific file.


For a typical double stack system you will have configurations generated for the following destinations:

    • ABAP instance
    • JAVA instance
    • SAPStartSrv
    • File (for GC)


The following picture shows an example of a Jco destination. As you can see, the Jco destination has the connection information to the managed system, client, user, password, system number and hostname of the application server.


  • Actions: The actions indicates to the WilyHost Agent what are the metrics to be collected from the managed system. For all destinations in the SAPAgentConfig.xml a pool of actions are configured. The actions point to an action templates that are defined in the WilyHostAgentTemplate.xml file.


The following picture shows an example of some actions defined in a SAPAgentConfig.xml.

action_example.pngA SAPAgentConfig.xml fully configured will look as follows:


The following picture describes how the destinations and actions work in the managed system. As you can see, the destinations are the location where the data will be collected and the actions are the collections of data.


The file IntroscopeSAPAgent.profile holds the connection configuration to the Introscope Enterprise Manager. This file will tell the WilyHost application what is the Enterprise Manager that the wilyhost application must connect. The activity Introscope Host Adapter in the Managed System Configuration uses the IntroscopeSapAgent.profile.template file and then creates the IntroscopeSapAgent.profile. The following picture shows an example of IntroscopeSapAgent.profile.



If you find out that there is some issue with the wilyhost application, for example: agent is not connected to the Enterprise Manager or managed system metrics are not being collected. Then the SMDAgent logs must be checked to find out what is the root cause of the issue. The wilyhost application may not work correctly due to distinct issues and the SMDAgent logs will show the root cause.


The SMDAgent logs can be downloaded using the Agent Administration UI:


The logs related to the wilyhost application are the following:


Logging informationLog File

SMD Agent System log file


SMD Agent Application log file. All of the interesting logging for the Wily Host Agent will be found here


Host Agent Information when trying to connect to the Enterprise Manager

RFC Connections/usr/sap/SMD/SMDA<xx>/SMDAgent/dev_jrfc.trc


1) How to check if the WilyHost agent is connected to the EM: Check the jmv_smdagent.log, this file shows the information about the connection between the wilyhost application and the Enterprise Manager. If the WilyHost application cannot connect to the EM the jvm_smdagent.log will show the root cause. The following picture shows an example of log entry for a successful connection:

jvm_smdagent.pngIt is also possible to check if the wily host application is connected to the EM directly in the Introscope Investigator. By default the wilyhost application connects to the EM using the process name = 'SAP HostAgent Process' and agent name 'SAP HostAgent <SMDAgent_instancename>'. The following picture shows the same agent of the above log entry connected to the EM.

investigator.png2) How to check if actions are being collected: Compare actions defined in the SAPAgentConfig.xml with information available in the Wily Investigator. You should see nodes in the investigator with the same prefix of the actions.


If you find out that some actions are not started, e.g. workload analysis is missing, nodes in the introscope investigator are not available. Then the SMDAgentApplication.log must be checked. Usually, the actions are started when the SMDAgent process is started. So, to check issues with the actions it is good to restart the SMDAgent. It can be done in the Agent Administration UI as follows:

reboot_agent.png3) Example ABAP Instance action cannot be started: You see that you have no ABAP data in Introscope or in workload. You download the SMD log files and you see that you have a JCO issue. The SMDAgentApplication.log shows that the user is locked:


Solution: The WilyHost application uses the SMDAGENT_<Solman_SID> to connect to the managed system. In this case, it is necessary to check the password of user SMDAGENT_<Solman_SID> and unlock the user. This can be performed in step Create Users of the Managed System Configuration for the affected system.


4) Example SAP GC action cannot be started: You see that you have no SAP GC instance data in Introscope or in workload. The SMD Agent logs shows the following errors:



Solution: The SAP GC is collected from file std_server* which is located in the managed system work folder. In this case, it is required to ensure that the path to the files is correct. It is possible to compare the file shown in the log error or in the action definition in the SAPAgentConfig.xml. If the path is wrong, check the paths provided in step Enter Landscape Parameters in the Managed System Configuration for the affected system.


I hope you enjoy this post.


You can leave questions below, I will try to answer them as soon as possible.


Thanks / Obrigado


Allam Drebes

Few months back we have decided to implement ChaRM with cCTS and I was looking eagerly for some blogs which talks about good and bad of it, but I was not able to find much. Then I thought I should write one when I have good understanding on this.


To start with we have followed the below how to guide of cCTS.


To understand the simple flow setup this is enough but if your landscape is complex then it’s difficult to manage with this little piece of info.


The landscape where we have started is an ECC dual track (Maintenance and Development) and singe track BI for both maintenance and development.

As its being a dual track customer wants us to setup enhanced retrofit as well. The systems in the landscape are as below:


Points to be noted during clustering:

As per the how to guide all similar role systems should be made as one cluster e.g. all DEV systems in one cluster and all test systems in one cluster. If we can take the above landscape as a use case there should be three DEV systems in one cluster.



The clustering is closely associated to logical component in a project, systems must be even in all the logical components of a project else clustering is not possible.


Not necessarily all systems have to be in cluster e.g. retrofit.


Problems in clustering:

1. If one system is down in your cluster we cannot move transports to any other systems in the same cluster. E.g. In the above landscape quality cluster is having three systems two of ECC and one of BW and the project QAS system is down for maintenance then we cannot move transports to QAS of Maintenance or BW.


So plan you clusters properly so that there will not be any dependencies.


2. As retrofit is involved we have added the post processing system in logical component so the logical component will have five systems but in clustering you still have only four clusters (CD1, CQ1, CPR1, CP1) in this case systems will not be able to identify the clusters.


To make this work define another logical component with only post processing system, as this logical component is not even this will not be considered during clustering.


3. In a project we have defined DEV, QAS, PPD, PRD in logical component and in cluster we have made only three cluster DEV as cluster one, QAS and PPD as cluster two and PRD as cluster three. In this case as preprod is also kind of a test system so we can club both systems into one cluster.


Real scenario: A new development is started in project A and was tested well in QAS now it is yet to be moved to PPD system. Later there is a change in plan and these changes are decided to be moved as part of project B, when you try to change the project assignment of this change document system give message that TR’s are not moved to all the systems in the cluster hence you cannot change the project assignment or decouple the TR’s from this change document till its moved to all the systems in the cluster.


Hence plan your clusters properly considering multiple use cases.


4. In ChaRM without cCTS if you have to stop the TR movement to next system we can delete the TR from the import queue before the import all job run. But in cCTS this is not possible even after deleting the TR and transport collection, changes will still move to next systems.


5. In cCTS ChaRM projects sometimes the TR will not move to the next system even after the import all job run. In these cases we have to check the log of transport collection which will give you the clue of what went wrong.


6. In some cases the transports will move to the next system but the TR will have a message “return code unknown” because of unknown return code it gets into the import queue again and again currently I didn’t find any way out for this.


Hope the above information will help in design your clusters well. 



SAP Solution Manager for both the LoB and IT


SAP's John Krakowski and his colleagues are  providing more information below about what to expect in the ASUG Pre-Conference session for "Expanding Your Borders with Solution Manager" which is being held June 2nd in Orlando, Florida.  Please read below:


NOW is the perfect time for every organization to register a representative to attend the ASUG Preconference Full-Day Seminar Expanding your Borders with SAP Solution Manager’.

On the SAP SAPPHIRE NOW | ASUG ANNUAL CONFERENCE home page, you will see the statement ‘Get the latest technological vision, actionable insights you need to drive profitability and growth, and influence future SAP offerings’, and on the ASUG PROGRAM home page is the statement ‘Every Experience Adds up to Your Success’.

These two statements are in perfect alignment with the tremendous SAP Solution Manager benefits and features that can be realized by all organizations and both their Lines of Business and IT.

More than ever, the market never stands still and neither can SAP and SAP Solution Manager. Year over year, SAP Solution Manager pre-conference seminars have proven to be among the most successful, valuable, and important topics for the ASUG Community. This year’s focus is to demystify, simplify, and discover new ways to approach your SAP Solution Manager adoption for lasting benefits to drive maximum value from your SAP Solution environment. SAP Solution Manager combines tools, content, and direct access to SAP to manage everything from deployment to solution monitoring and improvement. Based on an SAP support contract, the solution can help you optimize core business processes, your IT infrastructure, and innovate with two value releases per year.

This preconference seminar will help you refresh your SAP Solution Manager information to address the painstaking and time consuming efforts and potentially high risks to adopt innovations in your existing SAP solution, such as test phase duration, projected costs, and business user impact. The session is designed to provide maximum opportunity for you to hear from, interact, and see demos with several key and diverse ASUG members (Customer, Partner, and SAP) knowledgeable about SAP Solution Manager and obtain insight into their playbooks. You will be presented with multi-faceted topics, such as best practices for deploying innovation reliability and quickly while minimizing business risk, to increase your understanding and make SAP Solution Manager even more relevant to your organization. You will walk away with specific ways to expand your use of SAP Solution Manager, maximizing the value of your support engagement with SAP and your partners. You'll be able to streamline internal processes, minimize manual effort, reduce operational costs, and introduce new business functionality with greater ease.


Leveraging SAP Solution Manager more fully has been shown to increase reliability and help lower total cost of ownership:


  • Discover how integrated SAP IT Portfolio and Project Management, provides visibility and collaboration between project and change management teams.
  • Learn the best landscape for Two Value Releases per Year.
  • Hear about the recommended major and minor release approach.
  • Understand how to adjust and test only what matters when managing innovation projects with SAP Solution Manager’s Scope and Effort Analyzer.
  • Gain steps to improve Custom Code Management.
  • Review Solution Documentation best practices and whitepapers.


Also, walk away with information about:


  • SAP’s Control Center Approach for proactive support and to accelerate innovation.
  • Deployment and Run SAP like a Factory best practices for SAP HANA.
  • IT Service Management best practice processes with SAP Solution Manager.
  • What the new central CTS means for Change Control Management.
  • Learn information about SAP Solution Manager’s strategic direction and release plans, with details of the new release’s exciting innovations such as a new approach for collaborative process design.


Don’t miss out learning about the new features and breaking announcements!

Register Today


Photo by SAP

Could this be you, asking John questions during this ASUG pre-con?

I also  encourage you to read what former SCN Member of the Month Thomas Dulaney wrote in his blog last year about the ASUG Solution Manager pre-conference session at Review: ASUG Preconference ==> SAP Solution Manager 7.1 – Additional Value Creation Through Technological Innovations


He says:

"I have absolutely *nothing* negative to say about the ASUG preconference sessions. The three presenters were incredibly well informed. The presentations were incredibly well prepared. It was clear that this preconference session was designed and developed as a smoothly flowing whole session and not a collection of one hour sessions designed for a different audience. "


Register Today

Being involved with the new Logical Components as a developer from quite sometime, I have realized there are some common issues that are faced by consultants while working with them in the new Logical Components in LMDB.

Question: I do not know how to work with the new Logical Components

Resolution: Look at the following link


Question : I don't see the Logical Components created in customer namespace in LMDB however it exists in SMSY?


  • Logical Components exist in SMSY
  • During Managed system configuration it is possible to define Logical Components
  • In LMDB, the only option available is to create new logical component to assign to a Technical System.
  • If you attempt to edit the logical component in SMSY, the following message is displayed:
  • The selected logical component is not yet available in the logical component editor.
    Therefore, you can still edit this logical component with transaction SMSY.

Issue : You don't see any Logical Components in LMDB transaction apart from the one's shipped by SAP as templates.

Resolution: Goto solman_setup, click on System preparation-> Goto step 6-> Click on the link "Migrate SMSY data to LMDB"-> In the UI sub-step that opens execute "Migrate Logical Component Data"


Question: I see a sync issue between LMDB and SMSY, the product instance/systems selected in LMDB and saved are not the one's  shown in SMSY or the system and roles are not matching.

Issue: bug in the code

Resolution: Implement all then relevant notes in the application area SV-SMG-LDB-LC, delete and recreate the Logical Component, you can change the specific product instance or delete the technical system and add it again. Press save in between.

Question: I do not know to which Product instance of the Technical system, the Logical component should be assigned

Resolution: It has been discussed in the blog


Question: I do not see a Logical Component for a certain Product / Product Version

Resolution: With 7.1 SP10, SAP has stopped shipped new Template Logical Component, Create you own logical components in the customer namespace and assign the required product version->product instance

Question: The Logical Component systems are yellow even though the systems have been upgraded.

Resolution: This means that the Logical component assignment to the Technical system is not updated. Check out the Technical system by clicking on the ExtSid of the Technical system, If the product instance assigned to the Logical component is not upgrade, select "Maintain", click on search and as proposal is selected by default, select the checkbox of the correct product instance. Close the pop-up and save.

If the Technical system is still yellow, open the software node of the Technical System and check the assignment of the Logical component, it is correct or not.

How to Edit the Categorization Schema to include Newly Created Custom Transaction types


SAP strongly suggests to copy the default Transaction Types for ITSM and ChaRM to the Customer namespace (Z* or Y*) before customization begins.  These steps are done via the Guided Procedure for ChaRM, as is the creation of the Categorization Schema for the S* Ttypes.


In order to enable categorization for Customer namespace Incidents, Requests for Change, and the Change Documents, you must copy the SAP_SOLUTION_MANAGER_TEMPLATE Cat schema to the Customer Z Namespace and include the Z* Transaction Types.


Pre Steps:

  1. From Solution Manager: Launch sm_crm




  2.  To Enable Table Keys in Drop Down:


  • In WebUI Click Personalize




  •   Check box for Enable 'Show Keys in Drop Down' -> Save






From WebUI:


  1. Choose -> Service Operations -> Categorization Schemas






  •     Copy this Schema




3.  Change the Schema ID and Name to Z Namespace and Save




4.  Put the Schema in Edit Mode:




(If editing a currently active version of a schema, First
Create a New Version of the Schema




5.  From General Data Assignment  Block  Choose Drop Down Status on Right, choose Draft.

** Be sure to edit the Valid From Date , Default value is 24 hours in the future **






6.  From Application Area Table on Right, Choose New




  • Create an Entry for Service Order -> Transaction type/Catalog Category ->

  • Make Entries for ZMCR, ZMAD, ZMGC, ZMHF, ZMMJ (Choose (D)


  • (* When editing/creating a copy of the Standard Schema, Remove all Standard S*ttype entries)






7.  From General Assignment Block:


  • Choose Valid-From Date and Time (default is 24 hours ahead)
  • Put Schema in Released Mode ->





8.  Save the Schema





Go Back to Search for Categorization Schemas:


Once Valid To Date is reached, the Status of schema will change to Active



Exit UI


To Test, Create a New Change Doc and verify the Categories are enabled:

Dear reader


As service delivery manager in charge of promoting Solution Manager the first thing that I found it interesting is : a customer within SAP Enterprise Support and SAP MaxAttention we have no addittional license fees to pay.

Interesting link: https://websmp109.sap-ag.de/~sapidb/011000358700000033422011E/__start.htm


Since we implemented the automated registration of incidents in our sevice management tool thanks to SAP Solution Manager.The next steps is to implement CHARM.Still it is not easy to convince new customers.What are your arguments to convince your customers to go onboard with SAP Solution Manager?


Thanks for sharing.


Kind regards,


There is a common question during Implementation projects that the customer and project team always ask - Why ARIS & Solman and why not just one of them.


This blog aims to clearly provide a distinction between the two.


ARIS is an Enterprise Level Business Process Modeling tool. The Business Strategy of the Organization gives birth to Business Processes across the different Organizational Unit. These are drafted in the ARIS modeling tool as a 7 level structure.

What is distinctly different in ARIS is that it does not matter if the Process broken upto the Process step or activity or task is running on SAP or any other system. ARIS just aims to map all the processes that runs in the Enterprise.


The IT Strategy leads to a "Project" - an implementation, upgrade or other kind of project. If this project is an SAP Project, then we could use Solution Manager in addition to ARIS.

What Solution Manager does is to import the Business Process from ARIS to a 3 level structure and "translate" these processes into the "SAP Objects world", namely the Transactions, IMG Objects, Dev. objects, etc.

Basically Solman in that sense is merely a "Translator". Business Process translated to the equivalent SAP Object.

The Business processe now gets a Transaction, Program, Job or other SAP objects assigned against it, the IMG documentation, other project documentation gets added etc. thereby completing the translation to an SAP world.



Business Strategy -> ARIS

IT Strategy -> SAP Project -> Solution Manager


The key point is - tomorrow if the Business process that is in ARIS need to run on a mobile device or a third party system replacing SAP etc, these processes should still be available on ARIS. The SAP translated objects just gets replaced with the new system that is being implemented.


Now, what are the synchronization directions?


ARIS -> Solution Manager


From ARIS all the Business processes that are "In Scope" for the Solution Manager "Project" should be synchronized from ARIS to Solman

Ideally, for the Business Processes the synchronization should always be one sided. From ARIS to Solman. This is because of where we started this article from - the processes at the Enterprise level is irrespective of whether they run in SAP or non-SAP. The processes should first be defined in ARIS and if they are running in the SAP systems then they are translated into the SAP object world in Solman!!!


Solution Manager -> ARIS

Any SAP artefacts that are created during the "Project" have to be synchronized from Solution Manager to ARIS.

We start with the "Project" itself.


First synchronize the Solman project into ARIS, copy the processes into this project and then start your synchronization to Solman.


Next will be the "Document types" and related "Status values". These have to be defined in Solman project and then imported into ARIS and reused from the Process Library against the processes.

Also the "Systems" which are created in the System Landscape need to be synchronized into ARIS. Note here that the Systems (SAP & non SAP legacy systems) are added to the LMDB of Solman thereby completing the Technical landscape documentation and then grouped into logical components are assigned to the Project. This is now reverse synchronized to ARIS.


You could also create "End User Roles" in Solman and synchronize back to ARIS.


In summary any SAP objects that need to be depicted in the process flow on ARIS has to be created in Solman and send back to ARIS.


Hope now that this article provides clarity on whether ARIS and Solman need to co-exist. Once again - Yes, they should!!!

This is part 2 of my notes from today's Admin 2014 Solution Manager Jump Start with SAP's John Krakowski


Part 1 is here SAP Insider Admin 2014 Solution Manager Jump Start - Part 1 - Key SAP Notes


SAP Mobile Solution Manager apps: You can learn about these at http://help.sap.com/solutionmanager71 then select http://help.sap.com/sm-mobileapps

  • End user experience mobile apps
  • Performance and availability
  • Keep finger on pulse of remote locations
  • It is a web dynpro? Yes
  • Does it use Gateway? Yes, that is out of the boxs


SP10 has dashboard apps


Business Process Monitoring which is a “sister application” has over 300 indicators


Solution Manager has over 10K productive installations with 300 go lives every month


It is ITIL verified and the first one to have 15 processes verified


Figure 1: Source: SAP


Figure 1 shows the ICC which is looking at projects timelines


OCC helps IT administrators what is going on in business


MCC is premium engagement – Max Attention – direct access to Mission Control Center in Newtown Square.  If you have requirements and see SAP standard functionality not met SAP looks at it.  If can’t be done, what is planned.  Goal is to reduce custom code and to help customers reduce custom code.


Figure 2: Source: SAP


John said “not one tool that does it all like SolMan” (Figure 2)


Wherever you start – have assurance that integration is guaranteed


How well can tools support the latest products available to you from SAP?


Are existing tools enabled to support HANA?  Solution manager today can run and operate your HANA project


SolMan is keeping in step with latest products


Figure 3: Source: SAP


John wants everyone attending the Jump Start to publish a quote similar to the one in Figure 3.


He suggested focusing on a particular pain point


Take away from him was when you have a key issue/challenge – include Solution Manager as part of the conversation


Two Value Releases


Figure 4: Source: SAP


Nervous about custom mods and nervous when doing custom mods and hundreds of transports


Testing effort is huge and doing soup to nuts testing


Downtime windows are shrinking


White paper released (SMP logon req'd) this talks about how customers can accelerate and improve major releases and projects through business suite. 


This 70+ page white paper should be used as a baseline to compare against you are managing areas and see how you align with what SAP recommends to customers.  Something to compare against as opposed to calling in SAP or whoever you bring in


Core components


Figure 5: Source: SAP


Figure 5 shows the costs of managing changes based on some assumptions


Figure 6: Source: SAP


Regression testing, downgrades – if this is in DNA, SAP is offering tools to work a synchronized strategy


You define windows for a major releases and minor releases


Looking to build a schedule to align projects to.  Today many are using spreadsheets / project is part of it


What are the tools to help you align?



Figure 7: Source: SAP


If doing SP’s then apply a technical enhancement package if available.  This is a best practice.


How can from an IT point of view always consider applying the available enhancement packages to your system


SAP wants this to be a starting point to reduce your custom modifications


Figure 8: Source: SAP


Why? In terms of performance tuning, latest code line, especially related to HANA


SAP is developing a new code line for HANA


If have a HANA based system there is a separate SP for HANA based systems


Efficiencies are realized taking advantage of enhancement packages


To be continued...


Filter Blog

By author:
By date:
By tag: