3751184 - Import of SQL server views into replication flow fails without any further information

• Import of views from a Microsoft SQL Server source into a replication flow fails during creation or deployment.
• Views can be selected, but the import ends with status "Failed".
• Error code observed in the HAR trace: "getMetadataReplicationFlowFailed".
• Error message observed in trace/logs: "Error: No schema found for ".

SAP Datasphere

1. In Data Builder, create a new replication flow.
2. Select a Microsoft SQL Server connection as the source.
3. Select the container/schema
4. Try to add one or more SQL Server views as source objects.
5. After selecting the view(s), the import fails with status "Failed" and without any further information.

The required database schema for the replication user is missing in the Microsoft SQL Server source, leading to the error "No schema found" when retrieving metadata for views.

1. Verify the database user used by the Datasphere connection to the Microsoft SQL Server source.
2. In the SQL Server, ensure that a schema exists with the exact same name as this database user.
3. If it does not exist, create the required user and a dedicated schema owned by that user with the following commands:
      -  CREATE USER <ds_rep_user> WITH PASSWORD = '<Strong!Password>';
      -  CREATE SCHEMA <ds_rep_user> AUTHORIZATION <ds_rep_user>;
4. Grant the required privileges to the replication user on this schema so it can create and manage replication objects (for example, shadow tables, procedures, sequences).
5. Revalidate the Datasphere connection, then retry adding the SQL Server view(s) to the replication flow and deploy.

• Refer to: Prepare connectivity to Microsoft SQL Server
• Refer to: Importing tables and views from sources

datasphere, replication flow, sql server, mssql, view import failed, getMetadataReplicationFlowFailed, no schema found, har trace, delta loading, user schema, replication user, replication objects, shadow tables, data builder , KBA , DS-DI-RF-UI , Replication Flow editor, monitoring and deployment , Problem