Recommended procedure
We recommend that the main system be defined when setting up the project or the solution. Do not attempt to work in SAP® Solution Manager while the synchronization is running. This will prevent data from being overwritten unintentionally during synchronization.
To avoid version conflicts when using BPR elements, use an SAP® Server for synchronization.
Synchronization
To verify that required attributes were not changed unintentionally after database editing, perform a consistency check.
If you transfer template projects to SAP® Solution Manager and use transports, you need to ensure that the user who runs the synchronization is assigned a maximum of one open transport for this project.
Otherwise, all transports will be ignored. If you need functions that require transport assignments, run the report Z_SOLAR_TPROJ_TADIR_CREATION in the SAP® system. This restores the missing relationships.
Transfer documents
If test and training documents were transferred to your database with a program version up to 7.2.0.551017, the project documentation symbol is used for the different types of documents. To avoid that test and training documents are entered on the Project documentation tab in SAP® Solution Manager after the transfer, you must use the relevant symbol types for information carriers.
In this case, start the synchronization for all projects and select the Transfer data to ARIS project option. This automatically assigns the document-specific symbols. Afterwards, you can transfer documents that were added in ARIS to SAP® Solution Manager.
The following table indicates which symbols are used for the different types of documents, and on which tabs the documents will be managed after their transfer to SAP® Solution Manager.
Symbol |
Symbol type |
SAP® Solution Manager |
|
General documentation (only for template projects) |
General documentation tab |
|
Project documentation |
Project documentation tab |
|
Test documentation |
Test cases tab |
|
Training documentation |
Training documentation tab |