--- title: "Mappings" slug: "mappings" updated: 2024-11-14T13:04:44Z published: 2024-11-14T13:04:44Z canonical: "skthelp.syniti.com/mappings" --- > ## 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. # Mappings This topic contains the following sections: - [Importing Datasets into Mapping](/v1/docs/importing-datasets-into-mapping) - [Create Target Tables](/v1/docs/create-target-tables) - [Build XML Scripting for Dataset](/v1/docs/build-xml-scripting-for-dataset) - [Create & Maintain Target Sources](/v1/docs/build-xml-scripting-for-dataset) - [Mapping the Fields of a Datasource](/v1/docs/mapping-the-fields-of-a-datasource) - [Create Working Tables](/v1/docs/create-working-tables) - [Create Reports](/v1/docs/create-reports) - [Value Mappings by Object](/v1/docs/value-mappings) - [Execution of the ETL Jobs](/v1/docs/execution-of-the- Project Setup](/v1/docs/project-setup) for details of the steps. ![](https://cdn.document360.io/ca09b4e9-1857-4c63-9f0e-1f25f166f447/Images/Documentation/b9e0a995-4ded-40a9-8bea-082568309c2b.png?sv=2026-02-06&spr=https&st=2026-11-17T19%3A21%3A11Z&se=2026-11-17T20%3A21%3A11Z&sr=b&sp=r&sig=fR6q7k6h8mqDewGcrQxfAbuV9fAhXBDDuWJr%2BnJ5Yrs%3D) Migrate: Project Setup: Edit Release: Set the ETL Tool Within [Administer > Setup > Parameters](/v1/docs/parameters), a default ETL Tool is assigned as well. However, each Release overrides this default for the ETL Tool selection. ![](https://cdn.document360.io/ca09b4e9-1857-4c63-9f0e-1f25f166f447/Images/Documentation/dc015120-c686-45a8-833e-e711a9fc8a67.png?sv=2026-02-06&spr=https&st=2026-11-17T19%3A21%3A11Z&se=2026-11-17T20%3A21%3A11Z&sr=b&sp=r&sig=RHuJRQALEKEU64YCvEA4g109DlNNc8SZGOiupL8WLRw%3D) Parameters: ETL Tool In this image of the Mappings page, notice that the **ETL** ![](https://cdn.document360.io/ca09b4e9-1857-4c63-9f0e-1f25f166f447/Images/Documentation/079743fe-6687-4730-9c0d-8a84732804f8.png?sv=2026-02-06&spr=https&st=2026-11-17T19%3A21%3A11Z&se=2026-11-17T20%3A21%3A11Z&sr=b&sp=r&sig=OgKkIQ5jzS7e0k5w8TjAJWEy9zmL2hDTFKGx98jLe6Y%3D) icon displays within each section of the Mappings page. It contains the tasks and jobqueue steps of that section, and may be run through each section or at the Release level for all objects contained and actively setup. Refer to section [Migrate > ETL Jobs](/v1/docs/etl-jobs-details) for more details of this process. Should the project select the **ETL Tool** as SAP Data Services, these ETL icons are not visible on Mappings page. ![](https://cdn.document360.io/ca09b4e9-1857-4c63-9f0e-1f25f166f447/Images/Documentation/7d4160c0-4e1a-42e1-b209-e13f1a19e571.png?sv=2026-02-06&spr=https&st=2026-11-17T19%3A21%3A11Z&se=2026-11-17T20%3A21%3A11Z&sr=b&sp=r&sig=IydEG%2Fk5HyD5XByYFffJA5Xx%2BJMF%2Bldobxg9%2B4OeKJk%3D) Mappings: ETL Tool: Syniti Migrate ## Working in Mappings View the following page by navigating to **Migrate > Mappings** from the Syniti Migrate Homepage. > [!NOTE] > Note > > If the Release has been assigned ETL Tool as **Syniti Migrate** within pathway **Migrate > Project Setup**, then this page displays additional columns for ETL and allow for processing conversion of data for the Release / Dataset / Target / Source from within the Syniti Migrate system. ![](https://cdn.document360.io/ca09b4e9-1857-4c63-9f0e-1f25f166f447/Images/Documentation/3714b59c-d9e8-4b1b-9ace-251a60a64422.png?sv=2026-02-06&spr=https&st=2026-11-17T19%3A21%3A11Z&se=2026-11-17T20%3A21%3A11Z&sr=b&sp=r&sig=AASkQMbFIqM5QWbBdbUN8RpdvhoEp67FwG4CRsbEWUw%3D) Mappings This page includes four panels - Releases, Datasets, Targets and Sources. | Panel | Description | | --- | --- | | Releases | Project Release created during the Project Setup process. See [Migrate > Project Setup](/v1/docs/project-setup) for details. | | Datasets | Datasets that are relevant to the Release - Subject Area created in Dataset Design process. See [Catalog > Dataset Design > Create & Maintain Datasets](/v1/docs/create-maintain-datasets) for details. | | Targets | Target tables created during the Dataset Design process. These tables include mapping opportunities defined in Dataset Design process as well. See [Catalog > Dataset Design > Maintain Tables and Fields](/v1/docs/maintain-tables-and-fields-tab) for details. | | Sources | Source system tables imported during the Datasource creation process. See [Catalog > Datasources](/v1/docs/datasources) for details. | As an example of this process: The Releases and Datasets Panels determine the scope of the release. For example, "Release One" of a project may include on master data Datasets, "Articles" and "Business Partners", while "Release Two" may include "Inventory" and "Pricing" Datasets. Dataset are imported individually base on the scope and requirements of the Project Release. The Tables and Source panels determine how each dataset is mapped from one or more legacy sources. Source tables are added and associated to Target Tables for enabling the field mappings for those active target fields. Refer to section [Migrate > Copy a Release](/v1/docs/copy-a-release) for details of outcome of this process on the Mapping process. ## Active VS Inactive ### Marking Dataset as Not Active The Mappings page performs as a Hierarchy to the mapping process. If the user should mark a Dataset as Inactive using the toggle for Active switch, the downstream activity is hidden. In the example below, Dataset has been marked as not Active, and all Targets and Target Sources are now hidden from view. If the user changes toggle back to Active for a Dataset, then all downstream activity is again be visible. > [!NOTE] > Note > > A warning message displays once toggle is changed ' **Change the Dataset to Inactive?**' User must click on **OK** to proceed. ![](https://cdn.document360.io/ca09b4e9-1857-4c63-9f0e-1f25f166f447/Images/Documentation/cf4f212c-023e-4ef5-8710-50877d106542.png?sv=2026-02-06&spr=https&st=2026-11-17T19%3A21%3A11Z&se=2026-11-17T20%3A21%3A11Z&sr=b&sp=r&sig=wKkOpBEJk6dPglNhJykGej8hnACKTEjbI6t9otP%2FHN0%3D) Mappings: Dataset toggle set to not Active ### Mark a Target Not Active If the user should mark a Target as Inactive using the toggle for Active switch, the downstream activity becomes hidden. In the example below, Target has been marked as not Active, and all Target Sources are now hidden from view. If the user changes toggle back to Active for a Target, then all downstream activity is again visible. > [!NOTE] > Note > > A warning message displays once toggle is changed ' **Change the Target to Inactive?**' User must click **OK** to proceed, or **CANCEL** to quit the process. ![](https://cdn.document360.io/ca09b4e9-1857-4c63-9f0e-1f25f166f447/Images/Documentation/2de6eae7-d4d7-4dc5-8df3-eaf6a4e886ae.png?sv=2026-02-06&spr=https&st=2026-11-17T19%3A21%3A11Z&se=2026-11-17T20%3A21%3A11Z&sr=b&sp=r&sig=9hXvLgYGuD4sPYKLZJtQuS%2FlXvTG7ShAEIlSuofMqk8%3D) Mappings: Target toggle set to not Active ### Mark a Target Source Not Active If the user should mark a Target Source as Inactive using the toggle for Active switch, the access for ETL and Mapping is hidden. The two icons that provide links to the pages become inactive for use. In the example below, Target Source has been marked as not Active, and both the Mapping icon and the ETL icon are now inactive. If the user changes toggle back to Active for a Target, then this activity is again accessible. > [!NOTE] > Note > > A warning message displays once toggle is changed ' **Change the Source to Inactive?**' User must click **OK** to proceed. ![](https://cdn.document360.io/ca09b4e9-1857-4c63-9f0e-1f25f166f447/Images/Documentation/d9182a4b-1e76-49c0-9035-efedec324979.png?sv=2026-02-06&spr=https&st=2026-11-17T19%3A21%3A11Z&se=2026-11-17T20%3A21%3A11Z&sr=b&sp=r&sig=u9zhIo3wT8Nw3Fkhl2ftukI2rCAGzV6onGonONz%2BR8w%3D) Mappings: Target Source toggle set to not Active Refer to section [Importing Datasets into Mapping](/v1/docs/importing-datasets-into-mapping) for subsequent steps in this process.