1 4 5 6 7 8 23 Previous Next

SAP Solution Manager

344 Posts

Hi All,


As you probably aware SP8 upgrade of SOLMAN 7.1 can bring you some issues which would require some time to resolve.


One of them I mentioned in the link below:




Today I’d like to share with you another one.


I’ve noticed that in a transport request screen of a change document ‘Create’ and ‘Cancel’ buttons get changed to ‘No Text’.




To solve the issue I had to create online text repository objects in English. (I presume that they already exist in German).


Run transaction SOTR_EDIT




Select  "Short Text"


Language: "English"


Text: "Create"




and click Create button




In a next sreen maintain the following:


Package: "AI_CRM_CM"


Object Type: "WAPP"


Change the Length field to bigger value such as 32


Ignore few warning messages and save it into a transport request




Then I've done the same for other text repository objects (below), the only difference was about the Text filed.


"AI_CRM_CM/CANCEL_BTN_TXT" with text "Cancel"





“AI_CRM_CM/TRANSPORTREQ_CUST" with text "Customizing Request"





"AI_CRM_CM/TRANSPORTREQ_WORK" with text "Workbench Request".





"AI_CRM_CM/TRANSPORTREQ_TYPE" with text "Request Type"






Then I’ve done the translation for the online text repository objects.

This is not necessary if your system's language is English, but required if other languages than English are used.


So,  run transaction SOTR_EDIT



Select Text Type "Short Text"


Language: "English"


Text: "Create"




and click Change button




Navigate to menu path:  Goto -> Translation, select Target Language and double click on it.




Press ‘Yes’ to confirm the next message



   and save it




Repeat the above steps for other online repository objects' translation:









Now the original texts appear in the Transport request creation screen:



Please have a look at SAP note 1806613 for further details


I hope this helps,





Diagnostics Agents Verifications Post SAP Solution Manager installation


Hello, to continue with the intention to create a index (main post) of verification that help us to check errors while and after a Solution Manager Installation, now is time for Diagnostics agents verifications; what do you need to check after a solution manager installation to avoid problem while setup diferent solman scenarios ?




ConnectionsDiagnostics AgentsAuthorizationsBI/BWCRM
Own JobsCentral Correction NoteSaprouterServices SICFSLD/LMDB
Solution ManagerSP Components statusCommunication portsjava stackSystem LandScape


Solman Experts Useful Content:


Prakhar Saxena -> Upgrade Roadmap -> links

          Prakhar Saxena -> Diagnostic Agent Compatibility

Diagnostics agents checks:


IDverificationsap noteDescription
1Check that al agents are on the last release1365123you can check current release of instaled agent
quickly in file "dev_smdagent" in DAA folder
2Check the agent configuration parameters from RCA workcenter using the option "diagnostic self check"help.sap.comRCA is setup automatically after you finish system
preparation and basic configuration, if you found
problems on "diagnostic self check" then you have a
problem on diagnostic agent installation
3Check if you can open the link for manage managed system diagnostics agentslink
4Check the release of saphostagent and upgrade it to the last release and/or SP, remember that:
"SAPOSCOOL is no longer avairable with SAP kernel as from 7.10"

SAP NOTE:  1309499  – hardware capacity analysis in SAP Services

SAP NOTE:  1031096  – Installing Package SAPHOSTAGENT

5Is Willy Introscope HostAgent application installed on managed system inside diagnostic agent core ?797147help.sap.com link
6Check if you can access to Wily Introscope Enterprise Manager and it is running797147help.sap.com lynk
7Since 1st of October, 2012, SAP JVM 4 is the only supported JDK on this release. See SAP Note 1708967 for details.1708967only infomration
8Check if ISAGENT component and LMSERVICES is on the last release,1793553that is to prevent some problems about sap early watch grey
9Check table "E2E_RESOURCES" to avoid CPU overload

that is not only for diagnostic agents but is for avoid

some headhaches

10Is diagnostic agent using saprouter ? check saprouter dev_trace and log filesaprouter

Remember that Diagnostic agent can use without

any problem a remote connection trough saprouter,

but if you do the same with wily intro-scope

saphostagentyou will have a lot of connection problems.

11Check agents logs770853

1.- Increase the trace level

2.- check logs on:
Goto: Agent Administration -

> Agent Log Viewer for SMDSystem.*.log

and SMDAgentApplication.*.log.

12If we have some problem with diagnostics after all of that is ok, we have to create a support message as indicated on that support note1076573Remenber to use that component "SV-SMG-DIA"


Related information from scn forum contributors and friends ;-)



Additional information:



  1. StopServer.bat
  2. sdm jstartup "mode=standalone"
  3. sdm changepassword "newpassword=sidadm555"
  4. sdm jstartup "mode=integrated"
  5. StartServer.bat



  • Useful link to check diagnostic configuration
Formatted link Description
http://<SMD host>:<Java HTTP port
http://<SMD host>:<Java HTTP port>/sap/monitoring/ComponentInfo To check software component information of the java system
http://hostname:5x000/utl/UsageTypesInfo to check usage types



Access to Wily Enterprisse Manager
  • Diagnostic Agent Compatibility at PAM:





ConnectionsDiagnostics AgentsAuthorizationsBI/BWCRM
Own JobsCentral Correction NoteSaprouterServices SICFSLD/LMDB
Solution ManagerSP Components statusCommunication portsjava stackSystem LandScape


Hope that table can help you when found any diagnostic agent installation and/or configuration problems inside your system landscape within solution manager.


Best Regards,


After publishing the blog(http://scn.sap.com/community/it-management/alm/solution-manager/blog/2013/10/09/architecture-of-monitoring-and-alerting-infrastructure-in-technical-monitoring), I got few queries on what these "Data Providers" are and how do they work?. So I thought of narrating the Data Providers and their importance in the overall Technical Monitoring runtime architecture.



Source: SAP


Data Providers are responsible for collecting metric values from the monitored objects and sending it to the Solution Manager Monitoring and Alerting Infrastrucure. To understand all the 'connections' behind the scene in Technical Monitoring; I am including the picture from Solution Manager wiki(http://wiki.scn.sap.com/)  here to simplyfy my effort in explaining all the 'wires and plugs'.




Source: SAP



There are 2 different types of data providers that you can identify in the Technical Monitoring; they are:


1. Pull Data Providers


2. Push Data Providers


Let us see them more in detail;


1. Push Data Providers


The metric values collected by different Data Providers are sent to Solution Manager via web services. There are 2 Push Data providers exist in the Technical Monitoring;


i. Push Introscope - Enterprise Manager collects the metrics and they are pushed to Solution Manager via web services.


ii. Push Diagnostic Agent - The Diagnostic Agent collects the Metrics locally (at OS level) and pushes the data to Data Provider Connector at the SOlution Manager side.

2. Pull Data Providers


As the name suggests somebody is pulling the metrics data from the source; and there are 4 different type of Pull Data Providers are invloved in technical Monitoring;


i. RFC Pull ST-PI - The Solution Tools plug ins are the essential part of Monitoring infrastructure;The metrics are then collected locally on the managed system by using function modules which are part of the ST-PI plug-in.


ii. RFC Pull ST - This is a local Data Provider within the Solution Manager system;the extractor in the solution manager collects the relevant monitoring data from different applications.


iii. RFC Pull ST-BW - All the data stored in the infocubes of BW system (Solution Manager or External) are retrieved and sent to the Monitoring Infrastructure.


iv. Pull DBMS - All the database related information from the DBA Cockpit are retrived to cater the needs of Database Monitoring in the Technical Monitoring.


Troubleshooting Data Providers


Data extractors can be monitored in the “Solution Manager Administration” work center. Here you can find the Infrastructure application. Select button “Alerting Framework”. This will provide a list of all extractors that are used for the MAI infrastructure. Here you can see different type of Data Providers, Extractors and their status.







Basically Consultant work kind of implementation oriented, It is been long time I get into the operational related stuffs, But its good to get into the operational related troubleshooting time to time. Its much useful to understand the technical things working in the back end. Through this blog I would like to share what are our learning from the Full Text Search implementations for Solar01 documents, Our Solution Manager release is SM 7.1 SP7, but I could assure that this blog would be applicable for all release levels of solution manager.



Implementation Guidelines


Last Monday I got request from business to implement Full Text Search for Solar01, Full Text search is the feature of TREX, which helps to search the documents based on words or phrases. Full text search in solution manager can check by solar01 -> Business Blue print menu ->  Find Document -> Extend Attribute Selection -> Full Text Search.


You can give any words in the search term column, system tried to give the list of documents accordingly. Before implementation you could only get "No documents found".




I knew that Trex installation is the prerequisite for full text search and have done lots of trex installation, so there wont be any problem in Installation of Trex, We have already running Trex in one of the host. Connected our solman by creating RFC destination. ( I would like to one small hint here RFC destination should be created by the admin user who has the role SAP_BC_TREX_ADMIN), Trex admin tool creates the Trex RFC with the registered program of naming convention TREX_SID_XXXXX.




But the requirement is the full text search in solar01, so started to search the document for all the sources. We got below guide, which is good and pretty clear, Integration of Trex with Solution Manager for Full Text Search. We followed all the steps, But output is negative. Not able to get the result from full text search.



Confusion leads Clarification


Later we got the below Note 750623 - Solution Manager: Full text search in KW documentation. As per the note we need to follow all the steps in the below spro path SAP Solution Manager -> Technical Settings -> Document Management -> Servers -> Connect Index server for full Text search




This is entirely different from the above guide, The guide mentioned to create RFC from Trex admin tool, later use that RFC for indexing, which we tried, but couldn't help.


Hence we followed the SAP Note.  Manually created two RFCs as IMSDEFAULT and IMSDEFAULT_REG with different program names (ims_server_admin.exe.rfc_sapretrieval), But connection test of both the RFC failed, Though index server and Trex connectivity already working perfectly in OS level.




In SCN there are lots of discussion related to these two RFCs but all of them closed as unanswered. (https://scn.sap.com/thread/1973485, http://scn.sap.com/message/14238836) even not sure from where these ims_server_admin.exe.rfc_sapretrieval coming. We left with no help and bit confused.



Troubleshooting Tips


We checked all the way that trex server side is everything perfect. So we decided to check the logic behind Full text search, Below are the steps we followed to fix this known issues on full text search.


      • Make sure that, TREX RFC configuration is fine and index server also working fine at OS level.
      • Just deal with logical, its NOT required to use the IMSDEFAULT and IMSDEFAULT_REG. Instead we can use the RFC created in TREX Admin tool for both index and searching purpose.
      • Just GoTo SRMO, create new SSR with the RFC created in Trex admin tool, set as default, search engine could be DRFUZZY.  




      • And click the RFC destination tab, Change both Index and search RFC as TREX_RFC created in trex admin tool , Ignore all the warning.
      • Check connection test working, If connection test not working, then you need to check in trex admin tool.




      • Go to Index Category tab , check any Index category created before, if yes, Please delete.



      • Go to SKPR07, In document class SOLARGNSRC , choose the language EN , Document area IWBSOLAR, proceed to mass – actions -> Re- index for document area, this creates the index category for the language you selected, once done, repeat the same for other languages too.
      • You can verify by Indexed document button, or text indexing, Click the diagnosis button on Top, make sure all are green.



      • Now go to SRMO, Index category tab, select the index category created and display,verify all defined language indexes created. Check the Text Indexing, you must get green here, if not, again delete the index category recreate by step 7.
      • Then go ahead and schedule the daily job for regular indexing by the report RSTIRIDX_REINDEX, but make sure you created variant for the report for all the languages you wanted to create index. Because we found that, default only language DE is chosen. Hence we must define our language preference.

                        trex 13.JPG

      • Once job completed, Goto SKPR07 Document AREA iwbsolar -> text search -> you must get the list of all the result according to the word you search.




      • Go To SRMO -> Index category -> select the Index category which newly creaked for Document area IWBSOLAR -> select the language -> click Text indexing and Text Searching -> It should be green.



      • Now Go To solar01, try the find document by full text search it should work.

Let´s assume you are a IT Manager or CIO for an Small an Medium Enterprise (SME), your Board is asking you to optimize your System Landscape, move to the cloud any non critical system and at the same time reduce all the possible operational costs


So, Houston!!, we have a problem:

"You need to grant your business continuity, system operability and optimize their IT platform with an very adjusted budget"


Any problem, bring a challenge:

"How to protect your SAP infrastructure without upfront an investment and get all the benefits of SAP Enterprise Support as soon as possible?"


And with SAP you will always find a solution:

SAP Solution Manager as a Managed Service!




With this innovative model, operated exclusively by Run SAP Partners, you will get the solution for this problem and the key to drive your challenge without upfront investment costs.


A Cloud based SAP Solution Manager will also reduce the implementation times in at least 4 weeks, which give to you all the benefits of your SAP Enterprise Support contract in a suitable scenario.


For more information please visit us at SAP TechEd (Las Vegas / Amsterdam / Bangalore), or get in touch with your preferred Run SAP Partners

As mentioned in my previous blog, there is a must need authorization or Business Role for IT Service Management for all users.



There are multiple options to customize this new interface and I am just highlighting one easiest and useful one.


Let us say we need to have a new title replacing "Solution Manager IT Service Management" or logo text



In order to create it we can navigate to below activity in Define Business Role and can access our custom Business Role ZSOLMANPRO etc.



Now in the Logo Text field we can maintain a text we want to replace with.



We can save this in a Transport Request and can be moved to Solution Manager Production Environment.


Now in SM_CRM or IT Service Management workcenter, we can observe the title is changed



One of the big advantage here is we can customize the business roles like other configuration activities of IT Service Management and transport it. Thus, all the users who already have the connected PFCG role here ZSAP_SM_CRM_UIU_SOLMANPRO will see this difference.


There is also another way but I don't recommend this method for Business Role assignment to user's which is using Parameter ID option as below.



For configuring or creating a new business role, refer below guide on SMP.



Some important SAP Notes


o 1115493 - CRM Web UI: Mandatory SICF services for CRM framework

o 1144511: System parameters required for CRM WebClient

o 1244321: Activation of detailed CRM WebClient error analysis during the development phase

The report AC_ALRT_ANALYSIS_TOOLS provides the plethora of tools to troubleshoot Technical Monitoring issues in 7.1. However most of us would get confused with the new jargons that we come across while troubleshooting. Hence I decided to dismantle the Monitoring and Alerting Infrastructure by individual components to understand the events and workflows.


Below picture represents the MAI in Technical Monitoring



Source: SAP


So let us see the individual components in above picture and understand what is happening behind the scene.


1. Data Provider Connector




The Data Provider Connector(DPC) receives metric values from the Data Providers typically different Agents involved in the setup.There is a huge inflow of data from these providers hitting the DPC at regular intervals. DPC verifies validity of recieved data with the central configuration settings and the metrics which are not configured are rejected.


Behind the Scences:


1. Metric values from the Data Providers are recieved at Data Provider Connector
2. A Web Service receives error messages from Data Providers and Checks if retrieved metrics are valid. Metrics which are not
known in central configuration are rejected.
3. If the Metric is Reporting relevant it is sent to BW Store
4. If the Metric is Monitoring and Alerting relevant it is sent to Event Calculation Engine.


2. Event Calculation Engine




Event Calculation Engine calculates the current status and the events from the metric values. So it acts as a Traffic Signal Indicator, it decides what rating to be given for the Metric just recieved from the DPC. The Metric is compared against the Configuration settings and a combination of Current Status + Rating (Green, Yellow, red) is decided.


Behind the Scences:


1. The Data Provider Connector sends Metriv value to the Event Calculation Engine
2. Arrive at a 'Event' which is a mixture of Current Status+ Rating for the Metric in hand.
3. Event+ Metric Store is updated with the arrived rating and status for the Metric.


3. Alert Consumer Connector



Alert Consumer Connector receives new alerts from Event Calculation Engine and decides what happens to the alerts.

Behind the Scences:


1. Alertsfrom Event Calculation Engine is recieved at the Alert Consumer Connector
2. Calculates if a new Alert has to be generated od any existing alert to be updated.
3. New or updated alerts are written to the Alert Store
4. Decides based on central alert configuration if the alert has to be forwarded to any other 3rd party tools.





This blog is child blog  of the below blog:


ZMCR - Custom 3 Step Approval Procedure


Go to SPRO in the below link:





Click on the Define Partner Determination Procedures






in the below picture you will have chance to check are all partner functions, you are planning to use, selected in your RFC for daily use ??






in our case all partner Functions are present.

This blog is child blog  of the below blog:


ZMCR - Custom 3 Step Approval Procedure


, but can be solo guide for the Rule creation as well. 


To create rule policy for the newly created app procedure you should start CRM_UI transaction with the proper transactions2013-10-03_15-56-14.jpg


our final rule will look like is presented below:




we should create rule for each our app. Step this means this will lead  that for each process you should corresponding Partner Function like is presented in the above picture. SDCR0002 Change Manager, SDCR0003 Change AB, SDCR0004 Quality Manager,


To create its own App procedure Rule  you can follow below process example:


Clik on the "New" button on the below screeen.





then in the next screen in the Context you will choose Approval management, and in the Rule police you will put the rule name in our case Proba_boris1








then you will get next screen





then click on the Draft Rules , and again click on the  "New" Icon again




in the Rule folder details you can enter rule description , and again you can click on the New button again.




in the red square box you can start creations of the rule itself :





if your approval procedure is Z01 and if your Approval Step is Z_step_02, and if your Approver is empty, then put as the Partner Functions - Change Advisory board that you entered in the RfC input screen:

After you finish with the Rule you must Release Draft Rule like is presented in the left part of the Rule editor.





after you release you rule it should looks like the above. It should have green traffic light.

This blog is child blog  of the below blog:


ZMCR - Custom 3 Step Approval Procedure


On the page 4 of this manual you have information when and where will you use Rule Modeler Profile. 



in our case we will create new one named Z3T_CM_AP_PROC this one we will use along with our newly created approval process ZMCR0001.


Where in SPRO you should do customizing??


In the CRM’s SPRO section you should choose CRM_IC_55:


in the next screen you can add our Service Manager Profile that will go along with the our newly created app procedure.







use new entry to create new one





then you will have this :






next step is to add your rule to the service profile. Please follow below steps





on the next screen click on the Ok




in the policy insert our rule name:







If you  are not shure about exact name of your approval you can recall it  via the rule modeller transaction:



the name should be the same with the blanks!!!









then you can return to page 4 where you can put our newly created name Z3TCM_AP_PROC

Preparation of the Custom 3 Steps Approval Process


Working environment: SAP Solution Manager 7.1 SP8


Our  goal is to have possibility in SMCR0001 of two types (or more) of APP procedures to which you should decide in the ZMCR drop down menu during your creation of ZMCR document.



Approval process will be in 3 steps.

  • First step performed by: Change Manager (SDCR0002)
  • Second step performed by: Advisory Board (SDCR0003)
  • Third step performed by: Quality Manager. (SDCR0004)


Ok let’s start with the customization:


In SPRO you should start in the section


in the first step you should define ZMCR001 Apprv. Procedure  with the New Entries you should get chance to create new approval process with the below attributes like is presented in the below picture:






next step is to define 3 new approval steps like is presented in the below picture:



The next screen you should define – Assign Approval Steps. In this step you add Partner Functions to the each step (in our case will be Change Manger , Quality Manager, Change Advisory Board)


Step 3: you should add Z3T_CM_AP_PROC later in the process when you create this profile via SPRO action CRM_IC_055


How to create this Rule Modeler pls follow below link to blog:


Step3 - Rule Modeler Profile Creation (CRM_IC_55 spro)


In the next screen (action) you should define which steps are previous for the approval process itself.




in the next step you should approval Determination Procedures. You should add ZMCR0001 and Ruler Modeller Prof. that you are going to to add later when finish the STEP 3. (details you can find in the below Blog Link)



Step3 - Rule Modeler Profile Creation (CRM_IC_55 spro)


The next step is about how to assign Default Approval Procedure.

This procedure will be always available in the drop down menu of the corresponding RfC. In case you would like to have all approval procedures available in the Request for Change drop down menu like is presented in the below picture:




To do this you should neither  add nor create any Approval Process. Please follow the below process:




In the section Assign Default Approval Procedure your settings should be like in the below picture. As you can see

Default Approval Procedure screen is empty like is presented in the below picture:



...this means that you will have all approval procedures available to choose in the RfC drop down menu!!


If you would like to reduce it  Approval  Procedures just on one, then you need to add following line in the above screen:



this action will result that you will have just one App. Procedure available in your RFC like is presented in the picture below:




STEP 2. Rule Creation with CRM_UI

To create rule policy for the newly created app procedure you should start CRM_UI. For the complete process please follow the below link.


Step2 - Rule Creation with CRM_UI - Approval Procedure



How to Check Assigned Partner Functions in RfC


If your newly created approval Process has a new  Partner Function (e.g. Quality manager) you must add it to RfC otherwise it will not work.

To check if your Partner Function for our 3 tier process approval process belongs to our document type for RfC, you should use below link :



How to Check Assigned Partner Functions in RfC (CRM_PARTNER_PDP)



Approval Procedure determination via Multi Level Categorization


For more advance configuration of the approval procedure please follow the below blog from Daniyar Kulmanov

Approval Procedure determination via Multi Level Categorization



During the activation of Downgrade Protection in Solution Manager ChaRM 7.1 many of you may have faced errors or at least warnings related to missing CTS Plug-in in managed systems.  If CTS Plug-in is not installed in Solution Manager and distributed to the managed systems, the Downgrade Protection functionality can’t work properly.


In this blog there is some information about this plug-in, why we need it and how to proceed.


We will hear a lot about CTS Plug-in when the next Support Package stack is released, because of the Central CTS functionality that will be delivered. CTS Plug-in is also necessary for CTS+.

What is CTS Plug-in


CTS Plug-in is an add-on containing enhancements to CTS (Change and Transport System). CTS_PLUG 2.0, software component CTS_PLUG 200, is delivered with SL Toolset and installed using Add-On Installation Tool.


cts plug-in.jpg


According to the Online Help,the CTS plug-in is available for the following releases:

  • For SAP Solution Manager releases as of 7.01 SPS25.

As of SAP Solution Manager 7.1 SPS05, CTS plug-in is an obligatory component. This means it is automatically installed with SPS05 of SAP Solution Manager 7.1.

  • For SAP NetWeaver releases as of SAP NetWeaver 7.3 Enhancement Package 1.

The functions of the CTS plug-in may vary for different releases and SP versions.


The current version of CTS plug-in available for download in the SAP Marketplace is 2.0 SP08 and is delivered with SL Toolset 1.0 SP08. Check note 1787683 for more information about SL Toolset 1.0 SP08. But from what I understood, SP08 has only fixes and SP07 has patches for functions in Change Request Management for SAP Solution Manager 7.1 SP9, which is not yet available. Maybe that’s the reason why the Online Help and the SAP Note related to CTS Plug-in still consider that the current version of the CTS plug-in is SP06, delivered with SL Toolset 1.0 SP07.


CTS plug-in is available for the following releases:

  • SAP Solution Manager 7.01 as of SP 25
  • SAP Solution Manager 7.1 as of SP 01
  • SAP NetWeaver 7.3 Enhancement Package 1


For more information on SL Toolset, refer to http://service.sap.com/sltoolset.



The CTS plug-in is integrated into the existing Change and Transport System. It enhances the functions of the existing CTS.

Below there is some info from the SAP Note 1665940:


  • CTS_PLUG 200 consists of the following parts:
    • CTS server plug-in, release-dependent

               This plug-in installs the included functions in the current system.

               This is either an SAP Solution Manager system which acts as the CTS server, or

              an SAP Netweaver system.


    • CTS Bootstrapper plug-in, release-independent

                This is required to activate the CTS server plug-in on the corresponding system.

    • CTS Services plug-ins, release-dependent
      These are required to update CTS functions in the managed systems, if you are using functions of the CTS plug-in that use managed systems.
      Available for the following releases:
      SAP NetWeaver 7.40 SAP_BASIS SP02
      SAP NetWeaver 7.31 SAP_BASIS SP01 to SP06
      SAP NetWeaver 7.30 SAP_BASIS SP01 to SP09
      SAP NetWeaver 7.02 SAP_BASIS SP06 to SP13
      SAP NetWeaver 7.01 SAP_BASIS SP07 to SP13
      SAP NetWeaver 7.00 SAP_BASIS SP14 to SP28

Why we need the CTS Plug-In in ChaRM


With SAP Solution Manager 7.1 SP05, Downgrade Protection (DGP) was delivered to reduce the downgrade risk in the managed systems. The DGP checks are performed when you release, import, decouple, assign a transport request or reassign a change document.

When Downgrade Protection is activated in Solution Manager, the system checks if the CTS Plug-in is activated when we perform the Downgrade Protection analysis. The CTS Service plug-ins contain analysis functions for downgrading and overtaker requests based on object overlaps.



According to the OnLine Help, the following functions are available for CTS plug-in on SAP Solution Manager 7.1 and SAP NetWeaver 7.31/7.40:

  • Connecting further applications with the Change and Transport System:


The Change and Transport System allows you to manage transports of ABAP objects in your system landscape. Using the enhanced Change and Transport System (CTS+) you can transport non-ABAP objects using the CTS. In addition to this, you can connect further non-ABAP and non-SAP applications with the CTS to transport these objects using CTS. CTS plug-in contains the required functions to integrate these applications in CTS.


  • Managing transports of non-ABAP objects:


The new version of Transport Organizer Web UI is an improved browser-based WebDynpro ABAP application to manage transports of non-ABAP objects. You can use this UI to create transport requests, and get an overview of all transports in a system, for example.


  • Importing non-ABAP transports using the Import Queue Web UI including import checks:


To import transports of non-ABAP objects, the Import Queue Web UI is available. It is also a browser-based WebDynpro ABAP application that allows you to perform imports into target systems. Integrated import checks allow you to check for predecessor transports in the import queue or for potential downgrading transports.


  • Distributing CTS service plug-ins using the Plug-In Management Web UI:

If you are using Change Request Management on SAP Solution Manager you may be asked to distribute the so-called CTS Service plug-ins, which are part of the CTS plug-in, to the managed systems. Plug-In Management Web UI allows you to check the prerequisites for the distribution and finally distribute the CTS Service plug-ins to the managed systems where required.


As this blog is related to ChaRM, I will focus on the Distribution of the CTS Plug-in to the managed systems.


Note: To be able to use the functions contained in the CTS plug-in, the system on which you install the CTS plug-in must be configured as the domain controller and it must also be the communication system for your non-ABAP systems.


Installing the CTS Plug-In   


First thing you need is to install the CTS plug-in. You can update plug-in by installing the current Support Packages. As of SAP Solution Manager 7.1 SP 05, the CTS plug-in is contained in the SAP Solution Manager Support Package stack. You obtain the plug-in automatically by importing the Support Package stack.


  1. You must first implement SAP Note 1691028 in your SAP Solution Manager as a prerequisite.

  2. Before you install CTS_PLUG 200, keep in mind that it is not possible to uninstall ABAP add-ons.

  3. Make sure that you have installed the latest SPAM/SAINT update on your system. If a new version is available on SAP Service Marketplace, import the new SPAM/SAINT update.
      • In order to install CTS_PLUG 200 SP06, at least version 47 of the SPAM/SAINT update is required. In order to use all functions of the CTS Plug-In on SAP NetWeaver 7.31 and 7.40, version 49 is required.

  4. Ensure that at least the following versions of tp and R3trans are installed on your SAP Solution Manager/SAP NetWeaver system  AND on any managed ABAP system or communication system, if you are using CTS plug-in functions on managed systems:
      • tp version 380.05.18 or higher (720 kernel)
      • R3trans with a release date of 06.03.12 or later (720 kernel)

  5. Obtain the following notes before you begin the installation:
      • Add-ons: Conditions: 70228
      • Problems with transaction SAINT: 822380

  6. Check that your system meets the following prerequisites: If you have not yet installed these component Support Packages, you can include them in the installation of CTS_PLUG 200. For more information, see Note 83458.

  8. Required Components and Support Packages:



Support Package






SAPKB731001 to SAPKB73106



SAPKB70206 to SAPKB70213



SAPKB70107 to SAPKB70113


Note: You can install CTS_PLUG 200 on any SAP NetWeaver system with the above releases, but the functions only work on SAP Solution Manager systems and on SAP NetWeaver systems as of 7.31 SP01. SAP recommends that you install the CTS plug-in only on SAP Solution Manager systems and SAP NetWeaver systems as of 7.31 SP01.


Next steps will be:


  1. Install the CTS plug-in according to SAP Note 1665940. Be sure to have the latest version of this note.
  2. Activate the Services for Plug-In Management Web UI.
      • Activate Service /sap/bc/webdynpro/sap/cts_configuration_plugin_mgnt
      • You can easily find it from the SICF main screen entering SERVICE in field Hierarchy and CTS_CONFIGURATION_PLUGIN_MGNT in field Service Name, and executing the report.


Distributing the CTS Plug-in


There is a Web UI called Plug-In Management that you can use to distribute the plug-ins to the managed systems. For non-ABAP systems, the plug-ins are distributed to the ABAP communication system of the non-ABAP system.



To start the UI, you need the authorization object S_TRANSPRT with field ACTVT and value 03.


  1. Logon to Solution Manager (which is your CTS Server) and run transaction SZENPLUGIN. The CTS Plug-in Management Web UI will start in the browser.



cts plugin screen.jpg



  1. Select the systems to which you want to distribute the plug-in and validate their status.


Validate the system before distributing the plug-in. The system will verify whether all prerequisites are met. Depending on the result, the system displays a red or a green traffic light icon in the Status column. If the status is red, you can display more information using the link in the Status column.


You can use the Filter button to help you filter the systems you want to see. You can also personalize the list view and add/hide fields


To perform a validation: Your user also needs to exist in the managed systems.


validation complete.jpg









    Press See Details:



    details validation.jpg



    If the system informs you that the import destination is missing, you need to configure the RFC Import destination between the CTS server and the managed system. Depending on the configuration of the CTS server, this connection may be re-used from an existing SAP Solution Manager destination. You only need to create this RFC if the systems asks you to do it during the validation.



  • In SM59, create the RFC according to the following naming convention: TMSIMP@<SID><CLIENT>.<DOMAIN_NAME>
  • For non-ABAP systems: Use the communication system of the import target as the Target Host for the destination.
  • For ABAP systems: Use the actual target system as the Target Host for the destination.
  • SAP Recommends to use Trusted system. In exceptional cases, you may also use a specific user and password. SAP also recommends to encrypt communication data using Secure Network Connection (SNC) for RFC communication with managed target systems.

    Validate the system again after you configure the Import Destination.


    1. Distribute the plug-in.


    Distributing the plug-ins means importing transport requests into the managed systems.

    For non-ABAP systems this means importing the transport requests in the ABAP communication system of the non-ABAP system.


    To distribute CTS plug-in on the managed systems, your user needs to be assigned the authorization object S_TRANSPRT with field ACTVT and value 03 as well as authorization object S_CTS_ADMI with field CTS_ADMFC and value IMPA.


      • Select the managed system and choose Distribute Plug-In.




      • In the dialog box, confirm that you want to import the transport request.


    import plugin.jpgplugin has been distributed.jpg


    You can click More Information in order to read additional information about Distribution of CTS Service Plug-Ins.


    The CTS Service plug-in and the CTS Bootstrapper plug-in are distributed to the managed system. If the managed system is a non-ABAP system the plug-ins are distributed to the ABAP communication system of the non-ABAP system.



    Transports imported into the managed system:


    transports cts plug-in.jpg



    Example of the object list:


    transport bootstrap.jpg



    Distributing CTS plug-ins using RFC destination and program


    If you cannot update your SAP Solution Manager to at least SL Toolset 1.0 SP07 (CTS Plug-in 2.0 SP06) and don’t have the Plug-in Management Web UI, you can install or update the CTS plug-ins on the managed systems executing program CTS_DISTRIBUTE_PLUGINS on SAP Solution Manager which distributes the plug-ins to the managed systems. You may need to configure the Import destination in this case too.


    1. Run program CTS_DISTRIBUTE_PLUGINS and enter in the selection-screen the System ID and Domain to which you want to distribute plug-ins. Execute it. The execution will take some minutes.




    1. If the program displays a message that the installation of plug-ins was successful the updated plug-in functions are available in the system and you can skip the next sections.
      Repeat these steps for every system which requires updating.
    2. If the program displays a message that an import destination has to be configured, create the RFC destination as described above in topic Validating. After you have created and tested this destination you can execute program CTS_DISTRIBUTE_PLUGINS again.


    After moving here & there in different blogs, wikis and SCN posts, finally I could able to generate EWA for JAVA based systems. I thought of sharing the steps for creating the Early Watch Alert (EWA) for all JAVA based systems with you.


    Below is the scenario for generating EWA :-

    JAVA System

    Enterprise Portal (EP) server of NW 7.3 EHP1 SP6

    Solution manager Sever


    Solman 7.1 SP 8 with MS SQL 2012




    Windows 2008 R2 (64 bit)



    Prerequisites to be checked & performed


    1. As per note 797147, download the Wily files (always select 'automated installation' option while selecting the downloadable files):-



         1.3. Agent files for the managed systems Introscope 9

    2. Update LM_SERVICE in solman server as per note 1900777 .


    NB: While deploying this component, you may get following error message. To get rid of this error allot SAP_J2EE_ADMIN role to j2ee_admin user .


    Error 1.JPG

    3. Check RTCCTOOL tool ( run RTCCTOOL in SE38 ) in solman server and apply the prerequisites .



    4. Register the JAVA system (EP) in solman SLD . After completion of SLD registration & synchronization between SLD and LMDB , make sure all software component and product version is coming properly both in LMDB & SMSY. Then add the product version (Logical Component) to a solution in SMSY. [Addition of solution is also been taken care of  in managed system configuration, but I prefer though SMSY for time saving ]



    5. Download eula.txt and osi package (9.1.5) from http://opensrcd.ca.com/ips/osgi/ third party FTP link.



    6. Install latest diagnostic agent both in Solution Manager and EP server and register both of them in solman SLD. You can select SLD registration option while installation of SMD agent .


    Configuration Procedure

    1.  Install Enterprise Manager 9 in solution manager system . Before that extract EM and make following changes in eula.txt file :-

    " LGPL = accept "


    Copy the eula.txt and osi package (9.1.5) to willy EM install able folder and continue the silent installation .  Silent installation takes the input from "installer.properties" files available under EM extracted directory. In case you want to install with front end GUI, then remove this file from that folder and run the set up file. Verify the installation in "/usr/sap/ccms/wilyintroscope/install/Introscope_<version>_InstallLog.log.". It should show SUCCESSFUL for all installations.



    2.  Extract the EM management module zip file and copy in /usr/sap/ccms/wilyintroscope location. Then take a restart of EM windows service to reflect the management module.



    3.  Enable the maintenance mode in solman server and then install ISAGENTJ515_0-10010975.SCA in EP server through JSPM .



    4.  Now again disable maintenance mode and  check whether both the diagnostic agents are showing GREEN color or not in Agent Administration . You can access the same through "http:<FQDN of solman server>:<http port>/smd/AgentAdmin" link.



    5.  Also check webview URL "http://<solman FQDN host name>: 8081/webview" . This port may be 8080 also. In case it gives following error :


    Error 2.JPG

    Use following solution :-


    Change "introscope.enterprisemanager.webserver.port" parameter to 8080 in IntroscopeEnterpriseManager.properties file under "<installation drive>:\usr\sap\CCMS\wilyintroscope\config" and restart SMD and Willy windows service and try.

    6.  Install Microsoft Silver light in solution manager server.



    7.  Now check "http://<solman FQDN host name>:<http port>/webdynpro/dispatcher/sap.com/tc~smd~navigation/StandaloneApp?APP_ID=SMD_WILYADMIN_JAVA" URL and confirm whether the Enterprise Agent installed in managed system can communicate with Enterprise Manager installed in solman server or not. Now click on "configure Introscope agent setup" and select the required "Autoprob Directives" and press "APPLY" button.


    8.  Now the full & final step is "Managed System Configuration " for java system (EP). Run the pre-requisite diagnostic requirement for JAVA server and and apply if missing updates found.



    9.  After performing complete managed system configuration , you can get the EWA report for the  solution as well as for the JAVA system in solman_workcenter > 'System Monitoring' tab > Reports > 'select the solution'.



    Troubleshooting Related Notes

    1010428 , 1852733, 1765041, 1900777, 1663549, 1611483 .


    I hope these clear cut steps will help you ahead .



    This blog is inspired by "Introscope Version 8 Installation Guide For SAP" , "EWA for non-ABAP components" documents.



    Sure that this trick is already know for must of you that work daily with product availability matrix ( friendly named "pam" ), but for me is don't know since some days that I try to find more Technical information about new release of SP10 (before you are able to download SP10), the trick is just to list some sap notes that will be available for next Solution Manager FP2  (SP10), there are 2 options to get that list.


    One options is from swdc software download catalog or other from a note advance search selecting product version and SP level and/or expanding stack info inside a SAP Note ( that option is on the last step of the table ).


    to find a better way to publih on snc y try to use a table with a thumbnail for the image that you can expand clicking it, and a short description of the step at the left column for that people that love read whitepapers (with poor English) better than scan and screenshot  


    Step DescriptionScreenshot

    1.- SWDC

    Just open SDWC (software download catalog), select "SAP Software Download center" menu option and on the vertical menu, search for "Support package and patches" -> "Browse our download catalog" and on the right hand select "SAP Technology Components" after you can click on Solution Manager 7.1 and expand the "Solution Manager ABAP Stack"


    2.- display SP details

    Once you click on "Support packages", you will be the stack list just on the new frame loaded bellow, there you only can see at the last released stack SP8 Stack.

    Just search for the last stack  (the first on the list), on that sample process I select stack SP8 "SAPKITL708".


    3.- change url paramenter

    After you click on the "title" of the SP8 stack you will open a new windows to check the stack properties, that new internet browser windows end with a url parameter like this: ?sp1=SAPKATL708.


    4.- discover new objects

    Then on the url, just change the last stack number from 708 to 710, and you will be able to see the list from that stack corrections.

    I can select SP9, because must of that stack corrections sure that are omitted or included in the next SP10, SP9 are no released.


    5.- list notes

    Now on the Support Package SAP KITL710, you can see 203 Notes, 2 for BC Basic Components, 200 for SV Services and 1 for Miscellaneous; on that screen you can expand the complete list and lock at each note for get some idea about the new content and some correction to take in consideration before you star playing with SP10.


    6.- download list

    When the list are loaded you can see a most of SP10 notes, with component, note number, and note correction. that notes are available trough service.sap.com/notes advanced search but don't think that you can download and load to your solution manager (I don't test it).


    7.- option 2: from note search

    If you try to open a note with service.sap.com/note you can load that list from "Package name" as indicated on that screenshot from link:





    With that list we can see the amount correction are for:
    - Custom Code Management
    - Change Request Management
    - Solution Manager Implementation
    - Business Blueprint / Implementation
    - Project Administration
    - Landscape Management
    - Business Process Monitoring
    - Content for technical Monitoring
    - Solution Directory
    - Process Scheduling Management
    - Service Desk / Incident Management
    - Test Plan Management


    And more littler groups with 2 or 3 correction, after a quick read of the list I found something interesting to save when we can go to SP10, like:


    - 1724697 - Authorities for UI objects in the assignment blocks

    - 1883902- Start Transaction from Solution Manager is dumping in NWBC

    - 1871878-Alert Inbox: Gray Icons For EWA of Java Systems

    ( damn, other grey nightmare like ewa grey xD but this for MAI )

    - 1895860-Workload data collector dumps after long runtime

    ( other workload data collector problem :_( )

    - 1875419-ST710:AI_CRM_IM_UPDATE_FROM_SAP has a long runtime

    ( that's is really interesting if you work with a huge sap message )

    - 1876243-Optimize Job REFRESH_ADMIN_DATA_FROM_SUPPOR for one customer

    ( new and great option for VAR scenario )

    - 1885123-Reports to delete Solman Products and related Ibase comp.

    (I need that correction now)


    well, that post is not really usefull but interesting to know wo is possible to discover corrections before SPx are released, maybe there is other option for that but I don't know.


    Hope that can be usefull for someone


    Best Regards,







    This blog explains the end to end process of Test Management Option 3 in SAP Solution Manager, valid to SP07. In the underlying blog I explain the process of exchange of business processes, business requirements, test assets and test results between SAP Solution Manager and IBM Rational Tool.  The type of test run used is Manual run in the below example; if we chose to automate the testing process then  either IBM Rational Functional Tester or Worksoft Certify tools can be integrated . I am writing this blog in the same line as my previous HPQC blog for better understanding and comparing the process b/w these 2 testing tools.


    About IBM Rational Tools for SAP


    Rational Quality Manager is the offering in the quality management space by IBM Rational. It is a collaborative, web-based, quality management software for comprehensive test planning, manual testing, and integration with automated test tools.





    SOLAR02 Business Requirement Transfer Process


    The Business Blueprint Configuration (SOLAR02) is the single window for transferring the Blueprint from SAP side to Testing tool at the IBM side. During the Blueprinting process of a project, the Business Scenarios and Processes are defined and all the possible variants for standard scenarios are identified.  After the configuration of a Business Process by Functional Consultants , including the Development are done; the Blueprint can now be synced with the Testing tool for complete scenario testing. Business Process Document in a Documentation tab should be updated with the complete Process Flow. This plays a crucial role since the Tester working with IBM rational might not be SAP Expert. So this document would be the basis for any reference during the testing process.  We would take example of a Business Process “Procurement without QM”  under Procurement scenario  for our demo.






    The Business Process document for this Process is maintained under Gen. Documentation tab in SOLAR02. If you are configuring very specific to your company business process then the same should be maintained under Proj. Documentation tab.




    Transfer to IBM Rational Tab


    In the Transfer to IBM Rational Tab, two information are maintained.


    1. Business Requirement Document

    Business Requirement Document, as mentioned above would be the *only* source of information for Testers to understand what the Business Process is all about. This also should provide information on “How to” run the Business Processes and expected results from the run. So the document maintained either Gen Document or Proj. Document would serve  as a Requirement Document.





    2. Test Object


    Test Objects are the Transaction Codes, Configurations or any relevant Developments which are part of your end to end Business Process. With the help of all the Test Objects you should be able to run your Business Process completely, from Start to Finish.


    We would do the mapping in the IBM rational Connector that how Requirement Document and Test Objects are represented in IBM Rational Quality Manager tool after they are pushed from Solution manager




    The sample tab would look like below




    The Blueprint along with Test Objects and Test Requirements are transferred to IBM Rational QM via the Dropdown available on the left corner of screen.




    Testing in IBM Rational Quality Suites


    In Rational CLM, view SAP Business Blueprint requirement assets transferred.  A Requirements Collection Procurement is automatically created, contains the requirement assets specified for transfer.





    A Test Plan 'Procurement' is automatically created, will be populated with test case assets.The Requirements Collection 'Procurement' is automatically linked to the Test Plan Sales with Validated By traceability.






    In this example a Manual test script is being created, or a Functional test script recorded with Rational Functional Tester could also/alternatively be created and associated with this test case.






    When you run a test manually, you follow the test steps and perform operations on your application. Then, you compare the expected results with the actual outcome and record the results. You can execute a manual test as many times as needed. The results are stored separately for each run.


    Transfer the Result Back to SAP Solution Manager


    The test results are transferred back to SOLAR02 to update the Blueprint with the testing information. This is done via the IBM Rational SAP Connector.




    1. Attribute option in SOLAR02

    In the Transfer to IBM Rational tab in SOLAR02, the test results are displayed against each line item individually.



    2. SOLAR_EVAL txn code



    The entire view of test results are displayed in SOLAR_EVAL txn code as below




    Filter Blog

    By author:
    By date:
    By tag: