1. Log in to Solution manager system.


2. Access the Tcode SOLAR_PROJECT_ADMIN


3. then click on the CREATE PROJECT

create project.png

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

proj det.png

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

     Template is for global rollout.

     Optimization is for doing any customizing


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

lang n title.png

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

6. then click save

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


this is how you create a project.

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


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

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

Location: RT 15

Session ID: RT999

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


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

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

Location: Lines of Business Microforum LB221

Session ID: PS25097

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


Authorization Design at Almatis

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

Location: S331A

Session ID: BT1730

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


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

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

Location: S320G

Session ID: FI1686

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


Simplify Business Process Management and Modeling

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

Location: SAP Service and Support Center Demo Theater SC507

Session ID: SC20422

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


Put the Quality of Your Software to the Test  Microforum Discussion

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

Location: Partner and SME Solutions Center Microforum PS606

Session ID: PS22273

Speakers: Andreas Gloege, Quality Assurance Solutions (SAP)


Test-Drive New Solution Documentation in the Cloud

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

Location: SAP Service and Support Center Demo Theater SC507

Session ID: SC20416

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


How Verizon Used Automated Testing to Accelerate Its SAP Implementation

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

Location: S331C

Session ID: BT2012

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


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

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

Location: Theater 1

Session ID: PS20813k

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


Tools to Automate, Manage and Gain Efficiencies in Testing

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

Location: S310F

Session ID: PS1162

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


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

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

Location: Lines of Business Microforum LB221

Session ID: PS25097

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


Secure the Code That Runs Your Business

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

Location: Partner and SME Solutions Center Demo Theater PS605

Session ID: PS25064

Speakers: Lorie Volpe- Solution Strategist (SAP)



A Day in the Life of Setting up SAP Solution Manager

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

Location: S320B

Session ID: SM240

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

SAP TDMS for IS Utilities at AES (customer presentation)

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

Location: Room S310E

Session ID: IU1082

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


ASUG SAP TDMS Influence Council Session (supported by Nike)

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

Location: ASUG Theater A (on show floor)

Session ID: IF2377

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


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

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

Location: Roundtable #13

Session ID: RT2101

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


See you at SAPPHIRE!

settings done  action profile solman 7.1 support package 13

for information other things required check latest configguide for VAR scenario

For VAR scenario you can find a configuration guide on SAP Support Portal. Go to http://service.sap.com/support, tab SAP Solution Manager -> in left column choose "SAP Solution Manager for Partners -> Information for Service Provider -> VAR Solution Manager Setup -> Setup Documents". Expand "Administrator" area and you will find SAP Solution Manager 7.1 <SP<latest version> VAR Config Guide>


1. tcode SPPFCADM



note action profile ZMIN_STD_SEND_SAP_AUTO is not there by default .you can copy from another action definition say ZMIN_STD_SEND_SAP and adapt it to  ZMIN_STD_SEND_SAP_AUTO.




populate the container as per note 1084744 below.





sap note 1084744


3.1.4 Enter container values for the action definition AI_SDK_SP_SEND_AUTO


Select the application CRM_ORDER.

In the "Customizing and Configuration" section, choose "Define Action Profile and Actions".

Select the action profile "AI_SDK_STANDARD" and double-click "Action definiton" in the tree structure on the left. Select the action definition "AI_SDK_SP_SEND_AUTO" and double-click "Processing Types" in the tree structure on the left. Switch to processing mode.


Under "Settings Method Call", choose "Change Definition". Check the container element TEXT_ID    The initial value has to be SU99.  Change this (if required) by double-clicking the expression on the "Initial Value" tab.  Copy the change.


Create the following container elements if they do not exist already.:

Element = DOCU_NAME


Short Description = DOCU_NAME

Select "ABAP Dict. Data Type".

Type Name = DOKU_OBJ

Choose the "Initial Value" tab.


Choose "Confirm (Enter)".



Short Description = TEXT_ID which is transferred by resending

Select "ABAP Dict. Data Type".

Type Name = TDID

Choose the "Initial Value" tab.


Choose "Confirm (Enter)".



Short Description = Status executed when automatically sent

Select "ABAP Dict. Data Type".


Choose the "Initial Value" tab.



Choose "Confirm (Enter)".



Short Description = Status set after automatic sending

Select "ABAP Dict. Data Type".

Type Name = CRM_J_STATUS

Choose the "Initial Value" tab.


Choose "Confirm (Enter)".



Short Description = Additional status set in case of automatic sending

Select "ABAP Dict. Data Type".

Type Name = CRM_J_STATUS

Choose the "Initial Value" tab.


Choose "Confirm (Enter)".




set the conditions













You (or whoever managing your saprouter) may have received the following advisory already.

If not, regardless it's been past April 15th and we only have less than 3 months to act on this.

For those who are using saprouter VPN appliance, fear not as this only affects those customers who connect to SAP via SNC.

Affected customers should act now, else your SAPOSS connection will cease July 18th 2015.



SAP suggests to follow SAP note 2131531 to renew the saprouter certificate signed by the new SAP CA.

In addition to the instructions that are readily available in the SAP note and the detailed instructions link, this blog provides additional information in the hopes of helping you go through this renewal process easily and with little impact as possible. For example, the steps detailed in this blog allows you to test the connection before switching live to it.



SAP note/KBA:

2131531 - New Root Certification Authority for saprouter certificates



Detailed instructions:

Installing the sapcrypto library and starting the SAProuter | SAP Support Portal




1. Download the latest saprouter


As in the detailed instructions, follow the path. Also note that SAProuter 7.42 is available as of writing (latest patch level 111)

> Support Packages & Patches

> A-Z Alphabetical List of Products

> S



> your preferred O.S. version

> saprouter_XXX-XXXXXXXX.sar


2. Download the latest SAP Cryptographic Library

SAP Cryptographic Library Patch version 8435 is available as of this writing

>Support Packages & Patches

> A-Z Alphabetical List of Products

> S



> your preferred O.S. version



3. Create a new saprouter folder and extract the saprouter and cryptographic library files


NOTE: This is important if you want minimal disruption in your SAP link!


Create the new folder (e.g. /usr/sap/saprouter2). Copy the 2 sar files which you have previously downloaded to this folder.

Extract the sar files


# SAPCAR -xvf saprouter_111-*.sar



Also copy your existing saprouttab to this new folder


# cp /usr/sap/saprouter/saprouttab /usr/sap/saprouter2


4. Generate a new PSE and CSR


Set SECUDIR and SNC_LIB environment variables first

e.g. for csh in UNIX

# setenv SECUDIR /usr/sap/saprouter2

# setenv SNC_LIB /usr/sap/saprouter2/libsapcrypto.so


Then generate the PSE and CSR - where your CN is provided by SAP when you first requested the setup of your saprouter

# sapgenpse get_pse -v -a sha256WithRsaEncryption -s 2048 -r certreq -p local.pse "CN=<saprouterhost>, OU=<customernumber>, OU=SAProuter, O=SAP, C=DE"


Type in your PIN/passphrase when prompted.


View contents of the generated certreq CSR file, copy the text beginning from







into your clipboard


5. Paste the request/CSR to SAPRouter Certificates area

Logon to SAProuter Certificates | SAP Support Portal

Click on "Apply for a SAProuter certificate"

If you have multiple saprouters, choose the right one that you're working on

Click Continue

In the TextArea, paste your CSR content

Click Request Certificate


The next screen will show you the signed certificate.

Copy text beginning from








to your clipboard


6. Create a new srcert file and paste the signed certificate

In your new saprouter directory, create a new file called srcert.

Paste the signed certificate to that file and save.


7. Import the signed certificate to your PSE

# sapgenpse import_own_cert -c srcert -p local.pse

Confirm that the import was successful.


CA-Response successfully imported into PSE "/usr/sap/saprouter2/local.pse"


8. Create credentials for your PSE and secure your credentials file

# sapgenpse seclogin -p local.pse -O <user_for _SAProuter>

Type in your PIN/Passphrase when prompted

This generates the cred_v2 file

Secure your credentials file

e.g. for UNIX

# chmod 400 cred_v2

9. Confirm if certificate is imported successfuly

#  sapgenpse get_my_name -v -n Issuer

This should result to


Issuer  : CN=SAProuter CA, OU=SAProuter, O=SAP Trust Community II, C=DE


10. Import the old SMP CA Root certificate if today's date is before July 18th 2015.

Download the CA certificate from SAP note 2131531 (scroll down to attachment section)



Copy the smprootca.der to the new saprouter directory.

Import the certificate


# sapgenpse maintain_pk -a smprootca.der -p local.pse

Type your PIN/Passphrase when prompted


11. Test your new saprouter


e.g. in UNIX

# saprouter -r -S 3298 -K "p:CN=<host>, OU=<customer number>, OU=SAProuter, O=SAP, C=DE" -V 3


Note that with -S option you set the saprouter to listen to a different port other than the usual 3299. You can also set -V 3, so you get more trace info.


Set your SAPGUI or in transaction SM59, create a copy of your SAPOSS connection (e.g. copy to SAPOSS2).

Set the saprouter string (Msg.Server field) to use the above port





Test the connection.


Open or tail the dev_rout trace file to see if there are any errors


# tail -f dev_rout


11. Switch to your new saprouter when ready!

In UNIX you can do the following


saprouter -s

mv /usr/sap/saprouter /usr/sap/saprouter.old

mv /usr/sap/saprouter2 /usr/sap/saprouter

<start saprouter script> - something like

Using several free resources, we have gone live with Change Request Management.  As a start, we took advantage of the Expert Guided Implementation (EGI) for Change Request Management.  This is free for Enterprise Support Customers.  I knew when the courses were available by reading James Pearce content.  He is good about announcing when the EGI's are available.


For EGI's you spend a week with an SAP expert going live with your own sandbox system.  The SAP lectures are 2 hours each day, and you are given a 50+ page PowerPoint each day with some "homework".  The key is actually spending the time after the lecture doing the homework.  You need to have your Solution Manager system open so if you have questions that can't be resolved by e-mail SAP can log on to it.


Source: SAP


I want to thank Shamantha for her expert help and support during the EGI.  I couldn't figure out how to make a field open for editing.  Shamantha researched this and got back to me with the help the next day.


The downside of the EGI is your SP in SolMan may not be the same that the EGI covers.  We are on SP12 and a few of the screens were different.


Next, we also took advantage of the Ramp-up Knowledge Transfer for Solution Manager, also free.  These are available at service.sap.com/rkt-solman with a Service Marketplace logon.  This is free as well.  We used the recordings available and the processes listed.  The downside is the recordings are not on the latest release of Solution Manager so the screens do not match up.


Using the RKT demos, we created our own swim lanes for request for change, normal change, and urgent change.



The above is our interpretation/flow of the request for change.




Above is our normal change "swim lane".


Next, we took advantage of the resources in the SAP Learning Hub (note this is with a Learning Hub subscription; Discovery edition is free).  The Learning Hub explained things a little more in depth than the EGI did.  Learning from courses like SM200 and End to End, we created a step by step process of what the swim lanes depicted.


This formed the basis for our test scripts:



For knowledge transfer to the Change Manager, Change Admin and Developers, I used UPerform to record processes like SOLAR_PROJECT_ADMIN which is used to create projects.  This helped form the basis for training documentation.


Testing showed more changes needed to be made.  This is where SCN helped, and by searching my issues on SCN that lead me to Dolores Correa's Stuff | SCN content which helped us figure out how to get e-mail working with Change Request Management.


I also attended an ASUG webcast given by a customer on their Change Request Management solution.  They had been live with it for 2 years and in those two years never had an urgent change.  I liked the idea of limiting urgent changes, if at all possible.


So a combination of EGI, Learning Hub, RKT, SCN and ASUG helped us go live with Change Request Management.  We "get by with a little help from our friends" - hat tip to Ringo Starr, who is being inducted into the Rock and Roll Hall of Fame



Do you have a Solution Manager story to tell?  Next week, ASUG call for sessions for SAP TechEd Las Vegas opens.  ASUG would welcome your submission.  See Plan Now for Call for ASUG Speakers for SAP TechEd Las Vegas

In the Request for Change (ZMCR), I have configured the Approval Procedure to be determined by Multi Level Categorization.  When the ChaRM status is in "To Be Approved",  it does not make sense to allow the Categorization to be changed since the Approver Procedure might also change.   So, I had the requirement to protect the Categorization fields from changes when the status is "To Be Approved".     The IMG activity "Adjust UI objects by User Status" does not offer the Categorization fields for selection, so I needed to make the change in an Enhancement.


The following screen shots are from 7.1 SP11.


In ZMCR, put the cursor on the Category field and select F2.  Locate the UI Component name and View.





In tcode BSP_WD_CMPWB, enter the component name and Display...



Navigate to the Attributes in the Context Nodes and locate GET_I_CAT01 for the first Categorization field. If the logic is needed for the other Categorization fields, these changes can also be applied to GET_I_CAT02, GET_I_CAT03, and so on....



Create a new Enhancement in each GET_I_CATxx method as needed.   Here's my code...


method get_i_cat01.
"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""$"$\SE:(1) Class CL_BTCATEGO_CATEGORIES_CN00, Method GET_I_CAT01, Start                                                                                      A
*$*$-Start: (1)---------------------------------------------------------------------------------$*$*
ENHANCEMENT 1  Zxxx_CHARM_CATEGORIZATION_1.    "active version

data: ls_continue(1).

    PI_FIELD_SETTING = cat01_input_ready
    PO_RETURN        = rv_disabled
    PO_CONTINUE      = ls_continue.

if ls_continue ne 'X'. "continue with standard logic?

*$*$-End:   (1)---------------------------------------------------------------------------------$*$*
  rv_disabled = 'TRUE'.
  if cat01_input_ready eq abap_true.
    rv_disabled = 'FALSE'.






* Parameters are:


* PO_RETURN TYPE STRING " Editability status

* PO_CONTINUE TYPE CHAR1 " =X if standard should be processed

       ls_STATUS_TEXT    TYPE CHAR30,



PO_CONTINUE = 'X'. "default to process standard logic


* 1) Read ChaRM guid
      ev_header_guid = ls_HEADER_GUID.


* 2) Process only for ZMCR. If it is not, continue with original processing.
  select single process_type from crmd_orderadm_h INTO LS_PROCESS_TYPE
                             WHERE guid = ls_HEADER_GUID.

  if sy-subrc = 0

* 3) Read ChaRM status
        PI_GUID        = ls_HEADER_GUID
        PO_STATUS_CODE = ls_status_code
        PO_STATUS_TEXT = ls_status_text. "not used here


* 4) Check if pending approval. If it is not, continue with original processing.
*    The sequence for this was determined by watching in debug.
*    This will set the field to display only when in edit mode.
    if ls_status_code =  'E0012'.
      po_return = 'FALSE'.
      if pi_Field_setting eq abap_true.
        po_return = 'TRUE'.

      clear PO_CONTINUE. "skip standard logic






Fields are now display only when in status 'To Be Approved;....


Reflecting on past thoughts


I remember about three years back when i was involved  in a Solution Manager upgrade/implementation project, I advised a consultant from a Solution Manager consulting firm to dig into custom BW reporting on top of Solution Manager. In retrospect it's always nice to see advice was actually good advice. More and more customers are reporting on Solution Manager data nowadays so he should have had a head start on that by now already.


Revisiting reporting options


Not so long ago, I needed to do the same since we proposed at customer side to automate some statistical reporting which was generated in a manual fashion still. In the past I had done some discovery of potential options and some work on specific reporting (availability through ccmsping in a custom SLR for example) but not yet utilized custom queries. So I started again by looking at what's possible nowadays, some releases further down the road.




My first idea was to use custom queries in SLR (Service Level Reporting) in Solution Manager but that didn't work out as well as I had hoped. It's too restrictive and too slow to make quick adjustments and generate a result. Since I don't have a publishing platform (BusinessObjects, portal, ...) at hand at this customer on short notice I had to reside to an alternative option. You can see in above screenshot that it did work but you cannot build really advanced queries or anything so in the end it didn't have the requirements I was looking for.




In the end, I ended up using the Bex Query Designer and Bex Query Analyzer. Why? AnalysisOffice requires a specific license which is not in place.


I've played around with AnalysisOffice during ASUG preconference (at SAPPHIRENOW just recently) and it's indeed better / more interesting then Bex Query Analyzer.


Combining Bex Query Designer, Bex Query Analyzer and Microsoft Office, I was able to generate a PDF based report which meets the requirements of the customer in terms of reporting on KPI's. As a next step I will be looking at publishing options and leveraging the BI suite (Web Intelligence or alikes ...). You can read some related posts as I leveraged learning hub, read about that here and I tried out BW connectivity to SAP Lumira.as well which you can read about here.


Some challenges along the way:


  • The exception in Bex Query Designer is hard to leverage for building the graph in Excel. So I resorted to a calculated key figure matching the exception value so I have another column in Excel which can be used to build the graph.
  • I used an offset function to define the area where the data resides to have the graph dynamically build depending on the available data ~ some months are longer than other months and reporting on the previous month means you need a dynamic graph
  • Performance wasn't optimal ~ I leverage a number of Bex SAP notes to change some parameter settings to optimize the loading time and I also set the query refresh to single dataproviders in order not to be forced to refresh the whole workbook each time
    • I need to look into this further and potentially leverage caching as a way to speed things up further or try to use aggregation up front
  • Figuring out what's what isn't too easy, especially if you don't have a BW background so I spent some time on figuring out the key figures and how SAP calculated them to come to a specific result. Help.sap.com helped to some extent on the infoproviders and key figure description info (you need to know in what something is expressed also for example so check the content first ~ms versus second for example makes a big difference ).


In the end, it has been super interesting already to work this out and I look forward to do more around BI reporting on SAP Solution Manager based data. SAP Solution Manager 7.2 is approaching and as it approaches, I'll be checking what options we've got available there for custom reporting.

Solution Manager 7.2 was initially scheduled to be generally available by the end of 2015 (But reportedly postponed to Q2 of 2016) and will introduce big changes. From what we could see in the previews, we get a revamped Solution Documentation. What should we expect exactly? I have tried to synthesize all the information I got from the SAP webinars, with my comments as a Solution Manager consultant.

It would be great to discuss these planned changes. However, keep in mind that this blog entry is based on previews by SAP, and that the finished product might be different.



Pragmatic Business Process Management

Solution Manager 7.2 introduces what SAP calls “Pragmatic Business Process Management”. This is a way to underscore the fact that SolMan 7.2 is more “Business Processes Oriented. 7.1 was IT/Operations focused. 7.2 will try to balance things more, increasing value for Business Processes/Implementation. The goal is to get Business Process Experts more involved... This translates into most of the following items:



Documentation before project start

With more focus on implementation and Business Processes, one major flaw needed to be addressed. In 7.1, you can’t start documenting unless you have a landscape. This means that you business process expert can’t document unless the project actually starts. For 7.2, SAP want to decouple the documentation (or at least, the modelling of processes) from the actual landscape. The link will of course need to be done later on, but at least, there will be  no need to “wait” anymore.



Graphic Business Process Modeling

We gain a business process modeling tool, adapted from Power Designer. SAP is simply using the graphic libraries, so we shouldn't expect the functionalities of the tool. This modeling environment should be for business processes only (No enterprise architecture, no UML).

Screen Shot 2015-04-15 at 14.37.04.png

Source: SAP


Open interface to other Modelling tools

So far we had an integration with ARIS (that wasn't made by SAP). We should be getting an open interface that will make things simpler. Bi-directional, it will be possible to use it with any tool. It won't be part of the ramp-up (but added later).



Analytics extended to business cases

We should be able to relate business cases to KPI and thresholds from Business Processes Analytics Framework. The way to do it: We define this in implementation, store in SolMan, do our project, and in Live phase we can analyse and continuously check how well our KPI are met by the system users.



A new Documentation Lifecycle Model

Projects and Solution are two similar concepts for Solution Documentation in SolMan 7.1.

To document in Solution Manager, you will need to create a Project.

Let’s say you are starting an implementation, but will shift to maintenance after go-live. Then, the proposed model is as follows:

Screen Shot 2015-04-15 at 13.45.31.png

Source: SAP


So, you need to create an implementation project and document. This can be made from scratch, or using  “templates”. Once your project goes live, you need to transfer your documentation to a productive “Solution”, and then create a maintenance project. This maintenance project will be used for documenting your changes to the productive environment.

You end up with documents in double or triple, with different versions. You need to use the “compare and adjust” functionality…


As if this is not enough, projects and Solutions share a lot, but have a few specificities that make both of them necessary. So you should maintain both.


Solution Manager 7.2 will remove this issue by introducing one common directory for Business Process documentation. Projects and Solution are unified. New concepts are introduced. Old ones are rendered obsolete.



No more Reverse Business Process Documentation

We could see this coming. RBPD, or Reverse Business Processing Documentation, is a great functionality of 7.1. It helps you jumpstart your documentation in the less painful way possible. Instead of manually creating your process steps/ Business Processes and Scenarios, or having to choose them in the very dense BPR (Business Process repository), RBPD creates for you, based on your system usage, an almost ready to use Business Process Structure.

The disappearance of RBPD could be foreshadowed with the introduction of SEA, who also creates a ready to use business process structure for you (because SEA needs one). Or, even more so, with the introduction, with note 2061626, of the Blueprint Generator (used by SEA) as a separate functionality. The blueprint generator/SEA analyzes your system usage and create a Solution Documentation Project that contains all transactions and reports structured by the Application Component Hierarchy comparable to what you can already see in the IMG. Objects that are not standard are listed at the end, under “Customer objects”, and it is your responsibility to affect them to the right process step. This blueprint generator becomes standard tool to generate blueprints, and will be used by Solution Documentation.


And no more BPR

It gets replaced by the RDS Content.


A new architecture

New concepts are introduced by 7.2. Layers of libraries are now used to avoid redundancy of objects.

They are of 3 types:


Screen Shot 2015-04-15 at 14.03.19.png



Objects will be in the TOL only if used, with only one occurrence, and structured according to the application component hierarchy.

The PSL will also be created automatically based on usage. Multiple occurrences (of technical objects) will be allowed.

Process Step Library and Technical Object Library are available by system. E2E business process will be used to document across systems.

The creation of the E2E should be simple (you pull steps from the individual systems in the E2E library) but not required, as the TOL & PSL are enough to work with SolDoc. You can start testing as soon as SolMan is set up.



No more Solar Transactions

If you are somehow familiar with Solution Documentation, then you must know about the SOLAR Transactions. They are used to create, manage and do some reporting on your documentation project.

Those transactions are the heart of solution documentation in SolMan 7.1, and simply disappear in 7.2.

We gain instead, it seems, two mains views: The Solution Landscape UI, and the Solution Documentation UI.



Business Process Hierarchy with unlimited levels

In 7.1, you document with a 3 levels hierarchy: Scenarios, Business Process and Process Steps.

Without Solar transactions anymore, it's no surprise that the way structures are represented will change considerably. Instead of this 3 levels structure, we are getting boxes representing levels, and the possibility to have as many levels as we want. However, the 3 levels are still there, and will be the core of the documentation. We will simply be able to add as many levels as we want on top of them. This will be very close to the workaround used right now, which consists on coding levels through naming convention (combining levels in Scenarios names, for example).


Lifecycle based on Branches

Among the new concepts introduced, the “branches” hold a significant place. If you want a simple definition for a branch, it is simply, according to SAP, a versioning context for documentation. What this means is while we don't have the implementation/maintenance projects anymore, you will be able to maintain your different documentations without affecting the one that is productive. It's based on views that contains only pre selected processes.

Screen Shot 2015-04-15 at 14.14.05.png

Source: SAP



Integration with ChaRM

You have a change document open for some maintenance in your system, tracking your changes. The corresponding documentation is in the maintenance branch of your documentation. When your ticket is productive, you will simply need to make your maintenance documentation productive. And apparently, this is done automatically. So, 7.2 adds a new layer of SolDoc/ChaRM integration, which is great.

Screen Shot 2015-04-15 at 14.27.52.png

Source: SAP


Requirement management

SAP introduces requirement management in Solution Documentation, and in ChaRM. This will be particularly interesting for ChaRM, as It seems we are getting new transactions types for IT and Business Requirements. A workaround so far had been to adapt some of the standard transaction to allow requirement management using some specific statuses.



Logical component group

They get introduced to make logical components management easier and avoid redundancy of documentation. We should end up with much fewer logical components.



This is what I got for the previews. I will update my blog post or create a new one once I get access to SolMan 7.2.




The SAP Solution Documentation webinar can be found here:



Some additional information in the webinar on Solution Manager 7.2:


When working with the Diagnostics scenario in the Solution Manager, We must be very careful about the Introscope Enterprise Manager and always keep an eye on it to ensure the data collection is working well. The problem is that depending on the size of the landscape involved, this scenario can grow fast in complexity and it'll become difficult to identify if the EM is taking care of the job easily or if it is becoming overloaded.


The EM itself generates a file called "perflog.txt" which is simply a collection of performance metrics which are stored every 15 second cycle. This data is very useful to understand how the Enterprise Manager has been handling the load and if any action is required to improve its behavior. The hard thing about analyzing this file is that it generates a lot of data depending on how long the Enterprise Manager has been up and running.


With the help of my colleagues Roland Hoeller and Allam Drebes, a tool was developed to facilitate this analysis, and also share our knowledge with the customers. The EM Perflog Analyzer tool performs a series of checks in this file and provides recommendations accordingly. Right now, we're releasing it under version and it can be downloaded from its wiki page.


In this version we've added 5 main checks to be performed over the perflog file, which are the following:


  • Number of Metrics
  • Number of Agents
  • Java Heap Space
  • Harvest Duration
  • SmartStor Duration


Through these checks it is possible to identify if the EM is struggling to handle the load and needs any action from the user to correct the problem/avoid future issues. We plan to include more checks in the future as the tool develops further, but right now our focus is to deliver the tool with the most important checks and ensure it is working stable.


The main advantage of using this tool is that it'll make possible to understand how well the Enterprise Manager is working and predict issues beforehand based on the historical data present in the perflog.


I'm glad that we're releasing this tool today and I hope to hear the feedback from the community, to further improve the tool and facilitate the task of keeping the Enterprise Manager running well and reliable.

Please leave us your feedback and also let us know if you run into any issue when using the tool.

e delivered standard content for Guided procedure as alert resolution path for alerts that arise in job monitoring for ABAP Jobs.

Starting 7.1 SP12, this feature is available in the standard in Job Monitoring.





Launch the GP.



Step 1 of the GP provides link to open the alert details in a seperate window.




Subsequent stpes provides options to launch the job log in the managed system. This is mandatory step to be performed(also manually) as expect a job log holds the details of the execution of this job.


We provide also the jump-in to launch the job documentaion. Should the job be documented, the alert resolution could might well be docuemnted in the job document.




Beyond the standard GP delivered, it is possible to author GPs as well with customer specific resolution mechanism.

Entry point to the configuration from Technical monitoring workcenter


In Job Moniotring, move to step 4, define scope. Select a technical scenraio of interest (else you may want to create one). Technical scenarios are logical grouping according to the user requriement. There can be scenarios that represent for instance, all systems that belong to a business process or being monitred by a particular shift of operators or grouped based on the region of data source.


Select a scenario and move to .2 step for alert configuration. The top table provides an overview of all the selected metrics. On lead selection, the thresholds provided for each metric and the alert texts for selected monitored objects is available.



=> On edit, the text box next to ALERT TEXT opens up for editing. This is a re-usable technical component that is available for system monitoring as well.




2. Generate

3. Activate


For the changes to be seen in the notification triggered from Auto-notification and to see these texts in the alert inbox, when an alert is triggered for this MO.


Regards, Raghav

For some time now, I have been thinking about a way to allow functional people to monitor processes and message flows, but without letting them use SAP PO. In the past, PI monitoring came close and was not bad at all. But now, my requirements are completely covered using Message Flow Monitoring on SAP Solution Manager. This is what functional people need!


We use a SAP Solution Manager 7.1 SP12 system in conjunction with a SAP PO 7.4 SP09 system.




SAP PI 7.31 SP07 or higher and SAP Solution Manager 7.1 SP09 or higher. Also, make sure all MFmon related OSS notes are implemented, depending on your Solution Manager’s SP level. More information can be found http://wiki.scn.sap.com/wiki/display/TechOps/MFMon_Prerequisites#MFMon_Prerequisites-RelevantSAPNotes -> Relevant SAP Notes.


For all managed ABAP systems to be monitored with Message Flow Monitoring, make sure

  • ST-PI 2008_1_* plugin SP08 or higher is installed
  • In the SAP Solution Manager Configuration work center, the Managed System Configuration scenario has been performed.


You have set up Integration Visibility and run a discovery of your PI system landscape.

In case you need more (specific) setup details, please do let me know




On the SAP Solution Manager system, take transaction SOLMAN_SETUP…


… and follow the guided procedure.


All the steps in the guided procedure are very straight forward. For that reason, I will not go into detail.


Keep in mind that the Flow Maintenance (5) and Flow Group Maintenance (6) steps are imported. Here you build up your monitoring looks and provide names for an Integrated Scenario or a group of Integrated Scenarios.


Helpful extras


  • Once the setup was finished, I found out that the reporting part was not working at all. To enable it, please do the following: take transaction SICF, put in the field Service Name the value solmanlib and activate that service. Do the same for service name wda_e2eem_mf_overview
  • More information on (specific) Message Flow Monitoring authorizations can be found in a PDF document
  • Be aware of the payload part. You need to define User-Defined Message Search items on your SAP PO system. Only those ones will be visible.
    Have a look at the screenshots below.


An impression

general overview...


Again a general overview, but slightly different look


General overview with more details displayed.


Specific flow with all relevant details and payload



The flow track, in graphical modus, with the different systems involved.

For each system, a message status is available.



Reporting overview


Reporting details


Reporting details with a legend next to it



The second part of this tutorial, will show you how to install the certificate in the mobile device, in this case, I will install the certificate in my iphone.


For the part 1 of this tutorial use the following link:

How to use the new ONE Support LaunchPad(Ex-Portal) your Mobile devices - Part 1 / 2



1).-  I sended the certificate by mail to my email that is accessible by my mobile device. is important to attach the certificate file (certificate.p12)





2).- When you click in the attachment, the IOS will show the following screen, click on "Install"



3).-  Now you need to type the password that you use to export the certificate from your computer



4).- After the successful installation, you will the the Confirmation screen, press OK to continue.

5).-  Now connect to Launchpad.support.sap.com from Safari and start to enjoy the ONE Support Interface!!!!


Hi All

SAP Release the new ONE Support Launchpad (ex-Portal ) (https://launchpad.support.sap.com) that run in HCP with Fiori Style!!

This guide show you how to install a Digital Certificate in your mobile device and access to the new Portal Launchpad from you mobile device without type user/password every time.

For the part 2 of this tutorial use the following link:


How to use the new ONE Support LaunchPad(Ex-Portal) your Mobile devices - Part 2 / 2



1).-  Logon to service.sap.com/tcs with Firefox/Iexplorer


Screen Shot 2015-04-02 at 2.48.11 PM.png



2).-  Select the option Single Sign-On with SAP Passports from the left menu and click on the red button "Apply Here"Screen Shot 2015-04-02 at 2.48.46 PM.png



3).-  The system will ask your OSS Username and passwordScreen Shot 2015-04-02 at 2.49.15 PM.png




4).-  In the following screen you need to write your password again and click on "Apply for SAP Passport" button

Screen Shot 2015-04-02 at 2.49.35 PM.png

5).-  Firefox will confirm that the certificate was installed OK
Screen Shot 2015-04-02 at 2.49.51 PM.png

You can check that is installed in the right way going to "Advanced--> Certificates--> Your CertificatesScreen Shot 2015-04-02 at 2.50.09 PM.png

6).- now you need to select the certificate and click on the Backup button Screen Shot 2015-04-02 at 2.50.29 PM.png  

And select the folder and Name to save the certificate in your desktop
Screen Shot 2015-04-02 at 2.50.47 PM.png


The system will ask you a Certificate Backup Password
Screen Shot 2015-04-02 at 2.50.57 PM.png


7).-  after the successful execution, the system will show you the following screen and you will have your certificate file in your desktop.Screen Shot 2015-04-02 at 2.51.05 PM.png

    As administrators of solution manager, we are enthrusted with the responsibility to set up monitoring for BW process chains,   BO jobs, DS jobs. We wonder, sometimes, what would be good values for thresholds for certain time relevant metrics like Duration or typical values for records processed and/or data packages processed.


We all believe the past performance of the process chians & jobs are indicative of their general performance over a period of time. It would be very effective to have these values (Minimum , maximum, average of the last 10 executions) of these chains/jobs made avialable at the time of setup (SOLMAN_SETUP) and configuration to enable effecient monitoring.


BI Monitoring, provides this possibility.

In the SOLMAN_SETUP-> Technical Monitoring - > Job & BI Monitoring -> Bi Monitoring - > Step 4 (Define scope)-> Choose scenario - > Step 6 -> Monitoring & Alerting


Go to any of the monitored object types sub stesps( 6.1 to 6.4)


Choose the relevant chains/jobs and click on THRESHOLD MASS MAINTANANCE

In the below screenshot you could se that we can provide absolute value as +/- from MIN, MAX, LAS, AVG




A simlar example is with a percentage +/- for metrics (in this screenshot for Records procesed)



At this point in time, the values are fetched fomr the managed system and the corspoding values are calculated and shown in the main ALV. on Save & activate, these values atre persisted to the monitored objects. At this moment a pointer is converted to the value and the values are persisted!


As mentioned earlier, this is syncronised at this point in time. And not automaticallly adjusted as time progresses. But should there be a need, this reactivation can be done en-masse.




Regards, Raghav


Filter Blog

By author:
By date:
By tag: