table of contents


Basic Working

  • For each template, the Replicator App will create all dependency objects. For example:

    • RBI

      • Equipment/Location Template

      • Attribute or Indicator Groups

      • Attributes and Indicators

      • Code Lists

      • Matrix

      • Assessment Template

  • For RBI and IDMS , Technical ID (SAP Auto Generated ID - GUID) and Client ID (Server ID) are used to identify whether template should be created or updated in the target system, While Importing via the tool if both ID matches then template will update or else it create new template

  • For CML, Internal ID (User defined ID) are used to identify whether template should be created or updated in the target system While Importing via the tool if both ID matches then template will update or else it create new template

  • The replicator works with the principle of old ID and new ID. It keeps mapping between old id and new id in the system.

  • When a new object gets created, It maintains this mapping.

  • Objects which require dependent objects, it replaces IDs with this mapping.

  • For template dependencies (where one template is dependent on another), both

    templates should come from the same tenant as well as dependent template should

    be imported before main template is imported.

  • Descriptions not IDs. Descriptions are not unique. Multiple objects of the same type with the same descriptions could co-exist.

Back to Table of Contents