Cross Reference

This topic is related to the following sections:

• SAP Data Services for Migrate

• Preparation of XML in Migrate

• Importing XML Code Into Data Services

• Post Import Maintenance of Project

• Mapping Standards

• Report Building and Execution

• Export Building and Execution

• Cross Reference Building and Execution

About Cross Reference and Value Mapping

The translating of data from legacy to target systems will most likely include translating as a cross reference.  Within Syniti Migrate, the Cross Reference process is handled using Value Mapping. Refer to section Value Mappings for details of setup and use.

These translations are stored within tables XTVALUEMAP and LIST_TARGET_VALUE in the MIGRATE database. The steps for tracking and translating the Check Table values includes an Insert and then Update rule for each field designated at a Cross Reference (Xref).

Import of the Cross Reference process to DataServices

All fields mapped as an XREF are scripted within XML to build the following Workflows within the Project in DataServices.

1. XREF Update Dataflow/Query (Ex: FV_F0004_ADVWRK_CUSTOMERS_S_Upd_XREF)

2. XREF Insert (Ex: FV_F0004_ADVWRK_CUSTOMERS_S_Ins_XTVALUEMAP)

Note

Ensure that at least one field of each dataset is set for XREF type mapping to ensure that these XREF processes are included in the conversion prior to initial build of XML.  The user may remove them at any time if there is no use, but the system would not add them automatically in the future if they are added.

XREF Update Build and Use

The Update Dataflow and query for XREF stores every field that translates using the XREF process. The Dataflow is a basic update flow as shown below:

Within the query, the fields are each identified and mapped so that all XREF processing will perform during this step of the process.   This query will include all fields mapped as XREF.  Should the user need to add more fields to this process in the future, they must manually add them to the query step.  In this scenario, two fields are included in the XREF, and the target values are mapped using the XTVALUEMAP table.  Additional fields may be added manually following the same scripting as shown in the image below.

XREF Insert Build and Use

The Insert Dataflow and query for XREF stores every field that translates using the XREF process.  The Insert Dataflow pulls new values from the source table field to load to the XTVALUEMAP table for use in mapping.  This effort keeps the XREF data current.  If the Dataset does not contain any mappings for XREF, then this Insert Dataflow should be removed from the active project.

Note

Since this insert rule will pull in the new values in each source field being cross referenced, it will be very important to run the conversion prior to formal mocks so that these new field values may be captured and mapped in time for the official Mock run.

Each field for XREF is set up as a separate query in the Dataflow for XREF Insert.  These queries pull distinct values where the zActive flag = '1' to ensure that the values going into XTVALUEMAP table are valid.  Should the mapping of an XREF field include an XREF description, that value will also be loaded to the XTVALUEMAP table as the zXREF_DESCRIPTION.

The Merge Platform will combine each set of field data into one list, and then the final Insert Query will insert the records into XTVALUEMAP table as shown below including audit and supplement fields.