Skip to Content
Author's profile photo Reinhard Sudmeier

Do not delete communication systems with existing data

When you already started to replicate or upload master data from one system you should not delete this system any more. If you do so the existing master data will loose their source system and you cannot reassign it by recreating a system with the same ID.

The reason is that every system has a GUID (globally unique identifier), which is not visible on the UI and if you delete the system the GUID is gone. if you recreate a system with the same ID it gets a new GUID and the existing master data still refer to the old GUID.

Instead you can change the IDs and technical settings of existing systems or set them to obsolete.

Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Former Member
      Former Member

      Thank you for this information. This is very helpful.

      For further clarification, what would be the best approach for the scenario when the source system of the master data has to be changed from a legacy system to a new SAP/non SAP source system?

      Thanks again!

      Author's profile photo Reinhard Sudmeier
      Reinhard Sudmeier
      Blog Post Author

      Hi Kathryn,

      this depends on the scenario. If all master data need to be moved from one system on another renaming and changing the technical settings, even changing from SAP to non-SAP or vice-versa is the right approach. If you only want to move parts of the data, for example employees and cost centers were replicated from an HR system, but the cost centers need to be assigned to an FI system you need to create the new system and open an incident asking us to change the source system of the cost centers in the example above.

      Best Regards, Reinhard