Concept: This blog allow you to configure the SLA assignation based on the information of the incident, actually using customizing is not possible to use different conditions, this configuration allow you to play with several inputs to assign the SLA that you need.



In Solution Manager you need to execute the transaction BRFPLUS


In the Menu, select “Create Application

Define the Application name:


Remember to SAVE and Activate the application.

Create the New Elements:

Right click on the application and select to create a new element..


Create the element using the “Bind to DDC element (data Dictionary)


Us the DDIC element CRMT_SRV_SERWI to bind the Service Profile


Remember to SAVE and Activate


Execute the same steps for CRMT_SRV_ESCAL


Now you will see the Data objects created and activated


Create the Decision Table:

Now you need to create the Decision Table, right click on the application and select Expression—>Decision Table..



Create and navigate to the table


Now you need to define the columns.


Insert a new column from the Context Data Objects.


Select the Application SOLMAN and add the fields that you want to use for the assignation, for this example we use PRIORITY and CATEGORY


Now you need to add the Result Columns


In this case we use the objects created previously (CRMT_SRV_SRWI and CRMT_SRV_ESCAL)




Now you need to add new data to the table, you need to select the insert Icon


In this example we add 2 entries with different sets Priority and Service Profileimage036.png

Create the Function:

Now you need to add a function, Right click on the Application and then Select Function


Create the function and navigate to the object


Now we add the Data objects that will be used for the function, in the tab signature select Add Existing Data Objects.



Add all the objets found in the SOLMAN Application (This allow you to use different  columns in your decision table.



Now we need to define the Result data object , select Create in the action button.


Create a new Structure object to allow you to pass the 2 values


In the new structure, click in Add Existing Data Objects



Select the Application ZSLA and add the 2 new objects created in the previous steps.


Remember to SAVE and ACTIVATE

Create the Ruleset:

Now is time to create a new RuleSets, you need to select your Function (Blue pyramidal Icon) and then the Assigned Rulests tab, then click on “Create RuleSet”



Define the new name


After create the Ruleset you need to create a new Rule, to do that, you need to Click on “Insert Rule” and then in Create


Now write a description, and then select in “Then --> Add”, the option “Process expression—>Select..”



Now select the decision table created before


Now you need to SAVE and Activate.

Development Part


To implement this part you need to ask your development team for support,  you need to create a new PPF Action (you can replicate the configuration of the action ZMIN_STD_FIND_PARTNER_FDT).

Create a new implementation for coping the implementation ZAI_SDK_TEAM_DETERM and using the function module 'CRM_SERVICE_I_READ_OW' and CRM_SERVICE_I_CHANGE_OW to update the Incident


Best Regards


How to Add or Remove a System from a ChaRM Project


In a Scenario such as needing to add a 4th system to a Logical Component (Pre-Prod), or Remove such a system, please follow the steps below:


In our example we have a Project: ERET_M

Logical component for a system S71: SAP SOLUTION MANAGER [Solution Manager ABAP Stack]


101 – Dev

102 – QA

103 – Pre Prod

104 – Training

105 – Prod

Retrofit : RIG 501


Basic steps:


Close current cycle of maintenance project






Save through the next phases until reaching



Being Completed:




Next Agree and Proceed Through,







Adjust Logical components as necessary

From SMSY:





Create a new Logical Component in LMDB




Click Display -> Change


Green Check to Launch LMDB



Add Technical System and Adjust Type



Use transaction Solar_Project_admin

Add / Remove appropriate systems (in this example, adding Test System 104)


Create New Task List



View Task List




Adjust TMS






Dev -> qa


Qa -> pre prod


Pre prod -> prod


Final Product



Dbl Click S71 and Remove Transport Layer, add Development System in table below








Check Project

Create new cycle



Activate CTS Functionality




Check the Landscape

Create Task List






Confirm Changes to Project Landscape in Task List:



Manually catch up transports where required.






Do you need to know by the time you enter the office if the jobs that were scheduled during the night ended without errors?

Do you want to receive customized job reports on your mobile device?

Would you like to be able to receive the result of a Job Management POWL query, for example the list of jobs in a 24h time window as shown below, by email?

00 jsm_wc_smse_query.png




1. You have SAP Solution Manager Support Package 10 or higher installed


2. You have to create the required POWL queries in the Job Management Work Center that either

a) Collects the job data from the SAP system directly or

b) Collects the job data from an external job scheduler like SAP CPS by Redwood

The queries have to use dynamic time windows in order to get for example the job runs during the past 24 hours.




Once the queries are available you navigate in the Job Management Work Center to the Administration view and start the configuration of the POWL Query Result notification. As the name implies this works for al kinds of POWL queries and not only for the queries defined in the Job Management Work Center.

10 jsm_wc_admin - config.png

In the configuration application you just select Add, then select the POWL query you want to receive (make sure that you have selected the correct type of query) and enter your business partner number.

11 jsm_wc_admin_new_query_result.png

After pressing OK you should see your configuration in the list of available configuration. Select your configuration and the assigned business partners will be displayed:

12  jsm_wc_admin_new_query_result_2.png

Of course it is possible to assign more than one business partner to a configuration as you can see from this example:

13 jsm_wc_admin_new_query_many_recipients.png



Now that the configuration has been done return to the  Administration view in the Job Management Work Center and select Schedule Job in section POWL Query Result Configuration.

20 jsm_wc_admin -schedule.png

The job scheduling of Job Scheduling Management will be started already prefilled with the report to be schedule. Just enter your preferred start time and recurrence and you're done.

21 jsm_wc_schedule_email_job.png




What's next? Just wait for the job to run and you will receive an email containing the results of your POWL query, see the example below:

30 POWL_email.png

This is a follow-up post, and part 1 is available here.


a) Open Job Management WorkCenter. transaction SM_WORKCENTER, Select Job Management


b) Select Job Documentation, Click on ‘All’ for example

   Select relevant Job Document, click on Job Documentation-> Edit

   You can create a new Job Document as well.

job doc.jpg

c) In the New Window that opens, click on Systems tab

jobdoc systems.jpg


d)The new Job Monitoring Config UI should be launched, it may launch old BP MON Monitoring config based on the selection.

But the current document only deals with MAI based Monitoring



e) The Add Jobs button is disabled if at least one monitored object is found in MAI corresponding to the Job document.

On Press of “Add Jobs From Managed System”

The filter values in the popup come prefilled with Job Information provided in the job document.

add jobs managed.jpg



On press of “Get jobs from Abap System”, the row in the lower table is selected and added.

The lower table has the possibility of creating a new monitored object or use existing monitored object.

The JobDocu ID assigned to the monitored object, is the Job Documentation ID of the Calling job document.

On Press of “Add Jobs from External scheduler” the filter values are also prefilled.

The user selects the filter values and presses on Find, multiple rows are displayed.



g) After the job is added you can see that the add jobs button is disabled.


job as mon object.jpg


Thank you for going through my blog.

In continuation to earlier blog (Part 1) , we are going to explore the steps to configure and implement multiple SLA for same customer in Solution Manager 7.1 IT Service Management where single SLA is not sufficient.

Practical example would be a company/customer wants to have 24/7 support for SAP incidents and 12/5 support for non SAP incidents like hardware or IT Asset incidents etc.

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

Basically above signifies, the minimum configuration to have a properly copied transaction type (ZMIN/YMIN) which is having the relevant status profile and other configurations with master data in place.

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

  • SAP Tickets – assuming 24/7 support
  • Non SAP Tickets – assuming 12/5 support
  • Customer name -  assuming XYZ Corp India

(PS. Above are just dummy/Imaginary values and you can replace with with real values or as per requirement)

For SAP Tickets, the availability of support should be 24/7 i.e. 24 hours and 7 days a week. This means users can post ticket at any time or day and the response should be provided as per below agree criteria as mentioned in below table:





XYZ India


First Response By



To Do By




First Response By



To Do By




First Response By



To Do By




First Response By



To Do By



Table 1: SLA for SAP Tickets with 24/7 support

Please note: Timestamps First Response By and To Do By are for measuring the IRT and MPT respectively which are defined in the system for setting up the deadline.

For non SAP Tickets, the availability of support should be 12/5 i.e. 12 hours and 5 days a week. This means users can post ticket at any time during but support will be provided for 12 hours for 5 days within a week, excluding Saturday and Sunday.

The response or resolution for incidents should be provided as per below agreed criteria as mentioned in below table:





XYZ India


First Response By



To Do By




First Response By



To Do By




First Response By



To Do By




First Response By



To Do By



Table 2: SLA for non SAP Tickets with 12/5 Support


Let us start configuring the SLA as per our requirements mentioned in Table 1 and 2 with below 5 main steps in below sequence:

  1. Creation or Configuration for Service and Response Profile
  2. Creation of Product and assignment of Service & Response Profile
  3. Assignment of Service Products to Multi Level Categorization(MLC) & Sold to Party
  4. Configuration of SLA Determination procedure in SPRO
  5. Assignment of SLA Determination Procedure to transaction type


Step 1: Creation or Configuration for Service and Response Profile

First we need to create two different Service and Response Profiles in the system for XYZ Corp India customer. Therefore, logon to Solution Manager 7.1 system, now enter the transaction code “crmd_serv_sla” or follow the below SPRO path.

SAP Solution Manager Implementation Guide->SAP Solution Manager->Capabilities (Optional)-> IT Service Management-> SLA Escalation->Edit Availability and Response Times.

This will help us to configure Service and Response Profiles.

Click on Service Profile as highlighted in below figure and then click New Entries button as highlighted to create a new Service Profile.


Next step is to enter code (say ZSP), provide a description and then click on highlighted icon to maintain availability service timelines as per requirement for SAP Tickets/incidents. Thus, we create this one for 24/7 support.


Click on the highlighted icon will help to maintain the timelines or period. To maintain the service availability times 24*7 proceed as shown below.


Note: I am assuming all days are working here but it is possible to define our own Calendar (via SCAL transaction) which is very basic and easy for any Solution Manager Functional Consultant.


Further, click copy button as highlighted above then and save it.

On returning to screen or figure 2, again click new entries or repeat steps to create our second service profile for 12/5 timeline for non SAP Incidents/Tickets.

Once completed with Service Profile creation, we can now proceed further for response profile setup.

Next step is to configure Response Profile in the same transaction (crmd_serv_sla), so click Response Profile and click New Entries button.


Create a Response Profile ZRP and maintain a description. Choose Priority checkbox as shown.


Now click on Indicators for Response Times on the left side in above screen, which will change the right part of screen and we can maintain the priority values available in the system by pressing F4 as shown. Map all the priority values as requirement.


Once added from the figure 8, all the above priorities will be attached to response profile as shown below


Next for each Priority, we need to assign the relevant First Response By and To Do By parameter as per our Table 1.

Therefore choose Priority “1” as shown below and then click on Response Times on the left side of the screen.


Double clicking the Response Times node on the left side of our figure will open sub screen on the right part of same figure Maintain the values for two durations as shown below

  • SRV_RF_DURA – for IRT
  • SRV_RR_DURA – for MPT



Similarly, proceed for Priority 2, 3 and 4 by repeating above steps and maintain durations.


Similarly now we will create another Response Profile ZRP2 and maintain the parameter First Response By and To Do By as per Table 2 by repeating all above steps.

Step 2: Creation of Product and assignment of Service & Response Profile

Based upon example requirement for customer/company XYZ Corp India, we will now proceed to create 2 Service Products for SAP and Non SAP Incidents respectively. To create a service product, we can access the transaction commpr01, and this will open the below screen.

First, hit the search button in the Find Area.

Then a default SAP Service Product “Investigation” will be shown which is created via the Solman_setup – ITSM wizard. Double click to choose it and enter the change mode by clicking the Pencil or edit icon.  Further, assign the Service and Response Profile which will be empty initially.

Save it.

Similarly, we copy the above product using copy button to a different product by name Hotline and assign 12/5 Service and Response profile as shown below


Thus, we are now ready to move to assign them in Multi level categorization or step 3 as mentioned earlier in the blog.

We will continue in another blog with remaining or mentioned steps and its available now (Part3)

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


The following snapshots are used to demonstrate the  integration:


a) Launch Job Monitoring WorkCenter under solman_setup





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

define scope.jpg



c) Select scenario and navigate to Step 5.1

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

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

add jjobs.jpg


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

no jobdoc.jpg


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

jobdoc created.jpg


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


Lauch Jobdoc.jpg


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

Hello forum,


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


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


1888840 - How to generate installation keys in Solution Manager 7.1

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


LMDB stat screen




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


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


811923 - SAP Solution Manager Key

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

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


Anyone have more information about that last SAP note ?


Best Regards,


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


SAP also added steps for decommissioning in the latest Solution Manager 7.1 SP11 Operations guide. You will need access to the SAP support Portal to access the document. Here is the link to the guide and a screen shot of the location:




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

     a. IT Operator  composite role = SAP_TASK_INBOX_ALL_COMP

2. Enter Transaction SOLMAN_WORKCENTER in SAPGUI

3. Select Technical administration Workcenter

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



4. Select the Decommissioning Procedure and select Execute


5. Select Edit

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

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


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

     a. Automatic activities are completed by selecting execute all

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

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

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

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


9. Step 3 – Cross Application Clean-Up

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

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


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

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


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

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


12.  Step 6 – Landscape Management Clean-up

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


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


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

Hello all,


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


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


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


I am looking forward to hearing from you!

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



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



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



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






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



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



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



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

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

Over the years SAP has made huge investment in the Service Operations area of Solution Manager and the new version which is 7.1 today provides flexibility to all SAP customers to implement IT Service Management for entire SAP and non SAP landscape.


In my experience, this is a journey and we should not jump on it doing everything at the same time but rather go step by step to implement the various capabilities of IT Service Management in Solution Manager 7.1.


During several implementations for IT Service Management in SAP Solution Manager 7.1, we have come across a common requirement to have multiple SLA or Service Level Agreements for support.


This blog series will focus on detailed configuration or implementation steps for setting up multiple SLA based upon Multilevel categorization(MLC) or the different type of incident.

Basic concept of SLA

Service Level Agreements (SLA) are typically agreed by SAP Customer with vendors who provide support or services adhering to their requirements

Typically there can be various criteria for having different SLA requirements. For every customer SLAs can be different based upon business conditions or support requirements i.e. either service basis or for specific product basis etc.

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


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

  1. Service Profile and
  2. Response Profile


The basic concept are already explained in detail over wiki on below link

SLA Management - SAP IT Service Management on SAP Solution Manager - SCN Wiki


Just to add further over Service and Response Profile

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


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

IRT - Initial Response Time

MPT - Maximum Processing Time


Thus, based upon the actual situation, if we don’t see the incident IRT and MPT meeting then it is called as SLA breach or violation.

This has severe impacts based upon the contract between customer and vendor. We can build reports in Solution Manager to see the entire list of incident which are breaching IRT or MPT etc in SM_CRM transaction.

Typically, in my organization, we have seen several SAP customer’s going for a 24*7 ( i.e. 24 hours and 7 days working) support model or 12*5 (i.e. 12 hours and 5 days a week) support model based upon their specific support requirements with respect to region wise, SAP/ non SAP incidents i.e. category of incident or SAP Module wise like SD, MM, FI, etc. Therefore, it is very much possible to have a one customer who would like to have multiple SLA which means separate SLA for SAP tickets and other one for Non SAP Tickets.

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

Basically, the minimum is to have a properly copied transaction type (ZMIN/YMIN) which is having the relevant status profile and other configurations with master data in place.

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

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


Next blog is published now and you can check here

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


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






Right Click > Copy


Name of target application should be 'SOLMAN'



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



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




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


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



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



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




Now you need to create an Application, Ruleset, Decision table as you would create it for Support Team Determination. Instead of Component and Support Team in Decision table, use Category and Change Manager dataset; To configure application follow the steps mentioned in 5. CONFIGURATION IN THE BUSINESS RULE FRAMEWORK PLUS in the following link





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



In the Processing Parameters provide below information;\




PARTNER_FCT : Partner Function of Change Manager

FUNCTION_ID : is the one which we created in BRF+

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


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





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



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


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

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


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

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


Points to be noted during clustering:

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



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


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


Problems in clustering:

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


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


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


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


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


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


Hence plan your clusters properly considering multiple use cases.


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


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


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


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



SAP Solution Manager for both the LoB and IT


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


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

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

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

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

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


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


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


Also, walk away with information about:


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


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

Register Today


Photo by SAP

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

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


He says:

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


Register Today

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

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

Resolution: Look at the following link


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


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

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

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


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

Issue: bug in the code

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

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

Resolution: It has been discussed in the blog


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

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

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

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

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


Filter Blog

By author:
By date:
By tag: