I am sharing common issues faced while implementation of charm in SP12.


1. Normal change had status "In development" if it created from the RFC.




ZMMJ_ON_CREATE_MJ : Define the statuf value in the condition for this action.


image 2.PNG


2. Partner id is not visible in Charm approval procedure even after creating the policy.


You need to create the rule moduler profile and assign it here.



go to Service manager profiles


Copy as this profile in your own name



Give the service id as SRV_REQ_RULE_EXE



In the properties tab, assign the policy that you had created in rule policy through web ui


3. while extending the scope, release for approval is not visble.

Check the action release for approval and insert the status value and set the maximum value accordingly in the action defination.





Hope it will be helpfull.



Rishav Garg




Let’s share our thoughts on how to make a successful ITSM / ChaRM project!


For 8 years, I’ve done many of these, for small, medium and large SAP implementations and I’ve found that some key steps are always essential to guarantee the project success:

  • Define the improvements expected from the project and don’t forget to use TEA (Transport Execution Analysis) to detect hidden flaws in your change and release management process
  • Keep your ITSM / ChaRM solution simple and as close to the standard as possible
  • Take advantage of the project to align your release management process to SAP best practices
  • Don’t underestimate the change management aspects of the project
  • Don’t just test ITSM / ChaRM processes and define tests plans for the most complex scenarios of your change and release management processes
  • Make your training documentation as simple as possible
  • Start preparing the Go Live at least two weeks before the actual Go-Live date
  • After 6 to 9 month, measure the reality vs the expected results with TEA

In this blog, I will describe in detail, by project phase, why all those steps will guarantee a successful ITSM / ChaRM implementation. I've divided it in two parts, the next one will be published soon.

1. Project preparation


A customer has decided he needs to implement a change and release management tool and chose ITSM / ChaRM. He has defined his objectives, the expected ROI and the area where improvements are expected.


However, there is always a gap between how we think a process is executed and how it is really used on a day to day basis. Such gaps can lead to actual problems (regression, extra work for the development team, etc.). They should be identified before the project starts or its benefits might not be as high as planned.


To identify those gaps, SAP provides, in SAP Solution Manager a report called TEA (Transport Execution Analysis). It measures a list of predefined Key Performance Indicators to evaluate how your change, test, transport and release management processes are really executed.


It is very fast to run and you would be surprised by what we find. Here are some of the findings we made with some of our customers:

  • 60 dumps every day in average on a production system
  • 40 objects overwritten in production by an older version on a 6 months period
  • 800 transport requests opened in development for more than 6 months
  • Etc.


This report gives you a quick and clear understanding on where your efforts should be focused and what should be done to improve your IT processes.



2. Solution Design


This step is essential as it will determine how the solution behaves. My best advice, keep it simple and try to stay as much as possible close to the standard processes. It will make your life much easier in the future!


Keep it simple!

Each additional step, field or validation in the process makes it less flexible and will slow it down. Don’t forget that it will be used every day by your organization and that complex solutions requires a lot more training, which can be problematic when new employees arrive or a new partner starts working on a project.


Always think, before adding a new element,

  • Is it really necessary?
  • Can it create bottlenecks?
  • Will it increase the workload of your team, or even worse the workload of key members of your team?


Stay close to the standard processes

As for all SAP solutions, the further you get from SAP standard processes, the harder it will be to maintain and upgrade it.

Adjust ITSM / ChaRM processes to your organization but make sure you understand them well before making any decision. They are based on ITIL best practices and are designed to fit most IT organizations requirements.


Don’t be shy and align your release management process to SAP best practices

One of the thing that is usually overlooked is the release management. Any change and transport management tool will have an impact on the way you manage your releases in SAP. So don’t be shy and use this opportunity to align your release management process to SAP best practices.


Lately, SAP has produced some really great documents on how you should manage your tests, how you should bundle your changes, how to categorize changes, etc. Use those documents and make their principles yours.

It will make the difference between a good ITSM / ChaRM solution and a great one that optimizes the change and release management processes by reducing its costs, the time to market and the incidents in production.


To be continued in my next blog...

In this blog, I will show how to report in CRM_UI (SM_CRM) based on a new custom UI field created in AET. This is using SolMan 7.1 SP 11.


The requirement was to add a new field to the Request for Change (ZMCR) UI and allow the new field reportable in the Search Criteria.


To add the new custom UI field, I followed the steps in this post, so I won’t go into those details.



The requirement was to enable the new custom field to appear in the Search Criteria in SM_CRM here...



Tcode SM_CRM.  Confirm you have Configuration mode checked and select SAVE....



Select Change Request Management -> Requests for Change...



On the Search screen, select Show Configurable Areas…



Highlight the Search Criteria section and select…



If a Z Configuration Area does not already exist for the selected area, create one…




Select the Component Name to copy and COPY…



Confirm you are maintaining the Z business role.

Change the Usage, Type, and Subtype to <DEFAULT>. Select CONTINUE.





Select the newly created Configuration Area.

Locate the custom field that you want to show in the Search Criteria in the list of Available Search Criteria.








...error “500 SAP Internal Server Error - Exception condition “PROBLEM_WITH_QUERY raised” appeared…




In my case, I found that this error was caused by the enhancement generation not entirely completing when the custom field was added.  The new field was not found in table CRMC_REPDY.


To resolve this error, in tcode AXTSHOW, I needed to manual re-generate the enhancement.


Before re-generating, the high level was green, but the Appends and other objects were not active. I selected Generate Enhancement to complete this step.




After re-generating,  the new field was successful….




This caused the field entry to be created in table CRMC_REPDY…




Now, new field is reportable in SM_CRM…


If you use Technical Monitoring in Solution Manager 7.1 you should be aware of the Event Calculation Engine. The job is essential for the Monitoring and Alerting Infrastructure. If the job is not scheduled, no status and alert calculation is performed. It calculates monitoring status, Events and Alerts based on received Metric Instances and Event Instances an configuration information stored in the Alerting Directory. Especially it allows event correlation and propagation but also calculation of events.



You can schedule the job in the SAP Solution Manager configuration (transaction SOLMAN_SETUP) by
performing the following step: "Basic Configuration" -->"Configure Automatically" --> "Create Alert Calculation Job"


By default, the Event Calculation Engine runs once per minute within the job



The ECE is responsible for calculating the current status based on central configuration:

  • Calculates rating for metrics based on the metric thresholds
  • Calculates the event rating based on the contributing metrics and event rules
  • Writes the current status of metrics and events to the Event + Metric Store
  • Provides the events to the Alert Consumer Connector
  • Does its calculation based on categories (Availability, Performance, Configuration
    and Exception).





1) Is the Event Calculation Engine Job running and performing?

You can find the corresponding check in Self-Monitoring under the component Event Calculation Engine - Status of the Alert Calculation Job.

The Event Calculation Engine job runs every minute under the name SAP_ALERT_CALCULATION_ENGINE
(if not changed manually), which calls the report ACE_CALCULATION_CONTROLLER. The Self-monitoring checks whether the
job had been started in the last minutes. If it has not run within the last two minutes, the status is red.


If the status is not green, you can check the following:

The job is not scheduled: Schedule the Event Calculation Engine job in the SAP Solution Manager
configuration (transaction SOLMAN_SETUP). Configure the scenario Solution Manager Self-Monitoring in Technical Monitoring,
and go to Configure Infrastructure --> Configure Automatically, which contains the activity Create Alert Calculation Job. Switch to change
mode, select this activity and perform it, with Execute Selected.

The job is delayed or did not finish: The job is scheduled, but ran late, because there was insufficient background processing capacity to run the
scheduled jobs on time. Check the job log in the Job Overview (transaction SM37), and provide
more work processing resources, if necessary, e.g. by increasing the number of work processes.



2) Are there error messages for the Alert Calculation Engine?

If the status is not green, analyse the error messages in the Application Log, as follows:

  • Start the transaction SLG1, and enter the object E2E_ALERTING and sub object ENGINE.
  • The logs are ordered by job executions, error messages are highlighted in traffic light
  • Expand the runs in which errors occurred; and expand the rows by
  • The messages of the job run are displayed at the bottom of the window. Display the
    error message long text.


A solution is usually proposed,as well as the cause of the error. Proceed according to the text.



3) Are Housekeeping jobs running?


The housekeeping jobs have no direct impact on the MAI, but the performance of the engine job is
affected, if the housekeeping jobs are not scheduled.





If you do however experience further performance problems with the Event Calculation Engine please review the following SAP notes:

1964945 - Extended wait time for enqueue for BI reporting in Event Calculation Engine

1928160 - MAI: Optimizing the performance of event calculations

2014552 - MAI: Parallelization of Event Calculation for Better Performance

2021463 - Composite SAP Note, corrections for "Event Calculation Engine" SP12

2068288 - Long Runtime of SAP_Alert_Calculation_Engine Job in Technical Monitoring







The present blog is the result of the effort of our Solution Manager Technical Team, that working in different areas made this simple solution available to our user community.  There is no big secret behind this, but there are so many presentations SAP has in which they say it is possible to forward ITSM incidents to SAP, but after some weeks we could not find the easy way to do it and all the elements that are required to have all the pieces working like a Swiss watch.


Following our sense of sharing our experience as it flourishes, below you will find it all grained ready and ready for baking.



1.  There is an Assignment Block hidden in the ITSMWebUi, called SAP Collaboration.  You have to make it visible selecting Lazy or Direct.



3. You need to enable the transaction type actions that are relevant for this service.  Some are already activated, some others not.  Via transaction CRMC_ACTION_DEF select the transaction type (ZMIN  or ZMRQ) and activate the services below:




The actions above cover a wide range of activities related to the incidents opened with SAP.    For this particular blog, we are not going to deal with actions like Opening system for SAP or Maintain SAP Logon Data.  Although they are related to the topic per se, the goal here is to show how we can enable functionality.  Those mentioned actions are more Basis related and authorization and security may be involved to actually control who can perform them, as well.


4.  Behind the scenes, the processing of all requests uses the RFC (Remote Function Call - for the non-Basis folks), SAP-OSS.  That connection should be always enabled with a SAP marketplace user and its correct password there.



The connection test must be successful.  If it fails, coordinate with your Basis support.   On the paper, the SAP support user being used in the RFC should be an anonymous account with its correspondent associated user in the ABAP stack of your SolMan system.   That latter is recommended to be an account type System or Service, which password does not expire.   The reason for the match between those 2 accounts will be explained further down.



5.  All the users who regularly create incidents directly in the SAP marketplace, including the anonymous account should have an entry in the SAP Reference IMG > SAP Solution Manager > Technical Settings > Assign S-User for SAP Support Portal Functionality.



6.  With that in place you are all set.  The following screens will tell you how to create the incident and get the replies from SAP.


6.1 Create an incident as usual.   Important is that you add a description, which may not be mandatory for internal incidents, though no logic.


Remark:  You can also add attachments in the respective assignment block?


6.2.  If the incident is to be sent to SAP support portal, you will find in ITSM a new assignment block in the incident called SAP Collaboration.   Click there and the button Sent to SAP.



6.2  From then on, a process similar to the one you also followed when you had to open incidents in the SAP support portal.  You will need to proceed one by one through the screens, being aware that in many cases you do not have to worry about some empty fields.  The solution internally complete most of them as you move along.



6.3 For the screen below, what is most important is the system data and that is automatically entered due to the fact that in the moment the incident was created, a component was to be selected.       Provide any additional information that may help SAP to properly identify your system.  We only provided the basic part and that is sufficient.



6.4 For the next step, the system internally checks that the user creating the incident, has a S0* account in SAP service marketplace or in  SolMan's view V_AISUSER (or SPRO > SAP reference IMG > SAP Solution Manager Implementation Guide > SAP Solution Manager > Technical Settings > Assign S-user for SAP support functionality).   If you regularly create incidents in SAP support portal, we have taken care of your account, long time ago.    This was explained already in step 5.


Green means okay, whereas Red, means either the sapgui account used in ITSM has not been associated in the table referred above with a S-user account, or the sapgui account being used in ITSM does not have a S-user account at all requested in SAP support portal.   If there is an error on the screen bellow, consult your SAP Basis provider.



6.5  For the following screen, you are prompted to provide the specific SAP component at SAP that this incident should be associated with.  In other words, the team at SAP that you think should take care of this incident. Also, proceed to provide a priority to the incident, which may be different than the priority given to the incident in the header when it was originally created.




6.6  Provide any additional information that you think is important for SAP support to now.  This is not mandatory and you can skip it by pressing Next.



6.7  If you are satisfied, submit the incident to SAP, otherwise press the Previous button and review again.



Any errors when you submit, contact your Basis Team.  Most likely an issue related to RFC SAP-OSS.

6.8  In case the RFC connection is correct or was corrected, the result after submitting the incident should look like below.


As you can see, incident at SAP is 48869.



6.9  Additionally change the status of the ITSM incident to Sent to SAP, so that the requester is aware of the status of their incident.


6.10  The behavior in the background is exactly as if you had created the incident directly in the SAP support portal.  You do not need to do the step below, but it is just FYI.   You can open the incident at the SAP support portal and see that even the attachments of the original ITSM incident are also found there, as expected.



6.11  From then on, you are already familiar with the processing.


SAP eventually will place the message in Customer Action.  Further down we explain an automatic process to feed ITSM from SAP support portal, but you can individually check if there is an update from SAP for your own incident.  In the same Assignment Block SAP Collaboration, press the button Update from SAP.



6.12  If you see that the incident is in Customer Action, the reply from SAP has been included in the Assignment Block Text, and if they submitted attachments they will also be found in the respective Assignment Block, as well.


Reply from SAP with attachments:



6.13  If you are satisfied, you can proceed to Confirm the incident for which you press the button Confirm at SAP, or you can go back and Send to SAP for further actions.   After you confirm, you can even complete the survey from ITSM.  What else do you need!!!



7. Q&A?


7.1 Is there a way to automatically feed ITSM with the replies from SAP, instead of having to individually press the button Update from SAP at each open incident?

Answer:  Yes.   There is a program you can schedule for that to run every 5 minutes.  The program is AI_CRM_IM_UPDATE_FROM_SAP.   If there is a change found a the support portal for any incident in progress, the ITSM SAP Collaboration statusof each ITSM incident affected changes from Sent to SAP to Customer Action, and the ITSM incident's header status changes from Sent to SAP to In Process.  That action should trigger an internal email notification so that the incident processor at your company gets notified that an update from SAP has arrived.


That process or activation of that notification is well documented in: http://scn.sap.com/docs/DOC-35291


Important to say that the email configuration is optional, and it is based on events. The PPF actions that trigger the email are based on a scheduling condition

and a start condition.   The notifications are not triggered directly by AI_CRM_IM_UPDATE_FROM_SAP, but by the subsequent status change affected by the that program.


Recommendation.  Search in the marketplace for the program and apply all missing notes you have with regards to it.  There is a huge improvement SAP has done to that report over time, so you better dance with the latest and avoid unnecessary troubleshooting.


7.2  What about incidents we already created in the SAP support portal?  Can they be imported into ITSM?

Answer:  Yes, they can.  There is an option in the program AI_CRM_IM_UPDATE_FROM_SAP to create new incidents in ITSM for those cases.  There is even an option to create ITSM incidents for already confirmed messages, but that can overload your system and may take time to run.


7.3 What if I go and update the try to close the incident directly in the SAP support portal?

Answer:  Next time you run AI_CRM_IM_UPDATE_FROM_SAP it will bring over on to ITSM those updates.


7.4 What if I confirm the incident right in the SAP market place?

AnswerNice try!!!   SAP will send you back the incident and you will only be able to request confirmation in ITSM.


7.5  Will SAP still notify me via email that my incident at SAP is in Customer Action?

Answer:  Not anymore.  Note 1278052 explains SAP stopped doing that due to the confusion that created and also to enforce us to use ITSM, instead.  Read 9.1, which has the link to enable internal notifications.


7.6 What if there is an attachment in my incident larger than 4MB, current restriction SAP has in the support portal for the attachments?

Answer:  Oh boy!!! I cannot do the whole exercise.  I am already exhausted of typing   Could you give it a try and share with us?


7.7  What about reporting?  Can I see the incidents with the respective SAP message number assigned by SAP?

Answer:  Yes and from factory.  Stay tuned for the answer.   TIP.  It is an additional column you could add to the incident search.




Juan-Carlos Garcia-Garavito

Other posts from this author @ http://scn.sap.com/people/juan-carlos.garcia-3/content

Applies to:

Solution Manager 7.1 SP 7 or higher, ST-TST 300 SP0 or higher, CBTA 3.0 SP2 or higher (frontend), SAP GUI 7.30 or higher, ST-PI 2008 SP6 or higher, ST-A/PI 01P or higher.


The Component Based Test Automation is shipped with SAP Solution Manager 7.1 SP07 and higher. CBTA allows the creation of automatic tests like eCATT via a dedicated recorder. It supports scenarios on systems under test that are based on the SAPGUI, SAP CRM web-client, SAP ABAP WebDynpro, SAP Portal, SAP WEBGUI, BSP, SAP Java WebDynpro technology.

Unlike eCATT (record and playback approach), CBTA test scripts follow a modular approach. Therefore, test components can be reused and damaged test scripts be repaired fast. Apart from that, CBTA scripts can be created easily by business analysts while eCATT requires developers' expertise to creation and maintain test cases. CBTA is composed out of 2 software components: An add-on to be installed on SAP Solution Manager 7.1 from SP7 onward, and a front-end component to be installed on the user's desktop.


The following are the prerequisites that have to be met in order to use the CBTA script recording functionality for composite test scripts.

  • Check the compatibility for CBTA for front end, ST-TST 300, SAP GUI, ST-PI and ST-API (Available on SAP service market place).The CBTA compatibility matrix can be downloaded from http://service.sap.com/testing > Additional Information. Also refer the SAP note: 1763697 for more details on installation and configuration.
  • Install required SAP notes for both solution manager and managed system under category CBTA.
  • Complete the configuration for CBTA on solution manager along with SUT- System Under Test (managed system) for which the test is to be executed.
  • Maintain connection and credentials for SUT. Manage the SUT using CBTA setting under Test Management work center.
  • Enable scripting for SAP GUI on both solution manager and SUT.
  • Run self-checks for CBTA and SUT, also create SDC (System Data Container) for a project under which the business process is defined and want to assign the composite test script.

Additional information related to CBTA configuration in SAP Solution Manager can be found in CBTA Release Document and How-to Guide of CBTA.


Composite Test Configuration:

A composite test configuration comprises of test scripts (CBTA, eCATT or 3rd party test scripts), a system data container and a test data container (for data variant). You create a composite test configuration to create an end to end automated test case. The parameters can be passed between the scripts by changing their usage type. The data variant can be assigned using the test data container. The parameter values for which variant has to be assigned, must be of usage type ‘Exposed’.


Composite test.png

In the above figure , the composite test script is made of three individual CBTA test scripts. Each CBTA test script is made up of two types of components.

Default components are delivered by SAP with the CBTA software. They are stored in the SAP Solution Manager repository for eCATT test scripts (you can also create custom components in custom libary and can be called for specific requirements). They are used for standard actions like entering a value in a field, pushing a push button, selecting a tab page.


Screen components are generated after the recording. For each screen, a screen component is generated during the inspection process. This process retrieves information on the screen from the System Under Test (SUT) and generates a screen component. It contains one parameter for each field of the screen. The value can be assigned to such a parameter for which the system enters it in the corresponding field during execution.

A screen component reflects a single version of a screen. To differentiate between the versions of a screen, the system uses the system data container (SDC) and the target components. The version of a screen is the same on all systems of the same SDC and target component. For other systems, other screen components are created. You can reuse default and screen components in several test scripts. When a screen is updated, its screen components can be repaired, to make the repair of test scripts easier.


You have to define the sequence of the test scripts (steps) to be executed and the values of parameters. The parameter value can be passed by setting the usage type to ‘Local’ and providing the appropriate reference to the succeeding script.

Creation and execution of Composite Test Configuration:

Here, for our example we will consider only first two steps of an end to end composite test example. We want to create a composite test script comprising 2 steps (scripts) with the following parameters:


Step -1 Create quotation (CBTA script 1):

Import parameters: Customer, Material, Quantity etc.

Export parameter: Quotation Number.


Step-2 Create sales order from quotation (CBTA script 2):

Import parameter: Quotation Number

Export parameter: Sales Order Number


First, you will require a test configuration where you can add these two steps. This can be created directly from Business Blue Print (where the Business Processes are defined) as an Ad-hoc execution approach. You can also create the same from the ‘Test Composite Environment’ under ‘Test Management Work center’. For our example we will go with the second option.


Go to the ‘Test Management’ work center. Select the ‘Test Configuration’ sub-view for Test Repository. Click on ‘Create’.


In the pop up window provide the name of the configuration. Select the test tool as Composite Test from the drop down. Also provide the name of the composite test script and click on OK.


Select the appropriate Application Component using the value help. For system under test, select appropriate system data container (SDC) and select the target system for which the composite test is to be executed. Save the configuration as shown in the figure below.



Now, we have to put 2 of the steps (scripts) in the sequence. First we have to create the quotation. The corresponding CBTA script ‘Z_CREATE_QUOTATION_VA21’ is already created. Under the tab ‘Test Script’, add the CBTA test script‘Z_CREATE_QUOTATION_VA21’ for ‘Test Script Steps’. Now, the next step is to create the Sales Order in reference to the quotation number. The corresponding CBTA script ‘Z_CREATE_SO_VA01’ is to be added as the second step.


To pass the value of parameter Quotation Number created by the ‘Z_CREATE_QUOTATION_VA21’ test script step to the ‘Z_CREATE_SO_VA01’ test script step we have to change the usage type of the parameters.

First, open the test script ‘Z_CREATE_QUOTATION_VA21’ by double clicking on the name.The test script will be opened in the new tab. Change it in the edit mode. Export the Quotation number created in the export Parameter ‘MESSAGEPARAMETER1’ by exposing it as shown below. Save the script and change it to display mode.


Now, go back to composite test part and select the second step.


‘MESSAGEPARAMTER1’ is the input parameter to the script ‘Z_CREATE_SO_VA01’ which will receive its value from the output of the script ‘Z_CREATE_QUOTATION_VA21’. Now we will map the output parameter quotation number from the first step (script) to the input parameter team of the second step (script).



To do so, go to the ‘Ref. Parameter’ column of the parameter ‘SALES_DOCUMNENT’ under the details of test ‘Z_CREATE_SO_VA01’. Press F4 help and you can see the exported ‘MESSAGEPARAMETER1’. Select the parameter and click ok. Set the usage type to Local and save. You can now see that the parameter is mapped with the reference of previous step (script) as shown in the figure below.


Now, for all the parameters for both the steps (scripts) for which you want to provide the input as a variant, make the usage type to ‘Exposed’ using the drop down. You can assign the data variants using the test data container (TDC). The test data container with different data variants can be assigned under the ‘Test Data’ tab.

The execution of the Test configuration can be done directly from the test repository by clicking on the “Execute” button. At the end of the execution of the test you can find the report log as shown in the figure below. You can also find details for parameters for each step (script).


Similarly, we can add the third step “Creating Delivery” with the reference of the created ‘sales order number’ at the end of the second step (script) to complete an end-to-end scenario for sales document.  You can also create similar composite test scripts and pass the parameters in between.

About Author :

The author is part of RunSAP CoE team, having expertise in SAP Solution Manager functionality from ALM & RSlaF like Solution Documentation, SoDocA, Test Management, BPCA, BPMon, BP Analytics JSM etc.

With Solution Manager Release ST7.1 SP12 it is possible to use the Monitoring and Alerting Infrastructure (MAI) for the Business Process Operations (BPO) use cases.

A Wiki is now available which describes in a detailed way the steps to migrate a solution to MAI:


Migration from classic BPMon to BPMon on MAI - Solution Manager - SCN Wiki

A belated Happy New 2015! As a belated Christmas present I want  write this blog about the new key figure content that was shipped in December 2014. On Monday December 15, 2014 the new ST-A/PI 01R support package 1 plug-in was shipped to customers and this means that many new key figures have been shipped for Business Process Monitoring and Business Process Analytics in SAP Solution Manager. This blog will give a short overview about what is new. The plug-in contains (besides others)

  • New key figures related to a 3rd party sales process (often also called drop ship process)
  • New key figures where business documents (e.g. purchase requisitions, purchase orders, MM scheduling agreements) are brought togehter with MRP list information
  • New Automation rate key figures for WM and PM
  • New item related CRM key figures
  • New transportation lane related key figures for SCM APO


The new ST-A/PI 01R support package 1 is available for download and can be found under (SMP login required) http://service.sap.com/supporttools.A complete list/catalog of all available out-of-the-box key figures is available as MS PowerPoint presentation at (SMP login required in both cases)



  1. On slides 2,3 and 4 (Table of Content) you can find hyperlinks where you can directly access the respective chapter of interest.
  2. For application related key figures you find some of the listed Selection Options in bold letters. Those Selection Options are available as "Group by" fields in Business Process Analytics.
  3. Those key figures with '€' as bullet point support also a value benchmarking as part of the "Advanced Benchmarking" functionality.

Key figure news summary for selected areas

New key figures have been developed for 3rd party (drop ship) processes:
  • 3rd party sales document items without purchase requisition items
  • Overdue 3rd party purchase requisition items with sales information
  • 3rd party purchase order items overdue for goods receipt (only relevant for customer that post the statistical GR)
  • 3rd party purchase order items overdue for invoice receipt


New key figures where business documents are brought togehter with MRP list information to allow better insights in supply chain planning:

  • Overdue purchase requisition items with MRP list
  • Overdue purchase order schedule lines with MRP list
  • Overdue MM scheduling agreements with MRP list


New outbound delivery key figures bringing delivery and shipment information together:

  • Overdue outbound deliveries without shipment assignment
  • Lead time from outbound delivery creation --> shipment assignment


New Automation rate key figures for WM and PM:

  • Automation rate: Inbound transfer order items  (how many inbound transfer order items are created automatically vs manually)
  • Automation rate: Outbound transfer order items (how many outbound transfer order items are created automatically vs manually)
  • Automation rate: PM/CS notifications (how many PM/CS notifications are cleared automatically vs manually)
  • Automation rate: PM/CS orders (how many PM/CS orders are cleared automatically vs manually)
New CRM related key figures:
  • Sales document items in status 'open' or 'in process'
  • Service document items in status 'open' or 'in process'
  • Lead time from sales document creation --> Taking document 'in process'
  • Lead time from sales document creation --> Completing the document
  • Lead time from service document creation --> Taking document 'in process'
  • Lead time from service document creation --> Completing the document
  • Lead time from business activity/task creation --> Taking activity/task 'in process'
  • Lead time from business activity/task creation --> Completing the activity/task



New transportation lane related key figures for SCM APO:
  • Transportation lanes per product
  • Transportation lanes per location


Further reading

You can find all necessary information about Business Process Analytics in this document. Frequently Asked Questions about Business Process Monitoring and Business Process Analytics are answered under http://wiki.sdn.sap.com/wiki/display/SM/FAQ+Business+Process+Monitoring andhttp://wiki.sdn.sap.com/wiki/display/SM/FAQ+Business+Process+Analytics respectively. The following blogs (in chronological order) provide further details about Business Process Analytics and Business Process Monitoring functionalities within the SAP Solution Manager.



You are interested in the integrations of your solution Manager with the Signavio editor but during your integrations you have difficulties with the setting up your signavioconnector propoertes file.


User Guide for integration you can find in the Signavio online help  documentations where you have detail  descriptions how to implement the link between your SAP Solution Manager and Signavio SAP Solution Manager Connector 7.1.


My bog will help you just with the additional explanation of the User Guide sections which I've found not clear  during my integration effort.



In the User Guide online documentation  starting on  the sections  5.   there is difference in SP12 screens . It  differs from the online User Guide  documentations !


Sectiuon 5 part:




5.The Signavio SAP Solution Manager 7.1 Connector uses the BSI Enterprise Services (SOAP web service) to communicate with the SAP Solution Manager. This web service has to be enabled and configured before the connector can work properly:


a.Logon to your SAP GUI and start transaction se80.

b.Search for the package BSI_SERVICE_API:




in SP12 there is different screens for the BSI enterprise Services therefore please follow my blog in order to make your integrations properly.



If you will follow User guide in section f.  (f. Open the tab Transportation Settings and find the URL of the service binding. Please store the URL for later usage when configuring the connector. ) you will find that  URL from the section f. is missing:





In SP12  BSI Enterprise Services (SOAP web service)  looks a bit different. In order to get requested URL you should go


In SOAMANAGER follow steps:



on the next screen you will get URL you are looking for:



The above URL should be later used in your solmanconnector PROPERTIES files in the signavio HOME directory on your solman host. My URL example is following:






in order to fill out your solmanconnector properties file you must derive two parameteres from your WDSL URL Link:



solman.bsiservice.binding            =  /100/signavioconnect/binding_1

solman.bsiservice.endpoint          =   /sap/bc/srt/rfc/sap/bsiprojectdirectroyinterface 







To find out what is wrong with your solman connector the best place where to look is in the log file of the signavio HOME installation directory. The log file is located in the log directory!





in order to be able to sync your signavio editor content with your solman projects after each  restart you solution manager server -  you have to repeat step 8) from the Signavio SAP Solution Manager Connector 7.1.  user guide!!!


     8.Run the setup:

          In this step the connector establishes an Oauth connection to the Signavio Process Editor and asks for the a Signavio user to authenticate against the      Signavio Process Editor.    

Proceed as follows:



if you have questions do not hesitate to contact me.


Boris Milosevic

There are a lot of questions and discussions around the Technical Architecture that should be used for Technical Monitoring so I decided to start write blog post series as requested by community members. I want to keep the blog reasonable in length so I’ll write up parts on Technical Monitoring.

A first reasonable question is, how many SAP Solution Manager systems do I need?

This blog represents my opinion. If you have a different opinion, feel free to share and discuss it with the community at large as it can be of interest to all of us so please feel free to comment.


How many SAP Solution Manager systems do I need?


One of the first questions in terms of architecture for Technical Monitoring is “How many SAP Solution Manager systems do I need?”. The answer can differ greatly depending on what your plans are,  what you are trying to achieve and how large your landscape is.


Small size


A small customer with a small SAP landscape (one ERP system landscape) will often run a single SAP Solution Manager instance. When it comes to Technical Monitoring, it would mean that all systems get connected to this one SAP Solution Manager instance.


Having only one SAP Solution Manager system comes with typical advantages and disadvantages as you would have them in a traditional ERP landscape if you would only have a productive ERP system.


When it is time to update the SAP Solution Manager system, to avoid direct impact, you could clone or copy the SAP Solution Manager system and process the update on the clone or copy to test out the procedure before doing the actual update in a weekend for example (to avoid downtime / impact as much as possible).


Medium size



Many customers only have two SAP Solution Manager systems so often I see DEV – PRD landscapes at customers as we have a good amount of medium sized customers. This is a very common configuration that I’ve seen.

The discussion starts here with two SAP Solution Manager instances, which SAP systems (talking ERP now), do I connect where? Do I connect all DEV and perhaps ACC systems to the DEV SAP Solution Manager and only PRD systems to the PRD SAP Solution Manager system?

Well, I’ve said this before and about to say it again. SAP Solution Manager wasn’t really designed to have this kind of split so I only connect SAP Solution Manager DEV to itself as well as one or more sandbox ERP systems.

All other systems (DEV, ACC, PREPROD, PRD, …) get connected to SAP Solution Manager PRD in order to benefit from having all that data in one place.  One alert inbox for the support team, one single source of truth for reporting purposes, one single source of truth for specific scenario’s that require data and connectivity of all the systems that belong to a specific landscape.

The advantage of having a DEV SAP Solution Manager is that you have a place where you can try scenario’s out, perform support package stacks updates which makes it easier to minimize the impact on the PRD SAP Solution Manager.

Large size




You probably guessed I was going to say, large customers have three SAP Solution Manager systems but that’s not the general rule of thumb. It’s a SAP recommendation most likely but that doesn’t mean it’s really a necessity. It can make sense in case you are going heavy on custom development and want to invest in ITSM scenario’s where you really want to have a ACC system in place but what I see is that many SAP customers max out at two SAP Solution Manager instances (DEV, PRD) as their SAP Solution Manager landscape.

Larger customers can have larger landscapes (potentially scaled out). Some have a split landscape where they decide to go DEV1 – PRD1 for Technical Monitoring and DEV2 – PRD2 for IT Service Management and by doing it, separating out those scenario’s from running on the same SAP Solution Manager instance.

Why? Because they want to avoid impact of one scenario on the other scenario so they would like to patch DEV – PRD faster compared to DEV2 – PRD2 for example.

The drawing above shows an example of such a split landscape. You use one SAP Solution Manager landscape for Technical Monitoring purposes while you use a second SAP Solution Manager landscape for IT Service Management purposes. In the IT Service Management landscape, you don't use diagnostics agent. You only connect the managed SAP systems through RFC connections thus you ignore some red traffic lights in managed SAP system setup. Thet second SAP Solution Manager landscape can be monitored by the first SAP Solution Manager landscape where Technical Monitoring is implemented.

SAP Solution Manager – Diagnostics Agent architecture guide


I haven't gone into any kind of detail on agents or other elements yet here that make up the architecture. That might be content for a future blog post. In SAP note 1365123 - Installation of Diagnostics Agents there is a guide attached that provides you with insight on possible architectural options for Technical Monitoring. The PDF document goes through numerous possibilities and options which ventures outside of what I covered in this blog post.

I prefer to keep things simple in terms of not cross using elements as you can see in above “simplified” architecture schema’s. Why? Because complexity adds additional effort on multiple fronts, configuration, maintenance, support and troubleshooting to give some examples. The split landscape option translates into more maintenance effort but lower risks and it makes it easier to keep the SAP Solution Manager landscape up to date that is mostly used for technical scenario’s since you don’t impact ITSM processes that way.

Diagnostics agent on the fly as a default


At the moment, I advise to install Diagnostic Agents on the fly (as opposed to a regular, standalone Diagnostic Agent) as a default even if you only have a single SAP system per server because in SAP Solution Manager 7.1 SP12 it is a prerequisite to use automated reconfiguration .

Automated reconfiguration allows the system to reconfigure certain managed system setup steps and some other steps like automatically assigning new, default SAP templates in technical monitoring after the SAP product version has been updated.

If you haven’t seen or read about it yet, you can find a nice presentation on the SCN wiki: http://wiki.scn.sap.com/wiki/display/SMSETUP/Home

where you can also find the Sizing Toolkit which can help you calculate the need for scale-outs for example.

Under 7.1 SP12 (NEW) check out the presentation on Automatic Managed System Reconfiguration (PDF)

The Service Marketplace pages for Business Process Operations will stop being available in the very near future. This means that accessing information via the pages

will no longer be possible.


Therefore, all documentation for Business Process Operations (including overview presentations and setup guides) is now accessible via the SCN Wiki Page




This page gives a general overview about Business Process Operations. Each area of BPOps is shortly explained and links to a sub-page with more details are provided. These sub-pages per area are directly accessible  via the following URLs:


In these sub-pages you have access to the existing setup guides and further documents currently available in the Service Marketplace. All future documentation will also be made available here.


In the coming weeks we will further extend our documentation in these wiki pages and we will keep you informed in case of major updates.

The Part I of this blog gives the some tips in how to enhance the original urgent change flow to generate transport of copies. Today I will explain how to activate this customizing in your ChaRM Project. You can check it out on this link How-to enable Transport of Copies on Urgent Changes Flow (PART I)


Create a new Project under transaction SOLAR_PROJECT_ADMIN or close the current Project Cycle.


Before you create the new tasklist, you should perform the following steps:




Push button Show Avaiable Variants for Tasklist and select the Y/ZSAP0 tasklist variant. Without this step, transport of copies at urgent change will not work! If you don't make this change in before generate the Tasklist you will receive some errors when the urgent change flow when you stay at the status E0004.

Last month, I had the pleasure in colaborate with a brazilian food company (the world's tenth-largest food company)  speaking about some of our experiences, best practices and provide on demand consulting for their ChaRM Change Request Management Solution.


During our conversation the customer tell to me your wish to deploy Transport of Copies as part of the Urgent Changes flow. As we know, the Change Request Management cover a standard workflow containing the transport of copies procedure available only on Normal Changes.


In this blog I provide some hints in how you could set it up, however there is no guarantee and also standard support from SAP for this configuration.




Urgent Changes have their own tasklist (Type "H") to coordinate all transport requests. The original tasklist type H does not contain the action "Create Transport of Copies". In this case we need to enhace the tasklist type H using a custom tasklist variant. After this configuration, some ajustments must to be applied to control the TMS of managed system.

Just to clarify when the ToC will be generated and when the original Transport Request is released, I made the following pictures showing the "AS-IS" and "TO-BE" solution. You can adapt for your needs (e.g. creating additional status).


Standard Process Flow: Urgent Change (SMHF)


Enhanced Process Flow: Urgent Change (Y/ZMHF)


Configuration Procedure


Create a Tasklist Variant


          Access the IMG activity using the following navigation options:





          Push button "New Entries":




          Create the tasklist variant "Y/ZSAP0 ":






Define Tasks for Tasklist Variant


          Access the IMG activity using the following navigation options:





     Select all entries from Tasklist Variant "SAP0" and copy to Tasklist Variant  "Y/ZSAP0":



     Create a new record adding the task "Create Transport of Copies"  for the Project Type "H Urgent Change":






Define Header / Footer Tasks for Tasklist Variant


     Access the IMG activity using the following navigation options:






Repeat the procedure 2 from Define Tasks from Tasklist Variant configuration:




Register Tasklist Variant into Project Cycle


     Apply the SAP Note 927124.



Adjusting Conditions and Actions (TSCOM Tables)


     Some activities regarding the transport management system and consistency checks are triggered when  the change document is assigned to a specific status value.       To enable the urgent change flow to generate transport of copies, we need to change some actions and their conditions based on status value.



     Access the IMG activity using the following navigation options:




     On folder "Create Procedure Type" choose "Y/ZMHF" transaction type and their status profile:




     On folder  "Assign Actions"  make the follow ajustments for the User Status "E0004 - To be Tested":    



     On folder  "Assign Actions"  make the follow ajustments for the User Status "E0005 - Successfully Tested":




     On folder "Define Execution Times of Actions", make the follow adjustments for the User Status "E0004 - To be Tested":



     On folder "Assign Consistency Checks", make the follow adjustments for the User Status "E0004 - To be Tested":




     On folder "Assign Consistency Checks", make the follow adjustments for the User Status "E0005 - Sucessfully Tested":







Project cycles powered by the custom tasklist variant will be able to generate Transport of Copies. In my next blog I will describe how to use this feature.

Here's what I thought before using CHARM:


Charm will:

  • Remove Conflicts between developers
  • No more missing objects when transporting to production
  • No more keeping track of transport dependencies
  • Allow to bundle transports outside of SAP
  • Keep defects with original requests
  • There will be less transports


The above is living in Michelle's world of what CHARM will do.  NOT WHAT SAP or CHARM Claims to do.


So here's a scenario:

I would make changes to an object.  There would be changes to an outside system.  Developer 2 makes changes to a different object that is a part of my project.  All of the previous transports/objects will be bundled in one CHARM request.  Emergency and non-emergency transports will be taken into consideration.


Dum, Dum, Dum, Da, Dum - Drum roll please.  Charm to the rescue.


See below:




So was my vision correct?


In practice:

  • A regular transport is created.   Table 1 is not changed.
  • The transport and CHARM ticket are released for an emergency change.  It is immediately moved to production. (After testing in quality)
  • The regular transport has fields removed from table 1, and the emergency transport object is changed so it no longer requires those fields.
  • The emergency change is moved to production again.
  • The regular change is moved.  Now when the programs are regenerated - the table is generated, and then the program.    The emergency program is generated with errors - so it goes with error - 8, and the regeneration stops.


If the above confuses you.  You are not alone.  It confuses me and my BASIS people.   So the only solution I found was to create a new CHARM ticket with just the table.   Transport it first.  Re-transport the 2 Charm tickets.  They will go into the system clean.

In theory:

All transports are moved to production with the release.


In Practice:

  • Not all transports move to production.
  • The changes are backed out of the object, and the object is changed by the developer.  The developer ignores the conflict and can create the new transport request.
  • At this point the changes can't be moved without BASIS help.  Why?  Because there is a conflict.


In theory:

Only one developer works on an object at a time.  Or if more than one developer is working on it, then it's for the same project.


In Practice:

  • There can be more than one developer working on an object.  And yes, it is for two different projects.
  • So there are two options - add the object to the two different CHARM tickets.   Leave the object in the CHARM ticket that has it in it.  Either one will cause one CHARM ticket to be dependent on the other.  It will be a manual task to keep track of that.


In theory:

When a new table is created, all your developer's will know it is new and won't use it in their objects.


In Practice:

  • Developer's miss that the table was created in a different CHARM ticket.   They have no idea on the dependencies.
  • CHARM doesn't notify of the dependencies.
  • The move to production has errors.


OK - I'm done with the things CHARM doesn't do well.    There are some things that it does very well.


CHARM is amazing at:


  • Limiting the number of transports.   For a regular CHARM ticket that goes with a release, only the transport task will need released.   When the task is released, it moves in the background to the test system.  If there are problems, then I just create another task.  The transport request is never really moved until the move to production.
  • It is easy to create a configuration transport request and a development transport request.   Since they are both on the same CHARM ticket, they will move to production together.
  • If your CHARM ticket has been released,  and an error is found.  It is easy to create a defect request and attach it to your CHARM ticket.  This will keep the transports together in one CHARM ticket.
  • The test environment is easily locked down when the system is moved to testing.  This will stop everything except for emergency transports from moving to the test client/system.
  • The approval process is at the front end.  A CHARM ticket is not created until the CHARM request is approved.  That means a transport request can't be created.
  • Outside objects - I'm not sure as we haven't used CHARM for that yet.


So there you have it, my personal thoughts on CHARM.  Keep in mind, like all SAP products, different companies will have CHARM configured differently.  So some (or none) of what I've written may apply to you.


Does CHARM do what it claims to do?  Yes.  Does it do what you think it should?  You be the judge of that.  Personally, I think it does make my job easier.  It's not a silver bullet.  It doesn't fix all transport issues.


Please comment with some pros and cons.  And do let me know if I'm losing my mind with some of my comments. 



Closing the current Change Cycle and open a new One

SAP highly recommends, that customers close their Maintenance Cycle on a regular basis.

  • This allows a meaningful Reporting on Change Activities per Change Cycle.
  • On the other hand closing the Maintenance Cycle regularly helps to avoid a potential performance impact on the long run.

A Change Cycle is closed by processing the Change Cycle Document to the final CRM User Status:

  • SMMN for a Maintenance Cycle with Task List Variant SAP0,
  • SMMM for a Maintenance Cycle with Task List Variant SAP1,
  • SMDV for a Project Cycle.

Take over open Change Documents to the next Change Cycle

When you close the existing Change Cycle, for instance a Maintenance Cycle and open a new one, you are not forced to close all Change Documents, which belong to this Change Cycle.

SAP Change Request Management allows to take over open Change Documents to the next Change Cycle.

Project Completion and complete Closure of all related Change Documents

In SAP Change Request Management no automation for the Closing of Change Documents, which belong to a ChaRM Project is available.

However ChaRM offers program CRM_SOCM_SERVICE_REPORT as Standard Solution for Closing of Change Requests and Change Documents, which belong to the Change Cycle.

Before utilizing program CRM_SOCM_SERVICE_REPORT, you should check the following:

  • Status Profile Customizing (for the referring Change Cycle Document: SMMN, SMDV),
  • ChaRM Condition: SUB_ITEMS is defined for Change Cycle Documents SMMN and SMDV.

With the help of program CRM_SOCM_SERVICE_REPORT you can search for any kind of open Change Documents with various search criteria as:

  • Open Change Documents per Business Partner, Team, etc.
  • Open Change Documents per CRM User Status,
  • Different Service Process related search criteria, as 'Transaction Type', 'Posting Date', etc.


After having made your selection, you can let the program further process the open Change Documents up to their final CRM User Status.



In addition the program offers a 'Test run mode'.


Of course, the program CRM_SOCM_SERVICE_REPORT can be also utilized in order to close IT Service Management related documents such as Incidents or Problems.


Filter Blog

By author:
By date:
By tag: