Method filter and method configuration
If you synchronize with an incomplete method filter or different method configurations, unpredictable errors and loss of data may occur.
The current method filter must contain all required items defined in the method configuration of the SAP® synchronization.
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.
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.
If you are not using a user-defined method configuration, but user-defined model types, ensure that these model types are defined on the current client. Otherwise, select existing model types.
Ensure that projects are always synchronized using the same method configuration with which they were downloaded from the SAP® system.
Check a new method configuration using a previously saved SAP® Solution Manager project before you use the method configuration in a productive environment.
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.