To begin with , I will briefly describe the problem we faced and why we faced it and why am I talking about this file SAPAgentConfig.xml.

 

We have a landscape consisting of SAP MDM 7.1 SP10 systems. MDM has components like Master data server(MDS), Master data import server (MDIS) and master data syndication server (MDSS).

 

From technical/Basis perspective they are technical instances which can be installed separately or on a central system. You can read more about MDM in MDM related documentation.

 

We have installed them on one physical server but each component runs on separate logical host( for high availability purposes).To explain MDS was on running on logical host s1, MDIS on IS and MDSS on SS.

 

 

We have installed diagnostics agent on the physical server and have configured Agent-on-fly feature, so for each logical host-name running on the server a diagnostics agent forks a separate process.

 

 

So we have in fact 4 diagnostics agents running. 1 for physical host and 3 for logical host names.Here's more detail about Agent-on-the-fly.

 

Diagnostics Agent and HA Support - SAP Solution Manager Setup - SCN Wiki

 

So, we registered MDM in solman SLD, did the Manged system configuration and configured technical monitoring and also introscope host adapter setup.(IHA)


I have bolded introscope host adapter step, because this is where all the problem started and resolution is found. The monitoring never worked as expected as the metrics were mostly grey or reported incorrect values.

 

This was because, most of the MDM related monitoring metric values are pulled out from Wily EM by Solman. In wily EM, we had four agents registered while doing IHA setup.1 for physical and three agents for logical hostnames ,

 

For MDM application, a NCS library is used, which collects the monitoring and system related data of a MDM instance and sends it to the diagnostics agent which pushes it to Wily EM.


"Native Component Supportability (NCS): is an SAP utility (installed automatically with MDM) that you can configure on the application to produce performance metrics and scoping information in CA Wily Introscope for analysis  The settings are contained in the NCS configuration file"


The same NCS library concept is also used in BI/BOBJ, SAP business objects applications.

 

NCS library uses a configuration file ncs.conf, in which we can mention the agent host-name and agent port where the NCS library can sent the data to.

 

1259828 - Diagnostics Setup for MDM: Manual Steps in Managed System

 

Each MDS instance, MDS, MDIS and MDSS has a separate ncs.conf file to send the data to separate diagnostics agent.

We had configured agent hostname value to the logical host for respective MDM instance but the port was same 59818 in the files. Although the logical hostnames were different but they are all in fact on the same server and sending data to same port.

 

What we expected was that the monitoring related values for MDS, MDIS and MDSS should be reported under its respective agent in Wily EM ( S1, IS and SS), but it was being reported under only one agent and each time we restarted the MDM system or SMD agent the metrics would switch to some other agent. If it was under S1 it would move to IS or SS.

 

This was because, when we do IHA configuration it configures Wily Host Agent.It is a Diagnostics Agent application that analyzes and makes performance data available in Wily Introscope. Its configuration is stored in the SapAgentConfig.xml file . In this file is configured a port which is used for this data transfer. The file cannot be edited manually directly at OS level.Its encrypted.

 

It connects the diagnostics agent to Wily EM and is used by diagnostics agent to send monitoring data to Wily EM

 

You can access this file in

 

SMD agent administration application in solution manager system (http://hostname:port/smd/AgentAdmin)

 

Agent Administration -> Application Configuration -> com.sap.smd.agent.application.wilyhost -> Application Resources; select SAPAgentConfig.xml for the relevant diagnostics agent and export the file to your machine.

 

 

You can then open the file and change the default port (59818) to some other free port value and upload the file again using the same console and restart the agent. You need to do this for all the logical agents , now all the agents will have separate listening port to receive the Wily EM monitoring data from diagnostics agent.

 

So, if we assigned the S1 diagnostics agent the port 59816 , in the corresponding ncs.conf file for MDS , I will maintain this port only and if for IS the port is 59817 , maintain the same in ncs.conf file for MDIS and if for SS the port is 59819 maintain same in ncs.conf file for MDSS.

 

We need to restart the MDM application after making this change.

 

Once this was achieved, we had all the 4 agents listening on different ports for the incoming monitoring related data to be reported in Wily EM and we had proper segregation and the data was being correctly reported under the respective agent node in WIly EM as below.

 

 

Now the , Metrics in SOLMAN were working corrrectly, as it was able to pull values from the Wily EM and report it in technical monitoring. We were mainly concerned with Repository Loading status to report if a repository goes down and wanted this to work. We had opened call with SAP and after due follow up were able to put together the missing pieces of information and make it work.

 

 

I wanted to share the knowledge, so that others having similar setup consisting of logical hostnames on one physical host, having different applications running (MDM or other SAP application) on it are able to use this information to configure monitoring in solution manager.

 

Thanks

Amit

ASUG.pngDCODE.png

 

This is from the ASUG Solution Manager community; parts are reprinted with their permission:

 

SAP TechEd && d-code Pre-Conference Session: Express Delivery to Your Business with SAP Solution Manager

 

Deliver Software Solutions Fast with Design Thinking and Agile Software Engineering

 

Businesses are continually challenged with managing their IT complexity, a point proven by their high level of IT spending. The majority of IT budgets typically are allotted for hardware and services, leaving very little that is available for innovation.

 

Businesses in any market have bold dreams to expand to new markets, and are under extreme pressure to transform complex solutions quickly. SAP customers need to innovate and overhaul their traditional business models nimbly to compete in their marketplaces. However, adopting innovations can cause risks and additional costs for existing operations.

 

To meet consumer demands, and adopt new business models and partnerships, companies demand SAP solutions that address their business challenges, while identify risks in an early phase in order to get a solid decision base to consider during implementation.

 

In this session, presenters will demonstrate how the Pace-Layered Architecture Strategy*, introduced by Gartner Inc., will prove that safe adoption of innovation is indeed possible. You will discover how to achieve rapid innovation while making your corporate rollouts a non-event for the business.

 

Design-thinking concepts enable you to best understand new business models, and lead discussions concerning desirability, viability, and feasibility within the business transformation office. These concepts translate the new business models into an IT solution addressing these needs exactly.

 

Also, presenters will discuss how it's no longer necessary to rely on traditional waterfall approaches, and how you can leverage agile software engineering methods to capture the big picture in prototypes quickly to ultimately build the right things and build the things right.

 

Throughout this session, you will learn and take away how SAP Solution Manager is well-equipped to serve as the central delivery platform to facilitate the rapid prototyping of new solutions, business models and capabilities to:

 

• Document system landscapes and end-to-end applications

• Manage the release strategy to filter business requirements

• Improve, reduce, and avoid custom code required to support business processes

• Reduce testing efforts by only testing what has changed, and by automated tests

• Carefully manage dual-track system landscapes

 

Join us for this new, exciting and interactive session.  Register here.

 

You’re ensured to take away key information on how to build differentiating and innovative software solutions on top of SAP’s existing industry best practices, leveraging SAP Solution Manager, providing lower time to market, and enable tangible value realization for your company.

 

John Krakowski also says “The technical system landscape supported by SAP Solution Manager is a key element of a release strategy.  We’ll review the options and advantages of a dual track transport landscape to best support the lines of business and provide a flexible and stable production end user environment”.


**UPDATE** John Krakowski says "At our pre-conference, directly interact with special guest, Helmut Fieres, SAP AG, SVP responsible for development, SAP Solution Manager, about the next release SAP Solution Manager 7.2!"

 

Useful Links


Solution Manager 7.1 SPS12

SAP ALM NA RIG expert has provided the following key learning SCN blogs that address common customer questions about projects and the Business Process Change Analyzer in SAP Solution Manager.On July 18, 2014, a new ST-A/PI plug-in 01R was released to customers together with SAP Solution Manager support package 12

 

Related:

ASUG at SAP TechEd && d-code Las Vegas - 2014 Blog Collection

ASUG Pre-conference Sessions

ASUG is has opened registration for pre-conferences session at SAP TechEd && d-code on Monday, October, 20th  - see Announcing ASUG SAP TechEd d-code Pre-Conference Sessions

 

See Your fast track to the SAP HANA Cloud Platform at the ASUG pre-conference posted by Rui Nogueira

 

Join SAP's John Krakowski for  ASUG Pre-Conference SAP TechEd && d-code 2014 Express Delivery to Your Business with SAP Solution Manager

 

 

Join ASUG at SAP TechEd && d-code

OCTOBER 20-24
Venetian/Palazzo Congress Center


ASUG SAP d-code Las Vegas sessions are now published - for a complete listing please see here

 

 

 

http://scn.sap.com/servlet/JiveServlet/showImage/38-111039-503678/asug.png

 

Join ASUG in October

Status dependent import control is a part of the flexible ChaRM. It was introduced with Solman 7.1 Sp5.

The functionality it offers is to perform import only to transports that belong to specific Change document that has a specific status.

So it changes the import behavior of the usually used IMPORT_PROJECT_ALL as it performs an import subset of all selected Transports (relevant because of their corresponding Change documents status). The import method of this subset is IMPORT_ALL again but in comparison to the usual behavior of IMPORT_PROJECT_ALL it offers the possibility to have some TRs stay in buffer.

As this means what you have tested is not necessarily the same as what you will be going to transport it's absolutely mandatory to switch on the Downgrade Protection (DGP). Technically DGP is no prerequisite for status dependent Import, but logically it is. So please always switch on DGP first before you start to use status dependent import.

 

You can activate the DGP here in SPRO:

SPRO.jpg

Choose "Globally Activate Cross-System Object Lock and Downgrade Protection" in the popup.

Then Activate DGP here:

DGP.jpg

Please be aware that Cross-System Object Locking is active, this is prerequisite for DGP activation.

 

Now let's switch to the customizing of status dependant Import. After DGP was enabled you can start to setup this here:

Flex.jpg

As said above, what you want to reach is to have transports only being part of an import for the project if the corresponding Change document has a certain status.

e.g. you want to make sure Urgent Changes Transports will only be consolidated and part of the project import if the status is "Authorized for production".

btw. this setting makes perfect sense and is highly recommended as with this setting we can avoid that for Urgent Changes the consolidation Import with the project happens earlier than the original transport which normally is triggered in dialog directly from the Urgent Change document. So in this scenario status dependant import control even improves the standard behavior. :-)

But as you also want to make sure that the consolidation happens after the transport was triggered in dialog from the Urgent correction you must not forget to also maintain the status of the urgent change that comes in sequence after "Authorized for production".

In Standard SMHF Urgent change process flow that's: "Imported into Production"; "confirmed"; "completed".

It's crucial that you do not forget to maintain these extra values, as if not available the Urgent change consolidation with the project import will never happen and the transports that are waiting for re-import will be staying in the buffer for ever!

You can maintain status values for transaction types in the customizing for a combination of Project, System, Client and  System Role.

So you could setup the status dependant import e.g. for a specific project only. Or make a difference in system role for the behavior of import to QAS system in comparison to PRD system.

If you want to set it up in a generic way, meaning it should be available for all projects, systems and clients, you can use wildcards "*"

 

wild.jpg

only the system role has to be specified. (in this case p = production)

Going further you can then maintain the transaction types and status values for that combination of project, system, client and system role were you activated the "Import by status of selected elements".

For our example that looks like this:

UC.jpg

status.jpg

 

To get the full picture of all standard transaction types for status dependant import to production systems it looks like this:

all.jpg

So it also includes into the import all Transports form Normal changes (SMMJ) in status E0009 = "successfully tested" and Defect Correction (SMTM) in status E0009 = "confirmed".

Withe the customizing including theses status values for the standard transaction types you ensure you do not forget consolidation for Urgent changes nor the corrections from defects.

Of course you can also use that customizing for you own newly created status in the Z or Y namespace.

Good luck!

logo ifg solution manager w 25 prct.png

 

Established in 2011, the International Focus Group (IFG) for SAP Solution Manager (SSM) is a network of 14 user groups designed to create a platform for the exchange of best practices in the application of SAP Solution Manager. In collaboration with SAP AG information is disseminated on the best use of current versions of SAP Solution Manager and the proposed way forward.

The IFG for SAP Solution Manager is chaired by Wim Kiebert, Tata Steel Europe, who is also the chairman of the Solution Manager Special Interest Group of the Dutch SAP Users Group. The SAP representative is Dr Matthias Melich.

 

Our mission

The mission of the IFG for SSM is to establish the collaboration between the various SAP user groups in the area of SAP Solution Manager. In addition to the collaboration, exchange of experiences and knowledge, our goals are to combine and strengthen the feedback and influencing towards SAP. Target of our group is to support the various SSM focus groups as part of their national user groups (but not to replace them in any way).

 

How to Participate and join

 

Webinars

Webinars can be followed by everybody. For inviting people to join we will use the following channels;

  • Invites send via the National User Groups that are member of the IFG
  • Invites via web (this SCN blog, facebook groups, LindedIn groups) with a registration link
    • NEW!: Invite SAP Webinar Roadmap SAP Solution Manager 7.2 for 2014-11-24.
      Join this webinar to make the right choses for the future. See attached file to participate in the webinar or go directly to the Registration Link: Roadmap SAP Solution Manager 7.2
  • Sharing the webinar calendar

 

Core team meetings

IFG core team meetings can be followed by core team members. Core team members can be a representative from a National User Group or if there is no National User Group active you can contact us how to join. For checking the available user groups see link below.

 

Other user groups are very welcome to join our initiative.

In case of questions or ideas do not hesitate to contact us.

 

Useful Links

Hi all,

 

Last month, our customer gave us a request - "they wanted to see Time Recording assignment of their Key User screen". It sounds easy and in your mind, you think that it's very logical requirement, customer want to see Time Recording for each ticket, so they could manage the effort for their requests which had been sent to VAR, what they are paying for.

 

As usual, users used Personalize button for editing default Work Center page of their own and they just need to be assigned by right authorization. Such as with this case, authorization object SM_TIMEREP need to be maintained under Key User roles. But the issue is even I maintained that authorization object in Key User roles, there are no Time Recording assignment block is available for assigning to Key User from Personalize. So, what's the issue really?

 

I have try a lot of things, such as mixed roles between Processor and Key User, to find exactly which role responsible for Time Recording assignment block. But all combinations are failed, there are no specified roles for Time Recording assignment block, but Business Role SOLMANPRO. And follow SAP standard, we could not assign Business Role SOLMANPRO to Key User.

 

It's really a big challenge, but fortunately, SAP has provided us a useful tool to customize Work Center Page based on build-in UI Component. You can use that tool via Tcode BSP_WD_CMPWB - UI Component Workbench.

 

Now is the time to identify which UI Component is being used by Key User when they open a ticket.

 

1. Logon to ITSM under Key User account and open a In-progress ticket. Why? Because you cannot edit a Confirmed ticket, and you cannot identify UI Component if you cannot edit a ticket.

 

2. Click Edit, and put cursor in any box.

 

 

3. Press F2 and a Technical Data windows will appear. Pay attention into UI Component field.

 

 

Now you know, the UI Component is being used by Key User when they open a ticket is AIC_IM_REQ_H.

 

Similarly, I logon as a Processor, open an In-progress ticket, edit it and press F2, I know the UI Component is being used by Processor when they open a ticket is AIC_INCIDENT_H.

 

 

Now it's time we start cooking.

 

Run tcode BSP_WD_CMPWB, and open UI Component AIC_IM_REQ_H.

 

 

On the left, expand Views folder, you could see 2 views are listed down.

 

 

And they have different purposes:

  • AIC_IM_REQ_H/IncidentHeaderEF: it’s corresponding with Summary area on the screen when you open a ticket under Key-User. It contains all information about ticket.

 

 

  • AIC_IM_REQ_H/IncidentOV: it’s corresponding with the whole page when you open a ticket, included 3 areas as below.

 

 

Now double click on AIC_IM_REQ_H/IncidentOV, choose tab Configuration on the right. Sometimes, you will be asked to logon.


 

This tab will show you an overview about the screen that users will see when they open a ticket. With every field has its own properties, you not only can marked it as Mandatory, but also disable it from editing. It's up to your requirements.

 

You can see Available Assignment Block area, this area will contain all assignment blocks that could be assign more to Work Center Page. If there are any assignment blocks are not showed here, means it's not belong to Standard Configuration.

 

There are no UI Component AIC_IM_TIMEREP listed in this area, means Time Recording assignment block is not included in Standard Configuration of ITSM for Key User interface.

 

Basically, Work Center Page is an HTML page, means you could customize it by changing tags inside it, that's what I am gonna do, copy tags related with Time Recording block from UI Component AIC_INCIDENT_H to AIC_IM_REQ_H.

 

Use SE80 to open BSP Application AIC_INCIDENT_H

 

 

Expand "Pages with Flow Logic"

 

 

Double click on Repository.xml and choose tab Layout in case it's not opened as default.

 

 

Search in the content, and find all tags related with AIC_IM_TIMEREP. We will see some tags as below:

 

<EmbeddedView> tag

 

 

<NavigationLink> tag

 

 

<ComponentUsage> tag

 

 

Copy those tags to Notepad or anywhere to backup. Now using SE80 to open BSP Application AIC_IM_REQ_H and also expand Pages with Flow Logic, double click on Repository.xml file and choose Layout tab.

 

 

We copy all tags that we have copied from AIC_INCIDENT_H before to right places in this file.


Note: should pay attention on the name of UI Component AIC_IM_REQ_H and AIC_INCIDENT_H, we should replace AIC_INCIDENT_H with AIC_IM_REQ_H if it's mentioned in any tags before paste to the file.


-

-

 

Now click to Activate to apply changes to Repository.xml and activate it.

 

 

You could be asked to identify the TR for this change.

 

 

Going back to UI Component Workbench and open AIC_IM_REQ_H, choose view AIC_IM_REQ_H/IncidentOV.


Now Time Recording block is listed on Available Assignment Block area.


 

To assign it to one Tile (a definition about an area on Work Center Page of Key User), we just drag and drop it to that Tile. And don't forget to edit the Title for it. In this example, I assign it to Summary Tile.

 

 

Now Work Center Page of Key User has Time Recording tab

 

 

In this tab, if Key User has authorization to see Time Recording of everyone, they could see Time Recording of the others.

 

On Friday July 18th, 2014 the new ST-A/PI 01R plug-in was shipped to customers and this means that many new key figures have been shipped for Business Process Monitoring and Business Process Analytics in SAP Solution Manager. This blog will give a short overview about what is new. The plug-in contains (besides others)

  • New types of delta throughput key figures for Order to Cash
  • New key figures for vendor invoice processing scenarios like Financial Shared Service Center scenarios
  • New Automation rate key figures
  • New business workflow related key figures that bring business documents and technical workflow information together
  • New Exception key figures for Cost Object Controlling (CO-PC)
  • SAP CRM key figure enhancements

 

The new ST-A/PI 01R is available for download and can be found under (SMP login required) http://service.sap.com/supporttools.

A complete list/catalog of all available out-of-the-box key figures is available as MS PowerPoint presentation at (SMP login required in both cases)

 

Remarks:

  1. On slides 2,3 and 4 (Table of Content) you can find hyperlinks where you can directly access the respective chapter of interest.
  2. For application related key figures you find some of the listed Selection Options in bold letters. Those Selection Options are available as "Group by" fields in Business Process Analytics.

Key figure news summary for selected areas


New monitoring objects and key figures have been developed for Order to Cash throughput measurements, that require more granualr information than just on a daily basis. Those key figures are collected with some delta mechanism and can aggregate the throughput data in 5, 15, 30 or 60 minute buckets:
  • Sales documents (created, delta)
  • Outbound deliveries (created, delta)
  • Goods Issues for Outbound Deliveries  (posted, delta)
  • Outbound delivery items (created, delta)
  • Sales invoices (created, delta)

 

Attention: For those key figures it should be ensured that the corresponding housekeeping mechanisms of Business Process Analytics are activated.

 

New monitoring object "Changes in Documents" has been developed with a new key figure:

  • Changes in Sales Documents (measures all changes on header, item and schedule line level that are reflected in change tables)

 

New key figures for Purchase Requisition items, Purchase Order items, MM Invoices (AP), FI Postings, Open items (FI-AP) related to approval processes which are supported by business workflows:
  • WF: Purchase Requisitions with Workflow in process
  • WF: Purchase Requisitions with erroneous Workflow
  • WF-Lead TIme: Purchase Requisitions WF Creation --> WF Approval
  • WF: Purchase Orders with Workflow in process
  • WF: Purchase Orders with erroneous Workflow
  • WF-Lead TIme: Purchase Orders WF Creation --> WF Approval
  • WF: MM Invoices with Workflow in process
  • WF: MM Invoices with erroneous Workflow
  • WF-Lead TIme: MM Invoices WF Creation --> WF Approval
  • WF: FI Postings with Workflow in process
  • WF: FI Postings with erroneous Workflow
  • WF-Lead TIme: FI Postings WF Creation --> WF Approval
  • WF: Parked FI Postings with Workflow in process
  • WF: Parked FI Postings with erroneous Workflow
  • WF-Lead TIme: Parked FI Postings WF Creation --> WF Approval

Remark: The business workflow key figures are only working for workflows that are defined based on standard SAP business objects, i.e. BUS2105, BUS2012, BUS2081, BKPF and FIPP).

 

New automation rate key figures were introduced for Deliveries and Payments (vendors & customers):
  • Automation rate: Inbound Deliveries  (how many inbound deliveries are created automatically vs manually)
  • Automation rate: Outbound Deliveries (how many outbound deliveries are created automatically vs manually)
  • Automation rate: Vendor payments (how many FI-AP items are cleared automatically vs manually)
  • Automation rate: Customer payments (how many FI-AR items are cleared automatically vs manually)
Besides the workflow key figures for MM invoices and parked FI documents as well as automation rate key figure for vendor payments (all mentioned above), further key figures were introduced especially to support vendor invoice processing scenarios like Financial Shared Service Center scenarios:
  • MM invoices in status 'parked' (status of related business workflow can be included)
  • Overdue MM invoices with open FI-AP items
  • Purchase Order related invoices as % of total invoices
  • Overdue documents FI-AP in status 'parked'

 

New exception key figures were introduced for Cost Object Controlling (CO-PC):
  • Exceptions in Actual Result analysis (Sales Order) (related to transaction KKAK)
  • Exceptions in Actual Result analysis (Internal Order) (related to transaction KKAI)
  • Exceptions in Actual Result analysis (Project System) (related to transaction KKAJ)
  • Exceptions in Actual Settlement (Project System) (related to transaction CJ8G)
New key figures were introduced for SD invoices, Delivery items and Open items (FI-AR):
  • Exceptions due to billing block (shows especially those outbound deliveries that cannot be billed, because the corresponding sales order is blocked)
  • Missing fields in SD documents that hinder billing (shows especially those outbound deliveries that cannot be billed, because the corresponding sales order is incomplete)
  • Delivery items overdue for billing (next to delivery information also corresponding sales order item information about billing block and net value is provided)
  • Overdue documents FI-AR in status 'parked'

Enhancements for SAP CRM key figures:

  • All CRM Sales and CRM Services key figures have been enhanced, so that "User status" can be used as "group by"-field for Business Process Analytics.

 

Further reading

You can find all necessary information about Business Process Analytics in this document.

 

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

More often than not and at many customers I have worked for earlier, solution manager upgrade is a trivial task. Purely because not everyone implements the entire ALM suite and not everywhere will there be a plan to scale solution manager to accommodate more than 2000 systems, just for active monitoring! It’s easy to imagine the amount of content that was there in solution manager at SP08 where we started and safe to say it wasn't an easy task to upgrade it to SP11.

The main intention behind this blog is to give an overview of the drivers behind this upgrade, challenges we faced, recommendations and our learning.

 

Drivers behind the decision:

First and foremost, a lot of landscapes that were connected already to solution manager went through an upgrade early this year. With an intention of bringing solution manager to pace, the need was all the more strategic. For eg. Monitoring of netweaver releases 7.4 and above is not possible in SP08. Please refer SAP Note#1478974 for further details.

Another selling point for the upgrade was a lot of new features that SP11 offered. An overview of the same can be found here

 

Plan and the execution:

We had a 3 system landscape of DEV-->QA-->PRD and in addition a sandbox system. Preparations were on from March this year in terms of getting the sizing and forecast right (at least for coming 12 months).  However, the real execution of the upgrade started 2 months back. With a detailed plan we actually took less time to upgrade QA and PRD systems when compared to DEV and sandbox systems. The adjustments i.e. SPAU and SPDD were only done in Dev and then transported across so that they get automatically handled in QA and PRD. We actually finished the production upgrade over the weekend in 2 days [not considering the times for download media, preparation and post upgrade activities likes testing]. We released the system for production usage after 5 days.

SMEs from every module were given the task of testing their respective functionality and issues were tracked individually.

 

Issues we encountered:

I am mentioning only the standard SAP issues we encountered which were resolved by a SAP note here. Apart from these, obviously, there were several other customer specific issues we encountered.

  1. Editing a document in RMMAIN was causing runtime errors – Resolved by SAP note 1979874.
  2. Opening an ITSM incident lead to a runtime error in transaction CRM_UI/SM_CRM - The root cause of this were the new SAP Standard Page Attributes introduced with SP11 which were missing in the old Enhanced View, we added these attributes to the custom Enhancement Set.
  3. Background job : CCMS_BI_SETUP had errors in its logs - The errors were due to bugs, the resolution is to follow the recommended activities in KBA: 2022565 & Implement SAP Note : 2016251
  4. Jobs related to CCLM were failing - Initial CCLM Setup that was required for SP11 was performed, Notes : 01957735, 02015424, 02021553 & 1991568 were implemented for Specific Issues.
  5. Agent Authentication via 'certificates' are not supported in SP11 – Backward compatibility issue. This is a bug in SP11 and the Authentication Mechanism via Certificates doesn’t work, will have to be switched to Basic.
  6. BW monitoring configurations were giving an error on saving – Resolved by SAP note# 1952450

 

Recommendations and Learnings:

If and when you plan to upgrade, do keep the notes 1953075, 1843689 handy. These notes provide an overview of recommended corrections.

During the pre-processing phase of SUM the Document Repository is also locked along with the Development Environment so no changes to SOLAR01/02 Documents are allowed. End Users will not be able to edit documents in SOLAR01 & SOLAR02, other production operations can go on till the downtime phase of SUM.

With a fond hope that this blog will help you in planning and executing the upgrade better. Do let me know of your experiences as well. Happy upgrading!

In the last three weeks, I ran several upgrades to SP12 on SAP internal Solution Manager 7.1 Systems with different source release. Here, I would like to share my experiences.

 

All the systems I was handling are Solution Manager 7.1. with NW 7.02. SP release was SP10 or SP11.

 

 

Prerequisites for the upgrade to SP12

 

  • SPAM has to be updated to version 53
  • ST-ICC Package needs to installed / updated to Version 200

 

 

Problems during upgrade

 

 

1. I got twice a deadlock situation in the main import for package SAPKB70215

 

         Main import

Transport request   : SAPKB70215

System             : E2E

tp path              : tp

Version and release: 380.08.41 720

 

 
SQL error -60 accessing reportsource/TOUCH_REPORTS: POS(1) Work rolled back,DEADLOCK DETECTED

2018022 2018022

   
autorepeat is set to automatic, therefore this import is tried again

all 2 error messages up to here can be ignored

sap_dext called with msgnr 1:

  db call info

function:   db_repo

fcode:      TOUCH_REPORTS

tabname:    SOURCE

len (char): 32

key:        <3 blank separated report names>

retcode:    1

sql error:  -60 POS(1) Work rolled back,DEADLOCK DETECTED

SQL error -60 accessing  : POS(1) Work rolled back,DEADLOCK DETECTED

Main import

End date and time : 20140723161203

Ended with return code:  ===> 12 <===

 

Start import R3TRINTFIF_HTTP_SERVER ...

 

IF_HTTP_SERVER================IT
is included by 94942 master programs, therefore the buffer synchronisation may take some time.

IF_HTTP_SERVER================IU
is included by 1941 master programs, therefore the buffer synchronisation may take some time.

[    dev trc,00000]  table logging switched on for all clients                              2131  52.247673

 

report
CL_WDR_EMBEDDED_CLIENT_SMART==CP        (L) synchronized.

report
CL_SRT_TEST_MSG_ID_WSA_CLIENT=CP        (L) synchronized.

 

SQL error -60 accessing reportsource/TOUCH_REPORTS: POS(1) Work rolled back,DEADLOCK DETECTED

2018022
2018022


The problem could only be solved by stopping R/3 (not the database) and running imp all from command line...

 

tp R3I ALL E2E pf=/usr/sap/trans/bin/TP_DOMAIN_E2E.PFL -Dclientcascade=yes -Dstoponerror=8 -Drepeatonerror=8 -Dsourcesystems=
tag=SPAM&

 

2. Shortdump at the end of import

CALL_FUNCTION_PARM_UNKNOWN - Exception: CX_SY_DYN_CALL_PARAM_NOT_FOUND

Function parameter "EV_NO_EDIT" is unknown.

=> just restart SPAM

 

3. Additional Notes after Upgrade

 

In the follow-up steps including solman_setup the notes 2025884, 2020219 and 2042820 should be imported

 

 

Issues after the upgrade

 

Here I would like to describe some issues which were occurred after the upgrade

 

1. Missing UISAPUI5 and UI_INFRA Packages

In the Support Package Stack for SP12 are only the Packages for UISAPUI5 and UI_INFRA until Version 7. We found out that without the newer package versions 8 or 9 issues with the Technical Monitoring WoC and with sm_crm are occurring. After implementing relases 8 and 9 of these packages, the issues were solved.

 

2. ST-A/PI 01R was missing. Meanwhile, ST-A/PI release 01R is in the Download Stack for SP12 and can be implemented via TA SAINT.

 

3. After the upgrade a lot of shortdumps were arising: OBJECTS_OBJREF_NOT_ASSIGNED_NO -> CL_ICMON_IFCHANNEL============CP

-> could be solved after updating the content in solman_setup -> Technical Monitoring

ASUG.pngDCODE.png

 

SAP's John Krakowski is providing more information below on his ASUG SAP TechEd & d-code pre-conference session:


Deliver Software Solutions Fast with Design Thinking and Agile Software Engineering

1fig.png

Source: SAP


Businesses are continually challenged with managing their IT complexity, a point proven by their high level of IT spending.  The majority of IT budgets typically are allotted for hardware and services, leaving very little that is available for innovation.


2fig.png

Source: SAP

 

Businesses in any market have bold dreams to expand to new markets, and are under extreme pressure to transform complex solutions quickly. SAP customers need to innovate and overhaul their traditional business models nimbly to compete in their marketplaces. However, adopting innovations can cause risks and additional costs for existing operations.

3fig.png

Source: SAP

 

To meet consumer demands, and adopt new business models and partnerships, companies demand SAP solutions that address their business challenges while identify risks in an early phase, to get a solid decision base to consider during implementation.

4afig.png

Source: SAP

 

In this session, we will demonstrate how the Pace-Layered Architecture Strategy*, introduced by Gartner Inc., will prove that safe adoption of innovation is indeed possible. You will discover how to achieve rapid innovation while making your corporate rollouts a non-event for the business.

4fig.png

*Gartner, 2011 - http://blogs.gartner.com/it-glossary/pace-layered-application-strategy/

 

Design-thinking concepts enable you to best understand new business models, and lead discussions concerning desirability, viability and feasibility within the business transformation office. These concepts translate the new business models into an IT solution addressing these needs exactly. In the session, we’ll explain how design-thinking is a methodology that can unleash your ideas and creativity.

 

5fig.png

Source: SAP

 

Also, we’ll discuss how we no longer have to rely on traditional waterfall approaches, but can leverage agile software engineering methods to capture the ‘big picture’ in prototypes quickly to ultimately  ‘build the right things’ and ‘build the things right’.

 

6fig.png

Source: SAP

 

Throughout our session, you will learn and take away how SAP Solution Manager is well-equipped to serve as the central delivery platform to facilitate the rapid prototyping of new solutions, business models and capabilities to:

 

  • Document system landscapes and end-to-end applications
  • Manage the release strategy to filter business requirements
  • Improve, reduce and avoid custom code required to support business processes
  • Reduce testing efforts by only testing what has changed, and by automated tests
  • Carefully manage dual-track system landscapes

7fig.png

Source: SAP

 

In summary, the goal of our session is to introduce a standardized methodology and integrated tool chain to successfully enable companies who are seeking to maintain and increase their competitive edge through innovative business processes, with minimal risk to live operations.

8afig.png

Source: SAP

8fig.jpg

Join us for this new, exciting and interactive session

You’re ensured to take away key information on how to build differentiating and innovative software solutions on top of SAP’s existing industry best practices, leveraging SAP Solution Manager, providing lower time to market and enable tangible value realization for your company.

 

Discover SAP TechEd && d-code - http://www.sapdcode.com/

ASUG Pre-Conferences - ASUG Preconference Seminars | SAP TechEd &amp;&amp; d-code Las Vegas

Registration - https://d-code.2014.usa.sapevents.com/index.cfm?fuseaction=reg.ReturnLogin

 

Date: Monday: October 20th

Time: 8:30 am to 5:00 pm

Location: Las Vegas

 

Could this be you, asking John a question in October during the pre-conference session?

http://scn.sap.com/servlet/JiveServlet/showImage/38-105562-431118/johnk.png

Register today

This is the last blog in continuation to earlier blog series (Part 1  Part 2 & Part 3), we are going to explore the further steps to configure and implement multiple SLA for same customer in Solution Manager 7.1 IT Service Management where single SLA is not sufficient.


Let us complete remaining 2 steps as mentioned in earlier blogs and then test our entire configuration.


Step 4: Configuration of SLA Determination procedure in SPRO


Further, navigate to SLA Determination Procedure in SPRO


SAP Solution Manager Implementation Guide->SAP Solution Manager->Capabilities (Optional) -> IT Service Management-> SLA Escalation->Define SLA Determination Procedures


Choose the standard SLA determination procedure and then click copy button as highlighted below


 

 

Press entry key to start copying and confirm any pop ups. Also save it in a transport Request.

 

Further, click the ZMIN0001 SLA Determination Procedure and then choose access sequence on the left part of the same screen of figure below.


 

As we have copied from standard we have all the entries copied but it is not mandatory to have all of them and we can remove the irrelevant ones. To remove anyone choose the entry and click minus icon in above figure.


As we can see here lot of other criteria are available which gives us the flexibility of SLA determination via multiple choices offered by SAP.  Save and exit.


Step 5: Assignment of SLA Determination Procedure to transaction type


Now navigate to SPRO or follow below path


SAP Solution Manager Implementation Guide->SAP Solution Manager->Capabilities (Optional) -> IT Service Management->Transactions->Define Transaction Types

Now search for ZMIN or YMIN transaction type for incident management using position button or scroll down.


Please Note: This is assumed to be present as it is part of incident management setup in Solution Manager 7.1


 

Choose the ZMIN or relevant transaction which is configured for Incident Management and then click on Assignment of Business Transaction Categories option on the left side of screen.


 

Now choose Service Process in the figure 30 above and then click on Customizing Header in the left navigation tree.Next step is just to maintain or now assign our SLA Determination Procedure to the field shown in below figure.


 

 

Thus, we have successfully assigned our custom SLA Determination Procedure to our ZMIN transaction type and finished the setup of Multiple SLA’s.

Save and exit.


Thus above are the 5 main steps in addition to standard incident management which are sufficient to setup a multiple SLA for same customer who would like to have a separate support or SLA for SAP Incidents and another one for Non SAP Incidents respectively.


Testing - Multiple SLA


Now let us create 2 incidents with one SAP Application category and another one with IT Assets category respectively, to see if our SLA configuration is determined properly or not.


Enter transaction sm_crm, now choose the Business role SOLMANPRO or SOLMANREQU assuming multiple Business Roles are assigned to your ID.


In our case, we have selected standard SOLMANPRO business role delivered in standard itself (Out of Box). Provide multi level categorization, Sold to Party, Reporter(automatically picked up if configured) with priority.


 

Now click save button and thus an incident ID will be generated and ticket is posted. System will automatically determine the SLA and calculate the IRT and MPT date for us as shown below. In our example, as per Table 1 for customer XYZ Corp India, the dates are calculated properly


 

 

Similarly we repeat above steps to post an incident for IT Assets or non SAP category as shown below.


 

Thus, above steps can be utilized to configure and implement multiple SLA’s for same customers based upon multi-level categorization in Solution Manager 7.1.

In continuation to earlier blog (Part 1 & Part 2) , we are going to explore the further steps to configure and implement multiple SLA for same customer in Solution Manager 7.1 IT Service Management where single SLA is not sufficient.


Quickly what we have so far done is out of below steps, first 2 steps are completed.

 

  1. Creation or Configuration for Service and Response Profile
  2. Creation of Product and assignment of Service & Response Profile
  3. Assignment of Service Products to Multi Level Categorization(MLC) & creation of Sold to Party
  4. Configuration of SLA Determination procedure in SPRO
  5. Assignment of SLA Determination Procedure to transaction type

 

Thus, we are now ready to assign Products to Multi level categorization which are already having our Service and Response Profiles.


Step 3: Assignment of Service Products to Multi Level Categorization(MLC) & Creation of Sold to Party


In the CRM Web UI, choose the standard Business Role SOLMANPRO if multiple business roles are assigned.

 


 

Please note: Make sure the PFCG role (SAP_SM_CRM_UIU_SOLMANPRO) is assigned to your user ID for accessing SOLMANPRO Business Role. SAP_SM_CRM_UIU_SOLMANPRO is a standard PFCG role delivered by SAP for accessing standard IT Service Management interface and other relevant access.


From Solution Manager 7.1 onwards it is mandatory to use Business Roles as this is the only way to access the new interface. Kindly check my another blog for the same(SOLMANPRO)

 

Now click to choose the highlighted workcenter “Service Operations” and then click on categorization schemas as shown below.


 

Now we will assign our two service products to multi level categorization as mention earlier. This will enable us to setup multiple SLA’s as we have stated in tables 1 and 2 for SAP and Non SAP Incidents/Tickets respectively.


Once we have clicked on categorization schemas we get the below screen.




Click the Search button to list all the available schemas. As we have already assumed that incident Management is setup so we are assuming a custom multi level categorization is already available. For creating a new MLC, we can refer below guide

http://wiki.scn.sap.com/wiki/display/SAPITSM/Multilevel+Categorization


Thus select the relevant MLC and click “Version” button to create a new version of the same. Further, expand and choose “SAP Application” category as shown in below figure

  1. Click on the  New button in the Service Product block
  2. Assign the Investigation Product which has 24/7 support profile already attached


 

In the same screen of above figure, we further select “IT Asset” and “Hardware” category and assign the Hotline product which has 12/5 support profiles attached respectively.


 

Now save the new version of MLC and release it for use.


Next we need to create a Sold To Party which is very Basic configuration and therefore I am not covering here because our assumption is basic Service Desk/Incident Management is already configured.


The remaining configuration are covered in the last blog of the series as below.

How To - Configure Multiple SLA based upon MLC in IT Service Management - Part 4

Normally we are using BRF+ for support team determination using SAP Component, but also we can use the category id for the support team determination via BRF+.

 

Below step will hep to configure the BRF+ using category id.

 

Pre-requisite:

 

Test Management configuration.

Incident Management configuration

 

 

Version:

 

SAP Solution Manager 7.1 SP11 System used for below screen shot capture and configuration.

 

 

Steps:

 

1. In the test management, for the test status "Fail Retest Required"  needs to raise the defect message .

 

In my scenario we used ZMIN for defect incident configuration for BRF+ action profile usage .

 

so for BRF+, active the action definition ZMIN_STD_FIND_PARTNER_FDT in ZMIN_STD action profile

 

action_definition_active.png

 

 

2.During the defect incident creation in test management using the category schema  like shown below

Defect message creation.png

 

3. For category schema creation go to SM_CRM -> service operation -> Categorization Schemas and create your own categorization schema depend upon          requirement and make note . like show below SAP Solman support category id: CA_11

 

Categorization schema.png

 

4. Check the BRF+ configuration document- Support Team Determination via Business Rule Framework plus - SAP IT Service Management on SAP Solution Manager - SCN Wi…

 

After completing the 5.3  Create Decision Table in step 3.Choose the parameter CATEGORY from the query results.

 

category mapping.png

follow the step in the  BRF+ configuration document , in define the category id and support team details in the table contents

for support team creation go to SM_CRM -> service operation -> Organization Model

BRF+.png

After completing all the steps in the document, active the schema.( for every change needs to re-active the schema for reflection)

activate.png

 

Step:5 After filling all the details in the defect incident creation and click "OK".

 

            Now automatically the defect incident is created and support will get mail notification for processing.

defect message creation in 7.1.png

 

Hope this blog will help you in some extend to configure the Support Team Determination via BRF+ using category id in the defect incident (Test management)

The SP12 was released few days ago, and is glad  to found the new functionalities,

 

But this blog is only to remember everyone to check the RKT of Solman https://service.sap.com/rkt-solman, in this RKT, You will found the information regarding the new features released in SP12.

 

My recommendation is start with the Overview and check the new features.

 

The RKT have the following topics:

 

Screen Shot 2014-08-03 at 10.23.43 AM.png

 

In the Solution Manager Overview you will found the following Presentation with the New functionalities :-))Screen Shot 2014-08-03 at 10.24.16 AM.png

 

Best Regards

@WenSolman

This Blog is in continuation to my previous blog SolMan 7.1 Integration with UFTin this i am going to explain steps involved in connecting UFT with SolMan.

Install the UFT with SAP add-in.

 

Open UFT and from menu choose Tools -> SAP Solution Manager Connection... select this

Capture.PNG
The below pop-up is opened on selection:

 

Capture1.PNG

 

Server description will contain the list of servers available in SAP Log-on pad (saplogon.ini)  in some cases this will be blank.

UFT expects saplogon.ini file to be in C:\Windows. If the list is blank move a copy of saplogon.ini file to C:\Windows.

 

Enter user ID, pwd. with which UFT has to connect to SolMan click on connect button. Choose reconnect on startup and save password for reconnection on startup.

 

Every time when UFT is opened and the SolMan connection is established then SAP logo appears at the bottom of UFT as shown belowCapture.PNG

Choose a Recorded script and From menu choose the below path

Tools -> Options -> GUI Testing -> SAP Solution Manager

 

The below screen will open

Capture.PNG

In Run result maintain a network path to store the result of UFT.

In SolMan all the Test scripts have to start with Z so new test prefix and new file prefix should be maintained as Z.

 

After scripting is over, to transfer the parameters automatically to SolMan make below settings.

Capture.PNG

To see the parameters in UFT after scripting is completed navigate to below path

open script and from menu choose File -> Settings choose parameters tab, below window opens.

Capture.PNG

 

Hope this helps new users to understand and setup with ease.

Downloading Support Packs via Solman 7.1

Login to Solman System

Go to -> SE37 t-code

1.png

 

It Displays the following Screen

2.png

 

 

 

Enter the Function Module in the Box “ /TMWFLOW/MO_UI_BASKET_AUTHORIZ “  & press F8

2.png

The following screen appears and press Execute

2.png

 

It Displays the following screen which need to approval from our Download Basket

Select the File which need Approval & Confirm Download

3.png

After Confirming Download it Shows like below

4.png

Your Download get Approved -> then go to Download Manager and Select the Object to Download

5.png

Select the file and Start Download to Folder

5.png

Your Download Started

5.png

Check in folder

6.png

To Get the above Scenario exactly we need an AISUSER which is attached to our S-User(Market place ID)

For EX: BABU – S00xxxxxxxx

Follow the Screen Shots

Use T-Code “ AISUSER” in Solman 7.1.

6.png

Follow the next screen

If don’t ve any S-User contact Administrator .

 

 

 

 

 

 

 

 

 

 

Regards,

 

Chandrababu Katta

Actions

Filter Blog

By author:
By date:
By tag: