Dmee sap online_help

SAP DMEE configuration

1. Additional Documentation for SAP note 1062489: DMEE for outgoing XML payment files
¤2007 SAP AG. All rights reserved Page 1
Data Medium Exchange Engine (DMEE) for
outgoing XML payment files
This information was extracted from the SAP online help (R/3 Enterprise 470) by the
author of note 1062489. The full DMEE documentation can be found in the SAP help
help.sap.com: On the initial ‘SAP Solutions -> Overview’ screen, you select ’SAP R/3
and R/3 enterprise’ in the navigation area:
On the next screen, you choose the English documentation for SAP R/3 470:
This opens a new window. There, you drill down: Financials - Financial Accounting (FI)
- Accounts Payable - FI Accounts Receivable and Accounts Payable - Payments -
Executing the Payment Program - Payment Medium Workbench - Data Medium
Exchange Engine.
The Data Medium Exchange (DME) Engine enables you to define file formats that meet
the requirements of your financial institution. By doing so, you model an externally

2. Additional Documentation for SAP note 1062489: DMEE for outgoing XML payment files
¤2007 SAP AG. All rights reserved Page 2
defined bank format in the R/3 System, which allows you to send or receive data in the
form of DME files in this format.
The ability to define these formats in the R/3 System is particularly important in case
there is no worldwide or regional standard format or if the file must comply with bank-
specific standards. Covering such numerous and varied local format requirements is very
difficult in standard software, but the DME Engine enables you to define your particular
local format yourself – without any ABAP programming knowledge or coding. With this
Customizing tool, in the form of a graphical editor, you can define new formats flexibly
and, as format requirements change, modify existing ones efficiently.
Integration
Once you have modeled an external file format as aformat tree in the DME Engine,
calling applications can use it to:
xGenerate anoutgoing DME file as a flat file or an XML file
xConvert anincoming DME file to a format that the R/3 System can process
For SEPA, we have outgoing XML files.
Features
The system comes complete withpredefined format trees, which represent the file format
requirements in a number of countries. You can alsotransport format trees to other
systems, or alternatively upload and download them as XML files.
Applications – Payment Medium Workbench
The DMEE supports a variety of applications (tree types). In the SEPA environment, we
create outgoing files for the Payment Program (tree type PAYM), to submit payments to
the bank electronically. For this tree type, we use thePayment Medium Workbench
(PMW) to configure payment media.
When one executes a payment run, the system triggers the generic payment medium
program of the PMW for creating payment media. This program uses the DMEE format
tree to create the file to be sent to your bank. For this, the system requires aspecial
configuration of the corresponding payment method:
In Customizing forFinancial Accounting (FI), chooseAccounts Receivable and Accounts Payable
oBusiness TransactionsoOutgoing PaymentsoAutomatic Outgoing PaymentsoPayment
MediaoMake Settings for Payment Medium Formats from Payment Medium Workbencho
1. Create Payment Medium Formats
Create a new format with thesame name as your DMEE format tree. Choose the format
outputPayment medium without docs., and typeFile. UnderProgram control, set the
Mapping using DME engine indicator. Once this indicator is set, theDME engine button
appears, which allows you to access the DMEE format tree directly.
UnderFormat information, specify your country. You can also write documentation for
your PMW format by choosing the field help for theDocumentation module field. From
there, chooseProceed, and a document maintenance screen appears. Select document
classGeneral text, enter a name for the text, and create the documentation. Lastly, enter
the name of this text in the PMW format in theDocumentation module field.
2. Assign Payment Medium Format and Note to Payee to Payment Method

3. Additional Documentation for SAP note 1062489: DMEE for outgoing XML payment files
¤2007 SAP AG. All rights reserved Page 3
You need to specify that the PMW is to be used for the given payment method. To do so,
double-click the payment method. UnderPayment medium, set theUse payment medium
workbench indicator and enter the PMW format name you created in step 1 (which must
have the same name as the corresponding DMEE format tree). If you created
documentation for the PMW format in step 1, once you chooseEnter, anibutton appears
next to the format name. If you choose theFormat settings button, you branch to the
settings for the PMW format (the activity in step 1).
Creating Format Trees for Payments
1.Call the DME Engine by entering transactionDMEE.
2.Enter tree typePAYM
3.Enter the name of the format tree (equal to PMW format name)
4.ChooseCreate.
5.In the dialog box that appears, specify whether the format tree is to be used to
generate a flat file or an XML file. The SEPA formats work with XML files.
TheDMEE: Create Format Tree <format tree>screen appears.
6.Maintain data for the root node, called theheader, which appears automatically.
7.Insert nodes hierarchically to represent the DME file layout description, and maintain
the detailed view as needed for eachnode type.
8.Define amapping procedure for each node that serves as a source field (for outgoing
files). Based on the tree type, nodes that require mapping are elements, atoms, and
action nodes. The DME Engine offers a number of special functions, such as
aggregation.
9.Activate the format tree.
Once active, the format tree can be accessed and used as needed by the PMW.
DMEE Screen Layout
After you specify a tree type and a format tree ID on the initial screen of the Data
Medium Exchange Engine (DMEE), theCreate Format Tree <format tree> screen
appears. It is divided into three parts:
Tree structure (1)
On the left side of the screen, you define your format tree by inserting nodes in a
hierarchical structure.
Detailed view (2)

4. Additional Documentation for SAP note 1062489: DMEE for outgoing XML payment files
¤2007 SAP AG. All rights reserved Page 4
When you insert a node in the format tree, detailed information is displayed to the right
of the tree in the top frame. Here you specify additional data depending on the tree and
node type. The information is displayed like a card index; you navigate between different
areas by choosing the tabs along the top.
To display the details for any node, you double-click it in the left-hand tree structure. The
details then appear in the top right frame, and the node you have thus selected is
highlighted in the structure with a blue arrow ().
Source/target fields (3)
The bottom right frame contains all source fields (for outgoing files) or target fields (for
incoming files) that the system makes available for you, based on the tree type you
specified on the initial DMEE screen. These fields make up thesource/target field
inventory; you can select from them during the data-mapping process.
Header Data for Outgoing Files
You maintain the following header information, displayed on the various tabs, for format
trees representing outgoing data medium exchange (DME) files:
Administrative Data
You can document your format tree as needed. To do so, specify a name for your
documentation text in theDocumentation field; the name format<format tree
ID>_DMEE is recommended. You can then maintain the text directly in the SAPscript
editor by choosing. For more information on creating your own format documentation,
refer to the field help for theDocumentation field.
The format documentation is meant to contain general information that is relevant to
the entire format. If you want to document details at the node level (such as how an
amount is calculated), you can enter up to three lines of comments per node, on the
Comment tab (which is visible for all nodes except the header).
Theversion of the format tree is displayed. The system assigns the fixed value 000 to an
active version and 001 to a maintenance version.
Format Attributes
Here you specify a DDIC structure in the case of format-specific parameters. Depending
on the type of file format, you can specify other details: for flat files, you can enter
delimiter information; for XML files, you can specify further processing (via exit
module) for a file after its creation, by entering an XSLT program.
For format trees of the tree type PAYM, you can additionally specify that an
accompanying sheet is to be printed when the file is generated. The system supports the
printing of both simplified sheets and sheets with subtotals. If you specify an
accompanying sheet with subtotals, you must maintain the key fields on theSort/key
fields tab.
Levels
Here you specify the number of levels in the format. In addition, you can define a
repetition limit for each level. This value specifies how often a certain level may be
output. If this number is exceeded, the corresponding level cannot be output anymore. If
the limit is reached for the uppermost level in the format tree and additional data is to be
processed, a second file is generated. If the limit is reached for lower levels, the
preceding level is repeated so that data can continue to be output for this level.

5. Additional Documentation for SAP note 1062489: DMEE for outgoing XML payment files
¤2007 SAP AG. All rights reserved Page 5
Sort/Key Fields
Here you can specify how certain fields are to be sorted. For the payment program, for
example, you can sort according to currency or account by specifying the appropriate
source field. If a sort field is additionally marked as a key field, then a change to the
value in this field causes the corresponding format level to end. By activating bothKey
Field andNo Sorting, you specify that data does not need to be sorted by this criterion (if,
for example, it is already presorted in the Payment Medium Workbench); this results in
additional space in the sort fields, which allows you to use additional fields as sort fields.
If you indicate on theFormat attributes tab that an accompanying sheet is to be printed,
you maintain the key fields here, which define how the subtotals are calculated.
File Data
Here you specify whether segments are to be separated by carriage return or by line feed.
You can also enter your own format-specific characters that you wish to allow in or
exclude from the file; enter them one after another, with no spaces between them. If you
then select one of the following radiobuttons and choose the conversion function
Exclude/allow defined characters for the affected elements, the system does the
following:
xDo Not Allow These Charact.o The system removes the specified characters from the
character string.
xAllow Only These Charact.o The system removes all other characters from the character
string except for the ones specified here.
Creating Nodes
1. For the first node, position the cursor on the root node and choose the pull-
down menu next to the icon, or do a right mouse click on the root node and select the
node you want to create.
2. For successive nodes, double-click the node above where you want to insert the
next node, which the tool highlights with a blue arrow (). You can then specify
whether you want to insert the node on the same level or as a subnode.
Certain restrictions apply to node relationships within a format tree, but the tool only
offers you subsequent nodes that are permitted – provided you double-click the
node you want to insert beneath. For instance, an element cannot have a segment
as a subnode, so this is not an option when you insert a node that follows an
element.
3. Depending on the type of node you create, various data can be maintained in
the detailed view to the right of the format tree. For more information on the individual
fields, choose the field help.
Node Types for XML Files
Below is an overview of node types used in the Data Medium Exchange Engine (DMEE)
for defining outgoing DME files in the format of XML files:
Node Use
Element Represents one line of an XML file; can
contain a value itself, or it can be used to
group elements as subnodes
Atom Used: 1) to output more than one value to a
single element, or 2) to control which value is
output to an element (based on conditions)

6. Additional Documentation for SAP note 1062489: DMEE for outgoing XML payment files
¤2007 SAP AG. All rights reserved Page 6
Technical node Element that is not output to a target file; it
stores values that are used in other tree
nodes (elements, atoms) by a reference to
this node
XML attribute Represents a subnode of an element;
provides detailed information for an element;
can contain atoms as subnodes (for
example, to map conditions)
Data Mapping
For each element in the DMEE format tree, we have to define how data is to be mapped.
1. Insert an element (or atom as a subnode to an element) in the format tree
structure on the left.
2. The system automatically displays the detailed view for the node in the right
frame. This includes the following tabs: Attributes, Source, Aggregation, Conditions, and
Comment.
3. After you enter the required attribute information, select a mapping procedure.
Mapping procedures:
Select mapping procedure If
Constant The value is to be set to a constant
Structure field A value is to be retrieved from a specific source
field in the R/3 System
Reference to tree node An attribute (current value, length, or counter
reading) of another DMEE format object that
was already defined is to be used
Aggregation A value related to a reference node is to be
totaled and made available to this node
Exit module The standard mapping and conversion rules do
not meet your requirements and you wish to
specify an exit module
Ownmapping(atoms) – only
possible for elements
Your mapping rules are dependent on
conditions or if different parts of the element
are to be filled from different sources
No mapping – only possible
for XML format trees
The element is not to contain a source value
itself, but is used to group other elements or
other permissible subnodes below it.
4. Enter detailed source information:
In most cases, you specify that the target field is to be filled from one source field
from the R/3 System, which corresponds to the mapping procedureStructure field.
To specify the source field, you can enter the source field and structure directly
underSource, or you can select a field from thesource field inventory.
5.You can specify a conversion method used toconvert source field data to a
particular format for the DME file. This step is optional; if no conversion method is
specified, data is transferred to the target field in the format it has in the R/3 System.

7. Additional Documentation for SAP note 1062489: DMEE for outgoing XML payment files
¤2007 SAP AG. All rights reserved Page 7
Source/Target Field Inventory
For each DMEE tree type, a set of possible source fields (foroutgoing files) or target
fields (forincoming files) is predefined by SAP. These fields form the source/target field
inventory, which is generated automatically during the data-selection step. You can select
from these fields in the data-mapping process.
For the PAYM tree type, we have the following source field inventory:
xSource fields for the application, in structures FPAYH, FPAYHX, FPAYP.
xSource fields for note to payee (DMEE_PAYD)
xABAP system fields, for example the system date.
xSource fields for format specific structure (if exists)
xTechnical fields: These fields are additional ABAP system fields that are
usually not selected in the data-mapping process. However, they are still made
available in the case that you require such source fields.
Selecting Fields from the Source/Target Field Inventory
To select a field from the source/target field inventory, double-click the document icon to
the left of the field name, and the system transfers the structure and the field name to the
mapping source above. For a description of the fields, choose. To branch from the
structure directly to the ABAP Dictionary, choose.
You can also insert a new element in the format tree directly from the source/target field
inventory by highlighting the field name and dragging it to the format tree. The element
is inserted after the last node in the structure and assigned the technical name of the field.
Aggregation
This function enables you to aggregate values for specified format tree nodes (called
aggregation nodes) and it makes this number available to a defined field in the DME file.
You can either addvalues (e.g. to get the total amount of all payments) oroccurrences
(to get the number of payment transactions in a file).
Conditions
This function enables you to define conditions that control whether a certain format tree
node is processed during file generation or conversion.
You can define conditions for anynode type for outgoing files. If one condition applies to
several consecutive elements, you should define a composite. If you assign a condition to
a segment or a composite, it applies to the corresponding subtree. In this way, for
example, you can control that a complete record (a segment, including all its elements
defined as subnodes) is not output to the file.
You define a conditional relationship for a node in the detailed view underConditions,
which displays a condition list that looks like this:
Arg1-1 Arg1-2TypeOperatorArg2-1Arg2-2TypeOperator
x x x x x x x x

8. Additional Documentation for SAP note 1062489: DMEE for outgoing XML payment files
¤2007 SAP AG. All rights reserved Page 8
The first part of the argument is defined by the first four fields, and the second part by the
last three; the fourth field is the linking operator to the next condition line, if you define
one. You fill this condition list as follows:
Field Name Required Entry
Arg1-1 Here you specify field 1 of the first part of the condition argument.
This can be a constant, a source structure, or a reference ID (of
another node already defined in the format tree).
If a comparison value is a constant other than a numeric value,
then you must enter it enclosed in single quotation marks, like
'EURO' in the example below.
Arg1-2 Here you specify field 2 of the first part of the condition argument.
If, in Arg1-1, you entered a:
1.-Constant, then leave this field blank.
2.-Structure field, then enter the field name (which you can
take from the source field inventory).
3.-Reference ID, then enter the node attribute of the
referenced node that you want to check.
Type Enter the type of argument for the first part of the condition
argument:
1 = constant
2 = field in source structure
3 = reference ID
Operator Enter the operator to be used for the comparison, such as equal to
(=) or less than (<).
For more information on possible logical operators in the
condition, seeComparing Strings.
Arg2-1 Here you specify field 1 of the second part of the condition
argument. Like the first part, it can be a constant, a field in a source
structure, or a reference ID.
Arg2-2 Here you specify field 2 of the second part of the condition
argument. The same dependencies apply as for Arg1-2 above.
Type Enter the type of argument for the second part of the condition
argument. The same values apply as for the first part of the
argument.
Operator Here you enter the linking operator to establish the logical
operation (AND or OR) between two condition lines (only
necessary if you have two condition lines).
When a file is generated from one of the predefined applications, the system processes
the format tree and checks each node for conditions. If a condition is met, the system
processes the node; if it is not, the node is ignored.
If a condition for an upper-level node is not met, all subnodes are also ignored
during processing.
Activating Format Trees

9. Additional Documentation for SAP note 1062489: DMEE for outgoing XML payment files
¤2007 SAP AG. All rights reserved Page 9
You always maintain version 001 of the DMEE format tree. After you create or make any
changes to your format tree, you need to activate it so that calling applications can use it
to generate or convert a DME file.
Procedure
1. Complete maintenance of the format tree.
2. ChooseFormat treeoActivate or.
3. The systemchecks the format tree.
Result
If the check determines inconsistencies (errors or warnings), the system saves the format
tree in the maintenance version, 001. To activate the tree, you must first correct all errors
and then repeat the activation procedure.
If no errors are determined, the system activates the format tree and saves it as the active
version, 000.