Data Medium Exchange (DME) - Mapping

Transaction: DMEE Tree Type: PAYM The purpose of mapping is to reconstruct a file from the SAP system, which then bank can then use to process payments. The process of mapping begins with the bank first providing a file format. The format documents and file examples are then used to map the fields in SAP. Once complete the mapping is attached to the SAP Accounts Payable configuration so an output file can be generated during a payment run. File Structure: The first two levels are mandatory, and the levels beneath the dotted line differ depending on the structure of the bank file format. This ability to define the various subnodes within the payment file allows the user to define the structure of the file according to the banks specifications. DMEE Tree: Properties Root: ------------------------------------------Header Record: Payment Record: Trailer Record: Sorting:

Node Types:

Segment Group Segment groups are used for arranging segments. Segment groups can be followed by these nodes: segment groups or segments. In most cases, a new level in a DMEE tree begins with a segment group. Segment A segment represents a record in the target file. In an active format tree, each segment must have at least one composite or one element as a subnode. If you created a segment that contains only segments and segment groups as subnodes, you can convert the node to a segment group. Composite You create a composite for the purpose of grouping elements. Such a grouping is logical if, for example, one condition applies to several consecutive elements.

Element An element represents a field in the target file. For each element, you specify with which value or from which source field this file field is to be filled. If more than one mapping rule applies to an element - if the rules are dependent on conditions or if different parts of the element are to be filled from different sources - then you should define several atoms as subnodes of the element. Technical Node A technical node is an element that is not output to the target file. It stores values that are used in other tree nodes (elements, atoms) by reference to the technical node. For this reason, a technical node generally contains a reference ID. If you wish to output the contents of the technical node to the target file, then you can convert the node to an element. Atom You need to create an atom when you define more than one mapping rule for an element. Selected Node for Detail View This node was selected by double-clicking it. The details displayed on the top right belong to this node. All toolbar operations (delete, copy, and so on) apply to this node. In contrast, all operations that you can select from the context-sensitive menu with a right mouse click refer to the node which is currently selected by a single click. Reference ID of Node A node that contains a reference ID can be referenced from other nodes in the format tree. You can specify such a reference when you define mapping rules, conditions, or aggregation. You must assign unique reference IDs (within the tree). When you delete a node that contains a reference ID, be sure that no references to this node exist. Reference to another node exists This node contains a reference to another node. Moving the node could result in inconsistencies since certain references are not permitted in parts of the tree.

**Documentation from http://help.sap.com/ was used to source portions of the above information.

Data Element: Atom: Data Element: Tabs: 1. Attributes a. Attribute Types Constant Example:

Structure Field Example:

Reference to Tree Node Example:

Aggregation Example:

Exit Module Example:

Conditions Example: