Mapping When Using an Exterior ETL Tool

This topic relates to the following sections:

• Mapping the Fields of a Datasource

• Build XML Code for Source

• Download Individual XML Files

• Create Working Tables

About Mapping When Using an Exterior ETL Tool

This section is relevant to a Release using ETL Tool = Data Services (Not relevant to ETL Tool = Syniti Migrate. Refer to section Migrate > Mapping > Mapping the Fields of a Datasource > Mapping When Using Migration ETL Tool  for details of that process)

From the multi-panel page, mappings are completed from within the Sources panel.

First, select the data source and click the Mapping  icon in the page above. A page containing all of the active for mapping fields displays.  This list of fields contain all of the Migration tab fields that were marked as Active for Mapping OR Element Active.  A breadcrumb pathway is displayed to provide the Mapping team identity of the Release, Dataset, Target for this mapping. 

Note

This list never displays the field ZSOURCE as a value is defaulted from the datasource selected for this mapping.  Also, field ZSOURCE is never counted within the number of fields mapped on the main Mapping page or within any Metrics reporting built from this effort.  The ZSOURCE field is used for the conversion team's benefit and should not affect overall reporting and counts.

The Mappings panel displays the following Column Headers:

At first, all fields have a Map Status equal "New" and Build Status equal "New".   If the user should enter a value to the Map Action field and then save the mapping, the Map Status automatically updates from "New" to "In-Progress."

The basic icons for mapping the data are provided in the table below:

Icon	Description
	The View Mapping History icon provides a list of actions by date and user.
	The Copy icon provides the user ability to select by field to update the mapping to Copy, and provide additional fields for this mapping type.
	The Default icon provides the user ability to select by field to update the mapping to Default, and provide additional fields for this mapping type. NOTE:  Examples for Defaulted values are WEST, 1, NULL or <NULL>, BLANK or <BLANK>.  The field cannot be left without a value.  Add a value with no quotes.
	The Rule icon provides the user ability to select by field to update the mapping to Rule, and provide additional fields for this mapping type.
	The Xref Used icon provides the user ability to select by field to update the mapping to Xref, and provide additional fields for this mapping type. NOTE:  XREF Mappings require value in field Check Table.
	The Not Used icon provides the user ability to select by field to update the mapping to Not Used.
	This icon is provided for the Table and Field values in the Data Mapping Details panel.  A click on the icon for Table provides a list of the Top 50 rows of the table.  A click on the icon for Field provides Distinct values in the field.
	This icon provides option to update the Map Status to "Complete" as a one-click action.  Otherwise, the user may select the same value from the drop-down list.
	The Reject History icon provides the history for any rejection of the Mapping
	The Reject Icon allows Developer to click to Reject the Mapping and to send notification to the Mapper of the Rejection Comments
	The Mark in Progress icon updates the Build Status to In Progress and automatically saves the mapping details and lock the page for changes.
	The Unlock icon only dispays once the Map Status has changed to Complete.  To make changes to values on the mapping the user must click on the Unlock icon to open the mapping to changes.  Refer to Lock and Unlock of a Mapping below for more details.

These icons assist the user in making the mapping experience easier as they allow for updating many records in a dashboard rather than maintaining each field individually.

Once a row or field has been selected, the details for mapping of that field can be updated and saved. The cursor sets on the field for the associated mapping action, and the fields in the edit panel changes depending upon the criteria of each mapping action. The table below provides the fields and definitions of their usage.  In the example below, the Mapping Action = Default. 

Note

Be sure to change the Mapping Status to "Complete" before attempting to run the Build XML automation steps to ensure all the mapping logic is captured.  Click on the Checkmark  icon to update the Map Status to reflect Complete. 

The table below provides the Data Element and Data Mapping Detail fields and definition of their use:  These values are relevant to the field that is highlighted in the top panel for Mappings. 

Map Action Details for a Rule

In this example of a Rule Mapping, the user must define the tables and fields to be used as well as entering text comments of the rule specifics that are pushed into the ETL as descriptions.  In this mapping type, the user manually builds a view that filters to the set of records for update to the new value.  Migration does not build this Rule, but it documents the details within the ETL to assist the user in this effort. 

Within a Mapping Type = Rule, the user may select multiple rows containing table/field values to use in the join to build the update.  Click ADD ROW  button to provide additional rows of Table/Field. 

Note

Should the field Rule Sql and the button ETL RULES not display, it shows that the ETL Tool selected for this project is other than Migration.  For projects that use SAP Data Services to run the ETL process, these items are hidden. 

Map Action Details for Copy

This example displays the mapping action for Copy. 

Note

Should the mapping select a different table than the Target Source table, then although the action is still a Copy, this mapping is not update this field in the Insert Rule.  The system auto generates a View as an Update Rule for the mapping.

Map Action Details for Cross Reference (XREF)

This example shows mapping action for a Cross Reference (XREF).

Note

Should the mapping select a different table than the Target Source table, then although the action is still an XREF, this mapping is not update this field in the Insert Rule.  The system auto generates a View as an Update Rule for the mapping.  The Source XREF Update and Insert rules apply for both the simple and complex XREF actions.