For the data transfer between ARIS and SAP® Solution Manager to run without errors, the following conditions and rules must be adhered to.
ARIS provides you with optional support in creating SAP functions, transactions, and documents. If you enable the Open supporting dialog and Run transactions with SAP® Solution Manager check boxes on the Solution Manager options page, the transaction codes and assignment structure of new SAP functions will automatically be specified consistently. Documents can be transferred to SAP® Solution Manager.
Read the following notes before you transfer data:
Recommended procedure
We recommend that the main system be defined when setting up the solution. Do not attempt to work in SAP® Solution Manager while the synchronization is running. This will prevent data from being overwritten unintentionally during synchronization.
Transfer documents
When documents are synchronized in ARIS, the Project document symbol will be used for all document types. ARIS can no longer determine whether the document is a project document or a training document.
The training document type is no longer supported. The new Best practice documentation is introduced. Best practice documents have no document type and no document state. For best practice documents in ARIS, the General document symbol will be used by default.
The following table indicates which symbols are used for the different types of documents, and how the documents will be managed in SAP® Solution Manager.
Symbol |
Symbol type |
SAP® Solution Manager |
General documentation
|
Best Practice documentation |
|
|
Project documentation |
Project documentation |
Test documentation |
Test cases |
|
|
|
|
Method filter and method configuration
If you synchronize with an incomplete method filter or different method configurations, unpredictable errors and loss of data may occur.
For example, if you have unintentionally removed the symbol used for scenarios from the current method filter and transfer data to SAP® Solution Manager with deletion options enabled, your entire project will be deleted, since scenarios are ignored by the filter.
During the synchronization, the current method configuration of the SAP® synchronization is checked. If the method configuration has been changed in the meantime, ensure that all items of the original method configuration are also included in the current method filter.
If you are not using a user-defined method configuration, but user-defined model types, ensure that these model types are defined on the current client. Otherwise, select existing model types.
Changing object types and symbols for end user roles may result in errors, depending on the method filter. Since end user roles are reused from the role pool, there is a risk that the symbol, object, or connection type will no longer match. In this case, the default symbol is used. However, it must be included in the method filter.
A subsequently modified method configuration does not update any previously synchronized items. If items have already been synchronized in your database and you have subsequently changed their symbol, object, or connection types in the method configuration, they will continue to exist after another synchronization. The result is a mixture of old and new types in your database.
Object definitions and SAP shadow functions
The symbols shown are used if you are not using a user-defined method configuration. If you have customized the method configuration for using BPMN, please find out how SAP shadow functions that deviate from the default behave.
SAP® items are identified by the SAP ID attribute. The SAP ID is unique in SAP® Solution Manager. It is automatically specified during synchronization of data in ARIS. If you create a definition copy of a synchronized object, it will have the same SAP ID. It will then no longer be possible to perform synchronization, since the SAP ID is not unique and the object to be synchronized is not found. Definition copies of previously synchronized items must not be used.
Therefore, in SAP® process models with a specified SAP ID, SAP functions with an identical SAP ID must occur only once. You can recognize these SAP functions by this symbol if you have not changed the method configuration:
If you are using other occurrence copies of SAP functions, they are displayed with the SAP shadow function symbol by default and are not included in the synchronization:
During data transfer between ARIS and the SAP® system, the mandatory hierarchical structure is created as defined in the default method configuration of the project or branch. The method configuration determines how database items are displayed in ARIS, after they have been downloaded from SAP® projects and branches or after SAP® synchronization. The ARIS administrator can customize the default method configuration for projects and branches. This makes it possible to use different element types, for example, BPMNTM diagrams.
Hierarchy
The hierarchical structure of SAP® Solution Manager elements is structured in ARIS by means of the defined assignment structure. Structural elements are always represented by functions. The hierarchical structure is handled by functions with distinct SAP function type attributes, database subgroups, and models with related SAP model type attributes. The default symbol used for functions depends on the model type selected for the assignment. The SAP function type attribute of a function must match the SAP model type attribute of the assigned model. This model must only contain function occurrences of the next lower SAP function type. Several models of the same type can be assigned to a function. The SAP model type attribute can only be specified for the model relevant to synchronization, and the assignment structure must be consistent.
In SAP® Solution Manager 7.1, the process structure below the project node is fixed on a 3-level hierarchy: Scenarios > Business Processes > Process Steps.
To objects |
models are assigned of the |
These models contain objects of the |
---|---|---|
Project |
Project |
Scenario |
Scenario |
Scenario |
Process |
Process |
Process |
Process step |
As this structure is mandatory for SAP synchronization, in ARIS new SAP functions can be created using a wizard. This allows you to create all assignments automatically (see different procedures for SAP Solution Manager 7.1 or SAP Solution Manager 7.2).
With SAP® Solution Manager 7.2, this structure below the branch node is still mandatory. By placing elements in an arbitrary nested folder structure, there can be as many levels as required. In ARIS SAP folders are handled by subgroups, functions with the Folder SAP function type attribute value, and models with the Folder SAP model type attribute value. Folders can be used to structure scenarios as well as the Process steps library (PSL). Below the Business process structure, folders can only have scenarios or folders as subordinate elements. Superior elements can either be a folder or a root node. The same rules apply for the PSL. But since scenarios or processes are not available in the PSL, Process steps folders can only have process step originals as subordinate elements.
In ARIS, folders are handled like all other SAP structure elements branch, scenario, process and process step. For folder items, the new Folder and Process steps folder SAP function types and SAP model types are to be used.
Hierarchy |
Model type |
Subordinate |
Superior |
---|---|---|---|
Branch |
Project |
Folder Process steps folder(PSL) |
- |
Folder |
Folder |
Folder Scenario |
Folder |
Scenario |
Scenario |
Process |
Folder |
Process |
Process |
Process step |
Scenario |
Process step |
Process step |
- |
Process |
Process steps folder (PSL) |
- |
Process step original (PSL)
|
Process steps folder (PSL)
|
Process step original (PSL) |
- |
- |
Process steps folder (PSL) |
This example shows how this SAP solution is mapped in ARIS.
The Development branch of the DEMO_ARIS Branch solution was downloaded to the SAP database subgroup. The top structure always starts with a root function of the Project SAP function type. This root function, as well as the subgroup containing the branch's content, always have the same name as the SAP project or branch.
The subgroup stores the content in hierarchical levels.
It contains the Business process, Process step library, Roles, and the System landscape subgroups.
By default, the hierarchical structure is mapped without using a method configuration as follows. If you want to use BPMNTM, for example, you must customize the method configuration accordingly.
SAP Solution Manager 7.1 |
SAP Solution Manager 7.2 |
---|---|
SAP® Solution Manager projects and branches are represented in ARIS by start objects. Objects of the Function type are created automatically. You cannot change this setting. For the start objects, the Project SAP function type attribute value is selected automatically. Models of the Project SAP model type are assigned to the start objects. By default, a model of the Value-added chain diagram (VACD) type and a model of the Function allocation diagram (FAD) type are automatically assigned to start objects. The assigned application systems are listed in the FAD. The business scenarios are displayed in the VACD. Depending on the model type, the symbols representing occurrences of business scenarios change. These project models of the Project SAP model type may only contain business scenarios. By default, business scenarios are represented as objects of the Scenario SAP function type with the SAP® value-added chain symbol. You can also select other model types instead of VACD and use user-defined function allocation diagrams. |
SAP® Solution Manager branches are represented in ARIS by start objects. Objects of the Function type are created automatically. You cannot change this setting. For the start objects, the Branch SAP function type attribute value is selected automatically. Models of the Branch SAP model type are assigned to the start objects. By default, a model of the Value-added chain diagram (VACD) type and a model of the Function allocation diagram (FAD) type are automatically assigned to start objects. The assigned application systems are listed in the FAD. The business scenarios are displayed in the VACD. Depending on the model type, the symbols representing occurrences of business scenarios change. These project models of the Project SAP model type may only contain business scenarios. By default, business scenarios are represented as objects of the Scenario SAP function type with the SAP® value-added chain symbol. You can also select other model types instead of VACD and use user-defined function allocation diagrams. |
Objects of the Function type are created automatically in ARIS for SAP® Solution Manager business scenarios. You cannot change this setting. The value Scenario is selected automatically for the SAP function type attribute for business scenarios. Models of the Scenario SAP model type are assigned to the business scenarios. By default, a model of the Event-driven process chain (EPC) type and a model of the Function allocation diagram (FAD) type are assigned automatically to business scenarios. The assigned transactions, documents, end user roles, organizational units, or master data are assigned in the FAD. The business processes are displayed in the EPC. Depending on the model type, the symbols representing occurrences of business processes change. These scenario models of the Scenario SAP model type may only contain business processes. By default, business processes are represented with functions of the Process SAP function type with the SAP function symbol. You can also select other model types instead of the EPC or use user-defined function allocation diagrams. |
By placing elements in an arbitrary nested folder structure, there can be as many levels as required. In ARIS SAP folders are handled by subgroups, functions with the Folder SAP function type attribute value, and models with the Folder SAP model type attribute value. Folders can be used to structure scenarios as well as the Process steps library (PSL). Below the Business process structure, folders can only have scenarios or folders as subordinate elements. Superior elements can either be a folder or a root node. The same rules apply for the PSL. But since scenarios or processes are not available in the PSL, Process steps folders can only have process step originals as subordinate elements. Objects of the Function type are created automatically in ARIS for SAP® Solution Manager business scenarios. You cannot change this setting. The value Scenario is selected automatically for the SAP function type attribute for business scenarios. Models of the Scenario SAP model type are assigned to the business scenarios. By default, a model of the Event-driven process chain (EPC) type and a model of the Function allocation diagram (FAD) type are assigned automatically to business scenarios. The assigned transactions, documents, end user roles, organizational units, or master data are assigned in the FAD. The business processes are displayed in the EPC. Depending on the model type, the symbols representing occurrences of business processes change. These scenario models of the Scenario SAP model type may only contain business processes. By default, business processes are represented with functions of the Process SAP function type with the SAP function symbol. You can also select other model types instead of the EPC or use user-defined function allocation diagrams. |
Objects of the Function type are created automatically in ARIS for SAP® Solution Manager business processes. You cannot change this setting. The value Process is selected automatically for the SAP function type attribute for business processes. Models of the Process SAP model type are assigned to the business processes. By default, a model of the Event-driven process chain (EPC) type and a model of the Function allocation diagram (FAD) type are assigned automatically to business processes. The assigned transactions, documents, end user roles, organizational units, or master data are assigned in the FAD. The process steps are displayed in the EPC. You can also select other model types instead of the EPC or use user-defined function allocation diagrams. Depending on the model type, the symbols representing occurrences of process steps change. These process models of the Process SAP model type may only contain process steps. By default, process steps are represented with functions of the Process step SAP function type with the SAP function symbol. |
Objects of the Function type are created automatically in ARIS for SAP® Solution Manager business processes. You cannot change this setting. The value Process is selected automatically for the SAP function type attribute for business processes. Models of the Process SAP model type are assigned to the business processes. By default, a model of the Event-driven process chain (EPC) type and a model of the Function allocation diagram (FAD) type are assigned automatically to business processes. The assigned transactions, documents, end user roles, organizational units, or master data are assigned in the FAD. The process steps are displayed in the EPC. You can also select other model types instead of the EPC or use user-defined function allocation diagrams. Depending on the model type, the symbols representing occurrences of process steps change. These process models of the Process SAP model type may only contain process steps. By default, process steps are represented with functions of the Process step SAP function type with the SAP function symbol. |
Objects of the Function type are created automatically in ARIS for SAP® Solution Manager process steps. You cannot change this setting. The value Process step is selected automatically for the SAP function type attribute for process steps. Process steps represent the lowest hierarchy level and may have occurrences only in process models. By default, process steps are represented with functions of the Process step SAP function type with the SAP function symbol. |
Objects of the Function type are created automatically in ARIS for SAP® Solution Manager process steps. You cannot change this setting. The value Process step is selected automatically for the SAP function type attribute for process steps. Process steps represent the lowest hierarchy level and may have occurrences only in process models. By default, process steps are represented with functions of the Process step SAP function type with the SAP function symbol. |
|
The PSL has a similar structure but uses different element types. |
Assignments will be included if the SAP ID, SAP function types, and SAP model types match between object definitions and assignments that have already been synchronized.
Assignments are also included if no SAP ID exists (that is, object definitions have not yet been synchronized), and if SAP function types and SAP model types match between object definitions and assignments. All assignments without an SAP function type or SAP ID will not be included.
If you have customized the method configuration for using BPMNTM, find out about the assignment structure that deviates from the default.
If you move items in the ARIS database or in SAP® Solution Manager, these items are included in the synchronization only:
Synchronized ARIS items have an SAP ID. The corresponding items must also exist in SAP® Solution Manager. If an item that still exists in ARIS has been deleted in SAP® Solution Manager, this causes an error while transferring data to SAP® Solution Manager. If you delete items from SAP® Solution Manager, you must subsequently transfer the changes to ARIS. Process Step Library items cannot be deleted as long as they reference a business process step.
A logical component group that is defined in the system landscape of the SAP® branch can optionally be assigned to process steps. If assigned, the logical component group must be identical with the corresponding original repository step's logical component group. Logical component groups are specified in the SAP Solutions attribute SAP component. Process steps are functions with the Process step SAP function type. The SAP function type attribute is located in the SAP Solutions attributes attribute type group.
Transactions/executables and SAP® components
Attributes that are appropriate for the transaction type must be specified for transactions (screens). The SAP component must be defined in your SAP® project (system landscape).
The attributes Transaction code and SAP component must be unique. For example, if you want to run the transaction VA02 and use different SAP® systems, you must assign the executing SAP® system.
Please ensure that the spelling is identical. In ARIS, the system landscape is located in the function allocation diagram assigned to the project node.
Non-URL transactions must be assigned to logical components (SAP component attribute type).
For transactions (screens) that are assigned to process steps, the SAP component attribute of the Screen object and of the process step must be identical.
If you create transactions using the wizard, all attributes are automatically specified correctly. If necessary, enable the Open supporting dialog and Run transactions with SAP® Solution Manager check boxes on the SAP® options > Solution Manager options page.
Click ARIS > Options.
You can create transactions/executables so that they can be started in SAP® Solution Manager. The modeling convention defines that every transaction/executable must be modeled exclusively in models of type Function allocation diagram (FAD) on an object of type Screen. The FAD must be assigned to an SAP function. The Transaction code attribute can be specified by one transaction code only. Entering multiple transaction codes is not allowed. Therefore, an object of the Screen type must be created for each transaction.
On the SAP® options > Solution Manager options page, you can enable the Open supporting dialog check box to specify that you want to be supported when creating new SAP functions, transactions, and documents. This ensures that the data is automatically specified consistently when created and can be synchronized between ARIS and SAP® Solution Manager.
If you have enabled the check box, you can specify transactions only via screens. The Transactions dialog enables you to manage transactions only if the call was started for an SAP function with an assigned function allocation diagram. If this is not the case, the specified functionality is not available. If the attribute is specified on other elements, the transaction is ignored.
If you disable the check box, transactions can still be specified on the Transaction code attribute of models and objects. These transactions cannot be started in SAP® Solution Manager and are not included in the SAP® synchronization.
Use Test Designer to create and edit test projects.
When documents are synchronized in ARIS, the Project document symbol will be used for all document types. ARIS can no longer determine whether the document is a project document or a training document.
The training document type is no longer supported. The new Best practice documentation is introduced. Best practice documents have no document type and no document state. For best practice documents in ARIS, the General document symbol will be used by default.
The following table indicates which symbols are used for the different types of documents, and how the documents will be managed in SAP® Solution Manager.
Symbol |
Symbol type |
SAP® Solution Manager |
General documentation
|
Best Practice documentation |
|
|
Project documentation |
Project documentation |
Test documentation |
Test cases |
|
|
|
|