SAP Mapping - Automate_Studio_Manager - Automate_Evolve - Latest

Automate Studio Manager Migration Guide

Product type
Software
Portfolio
Integrate
Product family
Automate
Product
Automate > Automate Studio Manager
Version
Latest
ft:locale
en-US
Product name
Automate Studio Manager
ft:title
Automate Studio Manager Migration Guide
First publish date
2018
ft:lastEdition
2024-02-16
ft:lastPublication
2024-02-16T10:31:20.160000

Mapping between the source SAP system and the destination SAP system must be maintained.

Post-log in, information is fetched from the source Foundation site, and the grid displays the source SAP system information.

The next step is to map the source SAP system to the destination SAP systems.

  1. This is required for scripts with AutoRun and SAP server selected.
  2. Scripts marked with SAP server require valid mapping for migration.
  3. The destination SAP server must be from the global app or the app you are currently logged in to.
  4. You can add a new source SAP system. That system can be mapped to the destination SAP system.
  5. When you switch apps, the SAP system mapping of the destination app you are logged-in to is displayed.
  6. Mapping is stored for the source site and the destination site with the app in the local file in the executable bin – for example, Sapmapping.xml.