You can use a mapping template instead of creating a mapping from scratch.
Available templates are divided into categories on the Templates page. You can also view all templates, filter and sort the page, or search for a specific template. Drill down on a template to view more information about it, including the mapping image.
The following image shows the Templates page with the All templates tab open:
When you create a mapping template, you create a mapping that uses a copy of the mapping template.
The template mapping contains pre-populated transformations. Click on each of the transformations in the mapping to see the purpose of the transformation, how the transformation is configured, and which parameters are used.
The following image shows the Augment data with Lookup template with the Source transformation selected. The Description field shows how the Source transformation is configured:
You can use a mapping template as is or you can reconfigure the mapping. For example, the Augment data with Lookup template uses the p_scr_conn parameter for the source connection. You can use the parameter to specify a different connection each time you run the mapping task that uses this mapping. You might want to use the same source connection every time you run the mapping task. You can replace the parameter p_scr_conn with a specific connection, as shown in the following image:
When you save the mapping, you save a copy of the template. You do not modify the template itself.
Mapping templates don't apply to mappings in SQL ELT mode.
Data Vault templates
Use a Data Vault template to create a mapping that writes data to a hub, link, or satellite table.
The Data Vault category contains the following templates:
•Data Vault – Hub. Generates unique business keys and writes them to a hub table along with the date the records are loaded.
•Data Vault – Link. Creates relationships between hub or other link tables based on business keys and stores the connection in a link table.
•Data Vault – Satellite. Generates a satellite table to store descriptive data such as context or history for either a hub or a link.
You can use the templates individually or use all three to help you structure your data. However, Data Vault components must be loaded sequentially. A link record must reference existing hub or link records, and a satellite record must reference its parent hub or link record.
