1 4 5 6 7 8 26 Previous Next

SAP Solution Manager

381 Posts

Business Process Analytics in SAP Solution Manager went mobile. Since 28.11.2013 the new app "SAP Business Process Analytics" is available for download in Apple's App Store (see https://itunes.apple.com/de/app/sap-business-process-analytics/id765620530?mt=8). The app itself is only designed for iPad and requires iOS 6.0 or higher. It comes free of charge and provides some demo mode so that you can get an idea how the app works even if you are not connected to any SAP Solution Manager system yet.If you want to see your own Business Process Analytics data on the iPad then you require SAP Solution Manager 7.1 with support package 10 or higher and SAP NetWeaver Gateway 2.0 or higher.


The mobile app does not support all features of the desktop application but it supports the benchmarking and trend analysis based on InfoCube data.


So you can either select key figures or stored variants (as they exist within the desktop application).


Key figure and variant.png

You can then use the benchmarking or trend analysis features and drill-down to certain characteristics.


Drill down.png

If you then see something exceptional that you want to share with colleagues, you can annotate and send the finding via email.


Mark and send.png

As data is cached locally on the iPad you can even use the data offline and analyze your key figures, although you are not connected to the corporate network.


A short PDF on how to get the App running can be found at (login required) https://service.sap.com/bpimp > Media Library > Technical Information > Setup Guide - Analytics Mobile App.pdf.

A detailed Administration Guide can be found at (login required) https://service.sap.com/instguides > SAP Components  > SAP Mobile Applications > SAP Solution Manager > Administrator's Guide SAP Business Process Analytics.pdf


Further reading


Frequently Asked Questions about Business Process Monitoring and Business Process Analytics are answered under http://wiki.sdn.sap.com/wiki/display/SM/FAQ+Business+Process+Monitoring and

http://wiki.sdn.sap.com/wiki/display/SM/FAQ+Business+Process+Analytics respectively.


The following blogs (in chronological order) provide further details about Business Process Analytics and Business Process Monitoring functionalities within the SAP Solution Manager.

I was fortunate that this year I got some time to attend most of the solution manager sessions in SAP TechEd Bangalore, SAP is keep investing in solution manager, as you all know that Charm is well matured now. And Test management another important and equally growing well at customer side.


Through this blog I would like to share what are the future innovations are in track and major highlights as part of solution manager. These information I received from multiple sessions I visited and listened via TechEd Live and of-course all the slides as part of the SAP TechEd disclaimer policy.



Future Directions of Solution Manager Innovations



It is very clear that, SAP no longer going to be core ERP application company, there are lots of acquisitions, latest trends made the point very clear that SAP moving beyond core application company, proving cloud, in-memory, mobile solutions. This was well and most genuinely represented in Key note by Vishal. Since from the key note I was just keen to know that, How our solution manager would be going to support the IT environment which growing limitless in cloud/Mobile area? How solution manager going to cope with all the latest innovation trends on SAP?  But SAP has a clear road map and plan for future innovations at solution manager.  It clearly depicts that solution manager 7.1 is the only E2E integrated platform from SAP to drive the innovations, ALM and boosting operations quality at lower costs.


Solution Manager initially focus on optimize the IT processes. IT is moving forward as the key contributor for run business.  Hence solution manger future innovations are planned in such a way that to optimize both IT and Business strategy.






Highlight I - PPM integration



This is the one of the planned innovation, now it is live with SP10, with lots of expectations customers are eye on this new feature. Earlier I was in the view that this would help only on project management activities like running the project on time, estimation of efforts, resource management. But found this integration is much beyond the project management, It even help out to reduce the regression test cycles by synchronization of projects.  The details can be found here.





Highlight II - Central CTS+



This is the most awaited feature, since 2010 SAP delivered the vision of CCTS+ as one of the most powerful change and transport management feature. It is now launched and live with SP10, Central CTS+ is perfect fit for solution manager to support the latest innovations on cloud, mobile areas. It is because of CCTS+, Charm become more flexible on managing multiple tracks, support of downgrade protections, project synchronization.




Other information which I found interesting was, Traditional Solution manager CTS+ and TMS supports the HANA artifacts as similar to the JAVA SDAs. We can get some more information regarding this on sap note Note 1731044 - HANA content deployment EJB plugin for CTS+ (7.0x).





Highlight III - Auto Track Features on IT Infrastructure Management



As we all know that IT infrastructure management would be the real helper for running IT like a business. It has been said that now the IT infrastructure management would automatically detect the software installed without proper license in your IT landscape.  I was still very keen to check the demo on this live solution.





Highlight IV Innovations on Test Management



As Raquel already had already written well defined blog for SAP Ehp Test scope and effort analyzer and HP QTP integration ( Rajiv from SAP has the demo for BPCA and HP QC integration, he is from SAP India, easy to approach for more details ). Another interesting things highlighted on the most of the session was the enhanced feature of test option1 with the new CBTA and registration of other certified third party tools with solution manager, one of them we discussed about worksoft integration with solution manager.




Highlight V - Unified Infrastructure between E2E Monitoring/Alerting Infrastructure and BPMon



If you closely notice the Vishal's keynote, we can sense that how much sap is giving importance for the user experience. SAP Fiori is one of the major leading solution for focusing user experience at the high. SAP Screen Personas the other interesting one. SAP is also looking forward to enhance user experience in all the products, User experience is not only the customer experience, it is end to end user experience. It covers all the key users too. Using this as key, SAP solution manager 7.1 has already well defined UI. Now its going to be more enhanced and optimized way. Future solman 7.1 release has plan for unified infrastructure UI for configuration of different functionality. Since new MAI already become benchmark for better monitoring, our BPMon also soon going to be MAI based.




Since I was interested in custom code management, explored the innovations on CDMC/ CCLM area. I found that, there going to be new BI structure for reporting.


Other than that, there are new guided procedure available for HANA implementations and HANA daily basis checks, there was the plan for new regression testing tool START. We also got information on how SAP Test management supports Mobile solutions and cloud infrastructure.





It was very pleasant to meet most of the SAP solution manager folks like  Prakhar, Umesh, Rajiv, Sonal by person and shared the view on future track of solution manager, Over all feedback was good and we are expecting much more in future releases.

In my blog about BPCA improvements with SAP Solution Manager SP10, where I described the SAP Teched Amsterdam 2013 session ITM264 - Change Impact Analysis of SAP Upgrades using BPCA, Vivek Hegde asked in his comment about the integration with SAP Quality Center by HP. I have not worked with it yet, but I know there is some information available, so I decided to write this short blog showing where to find this info in the SAP Service Marketplace.

This integration was briefly mentioned in another SAP TechEd 2013 session: ITM117 - Test Management Overview: What’s New with SAP Solution Manager 7.1 SP05 and beyond.


Go to SAP Support->Ramp-up knowledge transfer. Select SAP Solution Manager 7.1 and Test Management. In Test option 2 there is a document about the integration.





As I don't have SAP QC by HP in any customer at the moment to show it working, I can just show some slides of this document for those who can't access the link. I will not blog a copy of the whole document, of course.

There are some pre-requisites for this integration.

In the SAP Solution Manager side:

1. You need SAP Solution Manager 7.1 SP05 or higher

2. Your managed systems must be connected and have the latest ST-PI

3. You need to configure SAP QC by HP adapter

4. Business Blueprint must be synchronized with SAP QC by HP

In the SAP QC by HP side:

1. ALM 11.0 or higher

2. EI 2.7

3. Requirements coming from SAP Solution Manager mapped to test cases in ALM

Slides from the SAP document:



Once the preparation is done, you can:

1. Trigger BPCA from SAP QC by HP

2. Do Impact analysis based on SAP QC by HP

3. Create Test Set in SAP QC by HP from BPCA

4. Perform Test Scope Optimization based on SAP QC by HP.

5. Create Test Set in SAP QC by HP with BPCA-TSO (Test Scope Optimization)

6. Extend existing Test Set in SAP QC by HP

I hope Vivek can share with us his experience if he makes this integration .



I would like to share how to fix missing/blank FQDN hostname and IP address for a Host in LMDB.


Ususally this value is automatically returned by Outside Discovery process, however in some cases these values are blank like below and we also encounter warnings in Managed System wizard -> Check Configuration as "No FQDN found in Host"





Now for Solution Manager 7.1 (SP04 and higher) please follow below steps to set the FQDN and IP address  -


Step 1- Open Agent Administration UI and goto tab Application Configuration as shown in below screen




Step 2 - Select the DCC agelet -com.sap.smd.agent.application.e2edcc in left pane under Agent applications list and choose the correct SMD agent in Scope drop down list for the host.

Then select "Edit" and click on "Add Property" as shown in below screen.

Note - It is very important to select correct agent for the host in "Scope" in below screen.




Step 3 - Enter the new Prperty Name "job.physicalhost.fqdn" and Property Value for FQDN usually "<hostname>.domain" as shown below and click OK.




The newly added value is now shown in Custom Value as shown below


Repeat this step for Property Name "job.physicalhost.ip" and Property value "IP address" of the host.


Step 4 - Then click SAVE (besides the Edit button near Scope) to save the changes.




Above FQDN and IP address values are also now saved in LMDB.


Then re-run the step Configuration Checks in Managed System wizard to complete the setup successfully.



Note -

Above steps vary according to Solution Manager 7.1 patch levels.

Please check below SAP Note for details and reference-

1626853 - SolutionManager7.1 - Outside Discovery FQDN Customization

Version : Solution Manager 7.1


SP level : SP10


Error step: solman_setup -> Basic configuration -> step:7 Maintain System in IBase -> Create IBase components for LMDB systems activities


During the SP10 post processing step, in Basic configuration step 7. Create IBase components for LMDB systems. I got the error An internal number range interval cannot be determined for category ALM_OBJ_7003 &  ALM_OBJ_7004. So i have check the  1741109 - ITSM 7.1 - Generation of IBase Components is not working . But this note release for SP08 and not able to fix the issue.


So i have check the SP08 system and compare the step in ITSM configuration in solman_setup.So found the issue will happen in SP10 , due to Create Hierarchy for Material Products activities is missed in SP10 system. (This activity will be found also in step "Perform Standard Configuration  --> Perform Additional Configuration" of the scenario IT Service Management -> Incident, Problem and Request Management.)




Go to  AICRM_PRD_SETUP_MAT -> will get the below option







Now the category ALM_OBJ_7003 and  ALM_OBJ_7004 will created in the particular system.


Execute the Maintain number range for material

material_number range.png

Now check the note 1741109  - ITSM 7.1 - Generation of IBase Components is not working and go to "Define Number Ranges for the Product Type "Material" and click the Groups, able to see the ALM_OBJ_7003 &  ALM_OBJ_7004 also created in the product material type.






Once again SAP TechEd was for me a great place to learn. I remember my first SAP Teched, in 2010, where I was so excited with so many good sessions to attend that I could hardly stop for lunch or a coffee break. Not that this behavior changed after some years...in fact I think it’s worse now since I also have my own sessions (Expert Networking Sessions) to present, meetings and other networking activities. At that time, after working with SAP for more than 10 years and with SAP Solution Manager for 5 years, I could for the first time meet in person the people behind the Products and ask questions directly to the source. It was also in my first SAP Teched that SAP Solution Manager 7.1 was first presented. I remember that my first hands-on session was about the new ChaRM Web UI in SAP Solution Manager 7.1 with Tobias Hauk, and I saved screen shots to send to my colleagues and to show to my customers the great improvements coming with the new release. The new release, as I already described in one of my blogs, changed the way the customers look at Solution Manager, specially regarding ChaRM and Service Desk (now ITSM).


This year again at SAP Teched I could see and practice some great improvements released with a new Support Package of SAP Solution Manager 7.1, SP10 (in fact SP09 and 10 together, also known as Feature Pack 2).  Some of these improvements are already described in other blogs here in SCN, specially in the ChaRM area. I will describe here what I learned about the improvements on BPCA - Business Process Change Analyser in the hands-on session ITM264 – Change Impact Analysis of SAP Upgrades using BPCA. This is for sure a session not to be missed if you plan to run upgrades in the next months.

It was a pleasure for me to support Rajeev Gollapudi and Sonal Kumar in this session. It was the first time I was supporting a hands-on session (a SAP Mentor support). I could help them answering questions of the attendees during the Exercises.

In this session, Rajeev explained how the Business Process Change Analyzer (BPCA) can help with doing an impact analysis of SAP upgrades with the new test scope optimization options.

First, Rajeev talked about the strategy for business transformation in major releases, explaining how to have continuous improvement in minor releases and changes with two value releases per year.


Then, he explained the SAP strategy for Test Management, with Solution Manager acting as a central hub to manage all SAP changes and E2E Integration Testing. We had an overview of the products and capabilities integrated with SolMan 7.1, as we can see in the slide below:


Next, Rajeev introduced the Motivation and Approach of BPCA. A main motivation is that planned SAP solution updates occur frequently, not only with SAP Support Packages and Enhancement packages being released but also with Customer changes. It’s usually very difficult for customers to know which critical business processes will be affected with these changes.  With BPCA it’s possible to have a Change Impact Analysis, where the customer can identify business processes affected and have a Risk-based test recommendation. Then, there is a Test Planning where Test Cases are reviewed and missing Test cases are created, generating a new Test Plan. And last but not least,  there is the Test Execution step where Regression Tests (manual or automated) are performed.

Then, we saw briefly how BPCA works, as shown in the slide below. I will focus on the improvements coming with SP10, so for more information about BPCA, please check http://wiki.scn.sap.com/wiki/pages/viewpage.action?pageId=221290030



As a preparation, you need first to have your business processes documented (your Business Process Hierarchy) in a Business Blueprint. You need to create a TBOM for every relevant process step. Transactions and Test cases need to be assigned to the relevant process steps.

The business user or the tester can manually run the transactions to generate TBOMs (dynamic TBOMs) or run a program that creates static TBOMs. Dynamic TBOMs are recommended for better accuracy. It’s also possible to create TBOMs using Test Automation Framework using SAP and 3rd party test automation tools, or using SAP TAO 2.0 SP04.

One of the improvements of SP10 is the possibility to generate Semi-Dynamic TBOMs.


According to Rajeev, semi-dynamic TBOMs can be created automatically. A background job can be triggered where a source code scan is performed on managed system and unused objects are filtered out (based on Usage and Procedure Logging function of your system – UPL data). Similar to the generation of a static TBOM, the system analyzes the environment to determine which objects are in the executable entity. Picture below is from the session:



Since last year we are waiting for the UPL function to be available for BPCA. I remember that SAP TechEd Vegas and Madrid attendees were excited when this function was mentioned as a planned one. 

Rajeev explained that:

  • UPL is a kernel based logging technology providing runtime usage information of ABAP procedure units like methods, function modules, subroutines and much more...
  • UPL complements the standard ST03N workload statistics of ABAP executables
  • UPL provides 100 % reliable usage analysis without measurable performance impact
  • UPL is available as of SAP Netweaver 7.01 SP10 with Kernel 720 Patch 94.
  • BPCA uses UPL to identify used ABAP procedure units and to create semi- dynamic TBOMs.

The next improvement was in the Test Scope Optimization for EhP Deployment

Standard BPCA change impact analysis shows that almost all business processes are impacted by EhP.  It provides 6% test effort reduction compared to total test effort.

BPCA with Test Scope Optimization, delivered with SolMan 7.1 SP01, gives a Smart ranking of Business Processes / Process Steps, with highest impact and lowest total test effort and consideration of process attributes to mitigate risk. You can identify your test scope and significantly reduce your test effort for regression tests.

In SP10, new functionalities were delivered.

  • New graphical summary screen showing the result summary of test scope optimization
  • Test Scope Recommendations based on the test scope optimization resulting in further optimization possibility
  • Improved performance of analysis run and test scope optimization to handle large change events.



During the exercises, we could:

1. Review a Business Blueprint and start background job for semi- dynamic TBOMs using UPL.


We first reviewed a project in SOLAR01 and SOLAR02, checked the test cases assigned to a process step and changed the System Role to Production. The assignment of the test cases (manual and automated test cases) would be used in the test scope optimization of BPCA.


  In the SAP Solution Manager Test Management Work Center, we selected Administration and then TBOM Utilities as shown below (the next pictures are from a SAP Solution Manager SP10 that I am currently working with):


A SAP GUI screen will open. We clicked Generation of Static and Semi-Dynamic TBOMs.


Then we saw the screen below, where we could select the Solution/Project for creating the TBOMs. In the UPL section we had to select the Production System Role.


2. Run Change Impact Analysis for EHP upgrade using Dynamic TBOMs

In this exercise, we could run an analysis for a ECC Support Package using Dynamic TBOMs, and use test scope optimization approaches to reduce the overall test scope. We used a SAP delivery transport request corresponding to a SAP Support Package 01 for SAP_APPL in ECC 6.0 EHP 6 for that.

The main screen is the Test Management Work Center->BP Change Analyser. In this application, we selected Transport Request as Impact Analysis type, the system and client where the transport is located, the number of the transport (could be more than one) and the Business Process Scope of the Impact Analysis (a project, a solution or both).

Example of a Change Impact Analysis screen in SP10 with type Transport Request and Project/Solution as scope.


The result is all the business processes impacted. Then for the result we run the “Optimize Test Scope”, which calls a Test Scope Determination UI.

We can see below an example of the results overview (next pictures from ITM264):


In the Test Optimization Ranking tab we can see the processes included in the scope for 100% test coverage and see the test coverage at each process step. 


We also could see ranked list of process steps and which test cases are included in the scope. In the Test Case Recommendations Tab we could observe that BPCA was recommending to create a new automated tests for a process step. From the same Test Scope Determination UI we can create the Test Plan.



3. Review semi-dynamic TBOMS created by background job

In this exercise, we could review the semi-dynamic TBOMs created using UPL.

When the job is finished, the log will show the process steps for which a TBOM was created. In SOLAR01, we go to a process step and select the TBOM tab in the Attributes 
Maintenance window. We can observe that a “semi- 
dynamic” TBOM was created by the background job for that node.


4. Run impact analysis against Semi-Dynamic TBOMs and compare results

In this exercise, we could run an analysis for a ECC Support Package based now on the new semi dynamic TBOMs, and use test scope optimization approaches to reduce the overall test scope. As in the 2nd exercise, we used a SAP delivery transport request for that.

We could see that the result was different from the exercise 2, which used Dynamic TBOMs, specially the number of objects in the support package impacting each process.

In the pictures below we can see the different results. Note that the graphs show missing tests for project/solution that were not shown in exercise 2, and the number of Impacted processes with Test Scope Optimization was lower. The Manual effort was much lower. The total test effort in hours and the number of Test cases were also much lower.




Future improvements

It’s planned to be delivered a new application called Scope and Effort Analyzer. This is also something customers are waiting very ansious. The first time I heard about it was during the Teched 2012. 

This new functionality is supposed to fulfill the following customer needs:

1. Better planning of efforts for EhP deployments

2. Identification of required developers for custom code and modifications adjustments

3. Blueprint and Test Scope identification

4. Test scope optimization and recommendations


When it's available, the new functionality will provide:

1. BOM of changed objects.

2. Identification of SAP objects used by customer.

3. Used and unused custom code and modifications.

4. Change Impact Analysis for custom code, modifications and business transactions.

5. Scope and effort estimation, optimized test scope.

After reading my previous blog, I hope now you have fair idea on what the PPM and ChaRM integration is all about. Now let's get bit technical and see the step by step procedures for integrating PPM with ChaRM in SP10.


One absolute important thing to know is; there are many actions, text procedures related to PPM integration have been updated in Change Request Management related standard Txn types in SP10. So if you are already using ChaRM (assuming you are using Z* txn types) then all these new actions and text procedures should be recreated in the Z* txn types. The integration is all about adopting the new content delivered in SP10 to our Z* txn types. If you are copnfiguring ChaRM freshly in SP10 then the integration becomes lots easier (however in real world there are many customers who are already using ChaRM in < SP10 ) .So let us assume, for this blogs sake, we are already using ChaRM and our Change Request Txn type is ZZCR.


Configuration Prerequisites


1. Partner Function SMCD0005 (PPM Resource)


Transaction DNO_CUST04 has been updated with new field PPM_RESOURCE_PFCT in SP10. New partner function SMCD0005 needs to be maintained against this field. Defaults settings need not be changed if you are planning to use SMCD0005 as PPM Partner. You may also maintain your custom partner in DNO_CUST04 but it is optional.




However the new Partner needs to be maintained in the Partner Function in Procedure screen to utilize this partner in Change Request.



2. Text Types adoption


Transaction DNO_CUST04 has the parameters PPM_TEXT_TYPE and PPM_DESCRIPTION_TYPE. Enter the text types. The default values are:


We can leave this untouched until and unless you want to use your own text types. So there is nothing to change here.




However we need to add these Text Types to our Z* Text Determination Procedure used in ZZCR (ZZCR0001). So make below entries in the following customization: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Capabilities (Optional) -> Change Request Management -> Transactions -> Text Management > Text Detn Procedure


text detn 001.png


3. PPF Actions Adoption


A new action SMCR_CREATE_PPM_TASK is updated in the action profile SMCR_ACTIONS. This needs to be adopted to ZMCR action profile. So let's see what is the action definition of this newly delivered action and what parameters needs to be adopted while recreating this action in ZMCR.






So we need to create a custom action ZZCR_CREATE_PPM_TASK in our ZZCR action profile and adopt the above settings to have this action ready.


4. SET_STA_TASK Action


The action SET_STA_TASK sets the task status. Ensure that this action is specified for each status value in the status schema of the request for change. This needs to be adopted to our ZMCR action profile using following path: SAP Solution Manager Implementation Guide -> SAP Solution Manager —> Capabilities (Optional) —> Change Request Management —> Change Request Management Framework —> Make Settings for Change Transaction Types. This action is responsible for mapping the status b/w PPM Task <> Change Request.




Integration Information


1. Define Project Type Mapping


This information determines the SAP Solution Manager projects you can assign to a Project Management project. You cannot assign a SAP Solution Manager project to a Project Management project whose type is not in this mapping.




2. Define Project Status Mapping


This information is used to synchronize Project Management project status values to an SAP Solution Manager project. The mapping can depend on the SAP Solution Manager project type or be independent of it. Maintain the project type if you use different status values in the project type templates; leave it empty if you use the same status values for some or all project types.If you do not maintain the mapping for a Project Management status value, or the SAP Solution Manager status value is not valid for an SAP Solution Manager project, the status of the SAP Solution Manager project remains unchanged.




3. Map Transaction Types onto Task Types


Choose which Project Management task types are mapped to which SAP Solution Manager transaction types. Then, for each mapping, maintain the task and transaction type, the creation and assignment mode, and the indicator to restrict time recording. If the indicator is set, only resources that are assigned to the transaction with partner function PPM Resource (SMCD0005) are allowed to record time.





4. Map Task Status onto Request for Change Status


Using this you map SAP Solution Manager status values of requests for change onto Project Management task status values. This updates the status of the Project Management task, depending on the status of the request for change.




This is it !. Now we can start using PPM Projects with ChaRM. I shall publish a new blog on how to work with PPM and CharM in realtime with use cases.




Now SAP TechEd Session is going on, There were lots of new announcement, product strategy, roadmap updates shared in SAP TechED LV and Amsterdam. Next most awaiting one would be our SAP TechEd Bangalore, There would be much more excitement things queuing. Some of the common things in Agenda but with more zeal as key note by Vishal ( which last year we missed), 6 min Demo Jam with geeks, also very special unique things like SCNis10 celebration, Sourav as special guest and much more. Apart from all fun, SAP teched is one of the best technical and educational conference, we were provided for lots of hands on training, lectures, Demo Pods and new Q/A speaker booths with hands on speakers. With my passion on ALM area, I drill down to always solution manager related sessions. This year also there are more than 100 sessions scheduled for ALM area.


As you all know that, Since from SM 7.1 released SAP done much investment on User experience, custom code, Charm, ITSM and last but not least Test Management, SM 7.1 SP8 and SM 7.1 SP10 both these releases has dedicated enhancement for Test Management and Charm.


Charm is getting well matured now, there are lots of customers are getting benefited, As we consultants knew that how the configuration itself get automated and make our life easy


Now SAP Test management is one of the eye focusing area in solution manager, there are customers hiring candidates who would be expert only on this module, we can write couple of blogs only about the importance of testing in SAP.


SAP solution manager serves best for the support of testing, starting from Ecatt ( earlier version where only SAP GUI is supported) till the latest automated testing tools like CBTA and the future expectation like Standard regression testing (START). Like this we can count on the enhancement done on the testing area by SAP based on the customer requirement.


You may be very new to SAP Test management with the basic questions like what is test case, test script, what are the test management tools available, what are the sap test management options, you may be with intermediate level looking for more guidance on actual hands on new CBTA tool, new Test automation framework  or you may be already had handson looking for more answers for third party integration, TDMS, Test management for mobile and HANA products, why SAP testing third party tools, what are the future roadmap on testing.


What ever you are, if you are interested in SAP Test management and wanted to know that where is SAP with context to the test management support for customers, I would suggest the below session would be a better fuel for your brain.


Important Demo Sessions



ITM945      SAP Test Option 1


This is one of the finest session and repeating again on Friday, this is the two hours demo session for SAP's new enhanced SAP Test Option 1 which gives the clear picture of Test Automation framework which includes the major tools like Ecatt, CBTA , QTP. This session might cover the latest registration of third party automated test creation tools via SUT. if you are the beginner in test management, This session would be suits for you, you can get the answered from your very basic questions like what is test case.



ITM949      SAP Test Acceleration and Optimization 3.0 for Regression Testing


This is two hours hands on session for tagged with beginners, SAP TAO 3.0 is recently released with much more enhancement for optimizing testing automation. Even if you were not worked before SAP TAO earlier version also, you can visit and get the very fresh essence of SAP TAO and its use cases.



ITM164      Test Automation using SAP Solution Manager


This is about the new component based test automation tool, I would be assisting this hands on, The exercises in this session would be very detailed, you can get step by step working scenario for CBTA associated with Test automation framework.



Testing for HANA and Mobile solutions


We are growing, our landscapes are flying cloud, HANA and Mobile are part of our landscape since 2010. What about testing options for these products. Will solution manager capable of managing and supporting our emerging technology changes and complexity in the landscape? The answer is perfectly yes. Solution manager 7.1 is designed in such a way, which can support your products on HANA, Mobile, Here are couple of sessions available for the update of test strategy on HANA and mobile. Don't miss this very informative one hour lectures


ITM119      Test Strategy for Mobile Applications

ITM118      Test Management for SAP Business Suite Powered by SAP HANA Migration Project



Enhancement showcases


SAP has fine road map for Test management, there are couple of session would be delivered to update the very prominent enhancement of the test management to the customers



ITM117      Test Management Overview – What’s New with SAP Solution Manager 7.1 Feature Pack 2


This basically give whole picture of Test management and customer usecase.



ITM218      EHP Scope and Effort Analysis – Only Adjust and Test What Matters


This session is the showcase of new scope and effort analysis feature and its business uses.



Q/A with speakers


Even after all these sessions you were not cleared there are couple of dedicated 30 min Q/A booths available with face to face discussion with the speakers.


SPK10520     Q&A: Test strategy for mobile applications with Sonal Kumar

SPK9661      Q&A: Past, Present, Future Of Test Management With SAP Solution Manager with me.


I assure if you attended any combination of the 2 to 3 sessions above all your major doubts on testing is clarified.  Hope I would get some of the most critical customer use cases updated. Plan your agenda now. Enjoy your most informative learning and sharing day at SAP TechEd!!  Looking forward to meet you all!

Demo Content


SAP Solution Manager 7.1 Landscape Management Database (LMDB) in SPS10, offers features, which improve landscape data management with by unification, simplification, automation, and functional enhancements. Three of these improvements are shown in a three parts demo of step 1 of

transaction SOLMAN_SETUP > Managed System Configuration:


For a description of these and the other improvements, see Evolution of Landscape Data Management – Part II: What’s better with LMDB in SAP Solution Manager 7.1, SPS10? For information on landscape data handling in general, see Landscape Descriptions.


Additonal Information




Looking forward to your feedback...

There are whole bunch of features in SP10 and I am sharing some of them available via managed system setup.


We have now automatic assignment of Diagnostic relevance flag



Therefore, upon clicking Set Automatically the Diagnostic-relevant is set automatically as shown below. Also, notice the logical component step is shifted to initial step of the wizard which makes more sense.



Another new feature is a check for managed system ST-PI and it highlights a warning that if we don’t keep the managed system ST-PI up to date like below


Also, in the step 7 i.e. Create User we can create them as a mass user creation process. In addition, for the roles we can now assign naming convention and user group easily.

I will share few more later.



Today i was trying to discover the root cause of a SMSY data migration in step 5.3 of System Preparation of Solman_setup, we start working with our solution manager around 4.0 release or less (i didn't know solman on that ages), that days my company colleges usually create managed system information manually in smsy, servers, data base host, product systems, etc... Then, when we star on the first setup of Solution Manager VAR scenario we use data providers as SLD, RFC and create the information from that data providers or from SAP marketplace license data.


After that the current situation is a mix of old manually data, old sap marketplace data, and new LMDB data fron SLD data sources in solution manager 7.1 that make us that situation:



Well, after that huge number of errors we have to start with a single system to investigate the cause of the problem, the first system is:


A72AMZ01  - 0020209397 A72 Netweaver 7.2 - No relevant product instance found for product SAP BI ACCELERATOR


>>> You can go Directly to the Trick without reading the initial problem <<<


Lest go to search that system in solution manager, remember that on solution manager 7.1 SMSY is "recommend" to not be used, so we search the system trough "Solution Manager Administrations", "Solution Manager Configuration" workcenters and LMDB but the system is not missing in each of that option, obviously not in LMDB because the system can be migrated on the before picture.



Well, beside SAP recommendations i try to search for the system in SMSY, but I get a nice surprise because we use "data separation" in solution manager. If you use Data separation you will be asked to select with customer data you are looking for, but as you can see on "migration problems" you don't know the customer from the affected system, so you can't find the system in SMSY as not as you select without customer assignment or public.




We have a liter sigh, because we can search the customer name with the installation number from the "smsy migration list", the installation number is "0020209397". So with that i try to search the lost system in "Solution Manager Administration" and "Landscape browser" 7.1 work centers without success.



That's coming really hard to search a first system of a list of more that 300 with migration problems , so after that situation i decide to try surfing trough debug to find a solution that allow me to see that system on SMSY, and discover the problem:


The Trick to disable "data separation" in SMSY with debuggin


Go to function module "SMSY_SHLP_BP_SPC_FOR_USER" that is used in search help when the system ask you to select one customer, navigate to line 78 and create a breakpoint.



The key is the internal table "shlp-selopt", after the breakpoint is set, go back to SMSY and trough debug tools change values from that internal table.


When the select customer screen appears you have to input ALL_CUSNRS in entry field. (if you don't do that, that trick don¡t work)





After to remove the "X" value from the low parameter in the internal table shlp-selopt you will be able to see all systems in SMSY.




Then, after that you can just open product system from the select object option inside SMSY


( You will have to repeat the debug edit any time you move in SMSY)



The customer is: 13416, so, now we can just select that customer on SMSY start and try to discover the problem with the migration of product system that have a "SAP BI ACCELERATOR 7.0" for that system, on the migration log from SMSY we can read something like that: "No relevant product instance found for product SAP BI ACCELERATOR", so lest go in SMSY in "Product Instance Selection".


( Yes, you can go to view V_AIINSNRS to discoer the customer number, but if I do that yo will not be able to see that trick working to use SMSY ;-) )



Humm, is that the problem ?


Lest go to try to solve that updating the flag. You are able to update that flag in SMSY without any problem in Solution Manager SP08.




Now lest go to check again the migration tool from solman_setup step 5. After the "Calculate Candidates" i see that it is not enough to select the relevant instance, it is necessary to assign a technical system. So, lets go to fix all errors after technical system assign type ( i get a lot of errors on the mapping of the SMSY technical system, like "Cannot map SMSY system type 'THIRDPARTY' to an LMDB system type" ). That part make me come back to SMSY technical system assignment more or less 5 times as i get the correct one.


When you solve all warnings in "SMSY", then you will be able to see that on "SMSY Migration Tool".




Final Words and lesson of my own experience to remember on future solman upgrades:


1.- If it's possible, try to do not upgrade the Solution Manager, a Flesh Installation will make you live easy.

2.- Never create system information manually.

3.- If any customer have wrong information in sap service marketplace, cal your customer to fix that before download it to solution manager.

4.- If you update AISUSER, V_AISAPCUSTNOS and V_AIINSNRS with all your customer information you will fill your Solution Manager of wrong Data.




I listen from some friends that on SP10 it's not possible to edit anymore system information on SMSY, so i can't test that in SP10. But, what will hapen when I upgrade my Solution Manager to SP10 ?


Who I can delete all that wrong system data from the solution manager if i can see it ?


Hope that post can be useful to someone with a similar situation.


Best regards,














This blog is complementary to the one recently published (see below) by our Canadian colleague François Michel, depicting the typical paths to adopt SAP Solution Manager 7.1: installation or upgrade. The paper described the direct and hidden costs of the two approaches, and the present blog aims to provide remarkable customer cases.

Since the general availability of this product version in August 2012, my team has directly supported more than 50 customers of all sizes on their journey to release 7.1.


I would like to describe here the 3 main different “categories” of customer we have identified and to illustrate them by some real-life cases.

Any resemblance to actual events, or organizations, is not a coincidence. It is deliberate !




The “upgrading is a piece-of-cake” category:


For the great majority of customers, the usage of SAP Solution Manager encompasses scenarios like Maintenance Management (MOPZ…), basic System Monitoring (Early Watch Alert reporting) and Solution Documentation (creation of business process hierarchies and storage of documentation in SOLAR projects) or Solution Implementation (usage of Roadmaps for example).

Those scenarios do not suffer from any impact during an upgrade if the upgrade roadmap is well respected. Furthermore, the upgrade scenario ensures that valuable historical data (documentation, EWA sessions etc.) remains available.


Image 1.jpg


Reference project:

Medium company turning into a multinational player in the Fragance and Flavor industry, with more than 3000 employees in 15 countries and € 638 Million turnover.

The upgrade project was achieved in a very short time (6 weeks), for 2 Solution Manager Instances. No impact was detected on the project documentation, test plans and all “historical data”. Only minor issue occurred on a Roadmap that became unmodifiable, because it relied on obsolete SAP content. A new Roadmap, based on an updated content, was created. Together with the technical upgrade, within those 6 weeks, a simple Incident Management process was put in place.




The “upgrading is a functional challenge” category:


Apart from the basic scenarios we mentioned above, two scenarios are widely adopted by the SAP Solution Manager customer base: Application Incident Management and Change Request Management.

For those customers, upgrading their system is usually the only option that makes sense, as they want to keep the history of all tickets created over the years of usage of Solution Manager 7.0/7.01. But unfortunately, the “old” tickets are retrieved and displayed in ABAP screen (or WorkCenters) whereas all the “new” tickets will be created and displayed in the CRM Web UI.

The new UI also brings a lot of new features, so upgrading a Service Desk or ChaRM solution based on Solution Manager 7.0/7.01 means to perform adaptations to existing customizing, to implement new customizing and on top of that to train the users to new interface and to the updated processes.

This suddenly turns what is usually seen as a pure technical (IT) project into a functional one.


Image 4.jpg


Reference project:

Multinational company specialized in authentication solutions and services with approximately 7000 employees in 50 countries with a €12 Billion turnover.

The project overall duration was 6 months. The upgrade was performed on a system where Maintenance Management, Solution Implementation, Test Management, Incident Management, Change Request Management (no integration with transport tools) where used productively. And during the project, the Change Control was introduced (integration with transport tools) as well as Applications Operations (technical monitoring) and Business Process Operations (business process analytics and monitoring) but also Custom Code Management.

The IT Service Management (incidents…) and Change Management processes were fully redesigned, to be optimized and more integrated. Then, a full data migration was performed. All the “old” tickets have been recreated in the new CRM UI, with all the transaction history, logs and attachments. Even more: the open and released transport requests were reassigned to ChaRM cycles and ChaRM tickets.

At the opening of the system to the users, it would look like they had always used this tool. No loss of information, no complex transition period, but well integrated features to use and discover.




The “give me a new box” category:


Finally, we find a lot of customers that haven’t really leveraged the capabilities of Solution Manager but strongly consider reestablishing it in their organization. Those customers have instances that are not really well connected to the managed systems in their landscape. They use only compulsory features like MOPZ. Those instances are probably not updated regularly. The basic configuration is not complete. The master data (landscape definition, processes definition in particular) is missing or obsolete.

For those customers, an upgrade brings no significant value. The best way to establish a new, reliable foundation for a Solution Manager implementation: perform fresh installation of a clean Solution Manager landscape (at least 2 systems) with the latest possible release. It will be more efficient than performing a data cleansing on the platform.

Typically you will encounter this type of situation in organization that have decided to "reboot" their Solution Manager and made their choice to use it in replacement of one or multiple legacy tool. In most cases, to replace an outdated ticketing tool for Incidents, Service Requests or Change Requests. Or to setup a more robust monitoring (technical or business process oriented).


Image 5.jpg


Reference project:

Multinational company specialized in Oil and Gas industry, with close to 100000 employees worldwide and a €180 Billion turnover.

The project aimed to replace a corporate IT Service Management solution (for technical and functional support purposes and used by internals and implementation partners) used for nearly 10 years.

The customer decided to adopt Solution Manager IT Service Management scenario (incident, problem and request for change management). Due to strict Due to strict planning constraint, the new Solution was designed, implemented, tested and delivered in 5 months only. And a full data migration was performed to extract 100,000 tickets from the legacy ticketing tools and recreate them in Solution Manager.

The implementation of ticketing features in Solution manager is actually the first step of a more comprehensive adoption plan of Application Lifecycle Management: Solution Documentation, Test Management, Change Control Management are the next steps.




In a nutshell...


  • The “upgrade” scenario is always the first one to consider…
  • But the complexity of the upgrade highly depends on the scenarios of Solution Manager you use already !
  • If you perform a fresh installation, establish a rock-solid landscape with preferably 3 systems.
  • For the Service Desk or ChaRM happy users, consider using data migration strategies in order to keep your historical data safe in your new Solution Manager 7.1


And remember that SAP Solution Manager 7.01 is running out of maintenance on 31st of December 2013 !

The time to move to release 7.1 is now...

When, last year, we took on writing the first white book written on Solution Manager 7.1 in French (along and with the
support of the French Association of SAP users - USF), we had to provide some real data around the actual use of

Solution Manager in Europe. We interviewed 120+ major European SAP customers.


At that time, most of them had a plan for the migration or upgrade of the 7.1 release, and most of them were following

SAP official recommendations:


You should  definitely upgrade if

You may want to consider a new installation if

  • you are currently using SAP Solution Manager 
  • systems are connected and data transmitted (e.g. SAP EarlyWatch Alert)
  • business processes are documented inside SAP Solution Manager
  • any data exists which you want to preserve
  • your SAP Solution Manager system is outdated and not really being used
  • none of the information contained needs to be preserved
  • It’s a sandbox installation used for evaluation purposes
  • Main purpose is to generate keys and download Support Packages


In 2012, installation was preferred to upgrade scenario for 60% of those customers, not only because they had a

limited use of Solution Manager, but also because at that time, people would believe that installing New Solution

Manager would be easier than upgrading an existing one…and would avoid a drastic clean up of the existing system !


For the remaining 40%, the natural choice (upgrade) was guided by the need to leverage their investment and maintain

Service Desk and ChaRM history, Solution Documentation, Business Process Monitoring.


Today is November, 22nd, 2013 and one could say “why are we still talking about it! “. However, given the fairly high

attendance to our conference session delivered during Las Vegas Teched with our Partner oXya, (“Install from scratch

or upgrade”) we thought it would still be useful to present you some facts and figures about the real cost of each


Standard installation/upgrade scenario

schema 1.jpg


Below are the average estimated effort observed for standard installation / upgrade scenario (MD = Man Day).


Average effort for standard installation/upgrade scenario

schema 2.jpg

Basically, upgrade is in average 50% cheaper than a fresh install !


Keeping in mind that we have not yet taken into account the additional costs of data recovery, one could ask:

“why would a company choose register again and configure each and every system of the landscape, as
well as the Agents?


In other words….why even bother with this scenario?


Data recovery/transfer scenario

  schema 3.jpg

Let us take the case of one customer who decided to install from scratch their SAP Solution Manager systems,

with a landscape of 30 connected systems, 2 Solution Manager, and 3 projects including 500+ assigned

documents. In this case, only Early Watch Alert was actually used for Operations.



The total upgrade cost had been estimated to 10 to 15 MD, so between 40% and 66% cheaper!
Moreover, 1 month after the upgrade, they realized that EWA data would have been accelerators for

using Sodoca with the help of RPBD (statistical data…). Now, would it be possible, at that time, to

anticipate those “hidden” costs?



The response to the question “Why would NOT a company choose the upgrade scenario?
is very simple : "
ONLY IF they are not using Solution Manager AT ALL!"



Still, the upgrade scenario looks sometimes like a long and somehow uncompleted journey, especially
when it comes to the tricky part: the adaptation of Service Desk/ChaRM scenarios from the “old” to the
“new” interface, as 7.0 tickets Sap Solution Manager cannot be managed through this web interface.
  • As of SAP Solution Manager 7.1 version, tickets are displayed and managed through a user

       friendly web interface, called “CRM UI”

  • 7.0 Sap Solution Manager tickets cannot be managed through this web interface.


Consequently, two interfaces have to be used by end users :

schema 5.jpg


This usually means at the end of the project a transition phase (weeks or months) where the users have to switch

between the two interfaces.


For those circumstances, one could implement some data migration toolkit (*), providing such features as:


  • Migration of 7.0 tickets into 7.1tickets
  • Creation of 7.1 tickets from external sources
  • Capability to create ticket chains (document flow)
  • Capability to retrieve migrated tickets history (log) and attachments
  • Capability to reassign transport requests to ChaRM cycles
  • Capability to address customer-specific fields and controls
  • Analysis with test mode




  • Consider the upgrade as a default scenario. Otherwise pay attention to side effects and impacts.
  • Use Upgrade Planner to best prepare your installation or upgrade.
  • Use Quicksizer for Solution Manager to safeguard the sizing of your infrastructure.
  • Use “Content Transfer” Best Practices to quickly identify how your data can be transferred.
  • If you are running CRM based scenario like Service Desk or ChaRM, consider a data migration toolkit


(*) follow me for my next blog: “Ticket migration toolkits for 7.0 – 7.1 upgrade”

To be able to freely select the changes and transports, that shall be imported into a system or with using Additional Variant you can do intelligent pre-selection based approach.


Before we should proceed with any further discussion and how-to approach will be nice to know how Selective Import (SI) feature will support us in CHARM project. First of all it is part of the flexibility options for ChaRM (available from SP8) but Selective import itself (part of flex consulting solution for ChaRM) is available from SP10 onwards in standard.



For the better understanding of complete CHARM Import Strategy SAP provided us with the below matrix.







To get the above matrix more clear for subject of Selective Import I will summarize the above table just in two sentence:


  1. Selective Import IMPORT_SEL: customizing parameter which helps  in control of any change document  import to P environment. You will have SI popup for ZMMJ document type. SI for document type  ZMHF does not make sense therefore is not supported .
  2. Status Dependent Selective Import IM_STA_SEL:  We can call it Fine Tuning SI. With this parameter we can control P environment in the way that you can have SI popup  just for one user status for example : E0014 Released for Import of your ZMMJ document type. This means that you will get TR listed  in the SI popup just for the changes that belongs to the document type  which is in E0014 user status! Again all this configurations is relevant for the ZMMJ but not for ZMHF.



Status Dependent Import IMPORT_STA - important parameter ,  is not part of the Selective import feature but it is part of CHARM's global Import Strategy. This parameter is important if you like to prevents imports of the ZMHF TR in the PRD buffer while you are performing Go-Live of the corresponding project.

For an example :  ZMHF can be in process of testing  (still UNTESTED but TR is present in the PRD buffer)!! With this parameter you can control which of the available ZMHF's transports in PRD buffer  should not go to PRD when you are performing Go Live import from the Task list!




Customizing Process for Selective Import


First you should go to the SPRO




Selective Import (not Status Dependent) IMPORT_SEL


in the next screen we should activate Select import feature just for one specific project (e.g. SP10TEST project name) and it will not be active for all others project in your solman landscape. You also have possibility to restrict it to the specific client and system in your logical component , also you can restrict via System Role specifications like we did: Just for the system role Production!!


You should get possibility to add it via New Entry button. For the Import Strategy please select IMPORT_SEL !




To test above scenario we should create an example ZMMJ document type where we should get Selective import popup screen for each ZMMJ User Status related to  PRD  environment!


Later in the text you can see all this in action.




Status Dependent Selective Import IM_STA_SEL



To activate this feature you should in your customizing activate following Import Strategy IM_STA_SEL:






the you should add New Entry in the Status-Dependent Import section:



Step 1:




Step 2:








Your customizing part is over : now you can test it on your SOLMAN system!!


For a test we can create two documents, one  ZMMJ that will be in user status E0009 therefore TR imported in the QAS and ready/waiting in the PRD buffer to be imported during Go -Live. Second ZMMJ will be in user status E0014 Released For import  and according to our customizing settings only this document TR will be available for import in the SI pop up screen!


Corresponding SMMN  is in the Go- Live phase and follow the below screenshots:



ZMMJ in E0014 Released for Import



ZMMJ in E0009 Successfully Tested



Next action is Operator will log in your solman system and he will start import to the production system from the corresponding Task List. During his process you will get Selective Import popup Screen for import in to PRD system



when your confirm this scheduled job you should get Selective Import Popup Screen like is presented in the below picture:




As you can see from the above picture just ZMMJ document 8xx1122 is available and free to select in the SI pop up screen. Document 8x1121  in status E0009 has its TR in the PRD buffer ready for the import but in the SI pop up screen you are not able to select it.!! 




All suggestion and questions are more then welcomed

When we used  the Solution Manager projects (SM Projects) for Change Request Management, there was a need for a bigger project management tool which would help us in managing the IT Projects in more structured way.  What I mean by the structured way is the seamless information exchange between the Project Management Office (PMO) and Change Management Team in a maintenance or implementation project.


Project Management (PPM Project)  is a cross-industry tool which is used to plan and monitor development and consulting projects.  Many customers use PPM to effectively manage their ongoing projects since it has wider integration possibilities (like PS, FICO…). With SP10, exciting things are happining with Project Manageemnt  in Solution Manager area as we are seeing Solution Manager maturing as THE TOOL for entire IT Management (call it ERP for IT). When PPM is deployed in Solution Manager system we see this new possibility of running the projects in a better way.







Source: SAP


Using this;

A. Customer can leverage SAP PPM as the project planning and scheduling tool in SAP Solution Manager.

B. SAP Solution Manager tool remains as Project Excecution Tool and Change Managemnt is now Integrated to PPM Project Management functionality.


Solution Manager Project is assigned  to PPM Project and we can chose what type SAP Solution Manager projects can be assigned to a Project Management project.





Status Mapping b/w PPM Project and Solution Manager Project is allowed. This allows mapping  SAP Solution Manager project status values onto Project Management project status values. This information is used to synchronize Project Management project status values to an SAP Solution Manager project.




The Tasks in the PPM Project is where the Change Request is mapped. There are several ways to create  Change Request/ Tasks  in this integration.


i. Manually create transaction out of task: You will be able to create a transaction via a button, after the task has been released.

ii. Automatically create transaction on release of task: The system creates the transaction automatically after the task has been released

iii. Create task on customized action of transaction: In the transaction there will be an action available to create the Project Management task.




The Change Request inherits the title from the respective Task.


This integration allows the time recording features too, time recording can be done in Request for Change and the data is transferred to PPM Task. Another feature is  mapping the SAP Solution Manager status values of requests for change onto Project Management task status values. This updates the status of the Project Management task, depending on the status of the request for change.


Functional Restrictions


  1) You cannot assign more than one SAP Solution Manager project to an SAP Portfolio and Project Management project

  2) You cannot assign more than one SAP Portfolio and Project Management project to an SAP Solution Manager project

  3) You cannot assign more than one request for change to an SAP Portfolio and Project Management task

  4) You cannot assign more than one SAP Portfolio and Project Management task to a request for change

  5) No distributed deployment

  6) No integration of Quality Gate Management

  7) No Roadmap integration

  8) No migration of objects from the existing integration of Change Request Management and cProjects.

  9) No functional relation and no assignment between the new integration and the existing integration of Change Request Management and cProjects

10) You can assign only one SAP Solution Manager project to one SAP Portfolio and Project Management project. The relationship is always 1:1, so the

assignment to an SAP Portfolio and Project Management project is not copied when you copy an SAP Solution Manager project.

  11) When you transport an SAP Solution Manager project, the SAP Portfolio and Project Management project assignment is not transported.

  12) Not every SAP Portfolio and Project Management project type can be assigned to every SAP Solution Manager project type. The possible assignment

combinations of project types are defined in the customizing.

  13) An SAP Portfolio and Project Management project that is assigned to an SAP Solution Manager Project cannot be archived.


(Credit: SAP IT PPM presentation)


I am still exploring other features and very excited about this integration and endless possibilities we can now achieve with PPM - SM Project Management tool.  I shall blog my experiences in coming days.





Note: The technical configuration of above mentioned integration is explained in this blog:






Filter Blog

By author:
By date:
By tag: