Snapshot Datasource Build Import XML

This topic contains the following sections:

• Snapshot Management

• Edit Snapshot Tables and Columns

• Snapshot Datasource View Import XML

About Snapshot Datasource Build ImportXML

This process builds out the tables in the database for the Snapshot Datasource as well as building the XML Scripting for the Project for Import from System Datasource to Snapshot Datasource the rows of data.  This process is relevant for ETL tools = SAP Data Services.  This process is not necessary if the ETL Tool is Syniti Migrate.

Note

Since the Datasources are not Release specific, the setting for ETL is taken from the Parameters page.

Prerequisites to Running the Build Import XML

• Prior to running this Build XML process, make sure to have already attached a Source Datasource from which the table rows of data are pulled.  The Source Datasource may be a source system or target system, and the data is pulled into the Snapshot Datasource tables (either SRC or TGT prefix) in the Snapshot database based upon this setup.  The tables for import of data need to be marked as active and contain the metadata for Columns and other formatting so that the data builds properly in the XML Scripting. 

• The System Datasource must have a value in field XML Datastore prior to running the Build Import XML process.  If there is no Datastore value, this build fails. 

• If within Parameters page the ETL Tool = SAP Data Services, the Build and View XML processes is active.  If however, the ETL Tool = Syniti Migrate, then this section is not relevant.  Migration ETL Jobs Tool does not use XML Scripting. 

Note

The field XML Datastore within the Snapshot Datasource must contain a value in order for the XML scripting to build properly - if this field is left blank a check during the Build Import XML produces an error message for missing XML Datastore value.

Column Do Not Import flag

Should the user flag columns for Do Not Import, those columns are left off the XML Import build scripting for the ETL.  The fields remain included in the SQL scripting  for the table builds in the database system. 

Note

The Set Import Flags button is present for Snapshot Datasource tables only.  In this case, the user may click on the button to mark all fields (except Key fields) as Do Not Import.  This reduces overall updates should the majority of fields need update. 

A warning message displays.  Click OK to proceed to update all columns except the Key fields as Do Not Import or click Cancel to exit this process. 

Datasource: Snapshot Datasource: Set Import Flags to Active

Build Import XML 

While viewing the Snapshot Datasource Details stored within Application Syniti Migration, click BUILD IMPORT XML  button to build the XML code.

The Snapshot Datasource is attached within section Source Datasources to one or more source systems.  The tables used for Datasets and Mapping is active within both the source Datasource as well as the Snapshot Datasource as this indicates that they are promoted in the XML scripting for import to the ETL and DDL builds within the Database.

This action builds the XML code that can be downloaded and imported to the ETL Data Services to accelerate the migration process. The Job Queue produces 2 jobs - one to create the XML file loads and DDL Scripting as one step, and one to build the tables within the database as a step for each table with status of completion. 

A window displays to indicate that "Job Queue has been initiated successfully".

Note

Should the Snapshot Datasource be an SAP system, the Build XML process fails if the SAP Client is not defined within the Source Datasource.  See the error shown in DEBUG LOG for Building XML below:

DEBUG LOG: Build XML for Snapshot Datasource: Error Message

An error message displays.

If the job does not have issues, it may take some time to complete. Review the status of this build by a click on pathway Administer > Job Queues

The user may view the Debug Log entries associated with each step by clicking on the Debug Log   icon.  In the case above, the tables are already created within the Snapshot database, and so they ERROR as they do not build again. 

Format for DATE fields and SAP Default Date (00000000)

Note

Date fields translate in a format of MM/DD/YYYY as example '01/01/1900'.  Additional scripting is added to each DATE field to include a filter that updates for the SAP Default date (00000000) to '01/01/1900.'  See the example highlighted below -

Snapshot Datasource: View XML: TargetSystemSAPTable scirpting: Format and Filter for DATE fields