Error code - SOLAR_0025

The error is reported during SAP® synchronization. A conflict occurred while checking consistency rules.

Error message

SAP® synchronization was previously performed with another method configuration. Synchronization with different method configurations can lead to unpredictable errors and loss of data. Please click Help for further information. The following elements were changed:

Cause

You have already downloaded or synchronized the project with another user-defined method configuration. The method configuration has been subsequently changed or you have selected a different one. Therefore, you are synchronizing with different method configurations.

Solution

To avoid errors, you are urgently advised not to change method configurations with which projects were downloaded or synchronized. Errors will not occur if you change the method configuration for items that do not yet exist in your project.

Click No (recommended)

Performs SAP® synchronization based on the method configuration with which the project was originally downloaded from the SAP system. If it has been deleted, it will be restored. The current method configuration is ignored.

Click Yes

Performs SAP® synchronization based on the current method configuration. The configuration with which the project was originally downloaded from the SAP® system is not taken into consideration. The original configuration is overwritten by the current one and cannot be restored.

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.

Ensure that all user-defined method extensions are included in the current method filter. If you use a user-defined method filter, ensure that all items listed in the summary of Method Configuration Wizards are included in the filter.