1 4 5 6 7 8 40 Previous Next

SAP Solution Manager

589 Posts

In 2011 the Business Process Operations dashboards were introduced. Those dashboards are especially used to track progress during business process improvement activities. As those dashboards also used by senior management in order to understand where progress is achieved and where it is not it is always a challenge to provide the right level of granularity. Many large companies who are operating all around the globe and where the organization is split into different markets, regions or business units asked how this can be reflected in our dashboards?! The special challenge is typically the fact that the markets or regions are not directly reflected as such in the respective SAP system, i.e. no company code, sales organization or plant represents a specific market or region. Instead a market comprises several different company codes, sales organizations or plants.

 

Since SAP Solution Manager support package 12, this challenge is solved by so called virtual characteristics. With the help of of those virtual characteristics you are now able to build dashboards that provide a global overview about all your markets, e.g. as shown in the dashboard below the data is split between the 4 markets America, Asia, Europe & Japan. Additionally you see one column comprising possible company codes that are not (yet) assigned to any market.

Dashboard overview.png

If you configured some additional parent child relationships between your panels, then a forward navigation is possible. So if you click on the cell for "Open and overdue FI-AR items" in America, then you get to see which company codes are part of the market.

Dashboard details.png

So how can you get your markets, regions shown in your dashboards?

 

Getting virtual characteristics into a dashboard


If you access your setup environment for Business Process Operations dashboards, then you have to assign the respective virtual characteristic on Analytical Key Figure Instance (AKFI) level to a Category or Drilldown dimension.

Use virt char in dashboard.png

 

Now if you look into your SAP Solution Manager you will not see any such virtual characteristic immediately. You have to create those first, before they can be used.


Defining new virtual characteristics

 

If you want to create and define virtual characteristics according to your needs, then please access the BPO reporting infrastructure from within the Business Process Operations work center. As of support package 13 you should find there one tab strip Virtual Characteristics which will help you with some kind guided procedure.

Note: In support package 12 the application was already shipped but not yet linked to the BPO reporting infrastructure UI. Please call https://<server>:<port>/sap/bc/webdynpro/sap/ags_ri_vcharstics?sap-language=EN&sap-wd-configId=AGS_RI_VCHARSTICS_AC01 to access the application.

 

As the data access to the generic Infocube/Twincubes in Business Process Analytics and BPO dashboards happens technically via so called Semantic IDs, you have to create such new Semantic IDs first with the pre-fix ZVIRT. The semantic ID defines as an example whether the value '0001' in parameter 1 is representing plant '0001' or company code '0001' or sales organization '0001'. For our dashboard shown above we defined some new semantic ID 'ZVIRT_MARKET'.

1 define semantic ID.png

In a 2nd step we defined a new virtual characteristic ZVIRT_CHARSTIC_MARKET (the one that we assigned to an AKFI as seen above) and assigned to it the newly created semantic ID. Every virtual characteristic that you want to create, has to start with the pre-fix ZVIRT_CHARSTIC.

 

2 Map virt char and semantic ID.png

In the 3rd step we defined for our new virtual characteristic that the 'concrete values' for our markets are America, Asia, Europe & Japan. Those are the 4 markets displayed on the dashboard at the beginning of this blog.

 

3 create virtual char.png

 

In the 4th and final step we defined for every possible virtual characteristic value which "real values" from the SAP system are comprised, e.g. our market Europe consists of the company codes 3001 to 9999, DK01, FR01 and IT01. In case of sales key figures you would need to define another mapping for Europe which uses semantic ID ERP_VKORG in order to also map which sales organizations belong to market Europe.

 

4 map virtual to real.png

 

In the last step of the guided procedure you have to assign the virtual characteristic to the respective key figure instance where you want to use it. You also have to declare which semantic ID shall be used for the determination of the right virtual characteristic value (e.g. in a sales order item key figure you might have company code, sales org as well as plant information. In the market definition you might have done the assignment for all three semantic IDs ERP_BUKRS, ERP_VKORG, ERP_WERKS. Now in this last assignment step you tell the system which of the three semantic IDs should be taken into account for the exact market determination (in the worst case a plant that is assigned to Japan is pointing to a sales org that is assigned to Europe).

 

Note: If the filtering via virtual characteristics in Business Process Analytics shall also be taken over when jumping into the detail list, then you have to create a corresponding entry in the 5th step of the guided procedure, i.e. create an entry BPM_Detail_List.<key figure>. This double maintenance is supposedly eliminated with support package 15.

 

After this mapping definition and assignment of new virtual characteristics to your respective AKFIs used in the dashboard, you can lean back and enjoy your new dashboards which automatically split your data according to the newly defined markets, regions, business units etc.

 

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.

With SAP Solution Manager 7.1 support package 14 another puzzle piece has been added towards a complete "Business Process Improvement Suite" as I would call it. While we provided Business Process Analytics as the root cause analysis tool in 2010 (meanwhile also available in an ad-hoc version and as native iPad app) and added a dashboard layer on top in 2011, we now shipped a new SAPUI5 application called "Dependency Diagrams".

 

Note: Please refer to SAP note 2228248 in order to learn which steps are recommended when moving from support package 5-13 up to support package 14! Also implement SAP note 2323531 - Corrections Business Process Improvement for SAP Solution Manager 7.1 SP14 - Dependency Diagrams

 

As we ship such a vast KPI content out-of-the-box with close to 1.000 KPIs, customers can easily lose the overview on what is measured and tracked in what way and for what purpose. With the help of the Dependency Diagrams you can build kind of KPI trees where you bring the different KPIs into some logical, hierarchical order. You can visualize the dependency chains of KPIs and get the "picture" updated with your live data.

 

The easiest way to access the new application, is to define a new favorite in the user menu. Just specify BSP application AGS_KPI_TREE and select WebContent/index.html from the value help as start page.

Note: Remember to activate the corresponding BSP service in transaction SICF.

Runtime BSP.png

 

When you then access the application you can select one diagram that must have been defined beforehand, e.g. looking at a diagram about the typical financial business KPI "Days Sales Outstanding (DSO).

 

Initial select.png

 

After selecting the diagram you get to see the root level (here Days Sales Outstanding itself) and the dependent level 1 KPIs. In our example all five level 1 KPIs are collected via Business Process Analytics, i.e. why you see an Analyze-hyperlink which allows a direct forward navigation into Business Process Analytics. The backend data from your SAP BusinessSuite or SAP S/4 HANA system can be shown as count of documents/items (e.g. 241 deliveries or 310 SD invoices) or as one accumulated monetary value (e.g. 2,7 million Euro or 311,3 million USD).

The tiles that you see could be

 

Below SD Orders not billed and Open customer items we see a '+' icon, so we can further expand the tree in those areas.

 

Small tree.png

 

As we know that the majority of billing documents is created via billing run, we put another KPI below the SD Orders not billed. This additional KPI looks specifically at all error messages that were raised during billing due runs. One of the most typical error messages is the problem of incomplete sales order items and hence you can further expand to see Missing fields in SD documents.

Big tree.png

So with the help of this application you can

  • Bring business BW reporting and operational Business Process Analytics data for root cause analysis together in one view
  • Structure your KPIs in meaningful dependency diagrams, so that every manager and subject matter experts understands the leverage that one low level KPI might have on any (business) KPI on top, like DSO.
  • Set threshold values so that the numbers in the tiles get a green, amber or red rating
  • Decide if you put your focus on document numbers or monetary values (and which target currency)
  • Use the forward navigation to get from this overview into the actual root cause analysis with Business Process Analytics.

 

This application can be used on any device and any screen resolution, because of the SAPUI5 user interface. Just access URL

<server>:<port>/sap/bc/ui5_ui5/sap/ags_kpi_tree/index.html#/<technical name of Dependency Diagram>

 

 

Configuration

 

There are no diagram templates shipped with this application. Instead you have to model everything yourself. The configuration has some similarities to the configuration of Business Process Operations dashboards in SAP Solution Manager. So you have to create Analytical Key Figure Instances (AKFIs) first, where you define which data should be displayed from which source and define potential thresholds. Then you model the respective Dependency Diagram / KPI Hierarchy and bring the AKFIs into some logical order.

 

In order to access the configuration application it is easiest to create a new favorite in the user menu. For this specify AGS_RI_KPIHIERARCHY_SETUP as Web Dynpro application.

setup webdynpro.png

If you access the setup environment, there is always just one root. After this you always just specify which AKFI is child of which other AKFI (identified by technical name not description). You can always have more than one child for every parent tile. Based on these parent/child relationships the application calculates the hierarchy level automatically and arranges the tiles from top to bottom.

Diagram setup.png

 

So if yo have Business Process Analytics already up and running in your SAP Solution Manager 7.1 with support package 14, then you should be only a few clicks away from creating your own Dependency Diagram and show it to your management in order to get the budget for your desired business process improvement activities.

 

For more details regarding Best Practices you can refer to a detailed PDF (~15 pages) which is stored at Business Process Improvement - Solution Manager - SCN Wiki

 

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.


AS ABAP SLD registration process:


You should perform ABAP SLD registration by executing transaction RZ70.



2016-01-21_13-19-54.jpg



in case you have problem with SLD_UC registration  (DETAIL: TP SLD_UC not registered!!!!) please consult this link (read comment from vijendar reddy  )!!



AS Java SLD registration process:



The properly configure this service, the following must be done.

Use the Destinations Service to:

 

1. Set up the registration by creating a destination called "SLD_DataSupplier" of type HTTP. Enter the following configuration settings. (Note: The specified user must have the user role "SAP_SLD_DATA_SUPPLIER" or higher on the target SLD Server.)

  • Appropriate URL (http://<host>:<port>)
  • Authentication should be set to BASIC
  • Appropriate User Name and Password

2. Set up the AS Java access to the SLD by creating a destination called "SLD_Client" of type HTTP.

Enter the same configuration settings as in the SLD_DataSupplier destination.

(Note: The specified user must have user role "SAP_SLD_GUEST" or higher. Aditional write access permissions may be required by certain applications. Refer to the corresponding application documentation for SLD access requirements.)



2016-01-21_13-00-43.jpg

 

2016-01-21_13-08-00.jpg

 

2016-01-21_13-09-17.jpg

2016-01-21_13-10-54.jpg

 

2016-01-21_13-11-03.jpg

 

 

Now you can start registration of yours AS Java in the SLD by executing following action:

2016-01-21_13-15-44.jpg

 

 

pls execute red box button

 

2016-01-21_13-16-28.jpg

 

 

At the ned go tyou SLD and check is there your AS JAVA and AS ABAP present/registered !!

 

Happy registering! 

 

BM

Changing the configuration of the Metrics and Alerts in the template and activating the changed settings can be done from front end applications like System Monitoring and Alert Inbox.  This functionality is provided from front end applications to reduce the number of steps in changing the configuration of Metrics and Alerts and to make the configuration change process fast and simple.

 

Note:The functionality mentioned in this blog is specific to Solution Manager 7.2 release. Also please note that when the document is viewed in the PDF format, Red rating icons are shown in dark blue and Yellow rating icons are shown in light blue.

 

 

Procedure for changing the Configuration from Alert Inbox

 

Settings that can be changed for an Alert from Alert Inbox


Following data can be changed for an alert from Alert Inbox.

  • Alert Active/Inactive status
  • Notification variant data
  • Incident variant data
  • Third part Component variant data
  • Auto Reaction variant data
  • Alert Active/Inactive status

 

 

Settings that can be changed for a metric from Alert Inbox

 

  • Metric Active/Inactive status
  • Threshold Type – It can be changed to Info only
  • Threshold Values

 

Scenario 1 – Custom template has been assigned to the managed object and an alert related to the managed object is available in Alert Inbox.

 

       1.     Navigate to Alert Inbox on “System & Application Monitoring” work center.

       2.     Select a record on System Alerts/Database Alerts/Host Alerts query and click “Change Configuration” button.

       3.     The following pop up appears when a custom template has been assigned to the managed object.

1.png

Following data can be changed for an alert from Alert Inbox.

  • Alert Active/Inactive status
  • Notification variant data
  • Incident variant data
  • Third part Component variant data
  • Auto Reaction variant data


Each wok mode is shown as a tab in which the selected alert is active. User can make the changes at the work mode level also.


Options “Apply changes to template <template name>” and “Apply changes on the managed object only” will be displayed on the pop up.


When a Custom template is assigned to the managed object, then user will have the option to change the settings at the managed object level or at the template level.


4.     Make necessary changes and select the option “Apply changes on the managed object only” and click on “Apply Changes” button.

The changes made are applied only at the managed object level.


5.     Select another record on System Alerts/Database Alerts/Host Alerts query where a custom template has been assigned to its managed object and there are no managed object specific settings and click “Change Configuration” button.


6.     Select the option “Apply changes to template <template name>” and click on Apply changes button.

The alert settings will be changed at the template level and the change is reflected for all the managed objects on which this template has been applied. The list of managed objects using the this template can be found on clicking the link “Show affected managed objects” next to the option “Apply changes to template <template name>”


Clicking on the “Close” button without performing any action on the pop up cancels the operation. Functionality is same as mentioned above while changing the configuration of alert from Alert Group details page.

Scenario 2 – SAP template has been assigned to the managed object and an alert related to the managed object is available in Alert Inbox.


                            The following pop up appears when a SAP template has been assigned to the managed object and the user had selected an alert in Alert Inbox and clicked on “Change Configuration” button.


2.png

User will have the option to change the settings only at the managed object level. Make the changes and click on “Apply Changes” button.


If managed object specific settings are maintained for the managed object already and if user wants to make further settings for the alert, then user will have the option to change the settings only at the managed object level.


            Functionality is same as mentioned above while changing the configuration of alert from Alert Group details page.

 

Scenario 3 – Custom template has been assigned to the managed object and the user would like to change the configuration of the metric from Alert Inbox.

 

On the Alert details table select a metric and click on “Change Configuration” button.

3.png

The following pop up appears when a custom template has been assigned to the managed object. All the Active work modes for the metric will be shown as separate tabs.

 

4.png

 

User will have the option to change the settings at the managed object level or at the template level.


Options “Apply changes to template <template name>” and “Apply changes on the managed object only” will be displayed on the pop up.


If the option “Apply changes to the template” is selected, the metric settings will be changed at the template level and the change is reflected for all the managed objects on which this template has been applied. The list of managed objects using the this template can be found on clicking the link “Show Managed objects where the changes take effect” next to the option “Apply changes to template <template name>”


If the option “Apply changes only on the managed object” is selected, changes made will be applicable only for the managed object.


Scenario 4 –SAP template has been assigned to the managed object and the user would like to change the configuration of the metric from Alert Inbox.

 

1.     If a SAP template is assigned to the managed object, then user will have the option to change the settings only at the managed object. Following pop up will be displayed, and the user should click on the “Apply Changes” button after making the specific settings on the pop up. The changes made for the metric will be at the managed object level.

5.png

2. If managed object specific settings are maintained for the metric then user will have the option to change the settings only at the managed object only. Following pop up will be displayed and the user should click on the “Apply Changes” button after changing the settings on the pop up.

 

6.png

Make necessary changes and click on “Apply Changes” button. The changes made are applied only at the managed object level.

 

3. Clicking on the “Close” button without performing any action on the pop up cancels the operation.

 

Procedure for changing the Configuration from System Monitoring

 

Settings that can be changed for a metric from System Monitoring

  • Metric Active/Inactive status
  • Threshold Type – It can be changed to Info only
  • Threshold Values


Scenario 1 – Custom template has been assigned to the managed object and the user would like to change the configuration of the metric from System Monitoring.

1.     Navigate to System Monitoring application on “System & Application Monitoring” work center.

2.     System Monitoring application is launched.


7.png


3.       Click on any tile shown on “Status Overview” panel and navigate to System View.

4.       Click on any Category icon on the tile related to the system and navigate to “System Hierarchy” view.

5.       Hover on a metric in the “Event and Metric” view.


8.png


6.       Click on “Change Configuration” link.


The following pop up appears when a custom template has been assigned to the managed object and no managed object specific settings exist for the metric.

9.png

    • All the Active work modes for the metric will be shown as separate tabs.
    • User will have the option to change the settings at the managed object level or at the template level.


Options “Apply changes to template <template name>” and “Apply changes on the managed object only” will be displayed on the pop up.

If the option “Apply changes to the template” is selected, the metric settings will be changed at the template level and the change is reflected for all the managed objects on which this template has been applied. The list of managed objects using the this template can be found on clicking the link “Show Managed objects where the changes take effect” next to the option “Apply changes to template <template name>”


If the option “Apply changes only on the managed object” is selected, changes made will be applicable only for the managed object.

 

Scenario 2– SAP template has been assigned to the managed object and the user would like to change the configuration of the metric from System Monitoring.

 

    • User will have the option to change the settings only at the managed object. Following pop up will be displayed, and the user should click on the “Apply Changes” button after making the specific settings on the pop up. The changes made for the metric will be at the managed object level.

10.png


    • If managed object specific settings are maintained for the metric already then user will have the option to change the settings only at the managed object only. Following pop up will be displayed and the user should click on the “Apply Changes” button after changing the settings on the pop up.

11.png

Make necessary changes and click on “Apply Changes” button. The changes made are applied only at the managed object level.

Clicking on the “Close” button without performing any action on the pop up cancels the operation.


 


This setting is global for all users!

 

1. Enter Workcenter "customizing mode"

 

Add "&sap-config-mode=X" to the end of the workcenter-URL:

 

Example:

ags_workcenter?sap-client=100&sap-language=DE&sap-config-mode=X

or

ags_workcenter?sap-config-mode=X



2. Right-click on one of the workcenter tab and select "Settings for current Configuration":

step2.png



3. Click on "Tabstrip Control"

step3.png


4. Click on "Re-Sort"

step4.png



5. Define the order of the tabs using the buttons "Up" and "Down"

step5.png

Hi to all,

during SUM deployment of SP01 of Solution Manage 7.2 I run in to problem where SUM process stopped in the process EHP_INCLUSION in the log file SPDA_EHP_INCLUSION.LOG you can find following line:

 

"2WETN607 The import of Prepackages is not allowed in this system"SAPK-74014INSAPGWFND""SAP_GWFND""740"Solman "

 

 

 

What you should do is following :

 

start the report RSSETPACKAGEDEPLOYMENT and put the following

 

for the Software component SAP_GWFND  :

 

- instead of T put P in the Maintenance  Type

 

sum_prob.jpg

 

I hope this was helpful!

ITSM & ChaRM – Reminder / Escalation emails using Date Management (Dates and Durations) Part 3

 

This is the continuation to the Part 1 and Part 2 blogs.

 

ITSM & ChaRM – Reminder / Escalation emails using Date Management (Dates and Durations) Part 1

 

ITSM & ChaRM – Reminder / Escalation emails using Date Management (Dates and Durations) Part 2

 

 

In this part, the Custom Duration field is made available in the Web UI configuration for the relevant document type.

The sample requirement discussed in Blog 1 and 2 is again used for Part 3.This is the sample requirement in context of Part 1/2 of the Blog –

 

When an Incident has been forwarded, the requirement is to send a Reminder/escalation email after a specific wait time if the Status is still unchanged.


 

 

Below are the Steps:


SPRO Configuration to enable the linking of the custom duration to the BTDateSET

blog-3-1.png

blog-3-2.png

 

 

Custom Enhancement has to be created for the Standard component (In my Case it is Incident) AIC_INCIDENT_H. This has to be done before proceeding with the required settings for the Custom Context nodes.

blog-3-3.png

**Refer the Blog by Harshit Kumar for completing the above step**

How To Enhance a Web UI Component in SAP CRM - CRM - SCN Wiki

 

blog-3-4.png

blog-3-5.png

 

Click Continue till reaching ‘Create Links to Custom Controller’ and then

 

blog-3-6.png

blog-3-7.png

 

The BOL relation as shown in the above screenshot is available only if it has been maintained in the SPRO as shown earlier in this document.

 

blog-3-8.png

 

 

The Superclass in the Context node’s Implementation class is changed to CL_CRM_UIU_BT_DATE_CN to handle dates.

blog-3-9.png

 

blog-3-10.png

 

Delete the Check for the errors (Remove the extra Base_Entity_Name attribute from the class) and activate.

blog-3-11.png

 

Log off and Logon to see the Attribute ‘Date’ available under the new custom node.

blog-3-12.png

 

**The Blog from Chand Shaik is used as the base reference for the next few steps**

Adding Date profile's Date type Fields as Context Attribute to the UI component

 

The below steps were done different from that of the blog to match to the DURATION specific requirement.

 

 

In the ‘ON_NEW_FOCUS’ method the replacement code was updated as below to refer the Z_FWDDURA duration created in SPRO date profile.

blog-3-13.png

blog-3-14.png

TIP : ***For Date, it is T and for duration, it is D for lv_category. The LV_date_type is the Date type or the Duration id defined in the Date Profile***

 

The GETTER and SETTER methods were activated for all the attributes below Date attribute (This may not be required- Did this as trial and error for getting troubleshooting ‘Not Bound’ text in the value of the field in the Web UI).

blog-3-15.png

blog-3-16.png

 

The Web UI configuration now will have the Custom node ZFWDDURA.

blog-3-17.png

blog-3-18.png

blog-3-19.png

 

<---------------End of the blog--------------->

ITSM & ChaRM – Reminder / Escalation emails using Date Management (Dates and Durations) Part 2

 

 

This is the continuation to the Part 1 blog -- ITSM & ChaRM – Reminder / Escalation emails using Date Management (Dates and Durations) Part 1

 

In this part the PPF action for the Email is configured for the below sample requirement discussed in Blog 1.

 

This is the sample requirement in context of Part 1 blog --

When an Incident has been forwarded, the requirement is to send a Reminder/escalation email after a specific wait time if the Status is still unchanged.

 

Below are the Steps:


Action Definition:

 

blog-2-1.pngblog-2-2.png

 

Here I have used the Smartforms mail option. If you want to use other email options like HTML mail forms check the blog from  Dolores Correa.

Incident Management and Change Request Manageme... | SCN

 

 

 

Conditions:


The Action for the email will be scheduled when the Status “Forwarded” is set. Below is the schedule action for that.

blog-2-3.png

 

The Email should be ready to be sent when the status is still in “Forwarded” and when the Current date & time is higher than the Maximum time limit.

blog-2-4.png

 

The custom date type parameters for the condition can be identified under the Deadlines set.

blog-2-5.png

 

I have also set the Time of Processing for the action as “Processing using Selection report”.

blog-2-6.png

 

The background job scheduled using Transaction CRMC_ACTION_JOB will handle the execution of the email action. This Job would process the Actions for the Incidents, which currently meets the Start conditions.

blog-2-7.png

 

***I have also written Part 3 blog. If you are interested in displaying the Wait time Duration as an editable field in the Web UI configuration for the relevant document type then you can refer it.***

 

ITSM & ChaRM – Reminder / Escalation emails using Date Management (Dates and Durations) Part 3

ITSM & ChaRM – Reminder / Escalation emails using Date Management (Dates and Durations) Part 1

 

In few of my previous projects, I have come across the requirement to send an Automatic Reminder or Escalation email. This email has to be sent automatically when the allowed time limit exceeds. There are Standard Reminder/ Escalation email Actions available under the Service Request management for SLA escalations. However, for General Reminders/Escalations on delays in Processing, etc., there is No Standard functionality currently available in Solution Manager – ITSM & ChaRM. I hope this blog would help to handle such requirements.

 

I have used a sample requirement for the context of this Blog. It goes like this -- When an Incident has been forwarded, the requirement is to send a Reminder/escalation email after a specific wait time if the Status is still unchanged.

 

Below are the Steps to do this:


Update the applicable Date profile with the Custom date types, date rules, and duration.

blog.png

 

The Custom duration is for saving the Maximum allowed time before the email could be sent.

blog-1-2.png

 

The below date types are for calculating the Clock Start Time and the Time it exceeds the allowed wait period.

blog-1-3.png

 

The Custom date rule is to calculate the maximum allowed/ wait time. In this example, it is for calculating ZFWD_LMT_MAX.

blog-1-4.png

 

The XML code for the date rule is updated as below.

blog-1-5.png

 

***If you want to use a different set of Date rules for your situation then you can refer the Blog written by Deepa Madyalkar in the CRM space Creation of Date rule using XML rules. - CRM - SCN Wiki

 

 

Assign the new Custom date types, date rules and durations to the applicable Date profile.

blog-1-6.png

blog-1-7.png

blog-1-8.png

blog-1-9.png

blog-1-10.png

blog-1-11.png

blog-1-12.png

 

The Duration can be assigned with a Default value (here I have assigned it as 24 hours) if the maximum Time limit is Fixed.

 

In order to maintain the duration as a variable value and make it available for edit in the CRM UI of the document check the ***Part 3 blog***.

 

ITSM & ChaRM – Reminder / Escalation emails using Date Management (Dates and Durations) Part 3

 

blog-1-13.png

 

The Settings related to SLA Escalation can be used for updating the duration.

 

The Current Date and time is assigned to the date type ZFWD_LIMIT when the status is changed to ‘Forwarded’. The below setting will do that. Then based on the date rule and the duration (Z_FWDDURA) the ZFWD_LMT_MAX will be calculated for the trigger point for the escalation or reminder email.

blog-1-14.png

blog-1-15.png

 

***The Configuration related to the PPF Action and conditions for the Escalation or Reminder email are explained in Part 2 blog***

ITSM & ChaRM – Reminder / Escalation emails using Date Management (Dates and Durations) Part 2

Hi All,

 

I am happy and excited to right my first ever blog on this community. I have taken so much from this great community while resolving many issues reading many wonderful blogs. Its time to return back something to help others. I am writing about an experience, which can be described as metric explosion as per CA.

 

How it started ?

Few days back our network team came up with information that network utilization between two servers (one was hosting MII application and other was hosting wily EM) is very very high and resulting into packet loss. Same day we got some alert for high memory utilization for MII application.

 

What was the Error?

While checking the Wily Introscope Agent logs (location /usr/sap/<SID>/SMD<XX>/SMDAgent/temp/IntroscopeAgent.<SID>_<Instance>_server<x>), I found below exception

 

[IntroscopeAgent] IntervalHeartbeat.execute threw executing: Remove Metric Data

java.lang.ArrayIndexOutOfBoundsException: 5047

    at com.wily.util.adt.CanonicalObjectPoolWithKey.removeCanonicalObjectWrapperInternal(CanonicalObjectPoolWithKey.java:357)

    at com.wily.introscope.agent.recording.MetricRecordingAdministrator.removeMetricFromThreadLocalCache(MetricRecordingAdministrator.java:1194)

    at com.wily.introscope.agent.recording.MetricRecordingAdministrator.removeMetricData(MetricRecordingAdministrator.java:1090)

    at com.wily.introscope.agent.recording.RemoveMetricDataWatcher.ITimestampedRunnable_execute(RemoveMetricDataWatcher.java:81)

    at com.wily.util.heartbeat.IntervalHeartbeat$BehaviorNode.execute(IntervalHeartbeat.java:944)

    at com.wily.util.heartbeat.IntervalHeartbeat.executeNextBehaviorAndCalculateSleepTime(IntervalHeartbeat.java:489)

    at com.wily.util.heartbeat.IntervalHeartbeat.access$300(IntervalHeartbeat.java:28)

    at com.wily.util.heartbeat.IntervalHeartbeat$HeartbeatRunnable.run(IntervalHeartbeat.java:665)

    at java.lang.Thread.run(Thread.java:761)

 

I noticed that before this exception , number of current live metrics were in range of 1000-14000, but after the exception number of live metrics started to grow up and reached above one million. (in the same file you can search for logs like below)

 

11/09/15 02:19:03 PM GMT [INFO] [IntroscopeAgent] Number of current, live metrics=1012

12/11/15 03:02:28 PM GMT [INFO] [IntroscopeAgent] Number of current, live metrics=1035158.

 

It was clear to me that this issue is causing high memory and network utilization.

 

On the below mentioned link (From CA support), I was able to find more information about interface mentioned in the exception and what is a metric explosion:

https://support.ca.com/cadocs/0/CA%20Application%20Performance%20Management%209%206-ENU/Bookshelf_Files/HTML/APM--NET%20Agent%20Implementation%20Guide/index.htm?toc.htm?1479622.html?intcmp=searchresultclick&resultnum=1993

 

How it was fixed?

To fixed the problem we restarted the sap java application and it resolved high network and memory utilization.

 

As of now I am not aware of the aware of the permanent solution but I am working on the same. I know there is a memory leak issue with ISAgent version 9.1.0.X but we were using ISAgent 8 when this issue occurred. Will update my blog when I will be having a permanent resolution for the same.

 

Thanks and Regards

Sachin Gupta

!!! Great News from SAP Solution Manager !!!

 

 

SAP Solution Manager 7.2 has started Ramp-Up successfully.

Watch the ramp-up video on YouTube.

 

Please refer to the SAP Help Portal for more information.

Early Knowledge Transfer (formerly known as Ramp-Up Knowledge Transfer) will be available soon at http://support.sap.com/ekt-solutionmanager.

Yes, that's right, automatically updating a system after a product upgrade is possible in SAP Solution Manager since a while now. Unfortunately many customers do not yet have this in place and are still doing everything manually where some automation is possible (not saying it's perfect in other words but the automation can help reduce efforts).


So here goes a small blogs post to hopefully inform more customers, partners, community members that this option exists.


I'm talking about the customizing that can be set in SAP Solution Manager by following the instructions of SAP NOTE 1832868 - Automatic Managed System Adjustment after Product Upgrade


An example:

You've got ERP 6 EHP6 and you update it to ERP 6 EPH7. If your system is well maintained and you don't run into an exception which is not covered (see SAP NOTE 1832868 mentioned above), the LMDB will automatically update the system so it's reflected that it has been updated to EHP7.


Figure out what went wrong


To figure out what went wrong when it doesn't work, you'll need to check the job log of SAP_LMDB_NOTIFY_LDB*


If you don't see much detail in there, you might not yet have SAP NOTE 2211344 - Enhancement of the SAP_LMDB_NOTIFY_LDB job log by detailed error descriptions


CR Content consistency (important)


One of the most common reasons why it would not work are CR content inconsistencies so to avoid those, you should read this blog post  by SAP Mentor Matt Fraser so you know how to check the content so you can keep it consistent.

During this years SAP TechEd season there is also one session ITM104 about "Business Process Improvement for SAP solutions". The session of my colleague Sabine Schmitt in Barcelona got recorded. So if you were not able to attend SAP TechEd, then you can watch the 41 minute session here at

http://events.sap.com/teched/en/session/26544.

 

In this session you

  • learn about the basic ideas behind "Business Process Improvement for SAP solutions"
  • get to see a system demo for Business Process Analytics as root cause analysis tool
  • get a system demo about the newly launched Dependency Diagrams, where you can visualize KPI dependencies
  • get an idea how a new application "Progress Management Board" could look like in some future release.

 

 

For more information on Business Process Analytics you can access the following document http://scn.sap.com/docs/DOC-48233. The Business Process Improvement landing page can be found here http://discover.sap.com/germany-business-process-improvement.

Note: Please view this document in the PDF format to view the complete text.

 

Overview:

Work Mode settings can be maintained for Technical Systems, Technical Instances, Hosts and Databases. The configuration is possible at various levels within the Technical Monitoring set up steps. You can maintain Work Mode Specific settings for monitoring on custom template level, alert level, metric level and at the managed object specific settings level.

 

Purpose of the blog:

There are various options available for Incidents, Notifications, Third-Party, Auto-Reaction which can be selected for each workmode. The focus would be on explaining what each option is about in detail. Note:  The functionality mentioned in this blog is applicable to Solution Manager 7.1 SP08 and above SPs and to Solution Manager 7.2 release.

 

Level 1: Custom Template - Template Settings

1. Navigate to Step 4 of System Monitoring scenario on SAP Solution Manager Configuration work center.

2. Select a Custom template.

3. Select the “Template Settings” tab. Options shown in the table below are available for the fields “Automatic Incident Creation”, “Automatic Notification”, and “Third-Party Components” under section “Default Settings”.

1.png

Field

Option

Meaning

Automatic Incident Creation

Active

Automatic Incident Creation is Active at the template level and the user enters the required details.

Inactive

Automatic Incident Creation is Inactive at the template level

Global Settings (Active/Inactive)

If the option "Global Settings (Active) is shown,  it means that Automatic Incident creation is active at the Global level and the template will be using the settings maintained at the Global level

If the option "Global Settings (Inactive) is shown, it means that Automatic Incident creation is inactive at the Global level and the template will be using the settings maintained at the Global level

 

The behavior mentioned in the table above is same for Automatic Notification Creation and Third-Party Components.

 

Note: Global level settings can be viewed on Step 2.3 Default Settings.

 

4. Options shown in the table below are available for the fields “Automatic Incident Creation”, “Automatic Notification”, and “Third-Party Components” under section “Work Mode Functions”.

 

2.png

Workmode

Column

Option

Meaning

Planned Downtime

Automatic Incident Creation

Active

Automatic Incident Creation is Active for the specific workmode at the template level and the user enters the required details. The details entered are only specific to this workmode and is not applicable to other workmodes.

Inactive

Automatic Incident Creation is Inactive at the template level for the specific workmode

Global Settings (Active/Inactive)

If the option "Global Settings (Active) is shown,  it means that Automatic Incident creation is active at the Global level and the workmode at the template will be using the settings maintained at the Global level

If the option "Global Settings (Inactive) is shown, it means that Automatic Incident creation is inactive at the Global level and the work mode at the template will be using the settings maintained at the Global level

Use Default Settings

Settings maintained under the "Default Settings" section will be used by the workmode. By default the value that is selected for each work mode is "Use Default Settings". User can change the option to others if required.

 

 

 

 

The behavior mentioned in the table above is same for Automatic Notification Creation and Third-Party Components.

 

Level 2: Custom template Alert level

 

5. Select the Alerts tab and select an Alert.

 

Options shown in the table below are available for the fields “Automatic Incident Creation”, “Automatic Notification”, “Third-Party Components”, and “Auto Reactions” under section "Default Alert Settings" in the respective tabs (Incidents, Notifications, Third-Party Components and Auto-Reactions).

 

Field

Option

Meaning

Automatic Incident Creation

Active

Automatic Incident Creation is Active at the alert level and the user can enter the required details.

Inactive

Automatic Incident Creation is Inactive at the alert level.

Template Settings (Active/Inactive)

If the option "Template Settings (Active) is shown,  it means that Automatic Incident creation is active at the template level and the alert will be using the settings maintained at the template level. By Default the option "Template Settings" will be selected. User can change the option if he wishes.

If the option "Template Settings (Inactive) is shown, it means that Automatic Incident creation is inactive at the template level and the alert will be using the settings maintained at the template level.

By Default the option "Template Settings" will be selected. User can change the option if he wishes.

 

 

Options shown in the table below are available for the fields “Automatic Incident Creation”, “Automatic Notification”, “Third-Party Components”, and “Auto Reactions” under section “Work-Mode-Specific Alert Settings”.

 

Workmode

Column

Option

Meaning

Planned Downtime

Automatic Incident Creation

Active

Automatic Incident Creation is Active for the specific workmode at the alert level and the user enters the required details. The details entered are only specific to this workmode and is not applicable to other workmodes.

Inactive

Automatic Incident Creation is Inactive at the alert level for the specific workmode

Template Settings (Active/Inactive)

If the option "Template Settings (Active) is shown,  it means that Automatic Incident creation is active at the Template level and the workmode at the alert level will be using the settings maintained at the template level

If the option "Template Settings (Inactive) is shown,  it means that Automatic Incident creation is inactive at the Template level and the workmode at the alert level will be using the settings maintained at the template level

Use Default Settings

Settings maintained under the "Default Alert Settings" section will be used by the workmode. By default the value that is selected for each work mode is "Use Default Settings". User can change the option to others if required.

 

 

The behaviour mentioned in the table above is same for Automatic Notification Creation, Third-Party Components and Auto Reactions.

 

Note: The option Template Settings (Active/Inactive) will not be available for Auto Reactions.

 

Level 3: Managed Object Settings - Template level

 

6. Navigate to Define Scope step.

7. Select a managed object and navigate to Setup Monitoring step.

8. Select the managed object in the table and click on the link “Maintain MO-Specific Settings”.

9. Select the tab “Managed Object Settings”.

10. Options shown in the table below are available for the fields “Automatic Incident Creation”, “Automatic Notification”, and “Third-Party Components” under section “Default Settings”.

 

13.png

Field

Option

Meaning

Automatic Incident Creation

Active

Automatic Incident Creation is Active at the managed object settings template level and the user enters the required details.

Inactive

Automatic Incident Creation is Inactive at the managed object settings  template level

Source Template Settings

If the option " Source Template Settings” is selected, it means that the value which was entered on the Incidents tab of the template which was assigned to the managed object would be used.                                        

By Default the option “Source Template Settings” is selected. User can change to another option if he wishes to.

 

14. Options shown in the table below are available for the fields “Automatic Incident Creation”, “Automatic Notification”, and “Third-Party Components” under section “Work Mode Functions”.

15.png

Workmode

Column

Option

Meaning

Planned Downtime

Automatic Incident Creation

Active

Automatic Incident Creation is Active for the specific workmode at the managed object settings template level and the user enters the required details. The details entered are only specific to this workmode and is not applicable to other workmodes.

Inactive

Automatic Incident Creation is Inactive at the managed object settings template level for the specific workmode

Source Template Settings

If the option " Source Template Settings” is selected, it means that the value which was entered on the Incidents tab of the template which was assigned to the managed object would be used.                                        

Use Default Settings

Settings maintained under the "Default Settings" section of the managed object settings template will be used by the workmode. By default the value that is selected for each work mode is "Use Default Settings". User can change the option to others if required.

The behavior mentioned in the table above is same for Automatic Notification Creation and Third-Party Components.

 

Level 4: Managed Object Settings - Alert level

 

12. Select the Alerts tab and select an Alert.

 

Options shown in the table below are available for the fields “Automatic Incident Creation”, “Automatic Notification”, “Third-Party Components”, and “Auto Reactions” under section "Default Alert Settings" on the respective tabs (Incidents, Notifications, Third-Party Components and Auto Reactions).


Field

Option

Meaning

Automatic Incident Creation

Active

Automatic Incident Creation is Active at the managed object settings alert level and the user enters the required details.

Inactive

Automatic Incident Creation is Inactive at the managed object settings  alert level

Source Template Settings

 

Source template always refers to the template which was assigned to the managed object.

If the option " Source Template Settings” is selected, it means that the value which was entered in the Incidents tab of the alert of the source template would be used.                                        

By Default the option “Source Template Settings” is selected. User can change to another option if he wishes to.

Managed Object Settings (Active/Inactive)

If the option "Managed Object Settings (Active) is shown,  it means that Automatic Incident creation is active at the Managed Object Settings template level and the alert level will be using the settings maintained at the Managed Object Settings template level.

If the option "Template Settings (Inactive) is shown,  it means that Automatic Incident creation is inactive at the Managed Object Settings Template level and the alert level will be using the settings maintained at the Managed Object Settings template level.


Options shown in the table below are available for the fields “Automatic Incident Creation”, “Automatic Notification”, “Third-Party Components”, and “Auto Reactions” under section “Work-Mode-Specific Alert Settings”.

 

17.png

 

 

 

Workmode

Column

Option

Meaning

Planned Downtime

Automatic Incident Creation

Active

Automatic Incident Creation is Active for the specific workmode at the alert level and the user enters the required details. The details entered are only specific to this workmode and is not applicable to other workmodes.

Inactive

Automatic Incident Creation is Inactive at the alert level for the specific workmode

Managed Object  Settings (Active/Inactive)

If the option "Managed Object Settings (Active) is shown,  it means that Automatic Incident creation is active at the Managed Object Settings template level and the workmode at the alert level will be using the settings maintained at the Managed Object Settings template level.

If the option "Template Settings (Inactive) is shown,  it means that Automatic Incident creation is inactive at the Managed Object Settings Template level and the workmode at the alert level will be using the settings maintained at the Managed Object Settings template level.

Source Template Settings

 

Source template always refers to the template which was assigned to the managed object. If the option "Source Template Settings” is selected, it means that the value which was entered on the Incidents tab for the workmode at the alert level of the source template would be used.  By default, the value “Source Template Settings” is used.                                      

Use Default Settings

Settings maintained under the "Default Alert Settings" section will be used by the workmode

The behaviour mentioned in the table above is same for Automatic Notification Creation, Third-Party Components and Auto Reactions.

 

Note: The option “Managed Object Settings (Active/Inactive)” will not be available for Auto Reactions.

 

Further explanation related to the option “Source Template Settings” .

Assuming the component “SV-SMG-MON-ALR-CFG” is used at the Alert level for the work mode Planned Downtime in the source template.

When the option “Source Template Settings” is used for the workmode at the alert level on the Managed Object template, then the value which would be used by the alert for the Planned Downtime would be SV-SMG-MON-ALR-CFG.

This blog is based on the EXP session I gave at SAP TechED Barcelona. On request of SAP TechED attendees and community members who couldn't be present at the session this blog post provides the information I have shared.


The week before SAP TechED Barcelona, I've spent a week at SAP Rot / SAP Walldorf to learn and discuss around SAP Solution Manager 7.2. Thanks to SAP for organizing this event to bring partners who focus on SAP Solution Manager up to date. You can find tweets and screenshots on twitter on hashtag #solman and #sapsoled2015. You can have a look at a condensed storify with screenshots here.


Product versions

 

SolMan72architecture.jpg

Source: https://service.sap.com/roadmaps "Solution Manager roadmap"

 

SAP Solution Manager 7.1 will reach end of maintenance at 31/12/2017 due to the fact that the AS ABAP stack is running on an old SAP Netweaver version (7.0 EHP2) and the AS JAVA stack is using an old SAPJVM 4.1 version. Those old versions run out of maintenance so an upgrade is needed.


SAP Solution Manager 7.2 will run on SAP Netweaver 7.40 (both AS ABAP and AS JAVA) and has the capability to run on AnyDB (Sybase ASE, Oracle, MS SQL, ...) or on SAP HANA. The CRM component goes from CRM 7.0 EHP1 to CRM 7.0 EHP3.


SAP HANA capabilities


SAP HANA can be placed under SAP Solution Manager 7.2 without the need for a SAP HANA license. Ofcourse customers still have to pay themselves for the appropriate hardware. This is a really nice incentive from SAP if you ask me. It can help introduce SAP HANA into organisations that do not yet run SAP HANA and provide the opportunity to get used to it. That way the organisation can prepare to support SAP HANA also for Business Suite and beyond.


It's not yet an S/4 HANA like solution so the data structures are not yet simplified in scenarios that were already existing. It's more like Suite on HANA if one would compare the current state of capabilities and what is leveraged out of the box to the ERP side of town.


This means SAP HANA brings data size reduction comparable to moving from ERP on AnyDB to SAP HANA which is somewhere between factor 4 and 10 (if the source database was uncompressed. Factor 4 is more common) depending on what kind of data is stored (unique entries versus recurring entries which can be compressed to a larger extent).


Further, you can leverage search capabilities of SAP HANA so customers who have a SAP TREX in place for SAP Solution Manager could simplify their landscape and no longer need to use SAP TREX for search capabilities.


In terms of speed, you'll notice it most in reporting capabilities since that selects data rather than scenarios where lots of inserts take place. However, the non optimized embedded BW is still present so in the end the system doesn't unleash SAP HANA performance out of the box. Lots of inserts (for example in Technical Monitoring) is typical for non optimized / simplified scenarios and therefor you won't notice a big performance difference there.


So far, standard SAP scenario's do not specifically require SAP HANA so you could also run on AnyDB (Sybase ASE, Oracle, MS SQL,...) without missing out on scenario's and features at this point in time (SAP HANA specific scenario's might be on the horizon though).


Celonis, a SAP HANA start-up has created a process mining application on top of SAP HANA. This can be leveraged by ITSM to check the process flow of incident tickets. This can help the customer identify where time is lost and where tickets are ping-ponged in between different teams. This can then lead to further optimizations of support provided. I didn't get lots of details on this yet but I assume this does comes with a pricetag since it's created by a start-up company and can be used on top of standard SAP


More scenario's that leverage SAP HANA will come afterwards. SAP has also started work on a next generation SAP Solution Manager (S/4 HANA principals being applied to simplify data, do direct operational reporting, get rid of indexes etc). but that's in a really early stage still.

Moving from SolMan 7.1 to SolMan 7.2 - technical


Upgrade using SUM / Dual Stack split using SWPM


From a technical point of view, an upgrade and dual stack split takes place. This means that you'll end up with two SID's, one for the AS ABAP part and one for the AS JAVA part.


What is AS JAVA still used for?


AS JAVA is still used by SolMan 7.2 for diagnostics agent connectivity and root cause analysis. In theory and probably also practice you could leave it out of the CHARM Solution Manager landscape if you've got two Solution Manager landscapes, one for Technical Monitoring and one for ITSM and CHARM which is not uncommon for large customers.


AS JAVA could also serve the purpose of local SLD for SAP Solution Manager although in general many administrators seem to prefer a central SLD nowadays with a higher Netweaver stack version and seperated maintenance cycles.


Sometimes AS JAVA of SAP Solution Manager is used for Adobe Document Services (ADS) to serve the ERP landscape. I've seen this mostly at smaller customers who do not create a seperate AS JAVA instance for that purpose.


Database options


When you look at the database you also have multiple options:


One database, with two schema's, one schema for AS ABAP and one schema for AS JAVA where both have AS stacks their own SID or a dedicated database for each.


Moving to SAP HANA


When you also move to SAP HANA you perform an OS/DB migration (can be done using SUM DMO for the ABAP stack) and also here you have the above options available. In the HANA Enterprise Cloud (HEC) at SAP, most customers who have been testing SolMan 7.2 SP0 have AS ABAP running against SAP HANA and AS JAVA running against Sybase ASE. However, as noted in the previous "chapter", you could run both instances against SAP HANA using a separate database schema.

Moving from SolMan 7.1 to SolMan 7.2 - functional


There are a lot of changes in SolMan 7.2 so this means SAP partners and customers need to have an understanding of these conceptual changes. These are discusses already in other blog posts and video's that you can access through the SAP Solution Manager space on SCN.


Timeline


Timing wise, SP1 is the first ramp-up version, SP2 is expected around March 2016 and SP3 (General Availability) around July 2016.


User experience

userexperience.jpg

Source: https://service.sap.com/roadmaps "Solution Manager roadmap"


In SAP Solution Manager 7.1 there was a big mixture of different UI technologies: SAPgui, WebDynpro, Flash, Silverlight etc... Not exactly what one would expect or enjoy in general.


This has been improved a lot from what I was already able to access in SolMan 7.2. The start point for the end-user is Fiori launchpad. You'll notice that you different functionality or scenario's are available as tiles there.


Someone asked me the question how handy that really is and asked me what if you want to switch to an ABAP transaction? I found it enjoyable to work through Fiori launchpad and new UI's. It felt rather refreshing. If you want to combine the ability of calling up ABAP transactions and accessing Fiori or SAPUI5 apps, you can leverage Business Client 6 which has just recently released and can handle multiple UI types in a single front-end client.


This new user experience also has some effects on the architecture. If you would also utilize SAP HANA specific applications (running on XS for example) and you would want to combine tiles you need a Web Dispatcher to dispatch to the correct application server.


Test drive SAP Solution Manager 7.2 in the cloud (coming soon)

 

SAPCAL.jpg

SAP is planning to release an image of the SAP Solution Manager 7.2 ramp-up (SP1) to SAP Cloud Appliance Library (SAP CAL). This will allows customers / partners to test drive the different SP stacks of SAP Solution Manager 7.2 ramp-up versions (on SAP HANA even) in cloud environments that are provisioned through SAP CAL (Amazon AWS for example).


Another great initiative of SAP if you ask me, I personally very much like SAP CAL / Amazon AWS capabilities to test drive products of SAP. Expected delivery would be in December.


SAP Solution Manager and SAP Mentors


The SAP Mentors are SAP's knights of the round table if you would express it in Camelot terms. We gather up around the table with SAP to discuss where SAP is going in all product area's of SAP. SAP Mentors are elected through the community (by community members, SAP, SAP Mentors and externals even).


We've got really close connections to the SAP Solution Manager executives and teams so we continuously provide feedback and collaboration on new products and services. We also represent the community at large so we value SAP Community Network and welcome feedback from community members as well as other sources like User Groups. We notice trends through our engagements and bring those forward to SAP.

Actions

Filter Blog

By author:
By date:
By tag: