Data Mapping
The last step in creating a DMEE format tree is to define how the data is to be mapped. Outgoing and incoming DME files represent opposite cases regarding data mapping:
In the case of outgoing files, you map internal system source fields to the target fields in a DME file. The tree type determines which system structures and tables are available for mapping (for example, the
FPAY*
structures for thePAYM
tree type).For format trees for incoming files, you need to map data from a DME file to target fields in the file you are converting to (in a format that the system can process further).
Features
Based on the tree type of your format tree, the system selects all fields that are predefined for the particular application. These system fields form the source or target field inventory and are made available to you when you do the data mapping.
When you define your tree structure, you must link the fields in your file format to the corresponding fields in the system. This enables the DME Engine to extract, in the case of outgoing DME files, the required data from the appropriate fields when you later generate a file. For incoming DME files, just the opposite is true: You map how the incoming data is to be filled in the corresponding system fields.
There are several mapping procedures, and they differ for outgoing and incoming files. The most common procedures are the direct reference to system fields or the specification of a constant. You can also define more complicated mapping rules by including conditions, aggregation, or exit modules. You may also need to convert the format of your data based on a number of available conversion rules.