• 25 Mar 2024
  • 3 Minutes to read
  • Contributors
  • Dark
  • PDF


  • Dark
  • PDF

Article summary

This topic contains the following sections:

About Datasources

Although the Datasources and Datasource Server connections are stored within Syniti Data Catalog and Syniti Replicate, Migrate tracks and store the tables and columns of these datasources for use in mapping fields and reporting.

This section of the system provides a wizard to assist in building the connections to the Syniti Replicate system to pull in metadata based upon the type of build. These connections include:

  • To legacy data from an ERP system, such as Baan, SAP HANA DB, JDE to pull source data for migration.

  • From an SAP ECC or HANA S4H system to pull target metadata for an object to be migrated to that system.

  • For the working tables as a connection to build out the pull through views.

There may be multiple legacy systems used in the effort to build the future-state target system. This could include SAP systems, legacy purchasing/sales/inventory systems, or cleansed data from Construct (Excel or database tables/fields).

Prerequisites to Datasources

  • Each project requires datasources for the source data, target data, and the database system. These are setup within Syniti Data Catalog system and then linked to the same Datasources added in this section of the Syniti Migrate system.

  • Datasource Servers may be required - these are set up for the Working database and the Syniti Construct servers.

Users and Roles in Datasources

The IT Lead or Project Manager set up the Datasources using the Role of Admin. Developers have access to view the Datasources as it applies to the migration of data, but in a Display mode.




The IT Lead or Team Administrator responsible for all Dataset Design initial setup


The user developing the ETL process in Syniti Migrate


Administrator has display/change/delete access while Developer has only display access.

Rules and Tasks specific for Using a Client's Database

Refer to the section The Data Migration Process for details of working in a client's database servers. In some cases, the project uses SAP HANA DB or Oracle DB or a Client held SQL Server for the working database. The Syniti Migrate application is stored in SQL Server, however, the data may reside in a different Database. The Data Migration Process provides sections for :

Working in Datasources

View the following page by navigating to Catalog > Datasources from the Syniti Migrate Homepage. This page includes three functional panels of Datasource in Syniti Migration.

This multi-panel page displays the type of Datasource in the Left side panel; the Tables of the selected Datasource in the upper right panel; and the Columns of the Table selected in the lower right panel. This way the user may view multiple data for the same selected connection.

Datasources may be filtered using the Show* field as shown below.  The user may select to view Hierarchy (shows all levels) , Applications, Interfaces, or Datasources using this filter field. 


Datasources multi-panel page

When the page is filtered by Hierarchy, the Left side panel displays as a hierarchy with these levels:

  1. Application

  2. Instance

  3. Datasource

Each of the levels contain details and a list of tables and columns.  The Datasources may be tracked and documented much like any other client information. 

Within Datasources section the grid displays the following columns:




The name for the of the level Datasources (can be an Application, Instance, or Datasource)


The description of the level Datasources

Connection Status

Provides the Connection Status for the Datasource (not applicable for Application or Instance)


Toggle for status of the row data.


Field defaults as Active (not applicable for the Application or Instance). 


Server Name as identified in the Connection section of the Datasource (not applicable for the Application or Instance)


(not applicable for the Application or Instance)


From within the grid, if the user clicks to test a datasource that does not have any server information, the system prompts the user to enter the connection info, and the validation status is set to unknown.  This continues until the datasource server info is configured.

Was this article helpful?


Eddy, a generative AI, facilitating knowledge discovery through conversational intelligence