Preparation of XML in Migrate

This topic is related to the following sections:

• SAP Data Services for Migrate

• Importing XML Code Into Data Services

• Post Import Maintenance of Project

• Mapping Standards

• Export Building and Execution

• Report Building and Execution

• Cross Reference Building and Execution

About Preparation of XML Code

During the process of building the mapping and migration of data from source to target systems, there are opportunities to export the associated XML scripting from the system to a file. This file will then be imported into SAP Data Services. This process of exporting and importing of scripting files reduces the overall time spent in building out the hierarchy of Jobs, Workflows, Dataflows, and Queries.

The XML scripts are not intended to build the entire transformation of data. The intricate rule specifics will need to be built manually by the developer as well as adding each Source Mapping Workflow to the Transform within the Project. The process of importing is not intended to be a complete solution, but a foundation from which the developer may enhance the process. Make sure to always check the scripting for accuracy. Validate each section of the Project after import, and test run the jobs for successful use going forward.

Within Syniti Migrate, there are three specific sections where the building of XML and DDL scripting takes place.

Building XML for Datasources to Datastores

Snapshot datasources and the Working database associated with migration of data are scripted out in XML to add the tables and columns for the Datastores in SAP Data Services. The list includes the Source snapshot, the Target snapshot, and the Working database.

• The Source snapshot refreshes each of the source tables stored in the database system. Within the SAP Data Services, an Import job from source system to source database will keep the data consistent to the dates of the conversion Mocks.

• The Target snapshot refreshes each of the target tables stored in the database system. Within the ETL tool, an Import job from target system to target database will keep the data consistent to the date of the conversion Mocks.

• The Working database storse the tables of the conversion and is tied to the same tables in the active database of the project.

For more details on the maintenance of Datasources within Syniti Migrate and preparation for building of the XML scripting, please refer to the section Snapshot Datasource Build Import XML for details of this process.

From the Main page use pathway Migrate > Snapshot Management to display the Snapshot Datasources, Tables, and Columns as shown below:

At this point, the user clicks to select the Snapshot Datasource, and then click Edit  icon to view the Datasource's details.  Scroll toward the bottom of the Details panel page to locate the section XML. Click the BUILD IMPORT XML button to build a new copy of the scripting.  The system produces a message indicating the build is in process.

Note

If the XML scripting has not yet been built, you may only see the BUILD XML IMPORT button on this page.

To view the XML Scripting, click on the VIEW IMPORT XML  Button.

Note

The Datastores for each of these Datasources must first be created manually within SAP Data Services Datastore section before the XML files are imported to Data Services system.

Building XML for the Mapping Dataset

During the process of mapping the object from source to target fields, the user has the opportunity to Build XML for the Dataset. This XML script contains the Project outline including the Project, Jobs, Workflows, Dataflows, and Query structures for the entire dataset.

Having already manually created the Datastores within SAP Data Services, this process successfully imports to the ETL tool. The Datasources are setup for import of tables and table data base upon the prior section of this document.

For details on the maintenance of Dataset Mapping within Syniti Migrate and preparation for building of the XML scripting, refer to the section Build XML Scripting for the Dataset.

From the Homepage. use pathway Migrate > Mappings to view the Releases, Datasets, Targets, and Source Mapping data for an object.  Click the Edit  icon for the Dataset to view the Release Dataset details page.  Once the XML scripting has been built, there will be three buttons available for use:  BUILD XML, VIEW XML, and DOWNLOAD XML.

At this point, the user may click on the VIEW XML  button to display XML scripting for this dataset.

Note

If the Datastores are not setup, and the tables are not imported, those tables import as part of the XML script but fail with a red x in the transformation because they don't really exist in the Datastore.  Create the Datastores, import the tables, and then re-map these tables in the transformation to correct this issue.

The DDL and table building is created as a Job Queue immediately as part of the XML Build process.  The user may find this DDL scripting for the Table Create stored in the Job Queue within the step for the Table.  If the table fails to build, the user may copy that scripting into the Database to view the detailed messaging.

Building XML for the Mapping Sources

During the process of mapping the object from source to target fields, the user has opportunities to Build XML for each of the Sources for mapping to Target. This XML script will contain the Workflow, Dataflows, and Queries that make up the Source transformation.

Having already manually created the Datastores within SAP Data Services, this process successfully imports to the ETL tool. The Datasources are setup for import of tables and table data base upon the prior section of this document.

For more details on the maintenance of Sources Mapping within Syniti Migrate and preparation for building of the XML scripting, refer to section Build XML Scripting for Source data.

From the Homepage, use pathway Migrate > Mappings to view the Releases, Datasets, Targets, and Source Mapping data for an object.  Click the Edit  icon for the Source to view the Source Details page.  Once the XML scripting has been built, there will be three buttons available for use:  BUILD XML, VIEW XML, and DOWNLOAD XML.

Mappings: Source Details: Download XML

At this point, the user may click on the VIEW XML button to display the build of XML scripting for this source.

Note

If the Datastores are not setup, and the tables are not imported, those tables will import as part of the XML script but will fail with a red x in the transformation because they don't really exist in the Datastore.

Create the Datastores, import the tables, and then re-map these tables in the transformation to correct this issue.

The DDL and table building is done as a Job Queue immediately as part of the XML Build process.  The User may find this DDL scripting for the Table Create stored in the Job Queue within the step for the Table.  If the table fails to build, the User may copy that scripting into the Database to see what the detailed messaging is in that system.