1 4 5 6 7 8 25 Previous Next

SAP Solution Manager

368 Posts

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


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



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







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


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



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

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




Customizing Process for Selective Import


First you should go to the SPRO




Selective Import (not Status Dependent) IMPORT_SEL


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


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




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


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




Status Dependent Selective Import IM_STA_SEL



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






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



Step 1:




Step 2:








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


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


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



ZMMJ in E0014 Released for Import



ZMMJ in E0009 Successfully Tested



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



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




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




All suggestion and questions are more then welcomed

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


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







Source: SAP


Using this;

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

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


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





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




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


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

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

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




The Change Request inherits the title from the respective Task.


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


Functional Restrictions


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

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

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

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

  5) No distributed deployment

  6) No integration of Quality Gate Management

  7) No Roadmap integration

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

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

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

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

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

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

combinations of project types are defined in the customizing.

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


(Credit: SAP IT PPM presentation)


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





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





Just a few days ago, SAP released the new feature pack for SAP Solution Manager 7.1 by releasing SP10. Many of you might ask themselves what has been shipped and improved in this new release? In this blog I would like to give a short overview from a product management perspective.


* * UPDATE * *
More content and interesting blogs in SCN about the new features are linked in this document now!


Table of Contents


Integration of Central CTS Infrastructure

It was about time. The new central CTS infrastructure was already revealed some time ago, now it is the moment for prime time. With the latest support package, the new infrastructure is available to all our customers. The new infrastructure fully supports one of our focus-areas in Change Control Management which is "flexibility". By introducing two new entities, we can overcome existing limitations of the classic TMS, changed the way how transports are managed and implemented new features and functionalities that have been on the wish-list of many customers. In this blog I just want to highlight briefly what this new infrastructure is all about, how it works and mention some key benefits.


Two new entities: Transport Collection and Clusters

The two entities are the "Transport Collection" and the "Transport System Cluster". A Transport Collection is mainly a container for one or many transport requests that belong to a particular change. It does not make any difference whether they were all created in the development system of your ERP landscape or in any other system that belongs to the development cluster. So what is a system cluster again? Right! Important thing to understand: The system cluster is a new layer that is introduced by the central CTS infrastructure. It allows you to model dependencies on system level. The idea is to assign all system of a particular role together (e.g. Dev-Systems) that have a logical relationship in your solution landscape.


Let's take a simple example: Your landscape consists of SAP ERP, SAP BW and SAP BusinessObjects. Typically your changes require adjustments in almost all of the systems: A backend change in ERP needs a change in BW, in order to update and display the reports correctly. Also the iViews in the Portal need to be updated, so the data is retrieved correctly after the change in ERP.


With the central CTS infrastructure, you can now have a change in ChaRM that has transports for all three systems - technically all of them are assigned to the transport collection. However, the transport collection is not shown to the end-user, as this shall remain a technical detail. Central CTS will make sure the import is done correctly for all the transports requests of the collection. Today a simultaneous import will be triggered via the system node automatically, which will trigger the import for all related systems as well. This helps to ensure that dependent transports that logically belong together are not forgotten or missed out, when moving a change through the system. On collection level, all transports are always referenced and assigned to the same change.




Flexibility with Released Transports and Handling of External Transports

Besides the mentioned cluster and collection entities, the infrastructure enables a completely flexible transport management. In the past, transport requests that have been "released" could not be reassigned to another CTS project. This made it impossible in ChaRM or QGM to remove them from a project and assign them to a later release. However, reality shows that this is exactly the kind of "flexibility" that is required in order to react on changing business demands and project situations. Sometimes shortly before the go-live we need to be able to react and decide whether a transport or change shall take part in the go-live or not.


This is where the new infrastructure comes into the game. By introducing the transport collection, and assigning the transports via the collection to the solution manager project logically, we don't need to change the CTS project on the transport if we want to reassign changes between projects or releases. This means we now really have the maximum flexibility on the technical transport layer - making it easy to inherit this flexibility upwards to the process-layer. From a process point of view, it is always easy to introduce new flexible processes, modify the workflow, insert additional steps - but it was always hard to also ensure the consistency on the technical layer. With Change Control Management in SAP Solution Manager and our tools Quality Gate Management and Change Request Management, we want to keep this link between the technical layer and the process layer. It is our goal to support you even in complex environments and provide you with a tool, that is capable of managing the transports this way. Now we really reached this level of flexibility and make the story come true.


Additionally we introduced the support for "external transports" - which means we are now able to take existing transports, assign them to ChaRM or QGM entities and move the throughout the landscape. Without modifying the original transport or taking  the content and re-packing it into a new transport. The use-case behind this feature is the following: Many customers get add-ons for their existing SAP solution from 3rd party service providers. Such add-ons are often delivered via a transport request file (which we call external request). However, in order to ensure that customers do not modify the add-on, this transport must not be changed or repacked in any way - otherwise the customer will loose the warranty. Service Providers mostly only provide warranty and services for the original package. In the past it was not possible to handle those kind of "external transports" with ChaRM or QGM, as they have already been released and we have not been able to manage them with the existing infrastructure. As mentioned above, the new infrastructure is also capable of handling released transports - thus delivering the basic foundation to allow a control of external transports not delivered from SAP, but any 3rd party vendor.


Interested in learning more about this new infrastructure and its capabilities?


The official online documentation is already available today on the SAP help portal. Also there is a detailed configuration guide available here in the SAP SCN. If you would like to get started today, also have a look at the SAP Solution Manager Ramp-Up Knowledge Transfer area on the SAP Service Marketplace: http:service.sap.com/rkt-solman


Enhanced Approval Management & Substitution Feature

With the approval management a key part of the Change Management process has been enhanced with SP10. In the past it was enough to have the proper authorization, in order to execute specific approval steps of an approval procedure.



Now we introduce the enhanced approval management which will make it possible to control quite detailed, who is able to approve: Only the person that is really assigned to an approval step can approve a given step - and only this step. Other steps cannot be approved by this person - as well as other users, that might have the approval authorization in general, cannot approve as well. Please see the picture above for an illustrated example.


In order to avoid bottlenecks in the process (e.g. an assigned approver is on vacation and cannot approve right now) we introduced a substitution functionality. By defining a substitute, people can make sure that their assigned approval steps can also be executed by this substitute. Of course, the substitute needs to have the general authorization to do approvals - otherwise it will not work.


Another feature that has been introduced now is the possibilty to assign business partner groups for the approval. A typical customer situation is the following: Instead of assinging individual people an entire group of people will be assigned to the approval steps, because only one out of the group needs to approve and it is not important who will do it. Maybe you have a group of change managers or system owners


The group approval feature does not work together with the substitute feature - because the group should be able to "substitute" for herself. Otherwise group-approvals and individual-approvals can be mixed quite easily within an approval procedure, as shown in the picture below.


Read more about this new feature, and how it works in this Blog from Michael Vollmer. Boris Milosevic has also published a blog about the setup of the group-approvals in particular: The Group Approval - PPOMA_CRM Org. Model -  CHARM SP10



New Import Strategy: Selective Import

Being flexible with the imports in Change Request Management was already a focus topic of Feature Pack 1 of SAP Solution Manager 7.1 (SP5). There we introduced already the "preliminary import" for Normal Changes, as well as the possibility to have a "status dependend import". Bundled with the downgrade protection features, this already increased the flexibility of the overall solution dramatically. Now we took the next step: Introducing the "selective import" which allows you to select freely what kind of changes or transports you would like to import.


Based on the import buffer of a system, the selective import strategy will show a popup window, listing all changes and transports that are waiting for the import. The administrator can then select, which changes or transports shall be imported. The main entity is always the change, as this should be a consistent unit in your change management environment. Only transports without a relationship to a change can be selected individually - otherwise always the whole change is "in" or "out".


There is also another blog in SDN available already that contains some additional customizing and configuration hints: New Import Strategy : Selective Import Solman 7.1 - SP10 (How To)


Integration with IT Calendar


When the IT is growing, more systems and people are involved, the management of all these different system, technologies is getting more and more challenging. With SAP Solution Manager, SAP would like to support you by providing a central calendar for your IT employees. In this calender they can find all required information about planned work modes, changes, project/release timelines and other IT events. The next step towards a true single source of truth.


With SP10 we enabled Change Request Management (and Quality Gate Management) for an integration with the IT calendar in SAP Solution Manager. This helps you to establish a real "Change and Release Calendar". Every Request for Change or Change Document can be integrated and displayed in the IT calendar. This will make it easier for Change Advisory Board meetings to check the planned/forward schedule of changes or publish a projected service outage plan for your systems to the end-users or IT personnel.


In order to configure this integration, there is a simple customizing report available. It will allow you to configure the integration more in detail: what should be copied/transferred to IT calendar, how shall it be displayed, ...


Some additional information and how-to descriptions can be found in this blog: IT Calendar and CHARM integration Solman 7.1 SP10 (How To)



Integration with SAP PPM


Change Request Management is now fully integrated with the project management (formerly known as cProjects) of SAP PPM. This means you can now link Requests for Change from ChaRM with associated project tasks in PPM. Relevant information about the task will then also transferred automatically from the task to the RfC and back. When your developers are doing time recording, the information is automatically summed up, then transferred and finally displayed agregated on the task.


The idea is to support the project manager by keeping the overview about his project and the different activities, without the need to look into the different changes that might exist. The information is available directly in his working environment. On the other hand, people from the project that work with the changes, don't need to go into PPM to report their working times or the status of the task. This can be done automatically via the RfC and change document.


Additionally you can benefit from the integration into the SAP ERP, that is supported by SAP PPM out of the box. As this is a quite huge area I don't want to squeeze it into this blog but rather plan to publish a seperate blog focusing on the integration and the features and highlights of it. Stay tuned!


In the meantime the community was active already - please find more information also in this blog: PPM Projects integration with Change Request Management in SP10


New Scenarios and Enhancements for Retrofit

You certainly don't need to establish a full Change Request Management implementation in your organisation, in order to benefit from retrofit (New for you? Read more in this blog from Hannes Kerber ). However, as retrofit was built based on the transport management infrastructure that is also used by ChaRM, I wanted to mention some of the enhancements also in this blog about the ChaRM related news. Still, retrofit is also integrated into the standard ChaRM processes and will make it easier for you, to perform and trigger the retrofit process directly from a change document.


With SP10 we released some new scenarios for retrofit that include also the support for BW as well as other custom scenarios. I plan to publish a seperate blog about the key benefits and functionalities this provides for our customers.


Pre-Configured Email Notifications based on HTML Mails


Notifications about new changes, activities that need to be done or other relevant information about a Change Document or Request for Change are vital for a good change management process, in order to avoid bottlenecks and keep the process flow alive.


In the past, customers had to implement those kind of notifications completely from scratch. Now SAP delivers some pre-configured actions and conditions within the standard workflows to setup such notifications. This will make it much more easy to configure and use the email notifications in the process. Plus there is now also support for HTML mails: Instead of using smartforms, you can now use HTML Mails (a general component from SAP CRM that can simply be re-used) to setup your mail templates - including a direct link to the document.


Enhanced Home-Widgets

The home-widgets that we introduced with SP5 for ITSM have been very well accepted by our customers. Soon after the release, people started to ask for support of ChaRM transactions for the widgets and additional configuration possibilities. I'm glad to report today: We have been listening!


The new home widgets are now available with SP10 and they are fully customizeable. Customers have now many many possibilities how they can include those widgets into their business roles. Of course, also the support for ChaRM entities like change documents or requests for changes is possible! The picture above shows the "My Messages" widget for change documents as an example.


Additional minor Usability and UI improvements

Finally we also did some general usability and UI improvements. I don't want to highlight all the small things, as I probably would forget something anyway - but I want to highlight at least two areas: Search and Status Overview.


The search we can see in the picture above: A whole set of new search criteria has been introduced. Moreover, the entire search for the ITSM scenario between Incident, Problem, Service Request and Change has been harmonized. The goal was to provide the same search criteria and the same initial configuration for all our standard transaction types - making it easier for customers and end-users to keep the overview.


Besides that we introduced the "Status Overview" assignment block to all ChaRM transactions.


It is not visible per default, but you can simply enable it via personalization now. In the past, this assignment block was only available for the change cycls (maintenance cycle or project cycle). We received great feedback - many of you appreciate this assignment block, as it directly shows in which status the document is, and what kind of other status values are existing - even though it does not really show the exact workflow-process that has been designed. Finally we decided to enable this for all our standard transactions, and leave it up to the customer, whether he would like to show it to their end-users or not. Of course, I still hope to have a real graphical view of the workflow sometime in future...let's see



Well, that's it with my little overview - I hope there is something you have already been looking forward to or you just enjoy the new features. If you are new to Change Request Management (ChaRM) and have been hesitant in the past, why wait? Now is the right time to get started. Get your SolMan on 7.1 SP10 and kickstart your ChaRM experience...


Related Links:


Join the SAP Solution Manager community here in SCN and explore our SAP Solution Manager space, to find out more or ask specific questions, exchange experiences with others or check for issue-resolutions.


- Tobias

The performance of a company's IT systems is crucial to its success - in any industry. Rapid response times and the availability of information at the click of a button have become a must.

This software tutorial shows IT managers how to use the root cause analysis capabilities of SAP IT Infrastructure Management to quickly identify and resolve performance issues.


SAP IT Infrastructure Management is a solution extension of SAP Solution Manager and was developed in cooperation with REALTECH. With SAP IT Infrastructure Management IT specialists are able to manage and monitor both applications and infrastructure with SAP Solution Manager.

SAP web page for more information: www.sap.com/ManageYourITInfrastructure

Discover all software tutorials: www.realtech.com/software-tutorials


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.


Filter Blog

By author:
By date:
By tag: