I was just remembering how I was struggled to understand LMDB in SM 7.1 SP1 in my own sandbox; Those days I don’t have any source for reference except the guide from SAP and the blog #sapadmin:: How to assign Product System in SOLMAN 7.1 & How LMDB, SLD, SMSY and Landscape Verification  work in SOLMAN7…

 

 

This blog is the asset for my entire team to know where to start in LMDB.  During that time it was big debate with Tom Cenens in the blog Solution Manager 7.1 Landscape Management Database - A motorcycle or a bike?   about easy usage of LMDB, Later SAP come forward and clarified the road map, need and necessity of LMDB Evolution of Landscape Data Management – What’s better with LMDB?

 

 

We might thought it was just a vision,accepted and moved on. but it was not true, that was tremendous effort put on these concept, As promised by Bjoern Goerke in 2012 Teched, LMDB gradually evolved and it was much more mature now.

 

 

I was recently asked to give training to some of the functional colleagues on solution manager basic concepts; it was amazing, LMDB now become more self-guided and they done the entire setup without much hurdle. It was automatically guided them to assign the missing technical systems, product systems and logical components.

 

 

t1.JPG

 

 

It was made my job easy!  I was impressed and my entire team was satisfied. Two weeks before I had discussion with Tom, finally was decided to reopen the old poll and to collect the feedback again.

 

 

Before that, Thanks to Wolf Hengevoss  for his continuous effort to bring the product much simple and more powerful.

 

 

You can check out the recent changes of LMDB in sp10. Evolution of Landscape Data Management – Part II: What’s better with LMDB in SAP Solution Manager 7.1, SPS10?

 

 

Now time for you all, let’s evaluate LMDB in SM 7.1 SP10, and how do you all feel? Take few minutes and finish the Poll by June 30th 2014.  SAP Solution Manager 7.1 SP10 LMDB

I will be publishing this as a series of blogs with all the steps required to understand(basic concepts), configure or setup multiple SLAs in IT Service Management based upon Multi Level Categorization in Solution Manager 7.1 which we have recently implemented or configured for a customer.


Over the years SAP has made huge investment in the Service Operations area of Solution Manager and the new version which is 7.1 today provides flexibility to all SAP customers to implement IT Service Management for entire SAP and non SAP landscape.

 

In my experience, this is a journey and we should not jump on it doing everything at the same time but rather go step by step to implement the various capabilities of IT Service Management in Solution Manager 7.1.

 

During several implementations for IT Service Management in SAP Solution Manager 7.1, we have come across a common requirement to have multiple SLA or Service Level Agreements for support.

 

This blog series will focus on detailed configuration or implementation steps for setting up multiple SLA based upon Multilevel categorization(MLC) or the different type of incident.


Basic concept of SLA

Service Level Agreements (SLA) are typically agreed by SAP Customer with vendors who provide support or services adhering to their requirements

Typically there can be various criteria for having different SLA requirements. For every customer SLAs can be different based upon business conditions or support requirements i.e. either service basis or for specific product basis etc.


We can implement or configure multiple Service Level Agreements to satisfy different requirements from support perspective, for multiple customers or a single customer itself. This means we now have got flexibility of easily supporting different deadlines as per customer scenario based upon the variants of configuration possible in the new version of Solution Manager.

 

Service Level Agreements (SLA) in Solution Manager works upon two main concepts of:

  1. Service Profile and
  2. Response Profile

 

The basic concept are already explained in detail over wiki on below link

SLA Management - SAP IT Service Management on SAP Solution Manager - SCN Wiki

 

Just to add further over Service and Response Profile

  1. Service Profile – This helps us to define the time period within which the support partner should provide the service. e.g. 24/7 support which means 24 hours each day of a week
  2. Response Profile –  This helps us to define within the time period what is the start date/time and what is the end date/time e.g. based upon criteria say priority what should be expected deadline for start and end

 

The two major parameters for SLA measurement offered by SAP Solution Manager are mentioned below which are part of Response Profile:

IRT - Initial Response Time

MPT - Maximum Processing Time

 

Thus, based upon the actual situation, if we don’t see the incident IRT and MPT meeting then it is called as SLA breach or violation.

This has severe impacts based upon the contract between customer and vendor. We can build reports in Solution Manager to see the entire list of incident which are breaching IRT or MPT etc in SM_CRM transaction.


Typically, in my organization, we have seen several SAP customer’s going for a 24*7 ( i.e. 24 hours and 7 days working) support model or 12*5 (i.e. 12 hours and 5 days a week) support model based upon their specific support requirements with respect to region wise, SAP/ non SAP incidents i.e. category of incident or SAP Module wise like SD, MM, FI, etc. Therefore, it is very much possible to have a one customer who would like to have multiple SLA which means separate SLA for SAP tickets and other one for Non SAP Tickets.


Please note: Before proceeding on it further, it is assumed that the system is already configured with Incident Management and custom Transaction Type like ZMIN or YMIN is present in the system as per requirement. Please check the below links for setting up the same.

http://www.service.sap.com/~sapidb/011000358700000608542012E

http://www.service.sap.com/~sapidb/011000358700000608872012E


Basically, the minimum is to have a properly copied transaction type (ZMIN/YMIN) which is having the relevant status profile and other configurations with master data in place.


Further, in our example, let us assume the below 2 different Service & Response criteria for our 2 different category of incidents

  • SAP Tickets – assuming 24/7 support
  • Non SAP Tickets – assuming 12/5 support

 

Next blog is published now and you can check herehttp://scn.sap.com/community/it-management/alm/solution-manager/blog/2014/06/02/how-to--configure-multiple-sla-based-upon-mlc-in-it-service-management--part2

Taking a cue from Daniyar Kulmanov on possibility of using BRF+ with ChaRM, I tried the automatic Change Manager determination from BRF+ framework. It worked ! and here is the procedure to achieve it;

 

The standard SUPPORT_TEAM function is copied to Z namespace to adopt the Elements. You can also create your own Z function from scratch if you are familiar with BRF+. I chose to copy the standard;

 

sshot-1.png

sshot-2.png

sshot-3.png

sshot-4.png

Right Click > Copy

sshot-5.png

Name of target application should be 'SOLMAN'

sshot-5.png

sshot-6.png

Write down the Function ID of this newly created function from Details tab;

sshot-21.png

 

You can see the Signatures inherited from the SUPPORT_TEAM in the copied function (Z_CHANGEMAN_FUNCTION). It contains all relevant elements for the Service Desk.

 

sshot-7.png

 

We will create a 'Change Manager' element which is relevant in our case. To do this follow the procedure shown in screenshots;

 

Click on Add New data Object and provide the details shown below;

sshot-9.png

 

Now add the Change Manager in the Result Data Object replacing the Support Team. You may get following error when you try to Save;

 

sshot-11.png

To overcome this error, remove the Change Manager from the Signature screen using Remove Data Object button.

 

sshot-10.png

 

Now you need to create an Application, Ruleset, Decision table as you would create it for Support Team Determination. Instead of Component and Support Team in Decision table, use Category and Change Manager dataset; To configure application follow the steps mentioned in 5. CONFIGURATION IN THE BUSINESS RULE FRAMEWORK PLUS in the following link http://wiki.scn.sap.com/wiki/display/SAPITSM/Support+Team+Determination+via+Business+Rule+Framework+plus

 

sshot-16.png

sshot-17.png

 

Now we create a Z action in Z(Y)MCR_ACTION action profile for calling this function; this new action is similar to SMIN_STD_FIND_PARTNER_FDT action delivered in SMIN_STD action profile of Service Desk.

 

sshot-23.png

In the Processing Parameters provide below information;\

 

sshot-3.png

 

PARTNER_FCT : Partner Function of Change Manager

FUNCTION_ID : is the one which we created in BRF+

APPLICATION_ID: 0050568E6E9A02DE82A4EC0838CD95E5 (alwas constant, refers to Appln SOLMAN  in BRF+

 

last step is to activate this action in Condition definitions. No need to provide any Start or Schedule condition for this action , just make it 'Green' in Conditions screen

 

sshot-25.png

sshot-26.png

 

That's all ! now depending on your decision table entries, whenever you select a category in change Request screen, Change Manager is determined automatically upon Saving.

 

sshot-4.png

Few months back we have decided to implement ChaRM with cCTS and I was looking eagerly for some blogs which talks about good and bad of it, but I was not able to find much. Then I thought I should write one when I have good understanding on this.

 

To start with we have followed the below how to guide of cCTS.

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/20c1ba0c-8f32-3110-bfa0-9d1e57522951?QuickLink=index&overridelayout=true&59017145670468

To understand the simple flow setup this is enough but if your landscape is complex then it’s difficult to manage with this little piece of info.

 

The landscape where we have started is an ECC dual track (Maintenance and Development) and singe track BI for both maintenance and development.

As its being a dual track customer wants us to setup enhanced retrofit as well. The systems in the landscape are as below:

Capture.PNG

Points to be noted during clustering:

As per the how to guide all similar role systems should be made as one cluster e.g. all DEV systems in one cluster and all test systems in one cluster. If we can take the above landscape as a use case there should be three DEV systems in one cluster.

 

Capture1.PNG

The clustering is closely associated to logical component in a project, systems must be even in all the logical components of a project else clustering is not possible.

 

Not necessarily all systems have to be in cluster e.g. retrofit.

 

Problems in clustering:

1. If one system is down in your cluster we cannot move transports to any other systems in the same cluster. E.g. In the above landscape quality cluster is having three systems two of ECC and one of BW and the project QAS system is down for maintenance then we cannot move transports to QAS of Maintenance or BW.

 

So plan you clusters properly so that there will not be any dependencies.

 

2. As retrofit is involved we have added the post processing system in logical component so the logical component will have five systems but in clustering you still have only four clusters (CD1, CQ1, CPR1, CP1) in this case systems will not be able to identify the clusters.

 

To make this work define another logical component with only post processing system, as this logical component is not even this will not be considered during clustering.

 

3. In a project we have defined DEV, QAS, PPD, PRD in logical component and in cluster we have made only three cluster DEV as cluster one, QAS and PPD as cluster two and PRD as cluster three. In this case as preprod is also kind of a test system so we can club both systems into one cluster.

Capture2.PNG

Real scenario: A new development is started in project A and was tested well in QAS now it is yet to be moved to PPD system. Later there is a change in plan and these changes are decided to be moved as part of project B, when you try to change the project assignment of this change document system give message that TR’s are not moved to all the systems in the cluster hence you cannot change the project assignment or decouple the TR’s from this change document till its moved to all the systems in the cluster.

 

Hence plan your clusters properly considering multiple use cases.

 

4. In ChaRM without cCTS if you have to stop the TR movement to next system we can delete the TR from the import queue before the import all job run. But in cCTS this is not possible even after deleting the TR and transport collection, changes will still move to next systems.

 

5. In cCTS ChaRM projects sometimes the TR will not move to the next system even after the import all job run. In these cases we have to check the log of transport collection which will give you the clue of what went wrong.

 

6. In some cases the transports will move to the next system but the TR will have a message “return code unknown” because of unknown return code it gets into the import queue again and again currently I didn’t find any way out for this.

 

Hope the above information will help in design your clusters well. 

AC_Logo_black_lores.jpg

 

SAP Solution Manager for both the LoB and IT

 

SAP's John Krakowski and his colleagues are  providing more information below about what to expect in the ASUG Pre-Conference session for "Expanding Your Borders with Solution Manager" which is being held June 2nd in Orlando, Florida.  Please read below:

 

NOW is the perfect time for every organization to register a representative to attend the ASUG Preconference Full-Day Seminar Expanding your Borders with SAP Solution Manager’.

On the SAP SAPPHIRE NOW | ASUG ANNUAL CONFERENCE home page, you will see the statement ‘Get the latest technological vision, actionable insights you need to drive profitability and growth, and influence future SAP offerings’, and on the ASUG PROGRAM home page is the statement ‘Every Experience Adds up to Your Success’.


These two statements are in perfect alignment with the tremendous SAP Solution Manager benefits and features that can be realized by all organizations and both their Lines of Business and IT.


More than ever, the market never stands still and neither can SAP and SAP Solution Manager. Year over year, SAP Solution Manager pre-conference seminars have proven to be among the most successful, valuable, and important topics for the ASUG Community. This year’s focus is to demystify, simplify, and discover new ways to approach your SAP Solution Manager adoption for lasting benefits to drive maximum value from your SAP Solution environment. SAP Solution Manager combines tools, content, and direct access to SAP to manage everything from deployment to solution monitoring and improvement. Based on an SAP support contract, the solution can help you optimize core business processes, your IT infrastructure, and innovate with two value releases per year.


This preconference seminar will help you refresh your SAP Solution Manager information to address the painstaking and time consuming efforts and potentially high risks to adopt innovations in your existing SAP solution, such as test phase duration, projected costs, and business user impact. The session is designed to provide maximum opportunity for you to hear from, interact, and see demos with several key and diverse ASUG members (Customer, Partner, and SAP) knowledgeable about SAP Solution Manager and obtain insight into their playbooks. You will be presented with multi-faceted topics, such as best practices for deploying innovation reliability and quickly while minimizing business risk, to increase your understanding and make SAP Solution Manager even more relevant to your organization. You will walk away with specific ways to expand your use of SAP Solution Manager, maximizing the value of your support engagement with SAP and your partners. You'll be able to streamline internal processes, minimize manual effort, reduce operational costs, and introduce new business functionality with greater ease.

 

Leveraging SAP Solution Manager more fully has been shown to increase reliability and help lower total cost of ownership:

 

  • Discover how integrated SAP IT Portfolio and Project Management, provides visibility and collaboration between project and change management teams.
  • Learn the best landscape for Two Value Releases per Year.
  • Hear about the recommended major and minor release approach.
  • Understand how to adjust and test only what matters when managing innovation projects with SAP Solution Manager’s Scope and Effort Analyzer.
  • Gain steps to improve Custom Code Management.
  • Review Solution Documentation best practices and whitepapers.

 

Also, walk away with information about:

 

  • SAP’s Control Center Approach for proactive support and to accelerate innovation.
  • Deployment and Run SAP like a Factory best practices for SAP HANA.
  • IT Service Management best practice processes with SAP Solution Manager.
  • What the new central CTS means for Change Control Management.
  • Learn information about SAP Solution Manager’s strategic direction and release plans, with details of the new release’s exciting innovations such as a new approach for collaborative process design.

 

Don’t miss out learning about the new features and breaking announcements!


Register Today


johnk.png

Photo by SAP



Could this be you, asking John questions during this ASUG pre-con?


I also  encourage you to read what former SCN Member of the Month Thomas Dulaney wrote in his blog last year about the ASUG Solution Manager pre-conference session at Review: ASUG Preconference ==> SAP Solution Manager 7.1 – Additional Value Creation Through Technological Innovations

 

He says:

"I have absolutely *nothing* negative to say about the ASUG preconference sessions. The three presenters were incredibly well informed. The presentations were incredibly well prepared. It was clear that this preconference session was designed and developed as a smoothly flowing whole session and not a collection of one hour sessions designed for a different audience. "

 

Register Today

Being involved with the new Logical Components as a developer from quite sometime, I have realized there are some common issues that are faced by consultants while working with them in the new Logical Components in LMDB.


Question: I do not know how to work with the new Logical Components

Resolution: Look at the following link

 

Question : I don't see the Logical Components created in customer namespace in LMDB however it exists in SMSY?

Symptoms:

  • Logical Components exist in SMSY
  • During Managed system configuration it is possible to define Logical Components
  • In LMDB, the only option available is to create new logical component to assign to a Technical System.
  • If you attempt to edit the logical component in SMSY, the following message is displayed:
  • The selected logical component is not yet available in the logical component editor.
    Therefore, you can still edit this logical component with transaction SMSY.

Issue : You don't see any Logical Components in LMDB transaction apart from the one's shipped by SAP as templates.

Resolution: Goto solman_setup, click on System preparation-> Goto step 6-> Click on the link "Migrate SMSY data to LMDB"-> In the UI sub-step that opens execute "Migrate Logical Component Data"

 

Question: I see a sync issue between LMDB and SMSY, the product instance/systems selected in LMDB and saved are not the one's  shown in SMSY or the system and roles are not matching.

Issue: bug in the code

Resolution: Implement all then relevant notes in the application area SV-SMG-LDB-LC, delete and recreate the Logical Component, you can change the specific product instance or delete the technical system and add it again. Press save in between.

Question: I do not know to which Product instance of the Technical system, the Logical component should be assigned

Resolution: It has been discussed in the blog

   

Question: I do not see a Logical Component for a certain Product / Product Version

Resolution: With 7.1 SP10, SAP has stopped shipped new Template Logical Component, Create you own logical components in the customer namespace and assign the required product version->product instance

Question: The Logical Component systems are yellow even though the systems have been upgraded.

Resolution: This means that the Logical component assignment to the Technical system is not updated. Check out the Technical system by clicking on the ExtSid of the Technical system, If the product instance assigned to the Logical component is not upgrade, select "Maintain", click on search and as proposal is selected by default, select the checkbox of the correct product instance. Close the pop-up and save.

If the Technical system is still yellow, open the software node of the Technical System and check the assignment of the Logical component, it is correct or not.


How to Edit the Categorization Schema to include Newly Created Custom Transaction types

 

SAP strongly suggests to copy the default Transaction Types for ITSM and ChaRM to the Customer namespace (Z* or Y*) before customization begins.  These steps are done via the Guided Procedure for ChaRM, as is the creation of the Categorization Schema for the S* Ttypes.

 

In order to enable categorization for Customer namespace Incidents, Requests for Change, and the Change Documents, you must copy the SAP_SOLUTION_MANAGER_TEMPLATE Cat schema to the Customer Z Namespace and include the Z* Transaction Types.

 

Pre Steps:

  1. From Solution Manager: Launch sm_crm

3.png

 

 

  2.  To Enable Table Keys in Drop Down:

 

  • In WebUI Click Personalize

 

1.png

 

  •   Check box for Enable 'Show Keys in Drop Down' -> Save

 

2.png

 

 


Configuration:

From WebUI:

 

  1. Choose -> Service Operations -> Categorization Schemas

 

4.png

 

  2.  Search for SAP_SOLUTION_MANAGER_TEMPLATE

 

  •     Copy this Schema
    copy.png

 

 

 

3.  Change the Schema ID and Name to Z Namespace and Save

7.png

 

 

4.  Put the Schema in Edit Mode:

 

edit.png

 

(If editing a currently active version of a schema, First
Create a New Version of the Schema

8.png

 

 

5.  From General Data Assignment  Block  Choose Drop Down Status on Right, choose Draft.

** Be sure to edit the Valid From Date , Default value is 24 hours in the future **

 

 

date.png

 

 

6.  From Application Area Table on Right, Choose New

 

new.PNG

 

  • Create an Entry for Service Order -> Transaction type/Catalog Category ->

  • Make Entries for ZMCR, ZMAD, ZMGC, ZMHF, ZMMJ (Choose (D)
    entries)

 

  • (* When editing/creating a copy of the Standard Schema, Remove all Standard S*ttype entries)

 

 

10.png

 

 

7.  From General Assignment Block:

 

  • Choose Valid-From Date and Time (default is 24 hours ahead)
  • Put Schema in Released Mode ->

 

12.png

 

 

8.  Save the Schema

 

 

Finished:

 

Go Back to Search for Categorization Schemas:

 

Once Valid To Date is reached, the Status of schema will change to Active

13_endresult.PNG

 

Exit UI

 

To Test, Create a New Change Doc and verify the Categories are enabled:

Dear reader

 

As service delivery manager in charge of promoting Solution Manager the first thing that I found it interesting is : a customer within SAP Enterprise Support and SAP MaxAttention we have no addittional license fees to pay.

Interesting link: https://websmp109.sap-ag.de/~sapidb/011000358700000033422011E/__start.htm

 

Since we implemented the automated registration of incidents in our sevice management tool thanks to SAP Solution Manager.The next steps is to implement CHARM.Still it is not easy to convince new customers.What are your arguments to convince your customers to go onboard with SAP Solution Manager?

 

Thanks for sharing.

 

Kind regards,

Theressa.


There is a common question during Implementation projects that the customer and project team always ask - Why ARIS & Solman and why not just one of them.

 

This blog aims to clearly provide a distinction between the two.

 

ARIS is an Enterprise Level Business Process Modeling tool. The Business Strategy of the Organization gives birth to Business Processes across the different Organizational Unit. These are drafted in the ARIS modeling tool as a 7 level structure.

What is distinctly different in ARIS is that it does not matter if the Process broken upto the Process step or activity or task is running on SAP or any other system. ARIS just aims to map all the processes that runs in the Enterprise.

 

The IT Strategy leads to a "Project" - an implementation, upgrade or other kind of project. If this project is an SAP Project, then we could use Solution Manager in addition to ARIS.

What Solution Manager does is to import the Business Process from ARIS to a 3 level structure and "translate" these processes into the "SAP Objects world", namely the Transactions, IMG Objects, Dev. objects, etc.

Basically Solman in that sense is merely a "Translator". Business Process translated to the equivalent SAP Object.

The Business processe now gets a Transaction, Program, Job or other SAP objects assigned against it, the IMG documentation, other project documentation gets added etc. thereby completing the translation to an SAP world.

 

So

Business Strategy -> ARIS

IT Strategy -> SAP Project -> Solution Manager

 

The key point is - tomorrow if the Business process that is in ARIS need to run on a mobile device or a third party system replacing SAP etc, these processes should still be available on ARIS. The SAP translated objects just gets replaced with the new system that is being implemented.

 

Now, what are the synchronization directions?

 

ARIS -> Solution Manager

 

From ARIS all the Business processes that are "In Scope" for the Solution Manager "Project" should be synchronized from ARIS to Solman

Ideally, for the Business Processes the synchronization should always be one sided. From ARIS to Solman. This is because of where we started this article from - the processes at the Enterprise level is irrespective of whether they run in SAP or non-SAP. The processes should first be defined in ARIS and if they are running in the SAP systems then they are translated into the SAP object world in Solman!!!

 

Solution Manager -> ARIS

Any SAP artefacts that are created during the "Project" have to be synchronized from Solution Manager to ARIS.

We start with the "Project" itself.

 

First synchronize the Solman project into ARIS, copy the processes into this project and then start your synchronization to Solman.

 

Next will be the "Document types" and related "Status values". These have to be defined in Solman project and then imported into ARIS and reused from the Process Library against the processes.

Also the "Systems" which are created in the System Landscape need to be synchronized into ARIS. Note here that the Systems (SAP & non SAP legacy systems) are added to the LMDB of Solman thereby completing the Technical landscape documentation and then grouped into logical components are assigned to the Project. This is now reverse synchronized to ARIS.

 

You could also create "End User Roles" in Solman and synchronize back to ARIS.

 

In summary any SAP objects that need to be depicted in the process flow on ARIS has to be created in Solman and send back to ARIS.

 

Hope now that this article provides clarity on whether ARIS and Solman need to co-exist. Once again - Yes, they should!!!

This is part 2 of my notes from today's Admin 2014 Solution Manager Jump Start with SAP's John Krakowski

 

Part 1 is here SAP Insider Admin 2014 Solution Manager Jump Start - Part 1 - Key SAP Notes

 

SAP Mobile Solution Manager apps: You can learn about these at http://help.sap.com/solutionmanager71 then select http://help.sap.com/sm-mobileapps

  • End user experience mobile apps
  • Performance and availability
  • Keep finger on pulse of remote locations
  • It is a web dynpro? Yes
  • Does it use Gateway? Yes, that is out of the boxs

 

SP10 has dashboard apps

 

Business Process Monitoring which is a “sister application” has over 300 indicators

 

Solution Manager has over 10K productive installations with 300 go lives every month

 

It is ITIL verified and the first one to have 15 processes verified

1fig.PNG

Figure 1: Source: SAP

 

Figure 1 shows the ICC which is looking at projects timelines

 

OCC helps IT administrators what is going on in business

 

MCC is premium engagement – Max Attention – direct access to Mission Control Center in Newtown Square.  If you have requirements and see SAP standard functionality not met SAP looks at it.  If can’t be done, what is planned.  Goal is to reduce custom code and to help customers reduce custom code.

2fig.PNG

Figure 2: Source: SAP

 

John said “not one tool that does it all like SolMan” (Figure 2)

 

Wherever you start – have assurance that integration is guaranteed

 

How well can tools support the latest products available to you from SAP?

 

Are existing tools enabled to support HANA?  Solution manager today can run and operate your HANA project

 

SolMan is keeping in step with latest products

3fig.PNG

Figure 3: Source: SAP

 

John wants everyone attending the Jump Start to publish a quote similar to the one in Figure 3.

 

He suggested focusing on a particular pain point

 

Take away from him was when you have a key issue/challenge – include Solution Manager as part of the conversation

 

Two Value Releases

4fig.PNG

Figure 4: Source: SAP

 

Nervous about custom mods and nervous when doing custom mods and hundreds of transports

 

Testing effort is huge and doing soup to nuts testing

 

Downtime windows are shrinking

 

White paper released (SMP logon req'd) this talks about how customers can accelerate and improve major releases and projects through business suite. 

 

This 70+ page white paper should be used as a baseline to compare against you are managing areas and see how you align with what SAP recommends to customers.  Something to compare against as opposed to calling in SAP or whoever you bring in

 

Core components

5fig.PNG

Figure 5: Source: SAP

 

Figure 5 shows the costs of managing changes based on some assumptions

6fig.PNG

Figure 6: Source: SAP

 

Regression testing, downgrades – if this is in DNA, SAP is offering tools to work a synchronized strategy

 

You define windows for a major releases and minor releases

 

Looking to build a schedule to align projects to.  Today many are using spreadsheets / project is part of it

 

What are the tools to help you align?

 

7fig.PNG

Figure 7: Source: SAP

 

If doing SP’s then apply a technical enhancement package if available.  This is a best practice.

 

How can from an IT point of view always consider applying the available enhancement packages to your system

 

SAP wants this to be a starting point to reduce your custom modifications

8fig.PNG

Figure 8: Source: SAP

 

Why? In terms of performance tuning, latest code line, especially related to HANA

 

SAP is developing a new code line for HANA

 

If have a HANA based system there is a separate SP for HANA based systems

 

Efficiencies are realized taking advantage of enhancement packages

 

To be continued...

Today I attended the Solution Manager jump start session with SAP's John Krakowski

 

It was packed full of information.  I will share what I can.

 

John said for Solution Manager it is "the Why and not just the What"

 

He said Solution Manager "helps support the lines of business, bring things together so company can stay at “competitive” edge"

 

He mentioned his theme for today "Two value releases per year"

 

He said if you are doing a Solution Manager 7.1 release tomorrow to go to SP11

 

He said the release strategy is listed in note 394616

 

For every support package for SolMan there is a Release Information Note (RIN); he said this is the most critical note BEFORE applying SP to system

 

  • Main note that 1595736 – a list of RINs for a specific support package – read it
  • Limits, restrictions, gotchas, prerequisites

 

He explained that a customer experienced pain re: diagnostic agents; SAP messages opened but the issue is described in RIN

 

He suggested being proactive and that RINs are critical

 

Another challenge is the diagnostic agent

 

SAP notes 1365123  - 1858920 – 1473974 – outlines automatic updater for automatic systems let Solution Manager update systems


Service & Support Tools – ABAP Managed systems

  • Update them when have a maintenance window
  • -Use Service & Support tools to gather and send to SolMan

 

LMDB – with 7.1 you are up close and personal with LMDB and need more data than SLD provides

  • SolMan is the only end to end support
  • Need a central repository for the systems
  • Key 1734860 is a key note
    • Lists all of LMDB resources

 

If you haven’t yet upgraded or installed 7.1 – ensure set up SAP Monitoring – greatly enhanced in 7.1 – improved in 7.10 to keep finger on pulse of SolMan – SAP administrative work center

 

He said to let it be early warning system

 

One common major challenge that all customers have – performance in SolMan system – sizing wise, technically Solman has enough hardware but it is not tuned.  How to troubleshoot?  See SAP Note 1835721 for performance troubleshooting tips and tricks

 

More to come!

JohnK.PNG

Hi,

I was playing around and I found this excellent Document about how to send SMS from SAP,  from Dinesh Singh,

 

http://scn.sap.com/docs/DOC-18406

 

My idea is help you in test this funcionality

 

You need to open an account in http://www.smsglobal.com/ and then go to the API Keys
Screen Shot 2014-03-17 at 5.05.14 PM.png

 

Now you can go to SCOT and Update the URL connection using the following.

 

http://www.smsglobal.com/http-api.php?action=sendsms&user=5psx0scp&password=<password>&from=+56911111111&to=<reci_addr>&text=<message>

 

Now you are able to send SMS from SAP :-))

Does this sound familiar to you:

…based on time-based schedulers, resulting in latency, idle time and gaps in critical processes. It took many people with “eyes on screens” watching everything to make sure the billing and payment are correct….."

 

Would you like to predict if your background jobs end on time? Imagine the following scenario:

During the evening, in production environment the over-night batch job chains are started.

The IT application manager is already at home. From his mobile device he logon to the company network, and launches the job progress monitor from his mobile device. The app shows him the overall status of the over-night batch chains.

He can easily identify how many jobs are completed already and how many are still in the waiting queue, when the over-night batch job chains can complete and are the key performance indicators required by the business department can be fulfilled or endangered.

The collection manager can easily check the payment job and can post payments as soon as they are received.

 

 

The SAP Job Progress Monitor application in SAP Solution Manager provides the following functionalities:

  • Group multiple job chains to monitor together
  • View overall group progress and job chain progress; drill down to job details
  • View the current activity distribution (percentage of active, scheduled, completed, and canceled jobs) within each group or job chain
  • View runtimes and estimated and actual end times of job chains
  • Send a snapshot of job chain progress by e-mail
  • Call a Solution Manager Scheduling Enabler (SMSE)-certified external scheduler such as SAP CPS by Redwood

 

The application is available for download from the following app stores: 

 

The configuration is explained in chapter two of the setup guide.

 

Further information on SCN:

 

Please note that the SAP Job Progress Monitor requires an SMSE-certified external job scheduler like SAP CPS by Redwood and is available as of Support Package 10 of SAP Solution Manager.

In this new blog, I'd like to elaborate on one very particular aspect of the SAP Solution Manager Upgrade Projects for which I already provided some insights there: http://scn.sap.com/community/it-management/alm/solution-manager/blog/2013/11/22/solution-manager-71--fresh-installation-or-upgrade--some-experiences-from-the-field. To be more specific, I would like to expose the main Data Migration scenarios challenges I could observe on various projects with the adoption of Solution Manager 7.1...

 

The preferred path to the release 7.1 of SAP Solution Manager is in most cases -as discussed in the previous blog- the upgrade of the existing system . It removes hidden costs and allows to leverage existing master data (logical components, iBase/Components, User Master Records, Business Partner Master Records etc.). Nevertheless, an upgrade also means radical changes in the CRM engine powering IT Service Management (ITSM) and Change Request Management (ChaRM) :

  • CRM 5.0 is replaced by CRM 7.0 EhP1
  • User Interfaces change from classical SAP GUI to SAP CRM Web UI
  • New 7.1 transaction types (SMIN, SMCR, SMMJ etc.) replace the old 7.0 transaction types (SLFN, SDCR etc.)
  • After the Upgrade, processing of 7.0 transactions is allowed, but only new 7.1 transactions shall be created

Image 4 640.jpg

The schema above (source: SAP) describes the transition phase for ITSM / ChaRM

 

For the organizations that have been using Incident Management or Change Request Management for an extended period and heavily rely on those scenarios to support internal or external audits, this historical data is very precious and needs to be retained.

Unluckily, when upgrading to Solution Manager 7.1, it ends up more or less like having two different tools : the 'legacy' with ABAP tickets and the 'new' one with CRM WebUI tickets. And during the transition period, you have to jump constantly from one tool to another, which is frustrating from an end-user perspective and do not help the adoption of the target 7.1 solution.

To avoid such a situation and to allow a lean and smooth transition to Solution Manager 7.1 ticket usage, the option of performing a full Data Migration can be considered. Here are the typical cases I encountered :

 

(1) - "Migration" of the 7.0 ABAP tickets into 7.1 CRM WebUI tickets within the same upgraded Solution Manager.

In this scenario, the Solution Manager is upgraded (master data are kept...) and the old ABAP tickets are of course accessible in CRM_DNO_MONITOR.

But to simplify the transition, the open tickets are migrated into the target 7.1 transaction types. The ticket number and statuses usually are identical, the metadata (processing log, changes to document) are retrieved as well as all attachments, text entries, business partners assignments etc.

Closed tickets can be migrated as well, and put in a closed (read-only) status in the target ticket type.

If some data mapping or transformation is required, management rules are implemented. Even more important, exception rules are implemented to manage missing or irrelevant data cases.

SOMITO-1.jpg

Some advanced migration tasks can also be considered :

  • Creation of document flow (linkage between tickets)
  • Assignment of Transport Requests (modifiable and even released one) to Change Documents
  • Re-assignment of Change Documents to new Project cycles
  • Upload of Cross-System Object Lock entries in Solution Manager

 

(2) - "Migration" of the 7.0 ABAP tickets into 7.1 CRM WebUI tickets between two different Solution Manager systems.

In this scenario, an "old" Solution Manager contains the ABAP tickets and will be decommissioned. A new fresh installation of Solution Manager 7.1 is performed. This strategy brings new challenges, as the complete set of master data do change as well !

During the migration, ticket numbers are often kept, the statuses are identical, the metadata (processing log, changes to document) might also be transferred (auditing purposes). And for sure all attachments, text entries... are migrated as well. The migration scope certainly involves all open tickets, for which further processing will be required afterwards. But usually also all closed tickets that will be migrated into read-only documents. Like in the previous scenario, data management and exceptions management rules are utmost important.

SOMITO-2.jpg

The same advanced migration tasks as mentioned earlier can be considered :

  • Creation of document flow (linkage between tickets)
  • Assignment of Transport Requests (modifiable and even released one) to Change Documents
  • Re-assignment of Change Documents to new Project cycles
  • Upload of Cross-System Object Lock entries in Solution Manager

 

(3) - "Migration" of tickets from a Legacy (non-SAP) tool into Solution Manager 7.1 CRM WebUI tickets.

In this last scenario, a third-party tool (Remedy, Lotus Notes etc.) holds all the tickets that should be migrated, as it will be decommissioned by SAP Solution Manager 7.1 (fresh installation). This strategic move offers a lot of opportunities, as Solution Manager is not simply a ticketing tool but a comprehensive and integrated IT Management platform.

In this scenario, the complexity is to extract from the legacy tool a structured list of all existing tickets, with all key information that will be required to populate SolMan ITSM/ChaRM tickets. Beforehand, a complete set of master data has to be created in Solution Manager and the target processes have to be designed and implemented before migrating.

Finally, the migration can be performed, mass creation of 7.1 tickets in the target system. A common requirement is that the ticket get generated with their original creation date (in the past). The metadata (processing log, changes to document) can be transferred as text file and attached to the ticket like all other kind of attachments. And again the migration scope encompasses both open and closed tickets.

As previously data management and exceptions management rules are a key to data migration success.

SOMITO-4.jpg

At last, some advanced treatments can be requested post migration, similar to the one we exposed earlier.

  • Assignment of Transport Requests (modifiable, sometime released one) to Change Documents.
  • Assignment of Change Documents to new Project cycles
  • Upload of Cross-System Object Lock entries in Solution Manager using standard function modules

 

In a nutshell,

those are the main data migration scenarios and challenges I had to deal with so far. This return on experience relies on 15 migration projects, ranging from few thousands of tickets up to a massive 100,000 tickets. Each and every single of those project falls into one of the category described here, and even though the expectations and constraints were always somewhat different, my objective here was to emphasize the common patterns...

Hopefully this small overview was interesting for the community. If you have particular questions or inquiries, feel free to post your questions or to contact me directly..

Solution Manager 7.1 SP10 brings improvements in many areas, as we have already seen here in SCN. Last month I was working with Quality Gate Management scenario (QGM), which is part of the Change Control Management, and could notice some improvements in this area too.

 

As in ChaRM, QGM has been integrated to Central CTS and to IT Calendar in SP10.

 

A new check was added during the set up of the project:

    • Disable transport release in Scope phase

 

Some features that we already had in ChaRM were introduced to QGM, such as:

    • Downgrade protection
    • Task Lists
    • Urgent Change
    • System logon

 

 

First of all, I recommend you to read the General Note for QGM 7.1: 1509091. This note mentions the new features, product limitations, authorization roles (I also mention some info about authorizations in my blog) and inform many other notes that must be checked depending on the Support Package you have.

 

One specific problem that I had was corrected by SAP note 1964353 - QGM: Landscape Graphics shows gray shapes since ST710 SP10mentioned in the General Note:

 

"Starting from 7.1 SP09; new SICF /SAP/PUBLIC/BC/QGM was created to provide access to QGM MIME repository. This service need to be kept activated otherwise the landscape graphic will not be displayed correctly."

 

 

Central CTS integration

 

Central CTS provides a technical infrastructure for the enhanced flexibility functions in Change Control Management. It can be used not only with ChaRM but also with QGM projects. There is an excellent doc about Central CTS here in SCN that I recommend: How To... Set Up cCTS for ChaRM and QGM

 

In QGM you will see a checkbox to define if you will use the new infrastructure or not during the set up:

 

qgm_img7.jpg

Disable transport release in Scope phase

 

During set up, in step 4 (Assign Quality Gates to System Roles) you can flag that Transport Release cannot be done in phase Scope:

 

qgm_img8.jpg

Trying to release original transports while phase is scope:

qgm_img1.jpg

 

 

Downgrade Protection

 

There is a new button in the QGM area of the Change Management work center where you select the projects (same area where you find Set up), for Downgrade Protection check:

qgm_img9.jpg

This button starts the Downgrade Protection check for the project you selected, and you can see it looking at the Details area:

qgm_img11.jpg

 

When releasing transports in QGM, if Downgrade Protection is active you will see if there are Conflicts. A message such as

 

"Release of transport XXXKNNNNNN, XXXKNNNNNN, XXXKNNNNNN canceled due to open conflicts" will be shown.

qgm_img2.jpg

In this case, the release action has been canceled. You need to identify the conflicts and either set their status to "Ignored" to ignore them or try to solve the conflicts manually. Then you can repeat the release action.

It's important to consider that if you ignore the conflicts, the system will no longer consider these conflicts and execute the action. Ignoring conflicts might lead to inconsistencies, so be very careful.

Picture below shows the details of a Downgrade Protection check:

qgm_img3.jpg

Task List in QGM:

 

From SP10 on, a Task List can be created for the QGM Project. Below you can see an example of an implementation project with QGM active and a task list created:

qgm_img4.jpg

 

qgm_img5.jpg

 

If you work with Maintenance projects, you can create a maintenance cycle. In this case, instead of having the End of Project Q-Gate, you have a Q-Gate called Deploy to Scope.


It’s possible now to import only transports from a change, instead of all the transports of a project. An import subset is done in this case, not import project, but then keep in mind there are risks of wrong import order and downgrades:



qgm_img6.jpg


Urgent Change in QGM


Besides the transaction type SMQC for Changes in QGM that we already know, which was introduced in SolMan 7.1 since the first Support Package, now there is a new transaction type SMQU, which means QGM Urgent Change.

Vivek Hegde has already mentioned in details this new feature introduced to Quality Gate Management in his blog.


System Logon


In the Details area, below tab System Landscape Graphic, there is now a button for Logon to the systems. You select one of the systems of your project landscape and then click Logon to jump to the system (if you use the work center in a web browser, it will ask you to open SAP GUI)

qgm_img12.jpg


qgm_img13.jpg


Integration to IT Calendar


Again in the Details area you have tab "Calendar View". In this screen you see your project milestones in a calendar, and now there is a button "IT Calendar" to take you to the IT Calendar in Solution Manager. Tobias Hauk has explained a bit about this feature in his blog New features of Change Request Management (ChaRM) with SP10 (FP2).

qgm_img14.jpg

The IT Calendar integrated to QGM and ChaRM allows you to establish a central calendar for all your projects and changes:

    • Change cycle phases
    • Change transactions
    • QGM phases
    • QGM Q-Gates and milestones


Please be aware of some required settings that need to be configured in Solution Manager:


  • Specify for which system roles the entries will be created in the IT calendar for change cycle phases and QGM phases,.
  • Specify a threshold for the grouping of similar objects (example: set a threshold of 5 for Request for Change means that all requests for change on a particular date are grouped if their number exceeds 5).

 

Ex. of one of the IT Calendar settings:

qgm_img15.jpg

 

IT Calendar showing QGM project phases:

qgm_img16.jpg

You will find more information about IT Calendar in this blog: IT Calendar and CHARM integration Solman 7.1 SP10 (How To)

Actions

Filter Blog

By author:
By date:
By tag: