1 4 5 6 7 8 37 Previous Next

SAP Solution Manager

552 Posts

1. Issue

When configuring solution manager CBTA for test automation related to SAP CRM 7.0x, some CRM services need to be activated.
Services such as UIF_LOGON en TAF_APPLAUNCHER.

 

example of error message: Service cannot be reached. What has happened: URL xxxxx/sap/uif_logon call was terminated because the corresponding service is not available.

 

 

2. Activating service TAF_APPLAUNCHER

In CRM backend, tcode SICF,

Search for service name *TAF* and apply filter.

note that taf_applauncher is not active.

Activate service.

 

 

 

3.Activating service  – UIF_LOGON

In CRM backend, tcode SICF,

Search for service name *UIF_LOGON* and apply filter.

note that service is not active.

 

 

 

 

 

First timer blog, any feedback is welcome.

Thanks and with kind regards,

 

Yee-Tee

We are in the Big Data age, we want to process a large amount of data and provide with enough predictive information to take an executive decision, if possible in a tablet format.

 

SAP Solution Manager is for sure one of the key data collectors that contain critical information about your IT landscape, system health, KPI’s, SLA’s, etc.

 

So, here we have the challenge: We need to provide executive dashboards for decision takers, in a tablet format (role based) and take the information from different sources, including the SAP Solution Manager

 

How to do this? Simple, with SAP Smart Business executive edition


Note: This is valid for on premise SolMan or for hosted editions (VAR’s, SMaMS) in this case, you need to ask your provider to provide you with the information required

 

Let’s plan it in just four steps:

 

1st Step:

First at all you need a SAP HANA System, some of you will stop reading now, but is not than complex, you don’t need a big system, on premise, nowadays with the SAP Cloud Appliance Library you can get a SAP HANA System in less than an hour, just go to http://cal.sap.com and select the cloud provider most suitable and that is all.

 

2nd Step:

Define a SAP HANA datamart (in this case your SAP Solution Manager) and connect it to your SAP HANA standalone system, data is transferred into SAP HANA with data services from several sources

 

3rd Step:

Install the SAP Smart Business executive edition, it needs no extra license beside the SAP HANA license itself, and you can download it from the SAP Service Marketplace:

 

Installations and Upgrades >> Browse our Download Catalog >> SAP In-Memory (SAP HANA ) >> SAP HANA Add-ons >> SAP SMART BUS EXEC.ED >> SAP SMART BUS EXEC.ED 1.0

 

4th Step:

Start building your Dashboards:


4.1 Select Data Source in SAP HANA

From your datamart you populated some SAP HANA view or table, it become available as the basis for the dashboard. By selecting the view and giving it a talking name, a catalogue of usable views is built up. 


4.2 Define KPIs

In this step the measures, dimensions, hierarchies in the view are identified. “Speaking names” can be assigned. Technical dimensions and hierarchies in the SAP HANA view can be assigned to a logical dimension in the KPI repository to allow global filters. Benchmarks, trends and the information design are defined. Number formatting is specified. Calculated KPIs may be defined. This can be done by business experts in a very simple and straightforward way. 


4.3 Define Visualization

The visualization of KPI's through tiles and charts are defined in this step. However, the information design, semantic coloring and number formatting is inherited from the KPI definition. The same holds for filtering dimensions. So per definition the information design is kept consistent throughout the dashboard and global filters are possible. This again can be done by business experts in a simple and straightforward way.


4.4 Compose Stories and Dashboards

Stories are collections of semantically related tiles, e.g. tiles about a certain topic like “Profitability”. Stories also define the multilevel Navigation between the different tiles. Dashboard can be composed by selecting on or several stories and either using all or a subset of tiles contained in that story. This is easy to do for end users.

 

Then you can consume the dashboard with your laptop, tablet or smartphone and take informed decisions without delay or need to be "at office"

How many of you remember ASAP, which used to come in a CD format? It had the necessary tools and content (right form QAdb to CI templates, if you remember) necessary for SAP Implementation. It evolved into ValueSAP & which finally evolved into Solution Manager.

 

Now I know, most of us from the SAP community are aware of SAP Solution Manager (fondly called as SolMan for brevity sake ), but are blissfully unaware of the rich functionality it has & so we end up utilizing it, to maybe, only 10% of its features. 

 

Don’t believe it?

 

Ok, let me ask you a simple question. Will you buy a smartphone and use it only for, say, morning alarm?

Absolutely NO!

 

...But that’s what we’re doing with SolMan (which incidentally comes absolutely free bundled with the SAP licenses you purchased) Most of the SAP customers are using its only one feature of SolMan, and that is to configure the SAP Router as a diagnostic agent connected with SAP and vice versa.

 

And unlike other freebies, SolMan is a power-packed tool, an integrated online platform to support implementations, operations and optimizations, in short the entire suite of ALM (Application Lifecycle Management). The ALM approach is holistic, because it covers aspects of deploying as well as optimizing your SAP solution.

 

During the deployment (more popularly called as ‘Implementation’) phase, it helps you in (related ASAP phases mentioned in brackets) are:

  • Central maintenance & access to all managed systems  (Project Preparation & On-going)
  • Central design & storage of all your business processes (Business blueprint)
  • Central definition, maintenance and storage of all business processes & technical documentation  (Business Blueprint & Realization)
  • Central creation of storage of test information (Realization)
  • Central creation and storage of custom development  (Realization)

 

Once the Implementation phase is over, Solution Manager comes handy in the post-Go-Live support (popularly called as Sustenance phase) for IT Service management. Solution Manager can easily be configured as a ticketing tool to manage the incidents/tickets. Considering other ticketing tools (like Remedy / Peregrine) come with a heavy price tag, it is worthwhile for customers to explore Solution Manager as a better (& cost-effective) option. 

 

More importantly, SolMan is very effective for Technical Monitoring during the Sustenance phase. It provides:

  • System monitoring – Allows you to access the latest snapshot of monitoring data for systems, databases & hosts
  • Jobs & BI monitoring – Allows monitoring of backgrounds jobs or complete BI scenario
  • End User Monitoring – Provides you availability and performance information from end user point of view
  • Integration Monitoring – Provides central access to monitor interfaces for performance, usage, availability & exceptions
  • Alert Inbox – Provides you access to alerts coming from different areas

 

  • Automated reporting – Provides access to view EWA (Early Watch Alerts) & Service Level Agreements
  • Interactive reporting – Provides you various pre-built reports about availability, performance, capacity & usage of your systems, scenarios, databases & hosts

 

Most of the reports are available as a Dashboard, which is a big plus.

 

For those who follow ITIL (IT Infrastructure Library) closely, SAP Solution Manager 7.1 has been also verified as ITIL compliant in following 15 core processes (to name a few ranging from Availability Management, Change Management to Service portfolio management etc.)

 

 

 

Now, again ask yourself the question, “How much functionality of Solution Manager my organization (or, my client) is using?”

On July 9th Evan Stoddard will be going over the SAP Solution Manager Road Map Webinar.  Evan will be going over current and future capabilities for SAP Solution Manager.   Recording available here: http://go.sap.com/assetdetail/2015/07/1c046390-337c-0010-82c7-eda71af511fa.html

Keep up to date on road maps here: http://scn.sap.com/community/product-and-solution-road-maps

Dear followers

 

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

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

 

https://service.sap.com/sap/bc/bsp/spn/esa_redirect/index.htm?gotocourse=X&courseid=70284599

 

Best Regards

Mateus de Freitas Pedroso

 

 

 

 

 

“Select and unmark group id SM-CREATE”

 

 

 

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

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

s2c_setup.png

 

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

 

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

 

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

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

(SAP Service Marketplace login required)

https://go.support.sap.com/kpicatalog

 

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

 

Full text search

Search.jpg

 

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

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

 

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

 

Multiple filter

Multiple filter.jpg

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

 

 

Details Overview

Detail overview.jpg

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

 

Details Definition

 

Detail definition.jpg

 

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

 

Details Technical

Detail technical.jpg

 

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

 

 

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

 

Further reading

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

 

Frequently Asked Questions about Business Process Monitoring and Business Process Analytics are answered under http://wiki.sdn.sap.com/wiki/display/SM/FAQ+Business+Process+Monitoring and

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

 

The following blogs (in chronological order) provide further details about Business Process Analytics and Business Process Monitoring functionalities within the SAP Solution Manager.


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

 

https://go.support.sap.com/kpicatalog

 

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

 

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

 

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

 

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

 

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

 

Filter according to Application Area

Appl area.jpg

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

 

Filter according to Business Goal Area

Business goal.jpg

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

 

Filter according to Category

 

Category.jpg

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

 

Filter according to End to End (E2E) business process

 

E2E process.jpg

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

 

Filter according to Industry Solution

Industry.jpg

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

Filter according to Product

 

Product.jpg

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

 

Filter according to Usage

Usage.jpg

 

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

 

Filter according to New / Updated

New.jpg

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

 

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

 

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

 

Further reading

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

 

Frequently Asked Questions about Business Process Monitoring and Business Process Analytics are answered under http://wiki.sdn.sap.com/wiki/display/SM/FAQ+Business+Process+Monitoring and

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

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

 

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

 

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

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

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


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

Job Monitoring – Notes to be implemented

About Job Monitoring:

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

 

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

 

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

 

  • Technical Monitoring
  • Business Process Monitoring
  • Job Management

 

Highlights

 

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

 

Prerequisites


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

 

Notes to be implemented in Solution Manager System,

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

 

Solution Manager SP

OSS Note

SP10

1909902

SP11

1972127

SP12

2038659

 

Notes to be Implemented in Managed (satellite) system,


ST-PI Release

Notes to be implemented

< ST-PI 2008_1_* SP09

1866169

= ST-PI 2008_1_* SP09

1956134

= ST-PI 2008_1_* SP10

2022442

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

2080101

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

2171512

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

2225431

 

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

 

ST-A/PI Version

OSS Note

ST-A/PI 01M and 01N

1581417

ST-A/PI 01P

1706837

ST-A/PI 01Q

1870459

 

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

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

 

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

 

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

 

Capture.jpg

 

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

 

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

 

Step 1 - Create a Custom Template

 

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

Capture.jpg

 

Now Click the button EXPERT MODE.

 

Capture.jpg

 

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

 

Capture.jpg

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

 

Capture.jpg

 

Step 2 - Adapt the Subject for Alert description.

 

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

 

Capture.jpg

 

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

 

Save the changes.

 

Step 3 - Activate the new Template

 

Now choose the step 6 - SETUP MONITORING

Capture.jpg

 

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

 

Done.

 

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

 

Capture.jpg

 

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

 

Capture.PNG

 

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

 

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

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

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

 

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

 

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

 

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

 

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

 

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

 

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

 

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

 

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

 

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

 

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

 

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

Dear All,

 

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


1.     Pre-requisites

               - Recent EWA report for the Satellite system

 

2.     Update service content

               Logon to Solution Manager system and execute t-code AGS_UPDATE

 

         

 

 

          Select Register Service

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

 

         

 

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

 

         

 

          Apply updates

 

        

3.     Create Self Service

          Execute T-code: SOLMAN_WORKCENTER

          Tab SAP Engagement and Service Delivery -> Services

          Select Create

 

         

 

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

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

 

          Resolution

 

          Run SE38 -  DSWP_CI_SERVICES_MAKE_SELF_DEL.

          Select SAP GoingLive Check and active this option.

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

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

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

 

         

      

          Execute T-code: SOLMAN_WORKCENTER

          Tab SAP Engagement and Service Delivery -> Services

          Select Create

 

         

 

         

 

         

 

          Enter the session planned date

 

         

 

          Assign contacts exists in Solution Manager system

 

         

 

         

 

    

              

 

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

 

              

              

 

               

 

               

 

                

 

                                                                 

4. OS/DB Migration Analysis – Prepare

                

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

           

                   

 

                    Select the product planned for Migration

 

                   

 

 

                   

 

                    Specify the source hardware

 

                   

 

                    Specify the target hardware

 

                   

                     

                    Answer the initial questions considering future requirement

                

                   

 

                    Specify the other systems involved in the current landscape

 

                    

 

                    Enter the technical data of system landscape

 

                   

 

                    Specify the project schedule dates

 

                   

 

                

                   

                

                    Finish prepare session

 

                   

 

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

 

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

 

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

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

 

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

 

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

stack.jpg

Without SFIN 1.0, select Support Package Stacks

Click Continue

targetstack.png

Select stack level which is applicable for SFIN 2.0

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

Select Applications for FIN 700

Click Continue

vhcal.png

Click Continue

addon.png

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

applied.png

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

relatedcomp.png

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

Actions

Filter Blog

By author:
By date:
By tag: