There have been a number of queries coming from the field regarding what is permitted for SAP Advanced Data Migration and Management by Syniti (ADMM), or the earlier SAP Advanced Data Migration by Syniti (ADM), when it comes to extracting data out of SAP ECC or SAP S/4HANA for data migration purposes, as well as when it comes to loading data into S/4HANA. I hope this short blog can provide clarity. For reference, the contents are summarised from what is found in the Software Use Rights and Service Description Guide documents.
When the source is SAP ECC with third-party runtime database:
- Syniti ADMM and ADM are allowed to extract data out from the source on a one-time productive basis (defined as an initial data load) to a SAP target using database level communication (which means ODBC, RFC, BAPI, SOAP, etc. are acceptable).
- Unlimited data extracts from the source are permitted to a separate, non-productive target prior to the conclusion of initial data load for purposes of testing and/or development.
- Unlimited data synchronisation by ADMM and ADM between the source and the intended target database is permitted via application-level API communication (i.e. SAP's API's like RFC, BAPI, etc. are allowed but not generic API's like ODBC, JDBC, or SOAP).
If ECC is running with third-party full-use databases, the above mentioned restrictions do not apply.
When the source is S/4HANA with runtime database or ECC on HANA with runtime database (i.e. HANA run-time):
- Syniti ADMM and ADM are allowed to extract data out from the source using application-level API communication (which means SAP's API's like RFC, BAPI, etc. are allowed but not generic API's like ODBC, JDBC, or SOAP).
- Unlimited data synchronisation by ADMM and ADM between the source and the intended target database is permitted via application-level API communication (i.e. RFC, BAPI, etc. are allowed but not generic API's like ODBC, JDBC, or SOAP).
If the source is S/4HANA with full-use database, the above mentioned restrictions governing S/4HANA with runtime database do not apply.
When the target is S/4HANA with runtime database (i.e. HANA run-time):
- Syniti ADMM and ADM are allowed unlimited writes to the target application using SAP HANA level communication (which means RFC, BAPI, ODBC, JDBC, etc. are allowed). This means ADMM and ADM are writing to Migration Cockpit staging tables (or S/4HANA application-generated structures).
- However, ADMM and ADM are not permitted to create staging tables or write to tables created outside of Migration Cockpit. No direct writing to the S/4HANA application tables is permitted for ADMM and ADM.
If the target is S/4HANA with full-use database, there are no restrictions on ADMM and ADM writing directly into the underlying S/4HANA tables. However, writing to (Migration Cockpit) staging tables for Migration Cockpit to be used as the last-mile loader into S/4HANA is still the supported scenario.
In conclusion, I hope the above has explored the various scenarios where Syniti ADMM and ADM are used for migrating data out of SAP ECC or SAP S/4HANA and covered the restrictions governing the use of these solutions in those scenarios.
