Create & Maintain Target Sources
  • 26 Mar 2024
  • 5 Minutes to read
  • Contributors
  • Dark
    Light

Create & Maintain Target Sources

  • Dark
    Light

Article Summary

This topic relates to the following sections:

Prerequisites

Prior to assigning a Target Source Datasource and a table to the Target within a Dataset in Mappings, the Dataset is Imported to the Release with one or more Target tables assigned and active. The Target Source is added for a selected Target table and serves as the working table within the selected working database.

Overview

Target Sources represent the working tables and contain all mappings from legacy to target.  A Target may have multiple Target Sources assigned and mapped for updates to fields of the Working Table. The primary Target Source table may be pulled from either a System Datasource or from these other options:

  • Register a table from a Working Datasource as a primary source table in Mappings

    Create a working table in Mappings from a table from a Working Datasource from the above registration

  • Register a view from a Working Datasource as a primary source table in Mappings

    Create a working table in Mappings from a view from a Working Datasource from the above registration

Note

Additional information may be derived from other "secondary" tables, e.g., description or address data tables. The Primary Source Table is used as the working table for migration in Data Services and the working database environment.

From the Mappings multi-panel page, the legacy source system and its primary sources are maintained under the Sources panel.

null
Mappings: Sources

The Sources grid displays the following fields:

Heading

Description

Index

Sequence of the Target Sources. Value increases by factor of 10 for each new entry.

Name

The Name of the Snapshot Datasource.

Primary Table

Name of the Snapshot Datasource table.

Mapped

A count of the records in the Target table mapped / All.

Active

Toggle to mark this Snapshot Datasource as Active / Inactive.

Notifications

Toggle to activate the Email  Notifications sent to the person responsible for this Snapshot Datasource mapping.

Mapping

Opens the Mapping page for this selected Snapshot Datasource. 

ETL

The ETL  icon will display if this target source is set by Release as ETL Tool = Syniti Migrate.

Mapping Options Icon opens a drop down to a list of Options relevant to Mappings.'#'160; Refer to section Mapping'#'160;Options below for details of this column. 

Mapping Options

There are currently four options relevant to Mappings as shown below - Auto-Map Source to Target, Set not mapped to NOT USED, Build Status Complete, and Value Mappings.  The first three options are discussed within Mappings, while Value Mappings is a part of the Enrichment Template process, and is discussed in that section. 

Auto-Map Source to Target - This action maps as a Copy from all Source Fields with exact Name as all Target Fields.  It is very handy for Interfacing where data is moving from system to system for same tables. 

Set not mapped to NOT USED - Once mapping is complete, a click on this option updates the remaining NEW fields to set to NOT USED.

Build Status Complete - The user has option to set an fields not yet marked as Build Status = Complete to now be Complete.

Value Mappings - Mappings from legacy value to target value are available within a table to form XREF cross referenced data.  Refer to section Migrate > Value Mappings for details of this process. 

null
Mappings: Source: Options

Add a Target Source

Within the Sources panel, click the Add   icon to create a new Target Source link to the Target, primary source tables for mappings and launch the Target Source window. From this window, field values are entered as shown below. All required fields must be updated for the save to complete.

Note

Should the Release have an ETL Tool setting of SAP Data Services , then the section for SAP Data Services is visible. Otherwise, it is hidden.

Target Source Table fields for create a Target Source as listed:

Section

Field

Definition

Details

ZSource*

Select the Datasource from which a source table is added. (Required)

Details

Active

Toggle for status of the source for future-state design mapping and migration.

Note

Defaults field as Active.

Details

Index*

Sequence of the Tables. Value increased by factor of 10 for each new entry. (Required)

Details

Primary Source Table*

The primary table (or View) that contains the legacy data from which the data is mapped to a Target.  (Required)

Note

Additional information may be derived from other "secondary" tables, Ex: description or address data tables. The Primary Source Table is used as the working table for migration in Data Services and the working database environment.

Details

Legacy Table Rename

Stores the legacy table name for reference if not provided by legacy system.

Details

Working Table

Working table name that is built within the database.

Note

This field is automatically updated by the action of clicking

CREATE WORKING TABLE button.

Details

Development Area

The development area transforms legacy data into target- ready data. Used by automation to create the tables and reports in the correct database.

Details

CREATE WORKING TABLE

Click button to initiate a job queue to build the target and working tables for this dataset.

Audit

Various Fields

These are the system generated values for auditing the work.

Management

Developer

The primary developer responsible for the build of the ETL process and the load of the Dataset data.

Note

This role must be defined in Syniti Migrate prior to project load cycles.

Management

Alt Developer

The alternate developer which can assist with the Dataset ETL development if the primary developer is unavailable.

Note

This role must be defined in Syniti Migrate prior to project load cycles.

Management

Mapper

The user responsible for the creating and maintaining Source-Table-Field mappings.

Note

This role must be defined in Syniti Migrate prior to project load cycles.

Management

Send Notifications

Toggle to set the Source Notifications as active.

SAP Data Services

Working Datastore

The name of the Data Services Datastore which is connected to the Working Database. Used by the Data Services automation to build Jobs, Work Flows, and Data Flows against the correct Datastore.

SAP Data Services

Load XML

The unique internal record ID used by Migrationâ„¢ Deploy used to organize all related automation files.

SAP Data Services

Load File Name

The name of the XML load file

SAP Data Services

Load File Date

The date on which the XML Load File was created.

SAP Data Services

BUILD XML

Click button to initiate a job queue to build the XML Scripting for this target source. It also attempts to create the working table if one has not already been built.

Note

The Primary Source Table provides a drop-down list of available Tables or Views as they were added to the Snapshot Datasource.  An example of this scenario is shown below.

null
SQL Server: View of Table for Snapshot Datasource

The resulting mapping for this Target Source provides the columns from the Snapshot Datasource.  As part of this process, the Working Table is auto generated within the database. 

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

Note

Should the Primary Source Table not have a primary key, upon saving a validation message displays.  The user should click on CONTINUE SAVE button to save the added Target Source or CANCEL SAVE button to cancel this action.


Was this article helpful?