This document might not provide help for all contingencies, for example, various individual systems as well as project configurations. Therefore, Software AG strongly recommends requesting Global Consulting Services for migrating existing ARIS projects to be further used with SAP® Solution Manager 7.2. You may order that service from your Software AG sales representative.
This procedure explains how to migrate existing SAP projects stored in your ARIS databases using several reports. The reports are managed in the SAP migration (Solution Manager 7.1 to 7.2) report category. After you have migrated your SAP system, all former projects will be available as solutions using the new structure of SAP Solution Manager 7.2. The migration is done in several steps. For each action, detailed information will be written into the report output files. The synchronization process will be logged as well.
Warning
If you have updated SAP® Solution Manager 7.1 to SAP® Solution Manager 7.2, it is absolutely essential not to change any content in the new SAP system until you have migrated the projects in ARIS. Migration is available only for projects that were migrated to a business process structure in SAP.
Procedure
If you are not about to create a new solution configuration for productive use, you can modify the settings for future needs after the migration has completed.
When completed, you have two databases. One holds the old 7.1 project and the other holds the SAP® Solution Manager 7.2 solution's branch already migrated in the SAP system. In the 7.2 solution the key for the SAP ID of the 7.1 project is maintained as Source ID attribute.
When running the report you first have to select the database containing the downloaded SAP Solution Manager 7.2 branch, and you need to connect to the SAP system holding your SAP Solution Manager 7.1 project.
This report copies all root functions of the Folder function type from the SAP Solution Manager 7.2 branch structure to the SAP Solution Manager 7.1 project structure. The model linked to the SAP Solution Manager 7.2-based solution root contains two folders, namely Process Step Library and Business Processes. Both folders are required for SAP synchronization.
When executed, the root level structure in both the project as well as the solution's branch is identical. The 7.1 project root has assigned a model of the project model type, containing the Process Step Library function of the repository folder function type and the Business Processes function of the folder function type. The Business Processes function has an assigned model. Its name is the same as the folder type and it now contains the scenarios. If used, an additional test project folder is created as root object within the business process structure. This folder contains the test scenarios. While migrating, the root folder will be identified to set all test designer markers to the related items.
This step is executed directly on the database containing the 7.1 project. Each shortcut occurrence will be replaced by a new occurrence based on definition which is a copy of a shortcut's definition. You can select appropriate symbols into which the old shortcuts should be migrated. When executed, all migrated shortcuts are listed in the report output file.
In EPC based models the report creates a new definition from the one used by the shortcut. The definition is identical in attributes and direct properties to the definition of the shortcut. Only the name carries the copy prefix. The definition is placed into the database group where the model is stored. It creates a new occurrence based on the old one. The new occurrence is identical in all properties to the old one, e. g. attribute occurrences, unions, symbols, position, size, etc. New connections based on the old ones are created. The new ones are identical in all direct properties to the old ones (arrow style, connection point, pen, etc.). Assignments or master relations are ignored as they refer to the original only.
Since the migration ID of the 7.2 solution is the same for shortcuts and the activity they refer to, the shortcuts will receive the same SAP IDs. Assignments from the shortcut definition will be ignored. The symbol for the new occurrence is specified in the project configuration. As it is not available to the report, you must select the desired symbol.
In BPMN-based models distinct definitions for shortcuts already exist. You only need to replace the BPMN call activity by a task of your choice. However on process level the disband process on SAP side will create new steps. These are unknown to ARIS. There is no way to create a mapping for them. You must remodel the process manually after the respective steps have been synchronized to ARIS.
In the 7.1 project for each occurrence with the shortcut symbol type you now have a new definition with the same attributes and a new identical occurrence. It looks exactly the same as before, except the symbol type has changed from shortcut to the one you have defined. In BPMNTM the User task is in use instead of Call activity. All Call activity properties have been removed.
This report consolidates the different transaction types for URLs. The values Long URL, SAP URL application and Predefined URLs from directory for the Transaction type attribute are converted to Web address or file.
When executed, all actions are listed in the report output file.
This report replaces symbols types. As in 7.2 solutions, the Training and the General document document types are no longer available. These symbol types are replaced by the Project documentation symbol type by default.
You can use different symbol types as well. They must be defined in the method configuration of your solution configuration.
Executables of the URL type that do not belong to a process step in SAP® Solution Manager 7.2 have a dummy logical component group maintained. In SAP® Solution Manager 7.1 they do not have a logical component. If you assign these executables in SAP® Solution Manager 7.2 to an existing logical component group, you should use this group also in the next report.
The report changes all values in the SAP component attribute, both on the function and executable level. Also, all attributes of the system application types in the system landscape are replaced by the values of the 7.2 system. In 7.1 ARIS projects, the logical component is represented as the name of the logical SAP component. It is maintained as an attribute on the step and executable level. In the system landscape, it is maintained as logical component attribute in the respective application system type definition. Unused logical components will not be corrected.
When running the report, you first have to choose the database containing the downloaded SAP Solution Manager 7.2 branch, and you need to connect to the SAP system holding your SAP Solution Manager 7.1 project. This is to map the migration ID provided by SAP to the SAP ID used by ARIS in 7.1 projects. You can retrieve the values for application server and instance number from your SAP log on. If prompted for the logical component group to be used in ARIS, select the one that matches the logical component group in SAP Solution Manager 7.2 for executables that have not maintained one.
When the report is executed, all changed objects are listed in the report output file, as well as all SAP components to be changed.
This report adjusts the 7.1 project on the ID level. It also adjusts the project origin, containing the synchronization type and the branch ID of the branch as well as the project configuration.
7.2 SAP IDs are mapped to the 7.1 project's structure elements. Structure elements are scenarios, processes and process steps. In the 7.2 solution, the 7.1 ID is maintained in the Source ID attribute. SAP IDs are exchanged on object and model level.
When running the report, you first have to choose the database containing the downloaded SAP Solution Manager 7.2 branch, and you need to connect to the SAP system holding your SAP Solution Manager 7.1 project. This is to map the migration ID provided by SAP to the SAP ID used by ARIS in 7.1 projects. You can retrieve the values for application server and instance number from your SAP log on. If prompted for the logical component group to be used in ARIS, select the one that matches the logical component group in SAP Solution Manager 7.2 for executables that have not maintained one.
When the report is executed, all objects that were exchanged and all objects that were not exchanged are listed in the report output file. Objects that were not exchanged might belong to shortcuts or object definitions that are no longer used in the project.
You are now ready to synchronize the project in ARIS against SAP Solution Manager 7.2. Since SAP introduced the Process Step Library (PSL) and all assignments have been moved from the business process steps to the PSL steps, this initial synchronization is mandatory for adjusting the 7.1 project to the new 7.2 structure.
Since you are now about to synchronize your operational project, you must adjust your solution configuration to match your needs. For example, if you use user-defined models or symbol types, or you can disable the pool roles (if you do not need them anymore). You are recommended to enable the delete options for assignments. This is to move content successfully from the business process step FADs to the PSL. It is also a good idea to create a copy of the database and test the synchronization on this copy.
The synchronization will create the PSL and link all steps from the business processes to the PSL. This establishes the master variant relation. Each step from the business process structure has now its master in the PSL.
If you have synchronized a different project with the SAP system that, during content activation, was migrated in SAP into another folder, you can repeat the migration steps for this project as well. After the process is completed, you have to consolidate your ARIS projects manually by exchanging the scenarios that were downloaded into the migrated solution folder. As PSL elements can be related to several process steps, for process steps you may need to decide which assignment belongs to the PSL element and which ones belong to the process step itself.
If test projects were included, they will be created in the SAP system while uploading the test scenarios.