1 4 5 6 7 8 25 Previous Next

SAP Solution Manager

363 Posts

It is possible to change the sequence of workcenter's in Solution Manager IT Service Management as our requirement with customizing and no development is needed.


Let us see how we can do this.


Assuming, we have the below workcenter's assigned to IT Service Management Business Role(Say ZSOLMANPRO) as shown with HOME workcenter on Top and Service Operations as last one



In order to change the sequence, Kindly navigate to the below path



Choose the Business Role(Customized one or copy of standard role SOLMANPRO etc). Here we have taken ZSOLMANPRO for e.g. and then navigate to Adjust Work Centers option as shown below.



Note: Never modify standard Business Role or content delivered by SAP.


Now in order to override the default sequence maintain the required values in WC Pos. column.



Done with customizing or our configuration is complete.


Now enter transaction sm_crm in Solution Manager and we can now see the different sequence for all the work centers assigned to ZSOLMANPRO business role.


As shown above, the entire sequence is changed as per our requirement.


Kindly check my other blogs for other customizing options in the same series.

Quick Tip : Customizing Business Role in Solution Manager 7.1 ITSM Part 1

Quick Tip : Customizing Business Role in Solution Manager 7.1 ITSM Part 2

In this document you can find additional Auth. Roles/Objects which are not document by SAP and they are necessary for normal work with IT Calendar.



To be able to use IT calendar integrated with the CHARM features  you should perform customizing in SPRO like is presented in the  IT Calendar Customizing PDF document.


In my case Change Manager should have responsibility to maintain IT calendar from the SMMN document type.



then you will get Calender




Now you will be able to either  Schedule New IT event or to Schedule Work mode :




To Schedule an IT Event :







To Schedule an Work Mode




from this screen you can suppress Monitoring Agents like is presented in the below pict.








The Change Manager Authorization  Roles To Maintain IT Calender


Change Manager should have additional authorization roles besides his standard ones to be able to maintain IT calendar. In order to work with calendar CM should have below SAP roles:


  1. SAP_ITCALENDER_DIS with the slight modification like is presented in the below pictures
  2. SAP_SM_DTM_ALL with default authorization.




After you make copy to Z* role you should add additional  authorization object  SM_ITE_ACT







Make copy SAP role to Z* one.





If you have anything to comment or add pleas go ahead.

All suggestions are welcomed.

How to create organizational Model for the CHARM Approval Group in the  Michael Vollmer's Blog of the  New ChaRM Feature with SP 10: Enhanced Approval Procedure Functions  he did not explain how to create Org Model via PPOMA_CRM , therefore I would like to show  this simple process - to create Approval Group Organization!


To be able to create an Organizational Model you should first create Organization Model for the Approval Group type Organization.


Goto SPRO :



then choose valid time period for your organization:




in the next screen you should chose name of the approval organization in our Case will be following:



Approval Organization 1


After you created approval organization you should create new postion like is presented in the below picture with the steps how to create :


  1. Select current Organization
  2. Create new Assigment/Relationship
  3. Choose “Incorporates Position”




then choose new name in our case Org. Model 1



your current Org Model is ready to assign the members Holders!


Click on the Org. Model 1 and with the right Click (DropDown Menu) go to Assign





in the next screen choose Owner / BP




then you will get:




in the above picture you can choose one or more then one ember of your future App. organization. In our case will be 3 BP.




Do not Forget to SAVE before you leave the transaction.



Hope that helps, if you have comments are find errors, do not hesitate to contact me.

Hello community,

today I would like to describe some facts regarding the usage of SAP BPC (SAP Business Planning and Consolidation) together with ChaRM (Change Request Management) and QGM in SAP Solution Manager.

First of all we have to differentiate between two cases:
A) SAP BPC running on Microsoft and transport management done via CTS+ and
B) SAP BPC running on SAP NetWeaver where transport management is done via regular CTS.

General Information:

In order to work correctly with QGM/Change Request Management in both cases, some parameters have to be set correctly.

First of all the CTS-Project assignment has to be mandatory. This will ensure that only transports can be exported that have a CTS project assignment. Secondly the CTS status switches need to be set like the following:


Details for Variant A)

In Variant A) the following parameter settings need to be done:

  • CTS_System_TYPE = JAVA

The process will then work like this:

ChaRM (or QGM) will create a transport request. This transport request will be assigned to the responsible developer. The Developer will execute the development and the changed BPC objects will be assigned to the transport created before. This is a manual activity that needs to be carried out. Afterwards the transport can be released and transported via regular ChaRM/QGM processes.

Details for Variant B)

In Variant B) the story is a little bit different. Here we don’t have any additional parameters to be set – besides the general settings described above. SAP BPC currently does not support the assignment of already created transport requests, when trying to deploy new configurations and content in your landscape. SAP BPC will create own transports, bypassing the standard user interface and thereby the ability to select a ChaRM transport. Some customers of BPC and ChaRM have been unsure, how they should react on this. SAP Note 1638440 describes this limitation more in detail.

In general, SAP BPC is working fine with the SAP transport management system (CTS) and I would like to show you some possibilities, how you can also integrate SAP BPC in your ChaRM change management process.

What is the solution?

The solution is pretty straight forward: The only possibility to assign the BPC created transport request to a ChaRM project and to a Change Document is before you release the transport request. The “Assign Transport” functionality within a Change Document is available with Solution Manager 7.1 SP5.

You can simply access it via the Transport Management assignment block in a change document:scn_assign_TR.PNG

The following process will apply:

  1. Once the Development is done, TR generation will be triggered via BPC. BPC will assign the changed objects to this transport.

  2. This transport request needs to be assigned to related ChaRM/QGM CTS project. This happens either automatically, when using the “Assign Transport Request” functionality or can be done manually in two steps: first project assignment, then ChaRM/QGM assignment via task list.

  3. The transport is then added to ChaRM/QGM and controlled via the regular functionalities.

  4. ChaRM/QGM will then manage the further export/import of the transport.

General facts about transport management for SAP BPC 10:

  • BPC NW 10.0 will support the transport of granular objects to move any given BPC object from development system to QA & Production systems. In 7.x, customers were required to transport whole AppSet every time.
  • Customers and consultants will need to take into account dependencies to insure a logical sequence of transport imports when transporting an Environment's objects in multiple transports (negative dependency check will prompt a warning).
  • BPC objects can be collected to a transport using the BW Administrative Workbench (transaction RSA1) which uses the standard transport process already familiar to BW users.

What is coming in the future?

With SP10 of SAP Solution Manager, we just released a new infrastructure (central CTS) that is also capable of handling "released" transports. This will give customers a maximum of flexibility for their change management process.

When you use the new infrastructure, also released transports can be atteched to a Change Document. This will bring you additional functionality when it comes to management of BPC transports with ChaRM.

If you would like to hear a bit more about SAP's strategy regarding Change Control Management and the new central CTS infrastructure, check out this video with product managers David Birkenbach and Tobias Hauk from SAP TechEd Live in Amsterdam. Also there is now the official online documentation available for the Central Change and Transport System.

Now I hope I could shed some light on the topic and you are able to handle your BPC related transports now also with Change Request Managemet!

- Tobias

This blog is part of a series on how to control document changes in Solution Manager. Here, I describe how to pull together the release strategy and custom attribute for Solution Manager documents with an enhancement code that gives the document name a new version number. Please see the earlier blogs to understand how this function works.


What I've done is co-opted the technical name for a Solution Manager document (field IWB_TECH_NAME) which is always present in the general attributes tab. This technical name is not open for entry, it is only filled from standard documentation from a template project. The technical name is generated in the enhancement as a concatenation of the Document type, PMO ID and version number (released versions + 1).


It takes advantage of design of the KW database storage. The Logical Info Object (field SA01PHIO-LOIO_ID) is always the same, even between saved changes of the document. Not so the Physical Info Object (field SA01PHIO-PHIO_ID) which changes on every single save, creating a new info object. This internal versioning is transparent to the user and permanent (deleting the document in solution manager doesn't delete the physical info object, it only removes it from the structure)


The enhancement spot used is SOLAR_DOCUMENT_EXITS


METHOD if_ex_solar_documents~save_document.



    c_pmo_reference TYPE sdok_propn VALUE 'ZDEPT',

    c_vers_abbr(3)  TYPE c VALUE 'V'.



    wa_new_name TYPE sdok_propv,

         wa_doc_type TYPE sdok_propv,

         wa_srch_str TYPE sdok_propv,

    wa_version(2) TYPE n,

    wa_mod_attr LIKE LINE OF et_modified_attributes,

    wa_pre_attr LIKE LINE OF it_previous_attributes.



*  Only perform exit if document is released



  WITH TABLE KEY name = 'IWB_STATE' value = 'REVIEW'.


  CHECK sy-subrc = 0.



* Ensure only count versions of same document type.


  READ TABLE it_previous_attributes INTO wa_pre_attr


  wa_doc_type = wa_pre_attr-value.



* Get custom attribute with PMO reference ID


  READ TABLE it_previous_attributes INTO wa_pre_attr

  WITH KEY name = c_pmo_reference.

  CONCATENATE wa_doc_type wa_pre_attr-value '%' INTO wa_srch_str.



* Count number of released versions for same document type


  SELECT COUNT(*) FROM sa01loio AS loio INNER JOIN sa01phio AS phio


   ON phio~loio_id   = loio~loio_id

   AND phio~lo_class  = 'SOLARGEN'

   AND phio~ph_class  = 'SOLARGNSRC'

   AND phio~langu     = 'EN'

   AND phio~prop05    = 'RELEASED'   " IWB_STATE

   WHERE  loio~prop06 = wa_doc_type  " IWB_SOLAR_DOCUTYPE

   AND    loio~prop08 LIKE wa_srch_str. " IWB_TECH_NAME



* Move new name with new release number to IWB_TECH_NAME


  wa_version = sy-dbcnt + 1.

  CONCATENATE wa_doc_type wa_pre_attr-value c_vers_abbr wa_version

  INTO wa_new_name.


  wa_mod_attr-name  = 'IWB_TECH_NAME'.

  wa_mod_attr-value =  wa_new_name.

  APPEND wa_mod_attr TO et_modified_attributes.




Function modules SA_KW_RFC_IOS_PROPERTIES_GET using field (SOLARGEN-LOIO_ID)  and SA_DOC_DS_SHOW_DOCUMENT were used to design this code snippet.


With this enhancement to allow versioning, the Program Management Office is provided with an additional axis to locate with SOLAR_EVAL repaort  a specific document that complements the Project hierarchy (y-axis) and the Business process tabs (x-axis).


This blog is part of a series on how to control document changes in Solution Manager. Here, I describe how to configure a release strategy for the approval and subsequent release of documents.


When creating a document, the status will be IN PROGRESS. A release strategy for releasing the document should require an electronic signature by the author when moved to status REVIEW, and because the document can't be signed twice by the same person, another signature will be required to put the document into RELEASED (or DECLINED) status. Figures 1 to 3 show the expected process in Solution Manager.



Fig. 1 Change status from In PROCESSING to REVIEW.


An electronic signature is required from PKISLOFF



Fig. 2 Display document and then approve change.


An electronic signature is required from PKISLOFF2. The reject icon is at the bottom, where comments can be added.



Fig. 3 Comments can be display in history tab, by clicking on the Display comment link (row highlighted).

Electronic signature set up depends on two transactions, STRUST (Figure 4) and SSFA (Figure 5), details in IMG path SAP Solution Manager > Scenario-Specific Settings > Cross Scenario Settings > Digital Signatures > Signature Strategy



Fig. 4 Create an entry in transaction STRUST for SSF Standard Applications


Fig. 5 Add the standard  apllication in transaction SSFA for SSF SAPSECULIB (needs to be present at O/S level).


Note that although the use case I mentioned in the introduction to this blog series was for FDA regulated requirements, I'm not showing how to implement application PPPI which is designed specifically for that. These electronic signatures will just prompt for the user password to allow a status change to the document.


Now for the configuration of release strategies. The IMG path to follow is SAP Solution Manager > Scenario-Specific Settings > Cross Scenario Settings > Document Management > Strategy for Documents


Before I describe the configuration of the release strategy, let me describe what it is first. There are only two approvers, the author of the document (because the author once they have released it for approval, can not release it a second time e.g. for approval) and the reviewer. There are many document types  that will need approval, but I have grouped them into four major groups, Project, Functional, Development and End-user (see Fig 5).  In my release strategy, the reviewers are the team leader(s) for each group.


Document types.JPG


Fig. 5 Example grouping for document types to be used for signature strategy allocation


Thus in configuration, I will set up four pairs of release agents:


P_AUTHOR and P_REVIEW for Project documents

F_AUTHOR and F_REVIEW for functional documents

D_AUTHOR and D_REVIEW for development documents

U_AUTHOR and U_REVIEW for end-user/training documents


In this example, F_AUTHOR and F_REVIEW user signature strategy FUNCTION. In Fig 6 for configuration entries, a system signature is required, and as defined in transaction SSFA this is the user password.  The author F_AUTHOR has to sign the document before the reviewer F_REVIEW, and once both have done so the document is released.



Fig. 6 Release strategy configuration


The various statuses and sequence are define in the status schema, after which it must be assigned to the document types to group them as defined in Figure 5. This is found in the project standards project template.


Fig. 7 Project standards template define status schema for document types.


In this naming convention example:
Document types use Stat.Schma FUNCTION and this uses Signature Strategy FUNCTION
Individuals = F_AUTHOR, F_REVIEWER uses AuthGrpDS = FUNCTION

Authorisation object C_SIGN_BGR uses AuthGrpDS = Stat.Schma



One final word. If done correctly, release of documents using a properly configured release strategy automatically creates a workflow event (see Fig. 8).


Fig. 8 Output from workflow event logging transaction SWEL


Many people think this can only be generated from an enhancement point, but in the next blog I will show how we use the enhancement point to automatically calculate the next version number every time a document is released.


This blog is part of a series on how to control document changes in Solution Manager. Here, I will describe how to add a new attribute to a solution manager object using the Document Modelling Workbench (transaction DMWB). My truly inspirational fellow SAP Mentor Raquel Pereira da Cunha wrote a blog on adding custom attributes to objects in projects and solutions, but unfortunately document attributes cannot be created by that method, so some deep-dive into KPro is required!


First, a warning. Incorrectly using the DMWB can seriously effect the health of your system! See notes 436430  - Prerequisites for the Document Modeling Workbench and 350535  - Knowledge Warehouse - Modeling before you begin.


Now, a quick introduction into document handling in Solution Manager, as shown in Figure 1. Whenever we set up a project in solution manager, it always requires a Knowledge Warehouse root key, the KPro context in the namespace /KWCUST/ together with language and release.


Various areas are available in solution manager, specifically IWBASAP for the road map and IWBSOLAR for project documentation. The folders within these areas are known in Solution Manager as Projects. The documents we wish add additional attributes to are known in KW as info objects. Hopefully the information contained therein will be of some value as useful project documentation.


KW basics.JPG

Fig 1: KW components. Source: SAP


In Fig 2 below, I have circled the area for solution documentation in KW, namely IWBSOLAR, and expanded the node hierarchy to expose IO attributes. Right clicking this node allows a new attribute to be created, namely ZRESPONSIBILITY. This is new attribute itself needs some attributes defined.


1. Field name

2. Table name. I have found that the table has to be client dependent.

3. Check property. I use 02 which will provide value help if search help is used with the field.


Fig 2. DMWB IO attribute definition


The next step (Fig. 3) is to add the new IO attribute to the Physical IO class. I've defined the attribute as unique. The More.. option allows for grouping and sorting behaviors to be defined. Although of the attribute is 64 characters, searching is limited to only the first 42 characters.


Fig 3. DMWB Physical IO attribute definition

The end result will look something like Fig. 4 with a new attributes tab for documents, and the field name coming from the data dictionary definition.


Before After.JPG
Fig 4. A new attribute for documents


What's that? There's nothing there? Ah, I always forget. The buffer needs to be refreshed. Use transaction for contexts SE33 and specify IWB_SOLAR_PROPS. I refresh the buffers globally. In a few minutes the attributes should appear.



Fig 5. A KW Context buffer refresh is required before changes appear.

In the next blog, I describe how to set up a release strategy for documents that have been checked out.

In this series of blogs, I'll discuss a way it is possible to introduce change control for documents in Solution Manager. Good governance of project documentation is a fundamental underpinning of change control in regulated industries such as ethical pharmaceuticals ("Big Pharma"), but observance of its mandated requirements needn't be an exorbitant overhead. 


In this first blog, I'll describe the cascade model, and describe how versioning of documents together with electronic sign-off is the essential aim. To achieve this objective, there are three steps to take, all blogged separately as all show some aspect that can be used independently for lesser requirements.


Blog 2: Adding a unique identifier to Solution Manger document attributes


Blog 3. Introducing a release strategy with electronic signatures for signed out documents


Blog 4. Solution Documentation: Automatically attaching a new version number to the document after release


Fig 1: The V-model of computer validation


In so-called regulated industries such as ethical pharmaceuticals regulated by the FDA, there's a methodical, by-the-numbers approach to any changes to a qualified computer systems such as those licensed from SAP. Even if drug manufacture is not used in the system, simply being part of the corporate infrastructure means its strictures need to be observed.


The classical V-model or "cascade" approach has to be observed, and each stage signed off. After an initial scoping, the User Requirements (URS) have to be established, then these are broken down into function specification (FS) documents and from these any additional developments spawned are written up as system design specifications (SDS).


After development, the changes are tested against the signed off SDS, and so up up the other side of the V-model. Importantly, documents must have a new version that spells out the deltas that are to be tested. Don't start testing before the document has been signed off, and for heaven's sake don't test against the wrong version, otherwise it's all invalid and has to be repeated. It's not so difficult with the odd few changes, but in large teams across multiple overlapping areas with tight deadlines, things tend to grind to a halt pretty quickly.


With the scene set, the first thing needed in solution manager is something to link all the disparate documents to a change. I call this the Program Management Office reference ID (PMOID), a unique number that the PMO assigns every change request brought before it and approves, and is then used to collect all development  and testing documents for tracking into Production. Something similar would be used by every change approval panel I would expect.


In the next blog, describe how to add this PMOID to Solution Manager document attributes.



SAP® Solution Managers integrated Service Desk, Test Workbench, and test automation framework enables SAP customers to handle all aspects of test management more effectively and efficiently. SAP Solution Manager 7.1 adds visualized test reporting based on SAP BW reports.


Our consulting solution Test Management Cockpit extends the scope of standard functions for analyzing and generating reports across all test phases. It can detect functional gaps in the test design phase and identify deviations from the test plan. Plus, transparent incident management makes it easier to monitor software quality and thus contributes significantly to the success of your project.


We are happy to announce that SAP Global IT chooses Test Management Cockpit for professional test reporting and as a basis for QA Dashboards.


Test Management Cockpit works with SAP NetWeaver 7.1, which comes with SAP Solution Manager 7.1. But with NetWeaver 7.3 we deliver a complete new user interface designed with Business Objects Design Studio.



The scope of the reporting includes analyses in the following test phases:

  • Test Design
  • Test Progress
  • Defect Progress


The key figures defined in the Test Management Cockpit help you to improve the software quality, identify bottlenecks in the testing process, and increase the efficiency during a tight time line for designing and performing tests.


With the new user interface, test reporting is really fun. You have all BW functionalities such as filters and drill-down; report parameters can be easily modified and saved for future analyses.



With Test Management Cockpit for SAP Solution Manager, you gain full transparency over your test processes, lower your reporting efforts, and can analyze all key data at the push of a button.


Test Management Cockpit is also part of our Test Management Service (Package M). And by the way - Test Management Cockpit works fine with mobile devices such as tablets.



Feel free to contact me or our reporting mastermind Tobias Fickinger (tobias.fickinger@sap.com) if you need more information. There is a user manual available in form of an interactive iBook for iPad or PDF (currently German only).


Best regards,



After setting up the SAP Solution Manager 7.1 Monitoring and Alerting Infrastructure, you might decide to disable monitoring or switch off alerts during certain time intervals such as planned downtime or regular system maintenance. Technical Monitoring can react to the following types of Work Modes that are scheduled within the Work Mode Management or SAP IT Calendar application.


  1. Planned Downtime
  2. Maintenance
  3. Peak Business Hour
  4. Non-Peak Business Hours
  5. Non- Business Hours


Work Modes can be set up for Technical Systems, Hosts, Databases and Technical Scenarios. The configuration is possible at various levels within the Technical Monitoring set up steps. You can decide if you want to switch off complete technical monitoring or modify single metric thresholds of specific systems.


Level 1: Global Work Mode Configuration

You can maintain Work Mode Specific settings for monitoring during the monitoring setup on global level (Step 2.6 Work Mode settings). For each work mode, it is possible to define whether monitoring is enabled or not. This acts as a “global switch” for Monitoring.


For example, If “Monitoring Enabled “ flag is unchecked for planned downtime then for all Managed Objects Types monitoring and alerting is disabled when a “Planned Downtime” Work Mode is scheduled on the managed object.


Global settings final.PNG





Level 2: Template Level Configuration

In case, you decide that only auto-notifications/incidents needs to be disabled for specific work modes and specific templates then template level configuration is relevant. You can define whether automatic creation of notification or incidents is active or not per work mode on template level (Setup step 4 Template Maintenance – valid for System Monitoring only). Template level settings take priority over global settings.

For example, if you decide that monitoring needs to be enabled during planned downtime of a Technical System but only email notification should be switched off then

  1. In the setup step 2.6 global settings, ensure sure that “ Monitoring Enabled “ flag is checked for all work modes “
  2. For the custom template (Expert Mode), set the Auto Notification to Inactive status for only Planned Downtime. Refer to the screen shot below. If you need to make the Work Mode settings specific to Managed Object then template settings has to be set at the specific Managed Object level.

Template settings.jpg


Level 3: Alert / Metric Level Configuration

If you decide that only certain alerts / metrics needs to be disabled during a specific work mode then you could focus on metric / alert level work mode configuration. You can define whether the measurement of individual metrics is active or inactive per work mode on each custom template. Also, thresholds can be adapted to work modes. Alert level settings take priority over Template Level settings

For example, if you decide that the threshold value of “Average Dialog Response Time (last hour)“ metric needs to be changed only for “Peak Business Hour “ work mode then

  1. In the setup step 2.6 global settings, ensure sure that “Monitoring Enabled “flag is checked for all work modes.
  2. For the custom template ( Expert Mode ) - go to the tab Metrics and select the Metric “Average Dialog Response Time (last hour)“ and click on Change settings
  3. In the details for the Metric, go to the tab Thresholds.
  4. In the Work mode specific threshold settings, select the work mode from the drop down list and configure the threshold settings.
  5. After you have changed metric settings, save the custom template.
  6. Assign the custom template to a system as needed.


Alert settings.jpg


Related links:

EEM and Workmodes





Past two weeks had gone very perfect, there were couple folks from business directly connected us for using solution manager for ensuring security of the entire system landscape, it’s because recently they received the information about SAP Security patch process day.



SAP Security Patch process day- What it is?


Security is the very big concern in Today’s SAP environment; we can go for secure installation but without making constant maintenance this is become big challenge, we had recently heard from SAP about SAP Patch process day, it was very simple concept; it’s a one of the very good security strategy.


As per SAP guidance, we could consider every second Tuesday of the month as “Sap Patch Process Day”. It is not kind of release schedule. It’s just creating a much disciplined regular plan for checking the security notes, patch updates, latest releases.  It means, creating a dedicated day for checking security related information, review it with your landscape and take action.



SAP Security Patch Process Day – How it is?


With this feature, SAP provides clear workflow for security validation and also make us more discipline by without ignoring any latest security related notes.  We have to nominate one of our representatives to sap as security patch contact, later he will be the responsible person to set the “patch day road map” for the methods and tools used for ensuring security in our entire landscape.



Role of Solution Manager


Though we have some generic options for ensuring security like security note search, SAP Solution manager is the major tool. More over Solution manger act as central security check hub for security patch process day. Entire series of security checks on the entire landscape carried out with the help of solution manager.



EWA Reports!! Always Helpful!!


EWA report has the strong recommendation for security related suggestions, like parameter change, DB Patch information; OS level security patch suggestions, Details SAP security release notes, Password risk details and much more.




We could sometime ignore the importance of EWA, but security suggestions in EWA reports are very best approach to make our environment away from security breaches but other potential threats.





This helps to list the status of implementation very recent sap hot news released from active global support.  (Hot news are the top prio1 notes, taken consideration as system crash or major data loss ) .





Change Management- System recommendation


I really wonder, how many of the customers ignoring one of the very finest functionality in solution manager, this is very good feature and made it work and you can visibly see the advantage of missing sap notes in entire system landscape.  There are couple of blogs already available to list out its features. Solution Manager System Recommendations feature review




Configuration and validation


This is another feature integrated with solution manager, using this you can compare your current system landscape settings with the SAP Standard latest release/customized target release to get the list of corrections, notes you have been missing in your landscapes. More over it helps to make sure all your the system in your landscape at the same security patch level. Other way it helps for cross system security check comparison too. There are various comparison option available like compare against security notes, hot news and patch notes. More details available here





Security Optimization session

It is one of the expert guided session provided by SAP to directly asses the security of your landscape and provide suggestion for improvement, Its available as self guided services in solution manager. More details refer here.


Other SAP Code Exchange reports for Central Security check



Security Dashboard


Solution manager 7.1 delivers the most efficient and transparent security dashboards, This is available under cross application dashboard apps, we can add to our management dashboard view for display the status.






Interesting Reads


SAP Patch Process Day White Paper

SAP Patch Process Day Over view

List of Z reports from Code Exchange behind all functionality



Lets use all the above mentioned features with in solution manager and make the landscape more secure and safe.

Plenty of requests are pouring upon me or queries from our existing customer's related to upgrading Solution Manager from 7.0 to 7.1 with service desk or change request management(ChaRM).


In fact, similar sort of queries are coming on regular basis in the forum so I thought let me share some useful information, if you are planning to do the same.


There is a big change in terms of Solution Manager (older)7.0 to (new)7.1 version and therefore Customer's using Solution Manager Change Request Management(ChaRM) and Service Desk have to go for dual Upgrade i.e Technical Upgrade followed by Functional Upgrade.


Therefore, it should not happen in any sort of unplanned manner or without proper planning or insufficient resources.


A proper phased approach must be used to complete this task to accomplish it.


Initially, we must do a proper or detailed understanding of the current setup especially in case of Service Desk and Change Request Management(ChaRM) as these 2 are heavily impacted in the newer version(7.1).


Some of the facts or learnings:

  • Very painful in case of no documentation existing for functionalities implemented already


  • Technical Upgrade itself might struck due to inconsistent notes/open objects in SE80 transaction so check with ABAP Team to resolve the errors and activate all the objects shown as inactive.


  • A very good document from SAP which helps to get the picture of new features and do the scoping



  • Old SLD version causes a NIGHTMARE and creates bigger problems so better to upgrade SLD version first otherwise LDMB starts throwing many error during synchronization etc.


  • All the configuration w.r.t to Service Desk and ChaRM which was done in 7.0 version will still be there but of no or less use because transaction types are changed and based upon different Business Object itself

        for e.g Incident Management SLFN is changed to SMIN ....Change Request SDCR is changed to SMCR etc

        Make sure you just have one entry now for in Dno_Cust04 table for PROCESS_TYPE = ZMIN etc and no values for PROCESS_TYPE_ADD or else                  you landed up with pop up asking you to choose transaction type


  • Post upgrade you might see - NO Multilevel categorization - this is a very common issue because in new version we have to configure it differently.Run the report AI_CRM_CREATE_CAT_SCHEMA to resolve this issue and can also refer detail guide here



       Once you have activated the standard MLC, it will be shown as below in SM_CRM transaction or the new interface in Categorization Schemas




  • There is new concept of Business Roles and unless configured properly it allows full access to all message processors like change manager, incident resolution team etc



I have recently published few blogs on the same which can be referred



  • Also, You might see that Risk field is empty - Refer below IMG path



Similarly, Urgency and Impact field might be empty.



  • Another big issue might be even you do all this customizing and setup the Project doesn't show up in the new interface or PROJECT Field


  • End User liked the IT Service Management a lot and happy to move a away from SAP GUI Interface to a new Web Based Interface but authorization management has to be properly configured via PFCG roles.


  • Maintenance cycle for ChaRM gets corrupted - There are lot of notes so check SMP


  • If customer plans to go for Non SAP Components - For Non SAP its a big challenge as there is not much documentation on the same and to implement for non SAP you need to create additional entries in SLD for system which replicate in LMDB and then create IBASE for Non SAP component to enable incident or Change to be posted on it


  • In short, things completely changed and need to have a good knowledge on SAP CRM UI Framework which is entirely different from SAP GUI. To Make fields mandatory/hiding its now just simple clicks instead of coding in SAP GUI which eases the task but needs to be familiar with it


  • There was an option of Multiple search for incident or service desk tickets in crm_dno_monitor in 7.0 version of Solution Manager and if interested on how to do search for multiple tickets at one go check below SAP KA. Thus it is still supported only the way of doing it changed

1918499 - How to multi-select in Web UI - Solution Manager IT Service Management


In addition, do check the wiki and Service Marketplace(Installation and Upgrade guides section)



Some useful notes

1677520  - Time Recording: Possible Data Loss on Upgrade

1613908  - Old Transaction Types in SAP Solution Manager 7.1

1779203  - Is Non-Unicode Solution Manager supported when Upgrading to 7.1?

Hope this gives you some good insights and all the best for the Upgrade

Today, SP10 is available! And here's about some new feature:


Starting with SAP Solution Manager release 7.10, the approval procedure assignment block from CRM standard was integrated, enhanced and used in the Request for Change.

The approval procedure allows customers to use an "approval workflow" that is executed during the Request for Change process. Customers can define several different approval procedures -  each approval procedure consists of one or many approval steps. Each approval step has a name, as well as a target business partner function, that is supposed to execute (meaning approve) this step (e.g. Change Manager, IT Operator, ...).

Customers can specify whether all the steps will be active for approval in parallel, or whether the approval steps have to be approved in sequence.

If the approval procedure is started, approvers which have to take action get notified via email notification  using a Workflow item. The email contains a link in order to access the document and execute their approval step - once all the steps are completed the entire document is set to "Approved", "Rejected" or stays in "To be Approved" (only if all approvers choose 'Not Releant').


Some approval procedure example:approval procedure example.png


Additionally, it is possible to set a default approval procedure or prefill the approvers with the relevant business partners via rule policies...the SAP standard delivers for the Request for Change (transaction type SMCR) here two rule policies, the first one setting the single delivered standard approval procedure as default approval procedure. This delivered approval procedure has only one approval step. The second rule policy fills the business partner entered as change manager as well into the approver in this approval step.

rule policy example.png


But...the authorization concept provided by CRM standard is limited, it just checks for a special authority object (CRM_APPRVL) to approve an approval step.

If the user has this authorization object assigned, then it is possible to approve each step, independent if the user's business partner is entered as an approver, or not. This 'open' approval concept is a feature from CRM standard but it is not feasible for most of our ChaRM customers.

old crm authority object.png



CRM standard had no improvement in this area on the scope for future releases. You can check Karthik Paramasivam blog which has a part that discusses/states this, too.



The ChaRM team was aware that this was a pain point and implemented some enhanced features for the approval procedure. After a SP 9 pilot phase with selected customers, these features are now released with the coming Feature Pack, technically SP10.

The new features have to be manually activated in the system by an IMG activity. But this is the last step you do after prerequisite customizing is done which is explain further on:

activate switch.png

Please be aware that there is an error in the IMG docu. The User Name of the customizing entry in the view should be space not '*' !!!

The new features of the enhanced approval procedure functions are:


1.) Enhanced authority concept with a new authorithy object SM_APP_AP

to control the enhanced approval procedure authorization features of specific transaction types (defined by the values of authorization field AIC_PROC):

  • Change the assigned approval procedure (activity 02 Change)
  • Approve an approval step where your business partner is assigned as approver (activity 37 Accept)
  • Delete an approval step  (activity 75 Remove)
  • Add an approval step  (activity 22 Enter, Include, Assign)
  • Administer (Power user: activity 70 Administer): do all above and approve other business partner's approval steps 

authority object.png

Attention: First it has to be stated that the authorization concept from CRM will only be enhanced so it restricts further. This means if CRM approval procedure logic already forbids a function it will not be allowed or overwritten by the enhanced approval procedure features.

Example: You can control if a user can add and delete an approval step via the new authority object but when you save the document after adding a new approval step, CRM standard might not allow the deletion of the step again. In this case, we do not allow it, either.


How it looks like:

In case your user does not have the authority to execute a function in the approval procedure, the buttons (delete, add) are inactive. In case you are not allowed to approve an approval step or change the approval procedure assignment, the fields are switched to display mode.

authorities show case.png


Delivered ChaRM standard roles and the new authority object:

Role SAP standard rolesActivity for
Power User, AdministratorSAP_CM_SMAN_ADMINISTRATOR70 (administer), 37 (approve) approval step, 75 (delete approval step), 22 (add approval step), 02 (change approval procedure assignment)
Change ManagerSAP_CM_SMAN_CHANGE_MANAGER37 (approve) approval step, 75 (delete approval step), 22 (add approval step), 02 (change approval procedure assignment)
Potential Approvers




37 (delivered inactive)


Using this feature:

1.) Maintain the authorizations with your roles or copy the standard roles if you start anew.

2.) Activate the enhanced approval procedure features


2.) Substitute a business partner


This part was available already in the Incident Management area and now has been integrated to the Change Request Management area.

The business scenario is that the business partner assigned to the approval step might be not available because he is on vacation, on travel, or got sick, etc.

Now it is possible to define a substitute for this business partner or define for whom you substitute. The dialog window is reused from the Incident Management area which means the substitute you define is as well defined for the Incident Management area :

manage substitutes.png

substitute pop up.png

Now, only the business partner entered as approver and all of his substitutes (and the power admin user) are able to approve the approval step.


Note as a prerequisite the user needs authority object 'SM_APP_AP' with activity '37' and the current transaction type in his role).


Currently, SP10 has one restriction in this area. The email notification which is executed to inform all approvers when an approval procedure is active, does not inform the substitute. We hope to close this gap with a future support package/release.


Using this feature:

1.) Maintain the authorizations and roles

2.) Activate the enhanced approval procedure features


3.) Maintain organizational units as approver

Some customers have not just a substitute but a special organization, meaning circle of approvers, which approves changes in the landscape. For these customers now it is possible to create an organizational unit in the org model and then assign this business partner of type organization as an approver.


First, you create your organization in PPOMA_CRM and assign your business partners which belong to the approval group.

org model.png

Then, after the authorizations are maintained and the enhanced approval procedure features are activated, you can assign organizational units as approvers.


Currently, SP10 has one restriction in this area. The email notification which is executed to inform all approvers when an approval procedure is active, does not work for organizational units. We hope to close this gap with a future support package/release.


Using this feature:

1.) Maintain the authorizations and roles

2.) Create the org model with the organizational unit and the assigned business partners

3.) Activate the enhanced approval procedure features



General Restrictions:

Substitute and organizational unit as approver do not work together. It's not allowed to substitute an organization with a business partner type person or other organization.



Hope that helps, if you have comments are find errors, do not hesitate to contact me.

If you work with Solution Manager 7.1 ChaRM or Incident Management, you know you can have different Web Client Business Roles which can be personalized by the users and also pre-personalized by the Administrators. In the Home page of a Business Role there are some content blocks which can be displayed or hidden by the business role administrator, so that they will be available or not to all users assigned to this Business Role. Once a content block is visible by default, users can personalize the Home Page and hide it if they want.


One of the Content Blocks of the Home Page is called IT News. IT News is a content block for Favorites Web Links that can be personalized by the users (each user can create his/her own list of Favorite Links) and by the Administrator (all users assigned to the Business Role will have the links available).


First of all, in order to see the IT News Content Block, the Business Role you are using must have been configured to show it. This configuration can be done in two levels: in the personalization of the Web UI for the user, and in the IMG configuration for the Business Role.


Open the Home Page and check if you see IT News besides My Saved Searches, My Open Task, Favorites, etc. If you don’t see it, click the Personalize button to personalize your screen:



Select one of the empty content blocks available, click the listbox and select “IT News”.  Save.

personalize itnews.jpg


Now you will see the IT News Content Block in the Home Page.


This block can be populated by each user and by the Administrator. In the case you just want to have your own favorite links, just click the Pencil icon in the IT News Content Block.



Add new links.


If the Administrator wants all users assigned to this business role to see a list of Favorite External Web Links, then it’s necessary to perform some IMG activities. These IMG activities will be saved in a transport request and can be imported into your Solution Manager Productive System (unless you only have a SolMan PRD, and not a DEV,or a DEV and a QAS. If you only have a PRD system, which is not recommended for those who use ITSM, then you will need to configure it directly there.)


Go to SPRO->Customer Relationship Management->UI Framework->Define Web Links:



In this activity, you will create a group of web links to be used in the Business Role. One Business Role can have one group for IT News, but one group can be created for one or for more Business Roles, so if you want you can reuse it.


First create the Web Link IDs. In the example below I created a new Web Link ID for SAP News:



Now, create a Group ID for External Links and assign your new link(s):



Assign the external web links to the group and save your changes:


Go to SPRO->Customer Relationship Management->UI Framework->Business Roles->Define Business Roles:



Select the Business Role you want to edit and, in the left panel, select Function Profile. Click New Entries to create a new line, and insert "EXT_WEB_LINKS" with the Profile Value that you just created (the Group ID). Save.




Go to the ITSM Web UI (transaction SM_CRM) and check the Home Page for the Business Role. You will see the link created for all users and your personal link:


In continuation to my previous blog on the Business Role customizations


Quick Tip : Customizing Business Role in Solution Manager 7.1 ITSM Part 1


let us explore some more options of customizing Business Role.


Let us say, we have implemented only IT Service Management without Change Management for a customer. In this case, it is not required to show all the possible search/Create options in CRM UI or IT Service Management interface.


To hide all the other workcenter in SM_CRM or CRM_UI transaction, navigate to SPRO in solution manager and navigate to below path.


SPRO->Customer Relationship Management->UI Framework->Define Business Role.



Now click on Define Business Role, choose the custom Business Role which is created earlier or copy of standard business role like SOLMANPRO or SOLMANREQU etc. Kindly do not modify standard Business Roles.



Double click the Adjust Work Center option here and unchecked the SM_CHANGE Workcenter in the Inactive MENU column as shown



This will remove or hide the Change Management workcenter in the SM_CRM or IT service management interface as shown below.



Thus, we have successfully able to hide the unwanted workcenter. In addition, we can do the same for Service Operations Workcenter/Master Data workcenter if we don't want to provide everyone this access.


But if we look closely we still have Request for Change under the CREATE Shortcuts.


Further, to hide/remove the Request for Change direct creation link from the CREATE Shortcut.Double click on Adjust Direct Link Groups and choose SM-CREATE option as highlighted below



Now unchecked the Visible tick from SM-CR-DC link which is the shortcut for Request for Change.



Finally, Change Management is completely gone from IT Service Management interface as shown below.



Similar way, we can hide other unwanted links or workcenter easily from our custom Business Role.


Please Note: We are just hiding and user's might be still having authorization to create Change Request so check PFCG authorization's as well.


Filter Blog

By author:
By date:
By tag: