Mapping SAP Solution Manager objects to definitions
To support the integration, System Architect uses BPMN Process definitions (and different Stereotype properties hin them) and introduces these new definition types: SAP Project, SAP Component, and SAP Transaction. The SAP Project import option gets the data structure exposed by Intellicorp’s web service and maps the hierarchy structure of the SAP Project to definitions.
The table below shows the mapping of SAP Project objects to System Architect definitions.
SAP Solman object
System Architect definition
Project
SAP Project
Business Scenario
BPMN Process (Stereotype: Scenario)
Business Process
BPMN Process (Stereotype: Process)
Process Step
BPMN Process (Stereotype: Step)
Logical Component
SAP Component
Transaction
SAP Transaction
SAP Projects can have multiple objects with the same name. However, System Architect requires unique names for different objects. To handle that, System Architect uses the SAPID value to create a new definition for each imported object. Unique names are created by combining the Name + _Number, where the Number is incremented until an unused name for a given definition is found. The naming logic works as follows:
•For Scenario, Process and Step, the naming convention described above is used, as Name+_Number.
•For Logical Component, the SAP name is copied, since these objects are uniquely named in SAP as well.
•For Transaction, if the object is unnamed, it is named as UNNAMED-SAPID.
Note Definitions that you create manually for the SAP Project definition are not listed in the Properties dialog by default. When you create a new BPMN Process definition, you must select Scenario as the value for the Stereotype property in the Analysis chapter of that definition. Otherwise, the new definition you create has Process as the value for the Stereotype property by default, and this would prevent that BPMN Process definition from being added as a child Scenario of the SAP Project definition.