Continue exploring Partner determination with default or dependent values, with certain conditions to have more flexible ITSM / CHARM procedures. There is topic on how to setup Partner determination via BRF+ and very good blogpost  from Vivek . But  why not think about other possibilities? And here comes crm framework called Rule policies, it is mainly used in solman as Dispatch tool, but if you digg it deeper the true possibilites are opens to your eyes


Example Scenario: Rule policy ITSM / CHARM partner determination (NO ABAP REQUIRED).



1.    Assign Rule modeler to Categorization schema of CR

2.    Create Rule policy type SRQ ZMCR_DEFAULT_BP

       Mapping If category = CAT_1 then route developer = 11.


4.    Assign policy

5.    Assign Service Maanger Profile to Change Request transaction

       Change Request = ZCR_SRQMROUTING

6.    Test



1. Assign Rule modeler to Cat schema of CR


First let’s go to Solman’s CRM WEB UI and setup things we need

Tcode SM_CRM – Service Operations – Categorization Schemas

Choose your Schema that assigned to Change Request

Add new version, go to Application Areas and press New and add

Appilcation ID – Rule Modeler

Parameter – Context

Value – Service Request Management

We need to have a row like a last row in pic below:



2. Create Rule policy type Service Request


Tcode SM_CRM – Service Operations – Rule Policy, now here we need to create a new Rule policy



Context – Service Request Management.

Give some name to Rule Policy



This technology will work for any type of Solman transactions both ITSM or CHARM.

Now its most interesting part – the design part!

Choose Draft Rules row, press Subnode


Name it as you like f.e. Category = Partners and hit Subnode again



Again give proper name to avoid confusion when you read policies and press Add Entry in Conditions block






Attribute – Order Category

Operator – Contains

Value – choose category you wish to map the partner functions f.e. our popular Change Manager in the example it is ATH


Now in Action block press Add Entry

Choose Action – Route to a Partner, Partner Function – SDCR0002 Change Manager, Partner – who we need to assign as Change Manager in this case


For example I have setup all needed partner functions to be filled for the category ATH see below:

Developer, Tester, Custom partner function and etc.


Do not hurry to go to the next topics, take some time and sit here, because here you can make any scenario you need.

For example you can combine multiple checks for any situation: User status, Priority or Change category with other condition like check the category. You may Match conditions with AND / OR operators.


3. Copy SAP_SRQMROUTING Service Manager Profile to Z/Y


Tcode SPRO - Customer Relationship Management - E-Mail Response Management System - Service Manager - Define Service Manager Profiles. Choose SAP_SRQMROUTING and press Copy button on the top, name it like ZCR_SRQMROUTING


4. Assign Rule policy to Service Manager Profile


Stay on your ZCR_SRQMROUTING – double click Directly Called Services – double click Properties

Policy = your created policy in our case YALM_ZMCR_2


5. Assign Service Manager Profile to Change Request transaction


Transactions - Additional Settings - Assign Dispatching Rule Profile to Transaction Types.




6. Test


Now go to SM_CRM and create or pick any Change Request and press More – Dispatch all partners will be filled as mapped like here: Choosed category = ATH, pressing Dispatch


All partners filled


This will work even if Partner Function is not empty


Have Fun J


With 7.1, the capabilities of central monitoring has immensely improved in Solution Manager. For setting up of monitoring of systems in the BI landscape and objects in these systems, we have certain options available now.
1. Via Technical Monitoring - BI Monitoring
2. Via Business Process Monitoring (BP MON) - BW process chain monitoring.
3. Via Unified Job Monitoring

I would like to highlight what is a good option to do and what are the pros and cons with each approach.


What is BI Monitoring In technical Monitoring

To provide central monitoring and alerting capabilities. Integrated with Guided Procedure for alert resolution path. This is to cater to the need of an administrator to get an overview of the health of the systems participating in the BI landscape in addition to the objects specific to the data flows within the landscape.
Target audience:
BI administrator
BOBJ administrator
Application Support
BI operations Team


1. Overview Monitor

A single screen overview of the
Health of all systems participating in the BI landscape
  • Availability
  • Performance
  • Exception
View of the health of data flow entities in the landscape
o BW Process chains (ETL)
o BOBJ jobs (Reporting)
o DS Jobs (Replication)
o Bex Queries & Templates (Ad-hoc Reporting)

2. Detail Monitors

Provides specific information on the health of these monitored objects by monitoring certain metrics per instance of these recurring jobs which are representative of the health of the data flows across the systems.
Overall health of the job
o Status
o Error logs * (managed system login maybe required)
Scheduling metrics
o Start delay
o Not Started on Time
Runtime metrics
o Duration
o End delay
o Out of time Window
Data integrity metrics
o Records processed
o Data packages processed
o Rows_read
o Rows_written * Data services

Supported system types in BI Monitoring
System Monitoring Metrics are integrated in the overview monitor of BI for following system types

  • SAP HANA Database
  • BWA(TREX system)
  • ABAP Source system
In addition to the system monitoring metrics, we can configure jobs/reports on top of these systems to be monitored.
  1. SBOP  (SAP Business objects platform jobs in CMC)
    1. 3.x
    2. 4.x
    1. 4.1
    2. 4.2
  3. BW ABAP server (Process chains, BeX Queries, Templates)


As you can see, these screens have a designated flow for navigation. A single overview screen to show the health of all participating systems in the landscape and subsequently drill down capability by system-type and then to the monitored objects per system and then to its instance details!

Some key features in BI Monitoring (Configuration time in SOLMAN_SETUP) which caters to handle mass objects in configuration UI

  1. Mass maintenance of Thresholds
  2. Take from managed system to assist in configuring thresholds
  3. Excel Upload & Download
  4. Provides the managed object details in the configuration to assist in providing thresholds value for metrics like  (Duration, records processed etc.)
Nevertheless, this application has certain limitations.
1. Runtime (Monitoring UI) is not always colured!

The Monitoring UI could report grey rating for certain monitored objects which are not frequently executed in the managed system. Like a chain that is executing only once a week in the managed system. The collection frequency is set to 5 minutes in solution manager. So the status of these chains in the monitoring UI will turn grey,10 minutes after the chain ends today. And kicks in only for the next execution, that is in the next week! Howevere the alert (if any) would remain in the alert inbox with the history of measurements.
{Increase the collection frequency. Instead of (once every) 5 mins, make it once every hour. Esp for longer running chains. This would mean the monitoring stays colourful for twice the collection frequency. so instead of 10 minutes, its available for 2 hours.  This has a flip side, "delay in alerting" bad news that of failure.}

2. Alert inbox has multiple alert groups open, for instance, for the same BW process chain LOG_ID due to
    1. Grey metrics (collector issue, MAI extractor issue, Engine design
    2. If an open alert of a chain failure is confirmed in the alert inbox, the next collection will again report this error and an alert is opened up again! (owing to a fixed look back time of 36 hours for the ST-A/PI collector)



=> SERIOUS CONSEQUENCE : Multiple (duplicated) email automatic notifications

Workaround for reducing the number of duplicate emails. (this does NOT eliminate the duplicate alerts. This would only reduce the duplicate emails)

1. Reduce the collection interval to a small and relevant window (to reduce the occurrence of grey metric from collector)

    1. However, in the advanced tab in scheduling of data collection, Managed system time zone is  not handled in ST< SP10 (UTC is considered)
    2. If the chain is  executed  over the midnight, it is not possible to configure this restriction in the design time

2. Increase the collection frequency. Instead of (once every) 5 mins, make it once every hour. Esp for longer running chains. This reduces the probability of a grey alert!  This has a flip side, "delay in alerting" bad news that of failure.

3.  Starting SP10, 2118848 can be implemented and the report program AC_BIMON_MASS_AUTOCONFIG to be executed with 'set retention time' to cicumvent this problem.


3. No analytics capabilities of the collected metrics. vis-a-vis Interactive reporting. No BW reporting!

What is it to monitor BW process chains Via BPMon - BW process chain monitoring?

    In order to support the end to end monitoring of Business processes, that could span across several systems and can internally comprise of different entities like interfaces, jobs, process chains, in Solution Manager, we have the possibility to orchestrate a Business Process and setup monitoring for the participating entities. In such a context, Process chains can be setup for monitoring.

    => A clear Business process driven approach for monitoring
    => Support of extended schedule and multiple not started on time etc,.
    -  has no overview of the underlying technical systems health
    -  has no contextual navigation to the underlying system monitoring.
    -  Always require a BP solution to be orchestrated in Solution Manager to setup monitoring!

    What is Unified Job Monitoring?

    Over the last one year, we have been pondering on means to fix these known issues and develop an application that serves the customer requirements by closing the existing gaps. Starting SP10, we unveiled the new work center -> Unified Job Monitoring.
    • There is a consistent approach to monitor all type of jobs (BW process chains, ABAP jobs, SBOP jobs, SAP Data Services jobs). Also monitoring SAP CPS (REDWOOD) scheduled jobs.
    • Reporting of background jobs without requiring direct access to production systems using the collected metrics (BW analytics)
    • Powerful monitoring capabilities with factory calendar awareness, job log content, and Business process context so on


    We have developed a brand new monitoring UI keeping in the interest to transition to the new html5 technology (SAPUI5). Find below a glimpse of this monitoring UI.
    Key features
    In order to remove redundant collection in the managed system and to provide a persona-specific runtime view, we have ensured to unify the configuration, data persistency, collection and monitoring UI.

    Design Time:

    1. Reuse of Monitoring Objects from the three entry points - BP Monitoring solution, Technical Monitoring scenarios, Job Documentation.
    2. Pattern-based MO is supported for ABAP, BO, and DS. However, BW Process Chain has to be fully qualified name
    1. Intermittent grey alerts are avoided
    2. Multiple email notifications are overcome
    3. Support of BW reporting.

    When to use what?
    1. If a need for Overview Monitor exist:     Technical Monitoring - BI Monitoring. With certain workarounds for the known limitations.
    2. For a pure Business process context:    BP MON - BW Process chain monitoring
    3. For a harmonized approach towards monitoring, Starting SP12, please migrate to BPMON and MAI integrated Unified Job Monitoring.
    SAP would continue to invest only in this option. Overall, Unified Job Monitoring addresses the known limitations of BI Monitoring and integrates
    BP monitoring based process chain monitoring.
    However, there are still gaps owing to the time required to develop. We intend to bring the best of both worlds together in this Unified job monitoring.
    Starting SP12, you could migrate existing BPMON Solution to MAI based solution. This would ensure automatic usage of Unified job monitoring if there are jobs, Process chains available in the classical solutions.
    Details: Execute the migration report R_AGS_BPM_MIGRATE_SOLU_TO_MAI via SE38. Use the F4 help to identify your solution.

    Similarly, there exist also a means to migrate relevant objects of existing Business Intelligence Monitoring scenarios to Job Monitoring Scenario.
    Details: In transaction SE38: AC_JOBMON_MIGRATION. Migrate or copy from existing BI Monitoring scenarios, job type objects (BW Process Chains , SBOP jobs, DS jobs) to a new Job Monitoring scenario to utilize the new collection framework and monitoring UI
    In 7.1 SP12 , all the three monitoring work centers co-exist. A comparison chart of features between Technical Monitoring - BI Monitoring versus Unified Job Monitoring is as below.

    FeatureBI MonitoringUnified Job Monitoring
    ABAP Jobs and stepsNAX
    BW Process chains and stepsXX
    SAP Business Objects Jobs (SBOP)XX
    SAP Data services jobsXX
    External Scheduler (SAP CPS REDWOOD)NAX
    BW Bex Reports & TemplatesXNA
    MAI features
    • Notifications
    • Incidents
    • Alert Inbox
    • Third party
    Integration to MAI System Monitoring and contextual navigation to System MonitoringXPlanned
    Contextual Navigation to Managed system analysis tools from Monitoring UIXPlanned
    Overview monitor For viewing the overall scenario health of all landscape entities & JobsXPlanned
    (MAI) Work mode awareness
    Mass handling of monitored objects & thresholdsXPlanned
    Integration to Job DocumentationNAX
    Guided Procedure for Alert ResolutionXX
    Please write to me regarding:
    1. How is job monitoring done today?
    2. Which job scheduling tools are used in the landscape (embedded schedulers from managed systems, CPS, UC4, Solution Manager JSM)?
    3. What are the relevant/important job types?
    4. Is SAP Solution Manager-based Job/BI monitoring used?What is the feedback? Which functionality is missing?


    Regards, Raghav, S

    Development Manager, SAP Solution Manager

    How to configure and Trouble Shooting DBA COCKPIT Configuration in Manage System Setup Solution Manager 7.1

    In Managed System Setup - Step 4 (Enter System Parameters) highlighted below



    Please provide all the required Details for DB Parameters


    DB Host

    Service Name

    Port Number

    TNS Name


    And User Name will be your ABAP Schema User/ For Java (SAPSR3DB)



    Once provided all the required information then save. you will see that log message saying


    The DBA cockpit
    connection %_******** is OK. DB Extractors can be activated




    Once this step is completed we can activate the DB Extractors in Step 8 ( Configure Automatically) . We can check the successful connection entry in

    DBACOCKPIT T-Code. Below is the screen shot for your reference.




    Trouble Shooting Connection Error



    If DB cockpit connection cannot be established then you will get below message.





    We can see that Error cannot establish DBcockpit connection




    as we can see the same connection entry in DBCO T-code. Delete these existing entries



    And delete all the entries in DBACOCKPIT and MSS and check the in Operating System Level

    tnsnames.ora at both location it should be the same as per the managed system

    entries. If not then change the entries and check the tns ping.



    Then configure the DBACOCKPIT in MSS in the same way shown above. Once the DBA
    extractors are activated check the connection in T-Code DBACOCKPIT in SOLMAN


    DBACOCKPIT Connection in SOLMAN à connection should be
    successfully established.


    Thank You,


    The cross-system object lock functionality ensures that when an object is changed in a managed system, a lock entry is created for this object in the central SAP Solution Manager system. Depending on the selected conflict analysis scenario, this lock entry prevents changes being made to this object by any other change (transport request). This applies to all managed systems and clients for which the cross-system lock has been activated.

    Once the cross-system object lock has been activated, the system can detect conflicts between objects in transport requests that have the same production system or the same production client as their transport target.

    The meaning of the cross system object lock function is to protect your production system from “passing developments”.


    Inside a Change Request Management maintenance project all changes (Normal, Preliminary, Urgent and Defect) will consolidate with the project. As the import method is IMPORT_PROJECT_ALL “passing developments” inside a project can never happen.


    An exception to this is that Preliminary Changes & Urgent Changes can pass each other within a project. Therefore the use of CSOL is necessary to protect the PROD system from downgrades.


    Also if more than one project is available for the same system landscape, CSOL can protect the PROD system from downgrades.


    Automatic Categorization of Objects to retrofit (Auto Import, Retrofit and Manual) is based on the Cross System Object Lock entries in Solution Manager
    If the Enhanced Retrofit function does not detect a Cross System Object Lock entry for an object of a transport requests that should be retrofitted, the object will be flagged as Auto Import object.


    A change to object A is performed in the DEV system. This change is recorded in the CSOL table of Solution Manager. Now it happens that in the PRD system a fix is needed. The fix will be performed in the MAINT system and has to change object A as well. As the CSOL entry blocks the second change (fix) of object A the only solution to go on is to delete the CSOL entry as the fix is necessary to solve the issue in PRD.

    If now the transport request in MAINT is released and the retrofit categorization is calculated the retrofit will not detect an entry for object A and therefore calculate a green case.

    If now retrofit is performed the version of object A in the DEV system is overwritten!


    How can we avoid this behavior?


    You can customize how CSOL shall behave.



    You will find default mode and expert customizing.

    We will need to use the "expert" customizing as the default mode does not protect you 100% from the issue described above.

    csol cust.jpg

    The "Project Relation" customizing is key for the enhanced retrofit scenario. In default it's set to "cross" which means conflicts from different projects as well as conflicts within the same project will stop the process.

    What we want to avoid is exactly that conflicts from different projects will end in a termination of the process. Therefore the project relation has to be set to "Specific". This means that only conflicts within the same project will result in a termination and for different project will only appear as warning.

    The other settings do not influence the enhanced retrofit behavior, so Change type relation and object type can be set however you need. But it's necessary that the project relation is only set to "specific" in the case you have the enhanced retrofit scenario active in your landscape.

    One exception comes if you can for sure exclude Maintenance projects in the DEV landscape. In this case urgent changes cannot be created (this is only allowed when using maintenance projects) which means the default mode comes back into the play again.

    Also possible is the warning only setting which results in that all conflicts will ever be detected as warning only and the process is never terminated.

    In this case it's necessary to also activate the downgrade protection (DGP). This will ensure that if you get a warning in CSOL you can still not get passing developments as it checks again for release and every import.


    So with these allowed settings you will never need to delete an entry from the CSOL list because of Urgent Changes needing to be implemented to PRD as fast as possible. Also in any other conflict situation you will never need to delete entries from the CSOL list to go on with your process.

    Like this you will never get a wrong "green" retrofit categorization which will end up in an over write in DEV.



    When using enhanced retrofit in Solution manager the use of cross system object lock is mandatory for the correct behavior of the tool.
    You cannot use the enhanced retrofit without having CSOL setup and activated for the retrofit relevant projects.
    With some of the available conflict analysis customizing settings in cross system object lock  the danger of downgrading your Implementation work appears.

    When using the enhanced retrofit, you should only use project relation "specific" . Any “cross-project” setting is not allowed, because a terminating cross system object conflict would require the deletion of the corresponding lock entry. But that lock entry is required for the correct  analysis of the enhanced retrofit.



    When using the enhanced retrofit scenario make sure your CSOL customizing is set to "specific" from the project relation point of view.

    Also "warning only" is a valid setup if on top DGP is activated. The default mode can also be valid for the enhanced retrofit scenario when it's ensured that no Urgent changes can ever be created in the implementation landscape (DEV).


    The looping capability are planned to be shipped with SAP Solution Manager 7.1 SP13

    Alternatively you can implement following notes in advance:

    • 2088536 - Downport CBTA Default Components
    • 2088525 - IF and LOOP Default Components for CBTA
    • 2029868 - CBTA - Runtime Library - Fixes & improvements



    A test script may need to perform actions against an unknown number of entries in a table. The script may therefore need to:

    • Start at first row and check if there is an entry
    • If entry exists perform one or more actions on the current row
    • Continue with next row




    Keyword: DO

    It can be used to iterate over several steps. It defines where the loop starts.

    • It must be used together with the LOOP keyword which defines where the loop ends.
    • The EXIT_DO keyword must be used as well to determine when to stop the loop.


    The CounterName parameter provides the name of the iteration counter. This counter is incremented automatically at runtime while iterating over the included steps. The actual value of the counter can be retrieve using the regular token syntax.

    For instance, when CounterName is set to "COUNTER" its value can be reused in the subsequent steps using %COUNTER% (or $COUNTER$ for specific situations where the percent character is ambiguous).


    If you plan to use nested loops please make sure to declare a different counter names.


    Component Parameters


    CounterName: Specifies the the name of the iteration counter.


    Keyword: EXIT DO

    It must be used within a loop that has been defined using the DO and the LOOP keywords. The EXIT_DO keyword interrupts the loop as soon as the condition is met.

    A typical use case is to check the value of iteration counter that has been declared via the CounterName parameter of the DO keyword.

    For instance, when CounterName is set to "COUNTER" its value can be checked using the %COUNTER% token.


    Component Parameters


    • Specifies the value of the left operand that is to be checked.


    • Specifies the boolean operator to use.

    The operators supported are the ones below:

      • = for "Equal to"
      • < for "Less than"
      • > for "Greater than"
      • <= for "Less than or equal to"
      • >= for "Greater than or equal to"
      • <> for "Not equal to"
      • {contains} for "Contains"
      • {startsWith} for "Starts with"
      • {endsWith} for "Ends with"

    An additional operator is supported when testing WEB applications (i.e.: applications running in the browser):

      • {matches} for checking whether the value matches a regular expression. The regular expressions are expressed using the .NET syntax.


    • Specifies the value of the right operand that is to be compared with the left operand.



    The options parameter lets you perform some adaptations or conversions of both the left and right operand before comparing them.

    The supported options are:

    • /u (for uppercase) - Both values are converted to upper-case before being compared
    • /t (for trimmed) - Both values are trimmed before being compared
    • /i (integer) - Both values are converted to an integer before being compared
    • /f (float) - Both values are converted to a float (or double) before being compared
    • /b (bool) - Both values are converted to a Boolean before being compared


    Keyword: LOOP

    It defines the end of the loop and must be used together with the DO keyword which defines where the loop starts.




    The following scripts was created for transaction VA02 (Change Sales Order) to add shipping information for each line item of an existing sales order.



    With DO Keyword the loop starts and the counter is set to ‘1’.


    To be able address the row number starting at ‘0’ we take the counter number minus ‘1’ using the CBTA_A_SETINEXECUTIONCTXT component.


    Then the scripts reads the value of the first row in the first column to check if an entry exists.



    If the value is empty we exit the loop with the EXIT_DO keyword.


    Otherwise the scripts performs the required actions for the current row

    • Select row


    • Menu Goto --> Item --> Shipping
    • Enter the required shipping information using the related screen component
    • Go back to main screen

    With the LOOP keyword the script goes back to the DO keyword while increasing the counter and processing further line items of that sales order.

    Mateus Pedroso

    MOPZ Framework 3.0

    Posted by Mateus Pedroso Nov 28, 2014

    Dear followers


    My name is Mateus Pedroso from MOPZ/LMDB/Solman Configuration team and I'll start to write some posts about these topics. I would like to start writing about MOPZ framework 3.0.


    MOPZ Framework 3.0 is the standard for Solution Manager 7.1 SP12, but you can apply note 1940845 to enable MOPZ 3.0 in Solution Manager 7.1 SP05-SP11. Note 1940845 must be always implemented in the latest version and this note fix some bugs in mopz 3.0, so it's very important to ensure that the latest version of note 1940845 is implemented even in Solman 7.1 SP12. The following points changed in MOPZ 3.0.


    - UI and performance.

    - Integration of the Maintenance Optimizer with the Landscape Planner.

    - Add-on installation procedure.


    You can check more details about MOPZ 3.0 in the pdf attached in note 1940845.


    One of the most important improvements is the Add-on installation. Here's a screenshot showing that now you can apply add-ons in step 2.



    Now it's easier to apply add-ons.


    In the next posts, I'll explain some LMDB/SLD topics related with MOPZ and how to fix some well known issues.

    Part 1 is Solution Manager 7.2 Roadmap Webcast Summary Part 1


    The usual legal disclaimer applies that things in the future are subject to change.


    Cloud Adoption


    Figure 1: Source: SAP


    When systems are on a Private Cloud such SAP HEC there is no real difference for SolMan


    For a Public Cloud – such as SuccessFactors, Ariba , the plan is to allow SolMan to provide services for public


    LMDB  will have new interface


    Figure 2: Source: SAP


    Public cloud performance monitoring  will be in Solman and will be in 7.2


    It is also included on SolMan 7.1 SP12


    Figure 3: Source: SAP


    Figure 3 shows how to register cloud service with a guided procedure


    Figure 4: Source: SAP


    Figure 4 shows interface and connection monitoring that is “In the pipeline”


    Solution Manager with In Memory Technology


    Figure 5: Source: SAP


    All customers who have a valid support contract can use Solman on HANA without additional licenses


    This will come with transition support, standards, and more


    Figure 6: Source: SAP


    Figure 6 is not part of 7.2 but a strategic message for the future


    SolMan will have a “Fiori like experience”


    Notice too that the reports will come from HANA Live, not BI/BW


    Figure 7: Source: SAP


    Install, register, do an upgrade will be improved with maintenance planner shown in Figure 7


    Figure 8: Source: SAP


    Figure 8 shows there is a ramp-up for maintenance planner today


    SAP is looking for ramp-up customers


    Maintenance optimizer will be gone in 7.2


    Figure 9: Source: SAP


    Figure 9 shows there is no new CRM release in 7.2; only an enhancement package


    Figure 10: Source: SAP


    SOLAR01 02 are going away


    Figure 11: Source: SAP


    Figure 11, was already previously announced


    Question & Answer

    Q: Java stack for SolMan – 7.1 – some functionality is removed from Java stack – going forward could we have Solman without the Java stack

    A: 7.2 will not be possible and Java is still required


    Q: Business process design – 7.1 – Advanced Business Process Blueprinting – how will it work in 7.2?

    A: First customer came back with feedback with lots of feedback and checked architecture and decided to rethink process modeling which is why coming out of new environment


    Advanced blueprint will not work on 7.2; only a few customers are using it


    Q: What is the planned support for current 3rd Party Tools: HPQC, Redwood CPS, Wily, Productivity Pak?

    A: Will continue to support interfaces in 7.1; will not have interface support during ramp-up – there are changes coming  - architecture is changing, want it stable before offer interfaces


    Q: What happens if upgrade from 7.1 to 7.2 and have open projects with transports?

    A: Current feedback – will have to close project; they are revisiting with development organization – customers are unhappy – customers want to continue to work after the upgrade


    Q: Will a planner Excel sheet be available, allow them to find risk and timelines?

    A: Not at this point but plan to offer the system – need to upgrade and see what the situation is



    Hopefully we'll learn more details at SAP Insider's Basis  SAP Administration 2015

    The official roadmap is at (SMP logon is required)


    The usual disclaimer applies that things in the future are subject to change.


    Matthias Melich, SAP, provided this webcast


    Current release is 7.1 with maintenance commitment to 2017


    Solution Manager 7.2 will into ramp-up middle of next year; by Q4 2015 SAP expects to be  GA


    Then if you are on Solution Manager 7.1 you have 2 years to transition


    Figure 1: Source: SAP


    In the past there have only done a few investments in implementation.  The next release will see a big investment – “pragmatic business process management” – most of this presentation is on this topic


    Most customers have large on-premise


    SAP is actively driving cloud


    Lifecycle shown in Figure 1 means most of customers will be in a hybrid situation to support on-premise and cloud solutions and integrated


    SAP wants customers to use SolMan for hybrid environment


    There is a difference: Solution Manager for HANA and on HANA


    Solman 7.2 will be available on SAP HANA


    SolMan 7.1 is IT and less for business


    SolMan 7.2 is a more business balanced SolMan


    Figure 2: Source: SAP


    Figure 2 on the left in Development system – planned, Solution Manager 7.2 will provide “state of the art” process modeling


    Picture shows what is typical in modeling environments


    PowerDesigner , which SAP acquired during Sybase acquisition, is being used


    Today – 7.1 need a landscape to enter business process steps; business process experts can’t use


    SAP wants to decouple this


    Use 7.2 early in project and hand over to business process experts, wants to make it easier to use for documentation for business processes


    SAP wants to extend diagnostic and analytics framework in Solman for managing business case


    SAP wants to extend framework to innovations area of SolMan  - relate business case to KPI’s


    SAP is investing in pre-configured solutions – have RDS’s (rapid deployment solutions)


    Figure 3: Source: SAP


    Figure 3 shows processes will have more than 3 levels


    Figure 3 shows a screen shot,  non-graphical view of Solman


    SAP wants openness to other modeling tools


    SAP will have a marketplace on SCN; will allow vendors to certify interface similar to Service Desk, with a bi-directional interface


    This will be for business process – not full-blown UML ; for full-blown look at PowerDesigner


    SAP hopes to have interface added by then; but will not be part of the ramp-up scope


    Figure 4: Source: SAP


    SAP will do away with some of the restrictions today


    Figure 4 shows a technical object library – transactions, reports, all objects in system only once – e.g. VA01 only once


    SAP will structure this library according to application component hierarchy


    Library is based on usage – object only goes to Technical Objects Library (TOL) if used


    It will generate this library automatically


    Process Step Library or PSL is based on usage – using application component hierarchy as a reference.  The PSL is the home for documents, test cases – can have multiple occurrences of technical objects – PSL is available per system. It is generated automatically; built on top of TOL


    E2E documents business processes across systems – business process library – can’t build automatically – this is optional – pull steps from individual systems


    Figure 5: Source: SAP


    Figure 5 shows several paths


    If customer has no solution documentation today, then the libraries are generated and build up to end to end


    If have solution documentation today, all documentation is in read-only after upgrade, customers migrate projects to new environment – not automated fashion


    Figure 6: Source: SAP


    Figure 6 shows the link to business case; once technical implementation is done, look at how implementation is by usage of systems – business view in pink

    IT view – requirements, test, change, application usage verification


    Part 2 of my notes is coming; focusing on the Cloud, HANA, future direction and question & answer



    Hopefully we'll learn more details at SAP Insider's Basis  SAP Administration 2015

    As part of my blog series on SAP Solution Manager 7.1 features and functions, I decided to write this blog post to give a high level overview of the steps needed to set up Business Process Monitoring in SAP Solution Manager 7.1 (used SP12 here). It’s not my intention to detail everything out in this blog post but instead give a view on which high level steps are needed in terms of configuration.


    For a detailed setup overview, check out the great presentation (BPM setup roadmap 81 pages) that you can find in the media library on or through the presentation material on business process operation - business process monitoring in


    In a previous blog post on getting started with SAP Solution Manager I explained briefly the initial steps to get started with SAP Solution Manager. For Business Process documentation, as a prerequisite, you have performed the system preparation, basic configuration for SAP Solution Manager and the managed SAP system setup for the SAP systems involved in the monitoring scenario.


    Quick configuration steps cheat chart


    First step: preparation for the Business Process Monitoring scenario through SAP Solution Manager: Configuration workcenter


    You start with the guided procedure for Business Process Monitoring  which you can access via the menu in the Solution Manager Configuration workcenter (or transaction SOLMAN_SETUP which is the same in the end).



    This guided procedure will help you to get the prerequisites in place to set up a Business Process Monitoring scenario.


    Prerequisite notes are checked for example during this guided procedure (via RTCCTOOL) and the detail log (link show) will show you what is missing in terms of SAP notes to ensure you have the latest corrections implemented.


    Prerequisite before setting up a business process monitoring scenario

    You need business process documentation in a solution within SAP Solution Manager (a structure that represents the business processes & business process steps) in order to do business process monitoring.


    There are multiple ways you can achieve this but I won’t cover them all in this blog because it would take this blog too far off topic. If you already utilize business process documentation, you can leverage what you have already build. Otherwise, if you want to set up a simple Business Process Monitoring scenario (let’s call it a test) it doesn’t have to take a lot of time to get started.

    You can create a Solution Manager implementation project using transaction SOLAR_PROJECT_ADMIN.  The minimal configuration there is that you give the project a title, you choose the language and you insert the logical components in the system landscape tab which represent the involved SAP systems for the business process steps.



    Once that is done, you can create a business process structure using transaction SOLAR01. Once your structure is ready (just keep it simple to start) you need to insert the structure into a solution. That’s done using transaction SOLMAN_DIRECTORY. If you don’t yet have a solution, you also need to create a solution, this can be via the SAP Solution Manager Administration workcenter.


    Setting up the business process monitoring scenario


    In the business process monitoring setup, you continue the setup (follow the steps, hit create and follow through the configuration) and you can configure business process monitoring against business process steps.


    After you run through the configuration steps, you can see the monitoring overview in the Business Process Operations (new) workcenter under Business Process Monitoring. Recently introduced is integration into the Monitoring and Alerting Infrastructure (MAI) which makes the technical architecture and the look & feel of the scenario, the same as for Technical Monitoring.




    As you might know Business Process Analytics was first introduced in 2010 with SAP Solution Manager 7.0 support package 23. A lot has happened since then, e.g. Business Process Analytics went mobile on the iPad. An overview about all features and the evolution of key figure content can be found in our central Business Process Analytics document. But something is not yet widely known - Business Process Analytics can also be used in an ad-hoc and real time manner. This additional feature is already available since SAP Solution Manager 7.1 support package 10 and it works no matter whether your managed system is running on SAP HANA or "anyDB". The name of our Web Dynpro application implies that it is only working for SAP HANA, but this is not correct.


    Technical prerequisites

    You require SAP Solution Manager 7.1 with support package 10 or higher.


    Your managed system should have ST-A/PI 01Q with support package 2 or later implemented. Additionally you should implement SAP note 2085063 - Business Process Analytics powered by SAP HANA related collector returns result list in wrong format



    Additionally required configuration


    In order to get the ad-hoc/real time Business Process Analytics working you have to create a new connector instance for the BPM_HANA_SUITE connector in the Data Source Manager.

    Dat source manager.png

    As the new Web Dynpro application is not integrated in the Business Process Operations work center, you should create your own favorite in order to directly access the application.




    Using Business Process Analytics powered by SAP HANA


    After creating the favorite, you can just click on the hyperlink and can access the selection screen from Business Process Analytics powered by SAP HANA. It looks very similar to the "traditional" Business Process Analytics. The main difference is that you do not have to select a solution. You just chose a system and client combination and then you have to filter for the key figure of interest (out of the 900+ available ones).


    Selection screen.png


    When selecting and executing one key figure the data collection is immediately triggered in the connected managed system and as soon as the data collection is finished, you get the Business Process Analytics analysis screen. SO compared to the "traditional" Business Process Analytics no setup and scheduling of key figures is required.



    Also the analysis screen is very similar to the "traditional" Business Process Analytics, but "only" the Advanced Benchmarking and the Age Analysis are available as "Analysis Types". No Benchmarking or Trend Analysis is provided as these features require some InfoCube access, which is not available per definition as we perform some ad-hoc, real time execution.


    The Detail Analysis is of course available in order to jump into the corresponding result list and accessing every single document if required.


    Further reading

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


    Frequently Asked Questions about Business Process Monitoring and Business Process Analytics are answered under and respectively. The following blogs (in chronological order) provide further details about Business Process Analytics and Business Process Monitoring functionalities within the SAP Solution Manager.


    Using business process documentation in SAP Solution Manager? Then you definitely want to know about the Solution Documentation Assistant (codenamed SODOCA). SODOCA allows you to verify your business process documentation structure. Are those SAP processes that we have documented really in use and perhaps an even more interesting question, did we miss something? Did we forget to document something?

    Are the processes we claim are in use, in use?


    The first thing you see when you open up a SODOCA analysis result is the business process structure and the checks that have been performed which are represented by traffic lights.

    A green light means:

    The process is in use in the SAP system (during the period that was analyzed)

    A yellow light means:

    One of the underlying processes of this business process is not in use in the SAP system (during the period that was analyzed)

    A red light means:

    The process was not used in the SAP system (during the period that was analyzed).

    Based on this result, the business process documentation can be adjusted. It’s not because a process (or step) is red that you have to remove it. It’s just an indication that it was not in use during the period you analyzed and then you should ask yourself the question, why is that the case?

    It can be related to the period analyzed (some processes are only performed once a year for example). To overcome that, you could analyze a period of a year as well for example.

    Another reason might be that you think they are using this transaction but in reality they are using another transaction (or report or Z ...) that allows them to do the same thing.

    Did we forget something in our business process documentation?


    In the result, under the tab Object Usage, you can find a tab Not in Analysis (given you selected these options when you set up the analysis).

    Here, you can find an overview of transactions (and other object types when selected) which are reported to be in use in the SAP system but not present in the business process documentation structure. So this is interesting in terms of checking whether or not you didn’t miss anything. It can of course also be the case that a new process has been put in place but the business process documentation was not updated.

    A repetitive cycle


    During SAP TechED && Dcode Berlin, attendees (yes, more than once) asked me how do I get started with SAP Solution Manager. What is the best practice?


    Since SAP Solution Manager 7.1 has a huge set of scenario's and applications which can be leveraged by the customer it can be a tricky question once you pass the initial configuration to get started.

    SAP Solution Manager contains a mixture of multiple products, it has a full CRM, an embedded BI (unless you opt out and use a separate BI system), a Solution Manager specific part and it runs on SAP Netweaver technology.

    Since I like to share knowledge and since I got this question more than once, I decided to start writing this blog post to help people get a better understanding. Since it's such a  broad  topic to cover, I won't be able to pull this off in a single blog post so if this blog is valued and found interesting, I can continue and blog more to end up with a series of blog posts to help community members figure out how all of this fits together.


    1) Installation


    Where it starts is, you install SAP Solution Manager 7.1. As a SAP customer, you can simply download the appropriate files and get started. Of course it's not too simple in real life so you'll need a SAP Basis admin who takes care of it. An installation typically includes a database, an application server, a host agent, a diagnostics agent, Wily Introscope and depending on the size of the landscape more. The SAP Basis admin also takes care of BC specific post processing for the Netweaver technology stack, such as the SAP Transport Management System configuration just to give a small example.

    A SAP Solution Manager landscape typically consists of two or more SAP Solution Manager systems. Some customers (small - midsize) only have one SAP Solution Manager system. In that  case, you would want to clone that system to test support package stack updates / upgrades on a clone of that system to avoid unplanned downtime if something would go wrong. If you plan to actively use SAP Solution Manager and use multiple scenario's over time, I would advise going for at least two SAP Solution Manager's to make it easier to test changes on your landscape. If you want to seriously invest in the IT Service Management scenario's (all the management modules) it can even make sense to go for a three tier landscape to have a better change management control if you're working with custom flows.


    2) System preparation and basic configuration


    picture 1.0: part of SOLMAN_SETUP left menu pane


    Once that is done, you have SAP Solution Manager up and running. Th next thing is the system preparation and basic configuration of Solution Manager which is performed through either transaction solman_setup or through the Solution Manager configuration workcenter. For this you'll need either a SAP Basis admin with knowledge on SAP Solution Manager or a SAP Solution Manager consultant with a technical background (preferably) since many steps are related to technical actions such as connectivity, data replication, BI content activation and so on.


    3) Managed system setup


    picture 1.1: part of SOLMAN_SETUP left menu pane + managed system setup right pane


    Next is the managed system setup (see picture 1.1, note that I blanked out actual system / host names) which lets you configure the SAP systems connected to SAP Solution Manager. In order for SAP systems to be known in SAP Solution Manager, they have to be known in the System Landscape Directory (SLD) connected to SAP Solution Manager and synchronized into the Landscape Management Database (LMDB). Another technical story in which you want maximal automation to avoid isses.


    Already in the early phases, the customer can choose to leave out certain elements depending on the use-case of their SAP Solution Manager implementation. There are customers who have two or more SAP Solution Manager landscapes which are used for different scenario's. For example, one landscape for Technical Monitoring and one landscape for IT Service Management (Change Request Management etc). For Technical Monitoring, you need diagnostic agents, for IT Service Management, you don't. This can result in a SAP Solution Manager system where the managed system setup has red traffic lights. So depending on the use case, it can be ignored. The reason for those separate landscapes (mostly seen at large customers) is that they want to update one landscape more frequently than the other and therefor split the use-cases over multiple SAP Solution Manager landscapes.


    4) The gates are open


    picture 1.2: SOLMAN_SETUP left menu pane

    As of this point, the gates to a large amount of scenario's open up. Depending on the scenario you want to set up, prerequisites exist. I won't list all possible scenario's and prerequisites here because that would just be too much. Steps 1,2 and 3 is what we called the "Technical Base" during an implementation project a few years back.

    Confusion rises - some scenario's / features are "just" available right now

    Here is where it can start to get complicated to understand where to go next or what to do next. A number of scenario's will just work without further action (except for bug fix notes perhaps) after steps 1,2 and 3. Some scenario's will be up and running but might have missing data for example. This is because from a technical point of view, the configuration can get rather complex. Due to the amount of prerequisites (thinking about Root Cause Analysis now for example), chances are pretty high, not every prerequisite was met during installation, post processing and that you'll need additional work to make every single feature work properly. Root Cause Analyis is one example which you don't see in the solman_setup menu tree because it should already be functioning after performing steps 1,2 and 3. Experience tells me it won't be correct and you'll need to take action to make it work properly.

    As from step 4 you need to think about functional prerequisites as well, for plenty of scenario's, you need business process documentation for example. Business process documentation is a next logical step in advancing the use of SAP Solution Manager if you want to leverage scenario's such as Business Process Change Analyzer, Test Scope Optimization and Scope and Effort Analyzer for example. Again, business process documentation is not part of this menu tree because that should also work after steps 1,2 and 3 you can just go and use the scenario but you do have to know how to get started within that scenario of course. I'll try to cover some of those aspects in upcoming blog posts.

    Implementing scenario's that require more work


    picture 1.3: guided procedure to configure scenario Change Request Management

    Many scenario's (visible on picture 1.2) offer guided procedures which can guide you to configure that specific scenario. If you want to go and configure Change Request Management for example, this would be the next step.

    Expert Guided Implementation

    SAP also offers options to help customers out to implement SAP Solution Manager scenario's. You can check out the expert guided implementation initiative of SAP over at

    I haven't yet used this service because I spent a lot of time in SAP Solution Manager but I have heard from customers who haven't got the time to build up that kind of experience in SAP Solution Manager that this service can be very useful to help them get started. The idea is that an expert from SAP helps you through the configuration for the scenario and with multiple calls, follows up on progress and helps you further to use the scenario.

    SAP Enterprise Support Value Maps

    Another recently introduced intiative of SAP are Value Maps | SAP Support Portal . The idea behind these are providing guidance to which resources (can be Expert Guided Implementation - EGI or something else) the customers can leverage to help set up a specific scenario.

    General advice

    For any scenario which you want to use, it's advised to go and look at relevant SAP notes to ensure you have the necessary prerequisites in place. Sometimes, the guided procedure in SOLMAN_SETUP (if available for the scenario you look at) will automatically check and report on the needed SAP notes which might be required on either your SAP Solution Manager system or Managed SAP system or both. As I've mentioned before, not all scenario's are in here so for some you'll need to check the relevant SAP notes yourself and check if your system is ready, meets those prerequisites to ensure the scenario will work properly.

    SAP Solution Manager is not that "simple" in most cases once you step outside the "we only use SAP Solution Manager to download files" realm of things. So it can definitely make sense to go for EGI or hire someone with SAP Solution Manager knowledge to aid you in your efforts. Figuring out complex scenario's yourself can take a lot of time.

    As of SAP Solution Manager 7.1 the CRM Web UI is the standard access to ITSM and ChaRM.

    The Web Client User Interface is the first step into a new era of user interfaces regarding usability and flexibility for the business user.




    Predefined business roles are the entry point into the application from an end user point of view.

    SAP delivers the following business roles to be used for ITSM and ChaRM:

    • SOLMANREQU for Reporter / End User / Key User
    • SOLMANDSPTCH  for Dispatcher
    • SOLMANPRO for Processor and Administrator


    Favorites and Tags are very good functionalities that can help the end user in the daily work.

    By using the following buttons, the user can save the current ITSM/ChaRM document as favorite or create a tag could to identify the documents related to the same topic.



    In this way, it is easy to access the documents later because the favorites and tags are visible in the home screen.



    However, in the above business roles the favorites and tags are not enabled by default.

    If the end users want to use it, they need to go to the following:

    1. Go to the Personilize menu
    2. Go to the assignment block Settings
    3. Enable the Favorites and Tags


    From my point of view, it should be better to have it enabled by default, so the end users will be able o use it without doing any personalization.

    In order to make the favorites and tags enabled by default in the business role, follow the step by step bellow:

    1. Go to the following IMG path:
      SAP Solution Manager Implementation Guide -> Customer Relationship Management -> UI Framework -> Technical Role Definition -> Define Parameters
    2. Copy the standard parameter profiles into a custom namespace
    3. Create new entries for the following parameters and Save
    4. Go the business role definition:
      SAP Solution Manager Implementation Guide -> Customer Relationship Management -> UI Framework -> Define Business Role
    5. Select the business role and go to Assign Function Profiles
    6. Replace the Function Profile ID PARAMETERS with the new parameter profile that you have created


    After that, all users assigned this business role will be able to see the favorites and tag button while processing the ITSM/ChaRM documents.



    After working on SAP Solution Manager during more than 2 years I would like to share with you our experience. Your feedback as “Solmaner” or SAP Solution Manager customer is more than welcome to help us improving our service!

    Our approach is based on the “no big bang” principle. Thus we built our SAP Solution Manager platform gradually, step by step.

    We first rebuilt the technical foundation when migrating from the version 7.0 to 7.1. After the technical foundation was laid out, we focused on getting the functional foundation (business process documentation) ready to be able to offer more extensive services.




    After the initial project, we proposed to our customers over time, the following services based on SAP Solution Manager  functionalities:


    • Technical Monitoring
      •   In general (interface enabled)
      • Specific scenario for Java performance (interfaced)


    • Incident Management
      • Incident creation from within SAP (interfaced)
      • Automated incident creation based on monitoring (interfaced



    • Custom Development Management Cockpit (CDMC)


    • Business Process Documentation


      • Solution Documentation Assistant
      • Business Process Change Analyzer/Test Scope Optimization


    • Change and Release Management (CHARM) (interfaced)


    Technical Monitoring

    The technical monitoring service gives you a lot of information about your SAP system health on regular basis via the EWA & SLRs reports and more. Other functionalities like Root cause analysis or DVM (Data Volume Management) give you also a good insight of your SAP systems status. I qualify it as the easiest service to promote as we didn’t have to do much to convince our customers about the added value it brings. It indeed increases the quality of the systems by alerting potential technical bottlenecks (security performance) and inefficiencies (performance, actual software levels) in an early stage.



    Incident Management

    Regarding the SAP Solution Manager incident management functionality we only use a part of it in the sense that the support messages are created from SAP satellite systems but registered automatically in a separate service management tool thanks to SAP Solution Manager. Our customers who requested this service deal with applications based only on SAP technology. We have another customer using our technical monitoring service but he doesn’t want  to use this service as he has different applications based on different technologies: SAP, JAVA, . Net etc.



    Custom Development Management Cockpit (CDMC)

    CDMC helps to manage and optimize the usage of custom development objects on the SAP ABAP stack.We used CDMC only twice in 2 years time during upgrades. Each time the analysis listed thousands of objects to go through to decide whether you remove them or you keep them: this is really time consuming. Besides our customer don’t find it user friendly. Thus we have to find a way to improve this service to have more customers using it.



    Business Process Documentation

    We spent most of our time developing our Business Process Documentation service. What we call Business Process Documentation in our service portfolio is a set of SAP Solution manger functionalities and concepts:

    • SODOCA
    • BPCA
    • TBOM
    • CBTA


    I like to use these acronyms; it makes me look like a technical specialist while as Service Delivery Manager I rely on the technical consultants and SAP mentor of my team to set up the scenarios. Nevertheless I can give you the high level principles behind these acronyms:


    • SODOCA: SOlution DOCument Assistant it checks whether the business process structure you define is correct by identifying the omitted or the unused transactions.


    • BPCA: the Business Process Change Analyzer allows you to check the impact of your changes on the documented business processes. Then the Test Scope Optimization permits you to identify the most impacted businesses on which you should focus your tests. Later on we will use this functionality in combination with CHARM (ChAnge and Release Management).



    • TBOM: Technical Bills Of Material. TBOM’s (Technical Bills Of Material) are used by other functionality in SAP Solution Manager such as BPCA (Business Process Change Analyzer). The generation of TBOM’s is part of business process documentation.



    • CBTA : Component-Based Test Automation: record and play back test scripts approach without additional licenses fees.


    We succeed to have a recurrent scenario on monthly release:

    • Identify the most impacted business processes by the changes (transport requests) with BPCA
    • Identify the business processes to test to cover 100% of test coverage with Test Scope Optimization


    In the coming months we would like to use CBTA to execute the test scenarios related to the identified business processed via BPCA/Test Scope Optimization scenario. In this way we will be able to propose an end to end change process.We would like also to use CBTA to generate automatically the TBOMs (Technical Bills Of Material) to review our business process structure.


    ChAnge and Release Management (CHARM)

    We set up recently CHARM service but it not yet used in production. A SAP Solution Manager consultant was surprised that we didn’t start with CHARM implementation. In an IT organization where there are already standards defined you have to give solid arguments to introduce another tool that has the same functionalities than the existing tools. The real added value of CHARM that we highlight is the transport management for SAP changes. Indeed SAP changes are managed in one service management tool but the release managers use additional excel files to manage the SAP transport requests. With CHARM the end to end change management process is supported by one tool with the possibilities of using transport of copies . Like for the incident management part the only customers willing to use CHARM are the ones who deal with applications based only on SAP technology. I am wondering is there any company using CHARM to follow their non-SAP changes: if a reader is in this case I am eager to listen or read his/her story.



    To conclude I believe that the real added value that SAP Solution Manager can bring to SAP operations is not sufficiently known. The fact that you have to implement a lot of OSS notes (at least in our case) to have one scenario working properly doesn’t encourage a wider usage of the SAP Solution Manager functionalities.


    From the exchanges I have so far with people using SAP Solution Manager they use mostly CHARM and Project Management functionalities. I haven’t met anybody using BPCA/Test Scope Optimization or SODOCA and I met only one team who started using CBTA.



    I am also wondering what is the real priority that SAP is giving to SAP Solution manager improvement now and for the coming years. This improvement can be done via a better communication about SAP Solution Manager capacities that are really underestimated.



    Unfortunately, they are still lots of people out there with preconceived ideas about SAP Solution Manager based on the earlier releases of Solution  Manager (pre 7.1).People have to be aware that there is a huge gap between the version 7.0 and 7.1 and I hope with the version 7.2 planned  for the beginning of 2016 there will be more customers using SAP Solution Manager for the continuous improvement of their IT operations.


    I am attending the SAP TECHED in Berlin November 11th-13th I hope meet out there a lot of solmaners:




    EXP17550Sharing an SAP Solution Manager 7.1 Implementation ExperienceNetworking Session (30min)   Thu 2014/11/1314:30 - 15:00Expert Lounge EL 2.1, Hall 2.2


    I can’t finalize this article without paying tribute to SAP passionate Tom Cenens who is also a SAP mentor. In a team all team players are important as each of them brings his added value. We are all convinced that Tom is part of those people who motivate and help people to grow by sharing their passion and knowledge with respect and humility.

    In this blog we will show how to maintain your Business Process Structure of your Implementation project with the ARIS tool ( supported via a Template project in Solution Manager) This blog will only cover the ARIS part related to the Business Process projects preparation. The part related to Solution Manager Template Projects will be covered in Boris Milosevic’s blog.


    Background: A template project is maintained in the SAP system (client) where you can make changes. For more information on this please refer to Boris Milosevic’s blog How To Set Up Project Environment in Order to Maintain your Implementation Project with ARIS tool.


    The environments in the two tools SAP Solution Manager and ARIS are synchronized and the ARIS content represents Business’ view of the Business Processes and the Solution Manager represents the system view of the Business Processes of the enterprise.


    The schema below shows the different steps to follow when creating a new project to improve a given Business Process area:

    Microsoft PowerPoint.png

    When synchronizing between ARIS and Solution manager there are object attributes in the ARIS objects that define how the synchronization should be done. By following the steps above and by using the Transform functionality in ARIS the new [Variant] copy of the Business Process area to be updated is redirected to synchronize with the Implementation Project in Solution Manager instead of the Solution Template Project.

    In the end of the step-by-step process I explain a short workaround needed because of a Transform bug in many versions of ARIS. We’re using Version, which needs the workaround.

    1. To start the update you synchronize the two “Master” environments.

    VMware Fusion.png

    • Select the Solution Template in SAP Solution Manager.
    • Accept the default settings and selections.


    The ARIS Master and the Solution Manager Master Template are now synchronized and contain matching business context.

    Microsoft PowerPoint.png

    2. Copy the ARIS Master Group (Project) and Paste it as a Variant in the [Parent] Group Node.

    Microsoft PowerPoint.png

    The new structure is visible in ARIS – this will be our Implementation project.

    Microsoft PowerPoint.png

    Now you need to take a look at Boris Milosevic’s blog How To Set Up Project Environment in Order to Maintain your Implementation Project with ARIS tool to find out what needs to be done in Solution Manager.


    4. In ARIS create a New, Temporary ARIS Database (TMP)

    VMware Fusion.png

    This database will be Transferred (ARIS functionality) from the Implementation Project in Solution Manager and is only used to Transform the SAP attributes of the objects in the ARIS Variant Project copy to allow it to later be synchronized with the Implementation Project in Solution Manager.


    5. Transfer Implementation Project from Solution Manager  to ARIS TMP database


    Verify the Implementation Project Structure in the TMP db.

    Check Warnings at end of this blog, and make adjustments if necessary.

    In the Variant MASTER Database, Select the Copied Variant Structure and

    6.Transform from the [Template] Project in the TMP Database.


    This step is necessary to properly set the SAP Attributes in the ARIS Variant Master Project [to “Point” to the Implementation Project in Solution Manager]


    Select the TMP Database as the Corresponding Database Containing the Implementation

    Project and OK

    Microsoft PowerPoint.png

    7. Work in the Variant Master make all changes required by the business and the organization. Assign, Publish and Validate Models with Process Owner.

    8. Synchronize the ARIS Master (Variant Copy) Project back to the Implementation Project in Solution Manager. Select the Variant’s root-object in ARIS.

    [Read the Warnings slide at the end of this blog before proceeding.]


    The Project is Now Approved and Ready to be Published in ARIS.

    Make sure Model Level Assignments are Assigned to the New Processes in

    the Variant Copy Master. Delete the Original Master Processes.




    There is a known bug with certain versions of ARIS. When creating a variant copy

    of TMPL, the root object is also copied.

    However the Transform function does not change the SAP ID or Project ID when

    Transforming the project from the TMP Database. A manual action is required.


    The Variant copy has been created and before Transforming the SAP Attributes from the TMP ARIS Database You need to Export (XML Export) the Root-object from the TMP Database and Import it into the MASTER Variant, then Consolidate the Variant copy and the imported object, using the imported object as the Master.

    After the Consolidation check the SAP Attributes of the Variant Root-object. Make sure the [SAP] Synchronization Project Attribute is the Implementation Project in Solution Manager.

    After this You can Perform the Synchronization with Solution Manager.


    Filter Blog

    By author:
    By date:
    By tag: