For this approach, instead of generating the staging tables directly in the SAP S/4HANA Cloud system, the migration cockpit generates the staging tables that need to be filled in a separate (remote) SAP HANA database. The customer IT Contact is responsible for subscribing to the SAP HANA Cloud service, provisioning the system and assigning the relevant permissions for access. The SAP HANA Cloud is a Database as a Service (DBaaS), which is free for up to 32 gigabytes of data. After this volume has been reached, there will be a cost for using the service.
Prerequisite Setup for Remote SAP HANA Database Schema
Either the customer or a member of the consulting team takes care of setting up the integration between the remote SAP HANA database and the target SAP S/4HANA Cloud system, which is documented in the set-up guide in Process Navigator: Data Migration to SAP S/4HANA from Staging (2Q2). After the integration is set up, consultants create migration projects and assign relevant migration object(s). The SAP S/4HANA Migration Cockpit generates the staging tables for these objects in the remote SAP HANA database through the integration.
On the customer side, someone with developer skills and access to the database tables that need to be migrated is responsible for extracting data from their legacy system(s) and loading into the remote SAP HANA database to fill the staging tables.
After the staging tables in the remote SAP HANA database are filled, the data is replicated to the target SAP S/4HANA Cloud system through the integration that has already been set up.
