Syniti Migrate

Value Mappings

This topic is related to the following sections:

This page contains the following sections:

About Value Mapping

Within the Migrate > Mappings section of Syniti Migrate, the mapping of fields that contain a check table may require a mapping from old to new values. For Mapping Action of Xref, field contains a Check Table name. The mapping also contains the field Xref Table which stores the Legacy Value, the Target Value, and the Load Value. Each of these fields are important to the translation from legacy to target mappings. The Check Tables require Value Mappings from the Legacy value to the Target value stored within XTVALUEMAP table, and if the target value is complex (which may be a concatenated string of fields) then to the Load value stored in table LIST_TARGET_VALUE table in the MIGRATE database.

Prerequisites for Value Mapping

  • The Datasource MIGRATE must be setup properly to point to the MIGRATE Datasource Server. Refer to section Datasource Servers for details of setup for the Datasource MIGRATE.

  • The Datasource MIGRATE must be setup within Snapshot Management as a source datasource for SRCCONSTRUCT so that the snapshot of data within tables LIST_TARGET_VALUE and XTVALUEMAP are aligned. Refer to section Add a CONSTRUCT Snapshot Datasource for details of setup and use.

  • Once the Dataset fields have been Mapped and the results provide opportunity for Value Mappings (XREF mapping), the object should be setup in the ETL and processed to import from Source to Working table rows of data. The process of inserting from the Working table to XTVALUEMAP table the values for each zXREF field provides the tables and rows of data for use in this process. Either the SAP Data Services XML scripting builds these rules to run in Data Services, or the Syniti Migrate ETL adds rules for this action automatically. Refer to sections within Mapping for details on the ETL process and SAP Data Services XML scripting of rules and cross references.

  • Within Administer > Advanced > Value Mapping Config, the check table may be setup for a more complicated translation from legacy to load values by adding an Import Query. Refer to section Value Mapping Config for details of setup and refresh of check tables by Subject Area.

Users & Roles in Value Mappings

The Migration Team Developers and Mappers are responsible for managing Value Mappings as part of the Migration ETL process.

Role

Definition

Admin

The IT Lead or Team Administrator responsible for all Syniti Migrate ETL initial setup.

Developer

The user developing the ETL process in Syniti Migrate.

Mapper

The business user responsible for the data being imported and its correct usage within the field.

Working with Value Mapping

Access the Value Mappings page from three sections of the Syniti Migrate application -

  • Within Migrate > Mappings, through a link from within Mappings while viewing a Mapping for XREF type (Option 1)

  • Within Migrate > Mappings, click Options icon stored within the Source table row of Mappings (Option 2)

  • Direct access to all Value Mappings tables using pathway - Migrate > Value Mappings. (Option 3)

The user may select to process Value Mappings for a field from within the field mapping page. There are two places for access to this process - from within the XREF Mapping row, or from within the Options menu displayed on each row of the Sources panel.

Option 1 - Access to the Value Mappings page through a link from within Mappings while viewing a the mapping details for action type XREF or Rule Xref as shown below:

Mappings: Data Mapping Details for XREF: Value Mappings link

Option 2 - Access the Value Mappings page through the Mappings page. The user may work on Value Mappings for each Source system directly within the Migration Application. In the Sources panel, click Options  icon to display options for the selected Datasource Table.

Mappings: Sources

Click on Value Mappings option.

Mappings: Options: Value Mappings

The Value Mappings page displays. The left side contains filter fields to determine the Check table for maintenance. The right side contains the details of the selected Check table.

First, filter to the Check Table by entering values for the Check Table section. The Check Table panel displays the following Column Headers:

Header

Description
Target System* Select the Target Datasource for the Check Table. (Required)

ZSource*

Select the Source Datasource for the Check Table. (Required)

Check Table*

Select from drop down list the Check Table for this Object. (Required)

Once the Check table is selected, the page loads the values into the right side panel for Value Mappings. The count of total records is stored in the page bottom. This is an active page and rows may be Added, Edited, or Deleted.

Value Mappings: Display table data

The Search  icon may be used to filter data for specific values.

Value Mappings: Read Only display of Locked table rows

Option 3 - View the following page by navigating to Migrate > Value Mappings from the Syniti Migrate Homepage.

Value Mappings

Add Legacy Values for Translation

Legacy Values may be added manually by clicking the Add icon. The save is not active until a Legacy Value (Required field) has been entered.

Value Mappings: Add a Legacy Value

Field

Description
Legacy Value Enter a legacy system value not already in table.
Legacy Description Enter a description of the legacy value.
Target Value Select from the list a Target Value if known.
Suggested Value Provide a suggested value if the Target Value list does not provide the value needed.
Not Applicable Toggle used to mark the record as not relevant to translation.

Once all required fields have been added, the user either clicks SAVE  icon or they may click Cancel to exit without adding.

Edit Check Table Value Mappings

To edit a row of data, click the Target Value cell for the row.

Value Mappings: Edit a row of data

The Value Mappings panel displays the following Column Headers:

Header

Description

Changed

Provides a Change  icon for selecting multiple rows for edits.

Legacy Value

Source Datasource value for this check table.

Legacy Description

Source Datasource value description for this check table.

Target Value

Target Datasource value for this check table.

Suggested Value

Enter a text value to provide a suggested value.

Not Applicable

Toggle used to mark rows as not relevant for Value Mappings.
Created From Table that provided this value mapping row.

Created By

User ID who created the record.

Created On

Date the record is created.
Modified By User ID who modified the record.
Modified On Date the record is modified.

The user may select a value from the drop-down list a Target Value for each Legacy Value provided in the list. As each row is manually updated, the row changes to dark gray indicating that this row has been updated.

Value Mappings: Edit rows

Once editing of the rows of data is complete, the user either clicks SAVE  icon or they may click RESET  button to remove all of the added changes. The Save icon if clicked produces a window to state that the data was Saved Successfully. Click OK button to proceed.

NOTE:  Records changed to add Target Values and saved update the XTVALUEMAP table stored in the MIGRATE database. The conversion of data points to the SRCCONSTRUCT database to pull and update the target values to the fields in the working table. Make sure to Repopulate the SRCCONSTRUCT.XTVALUEMAP table prior to running the ETL to use the latest values updated in the XTVALUEMAP table.

Delete Check Table Value Mappings

 

There are a few ways to delete records no longer needed:

  • A single row may be deleted by clicking the Delete icon for the row.

  • To remove multiple records, select the row to highlight and click on the Delete Selected Rows icon in the header.

  • To remove all records that have no Target Values, click the Delete Empty Values button in the header.

A message displays stating that the delete is successful. The list is updated for the total remaining rows.

Value Mappings: Delete Rows

Suggested Value

This field is used to supply a value for the Target Value where that Target Value is missing in the drop down list. The Suggested Value field stores the temporary value so that mapping and conversion may proceed until the target system is set with the same value for use as a Target Value

Value Mappings: Add a Suggested Value

An entry may be added to the Suggested Value field that is set as the Target Value during the Update rule for the XREF mapping. Notice that the Reset and Save icons are present due to the change to a row. Click Save icon to complete.

Value Mappings: Add a Suggested Value

Once Complete, Save the rows of data as usual. The Suggested Value displays.

Value Mappings: Save Data

Bulk Editing

Should there be a need to update multiple rows of data with the same values, the user may click on the Check box  icon at the Header level to mark all rows as selected.

NOTE:  As a option, the user may also click on multiple check box  icons to select some but not all rows.

Value Mappings: Bulk Edit Select Rows

They can then update all rows at one time, and save them. 

Value Mappings: Bulk Edit: Select target value

The modified rows display with updated values for the field edited with Bulk Edit. Click SAVE  icon in window.

NOTE:  The selected count displays at page bottom.

NOTE:  Records changed to add Target Values and saved update the XTVALUEMAP table stored in the MIGRATE database. The conversion of data points to the SRCCONSTRUCT database to pull and update the target values to the fields in the working table. Make sure to Repopulate the SRCCONSTRUCT.XTVALUEMAP table prior to running the ETL to use the latest values updated in the XTVALUEMAP table.

NOTE:  Should the updated and saved values need to be reversed, click the RESET button to revert back to original values.

Value Mappings: Bulk Edit: Save selected value

Reset Button

Once a row of data has been modified, the RESET button displays as active. Should the user make multiple changes and decide they are not necessary, click the RESET button to default back to the saved values.

Value Mappings: Reset

Value Mappings: Reset: Values Reset