1 4 5 6 7 8 37 Previous Next

SAP Solution Manager

548 Posts

Dear followers


I would like to post a video that I presented this month regarding LMDB troubleshooting. I made this presentation using the Meet the Experts framework from SAP.

In this video I showed some points that must be checked in case of issues with LMDB, where to look, what are the most important transactions, how to check and ensure the consistency of SLD and LMDB. The link with this video is available below.




Best Regards

Mateus de Freitas Pedroso






“Select and unmark group id SM-CREATE”




The SolMan 2 Cloud (S2C) Setup (Transaction S2C_SETUP) is the starting point if you plan to Monitor SAP Based Hybrid Solutions in your Solution Manager 7.10 (starting from SP13):

  • DELL Boomi
  • SAP Cloud for Customer (C4C)
  • SAP HANA Cloud Integration (HCI)
  • SAP SuccessFactors
  • SAP Sales and Operations Planning (S&OP) with SP14



This is the prerequisites to Exception Management (EXM) and Interface and Connection Monitoring (ICMon).


Exception Management will collect errors and exceptions directly from your Cloud Service using HTTPS connections.


Interface and Connection Monitoring will integrate these errors into the Monitoring and Alerting Framework. Notifications and Incidents can be automatically created in case an error is occurring in your Cloud Service.

In the previous part 1 blog I described the different filtering attributes which are currently available for the newly launched KPI Catalog in the cloud at

(SAP Service Marketplace login required)



In this blog I want to mention some other features that are part of the catalog.


Full text search



So instead of starting with some filters on different attributes you can also just perform some full text search. In the screenshot above you can see the search for 2 terms 'delivery' and 'billing'. The search engine will then search according to the following priority:

  1. The best search results are those where the search strings can be found in our key figur name itself
  2. The 2nd best results are those where the search strings could be found in the text below the key figure name
  3. The 3rd best results are those where the search strings could be found in the definition text in the detailed section (not shown in this screenshot, this will be handled further down in this blog)


The search is a fuzzy search, so also slight deviations from your search terms 'deliveries' instead of 'delivery' or typos like 'delviery' should be found accordingly. Once you see your search results, then all the filter attributes are adjusted according the limited set of findings.


Multiple filter

Multiple filter.jpg

Probably it is self-understood for yourself, but besides the full text search and the single filtering, it is of course also possible to set multiple filters, e.g. filtering on all key figures which are 'backlog' key figures in 'ERP' and belong to 'sales'. If you then click on some key figure of interest, then you get to see some additional details.



Details Overview

Detail overview.jpg

If you click on one search result, then you see all the assigned properties/attributes and you still see the (business) text description of the key figure on the next page. This text shall give you an idea what business problem can be realted to the measurement and some key figures even mention a possible business risk/impact.


Details Definition


Detail definition.jpg


The details definition section provides a more technical text description (priority 3 for the full text search mentioned above). This text should roughly describe (on table and field basis) the logic of the underlying data collection.


Details Technical

Detail technical.jpg


This last detail section describes the technical details, which output fields you can expect in the result list of the data collection ('Fieldlist') and which input parameters are available ('Filters') during the design time when you want to schedule/start the data collection.



If you have further questions, remarks or suggestions then please post them as remarks in this blog or send an email to bpimp@sap.com.


Further reading

You can find all necessary information about Business Process Analytics in this document. More information on Business Process Improvement for SAP solutions can be found here.


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 and

http://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.

Since June 1, 2015 a new general KPI Catalog is available at (SAP Service Marketplace login required)




to browse through key figure content that SAP ships out-of-the-box. The catalog uses SAPUI5 front end technology and hence can be accessed by any device with any kind of screen resolution from anywhere in the world with internet connection.


In its first version the current content of the catalog consists of key figures that were developed for Business Process Analytics and Business Process Monitoring in SAP Solution Manager, but key figures from other applications shall follow. Today the catalog "only" contains 562 different key figures as several hundred key figures (especially related to SAP APO and industry specific ones) are not yet included.


UPDATE: Since July 7 also the industry specific and SAP APO content is part of the catalog and the available key figures displayed in the catalog hence increased to 696.


Compared to the MS PowerPoint presentation (SMP login required) that was used so far to list all our key figures, the content in the KPI Catalog is not yet complete...but this will happen over time. Also compared to the MS PowerPoint, the new cloud catalog has many advantages that shall be described in this blog...actually there are so many things to cover that the blog is split into 2 parts to not overload this one single blog. This first blog will describe the different available filter criteria. The second blog will focus on the full text search capabilities and the available detail information.


One big advantage of the KPI Catalog is that you can filter for key figures according to different dimensions/attributes.


Filter according to Application Area

Appl area.jpg

The application areas "roughly correlate" to the traditional SAP modules, e.g. 'Manufacturing' relates to PP or PP-PI. But an application area can also comprise different modules across different products, e.g. 'Sales' relates to SD in ERP as well as CRM Sales or 'Sourcing & Procurement' covers MM in ERP as well as SRM self-service procurement.


Filter according to Business Goal Area

Business goal.jpg

As most of the Business Process Analytics key figure content was designed to support Business Process Improvement for SAP solutions activities, we took the most typical business goals that customers want to improve and used those goals as additional attribute for the key figure content. So if you are trying to reduce the costs in your Financial Shared Service Center and set the filter accordingly you should see key figures that can support such activities based on project experience from previous years.


Filter according to Category



In my blog about the 5 main key figure types, I described in 2013 how we categorize our content. Meanwhile we got a new category about Master Data related checks. All those categories are now available for selection so that you can wuickly find those key figures of a certain type of interest to you.


Filter according to End to End (E2E) business process


E2E process.jpg

Especially if you left behind the thinking in traditioanl SAP modules (application areas) and rather think of a business process from end to end, then this filter possibilty should be to your liking. If you filter for a process like Procure to Pay, then you should see SRM content related to shopping carts, purchase orders, confirmations, invoices as well as ERP content related to planned orders (type NB), purchase requisitions, purchase orders, MM invoices and even FI-AP related open items or payments.


Filter according to Industry Solution


Most of our standard out-of-the-box content is good enough to be used no matter what industry you are working in. But here and there, there are industry specifics that can only be covered in industry specific content. This content is currently not yet in the catalog, but shall be available soon, e.g. for Automotive, AFS, Banking, Retail or Utilities.

Filter according to Product



You can also filter the key figure content specific to the respective SAP BusinessSuite component, i.e. ERP, CRM, SRM or SCM. The later content for Supply Chain Management (SCM) is not yet  in the catalog, but should follow soon.


Filter according to Usage



Perhaps the least interesting filter is about Usage. This filter should only indicate the following. In general all key figures work for Business Process Analytics and Business Process Monitoring (--> usage 'Business Process Analytics'), except a few (often rather technical key figures), which are only available for Business Process Monitoring but not for Business Process Analytics (--> usage 'Business Process Monitoring').


Filter according to New / Updated


Like any nice catalog, we wanted to share insghts what is (relatively) new or which content was significantly enhanced lately (updated). In this first version of the catalog these attributes are related to the latest key figure shipment with ST-A/PI 01R support package 1. The status attributes will then change once the next ST-A/PI 01S will be shipped.


If you have further questions, remarks or suggestions then please post them as remarks in this blog or send an email to bpimp@sap.com.


The second blog about full text search capabilities and the available detail information can be found here in part 2.


Further reading

You can find all necessary information about Business Process Analytics in this document. More information on Business Process Improvement for SAP solutions can be found here.


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 and

http://wiki.sdn.sap.com/wiki/display/SM/FAQ+Business+Process+Analytics respectively.

If, for some reasons, you have to change the MetricCollectionDefinition.xml for some agents, make sure, you do not use any XML Pretty Printer (like Notepad++ with XML add-on). According my tests, the SAPControlWSCollector interprets added \n and \r (by the pretty printer), although these characters are outside the CDATA area.


You'll notice gray metrics in technical monitoring as well as following errors within the diagnostics agent's protocol, it a MetricCollectionDefinition.xml was formated using an XML Pretty Printer and uploaded to a Diagnostics Agent.


[MAIJobObserver] ERROR occurred for metric collection 00000000000000000002[com.sap.smd.mai.model.collector.SAPControlWSCollector].
com.sap.smd.mai.model.collector.CollectorException: [SAPControlWSCollector.collect] Connection to SAPControl Web Service failed. Collector : [SAPControlWSCollector]
Id: 00000000000000000002, SID:
, instance number:

at com.sap.smd.mai.model.collector.SAPControlWSCollector.collect(SAPControlWSCollector.java:147)
at com.sap.smd.mai.job.MetricJobRunner.run(MetricJobRunner.java:32)
at com.sap.smd.server.exec.TaskRunner.run(TaskRunner.java:46)
at com.sap.smd.server.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:781)
at java.lang.Thread.run(Thread.java:761)
Caused by: java.rmi.RemoteException: [WSConnectorFactory] Illegal sid

at com.sap.smd.agent.plugin.connectors.webservice.WSConnectorFactory.configureSAPStartSrvEndPoint(WSConnectorFactory.java:237)
at com.sap.smd.mai.model.collector.SAPControlWSCollector.connect(SAPControlWSCollector.java:504)
at com.sap.smd.mai.model.collector.SAPControlWSCollector.collect(SAPControlWSCollector.java:145)
... 4 more

This is at leasst valid for any Diagnostics Agent >7.40.

Job Monitoring – Notes to be implemented

About Job Monitoring:

The Job Monitoring is used for the proactive monitoring of business critical jobs/ BW Process Chains to ensure the business is running smooth. The following technical objects can be monitored with Solution Manager 7.1 SP12,


  • ABAP Jobs
  • BW process Chains
  • Business Objects Jobs
  • Data Services Jobs


The provision of configuring the Jobs/ Process Chains from Managed System as well as from external scheduler (Central Process Scheduler powered by Redwood) is available with SP12. The Job Monitoring is well integrated in the below entry points,


  • Technical Monitoring
  • Business Process Monitoring
  • Job Management




State-full Data CollectorsThis will avoid the grey alerts which would result in multiple/ duplicate email notifications. The intelligent scheduling algorithm written   in the Managed System would fetch the appropriate Job Instances and report to Solution Manager.
Elegant Monitoring UIThe Monitoring UI which renders the active Job Monitored Objects with the list of Job Instances
Reporting UIThe Status and Performance overview of a job can be visualized here which is populated from the BW Reporting store
Pattern based jobsPattern based jobs can be configured in Job Monitoring (For example, SPA*, HR*)



Please make sure the notes that needs to be implemented in Solution Manager and Managed System are implemented. Its MANDATORY to have all the notes.


Notes to be implemented in Solution Manager System,

Please choose any one of the note below based on your Solution Manager SP,


Solution Manager SP

OSS Note








Notes to be Implemented in Managed (satellite) system,

ST-PI Release

Notes to be implemented

< ST-PI 2008_1_* SP09


= ST-PI 2008_1_* SP09


= ST-PI 2008_1_* SP10


= ST-PI 2008_1_* SP11 & ST-PI 740 SP1


= ST-PI 2008_1_* SP11 or SP12 &
ST-PI 740 SP1 or SP2


= ST-PI 2008_1_* SP 12 or SP13 &
ST-PI 740 SP 2 or SP3



It is highly recommended to keep software component ST-PI at the latest support package level (see SAP Note 539977) in Managed System as well as in the Solution Manager system. New corrections can be provided for the latest two support package levels. The data collector changes provided in higher support packages are downward compatible e.g. a Solution Manager on ST 710 SP 12 can call a data collector in a managed system with ST-PI 2008_1_* SP 13.


ST-A/PI Version

OSS Note

ST-A/PI 01M and 01N







Once all the aforementioned notes are implemented in Solution Manager system and Managed System, the issues in the data collection would be solved.

This blog will list all the steps to be followed here covering how we can customize the Alert Description in Technical Monitoring workcenter  without any ABAP Development.


There are lot of customers where this requirement pops up so I thought may be I will share the simple steps to achieve this requirement without any development(ABAP) effort.


Requirement - In technical monitoring workcenter, we can see a lot of alerts stating same message like "Oracle Data not Available" or ABAP system not available" for all the configured or monitored systems.




Thus, for  a big list of systems where we need to filter on managed object column or create a custom query to get a system specific alert. So question arises - Is it possible to modify the subjet of an alert and include the ID/SID of the System in the subject of ALERT Itself.


Answer is Yes it is possible and let us know see how it can be achieved.


Step 1 - Create a Custom Template


In solman_setup transaction, kindly choose the Technical Monitoring ->System Monitoring Wizard and then navigate to ORACLE(or relevant database template) for modification of database alerts.



Now Click the button EXPERT MODE.




Click CREATE CUSTOM TEMPLATE button and then provide a name for your individual Production System etc( Please note that we are going to create a system specific template)



Now save it in a Transport Request and Package( here I have used $tmp only without any TR as don't want to transport.)




Step 2 - Adapt the Subject for Alert description.


Choose METRICS,EVENTS, ALERTS HIERARCHY tab and then click on Change Setting Tab




On the above screen, choose the relevant alert for description change etc and then in the Name field we can add SID XXX (e.g.) as per requirement.


Save the changes.


Step 3 - Activate the new Template


Now choose the step 6 - SETUP MONITORING



Further use Apply and Activate button to apply new configuration template.




Now if we visit our Technical Monitoring workcenter, it is possible to notice alert with respective System SIDs in the subject and no more filtering is required at all.




Also, in the dashboard the specific system, we can see all the Alerts with our custom description.




This is really an interesting standard customizing option which is giving us lot of flexibility to improve the usage of Solution Manager Technical Monitoring and we can also do whole bunch of other things here but restricting to topic here.


Another interesting topic is discussed below where we can see the steps to configure Alerts description in emails triggered via these alerts.

How To Configure -  Alert Description in Technical Monitoring Alert Emails (Notifications)

SAP Solution Manager 7.2 as per Market reports, was scheduled to be available in market, by 2015 end, but now has been postponed to probably, 2016 Q2. Looking forward to some large scale changes, to be introduced this time. Here I am trying to put in all the information I gathered from different sources.


Would like to state that this blog is an output of different study materials and sources, and can be a bit different from the planned final delivery.


  • 7.1 was IT/Operations focused, so, to balance it, SolMan 7.2 is more “Business Processes Oriented”, with a goal of involving more and more Business Process Experts.


  • In 7.1, you can’t use Solution Documentation without a landscape, (you have to maintain logical component in solar t-codes). For 7.2, SAP want to decouple the documentation from the actual landscape.


  • Out of several concepts of Solution Manager, for Solution Documentation in SolMan 7.1, we have 2- Project and Solution. You need to create a Project and a Solution (later, if you transfer your documentation, from an Implementation Project to a Maintenance Project), if you want to document anything in SolMan 7.1. Solution Manager 7.2 is expected to remove this issue by integrating Projects and Solution, and introducing One Common directory for Business Process documentation.


  • Now, we have something called, RDS (Rapid Deployment Solution) Content to replace the backbone of all Non-technical SolMan functionalities- Business Process Repository. Another way of SAP to lay more stress on Rapid Deployment Solutions.


  • SAP has decided to get rid of SOLAR Transactions in 7.2 that form the foundation of Solution Documentation functionality, till 7.1, and are used to create, manage and do some reporting on your documentation project. In their place, SAP is introducing two mains views: The Solution Landscape UI, and the Solution Documentation UI.


  • In 7.1, Documentation functionality of Solution Manager offers a 3 levels hierarchy: Scenarios, Business Process and Process Steps. Now, when SOLAR transactions are not there anymore, with 3 levels still there, SAP gives the option to Add as many levels (boxes) to it.


  • If you want to maintain your different documentations without affecting your productive solution, even if you don't have the implementation/maintenance projects anymore (Remember the concepts of Project and Solution, explained above?),


  • 7.2 adds a new layer of Solution Documentation & Change Request Management, by automatically making your maintenance documentation productive, the moment your ticket turns productive.


  • There are some/more Management options going to be introduced in Solution Documentation and Change Request Management, by SAP. We might get some new transactions types for IT and Business Requirements.


  • Number of logical components also, might also be getting reduced.

Dear All,


I would like to share one of my experience with SAP OS/DB Migration check session - Self Service using Solution Manager. As confirmed by SAP, our client's Solution Manager fulfill the requirement to generate Migration check service as Self service, I have generated service check session with SolMan system. Below are the steps followed.

1.     Pre-requisites

               - Recent EWA report for the Satellite system


2.     Update service content

               Logon to Solution Manager system and execute t-code AGS_UPDATE





          Select Register Service

          Select flag for OS/DB MIG Analysis Session (GA_MIGR & GA_MI_GP)




          Download Service Content. Wait for content to download from marketplace.




          Apply updates



3.     Create Self Service

          Execute T-code: SOLMAN_WORKCENTER

          Tab SAP Engagement and Service Delivery -> Services

          Select Create




          Activate Self-service OS/DB migration service with below steps

              Reference SAP Note: 2013680 - GoingLive Analysis not listed as a Self Service in Solution Manager





          Select SAP GoingLive Check and active this option.

          Navigate to AGS_UPDATE - Register Service and place a check mark next to GA_SP & GA_SP_GP. Save your change.

          Navigate back to AGS_UPDATE and ensure you download and apply the updates. All the lights need to be green.

          Run the steps again in the Work Center and you will now have the Self Service listed




          Execute T-code: SOLMAN_WORKCENTER

          Tab SAP Engagement and Service Delivery -> Services

          Select Create








          Enter the session planned date




          Assign contacts exists in Solution Manager system









               You will get pop-up windows in which provide your last EWA report and quick prepare steps.












4. OS/DB Migration Analysis – Prepare


               Now we are able to see session created. Click on "Check in Guided procedure". Answer the questionnaire related to OS/DB migration project.




                    Select the product planned for Migration







                    Specify the source hardware




                    Specify the target hardware




                    Answer the initial questions considering future requirement




                    Specify the other systems involved in the current landscape




                    Enter the technical data of system landscape




                    Specify the project schedule dates







                    Finish prepare session




If any correction required in any of the above details, goto initial screen of prepare phase and review and correct the information prior to report planned date.


Rest of the steps follows similar to EWA report generation. Migration check report will be sent from Solution Manager to the recipients mentioned in the procedure.


Same like Prepare phase follow the steps for Go-live report after migration of Production system

Once you’ve tackled challenge one, getting your Suite on HANA system registered properly into SAP Solution Manager, the next challenge arises, getting the right packages selected through the maintenance optimizer (or landscape planner) to implement SFIN 2.0.


If you’ve got SFIN 1.0 then SFIN 2.0 is visible under add-ons. Without SFIN 1.0 (so just ERP 6), neither SFIN 1.0 nor SFIN 2.0 was visible for me under add-ons. Instead it is visible through support package stack application instead (in a nutshell, screenshots below).


I didn't really see any information source mentioning this and this can be confusing for SAP Basis administrators so I decided to post this small blog.


Without SFIN 1.0, select Support Package Stacks

Click Continue


Select stack level which is applicable for SFIN 2.0

Keep an eye on SAP note 2117481 - Release Information Note: SAP Simple Finance, on-premise edition 1503 for this purpose

Select Applications for FIN 700

Click Continue


Click Continue


Select SAP Simple Finance 2.0 which is named SAP SFINANCIALS 1503 (released on 15/03) and click Apply


There are also related (updated) components for SAP Fiori and SAP Smart Business for SFIN 2.0 which you should include:


Note that moving your Suite on HANA system to S/4HANA SFIN 2.0 is not just a technical process, you need functional preparation before even doing any technical steps (except for SAP note implementation). Please read through all available documentation and SAP notes carefully before jumping into SUM.

     Recently I was in discussion with prospective customer, they are having a very vast landscape and have many interfaces across systems, they are looking for sustainable application  support, I was explain the components of SolMan and how Business Process operations  will helps them in their day to day business. They have asked me below questions during the discussion and I felt that they are very important from a business angel and this should be known to everyone hence I have decided to write this blog.


Do we need to implement Business process Monitoring is it value the investment?


Implementing BPM will help in protecting your initial investment by stabilizing your system faster.

If your systems are not stable and you see disturbance in your regular process because of failures in interfaces and / or background processes indicates that BPM has to be setup.


This is more relevant for solutions which are just live or which are still evolving.


Can we setup Business Process Improvement along with Monitoring ?


When the business process are stable you can look for business process improvement, these are basically long processed documents based on the planned date but are still open e.g. open sales orders of last year.


These deviations are caused by :

1. Wrong configuration

2. Poor master data maintenance

3. User training gap


In general most of the SAP customers will have it difficult to activate the application specific part of business process monitoring  directly with sensible threshold values because of above deviations. So its suggested to first set up Business Process Paralytics for these and clear the backlog’s, later on move to regular monitoring for these to have a control on backlogs.


These can be monitored using application specific monitors which are part of BPM.


When to implement BPA ?


BPA is an enhancement to BPM. When your business processes are stable and you want most of initial investment & achieve optimum.

BPA is used to improve the business process efficiency, we can set up a business KPI and measure it using BPA.


If your are not able to meet business KPI’s or want to improve lead time of your process e.g. complete OTC cycle in 4 hours. All these KPI’s can be set and monitored in BPA.


BPA will collect application specific data and stores in info cubes of SolMan for analysis.


When do we need to setup cross database comparison ?


If your solution is spread across multiple systems be it SAP or non-SAP and the data exchange takes place across systems, then we need a check to ensure data consistency.


Interface monitoring is already checking for failures so again why i need one more level of check ?


Interface monitoring will also do the same activity but only for the given time frame. Data consistency management should be setup as an additional safety net to discover inconsistencies that have occurred due to other causes like update termination, ABAP dump during update etc.

Hope this will be useful and will add some knowledge to readers.

Hello everyone! In this post, I hope to add some clarity and demystify how to create custom mail forms for ChaRM. There are a few posts on the topic, however I was not able to find all of the information that I needed in one place. With this post, I hope to make it easier for you to use Mail Forms.


In this scenario, we are generating mails forms in ChaRM for transaction types, ZMCR and in the Change Documents.


This post contains the following sections:

1. Creating custom fields to appear in the mail form

2. Maintain Attribute Contents for Mail Forms

3. Create a BADI to populate the fields

4. Create a Mail Forms containing standard and custom fields.

5. To maintain the HTML in the Mail Form directly

6. Add special fields to the form like….

     a) Insert a Company Logo

     b) Insert a hyperlink the the ChaRM

     c) Text Element Conditions

7. Test your changes

8. Update the Action and Conditions.



So here we go.  All screen shots are from 7.1 SP13.

Step 1) Creating custom fields to appear in the mail form

Create a custom structure containing the fields needed in your mail form. For example, this one contains business partners, textbox contents, and other fields.



Step 2) Maintain Attribute Contents for Mail Forms*

SPRO -> Customer Relationship Management -> Marketing -> Marketing Planning and Champaign Management -> Personalized
Mail -> Maintain Attribute Contexts for Mail Forms,


Create an attribute that will reference the new structure with “With no Marketing Attributes” and type = Not Relevant.



Select the new Attribute and assign the new structure selecting All Fields…


When you view the fields assigned, all of the fields in the structure should be displayed.

Note: I did encounter an issue when I was adding additional fields to the structure after it was in use. They did not always appear immediately in this list. This was because table CRMC_IM_FIELDS maintained via the view was not being updated on save. This took some trial and error. I needed to delete the attribute and re-add it and reactivate the table. It finally worked, but you may need patience. Another time when I updated the structure, the changes were immediately shown. Weird.


Step 3) Create a BADI to populate the fields

SPRO -> Customer Relationship Management -> Marketing -> Marketing Planning and Champaign Management -> Campaign Execution -> Badi: Maintain Additional Attributes for Mail Form Attribute Contents

This will create a BADI for definition CRM_IM_ADD_DATA_BADI. Assign the filter value to the name of the Attribute created in Step 2. Assign no type to the filter.



Here were the Attributes needed in the Class..



Here are the Types needed….



In method IF_EX_CRM_IM_ADD_DATA_BADI~CRM_IM_BPSELE, add the logic to populate the fields in the structure.

Being general, here is some high level logic. I trimmed out a lot of the logic for brevity, just so you would get the idea. But, if you have specific questions about how I populated by specific fields on my form, let me know and I’ll share more.


DATA:     lv_tabname           TYPE tabname,

lv_fieldname         tYPE fieldname,
ls_index             type SYTABIX,
ls_TJ30T             type tj30t,
ls_ct_att_value_temp type line of CRMT_IM_NAME_VALUE_TAB,
ls_ext_reference     type CRMT_PO_NUMBER_UC,

data: lt_tsocm_cr_context type table of tsocm_cr_context,
ls_tsocm_cr_context type tsocm_cr_context.

FIELD SYMBOLS:<fs_table_buffer>   TYPE ty_tables,               
<fs_att_value>      TYPE crmt_im_name_value,
<fs_table>          TYPE table,           
<fs_field>          TYPE any,
<fs_value>          TYPE any.

                 lc_CR_number        type string value 'CRMS_SRQM_GEN_FIELDS-CRM_SRQM_NUMBER',
                 lc_textid_longdesc  type TDID value 'CR01',

* 1) filter check
  If flt_val-SCENARIO ne lc_filtername.

* 2) ChaRM header data
  clear: ls_CRMD_ORDERADM_H.
  read table ct_att_values into ls_ct_att_value_temp with key name = lc_CR_number.
  if sy-subrc = 0.
    ls_cr = ls_ct_att_value_temp-value.

* 2b) Read CR/CD record
  select single * from CRMD_ORDERADM_H into ls_CRMD_ORDERADM_H where object_id = ls_cr.

* 2c) Read context
    when lc_CR. "RfC
* 2d) CR scope data
      SELECT * FROM tsocm_cr_context INTO TABLE lt_tsocm_cr_context
               WHERE guid = ls_CRMD_ORDERADM_H-guid.

    when others. "CDs
* 2e) CD scope data
      SELECT * FROM tsocm_cr_context INTO TABLE lt_tsocm_cr_context
               WHERE created_guid = ls_CRMD_ORDERADM_H-guid.  "for CD guid

* 3) For all variables passed
  LOOP AT ct_att_values ASSIGNING <fs_att_value>.
    ls_index = sy-tabix.

* 3a) See if the field name is already passed to badi
    SPLIT <fs_att_value>-name AT '-' INTO lv_tabname lv_fieldname.
    READ TABLE mt_tables WITH KEY table_name = lv_tabname ASSIGNING <fs_table_buffer>.

    IF sy-subrc = 0.
      ASSIGN <fs_table_buffer>-table_content->* TO <fs_table>.

      READ TABLE <fs_table> WITH KEY (lc_product_guid) = is_bp_act-obj_guid ASSIGNING <fs_field>.
      IF sy-subrc <> 0.

      ASSIGN COMPONENT lv_fieldname OF STRUCTURE <fs_field> TO <fs_value>.
      IF sy-subrc = 0.
        <fs_att_value>-value = <fs_value>.

* 4) If field is not already passed, read table to populate
      CASE lv_fieldname.
        when 'EXT_REFERENCE'. "external refencence
          SELECT single po_number_uc FROM crmd_order_index INTO ls_ext_reference
                                     WHERE header = ls_CRMD_ORDERADM_H-guid.
          if ls_ext_reference is not initial.
            <fs_att_value>-value = ls_ext_reference.
            MODIFY ct_att_values FROM <fs_att_value> INDEX ls_index TRANSPORTING value.

        when 'PROJECT_ID'. "Project assigned to CR. There's only one per CR
          LOOP AT lt_tsocm_cr_context INTO ls_tsocm_cr_context where PROJECT_ID is not initial.
            <fs_att_value>-VALUE = ls_tsocm_cr_context-project_id.
          MODIFY ct_att_values FROM <fs_att_value> INDEX ls_index TRANSPORTING value.
        when 'TEXT_LONG_DESC'.           "Text box - long description
          clear ls_text_value.
            EXPORTING P_GUID     = ls_CRMD_ORDERADM_H-guid
      P_TEXTTYPE = lc_textid_longdesc
            IMPORTING PT_TEXTS   = ls_text_value.

          <fs_att_value>-VALUE = ls_text_value.
          MODIFY ct_att_values FROM <fs_att_value> INDEX ls_index TRANSPORTING value.


Step 4)  Create the Mail Forms.
Tcode SM_CRM -> business role ZSOLMANPRO -> Service Operations. Create -> Mail Form (under section Search).



Select to create a new Mail Form and update the header fields…



The field Attribute Context will control the fields that are available for selection.  In my form, fields from standard attributes and from the custom attributes are needed.
To get some of the standard fields, I set the Attribute Context to Service Request Attributes.


Select Add Attributes.


Select the field needed and Insert…



Then, to add the custom fields, update the the Attribute Context to the new custom attibute that was added in Step 2....


Select the Add Attribute button again and change the Attribute Category to Additional Fields to see the custom fields. 

Select the field and insert.

As you add fields, the form will be displayed in WYSIWYG (what you see is what you get) format …


Step 5) To maintain the HTML
You may want to maintain the HTML directly, for example to format the fields into table columns so the labels and values up nicely.  To do that, select DESIGN <->SOURCE to toggle back and forth between the HTML and WYSIWYG screens….


If you are not comfortable with HTML, don’t fear it here! Just start with the one generated automatically by the WYSIWYG setup. 

To keep the sections easier to read, I inserted documentation lines like this… <!-- ROW STATUS -->

If you want to format the fields into table columns, here some logic to get you started. 
1) <table class="Data3"> indicates the name of the table, so you can have several tables in your form, if you want. This small part of my html has three tables.
2) <tr> and </tr> indicate the start and end to a table row. 
3) <td and </td> indicate the start and end to a table column.


This small part of the html will show the ChaRM status, the ChaRM document number, and the Multi Level categorization assigned….


<table class="Data3">
<td class="Data3"><font color="black" size="2"><strong><font face="Arial">Status</font></strong></font></td>
<td class="Data3"><span style='font-family: "Arial",sans-serif;'><strong><font size="2">                 </font></strong></span> <font color="red" size="2"><span style='font-family: "Arial",sans-serif;'><input dir="ltr" id="%SAP_CRMS_SRQM_GEN_FIELDS-CRM_SRQM_STATUS" value="Status"></span></font></td>
<h2><font size="3"><u>ChaRM Detail</u></font></h2>
<font face="Arial"><!-- ROW3--></font>
<table class="Data">
<tbody><!-- CHARM NO -->
<td class="Data"><font color="black" size="2"><strong><font face="Arial">ChaRM ID</font></strong></font></td>
<td class="Data"><font color="black" size="2"><span style='font-family: "Arial",sans-serif;'><input dir="ltr" id="%SAP_CRMS_SRQM_GEN_FIELDS-CRM_SRQM_NUMBER" value="Service Request ID"></span></font></td>
<table class="DataCat">
<td class="DataCat"><font color="black" size="2"><span style='font-family: "Arial",sans-serif;'><strong>Categorization     </strong></span></font></td>
<td class="DataCat"><span style='font-family: "Arial",sans-serif;'><font color="black" size="2"><input dir="ltr" id="%SAP_CRMS_SRQM_GEN_FIELDS-CRM_SRQM_SUBJ_CAT1" value="Subject Category 1"> /</font></span> <span style='font-family: "Arial",sans-serif;'><font color="red" size="2"><input dir="ltr" id="%SAP_CRMS_SRQM_GEN_FIELDS-CRM_SRQM_SUBJ_CAT2" value="Subject Category 2"> <font color="#000000">/</font></font></span> <span style='font-family: "Arial",sans-serif;'><font color="black" size="2"><input dir="ltr" id="%SAP_CRMS_SRQM_GEN_FIELDS-CRM_SRQM_SUBJ_CAT3" value="Subject Category 3"></font></span></td>


Play around with the html.  It's not as difficult as it looks.   Also, if you miss an end indicator, for example, the tool will try to fix the html automatically. Toggle back and forth between the WYSIWYG and HTML to see your changes and the auto changes.


Step 6) Add special fields to the form….
a) Insert a Company Logo.
Select Insert Picture and browse for the JPG of the logo to insert…

b) Insert a hyperlink the the ChaRM


c) Create a new Text Element to be display in Production
I have a hyperlink to open the ChaRM document in my mail form. Since the hyperlink for the Development and Production systems will differ, you’ll want to control which is displayed. There are a couple of ways to do that.  One way to create the URL hyperlink to work in SolMan production is to update, create a new Text Element and create conditions to check the source SolMan system ID.



Cut and paste the HTML from the original Text Element into the new Text Element.
Return to the WYSIWYG format and remove the original hyperlink that was copied…



Create a new hyperlink for the production system…


Update URL color if needed.

Since two Text Elements now exist, you need to add conditions to determine with each will be used.  Select EDIT STRUCTURE to create the Mail Conditions.




Select the Attribute Context that will be used to determine the condition. In my scenario, I have a custom attribute that was created for the SolMan system id and populated in my BADI.  Select the original Text Element and INSERT….

Select to assign the attribute …


Select the field and INSERT…

Enter the System ID for the SolMan development system.  You can add additional conditions if needed.



Select the other Text Element (e.g for production) and enter those conditions as needed….


When finished, select BACK…


Step 7) Test Changes after updating the HTML

On the WYSIWYG screen, select TEST SEND & PREVIEW (at the top) and select SAVE.

Step 8) Maintain the Actions / Conditions

Locate the email action for the form. Verify the method assigned is SEND_MAIL_WITH_MAIL_FORMS.

Set the method parameter “Mail template name” to match Mail Form created in the UI (Note that it is case sensitive).

Update the conditions to generate the form when needed.




Here is the resulting email in Outlook. (I did remove the logo and adjusted format a bit manually so it would fit in the screen shot better, but you get the idea.



Thank you for reading this long post! There was a lot to cover.   I think I covered everything.  If you find that I missed a part or something should have more detail, let me know and I’ll update the post.  


Have a great day!!!

1. Log in to Solution manager system.


2. Access the Tcode SOLAR_PROJECT_ADMIN


3. then click on the CREATE PROJECT

create project.png

4. then enter the name of the project and the type of the project and then ok button

proj det.png

     Implementaion type of project is creating project from scratch or you can use the template from template project.

     Template is for global rollout.

     Optimization is for doing any customizing


5. now in the new screen select the language and add the title to the project which makes us save the project

lang n title.png

person responsible will be by default the person who creates the project. if you want any other person you can assign in this page. so that he will be the admin for the project.

6. then click save

7. now in the popup screen give the details where your documents for the projects will be saved. and the click the TICK MARK


this is how you create a project.

Don't miss a chance to get the latest insights around SAP Solution Manager, Application Lifecycle Management solutions and QAS at SAPPHIRE NOW.


Test Automation with SAP Solution Manager 7.1 using Component Based Test Automation (CBTA)

Wednesday, May 6th, 03:00 p.m. - 03:30 p.m.

Location: RT 15

Session ID: RT999

Speakers: Larry Wilson- SAP Solution Manager and ALM Consultant (CoreALM)


Demonstrate the Value of SAP Solution Manager to Your Business for Application Lifecycle Management

Thursday, May 7th , 12:00 p.m. - 12:45 p.m.

Location: Lines of Business Microforum LB221

Session ID: PS25097

Speakers: Labinot Bytyqi- Sr ALM Solutions Architect (CoreALM)


Authorization Design at Almatis

Thursday, May 7th, 08:00 a.m. - 09:00 a.m.

Location: S331A

Session ID: BT1730

Speakers: Marci Braybrooks-Executive Director, SAP Solution Manager (CoreALM), Jerry Kidd- IT Applications Specialist (Almatis)


A Segregation of Duties Solution for the University of Nebraska Lecture Presentation

Thursday, May 7th,  02:00 p.m. - 03:00 p.m.

Location: S320G

Session ID: FI1686

Speakers: Marci Braybrooks-Executive Directory, SAP Solution Manager (CoreALM), Loren Blinde (University of Nebraska), Marlon Fueller (IBIS Prof. Thome AG)


Simplify Business Process Management and Modeling

Tuesday, May 5th, 01:00 p.m. - 01:20 p.m.

Location: SAP Service and Support Center Demo Theater SC507

Session ID: SC20422

Speakers: Matthias Melich, PhD, VP Application Lifecycle Mgmt (SAP)


Put the Quality of Your Software to the Test  Microforum Discussion

Tuesday, May 5th, 2:00 p.m. – 2:45 p.m.

Location: Partner and SME Solutions Center Microforum PS606

Session ID: PS22273

Speakers: Andreas Gloege, Quality Assurance Solutions (SAP)


Test-Drive New Solution Documentation in the Cloud

Wednesday, May 6th, 04:00 p.m. - 04:20 p.m.

Location: SAP Service and Support Center Demo Theater SC507

Session ID: SC20416

Speakers: Matthias Melich, PhD, VP Application Lifecycle Mgmt (SAP)


How Verizon Used Automated Testing to Accelerate Its SAP Implementation

Wednesday, May 6th, 02:30 p.m. - 03:30 p.m.

Location: S331C

Session ID: BT2012

Speakers: Nick Germanotta (Verizon), Bala Thangaraj (Senior Managing Consultant)


Loblaw Boosts Quality and Lowers Costs with Automation and So Can You

Wednesday, May 6th, 03:00 p.m. - 03:20 p.m.

Location: Theater 1

Session ID: PS20813k

Speakers: Mathi Natarajan- Sr Consulting Mgr (Cognizant Technology Solutions), Lindsey Billing- Senior Director IT Quality Assurance (Loblaw Companies Limited)


Tools to Automate, Manage and Gain Efficiencies in Testing

Thursday, May 7th, 08:00 a.m. - 09:00 a.m

Location: S310F

Session ID: PS1162

Speakers: Sam Press- Business Solution Manager (Johns Hopkins)


Demonstrate the Value of SAP Solution Manager to Your Business for Application Lifecycle Management

Thursday, May 7th , 12:00 p.m. - 12:45 p.m.

Location: Lines of Business Microforum LB221

Session ID: PS25097

Speakers: Labinot Bytyqi- Sr ALM Solutions Architect (CoreALM)


Secure the Code That Runs Your Business

Thursday, May 7th, 03:00 p.m. - 03:20 p.m

Location: Partner and SME Solutions Center Demo Theater PS605

Session ID: PS25064

Speakers: Lorie Volpe- Solution Strategist (SAP)



A Day in the Life of Setting up SAP Solution Manager

Thursday, May 7th, 03:30 p.m. - 04:30 p.m

Location: S320B

Session ID: SM240

Speakers: Michael Hawn- Solution Manager (Newmont Mining),Jonathan Bragg-Global SAP Technical and Development Manager (Newmont Mining Corporation)

SAP TDMS for IS Utilities at AES (customer presentation)

Monday, May 4, 2:15-3:15pm

Location: Room S310E

Session ID: IU1082

Speakers: Eduardo Fernando (AES); Peter Keller (SAP)


ASUG SAP TDMS Influence Council Session (supported by Nike)

Tuesday, May 5, 1:45-2:45pm

Location: ASUG Theater A (on show floor)

Session ID: IF2377

Speakers: Michael Wild (Nike); Peter Keller (SAP)


ASUG SAP TDMS Customer Roundtable (supported by AES & Nike)

Wednesday, May 6, 10:30-11:30am

Location: Roundtable #13

Session ID: RT2101

Speakers: Eduardo Fernando (AES); Peter Keller (SAP)


See you at SAPPHIRE!


Filter Blog

By author:
By date:
By tag: