To map the Enterprise Database Server features in the FeatureMap Designer, double-click one of the classifiers in the ClassifierMap Designer.
The FeatureMap Designer opens displaying the Enterprise Database Server features in a tabular format.
Click inside the box adjacent to the desired source feature, and draw an arrow to connect to the target feature.
For more information about the color coding of the connection arrows, refer to Interpreting the Color of the Connection Arrows.
On the Transformation menu, click Save.
Alternatively, click the Save icon (
).
To delete a connection between a source feature and a target feature, select the arrow, and press the Delete key.
Notes:
Right-click anywhere within the table in the FeatureMap Designer, and click Sort Feature Items. You can choose either Ascending, Descending, or Sort By Creation Order to sort the feature items. This enables you to locate a feature quickly when you have a large number of features in the FeatureMap Designer.
The master data set and its embedded data set, or any different level of embedded data sets of the Enterprise Database Server, should be mapped to different targets. Otherwise, the data of the parent-level data set will be combined with the data of embedded data set, as Data Exchange commits to the target only when the child-level data set is available. If there is no data available in the embedded data set, then the data of the master data set will not be transformed.
Embedded data sets at the same level cannot be mapped to the same target.
While mapping a source Enterprise Database Server Time data type to a target Oracle data type (Date, TimeStamp, TimeStamp with Time Zone, TimeStamp with Local Time Zone), Data Exchange displays a default date value (1900-01-01) along with the source data in the target.
In Enterprise Database Server the data type Date with a value 0 represents the number of days, and the start date is 1600-12-31. If you enter an invalid date, such as February 30, it is stored as 0 which represents 1600-12-31. After transformation it is stored as 1600-12-31 in SQL Server and Kafka, and as 31-DEC-00 in the Oracle database.
Mapping a Group, Occurs, or Group Occurs Data Item
To map occurs or group occurs data items that are large in number, you can map them to a SQL or Oracle target feature with XML data type. Each target XML can hold content up to a size of 2 GB.
While mapping, you can use any of the following mapping options:
Whole: When mapping the root node of an Occurs data item to a target feature with the mapping option selected as ‘Whole’, the resultant value of the target feature is a combination of values of the members of the Occurs data item.
Index: When mapping the root node of an Occurs data item to a target feature with the mapping option selected as ‘Index’, the target receives multiple records, where the value of each of those records will be the index of the Occurs member that has a value.
Value: When mapping the root node of an Occurs data item to a target feature with the mapping option selected as ‘Value’, the target receives multiple records, where the value of each of those records will be the value of the Occurs member with a value.
Note: When mapping a Group, Occurs, or Group Occurs to a target, value of the target would be the value of Group, Occurs, or Group Occurs, which is the concatenation of values of its members without separators.