--- title: "Dataset Design" slug: "dataset-design" status: "update" updated: 2025-05-06T05:18:38Z published: 2025-05-06T05:18:38Z canonical: "skthelp.syniti.com/dataset-design" --- > ## Documentation Index > Fetch the complete documentation index at: https://skthelp.syniti.com/llms.txt > Use this file to discover all available pages before exploring further. # Dataset Design This topic contains the following sections: - [Create & Maintain Subject Areas](/v1/docs/subject-areas) - [Create & Maintain Datasets](/v1/docs/create-maintain-datasets) - [Import / Export Dataset](/v1/docs/import-export-dataset) - [Maintain Tables and Fields tab](/v1/docs/maintain-tables-and-fields-tab) - [Maintain Data Elements tab](/v1/docs/maintain-data-elements-tab) - [Maintain Migration tab](/v1/docs/maintain-migration-tab) - [Stakeholder Details](/v1/docs/stakeholder-details) - [Attribute Details](/v1/docs/attribute-details) - [Working Databases in Migrate](https://skthelp.syniti.com/docs/introduction-to-syniti-migrate#working-databases-in-migrate) ## About Dataset Design The Dataset Design process captures the business process design including relevant tables and fields for a dataset. It is the To-Be state of the migration as well as the hub for governance of the processes and policies. The information gathered and stored in Dataset Design provides the Target side of the Mapping process. The Subject Areas are similar to a process within a company and they group the Datasets together that together form this process. The business process design includes all the relevant business objects, i.e., business partners, articles, purchase orders, etc., as they relate to one another within the business process. At each step of the process, there is usually 1 or more datasets that encompasses data needed to let a company process advance. ## Prerequisites Before working in Dataset Design, several steps must be completed within Syniti Migrate to enable the availability of the metadata for design. These steps include: - Create [System Datasources](/v1/docs/adding-editing-datasources) and [Snapshot Datasources](/v1/docs/snapshot-management#add-a-snapshot-datasource) linked to active Connection Agents for use in Dataset Design. - [Import Metadata](/v1/docs/import-metadata) from the target system. - Create the [Subject Area](/v1/docs/subject-areas). ## Users & Roles in Dataset Design The Design Team is responsible for determining the relevant functional areas for data migration and data governance. There are additional roles within Dataset Design that must be defined for both the business users and consultants. > [!NOTE] > Note > > Within Dataset Design, Security access for Datasets and Subject Areas may be restricted to certain roles (Ex: Admin only access). This is considered Child Control within Security. | Role | Definition | | --- | --- | | Admin | The IT Lead or Team Administrator responsible for all Dataset Design initial setup | | Dataset Designer | The developer responsible for control of the data in terms of governance | | Mapper | The business user responsible for the data being imported and its correct usage within the field | | Design Lead | The user that is responsible for the design and functionality of the target Dataset | | Developer | The user developing the ETL process in Syniti Migrate | ## Working in Dataset Design View the following page by navigating to **Catalog > Dataset Design** from the Syniti Migrate Homepage to launch the Dataset Design multi-panel page. This page includes two main functional panels of Dataset Design - Subject Areas and Datasets. | Panel | Description | | --- | --- | | Subject Areas | The business functional area under which the Dataset business objects are managed. Ex: Article Master or Procure-To-Pay | | Datasets | Datasets are the objects to be loaded and governed. | > [!NOTE] > Note > > The counts of each grid panel are displayed within parenthesis next to the panel titles. ![](https://cdn.document360.io/ca09b4e9-1857-4c63-9f0e-1f25f166f447/Images/Documentation/3c1e5ade-1e7b-4934-8a25-b90d6dfe479a.png?sv=2026-02-06&spr=https&st=2026-11-17T19%3A15%3A21Z&se=2026-11-17T20%3A15%3A21Z&sr=b&sp=r&sig=iKu9WuFuPAsJSutbHZ%2BpU%2Fi35ffKf%2BmJI42bUoEV8yI%3D) Dataset Design: Multi-Panel page ### Sliding Divider Bar This page is set with a Sliding Divider Bar - the divider may be moved from side to side to give more room to a panel. Refer to [Migration User Interface > Menu Structure](/v1/docs/menu-structure) for details of this benefit. ### Rules and Tasks specific for Using a Database other than the Migration SQL Server Refer to the section The Data Migration Process for details of working in a database that is not same as the Migration SQL Server. In some cases, the project uses SAP HANA DB or may even enforce using a different Client held SQL Server for the [working database](https://skthelp.syniti.com/docs/introduction-to-syniti-migrate#working-databases-in-migrate). For example, Syniti Migrate is stored in SQL Server; however, the data may reside in a different Database. The Data Migration Process provides sections for: - [Migration Using SAP HANA DB as the Database](/v1/docs/migration-using-sap-hana-db-as-the-database) - [Migration Using a 2nd SQL Server as the Database](/v1/docs/migration-using-a-2nd-sql-server-as-the-database) ## Subsequent Steps Refer to section [Create & Maintain Subject Areas](/v1/docs/subject-areas) for the next set of steps in this process.