Value Mapping Config

This topic is related to the following sections:

• Value Mappings

• Check Table Values

About Value Mapping Config

Check Tables validate and control values entered into fields, primarily using SAP as the target system. Within the mapping exercise, target fields are assigned as a mapping type of XREF (Cross reference) and a Check Table is assigned for the translation of field values from source to target. The Check Table values are imported as part of the Target Datasource import process.

During conversion, the rules insert new values from source to the Value Mapping table and update the target values in the conversion table based upon the value mapping translations set by the Client users.

The team maps from source values to the check table target values in a Value Mapping exercise to produce valid translation. But, in some cases, the target values do not exist within the Target Datasource, or the Target Check Table does not yet exist within the Target Datasource. This section provides the user with ability to create Check Tables and add fields within Check Tables for use in the Value Mapping process.

Once the Target Datasource becomes synced with the values in the Check Table, these manually configured values change status to system configured values. Users may Insert, Update, Delete, or mark inactive the values in these Check Tables.

Prerequisites to Value Mapping Config

These steps must be completed prior to working in Value Mapping Config:

• Datasets contain fields designated as active Data Elements. Data Elements may provide Check Tables for fields and the Dataset is assigned to a Target System. Refer to section Catalog  > Dataset Design for more details of this process.

• Within Mappings section the fields defined as Mapping Action Xref or Rule Xref have mapping status of Complete and have Check Table values. Refer to section Mapping Fields of a Datasource for details of this process.

• The System Views are views of the Check Tables stored within the Working Database of the object. These views must be defined prior to working in Value Mapping Config. Refer to section Migrate > System Views for more details of this process.

• Snapshot Datasources are in place that point to the Source Datasource where the Check Table data is stored. These Datasources provide the DATASOURCE_ID. Refer to section Migrate > Snapshot Management for more details of this process.

Note

In the case where SQL Server is not the working database (Ex: Oracle or HANA DB), a Snapshot Datasource must be built within the SQL Server db for this process to work. Also, the local Snapshot must contain the required DD Tables including DD02L, DD02T, DD03L, DD04T, DD05P, and DD08L.

** Refer to section  The Data Migration Process > Migration Using SAP HANA DB as the Database for details on HANA DB for the working database.

** Refer to section  The Data Migration Process > Migration Using Oracle as the Database for details on Oracle DB for the working database.

The Value Mapping Config page is empty until the team begins the process of importing Datasets to the Releases within Mappings. As the system imports the Dataset to build out the Mapping page, a procedure runs to build a Datasource value within Value Mappings Config should it not already exist, and then add each of the Check tables reflected within the Dataset target tables.

Users & Roles in Value Mapping Config 

The Data Migration Project Lead, Deployment IT lead, or the Migration Team Developers are responsible for managing the Value Mapping Config values.

Working in Value Mappings Config

View the following page by navigating to Administer > Advanced > Value Mapping Config from the Syniti Migrate Homepage. This page contains two panels - Datasources, and Check Tables associated with each Datasource. The Value Mapping relevant Datasources are determined by the imported Mapping Datasets containing a check table for the field. Since these Check Tables are used in Value Mapping, they become relevant as the Dataset fields are mapped within the mapping effort.

Note

The check tables that are not used in Value Mapping (Ex: CEPC, KNA1, MARA) are all to be marked as Active For Value Mapping = Inactive so that their values are not copied into the Value Mapping table. This streamlines the table content as these tables are transactional and not used for Value Map process.

Note

If the Datasource or Tables are not displaying as expected after a Dataset Import to Mapping, make sure to check the DEBUG LOG as they may have failed to import to this process due to missing Snapshot Managed Datasource or Tables.

The left panel contains each Datasource while the right panel displays each Check Table associated with the selected Datasource.

Note

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

Within the Datasources panel, there is a list of datasources that have been added. The Datsources grid displays the following:

The right panel displays each Check Table associated with the selected Datasource. The Check Tables grid displays the following:

Note

The Active for Value Mapping flag is used when the table is LARGE and not worthy of the standard Value Mapping process. This field is not directly tied to same field in Datasource table details. When this flag is set to not active, the result removes all value mapping for this table. So, within Mappings pages, the Value Mapping link is hidden and this table is no longer be visible in the Migrate > Value Mappings page. This table is not a part of the Value Mapping process, and the user must manually build a table that supports value mapping. Refer to sections Migrate > Value Mappings and also refer to Migrate > Mappings > Mapping the Fields of a Datasource for details of these processes.

GET CHECK TABLES button

This button checks for any check tables for the Datasource(s) based upon the Datasets that use that Datasource. If there are any new fields added or check tables assigned to fields within Mappings, then this button pulls in new Check Table metadata. A message displays to state that "Check Tables refreshed successfully." 

As a subsequent task, the user must Refresh the new tables with one of the three processes shown below.

REFRESH ALL DATASOURCES button

The REFRESH ALL DATASOURCES  button when clicked refreshes the table data for each listed Datasource for all active tables. It is best used as a set point prior to a Mock. Job Queues show titled as "Refresh Check table Values for S4H" as example. The Debug Log provides detailed tasks and outcomes for this refresh.

REFRESH the Datasource

This Refresh  icon refreshes the all active tables for the single Datasource selected. A Job Queue runs titled as "Refresh Check table Values for ECC from tgtECC" as example. The Job creates steps for Insert and Update for each active table in the list for that datasource. A click on the Debug Log  icon displays the details for each step. A Status of Complete shows that the step is successful.

The Insert Step inserts all rows of data into the MIGRATE. LIST_TARGET_VALUE table for each table for new records - it also updates the Created_By and Created_On field during this step.

The Update Step updates any existing rows of data with the MIGRATE. LIST_TARGET_VALUE table with new values found in the Datasource and checks for update to System Values checkbox - it also updates the Modified_By and Modified_On fields during this step.

The Debug Log provides more details of the step.

REFRESH the table

This Refresh  icon refreshes the table data for the single table selected. A Job Queue runs titled as " Refresh Check table Values for S4H T012 from MIGRATE.dbo.T012" as example. This job will contain two steps -

1. Step to insert records into the MIGRATE. LIST_TARGET_VALUE table new values from the Check Table stored in the Snapshot target database.

2. Step to update records in MIGRATE. LIST_TARGET_VALUE table where the value is changed.

To view the details of the refresh process, click Debug Log  icon next to the Step of the job. The INSERT step provides the count of records added to the LIST_TARGET_VALUE table in the MIGRATE database. These values are used in Value Mapping exercises.

The UPDATE step provides the count of records changed in the LIST_TARGET_VALUE table in the MIGRATE database.

Add a New Check Table for a Datasource

There may be a need to add a new table that does not exist within the target Datasource. To add a new table, click on the Add   icon within the Check Tables panel.

The image below provides an example of a completed Check Table details page.

Note

The Import Query remains blank until the table is refreshed and the job queue initiates the query to pull in the data. If the check table is added manually, the Import Query will be required in order for the check table to store values. Fields TARGET_VALUE, LOAD_VALUE, and DESCRIPTION must be included within the query or it will not save.

Note

The Import Query once entered is validated against the following criteria:

• When a Snapshot Datasource value is selected, the validation of query runs against the snapshot datasource.

• When Snapshot Datasource value is not selected (blank), the query runs against system datasource.

• When the selected table does not exist in either the snapshot or system datasources, the dialog produces and error on Save.

Note

The Import Query can concatenate multiple fields into the TARGET_VALUE field if necessary, and the the LOAD_VALUE field contains the actual value that is loaded to the target system. An example of an Import Query is shown below:

SELECT C.SPRAS TARGET_VALUE, C.SPRAS LOAD_VALUE, ISNULL(T.SPTXT, C.SPRAS) DESCRIPTION

FROM T002 C LEFT OUTER JOIN

T002T T ON C.SPRAS = T.SPRSL

AND T.SPRAS = 'E'

In this example, the two fields concatenate to build the TARGET_VALUE used to form a unique key value for the translation.

SELECT C.LAND1 + ':' + C.BLAND TARGET_VALUE, C.BLAND LOAD_VALUE, ISNULL(T.BEZEI, C.LAND1 + ':' + C.BLAND) DESCRIPTION

FROM T005S C LEFT OUTER JOIN

T005U T ON C.MANDT = T.MANDT

AND C.LAND1 = T.LAND1

AND C.BLAND = T.BLAND

AND T.SPRAS = 'E'

AND T.MANDT = '100'

WHERE C.MANDT = '100'

If the Import Query is not scripted correctly, it will fail upon save with an Error Message.

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

Edit an Existing Check Table

To edit an existing check table, click the Edit icon for the row that contains the check table. Each Check Table contains by default the Datasource, Check Table name, Table Description and Subject Area associated with the table. The user may alter to mark this table Active for Value Mapping, to select the Snapshot Datasource, or to apply an Import Query to provide exact details of the translation of the fields as shown below.

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