What is a method configuration?

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 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
of the
SAP function type:

models are assigned of the
SAP model type:

These models contain objects of the
SAP function type:

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.

SAP Solution (Example)

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.

Root object

The subgroup stores the content in hierarchical levels.

Branch content

It contains the Business process, Process step library, Roles, and the System landscape subgroups.

SAP Solution Manager 7.1

SAP Solution Manager 7.2

Project

Branch

Scenario

Scenario and Folder (optional)

Process

Process

Process step

Process step

 

The PSL has a similar structure but uses different element types.

You can change the model types to be used in the configuration of each project or branch. Predefined symbol and connection types are used in the models. Configuration administrators can adjust the predefined model, symbol, and connection types in the Method Configuration Wizard. If you use BPMNTM diagrams, you need to customize the method configuration for using BPMNTM.

Any conflicts are detected using the consistency rules prior to synchronization. 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.

Warning

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.

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.