The native interface between ARIS and SAP® Enable Now Producer allows documentation and other knowledge objects, such as simulations and courses, to be quickly and easily added to ARIS process structures.
ARIS processes and substructures can be imported into the SAP® Enable Now Producer, to add learning content. Afterwards, the links to the published learning content can be exported and can be started directly in ARIS from the corresponding process node.
The import process supports common ARIS model types such as BPMN and EPC. Custom model types can be specified optionally. Process models can be imported as media objects additionally, to use them in learning content.
If you want to use the native interface between ARIS and SAP® Enable Now, the following prerequisites must be met in ARIS:
Prerequisites
For detailed information about configuration and the use of SAP® Enable Now, such as ARIS Import and ARIS Export, refer to the related SAP online help.
Video tutorials are available for registered SAP customers
To do so, enable the ARIS Architect option in the SAP® options > Solution Manager option page.
All exceptions and calls to the SAP system are logged to the default client log file. Content that failed to be submitted to the SAP system is logged on the client machine. Log files are stored in the default java client directory. The file names contain the prefix sm72 and suffix .json.
Because information about downloaded and uploaded branch content can no longer be determined, errors are directly reported in message dialogs.
After the synchronization is completed and all <a_server> actions are logged, ARIS Architect actions are logged as well. The client log file contains messages concerning the data transfer of branch content to the SAP system and messages concerning the handling of documents. Both the client log file and the server log file are merged and stored by the ARIS Server. You can open the log file within the project or branch configuration.
ARIS for SAP Solutions will still support SAP® Solution Manager 7.1. You can configure the 7.1 version as well as the 7.2 version.
SAP Solution Manager 7.2 has a new concept and introduces new elements. This page gives an overview on how this new concept affects the data handling in ARIS. The main differences between SAP Solution Manager 7.1 and SAP Solution Manager 7.2 from an ARIS point of view are:
Branches
Projects, template projects and implementation projects no longer exist. The former project content is now called branch. In ARIS the project root node is replaced by the branch root node.
A branch is the entity that ARIS synchronizes with SAP Solution Manager. In the solution configuration you specify the SAP solution and the branch to synchronize with:
A branch represents a version of the SAP solution and contains its processes, libraries and systems. Per SAP default, there is always a production and a maintenance branch, but as many additional branches as required can be defined as well. When setting up a new solution, both the production and the maintenance branch are empty. The starting point for creating a new solution documentation is the maintenance branch. The solution will be available in production after it has been released from the maintenance branch in SAP Solution Manager.
Please note that you can use concurrent branches, for example, a development branch for customizing and/or one for upgrading to the newest release. If you create such a development branch from your production branch, it will contain the complete solution documentation from the production branch. Once the development or upgrade and testing are completed, changes will be available in production after they have been released from the development branch in SAP Solution Manager. You can synchronize your solution documentation with both branches. In ARIS each branch is independent from the other, that is, you can synchronize several branches of a solution into one as well as multiple ARIS databases, of course.
SAP Best Practice of branches consists of the following branches and their hierarchical structure:
The branch structure in SAP Solution Manager 7.2 looks like this example:
Logical component group
SAP Solution Manager 7.2 introduces the concept of Logical Component Group. This makes the management of logical components easier and avoids redundancy of documentation. Hence, much fewer logical components are the result. The hierarchical structure is as follows: SAP Solution > Logical Component Group > Logical Components. Logical components are detailed by the corresponding branch, for example, technical systems, roles, versions etc.
The PSL is one of several libraries that are introduced with SAP® Solution Manager 7.2.
The PSL contains process step originals (PSL items) and attached documents, test cases, etc. Each business process step used in a branch must refer to a PSL item. Multiple business process steps can reference the same PSL item. In ARIS, the PSL is downloaded into the Process Step Library database group of each branch. A relation is created for each business process step and its corresponding process step original.
Reuse of process step originals in business processes
Basic process steps can be defined as process step originals. Process step originals have individual names and descriptions, assigned executables, related roles, and specific documentation. You can reuse these process step originals in other processes as variants. Therefore, in ARIS Architect you create a new business process step and select the process step original on which the new business process step should based. A best practice is to use a standardized process framework to structure the PSL.
Example
In process A you use the process step original as defined. You simply map the process step original in the PSL to the business process step. In process B the business process step is slightly different. For example, an additional role and a document are required. Hence, at your business process step you add the new role, change the description and add a new document. It is still based on the same process step original, but has different roles and documents assigned and an individual description. When you select the business process step, you will see the properties of the process step original together with the properties of the business process step.
In Solution Manager 7.1 projects, you could connect several executables to one process step. SAP best practice for Solution Manager 7.2 recommends the use of a one-to-one connection between PSL steps and executables.
The Interface Library is one of several libraries that are introduced with SAP® Solution Manager 7.2.
The Interface Library is an inventory of interfaces that helps to facilitate the communication between partners. This structured collection of interfaces can be used and referenced directly at the process level. In SAP BPMN diagrams, interfaces can also be linked to intermediate events by adding an interface link. Because ARIS cannot save information about interfaces linked to intermediate events during diagram transmission, intermediate events are ignored.
In SAP Solution Manager, an interface is defined as a structural element that is saved in the Interface Library. An interface is identified by its name, its type (Interface or Composite interface), and additional parameters, such as Sending logical component group, Receiving logical component group, and Middleware logical component group. The Interface technology attribute is mandatory for interfaces of the Interface type.
In ARIS, the content of the Interface Library is mapped in the same way as all other SAP Solution Manager elements. The hierarchical structure of SAP® Solution Manager elements is structured in ARIS by means of the defined assignment structure. Structural elements are represented by SAP functions. The hierarchical structure is handled by functions with distinct SAP function type attributes, database subgroups, and models with related SAP model type attributes. Interfaces are represented as Class objects. Object definitions are created in the related Interface Library folder. Object occurrences are placed in the related function allocation diagrams (FAD).
In ARIS interfaces require these attributes:
The values in brackets are the related API names.
This attribute is mapped to the Sending logical component group in SAP Solution Manager. The values of the Sending component, Receiving component,and Middleware component attributes must match exactly the name of the logical component group as defined in the system landscape of the SAP solution.
This attribute is mapped to the Receiving logical component group in SAP Solution Manager. The values of the Sending component, Receiving component,and Middleware component attributes must match exactly the name of the logical component group as defined in the system landscape of the SAP solution.
Possible values are Interface or Composite interface.
The Interface technology attribute is required only for interfaces of the Interface interface type.
The Middleware component attribute is optional.
In contrast to SAP Solution Manager, in ARIS interfaces assigned to processes must not be modified. For one and the same interface, for example, you cannot use different descriptions or customer attributes because in ARIS, occurrence copies of the related object definitions are used. In ARIS, you can only modify the object definition stored in the related Interface Library folder. If you do so, the related Interface Library original in the SAP system will be modified too during data transfer to SAP Solution Manager. This is because interfaces are structural elements in SAP Solution Manager but they are mapped to assignments in ARIS. An interface is always related to the Interface Library even if the library is not included during data transfer. Note that attributes are always changed, even if you disable the Include Interface Library option in the Synchronization Wizard's Transfer structural elements dialog, but select the Transfer new interfaces option in the Transfer executables, documents, and interfaces dialog.
To add an interface to a process, place an object occurrence of the related Class object in the FAD of the process. An occurrence of an interface is identified by its external GUID.
If you create interfaces with assistance, you can select all mandatory attributes in the dialog. Interfaces created this way always match the consistency rules.
Flexible process structure
In SAP Solution Manager 7.1, the process structure is fixed on a 3-level hierarchy: Scenarios > Business Processes > Process Steps. With SAP Solution Manager 7.2, there can be as many levels as required by placing scenarios in an arbitrary nested structure of folders.
However, the three levels are still present, and will be the core of the documentation. You will simply be able to add as many levels as needed on top of them.
You can use folders to structure scenarios as well as the Process Step Library (PSL) and the Interface Library. 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. The hierarchical order is created by models and SAP functions with distinct SAP model types and SAP function types. For folder items, you can use the new Folder, Process steps folder, Executables folder, and Interface folder SAP function types and SAP model types.
Hierarchy |
SAP model type/ |
Subordinate |
Superior |
---|---|---|---|
Branch |
Project |
Folder Process steps folder (PSL) Executable folder Interface folder |
- |
Folder |
Folder |
Folder Scenario |
Branch or folder |
Scenario |
Scenario |
Process |
Folder |
Process |
Process |
Process step PSL Occurrence* |
Scenario |
Process step |
Process step |
- |
Process |
Process steps folder (PSL) |
Process steps folder |
Process step original (PSL)
|
Process steps folder (PSL)
|
Process step original (PSL) |
Process steps folder |
- |
Process steps folder (PSL) |
Executable folder |
Executables folder |
Executable folder |
Executable folder |
Interface folder |
Interface folder |
Interface folder none** |
Interface folder |
*In contrast to SAP, in ARIS you can use occurrences of process step originals as subordinate elements of processes.
**In contrast to SAP, interfaces in ARIS are not mapped as structural elements, but as assignments. In SAP Solution Manager 7.1, the sequence is available on each hierarchical level. In SAP Solution Manager 7.2, folders and PSL come into play. For both kinds it makes no sense to order the items in a distinct sequence. Folders, PSL steps and scenarios are sorted in alphabetical order instead. The sequence can only be maintained for processes and process steps.
Shortcuts and occurrence copies
Shortcuts have been replaced by the relation between PSL elements and database elements. In ARIS, occurrence copies of model objects, for example, of process steps, will no longer be offered. Now, references between objects will be in place. In ARIS, when copy-and-pasting an SAP-related object, such a master-variant relation will be created. Of course you are supported by a wizard.
Keywords
Keywords no longer exist. SAP now uses customer attributes instead.
Global attributes
Since projects, template projects and implementation projects no longer exist, global attributes are obsolete.
Customer attributes
Customer attributes with Undefined data type cannot be assigned to ARIS attributes. Attribute values can be specified only for customer attributes of the Value data type. If required, create new attributes to be used for the assignment.
Define order
The Define order functionality is not available for SAP solutions, since the SAP Solution Manager 7.2 does not provide sorting. Nevertheless, the standard ARIS behavior will remain the same:
Transactions
Transactions are now called executables.
All original executables (Screen objects) are stored in the Executable Library. Executables are contained in executable folders. You can place executables in an arbitrarily nested folder structure, using as many levels as required. In ARIS, Executable Library folders are represented by SAP functions of the Executables folder SAP function type. The same logical component group must be assigned to all subfolders of the Executable Library. You can download the Executable Library to ARIS.
In ARIS, executables are identified by the key deriving from the executable object, the type of the executable, and the related logical component group. The synchronization behavior for executable folders is the same as for other structural elements. For example, you can move them or assign a shadow symbol. If you have selected the Transfer Executable Library option, the library is transferred during SAP synchronization.
In SAP Solution Manager, each executable item has its individual SAP ID. In SAP Solution Manager, you can use an executable from the Executable Library and assign it to different process steps. These executables can have different attributes. In ARIS, you can have only one object definition representing an executable in a branch. You can create multiple occurrences of one definition, either in the Executable Library folder structure or in other database groups. However, all occurrences of this object definition have the same attributes. If you want to use executables that have different attributes, you must create definition copies and store them in the Executable Library in ARIS. If you use occurrence copies, ARIS checks whether the executable is contained in the Executable Library. This is the case if the related object definition occurs in the FAD of the related Executable Library folder. If you transfer only elements from the business processes folders during SAP synchronization, the attributes of those executables are not transferred.
Attributes are transferred, if the object definition of a Screen object occurs in the Function allocation diagram (FAD) within the Executable Library and you have selected the Include Executable Library option in the Synchronization Wizard's Transfer structural elements dialog. Attributes of executables are transferred only if the executable is part of the Executable Library and the related library folder is transferred as well. The attributes of the complete library are transferred if you have selected the Transfer Executable Library synchronization option in the Synchronization Wizard's Transfer assignments dialog.
SAP Fiori® Apps are available in ARIS.
Global attributes
Global attributes are no longer supported.
Customer attributes
Customer attributes will still be downloaded from SAP® Solution Manager, but without data types and values. Some static attributes of the value type are available and can be assigned. Customer attributes with Undefined data type cannot be assigned to ARIS attributes. Attribute values can be specified only for customer attributes of the Value data type. If required, create new attributes to be used for the assignment. Before assigning customer attributes, you must maintain the data types. For attributes of the value data type, maintain the attribute values according to the settings in the SAP system. In ARIS, Value attributes can have only one specific value.
Multi-value datatype
To handle Multi-value attributes in ARIS, you must assign Customer attributes of the Multi-value data type to ARIS text attributes. In ARIS text attributes, you can specify multiple values as a comma-separated list. The value pairs are listed as a value key (such as RIGHT in capital letters without brackets) followed by the value of the key in brackets (Right). As best practice, we recommend that you use the same strings for keys and values.
SAP added a new description attribute to each structure item.
Documentation
The different document types training, test, project and general are no longer supported. Instead of these types, the new Best practice documentation is introduced. Best practice documents have no document type and no document state. 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 test document.
The General document symbol will be used by default for best practice documents in ARIS.
There are some additional changes introduced with Solution Manager 7.2:
You can upload process models and process diagram variants as BPMN diagrams to the SAP system. ARIS models are automatically converted to BPMN diagrams of the selected type. Models of the EPC and the Value-added chain diagram types are always converted. Models of all other types that are relevant for SAP synchronization are converted only if modeling rules are violated. If a model cannot be converted, the model is not transferred. For BPMN diagrams available in ARIS, the layout of the ARIS diagrams is used. If ARIS models are converted, by default, the layout for generated BPMN diagrams is Horizontal and the System landscape is used as a target diagram subtype. You can select other settings, if required.
You can transfer models of only these types:
Prerequisite
Procedure
The synchronization starts and the models are transferred to SAP Solution Manager.
Process diagram variants are transferred only if process variant models are assigned to the related SAP functions of the Process function type. For process variants, you can only use model types that can be assigned to a function multiple times, such as Enterprise BPMN collaboration diagrams. The assigned models must have the Process variant SAP model type. All entities contained in the process variants are reused in SAP Solution Manager.
You can transfer process diagram variants as BPMN diagrams.
Prerequisite
Procedure
The synchronization starts and the models are transferred to ARIS.
The process variant models are assigned to the related SAP functions of the Process function type. The assigned models have the Process variant SAP model type. SAP objects of the Free system type are not transferred. All entities contained in the process variants are reused in SAP Solution Manager.
If diagrams were transferred from ARIS before, a new Enterprise BPMN model is created in ARIS. The original ARIS model is maintained. Modifications must be made in the original model. The new Enterprise BPMN model is not relevant for SAP synchronization.
Process diagrams are downloaded as a BPMN collaboration diagram (BPMN 2.0). In contrast to ARIS, SAP® Solution Manager requires a pool in SAP process diagrams. These pools are created in ARIS and the layout of imported diagrams is preserved.
Process diagrams previously imported to ARIS cannot be re-transferred to SAP® Solution Manager.