Exports

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

• Cross Reference Building and Execution

About Exports

Depending upon the process for loading data into the target system, there may be a requirement to build exported flat files.  As part of the project build, a section or Job for Export is defaulted into each project in DS.  The Export Job, Workflow, Dataflow, and Query works to produce flat files to store locally in a file pathway determined by the Substitution Parameter settings.  Refer to section Substitution Parameters for more details of this setting.

Export file pathways include the Object Short Name - This added path segregates the files by Object within the Export file to reduce issues with use.

Chunk the file

As part of the Dataset XML BUILD, Syniti Migrate incorporates a process for 'chunking' or splitting the file into smaller more manageable files so that the target system will not become overloaded.  It makes loading more efficient.

Build the DS Export Workflow to create CHUNKED export files based on the zCHUNK field on the target table.

1. zCHUNK defaults to 1 in the target table. If the developer does NOTHING, they will get one EXPORT file per Target Table.

2. If the Developer updates zCHUNK value in target table, they will get the same number of Export Files.

The image below provides an example of how these files will be saved in the designated Export folder on a shared drive for the project.