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 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. 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. You can assign several models of the same type, such as EPC or Function allocation diagram, to a function. If you use BPMN diagrams, only one assigned BPMN diagram is allowed. The SAP model type attribute must be specified only for the one 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. 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. 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/
SAP function 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. 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 has 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 System landscape subgroups.

SAP Solution Manager 7.1

SAP Solution Manager 7.2

Project

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.

Branch

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.

Scenario

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 Value-added chain diagram (VACD) type and a model of the Function allocation diagram (FAD) type are assigned automatically to business scenarios. The executables, documents, end user roles, organizational units, or master data are connected to SAP functions occurring 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.

Scenario and Folder (optional)

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 Value-added chain diagram (VACD) type and a model of the Function allocation diagram (FAD) type are assigned automatically to business scenarios. The executables, documents, end user roles, organizational units, or master data are connected to SAP functions occurring 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. 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.

Process

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 executables, documents, end user roles, organizational units, or master data are assigned to SAP functions occurring 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.

Process

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 executables, documents, end user roles, organizational units, or master data are assigned to SAP functions occurring 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.

Process step

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.

Process step

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.

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 must 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.