How to use scoped solutions in ARIS

In SAP Solution Manager 7.2 you can use scoping to restrict content to defined views. By specifying multiple scopes, you can split a solution into various parts that can be treated independently in ARIS.

Each scope in SAP Solution Manager is represented as a branch in ARIS. If you define a scope, for example, for sales scenarios in your SAP solution, you can download this content to ARIS as an individual branch of this solution.

For each scope of a solution a branch configuration is needed within the solution configuration. When creating a solution configuration in ARIS, the administrator can select the required scope. If a solution has no scopes defined, the Default scope is used. The Default scope represents the complete content of a solution.

If users download a scope to ARIS, the content is handled like an additional branch of the solution. The scope name is added to the solution name to indicate the scoped content. This combination is used as project name in ARIS. Assignments, such as documents, executables or roles cannot be reused. Each scoped branch uses its own assignments since the branches in ARIS are independent. If a role definition is deleted in scope A this action does not affect scope B since this content might be used there. However, if you change the content of a document that is used in scope A and in scope B, the changed content is also available in scope B.

If you share the same structure in multiple scopes and you delete structures in scope A that are still used in scope B, you will face problems when synchronizing data. SAP synchronization cannot distinguish between the different structures. The first data transfer will be performed correctly, the second will fail.

Warning

If the scope of a solution was changed in SAP Solution Manager make sure to start the SAP synchronization using the Transfer data to ARIS option. Otherwise folders added to the scope may be deleted.