Generate Mapping

Use the Generate Mapping screen in the left navigation menu to create a new mapping from source and target systems. This feature is also accessible via the Design tab in the top navigation. You can access via the Home Screen in the left navigation menu or in drop down menu via the Design tab in the main header.

When on the Generate Mapping page, you can collapse the Choose Connections and Choose Mapping Type sections by clicking on the header of each section.

You can resize the left hand column of the page by dragging the divider between it and the center column. Clicking the divider collapses the column entirely; click it again to restore it.

Choose Connections

To generate a new mapping choose a source and target data store from the two select lists.

To be available as a source or target, an Administrator must add them in the Manage Connections screen.

Choose Mapping Type

Once a source and target is selected, you then choose one of the available Mapping Types below.

Schema(s) allows you to select one or more schemas in the source database, generating mappings for each table in the schema(s) selected.
Table(s) allows you to select a single schema and then select one or more tables in the schema.
View(s) allows you to select a single schema and then select one or more views in the schema.
Custom Query provides the ability to craft custom SQL queries as mappings. Custom SQL gives you the ability to build data pipelines with the most advanced series of conditions.

If a selected map(s) already exists, you will receive a warning they will be overwritten if you should choose to continue.

Choose Schema(s)

Use this multi-select list to select schema(s) when you opt to create a mapping for a Schema(s) or Table(s) as noted above. The

button will remain disabled until all required selections have been made.

Once you click the Generate Mapping, the Generation Results will appear in the center of the page. The results will return the following fields:

Map Type
Source Connection
Source Schema
Source Table
Target Connection
Map Name
Status
Run button, to run the mapping immediately

Choose Table(s)

Tables(s) allows you to select a single schema and then select one or more tables in the schema. The

button will remain disabled until all required selections have been made.

Choose View(s)

After you choose Connections, Mapping Type (Views) and Schema/Table, the Generation Results will be displayed in the center of the page. The

button will remain disabled until all required selections have been made.

Custom Query

Custom Query provides the ability to craft custom SQL queries as mappings. Custom SQL gives you the ability to build data pipelines with the most advanced series of conditions.

Target Schema — choose an existing schema on the target, or type a new schema name.
Target Table — choose an existing table, or type a new table name. If the table does not exist Kodda creates it when the mapping runs (unless Disable Target DDL is on).
SQL — enter the query to run against the source connection.

In order for Kodda to generate a sequence (sometimes referred to as an identity column) use the Kodda function $sequence()$ in your query. At run time Kodda will generate this column as an identity/sequence column on the target table.

Click Run below the editor to test the query. The Query Results panel opens underneath with the rows returned, with paging and a search box. If your custom SQL is not accurate, you will be presented with an error message instead.

Once the query is tested, click Generate Mapping to create the mapping. Custom query mappings are named Cust.<target>.<source>.<target schema>.<target table> and appear in the Generation Results with a link to open them in Edit Mapping.

Activities

Generate Mapping creates an auto generated data pipeline from source to target, storing those parameters in the repository. Click the green Generate Mapping button and Kodda generates one or more mappings based upon the Mapping Type and selections noted above.

Be sure to review the Workflow Options and Advanced Options before you click Generate Mapping.

Once you generate your mapping(s), the Generation Results in the center pane of the screen show your mappings. Each Map Name is a link that opens the mapping in the Edit Mapping screen for you to review and/or modify as necessary.

Click the green run icon at the end of a row to run that mapping immediately. Status shows a check mark once the mapping has been generated.
If you auto-generated a workflow with the Generate Workflow option below, open it in the Design Workflow screen to review or run it.

Workflow Options

Turn on Generate Workflow to reveal the Workflow Name and Max Parallel Paths fields.

Click slider to automatically enable or disable generating a workflow.

Workflow Options	Description
Generate Workflow	Before you hit the button, if you set this Generate Workflow option on, then Kodda automatically creates all the mappings you need and a workflow to run them all. When generation completes, you see this new workflow under all the mappings in the Generation Results on the center console of the screen. This simple option allows you to generate the mapping and workflow all in one step. If your workflow is large and/or complex enough to warrant additional review, you can always edit the workflow to optimize its auto-generated logic. To edit it, just click the provided link which will migrate you directly to this workflow in the Design Workflow screen.
Workflow Name	When you opt to automatically generate a workflow with the Generate Workflow option described above, enter a name here for the resulting workflow. If a workflow with this name already exists, you are informed of it and forced to provide a unique workflow name.
Max Parallel Paths	Set the maximum number of parallel mappings allowed in the auto-generated workflow or some basic ability to tune your resulting workflow. For example, if generating mappings for 100 tables, and you select to automatically generate a workflow as noted above, setting this parameter to 20 will create a workflow with 20 parallel streams, each executing 5 mappings in sequence. These parallel streams are randomly generated by Kodda’s internal algorithms. You may review and edit the auto-generated workflow if you believe your data pipeline is large and/or complex enough to warrant the time spent optimizing the data ingest process, such as a 2000 table process in which you want some tables to specifically load before others, or other complex use cases. *While there is no max, a number between 2-8 is recommended.

Advanced Options

Options	Description
Disable Audit Columns	By default, Kodda automatically includes three standard audit columns of si_job_id, si_create_date and si_update_date on each table mapping it creates, and auto-populates them in the target records when the mapping is run. These columns are very useful in tracing the lineage of your target data. If the user does not want these fields generated in the target data, users can disable their creation by turning it on.
Disable Target DDL	When Kodda runs a mapping, if the mapped object does not exist in the target database, by default Kodda creates and runs DDL (Data Definition Language) to create the object, then loads the data. Kodda will also add any additional columns that do not yet exist on the target table. Disable this default behavior by turning this option on if you do not want your target table structures to be modified by the mappings generated. Disabling target DDL is useful if you have two databases that may not be fully in-sync and yet you still want to migrate data between them without touching their structure. For instance, if you are replicating data from a production to a test or development database, and you want to move the data only, but not change the structure in your test or development environment. The Detect Target Changes option below is often also useful when disabling this option.
Detect Source Changes	Kodda can duplicate tables from source to target automatically. Alternatively, turning this option on allows you to enforce that all the mapping(s) generated pick up any source data structure changes when moving data into the target. In effect, this allows you to add columns in your source system that will automatically appear in your mapping at run time. In addition if you drop columns in table(s) in your source system they would no longer be included data extract process.
Detect Target Changes	Set this will option on to ensure that data will only be delivered to columns that are available in the target. When generating a mapping to move data from source to target, if a column exists on the source, Kodda’s default presumption is that this column also exists on the target. This option instructs Kodda at run time to ignore columns from the source that do not yet exist in the target table. For example, if a column exists on the source, and the Disable Target DDL option has been enabled, Kodda will not attempt to insert data from this column on the target.
Match Source Names	By default Kodda will auto rename schemas, tables and columns with reserved words on the target table postfixed with an ”_”. Additionally, Kodda will auto rename columns that exceed the 30 characters in length. Kodda also generates a name for the target schema/database used for the target table based on the source connection and source schema name. Enable this to override this behavior and ensure that the generated mappings are set to deliver data to target objects with the same schema, table and column names found in the source.
Override Tgt Schema	By default Kodda names the target schema from the source connection name and source schema name, joined with an underscore (for example, connection `demo_db` and schema `sales` give `demo_db_sales`). Any characters other than letters and numbers are replaced with `_`, and names over 30 characters are abbreviated. For Salesforce and file sources the source connection name alone is used. Turn this option on and enter a Schema Name to write all of the generated mappings to that schema on the target instead.

Documentation

Generate Mapping

Navigation

Choose Connections