1 4 5 6 7 8 35 Previous Next

SAP Solution Manager

516 Posts

From SAP: “All live Meet the Expert Sessions are recorded and will be then available via SAP ES Academy ‘Replay Library’  www.service.sap.com/replay-library


The usual disclaimer applies that things in the future are subject to change.  Also a couple caveats:


1. I have not used this feature productively

2. I missed parts of this webcast in the middle so my notes are not complete




Figure 1: Source: SAP


Figure 1 shows that SAP plans to make Solution Manager more business oriented.


SAP also wants to make SolMan ready for HANA deployments


Figure 2: Source: SAP


SOLAR transactions that support documentation and implementation processes


SAP said this approach that had drawbacks


Figure 3: Source: SAP


Figure 3 shows the current pain points, including a “Rigid 3 level hierarchy”


SAP wants to use the new UI – HTML5


Basic Concept for SAP Solution Manager 7.2

Solutions can act as a an umbrella


Figure 4: Source: SAP


Solution (in Figure 4) covers system landscape where you need to know runtime environment, execution environment


New solution documentation UI works with LMDB content, logical component, new logical component group


It covers the processes that the customer execute


Figure 5: Source: SAP


Figure 5 shows the Solution landscape and documentation UI


Sub landscapes relates to a maintenance cycle related to ERP


Sites are processes deployed to multiple plant running different ERP systems – for global rollout use cases


Document types reflect what documentation to be available


Figure 6: Source: SAP


Figure 6 shows the planned solution documentation approach is to be both top down and bottoms up.


Figure 7: Source: SAP


Figure 7 shows where attach documentation related to executables


Business processes can be reused


Define configuration block; define dependencies of the block


Figure 8: Source: SAP


Library of executables, config units, interfaces – IT


Enable processes – assemble end to end processes out of artifacts


Figure 9:  Source: SAP


Introduce a change and include change documentation


Ensure properly documented in maintenance branch and transported


Documentation needs to be released

System Landscape


Figure 10: Source: SAP


Logical components have changed; solution documentation is bound to logical component group


When upgrade, you need to restructure logical components


Content Activation



Figure 11: Source: SAP


Figure 11 shows projects/solutions to move to 7.2 content structure; this includes BPMN modeling capability


Question and Answer:

Q: What is clear definition for branch?

A: Branch is a versioning context for documentation


Q: Is this Solution Manager running on HANA DB?

A: Can run on HANA or other databases


Q: Will integration with ARIS be possible?

A: Clearly plan to have open interface to integrate with third party modeling tools

Not available in first version but it is on the agenda


Q: Is there is a limit on the number of nodes you can have on your project

A: not known to him


Q: Will there be integration with PowerDesigner?

A: plan to have open interface to integrate with third party modeling tools


Q: What is the effort to migrate?

A: If you move content from SOLAR to new documentation – content is moved to process area – the respective library structures are created

Fellow Members,


In this blog, I would like to share my experience with recent Change Request Management projects. I read a blog on ChaRM on a Developers perspective and I liked it and it was close to the 'things' that you hear in a ChaRM Project. In the same lines, I tried to compile my notes from my work diary and present it here in plain English. The idea behind this effort is to highlight the quote "In theory there is no difference between theory and practice; but in practice there is.!!"


P. S: All the content expressed here are my personal opinions and do not represent my employer or SAP.


1. Concept of Change Request and Change Document


Often during the blueprint discussion phase of ChaRM projects, the most frequently asked question is 'Why do we need two documents in ChaRM process?'. Most of the customers I worked with, find this concept little confusing. The confusion is more profound if the customer does not have a established change management process or used to any other tools (like sharepoint, custom web forms or editable PDF forms..etc) as Change Request Forms. The hard time for consultant will be to convince the customer and make them understand, how Change Request will be used only for Approvals and Change Documents would be used for handling Transport Management aspects of entire process. So be prepared to convince that the Change Document is where all the action is.


2. Who will create Request For Change?


This topic sometime gets overlooked. The organization structure of companies running SAP varies from one organization to other. So we can not go with a notion that one size fits all concept. During a initial discussion phase, the work of consultant would become easier if the customer has a well established change management practice. Sometime the end user would be sales agent on the field or sometimes it's the help desk team. Sometime there would be scenarios where in the end user does not have access to SAP system and have to call the help desk hotline to raise a CR on behalf of him/her. So identifying the right set of people for end user trainings is an important factor to be kept in mind while designing the process. Understand your end users of the process.


3. Approvals in Change Request.


This topics varies from customer to customer and consultant needs to be prepared to expect more than 4 or 5 approvers for a single change request. The standard out of the box configuration has 2 level of approvers(Change Manager and Change Advisory Board). However speaking from my past experiences,average number of approvers I have encountered is minimum three.  This means for consultant would need to customize new partner functions and CRM UI aspects of it. It is possible to have up to 10 partner functions in Change Request UI, so technically we can have up to 9 approvers for a change request(one of the partner function is being reserved for Requester/End User). In some scenarios, the end user raising a change request would not be knowing who would be his 3rd level of approver for the request of change. In such cases we need to design automatic partner function determination using categories. This would ease the process. Also if the organization is huge, then expect to have a very long list of categories to be added to multi level categorization in a change request. In addition, if you could customize the approval procedure determination using categories then it would be applauded by the end users for sure !!   So try to incorporate automatic Partner determination and Approval Procedure Determination based on categories.


4. Emails in Approval Management


Everyone loves to receive a email if he/she was made as a approver for a change request(if possible in HTML mail format). The scenario would be even more useful, if the approvers receiving emails in a sequential way i.e first Change Manager receives an email, once he approves, Chnage Advisory Board receives email...so on. BUT unfortunately in a standard  process offered by SAP as of 7.1 SP12, the approvers only receive worklist emails in their SO01 inbox. And in the practical world I have never seen anyone checking their SO01 inbox for mails !. So by default, approvers in change request will not be notified via email for approvals. This was very disappointing for me in the beginning because this is one of the most frequently asked feature in ChaRM by all the customers I have come across so far. However later I learnt that with little customization you can convert these SO01 inbox worklist email to outlook/inbox email notifications. However please note, this converted email notification would be in plain text and not a fancy email you wish to see. There is a long thread ChaRM: Approval Settings - Email Functionality in Change Request by which I learnt how to do it. Email notifications for approvers as a part of worklist is one of the most needed feature in out of the box ChaRM solution, hope SAP would incorporate this as a standard feature in future releases. So If you are on 7.1 SP12 or below be prepared to be surprised that there is no html email for approvers !


5. Which Change Documents to use?


Again, this is one of the most debated topics and strangely, I have seen customers reluctance to use Normal Changes for maintenance purposes. Some of the feedback I hear during blueprint discussion meetings are like, Normal Change is too much 'clicks here and there' and Normal Change is not very flexible in 'what if..' situations. There could also be scenarios where Basis team is trying to minimize their efforts in Change Management and Transports execution process. In such situations they would always push for the Urgent Change instead of Normal Change. Normal Change fits perfectly if the customer has a defined release cycle concept. However in scenarios where the customer is so much comfortable with existing ad hoc transports import, then they expect your new process to work the same way. With the new preliminary imports and other enhancements as of SP12, things have started to change and Normal Change is finding more and more relevance for everyday change processes. The consultants job would be to thoroughly understand the customer requirement and compare that with Maintenance Cycle, Normal Change, Task list and other tools provided by SAP and design a best suitable solution.

There is another perspective for this. Some customers would only be looking to automate the Transport Management process and other would be interested  in complete re-haul of their change management practice to adopt to best practices. So it depends on whose boarding room you would end up So bring in the clarity on type of change document to be used and emphasize on importance of having a disciplined release strategy.


6. Approval for Transport Import inside individual Change Documents


I encountered this request 2 out 3 times in my previous engagements.  Even though Change Request is approved(in some cases by CIOs too) and handed over to functional/development team for implementation; the leads/managers of functional/development teams would still want to control the transport import process to follow on systems via approval apart from just controlling the phases of cycle. Again you can trace the origin of this type of requests to traditional email approvals that the team leads/managers used to provide before implementing new process. This type of requests can be handled easily by tweaking couple of new actions and statuses in the change documents. No big deal, but time consuming for consultants So be prepared to expect some more approvals in random places.


7. Simply the User Experience and UI as much as possible


Before you hand over the process to user trainings, try going for minimalistic approach in the CR or CD UI. By default you have lot many tabs inside CR or CD which may not be relevant for every customer. So tweaking the UI and removing not used tabs can add lot more value for the end users. In one of the projects, I was requested to simplify the UI to look like 7.0 version CR screen (with tabs on the top instead scrolling down UI). I have written a blog on how to transform the UI look from long scrolling form to simple tab based UI. Please refer that blog. So go with a lean design.


8. User Trainings


According to me,  this is one of most time consuming process in ChaRM implementation projects; it is every human's basic nature to be reluctant for the unknown or new things anyway . I recently used one of SAP's tool in training and content management portfolio, WPB (Workforce Performance Builder) and this tool turned out to be very useful for end user trainings in ChaRM. Users liked the way of learning new process ( like creating a new CR ...) in a completely new UI with relative ease. So be well prepared with Kubler Ross theory !





Source: Kubler Ross Change Curve


9. We went Live on ChaRM, what's next?

The entire success of your ChaRM project depends on the effectiveness of Basis team in handling Change Documents post go live. The maintenance of ChaRM related task should be owned by competent Basis team, as Esteban highlighted in the comment section, establishing roles and responsibilities in the supervising the Change Management process is vital. There should be a run book available with FAQs and common error situations in handling change documents.


Hope this helps all the consultants out there who would be handling ChaRM projects for the first time !!!


I would love to hear from all of you on your experiences, suggestions and feedback in the comment section.


With Regards,


Here is the second part of my blog on the steps to make a successful ITSM / ChaRM project. You can find the first part with this link:


3. Change Management


This is a part of the project that can easily be underestimated whereas it is one of the most important factor of its success.

When any ITSM solution is implemented, it replaces an existing tool or add a new tool in the IT processes. In any case, the old ways of working are going to change and it is never an easy thing to do.


To make the transition as smooth as possible, right from the beginning of the project, start communicating to the future end users about the project’s objectives, the solution designed, the benefits expected, etc.


It will help you in different ways:

  • Your teams members might identify some part of the process that have not been clearly defined or don’t fit how one group is used to work
  • The changes brought by the project will be more easily accepted and you will guarantee a much faster adoption of the solution
  • You will reduce the risk of the solution being rejected by some of your teams


You don’t need to spend a lot of time on those activities. Just a few days are necessary, but it will definitely change the way your solution is accepted.

4. Build


This is related to the change management part of the project, but don’t forget to involve ChaRM end users during the build phase. Organize demonstrations, Q&A, etc.


The build phase also requires a test landscape to validate the tickets behavior. You can always use solman, but the best configuration is to have an ERP sandbox as close as possible to the production landscape configuration.

It will make your life easier during the go live. You will avoid implementing SAP notes on the ERP systems, close to the go live date, because the SAP Basis level is lower on ERP than Solution Manager, for example.


5. Test


As for any IT project, the definition of the requirements is essential to successfully test the solution. You don’t want to forget any requirement, as it would lead to a solution partially tested. The best approach is to start building your requirements during the design phase. As you design the solution, you also define what should be tested and how.

Don’t forget to cover, with the requirements, your release management process and all the different ways your team works, depending on SAP modules or products.


6. Training


Keep your training documents simple. In many projects, I have seen clients build very detailed documentation. The problem is that they are very difficult to maintain and the end-users usually don’t use them, as the documents are too long and they cannot quickly find the answers they are looking for.

And remember that end-users will regularly change, your documentation should be easy to understand as the solution owner won’t be available to explain to all new users how they should use the solution.


Instead, when you’re preparing the documentation, think about how the end-users will consume it. What are the information they will need to look for regularly (naming convention, release management principles, etc.) and the ones they will look at once or twice (objectives of the project, ticket interface, etc.).

With this, you can divide your user guide in more comprehensive units and make sure that the solution will be used the way it was supposed to.


7. Go-Live


I have identified three steps to safeguard the go live of ITSM / ChaRM projects

  • Build the cut over plan throughout the project
  • Anticipate the technical operations
  • Build a transition plan for the existing tickets / transport requests


Build the cut over plan throughout the project

Depending on the size of the solution you’re dealing with, there can be a lot of operations that need to be performed. It is very easy to forget some.

To avoid that, the best thing is to start building the cut over plan as soon as the design phase starts and to update it regularly during the project.


Anticipate the technical operations

On most projects I’ve done, we usually had problems with the same operations:

  • System landscape preparation: basis team had trouble generating RFC destinations or setting up TMS the way ChaRM expects it
  • Authorizations on the satellite systems: the authorizations were not consistent on all the systems managed by Solution Manager and it can lead to errors in the processes (ex: transport requests not released)


All this problems can lead to a stressful go live and even delay it. My best advice is to anticipate those operations. Start working on them at least 1 or 2 weeks before the go live.


You will give your teams more time to solve the issues and will avoid all the stress.


Build a transition plan for the existing tickets / transport requests

When the new solution will be deployed, you will have tickets in your previous ITSM solution or transport requests not linked to ChaRM tickets. You want to reduce them as much as possible, as it will confuse end users and can lead to errors.


For ITSM tickets in the legacy system, you can chose between three options:

  • Manually create the tickets in Solution Manager: easy to do when you have a few tickets, but the workload quickly increases
  • Work with the old tickets until they are all closed and use Solution Manager for all new requests / incidents: it is the easiest solution, as no work is necessary to prepare the go live, but it can be confusing for end users
  • Automatically transfer the tickets from the legacy tool to Solution Manager: SAP doesn’t have any tool to fulfill this requirement, but there are software, provided by third party vendors, that can perform this operation. It is the best solution and can be cheapest depending on the number of tickets to transfer


For transport requests, if you have deployed the cCTS infrastructure, you can link released and unreleased transport requests to your tickets. In that case, the best strategy is to create tickets and link them to transport requests before the go live.

8. Post go-live


Depending on the size of your organization, the changes brought to your IT processes can take a while to be fully understood by your team.

Make sure they are supported after the go-live to understand how the solution works, how it impacts their day to day operations and what benefits they can get from it.


Finally, after 6 or 9 months, execute a new TEA report to measure the progresses made and compare them with the initial objectives. And don’t forget to communicate about your successes!

Hello All,

It was a simple issue but I spent 2 days on it hence writing this small blog, hope it will help others.

While generating stack file in Solman 7.1 SP12 system for ERP6 EHP7 (SAP_HR 600)system to HR Renewal2.0, even after selecting addon HR Renewal 2.0, in target stack MOPZ was capturing component SAP_HR & EA_HR till 604 and 607 respectively.

While HR Renewal 2.0 upgrades SAP_HR and EA_HR to 608 level.


Also I was getting below warning message-

SAP KERNEL 7.42 64-BIT UNICODE': Requested instantiation '20012195' invisible


Solution :


SAP note#1940845 is solution for this.


Issue was due to compatibility between backend services in SAP OSS system and MOPZ.

After applying above note in solman system, MOPZ captured correct packages for HR Renewal2.0 in stack file successfully.


Note also cleared warning “‘SAP KERNEL 7.42 64-BIT UNICODE': Requested instantiation '20012195' invisible” but yes this warning can be ignored.

Issues with the Trusted RFCs in CHARM

Trusted RFCs should be created with current user id and not any other user id because when you will log on from charm to do any modification after creating the transport request in web ui of charm it will not allow you to own the request(owner is changed).

All developers should have access to S_RFC and S_RFCACL objects.

This can be the main reason you won’t be able to schedule the transport release tasks in SCMA as it will initiate the call to TMSSUP* RFC.


Transport of copies are not getting created

While creation of transport copies, TMW rfc will be used and hence SMTMSMP user should have access to execute the function module TMW* in managed system, the main authorization object for this is S_RFC.


Bpmon security authorization issues

Sometimes monitoring object greyed out and alert cannot be viewed in WorkCentre also.

Solman read user in the rfc does not have proper authorization in managed system setup.

Required authorizations are profiles S_CSMREG and S_CUS_CMP

Also S_TABU_DIS authorization is required with field value as SS for DICBERCLS

File monitoring issues

Also for the file monitoring in BPMON, it is very much required for the user in managed system setup assigned in READ rfc from the solution manager to have the authorization object with S_CTS_ADMI with the value of TABL and EPS1.

Note:- The important role SAP_SM_BPOANA_ALL should be checked for all the users and should be configured as per the analytics guide.


Job monitoring issues

Error occurred in the job monitoring objects: This is the error occurred if the job documentation is not created and further not assigned to the job monitoring object. The authorization object required for this is SM_JOBDEF or SM_JSM_DOC. These objects are delivered through SAP_SM_SCHEDULER_BPO role. You need to see and activate the object SM_JOBDEF (in case old authorizations are active you need to adjust it accordingly). Further for configuring the business process monitoring the specified roles should present with user BPO_ADM_<SID>. Similarly for technical monitoring the corresponding user is SMC_JMON_<SID>.

As a logical consequence of my earlier blog How to setup Cross System Object Lock (CSOL) when using enhanced retrofit i want to write today a little about the settings for Down Grade Protection (DGP) in a dual landscape with retrofit.

The best practice use for Downgrade protection is of course "full protection" which means from a customizing setting point of view, an empty table, meaning "no exceptions" for DGP calculation.

You can reach these setting via IMG:



Select "Configure Downgrade Protection" and you will see the "Downgrade Conflict Type" first.


Here we do not want to do any changes and normally this is also where you never change. It's the table to configure what kind of warning or error should appear with which corresponding icon. I guess the standard setting to have the release check being a warning, the re-assign check warning too, the predecessor check critical and finally the imminent check very critical make perfect sense and therefore i never changed this.


We want to browse to the next setting which is the "Downgrade System Configuration".



as said before in standard this table is empty which means no exceptions setup, which results in full protection and a DGP conflict calculation for every conflict type (Release, re-assign, predecessor, imminent) for every system, client, system role and project.


Now i case of a dual landscape we have retrofit setup to look for conflicts between the 2 landscapes and calculate the corresponding retrofit type.

In case of no conflicts -> green case in case of conflicts -> yellow or red.

As the retrofit conflict calculation happens at the time of when a Transport is released in the retrofit source at the same time (or to say it technically correct before the retrofit calculation takes place) the DGP check will be performed.

As a consequence DGP will issue a conflict (of type warning) before the transport can be released and before the retrofit can be calculated.

So the DGP conflict has to be ignored first before the transport can be released. So we can more or less say for every conflict that will be handled via retrofit with a yellow or red type (conflict case) the DGP check will stop the process before.

This is of course an unwanted behavior, as the transport has to be released anyway and the conflict will be resolved using the retrofit tool.

Therefore i recommend switching off the release check of DGP for the source system in dual track retrofit landscape.

You can exclude that check from being performed by adding a line into the "Downgrade System Configuration".


Like that, when releasing a transport in the retrofit source system there will be no DGP check for that transport. The transport will be released and the retrofit calculation will take place and will put a yellow or red case. So you can solve the conflict by using the retrofit tool and will not be stopped by DGP every time before.

So i would resume that in every dual retrofit landscape the DGP customizing should have that exception that the DGP release check is switched off for the retrofit source.



SEA analyzes an SAP environment and documents the impact of an upgrade to an Enhancement Pack or Support Stack before the project begins in an effort to understand the costs and tests associated with the project. It is delivered with Solution Manager 7.1 (SolMan) and available since Support Stack 11.


Minimal configuration in SolMan is required to use the SEA functionality. A target environment will need to be configured and the system information included in LMDB.


Usage and Procedure Logging (UPL) is not required, but is recommended to be implemented in Solution Manager to obtain more accurate data. UPL is available on any ABAP based system and is based on the core functionality of the SAP Coverage Analyzer. Compared with Workload and Performance Statistics (ST03N), the UPL result will be more accurate. It is able to detect all online and background processes and submitted jobs. It can detect the usage of any ABAP process down to the most basic levels and will provide information about system modifications, user exits, development classes as well as single method executions. The Workload and Performance Statistics (ST03N) only counts the dialog steps during the running process but not the number of times it has been run, where as UPL can count the number of executed ABAP procedures on a daily base.


Results Summary


The Summary provides a wealth of information regarding the Upgrade Project including the target platform and version, the total number of days estimated for testing, the number of custom code objects that require adjustment, the number of modifications that require adjustment and the estimated amount of time to complete the development efforts on the custom code and the modifications.


In addition this Summary will provide you with a quick and clear understanding of what will be the overall effort of the upgrade project.  All of the information displayed is detailed in the other parts of the SEA report.



Standard and custom code impacts analysis

SEA provides a list of impacted modifications (SPAU and SPDD) as well a list of custom developments that will need to be modified as part of the upgrade project. Also, the toolset provides an estimation of time required to complete the development efforts needed to complete the project.


The list of impacted custom developments provides an indication of the issue with each object that’s needs to be modified. Also, the list can be exported to Microsoft Excel and used as work list.


The impacted SPAU/SPDD objects are displayed by their affected SAP Application Component and the impacted custom objects by Packages. For planning purposes this information is very valuable to understand the required resources for the upgrade. Prior to the introduction of SEA this information was only made available after completing a test upgrade.



Test Management


During the analysis creation SolMan can be used as the primary Test Management Application or integrated with a 3rd Party Test Management Application such as HP Quality Center. The recommend rule for SEA is that it can provide recommendations for creation of automated test cases.


SEA test scope optimization is based on the BPCA (Business Process Change Analyzer) feature of Solution Manager. Based on UPL, the tool is much faster to use and the analysis more precise.


The objective of SEA and BPCA is to assist the system in the performance of a battery of tests as efficiently as possible:

  • Only the business processes impacted are tested
  • The order of the test is determined by the number of objects impacted by each test. Those with a higher number of objects will have a higher priority. 
  • Automated tests are prioritized over manual tests, as they require very little effort to run


The test order is determined by the type of test conducted (manual or automated) and is influenced by the number of impacted objects tested. When executing the first four tests the test coverage  quickly increases to 60% (of the objects impacted by the upgrade).


In this portion of the SEA Results, the workload available can be modified during the testing phase. SEA provides the ability to quickly analyze the risks taken (% of the tests covered, business processes not tested). SEA is a very efficient tool to safeguard an SAP upgrade project by providing the impacts prior to execution  while optimizing the testing costs.


When using the Test Workbench in Solution Manager, the results of the test optimization can be exported as Test packages.


By reducing the granularity in the graph the provided the associated steps are listed and greater detail is provided on each step of the testing.


The detailed list of tests is prioritized by number of objects impacted.





SEA provides new functionality, which modifies the way IT organizations will plan upgrades. With it, there is a planning tool to precisely evaluate the upgrade budget and schedule, in order to decide if and when the project can be done.


The customer benefits of using SEA cover three main areas in terms of time and resources. The ability to understand the impact of an impending upgrade prior to having to do the upgrade, understanding the custom code and modifications that will need to be corrected, also Test Scope Optimization will focus on providing the proper resources to the specific areas where testing will be critical.


More information about the setup, installation and configuration of SEA can found at: http://wiki.scn.sap.com/wiki/display/SM/SAP+Solution+Manager+WIKI+-+Test+Management

Diagnostics Agent Doesn't Start on LINUX


  • The kernel bundled with the installer 7.3 SP02 or lower is not supported on Linux 3.x
  • Error message “"This patch level of the Startup Framework 720 has not been released for OS release Linux 3.x"


Upgrading kernel of Diagnostic Agent is generally not recommended. In any doubt on any issue being related or not to diagnostic agent kernel version, please raise a support message

Approach 1:-

Diagnostics Agent - How to upgrade SAP Kernel

You are in one of the following cases:

  • After upgrading the operating system you get an error message during the Diagnostics Agent restart like: "OS release <...> is not supported with this kernel (<...>)" or "<...> has not been released for OS release <...> <...>".
  • Your operating system is only released with Kernel 720_EXT.
  • Your operating system is only released with Kernel 721_EXT.

1. Obtaining the Archives

Download the latest SAPEXE archive from the SAP Service Marketplace under:

Software Downloads -> Support Packages and Patches -> A-Z Index -> K -> SAP KERNEL * UNICODE, and rename it from SAPEXE_<XXX>.SAR to SAPEXE.SAR.

If you upgrade from a Diagnostics Agent that was installed using a Diagnostics Agent Standalone Installer, you should expect up to 3 GB additional disk space consumption during and after the upgrade.


2. Preparations

1. Stop all the Diagnostics Agents available on your host.

2. Stop sapstartsrv

On UNIX: kill -2 <PID of sapstartsrv>

3. Remove any IPC objects that still exist (Unix only)

  Cleanipc <instance no> remove

3. Importing the new kernel on UNIX

Copy the kernel into a temporary directory <newkernel>.

1. Log on as user<dasid>adm and switch to the directory /usr/sap/<DASID>/SYS/exe/uc/<platform>

2. Save the sdiagag.lst file if it exists (from the <platform> directory)

3. Recommend saving the old kernel before deploying the new kernel.

4. Delete all of the files from the <platform> directory, including the subdirectories. This ensures that there are no remaining files from the earlier release.

    • ATTENTION: Make sure you are in directory /usr/sap/<DASID>/SYS/exe/uc/<platform>
      Execute: rm -rf *

5. Create a new <platform> directory and navigate to this directory to restore the sdiagag.lst file saved in step 2 (if it exists).

6. Unpack the new kernel in the <platform> directory:

           SAPCAR -xvf <new kernel>/SAPEXE.SAR

7. Switch to the Diagnostics Agent instance exe directory /usr/sap/<DASID>/SMDA<XX>/exe and save the sapjvm* files and directories.

8. Delete all content from Diagnostics Agent instance exe directory.

    • ATTENTION: Make sure you are in directory /usr/sap/<DASID>/SMDA<XX>/exe
      Execute: rm -rf *

9. Restore the sapjvm* files and directories you saved in step 7.

10. Since executables from the local instance executable directories may already be executed during the start, before sapcpe runs, perform an initial copy of the executables:

           cd /usr/sap/<DASID>/SMDA<XX>/work
sapcpe pf=/usr/sap/<DASID>/SYS/profile/<DASID> _SMDA<XX>_<hostname>

Approach 2:-

Diagnostics Agent - How to perform Agent Replacement

To replace a Diagnostics Agent, install a new Diagnostics Agent, and uninstall the previous Diagnostics Agent. This procedure can be relevant in the following scenarios:

  • Replace a Diagnostics Agent, which has problems that cannot be easily resolved.
  • “Upgrade” a Diagnostics Agent system, e.g.
  • Install a new Diagnostics Agent using a newer installer and a newer kernel, and get a Diagnostics Agent that has a new SAP JVM and a new SAP Kernel.
  • uninstall the previous Diagnostics Agent and Reset the server name in SOLMAN.

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

2192841 - Status propagated from Technical Instance, Database or Host is incorrect







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


Filter Blog

By author:
By date:
By tag: