Create & Maintain Datasets

This topic contains the following sections:

• Maintain Data Elements Tab

• Bulk Edit of Existing Data Elements

• Maintain Tables and Fields Tab

• Maintain Migration

• Import / Export Datasets

About Datasets

Within the Dataset Design section of Syniti Migrate, the objects are defined by Subject Area and Dataset. This information is imported to Syniti Migrate from Knowledge Platform.

Prerequisites

• The Datasources should be defined for the objects prior to creating a dataset. Datasource is a required field and it locks and does not allow for edit after the dataset has been imported into a Mapping. Refer to section Catalog > Datasources for details of defining Datasources.

• The Subject Area must be created in order to create a Dataset. Many Datasets can be assigned to a Subject Area.

Dataset Objects

View the following page by navigating to Catalog > Dataset Design from Syniti Migrate Homepage.

On the multiple panel Dataset Design page, Subject Areas are stored in the left panel and Datasets are stored in the right panel. The Dataset panel displays a list of Datasets within the highlighted Subject Area.

Note

The count of rows for the panel is displayed within parenthesis next to the panel title.

The Dataset grid displays the following fields:

Note

The Prefix is vital to the build of XML and build of the conversion as it shortens the name - it cannot contain special characters or spaces.

Sliding Divider Bar

Throughout the Migration system, pages provide the ability to move the divider bar between panels for a Vertical break or Horizontal break. As one example of this benefit, Dataset Design provides the user ability to move or slide the vertical page break from left to right and back. Refer to section Migration User Interface > Menu Structure for more details of this benefit.

Add a Dataset

On the Dataset panel, click the Add   icon to create a Dataset and launch the Edit Dataset Details window.

This is a multiple panel page where the left side panel stores the Dataset Detail information including but not limited to Name, Target System, Complexity, Attributes, Stakeholders, and Review Status. The right side of this multiple panel page contains associated Table and Field or Data Element details. The Dataset information is built within the Syniti Knowledge Platform and then imported into this section for use in the migration of data from legacy to target systems.

Within the Dataset Details panel, field values may be entered as shown below for the details of the Dataset. Fields within section Details remain static in nature. The remaining sections of Dataset Details panel alters based upon configuration of these sections including - Data Classification, Additional Details, Technical Details, Design Details, and Content Review. The section for Audit maintains field values automatically for use in metrics and reporting.

The field Dataset Type is a configurable field that determines the use of this Dataset (Ex: Report or Table) and the fields that are relevant with formatting. Once this field is updated, the remaining fields on the page updates to reflect the relevancy of the Dataset Type. The fields are set as Display, Optional, Required, or Hidden based upon this setting.

Note

The Dataset Type values are configured within Administer. View section for Adminster > Advanced > Dataset Types for more details.

Field definitions for Dataset Details:

When finished with edits, click the Save  icon to complete.

The Is Migration Specific Toggle - Visible within the Subject Area Details, Dataset Details and Data Element Details of the Syniti Migrate system. These toggles mark the object type as active for internal Migration Project team use such as Central Wave or Relevancy Targets. They are toggled as active to be excluded from the overall Migrate metrics calculations and to appear as if they are not "In Scope" objects for the Project.

Note

The Migration Prefix is vital to the build of XML and build of the conversion as it shortens the name - it cannot contain special characters or spaces. The Migration Prefix must be unique throughout the system. If the user enters a duplicate value, an error message displays during the save as shown below. This field is accessible to Developers or Admin roles.

Edit a Dataset

Once a dataset has been added to a Subject Area, it may be edited. Click the Edit icon for the dataset from within the Dataset Design page to modify the fields. A few fields like the Datasource field are locked and cannot be altered once the Dataset is created. To add Tables or Columns to an existing dataset refer to section Maintain Tables and Fields. When finished with edits, click the Save  icon to complete.

Delete a Dataset

Although the Subject Area details provides a Delete button, it is important to only delete a table that has not yet been mapped. The Active toggle marks the table as Inactive and prevent users from adding to the Mappings. This way history of this table may be stored in the system.

However, in the event that a Dataset Table was added in error, it may be removed by clicking the Delete icon for the table in panel Tables in the Dataset Details page. A Validation Warning message displays to warn that interfaces are deleted. This indicates that all Mappings, all Reports, all ETL tasks are deleted from the system should the user click on CONTINUE DELETE button. This action can not be reversed, so it should be used only in situations where the Dataset should not have been added.

Dataset Types and Use

Within the Dataset Design, Datasets are used to identify various different types of data. The Dataset Types are configurable within Administer > Advanced > Dataset Types. Examples are provided below:

• A Datalake (centralized repository that allows you to store all your structured and unstructured data at any scale) stores data that may be part of the active client system.

• A Report stores data elements both from the target system as well as derived data elements to document and build a report.

• An Interface stores the data elements used to transfer information from one system to another.

• A User Interface covers the process of migration of data from legacy to target systems.

• A Procedure may be used to document the steps of a procedure used in the daily processing of transactions.

• A Transaction documents the specific use and data within a specific transaction of business use.

Note

Dataset Types are configurable and have specific attributes documenting an interface - an API , map data into this.

Tier Field

See below for field definitions for the Tier Pick list:

** Datasource field

The system from which the active objects are mapped. The system is defined in Migration as a Datasource and maybe set as a Source or Target System on the Datasource Details page Ex: ECC, S4H, MDG. The Datasource is not be the Snapshot Datasource (tgtECC, tgtS4H), but instead the Source or Target Datasource (ECC, S4H).

Note

The Datasource field may only be changed prior to importing tables/fields. Once there are active tables and data elements, this field changes to Display only. Should the situation warrant changing the Datasource after the Dataset is imported to a Mapping Release, it would be wise to delete the entire Dataset and start over. Therefore, the user should determine a valid system and build that Datasource within Migration prior to any Mapping of source data.

When finished with edits, click the Save icon to complete.

At this point, the right-side panel becomes active and allows for adding new tables and fields to the dataset.

Central Wave Datasets

Central Wave depends on creating a Subject Area and Datasets specific to "Central Relevancy". These are Migration only objects similar to the Migration Data Elements that are mapped to determine the relevancy of objects like Sales Orders or Purchase Orders. These are not relevant to the Dataset Designer (if they are the SI who’s concern is for the objects loading data).

These Central Wave Datasets do not display in Dataset Design like the normal datasets. The Migration toggle assists with Security to make them hidden from Designers who do not need this information. These Migration toggled Datasets are also excluded from all Metric calculations.

Add Supportive Information for a Dataset

The left side of the Dataset Details page contains the Dataset Detail Fields. These fields are supportive of the Dataset Design, usage, classification, and review. Each section of this panel stores valuable information. At the header of this left side panel there are quick use icons as shown below:

Icon	Name	Use
	Subscribe	This icon adds the user name to the Subscribe list for email notifications when there are changes made to this object.
	Save	The Save icon saves the current entries.
	Cancel	The Cancel icon leaves the current page without saving changed data.
	Help	The Help icon links to the page in Syniti help text to provide detailed explanation of this section and use.
	Options	This icon opens to provide user access to View History, Data Definition Report , Export Dataset, and Import Dataset- See individual options below for details of each.
	Link	This icon opens to a page within Syniti Migrate that supports the details of the field value. The Stakeholder fields contain active or inactive links to the details for that Stakeholder.

Additional Options Icon

Within this icon of the Dataset there are four options:  Data Definition Report, View History, Export Dataset, and Import Dataset. This is a quick step process that allows the user to perform tasks without having to modify using the Edit process.

Data Definition Report - Provides a list of the active data elements by table and index. Refer to section Data Definition Report below for details.

View History - This option provides the history of changes for the dataset. Refer to section View History of Changes below for details.

Export Dataset - Allows for export to a local file all dataset details for use in development. Refer to Import / Export Dataset and Mappings below for details.

Import Dataset - Allows for import from a local file all dataset details for use in development. Refer to Import / Export Dataset and Mappings below for details.

Subscribing to a Dataset

At any time after the Dataset is added and saved, a user may Subscribe to the Dataset for notifications. The Subscribe icons add the user name to the Subscribe list for email notifications when there are changes made to this object. As the user clicks on the bell icon, it changes from grayed out to highlighted and a message displays "Subscription Added."

Icon	Name	Use
	UN -Subscribed	This icon adds the user name to the Subscribe list for email notifications when there are changes made to this object.
	Subscribed	This icon shows that the user is subscribed to this Dataset for email notifications of changes.

Note

Subscribing does not require that the Dataset be changed or SAVED. The action of clicking on the Bell updates the status to/from Subscribed.

As changes are made to the Dataset Details (Left Vertical list of fields) in the Object, notification emails forward to all subscribers. This process only takes place when the Dataset's Review Status has been set to either Complete or Re-Review.

Also, if the Dataset is deleted, independent of the Review Status, a notification is sent to all subscribers.

Note

Email notifications are sent from skp-no-reply@syniti.com. To prevent notifications from going to a spam folder, add skp-no-reply@syniti.com to the contact list.

Note

Emails are sent to the email address set up on the user's associated Employee record. Emails are queued, and then sent once per minute.

The email looks similar to the example shown below:

Data Definition Report

Provided below is an example of a Data Definition Report. The user would click Data Definition Report  stored within the Options icon in the header panel to open this window and provide details of the changes made.

Note

This report may be downloaded as a CSV file to a local drive by a click on the Hamburger  icon to select " Export all data as csv". The Columns may be reset to default by a click on Reset Columns.

View History of Changes

Provided below is an example of a Object History list. The user would click View History  stored within the Options icon in the header panel to open this page and provide details of the history of changes made to this Dataset.

Note

The Download icon will produce a file on the local drive with details of this table data. The Search icon will provide filtering of data.

Note

As with any page grid of data, on the right upper corner, click on the Hamburger page Details icon to view the options for field in or out, sorting, and Export all data as csv. This is extremely handy for situations where the data is fluid and changes or when there are many records that are hard to review in the small window provided for the list.

Import / Export Dataset and Mappings

During a multi-release project, a Dataset may be used multiple times within multiple Migration systems, and therefore it becomes necessary to export the data into a file and then import the same Dataset information for use in another Migration system. It exports only the setup of the Dataset to include the Tables, Fields, and the Data Element details. The import of Dataset data is inserted to an existing Subject Area within the new system or new release of same system. This process provides a shell for many large objects as well as providing a more accurate way to repeat an objects migration over many releases.

Export Dataset and Import Dataset reside within the Options icon in the header bar.

Refer to section Catalog > Dataset Design > Create and Maintain Datasets > Import / Export Dataset and Mappings for details of this process.

Data Element Priority using Drag and Drop

The Dataset Design team must take the time to properly order the data elements in the Dataset Design pages. Elements should be arranged in the same order they appear on the user Interface pages used to create or maintain the records in the Target System. The order of the elements defines the order in which the fields appear in Mapping workshops, in the Validation Reports, and across all the pages in Migration.

It can be difficult to Map and Validate a dataset which contains the fields in a random order. For example, the address fields should be grouped and prioritized so that an address is easy to validate. Having the address fields out of order and intermingled with all the other Customer fields makes it very difficult to work overtime. This is one of the most important aspects of a good Dataset Design, and extraordinary care should be spent to make it right from the beginning of the project.

Note

Easily edit the order of Data Elements in the multi-panel view by selecting(highlighting) the Data Element and dragging and dropping into the desired order. This automatically adjusts the index of the Data Element(s) reordered. If any sort order has been enabled for a column, the drag and drop functionality is disabled. Removing the sort order enables drag and drop functionality again.

Dataset Objects 

On the right side of the Dataset Design Details page, there are three tabs to pages that add and maintain the supportive information of this object (Data Elements, Tables and Fields, Migration). These pages are used as follows:

Depending upon the Security role of the user, one or more of these panel options are available for display or edit.