Payment Medium Workbench

Payment Medium Workbench
PDF download from SAP Help Portal:

http://help.sap.com/saphelp_dimp50/helpdata/en/cb/4104aadf2b11d3a550444553540000/content.htm
Created on October 20, 2016
The documentation may have changed since you downloaded the PDF. You can always find the latest information on SAP Help
Portal.
Note
This PDF document contains the selected topic and its subtopics (max. 150) in the selected structure. Subtopics from other structures are not included.
© 2016 SAP SE or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose
without the express permission of SAP SE. The information contained herein may be changed without prior notice. Some software products marketed by SAP
SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are
provided by SAP SE and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP
Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set
forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional
warranty. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE in
Germany and other countries. Please see www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.
Table of content
PUBLIC Page 1 of 27
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Table of content
1 Payment Medium Workbench
1.1 Creating Payment Media
1.2 Payment Medium Format
1.3 Payment Medium Format Supplement
1.4 Note to Payee
1.4.1 Alternative Payer, Alternative Payee
1.5 Selection Variants
1.6 Data Medium Exchange Engine
1.6.1 Outgoing File
1.6.1.1 Customizing Payment Methods for Use with DMEE
1.6.1.2 UMS1, UMS2, and UMS3 Tree Types
1.6.2 Incoming File
1.6.2.1 Convert Format of Incoming DME File
1.6.3 Creating Format Trees
1.6.3.1 Screen Layout
1.6.3.2 Header
1.6.3.2.1 Header Data for Outgoing Files
1.6.3.2.2 Header Data for Incoming Files
1.6.3.3 Creating Nodes
1.6.3.4 Node Types
1.6.3.4.1 Nodes for Outgoing Files
1.6.3.4.1.1 Node Types for Flat Files
1.6.3.4.1.2 Node Types for XML Files
1.6.3.4.2 Nodes for Incoming Files
1.6.3.4.2.1 Optional Supplementary Segments
1.6.3.5 Data Mapping
1.6.3.5.1 Mapping Outgoing Files
1.6.3.5.2 Mapping Incoming Files
1.6.3.5.3 Source/Target Field Inventory
1.6.3.5.4 Conversion of Source Data
1.6.3.5.5 Aggregation
1.6.3.5.6 Conditions
1.6.3.5.7 Exit Modules
1.6.3.6 Conditions
1.6.3.7 User-Defined Incoming File Checks
1.6.4 Activating Format Trees
1.6.4.1 Format-Tree Checks
1.6.5 Testing Active Format Trees
1.6.6 Transporting Format Trees
1.6.7 Version Management
1.6.8 Delivered Format Trees
!--a11y-->
PUBLIC Page 2 of 27
!--a11y-->
1 Payment Medium Workbench
Purpose
The Payment Medium Workbench (PMW) is a tool used to configure and create payment media sent by organizations to their house banks. This generic tool
will gradually phase out the classic payment medium programs (RFFO*) due to the range of advantages that it provides.
Superior control and verification of payment procedure
Improved performance with mass payments (> 50,000)
Better sort functions with payment advice notes
Clearer to work with than the myriad previous payment medium programs
Easier to maintain and to extend
Implementation Considerations
Before you can use the Payment Medium Workbench, you have to make various settings in Customizing. You can find the relevant activities in Customizing
for Financial Accounting, under Accounts Receivable and Accounts Payable
® Business Transactions ® Outgoing Payments ® Automatic Outgoing Payments ® Payment Media ® Make Settings for Payment Medium Formats
from Payment Medium Workbench.
Integration
The Payment Medium Workbench can be used by several components, for example FI-AP/AR, FI-TV, HR-PY, TR-CM, and TR-TM.
Features
The Payment Medium Workbench is embedded in a development environment. You can access all Workbench objects, (program objects, dictionary objects,
and mapping tool objects) with a double-click. The Payment Medium Workbench encompasses the following areas:
1. Customizing for payment media
Defining
Payment Medium Formats
Adjusting payment medium formats
Adjusting the
Note to Payee
Assigning payment medium format and note to payee
Creating, Assigning, and Transporting
Selection Variants
2. Creating Payment Media
Creating payment media without documents in file form

Output of the created data media into DME administration
DME administration supports both files stored in the TemSe or the file system, and payment messages like Internet payments (OFX) or IDoc.
Creation of payment advice notes

Output of the created payment advice notes as letter, fax, or IDoc
Creation of an output log (an error log too, if necessary) for each program run of the payment medium program
Constraints
At the present time, not all formats that can be created using the classic payment medium programs (RFFO*) are supported. You can display a complete list
of available payment medium formats in format definition, or by using input help (in configuration of payment methods in the country, for example).
!--a11y-->
1.1 Creating Payment Media
Purpose
The following describes creation of payment media using the
Payment Medium Workbench.
Prerequisites
When you configure the payment program you decide whether you want to use the classic payment medium programs or the Payment Medium Workbench .
You have to make this decision for every combination of country/payment method and sometimes supplement the data.
PUBLIC Page 3 of 27
To do this, in Customizing for Financial Accounting choose Accounts Receivable and Accounts Payable
® Business Transactions ® Outgoing Payments ® Automatic Outgoing Payments ® Payment Method/Bank Selection for Payment Program ® Set Up
Payment Methods per Country for Payment Transactions .
Use Payment Medium Workbench
In the screen Change View "Payment Method/Country": Overview select the required combination of payment method/country with a double-click.
The Change View " Payment Method / Country ": Details screen appears.
2. In the screen area Payment medium select the option Use payment medium workbench .
3. In the same screen area enter or check the Format and the Format supplement and save your entries.
Checking Formula Entries
In the upper screen area choose Use in company codes .

The system displays the Display View " Maintenance of Company Code Data for Payment Method ": Overview screen .
2. Choose the change mode and select your company code by double-clicking on it.
The system displays the Change View " Maintenance of Company Code Data for a Payment Method ": Details screen.
3. Choose Form data and check or supplement the existing formulas for your company code.
4. Save your data and choose Exit .
The Change View " Payment Method / Country ": Details screen appears again.
Check Note to Payee by Origin
In the selection tree choose Note to Payee by Origin .

The Change View " Note to Payee by Origin ": Overview screen appears.
2. Check or supplement the existing note to payee.
3. Choose Back.
4. The Change View " Payment Method / Country ": Detail screen appears again, and you should now save the data.
Process Flow
Creation of payment media
Creation of payment media using the Payment Medium Workbench involves several steps.
Customizing for payment media
You decide that you want to use the Payment Medium Workbench for the particular payment method.
You check the existing payment medium formats and make any necessary changes .
You configure the note to payee.
You maintain the
Selection Variants as prerequisite for the automatic scheduling of payment media by the payment program.
Creation of payment media using the generic payment medium program
You start the payment program and select the option Create payment medium during scheduling of the update run. In the payment run parameters, a
variant has only to be defined for the payment advice note print program of the Payment Medium Workbench .
Directly following the payment run, the payment balance is sorted automatically and split into groups according to the level of detail, for creation of the
payment media in the next step.
For each group, the payment medium program is started with the variant defined in Customizing. It selects the payments belonging to each group and
creates the payment medium using the format-specific event modules/mapping rules.
The payment medium is transferred to DME administration.
Parallel to step 3, the payment advice note program creates the necessary payment advice notes as letter, Idoc, or Fax (using Business Transaction
Events 00002040).
Result
The Payment Medium Workbench programs create:
Data media
PUBLIC Page 4 of 27
Payment advice notes
Output logs
Error Logs
!--a11y-->
1.2 Payment Medium Format
Definition
The payment medium format controls how payment orders and debit memo orders to the bank are created. The specifications (published by the banks or the
central banking committees) of the formats serve as the basis for definition of payment medium formats.
Example
Payment medium without documents: DME or Internet payments

Country-specific formats: ACH, DTAUS0
The Payment Medium Workbench contains a range of predefined formats, like the DTAUS0 format for domestic payment transactions in Germany, ACH for
domestic payment transactions in USA, and OFX for Internet payments via OFX.
To create a format, in Customizing for Financial Accounting, choose Accounts Receivable and Accounts Payable
from Payment Medium Workbench ® Create Payment Medium Formats .
To change a format, in Customizing for Financial Accounting, choose Accounts Receivable and Accounts Payable
from Payment Medium Workbench ® Adjust Payment Medium Format .
Formats contain various fields that are filled with field contents from your SAP system. This transaction is called mapping. There are two ways in which
mapping can occur.
With/to programmed function modules
Using the
Data Medium Exchange Engine
Use
The payment medium format can be country-dependent or country-independent and is assigned to one or more payment methods.
Structure
The following settings are made during definition of a format:
1. Payment medium type (DME, for example)
2. Level of detail of the payment medium
This is the level at which payment orders should be grouped in a file (for example creation of a file per combination of house bank and paying company
code).
3. Format-specific parameters
4.
Payment Medium Format Supplements (for example format-specific description for bank transfer and debit memo)
Events that call function modules, connection to DME Engine
Size of text fields for the
Note to Payee
Example
The note to payee for the German format DTAUS0 is described as follows:
13 x 27 bytes of space for the main note to payee (body text of 13 lines each with 27 characters)
1 x 11 bytes of space for the internal short reference
1 x 27 bytes of space for the external short reference
With the previous classic method for creation of payment media, the format is implemented as a program whilst the structure of the note to payee is
predefined.
!--a11y-->
1.3 Payment Medium Format Supplement
Definition
This is the key that facilitates the commercial description of data for the selected payment medium format. This is printed in the coding line of the payment
medium or copied into the appropriate field with data medium exchange, for example.
Thus, with debit memos, we can distinguish between collection procedure and direct debiting procedure.
PUBLIC Page 5 of 27
Use
You only use the payment medium format supplement if there is provision for this in the format specification.
In Germany, the payment medium format supplement is called Text key (Textschlüssel) .
!--a11y-->
1.4 Note to Payee
Definition
A note to payee is a field on a data medium containing information on paid line items relevant for the business partner.
Number and length of the note to payee fields are defined in the payment medium format, whilst the content itself is defined in the note to payee.
Use
SAP provides predefined notes to payee that you can adapt for your own formats. Notes to payee are structured according to the following methods:
With Customizing in SAPScript format
With a function module
With a combination of Customizing and function module
To adapt a note to payee, in Customizing for Financial Accounting, choose Accounts Receivable and Accounts Payable
from Payment Medium Workbench ® Adjust Note to Payee .
Structure
The note to payee consists of a maximum of 6 different line types:
1. Main note to payee for description of the payment, for example with the payment of invoices in the lines there is the invoice number, the invoice date,
and/or the invoice amount.
2. Internal short reference for your company for identification of the transaction in case of failed payment. This could be the number of the payment
document, for example.
3. External short reference for your business partner, a contract/customer number, for example.
4. Payment advice note that replaces the lines of type 1 where there is not sufficient space available.
5. and 6. See
Alternative Payer, Alternative Payee.
Integration
The note to payee is independent of format, a separate entity that exists alongside the formats. You can assign the note to payee to a format via the payment
method and the origin. You can assign a note to payee to several formats, thus minimizing the effort involved.
Example
Line type 1 Main note to payee line 1 No. 746 999 from 01.01.2000
Line type 1 Main note to payee line 4 Visit our homepage: www.sap.com
Line type 2 Internal short reference Payment document 6 785 987
Line type 3 External short reference Our account with you: 345 876
!--a11y-->
1.4.1 Alternative Payer, Alternative Payee

Note to payee structure
PUBLIC Page 6 of 27
This example shows in combination in the Payment Medium Workbench how you can handle two special cases, namely the alternative payer and the
alternative payee.
The Note to Payee consists of up to 6 different line types. Line types 5 and 6 are intended for following special cases:
Line type 5 supplements the text of line type 1 through specification of an invoicing party where the payment is made to an alternative payee.
Line type 6 supplements the text of line type 1 through specification of an invoice recipient where the payment is made from an alternative payer.
!--a11y-->
1.5 Selection Variants
Use
If you wish to use the
Payment Medium Workbench for creation of payment media, you have to enter selection variants for the generic payment medium program. These do not
have to be entered as parameters for every payment run, as is the case for the classic payment medium programs (RFFO*), rather they are maintained
centrally.
Prerequisites
In Customizing for the
Payment Medium Format, choose Adjust Payment Medium Format and determine the level of detail. The level of detail governs how payment media are
output in payment groups. In selection variant maintenance, the system displays all defined payment groups that each require assignment of one selection
variant.
Procedure
You can enter, assign, and transport selection variants for the generic payment medium program.
Assigning selection variants
At least 1 variant is defined in each payment group for each payment medium format. It is important to assign a selection variant to each group to ensure that
no payment is forgotten.
1. To assign a selection variant, in Customizing for Financial Accounting, choose Accounts Receivable and Accounts Payable
from Payment Medium Workbench ® Create/Assign Selection Variants .
On the left side of the screen, select the payment medium format to which you want to assign a variant. The system displays the format on the right side
of the screen. In order to make the list easier to work with, you can use Drag&Drop to copy formats to the favorites list.
When you place the cursor over a selection variant field and press F4 (input help) the system displays possible variants. Choose the variant you require.
Carry out assignment for each individual group level. You can speed up this process by using filter, copy, selection, and paste functions.
Save assignment of the selection variants.
Creating selection variants
To create a selection variant, in Customizing for Financial Accounting, choose Accounts Receivable and Accounts Payable
On the left side of the screen, select the payment medium format for which you want to create a variant. The system displays the format on the right
side of the screen.
Place the cursor over a selection variant field, enter a name for a new variant, and press continue.
The system displays a dialog box where you confirm variant creation.
The system displays the selection screen of the generic payment medium program SAPFPAYM.
Here, you enter the required selection criteria, then you maintain the attributes before saving the variant.
Choose Back to return to selection variant maintenance for the payment medium formats.
Save assignment of the selection variants.
PUBLIC Page 7 of 27
If you want to work with Dynamic selections you can enter several variants per group using the procedure described above ( Variant
® Enter further variants ). You should only use Dynamic selections to define selection variants where no alternative exists. After this, you need to ensure
that no payment order has been carried out in duplicate and that only 1 payment medium has been created for each order.
You can increase the level of detail in Customizing ( Adjust Payment Medium Format ) as an alternative to Dynamic selections .
Transporting selection variants
In selection variant maintenance for payment medium creation, it is possible to branch to transport of the settings made and the selection variants for payment
medium creation themselves.
1. To carry out the transport, in Customizing for Financial Accounting, choose Accounts Receivable and Accounts Payable
To transport the selection variants, choose Transport variants to all formats .
To transport selection variant assignment, choose Transport settings to all formats . You can decide whether you transport the currently selected
format or whether you transport all formats.
Result
The payment program starts payment medium creation using each selection variant entered.
!--a11y-->
1.6 Data Medium Exchange Engine
Use
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 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 as there is no worldwide or regional standard format. In some cases, no country
standard exists and 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 now 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 a format tree in the DME Engine, calling applications can use it to:
· Generate an outgoing DME file as a flat file or an XML file
· Convert an incoming DME file to a format that the R/3 System can process
Features
The system comes complete with predefined format trees, which represent the file format requirements in a number of countries.
You can also transport format trees to other systems, or alternatively upload and download as XML files.
!--a11y-->
1.6.1 Outgoing File
Definition
A data medium exchange (DME) file that you send – for instance, to your bank or tax authority – either as a flat file or in XML format.
Integration
You model the external format file as a format tree in the DME Engine. The following application areas (tree types) in Financial Accounting can then use
format trees to create an outgoing file:
· Payment Program (tree type PAYM)
The system can trigger the creation of a DME file from the payment program if, for example, you want to submit your vendor payments to your bank
electronically. For this tree type, you use the Payment Medium Workbench (PMW) to configure payment media.
When you execute a payment run, the system triggers the generic payment medium program of the PMW for creating payment media. The PMW format
uses the DMEE format tree to create the file to be sent to your bank. In this case, the system requires special configuration of the corresponding payment
method.
· Advance Return for Tax on Sales and Purchases (tree types UMS1, UMS2, and UMS3)
You run program RFUMSV00 to create an advance return for tax on sales/purchases for UMS1, and additionally program RFUVXX00 for UMS2 and
PUBLIC Page 8 of 27
UMS3. For further details, see UMS1, UMS2, and UMS3 Tree Types.
· Generic Withholding Tax Reporting (tree type WTRE)
You can use this program (RFIDYYWT) to prepare a withholding tax return as a DME file. Under Files , set the Create File indicator and specify a file
name. You do not enter a format tree directly; rather, the system takes the information it needs from the process type and output group you specify.
· EC Sales List (tree type ASLD)
To create an EC sales list as a DME file, you need to run report RFASLD20 (and not the standard report RFASLM00). Under Output control , you specify
the format tree to be used (in the DMEE tree type field), as well as the name the file is to be saved under.
· 1099-C Cancellation of Debt (tree type DEBT)
To create a DME file for 1099-C reporting for the United States, you run report RFIDUS99C. Under Output , specify format tree IDUS99C_1099C, as well
as file information.
From a technical view, the calling application carries out the following steps:
1. Selects data and fills the transfer structure
2. Calls DMEE modules with the data that has been selected
3. Obtains an internal table with data in format structure
4. Writes data to a file or to File/TemSe/... and, in the case of tree type PAYM, possibly updates DME administration
Note that a Business Add-In is available that enables you to modify the internal table (in step 3 above) before the DME Engine saves the file (step 4). You find
the BAdI in Customizing for Cross-Application Components , under General Application Functions ® DME Engine ® Business Add-Ins ® Outgoing Files
® BAdI: File Modification .
Creating Format Trees

To create a format tree for outgoing DME files, follow the standard procedure. Note, however, that a few of the steps contain information specific to outgoing
files:
· Defining header data
· Creating nodes
· Mapping data
!--a11y-->
1.6.1.1 Customizing Payment Methods for Use with DMEE

If you use a Data Medium Exchange Engine (DMEE) format tree of tree type PAYM to generate a DME file for a given payment method, you need to make a
number of related settings for the
Payment Medium Workbench (PMW).
In Customizing for Financial Accounting (FI), choose Accounts Receivable and Accounts Payable ® Business Transactions ® Outgoing Payments ®
Automatic Outgoing Payments ® Payment Media ® Make Settings for Payment Medium Formats from Payment Medium Workbench ®
1. Create Payment Medium Formats
Create a new format with the same name as your DMEE format tree. Choose the format output Payment medium without docs ., and type File . Under
Program control , set the Mapping using DME engine indicator. Once this indicator is set, the DME engine button appears, which allows you to
access the DMEE format tree directly.
Under Format information , specify your country. You can also write documentation for your PMW format by choosing the field help for the
Documentation module field. From there, choose Proceed , and a document maintenance screen appears. Select document class General text ,
enter a name for the text, and create the documentation. Lastly, enter the name of this text in the PMW format in the Documentation module field.
When you create your DMEE format tree, you also have the option of documenting it. The field help for the Documentation field (part of the
header data – Administrative data ) describes how to set a link from the DMEE documentation to the corresponding PMW format documentation.
Refer to the IMG documentation for the activity for further explanation of the other fields and dialog structure views.
2. Assign Payment Medium Format and Note to Payee to Payment Method
You need to specify that the PMW is to be used for the given payment method. To do so, double-click the payment method. Under Payment medium ,
set the Use 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 choose Enter , an i button appears next to the
format name. If you choose the Format settings button, you branch to the settings for the PMW format (the activity in step 1).
See also:
Delivered Format Trees

!--a11y-->
1.6.1.2 UMS1, UMS2, and UMS3 Tree Types

You create a format tree of the tree type UMS* to be able to generate an advance return for tax on sales and purchases. The three tree types differ in how the
data is summarized:
· UMS1: No summarization; data is output per line item
· UMS2: Summarization per tax code and/or transaction key
· UMS3: Summarization based on how you have customized the output
All three tree types can be used to generate a DME file as either a flat file or an XML file; this is defined in the format tree. Below are further details about
creating UMS* format trees and which program(s) you need to run to generate the corresponding output file.
PUBLIC Page 9 of 27
UMS1
You run the Advance Return for Tax on Sales and Purchases program; from the SAP Easy Access menu, choose Accounting ® Financial Accounting ®
General Ledger ® Reporting ® Tax Reports ® General ® Advance Return for Tax on Sales/Purchases ® Advance Return for Tax on Sales/Purchases
(or via Transaction SA38, program RFUMSV00). To create a file using an UMS1 format tree, choose the Posting Parameters button, then set the Create
DME File indicator, specify which format tree the system is to use, and enter a name for the file that is to be created. Run the program, and the system
generates a file.
UMS2 and UMS3

To select and prepare the required tax data, you first run the Advance Return for Tax on Sales and Purchases program (RFUMSV00), but do not set the
Create DME File indicator as above; instead, you must specify a program run date and an identification under Posting Parameters . Then, to generate the
file (flat or XML), you run the DME File for Summarized Advance Tax Return program (RFUVXX00). Follow the same menu path as above, and choose DME
File with Summarized Tax Data . To retrieve the data prepared by the prerequisite program, you need to enter the same program run date and identification.
Refer to the program documentation for further details.
Because UMS2 and UMS3 offer summarized tax data, the format trees are constructed a bit differently, as described below.
UMS2
The UMS2 tree type enables you to summarize per tax code or transaction key. When you create an UMS2 format tree, the source field inventory consists of
ABAP system fields and application-specific fields. The application fields (under For UMS2 ) include company code data, tax office data, and others, such as:
· Transaction key (KTOSL)
· Tax base amount (HWBAS)
· Tax amount (HWSTE)
· Tax on sales/purchases code (MWSKZ)
Assume, for example, that you work with tax codes A1 and A2, and you need to report postings of EUR 500 and EUR 200 for A1, and EUR 300 for A2. This
example describes how to summarize the A1 postings as EUR 700 and A2 as EUR 300; if you do not summarize by tax code, the output of the tax amount
will simply list EUR 1000.
To summarize the output as EUR 700 for A1, create a node Tax Amount A1 , specify the source as structure RFUMS2_TAX_ITEM and field HWSTE, and
assign a condition as follows:
Arg 1-1 Arg 1-2 Type Operator Arg 2-1 Arg 2-2 Type Operator
RFUMS2_TAX_ITE MWSKZ 2 = ’A1’ 1

M
This condition instructs the format tree to take the tax amount value (EUR 1000) in field HWSTE and list that portion of it with tax code A1 in this field (EUR
700).
You then create another node, Tax Amount A2 , with the same source structure and field; define the same condition, but with Arg 2-1 ‘A2’. In this case, the
condition instructs the format tree to list that portion of the tax amount value which was posted with tax code A2.
You repeat this step for as many tax codes as you need to summarize by.
UMS3
The UMS3 tree type differs from UMS2 in that it offers you 99 base amount fields (BAS01-BAS99) and 99 tax amount fields (STE01-STE99), whereas UMS2
only offers one field each for the tax base amount (HWBAS) and tax amount (HWSTE). The advantage of UMS3 is that you do not need to create conditions to
summarize by each of the tax codes. Instead, you define the summarization in Customizing and then map these values directly to the UMS3 format tree.
You configure the relevant settings in Customizing for Financial Accounting , under General Ledger Accounting ® Business Transactions ® Closing ®
Reporting ® Sales/Purchases Tax Returns ® Group Tax Base Balances or Group Tax Balances . To map these values to the format tree, choose
from the source field inventory fields under Source fields for application ® For UMS3 ® Advance Return for Tax on Sls/Pur., used for DMEE .
Using the sample amounts above, assume you have to report postings of EUR 500 and EUR 200 for A1 and EUR 300 for A2. The sum of all A1 postings must
be reported in field 6 on the tax form, and the sum of all A1 and A2 postings must be reported in field 10. In the Group Tax Balances activity, you specify the
following:
Tax Code Description Transaction Key Group No.
A1 16% output tax MWS 6
Then, in your UMS3 format tree, you map the group numbers from the Customizing activity to the corresponding source fields. So, in our example, you create
two nodes for each of the group numbers and assign the source fields BAS06 and BAS10, both from structure RFUMS3_TAX_ITEM.
Based on these Customizing settings and mapping to an UMS3 format tree, the output will be EUR 700 in field 6 and EUR 1000 in field 10.
!--a11y-->
1.6.2 Incoming File
Definition
A data medium exchange (DME) file that you receive – for example, an electronic bank statement from your bank.
PUBLIC Page 10 of 27
Integration
First, you model the external format file as a format tree in the DME Engine. Then, when you receive an incoming DME file, you convert it to the format
defined by the format tree.
Currently, the DMEE supports conversion into MultiCash format only (tree type MCSH).
If you need to modify the converted file before the system saves it, you can create a Business Add-In implementation in Customizing for Cross-Application
Components , under General Application Functions ® DME Engine ® Business Add-Ins ® Incoming Files ® BAdI: File Modification . This BAdI enables
you to change files based on a specific format tree, whereas the other BAdI for incoming files, BAdI: File Conversion , allows you to change all files for a
given tree type.
The R/3 System is then able to further process the file in MultiCash format. In the case of electronic bank statements, this could involve automatic posting
and clearing.
Creating Format Trees

To create a format tree for incoming DME files, follow the standard procedure. Note, however, that a few of the steps contain information specific to incoming
files:
· Defining header data
· Creating nodes
· Mapping data
In addition, some functions are designed specifically for formats for incoming files, namely defining optional supplementary segments and performing format-
specific checks.
!--a11y-->
Convert Format of Incoming DME File
Use
You use this program to convert incoming data medium exchange (DME) files to a format that the R/3 System can read and process.
Prerequisites
You have already created a format tree in the DME Engine that models the format of the DME file you are importing.
You have activated a standard Business Add-In implementation (or created your own) if either or both cases apply:
· Before the system saves the files it creates with this conversion program, you need to change one or both of them.
· The system is to automatically call a processing program once it has generated the MultiCash files (see Posting below).
You find the BAdI in Customizing for Cross-Application Components , under General Application Functions ® Data Medium Exchange Engine ® Business
Add-Ins ® Incoming Files ® BAdI: File Conversion . Note that this BAdI is for use with all files of a given tree type, whereas the other BAdI for incoming
files, BAdI: File Modification , enables you to change files based on a specific format tree.
Activities
To access the program, from the SAP Easy Access menu, choose Accounting ® Financial Accounting ® Banks ® Incomings ® Bank Statement ®
Convert with DME Engine .
When you run the program, fill out the following group boxes:
· DMEE: Format Details
Specify which tree type (currently, only MCSH) and format tree the program is to use to convert the incoming file.
· Incoming DME File
Specify where the program is to read the incoming file from, and its name and record format.
· Converted DME File
Specify where the incoming file, once converted, is to be written to, as well as a name for the converted file. If the program generates two files in the
conversion process (as is the case for tree type MCSH), then you only enter one file name and the system automatically creates two files from it. For
example, if you enter name.txt as the file name, the system then creates name_1.txt and name_2.txt.
· Logs
If you want the program to perform the checks for the incoming file (defined in the DMEE format tree you are using in the conversion) and to generate
a log containing the results, set the Generate Check Results indicator (refer to the field help for further details).
We recommend that you always set this indicator (it is set by default), because if you deselect it and errors occur during the file check, the
system still creates a converted file (which would be erroneous in this case).
You also have the option of logging all or selected data contained in the incoming file.
If you select both log options, the system displays the results in a single log.
· Posting
Here, you can specify that you want the conversion program to transfer the file to another report for automatic further processing (such as posting and
clearing of electronic bank statements). For more details on this option, refer to the field help.
!--a11y-->
1.6.3 Creating Format Trees
1. Call the DME Engine by entering transaction DMEE.
2. Choose a tree type.
3. Enter a name for the format tree, usually the name of the format itself.
For PAYM format trees, you need to create a corresponding Payment Medium Workbench (PMW) format as described here. The PMW format
and the DMEE format tree must have identical names, so if you have already created the PMW format, be sure to enter the same name for the
DMEE format tree.
4. Choose Create .
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 DMEE: Create Format Tree <format tree> screen appears.
6. Maintain data for the root node, called the header, which appears automatically.
7. Insert nodes hierarchically to represent the DME file layout description, and maintain the detailed view as needed for each node type.
8. Define a mapping procedure for each node that serves as a source field (for outgoing files) or a target field (for incoming 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 that enable you to model your
format description as a format tree, such as aggregation.
9. Activate the format tree.
Once active, the format tree can be accessed and used as needed by calling applications.
!--a11y-->
1.6.3.1 Screen Layout

After you specify a tree type and a unique format tree ID on the initial screen of the Data Medium Exchange Engine (DMEE), the DMEE: Create Format Tree
<format tree> screen appears. It is divided into three parts:
1. Tree structure
On the left side of the screen, you define your format tree by inserting nodes in a hierarchical structure.
2. Detailed view
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 ( ).
3. Source/target fields
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 the
source/target field inventory; you can select from them during the data-mapping process.
!--a11y-->
1.6.3.2 Header
The root node of the Data Medium Exchange Engine (DMEE) format tree contains technical settings and properties that apply to the entire file. Depending on
whether the format tree represents an incoming or outgoing file, you maintain different data on the detailed view to the right of the tree structure:
Header data for outgoing files

Header data for incoming files
For more information on the individual fields, refer to the field help.
!--a11y-->
1.6.3.2.1 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 the Documentation 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 the Documentation 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).
The version 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 the Sort/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.
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 both Key Field and No 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 the Format 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:
· Do Not Allow These Charact. ® The system removes the specified characters from the character string.
· Allow Only These Charact. ® The system removes all other characters from the character string except for the ones specified here.
!--a11y-->
1.6.3.2.2 Header Data for Incoming Files

You maintain the following information, displayed on the various tabs, for format trees representing incoming 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 the Documentation 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 the Documentation 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).
The version 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 whether the fields have a fixed position in the file or are separated by delimiters.
Assignment Rules
Each data record in an incoming file must contain a character string that uniquely identifies the record (called the identifier in the format tree). To model the
format of the incoming file, you define a segment for each record and assign each segment a reference ID. Then, in the assignment rules, you assign the
reference IDs to the identifiers in the incoming format, which links the records to the corresponding segments and allows the DME Engine to correctly convert
the levels of an incoming file. The ID offset identifies the number of characters that come in the string before the identifier.
To illustrate how assignment rules work, refer to the template format tree SAP_EXAMPLE (tree type MCSH):
Assignment Rules for SAP_EXAMPLE
Rule No. Identifier ID Offset Ref.ID of Tgt Segmt
1 HD 0 HEADER
2 BP 0 BUPA
3 PM 3 PAYM
4 VW 0 VWZW
5 TR 0 TRAILER
This format tree models a file format that contains five types of information: header, business partner, payment, note to payee (optional), and trailer. The file
marks the beginning of its header with HD and the beginning of its trailer with TR, represented by the reference IDs HEADER and TRAILER. Between these
records come business partner records (identified by BP), then payment data (identified by PM starting with the third character of the string), followed by the
note-to-payee information (identified by VW).
!--a11y-->
1.6.3.3 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.
In format trees for the payment program (tree type PAYM, flat-file format), you can specify output options (on the Node info tab) and
conditions for segments, while elements can be assigned a mapping procedure and the corresponding origin, aggregation, and condition
information. You can additionally enter up to three lines of comments, on the Comment tab, for each node type except for the header.
!--a11y-->
1.6.3.4 Node Types

Each node type performs a different function and various data can be maintained accordingly in the detailed view. You create format trees for outgoing and
incoming DME files using some of the same nodes, while others are unique. For an overview of the node icons and their respective use in the format tree,
refer to:
Nodes for outgoing files

Nodes for incoming files
For additional information on nodes and when to use certain node types, choose Extras ® Node legend on the DMEE: Create/Change Format Tree
<format tree> screen. The system displays the appropriate node legend, depending on which type of format tree you are in.
!--a11y-->
1.6.3.4.1 Nodes for Outgoing Files

The node types and their functions vary depending on the format of the outgoing file to be generated:
· Flat files
· XML files
!--a11y-->
Node Types for Flat Files

Below is an overview of node types used in the Data Medium Exchange Engine (DMEE) for defining outgoing flat files:
Node Use
Segment group Used to group segments
Segment Represents a record in the target file
Composite Used to group elements
Element Represents a target field of the DME file
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)
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
!--a11y-->
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)
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)
!--a11y-->
1.6.3.4.2 Nodes for Incoming Files

Below is an overview of node types used in the Data Medium Exchange Engine (DMEE) for defining incoming files:
Node Use
Segment Represents a record in the target file;

optional supplementary segments are also possible
Element Represents a target field of the DME file
Action node Represents a subnode of an element; it does not correspond to any

information from the incoming files, but it used to define special mapping rules
Check segment Stores checks that are valid for the entire incoming file; the check segment is
run once at the end of processing
Technical node Stores a value that is used in other tree nodes by a reference to this node;
used primarily for storing aggregated values that are used in file checks
!--a11y-->
1.6.3.4.2.1 Optional Supplementary Segments
Use
You define optional supplementary segments in format trees for
incoming files to identify a data record that corresponds directly to the previous record, but which is not mandatory in the file.
For instance, a file may contain payments per business partner, and sometimes a note to payee is included with the payment. You represent the payment with
a payment segment, and the note to payee with an optional supplementary segment.
Activities
You create a supplementary segment as a normal segment, and assign it a reference ID and the same level as the segment it is to correspond to. Then, in the
segment that the supplementary segment corresponds to, you enter the supplementary segment's reference ID on the Opt. Supplem. Segments tab; the
system then knows that the two segments belong together.
You also need to enter optional supplementary segments in the assignment rules in the
header data.
Example
To illustrate how optional supplementary segments work, refer to the template format tree SAP_EXAMPLE (tree type MCSH). It contains the following
segments, with the note to payee being an optional supplementary segment to the payment:
Segment Reference ID Level
Header record HEADER 1
Business partner BUPA 2
Payment record PAYM 3
Note to payee VWZW 3
Trailer TRAILER 1
Assume your incoming file contains the following data records:

HEADER------------------------------------------------
BUSINESS PARTNER------------------------------
PAYMENT 1-------------------------------------------
PAYMENT 2-------------------------------------------
NOTE TO PAYEE------------------------------------
PAYMENT 3-------------------------------------------
Based on the format tree, the DME Engine reads the payments of the business partner and writes them to the converted file. For payment 2, it recognizes that
a note to payee is included, and writes it together with the payment record.
!--a11y-->
1.6.3.5 Data Mapping
Use
The last step in creating a DMEE format tree is to define how data is to be mapped. Outgoing and incoming DME files represent opposite cases regarding the
data mapping:
In the case of
outgoing files, you map internal R/3 source fields to the target fields in a DME file. The tree type determines which R/3 structures and tables are available for
mapping (such as FPAYM for the tree type PAYM).
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 R/3 System can process further).
Features
Based on the tree type of your format tree, the system selects all R/3 fields that are predefined for the particular application. These 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 R/3 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 R/3 fields.
There are several mapping procedures, and they differ for outgoing and incoming files. The most common procedures are direct reference to R/3 fields or
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.
!--a11y-->
1.6.3.5.1 Mapping Outgoing Files

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
Own mapping (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:

a. If you choose one of the following mapping procedures, enter source data in the appropriate fields on the Source tab:
§ Constant
§ Structure field
§ Reference to tree node
§ Exit module
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
procedure Structure field . To specify the source field, you can enter the source field and structure directly under Source , or you can select a
field from the source field inventory.
b. If you choose Aggregation as the mapping procedure, enter data as required on the Aggregation tab.
c. If you choose Own mapping (atoms) as the mapping procedure for the element, you create as many atoms as you require in the form of subnodes
to the element. You then specify a mapping procedure and source information for the atoms.
5. You can specify a conversion method used to convert 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.
!--a11y-->
1.6.3.5.2 Mapping Incoming Files
Insert an element (or action node as a subnode to an element) in the format tree structure on the left.
The system automatically displays the detailed view for the node in the right frame. This includes the following tabs: Attributes , Mapping , Conditions ,
File Checks , and Comment .
Enter the required attribute information.
You can specify a conversion method used to
convert 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 incoming file.
Select a mapping procedure on the Mapping tab.
Mapping procedures:
Select mapping procedure If
Structure field A file value or a constant is to be mapped to a specific target field in the R/3
System.
Action nodes Your mapping rules are dependent on

conditions or if different parts of the element are to be filled into different
targets.
You then create as many action nodes as you require in the form of subnodes
to the element, specifying a mapping procedure and target information for
each action node. You must create at least one action node if you choose this
mapping procedure.
Exit module The standard mapping and conversion rules do not meet your requirements
and you wish to specify an exit module.
No mapping Data in the incoming file is not to be mapped to a target field in the converted
file.
You can log this non-mapped data in the
conversion program by specifying that values not mapped to target fields are
to be included in the file-data log.
In most cases, you specify that the source field in the incoming file is to fill one target field in the converted file, which corresponds to the mapping
procedure Structure Field . For this mapping procedure, you also need to specify the target structure, target field, and target offset. You can enter the
target structure and field directly, or you can select a field from the
target field inventory.
!--a11y-->
1.6.3.5.3 Source/Target Field Inventory

For each DMEE tree type, a set of possible source fields (for
outgoing files) or target fields (for incoming 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.
The source/target field inventory can consist of the following fields, depending on the tree type:
Source/target fields for the application
These fields are dependent on the particular application.
ABAP system fields
These fields are made available for each application. An example is the system date.
Technical 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.
Source fields for note to payee (internal table)
These fields are specific to the tree type PAYM (payment program). If the appropriate settings are defined in Customizing for Payment Medium
Formats for the Payment Medium Workbench and you select one of these fields as your source field, then a value will be filled in this target field.
Parameters and source fields from Customizing
These fields are specific to the tree type WTRE (withholding tax reporting). By choosing one of these fields, you map data that has been defined in
Customizing and that remains unchanged.
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.
!--a11y-->
1.6.3.5.4 Conversion of Source Data
Use
This function converts source field data to a particular format for the DME file. You can specify a conversion method for any of the mapping procedures
available for elements, atoms, and action nodes.
The system supports conversion rules for the following field types:
· Date
· Time
· Currency amount
· Character string
If you require an additional conversion method, you must specify an exit module for the node.
Activities
First enter the source information, then choose on the Attributes tab; the system restricts selection criteria and displays the conversion rules that apply to
the particular field type. Or, you can choose from all available formats via the input help.
Available formats
For field type You can specify a combination of the following data:
Date · Day, month, and year sequence

· Number of characters for year: two or four
· With or without separator
· Type of separator: slash or period
· Year, month, or day only
· Year and number of days since January 1
Time · Hour, minutes, and seconds sequence (with or without seconds)

· With or without separator
· Hour only
· Conversion to time stamp
Currency amount · Number of decimal places

· Decimal formatting: period, comma or none
· With leading zeros
· Left- or right-justified
· Output decimal value as 0 (round down)
· Arithmetic rounding to nearest decimal place allowed by the output format
(0.5 rounds up)
Character string · Left- or right-justified

· Left-justified with ending zeros
· Right-justified with leading zeros
· All characters in upper case (capital letters)
· Replace national characters
· Remove special characters
· Replace leading zeros with space
· Convert to numeric characters
· Exclude/allow defined characters
!--a11y-->
1.6.3.5.5 Aggregation
Use
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.
The aggregation function can be used at the end of a level or a file to:
Add the total value of specified nodes
In this case, you can only specify aggregation nodes that are filled with values (elements).
This could be the amount of all payments in a level.

You can also specify that the absolute values are to be added, which means that the system ignores the + and - signs.
Add the number of nodes
In this case, you can specify any aggregation nodes because the system totals the number of occurrences, not specific values.
This could be the number of payments in a level.
Activities
Outgoing Files
You can define an aggregation for elements or atoms. When you create either of these nodes, select the mapping procedure Aggregation . On the
Aggregation tab, you enter the reference IDs of the nodes you wish to aggregate and the aggregation type – how the aggregation nodes are to be totaled to
the target node (either summation of values or of total number of occurrences).
Incoming Files
You define an aggregation using a technical node. Assign it a reference ID and set the Aggregation node indicator on the Attributes tab, and enter the
reference IDs of the nodes to be aggregated and how they are to be aggregated on the Aggregation tab. The technical node stores the aggregated value,
which can then be used to:
Define a
condition or a file check
Map the aggregated value to a target field in the converted file
!--a11y-->
1.6.3.6 Conditions
Use
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 any node 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.
For incoming files, you can only define conditions for elements, action nodes, or technical nodes.
Activities
You define a conditional relationship for a node in the detailed view under Conditions , which displays a condition list that looks like this:
Arg1-1 Arg1-2 Type Operator Arg2-1 Arg2-2 Type Operator
x x x x x x x x
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 out 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:
- Constant, then leave this field blank.
- Structure field, then enter the field name (which you can take from the source field
inventory).
- 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, see
Comparing 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.
Examples
Format tree LM03 (tree type PAYM) is used to generate DME files for domestic payments in Finland. The following examples illustrate the use of conditions at
the element and segment levels.
Element Level
Within the batch record, a currency value is to be filled, which is represented by an element called Currency : it should be filled with a constant, 1, if the
currency read from the system field WAERS is EURO, and 0 if it is FIM (Finnish Markkaa) – defined at the element level with the mapping procedure
Constant . This is modeled in the format tree as two atoms beneath the Currency element, each one establishing a condition:
EURO (if condition is met, the format tree fills the constant 1)
FPAYHX WAERS 2 = 'EUR' 1
FIM (if condition is met, the format tree fills the constant 0)
FPAYH WAERS 2 = 'FIM' 1
Segment Level
Further along in the batch record, conditions are used to determine which segment is to be output. In the segment group Transaction Record , under
Specification Record , the tree contains two segments: Specification Transaction Record 1 and 2 .
LM03 outputs segment 1 if the value in structure FPAYP, field WRBTR (amount in foreign currency with +/- signs) is greater than 0. If it is less than or equal
to 0, this entire segment including its subnodes is ignored, and segment 2 is processed instead.
!--a11y-->
1.6.3.5.7 Exit Modules
Use
You can implement an exit function module to:
Define additional
mapping rules if the standard mapping and conversion rules do not support your requirements (for outgoing and incoming files)
You can also select data from additional database tables not included in the standard selection step (such as customer database tables) and therefore
not made available in the
source/target field inventory. The exit module can, however, use the same source/target fields as the standard mapping rules.
Define additional
file checks (for incoming files only)
Prerequisites
You have already created the function module you want to implement in the format tree.
You write ABAP source code in the ABAP Workbench – not in the DME Engine.
To create your exit module, you can use the following template function modules:
Outgoing: DMEE_EXIT_TEMPLATE or DMEE_EXIT_TEMPLATE_EXTENDED
Incoming: DMEE_EXIT_TEMPLATE_IN_MAPPING
Activities
Outgoing Files
You can specify exit modules for elements and atoms. When you create one of these nodes, select the mapping procedure Exit module . On the Source tab,
you then enter the name of the exit function.
Incoming Files
You can specify exit modules for elements, action nodes, and technical nodes. For use in mapping rules, enter the exit module on the Mapping tab and
select the corresponding radio button. For use in file checks, enter the exit module on the File Checks tab.
!--a11y-->
1.6.3.6 Conditions
Use
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 any node 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.
For incoming files, you can only define conditions for elements, action nodes, or technical nodes.
Activities
You define a conditional relationship for a node in the detailed view under Conditions , which displays a condition list that looks like this:
x x x x x x x x
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 out 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:
- Constant, then leave this field blank.
- Structure field, then enter the field name (which you can take from the source field
inventory).
- 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, see
Comparing 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.
Examples
Format tree LM03 (tree type PAYM) is used to generate DME files for domestic payments in Finland. The following examples illustrate the use of conditions at
the element and segment levels.
Element Level
Within the batch record, a currency value is to be filled, which is represented by an element called Currency : it should be filled with a constant, 1, if the
currency read from the system field WAERS is EURO, and 0 if it is FIM (Finnish Markkaa) – defined at the element level with the mapping procedure
Constant . This is modeled in the format tree as two atoms beneath the Currency element, each one establishing a condition:
EURO (if condition is met, the format tree fills the constant 1)
FPAYHX WAERS 2 = 'EUR' 1
FIM (if condition is met, the format tree fills the constant 0)
FPAYH WAERS 2 = 'FIM' 1
Segment Level
Further along in the batch record, conditions are used to determine which segment is to be output. In the segment group Transaction Record , under
Specification Record , the tree contains two segments: Specification Transaction Record 1 and 2 .
LM03 outputs segment 1 if the value in structure FPAYP, field WRBTR (amount in foreign currency with +/- signs) is greater than 0. If it is less than or equal
to 0, this entire segment including its subnodes is ignored, and segment 2 is processed instead.
!--a11y-->
1.6.3.7 User-Defined Incoming File Checks
Use
You can configure your own file-specific checks that are to be carried out on incoming DME files when you run the
conversion program. In the checks, you define that certain conditions are to be met before the file is converted. These checks refer to individual fields in the
file; you can also define a check segment that runs once at the end of processing and stores all checks that are valid for the entire file.
If you cannot represent a check using the statements provided in the DME Engine, you can create a
function module to perform the check and enter it here.
Features
If a condition you define is not met, you define how the system is to respond when you run the conversion program:
System is to generate a warning
System is to generate a error
Conversion program is to terminate
Standard messages are available for each of these system responses, or you can create your own message and specify it here.
Integration
If you set the Generate Check Results indicator in the conversion program and the defined check condition is not met, the system responds as follows:
System Response Related System Actions

Defined in Check
Warning Always creates a converted file;

Displays a log
Error Does not create a converted file if at least one error occurs;
Displays a log
Termination Always terminates the conversion program (even if the indicator above is not
set);
Does not create a file;
Does not display a log (only an error message)
If you deselect the Generate Check Results indicator, be aware that the program creates a converted file – even if errors occurred during the
conversion program.
Example
You want to check that the amount of all payment records sent in an incoming file must be identical to the total amount contained in a separate Total amount
element.
First, you create a technical node to
aggregate the values of the payment records with the reference ID "CHECK_TOTAL". You then compare this aggregated value against the value of the Total
amount element. Create a Total amount element and define the following check on its File Checks tab:
File Checks
Segment Operator (Logical) Arg2-1 Arg2-2 Type Operator (Linking)
Total amount = CHECK_TOTAL 1A 3 leave blank
The system automatically copies the current node to the beginning of the file check. You then define that the amount in the Total amount segment is to be
equal to the value in the node with the reference ID "CHECK_TOTAL". Type 3 indicates that the argument (Arg2-1) refers to a reference ID, so you need to
enter the node attribute that is to be checked in Arg2-2, which is contents in internal format (1A) in this case.
The value you specify for Arg2-2 depends on the type of argument (1=constant, 2=field of a target structure, 3=reference ID), so there is no input
help for the field. If the argument refers to a reference ID, you need to enter the node attribute that is to be checked in the condition. For possible
input values, refer to the field help for Arg2-2 and click on the node attribute link.
When the system converts an incoming file with this format tree, it checks that the total amount in the incoming file is the same as the aggregated value of all
payment records. If the amounts are not equal, the system creates a warning or error message in the log, or terminates the conversion program – as defined in
the file check.
See also:
For more information on possible logical operators in the check, see
Comparing Strings.
!--a11y-->
1.6.4 Activating Format Trees
Use
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
Complete maintenance of the format tree.
Choose Format tree ®
Activate or .
The system checks 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.
See also:
Version Management
!--a11y-->
1.6.4.1 Format-Tree Checks
Use
The system checks the format tree to prevent inconsistent data from being used when a file is generated or converted. You can execute a check manually at
any time in the format-defining process. In addition, the system performs a check automatically when you activate your format tree.
Activities
To perform a manual check, choose Format tr ee ®
Check or . The system carries out the following checks:
Syntax check
Consistency check (such as reference to node attributes)
Correct level distribution
Check for completeness
If the check generates error or warning messages, the system displays a log. The log indicates the type of message (red for error, yellow for warning, green for
information) and a short text. The text of an error message – which must be corrected in order to activate a format tree – is additionally highlighted in yellow. If
a long text is available for the message, you can display it by choosing .
After a log has been generated, you can display it by choosing Goto ® Log or .
!--a11y-->
1.6.5 Testing Active Format Trees
Use
The DME Engine includes a testing function, which enables you to test active
versions of format trees before they are used to generate a file.
This function is intended for small-scale tests only. You can employ it, for example, to test the effects of new conversion rules or to determine if the offset is
correct within a line or record. It is not intended to check an entire format tree – but rather a few lines – as it is very difficult to manually generate all application
data correctly.
Activities
On the initial screen of the DME Engine, choose Format tree ® Test active version or .
The DMEE Test Data screen appears. The system displays the source structures for the particular application, each followed by the most commonly
selected source fields for that structure. If you need to test fields not included here, you can add fields via the standard layout function.
Next you enter the data you wish to test.
Only enter data in those fields that are specified in the format tree as actual source fields.
To start the test, choose File ® Test or .
On the Data output dialog box that appears, the system displays in list form the results for the data you entered as they would appear in an actual DME
file.
If you do not enter data in the fields for which mapping rules are defined in the format tree, these fields remain empty when the test version is
output. Fields defined as constants are output accordingly.
See also:
Activating Format Trees

!--a11y-->
1.6.6 Transporting Format Trees

You can transport the active version of a format tree to other systems. The logical transport object for a DMEE format tree is R3TR DMEE; this contains all
associated database tables. To transport a format tree, choose either Format tree ®
Transport or on the initial screen of the DME Engine.
The DME Engine also supports an upload/download of format trees as an alternative to the transport:
Upload format tree
You can upload a format tree that you have as an XML file. To do so, choose Format tree ® Upload XML file on the DMEE initial screen. You then
specify the file name and the presentation server or URL address.
Download format tree
You can download a format tree and create an XML file on your PC that contains all format tree information. To do so, choose Format tree ®
Download XML file on the DMEE initial screen. After you specify which version you wish to download (active or maintenance), you enter the tree
type, format tree ID, and a name for the XML file.
See also:
Version Management
!--a11y-->
1.6.7 Version Management
Use
You can use the version management functions of the DME Engine to:
Store different versions of a format tree, including temporary ones
Compare two versions
Generate a new version
Retrieve an older version
Features
Each format tree exists in the following versions:
Version 000 always refers to the active version of the format tree.
Calling applications use the active version to generate or convert a DME file. You can also
transport the active version of a format tree to other systems.
Version 001 always refers to the current maintenance version (see below).
SAP delivers more than 40
predefined format trees that cover various requirements for generating outgoing files in nearly 20 countries. For each of these format trees, SAP provides an
active version (000), which can be used to generate files without any further configuration in the DME Engine. Each delivered format tree also comes with
version 999, which is an SAP reference version that you cannot change. You can always display it, compare it against any other version, or retrieve it to
generate another version from it.
Creating New Format Trees
You can copy any of the delivered trees and use it as a template for creating a new tree – to cover any regional or bank-specific formats not covered by SAP.
Once you save a new format tree, the system saves it as version 001. Once you
activate the maintenance version, it is stored as version 000.
To create additional versions of a format tree, you can:
Generate a new version
The system creates a new version from the current maintenance version. The new version becomes the new version 001, and the former 001 is copied
to the next subsequent version available.
Retrieve and make a copy of an older version
You select the version you want to retrieve and choose Version ® Retrieve. The system copies this version's contents into a new version 001, and
converts the previous maintenance version into the next available version.
Maintaining Format Tree Versions
You always maintain version 001 of a format tree. To do so, specify the tree on the initial screen of the DME Engine and choose Change .
Delivered format trees come with versions 000 and 999. As soon as you modify one of these trees, the system creates a maintenance version,
001, from the active version, 000.
If you choose Utilities ® Versions ® Version Management , you will see that the versions in the development database are always 000 (once you have
activated your tree) and 001. The system also displays any versions that exist in the version database. If you are working with a delivered format tree, you will
see version 999 here, as well as any other versions you have created.
Comparing Format Tree Versions
You can compare any two versions of a format tree by selecting them and choosing Version ® Compare or . The system displays all differences that
exist between the two versions; you can limit the list by displaying changes made only in the header or node attributes, or by displaying only those nodes that
were deleted, inserted, or for which the output was delayed.
Example
Assume the following versions exist for your format tree:
Versions in the development database:
000 (active)
001 (maintenance)
Versions in the version database:
002
003
004
You generate a new version, by choosing Utilities ® Versions ® Generate Version . The system copies the current version 001 to a new version, 005, and
you can now work with your new version, maintenance version 001.
Later you want to retrieve an earlier version, 002. You choose Utilities ® Versions ® Version Management , select version 002, and choose Version ®
Retrieve. The system copies the current maintenance version 001 to a new version, 006, and overwrites 001 with the contents of version 002.
!--a11y-->
1.6.8 Delivered Format Trees
Use
SAP delivers a number of predefined format trees that can be used by applications listed below, for the specified formats. The format trees for outgoing files
can be used to generate DME files without any further configuration in DMEE. In addition, you can use the format trees as templates to create new trees to
cover any regional or bank-specific formats not supported by SAP.
Two sample formats are available that highlight the features you can use when you create a format tree. They are both called SAP_EXAMPLE, and are
delivered for tree types PAYM and MCSH.
Integration
Outgoing DME files

The following applications in Financial Accounting (FI) use the format trees to generate a DME file to be sent, for instance, to your bank.
Payment Program (Tree Type PAYM)

The following PAYM format trees (used in conjunction with the Payment Medium Workbench format) cover most of the standard formats previously
supported by SAP as individual file generation programs, listed below as the corresponding classical payment medium program:
Country Format Tree Description Corresponding Classical Payment

Medium Program
Australia AU_BECS Domestic bank transfers/debit memos RFFOAU_T
AU_BECS_B Domestic bank transfers/debit memos RFFOAU_T

with balancing record
Austria V3 Domestic bank transfers RFFOAT_P
Belgium BE_BEPDTA Foreign bank transfers RFFOBE_E
BE_DOM80 Debit memos RFFOBE_D
BE_PIBDTA Domestic payments RFFOBE_I
Brazil FEBRABAN_P Domestic bank transfers RFFOBR_U
Canada 005 Human Resources and payments to/from New format

customers/vendors
Czech Republic CZ_GEMINI Domestic bank transfers RFFOCZ_U
CZ_GEMINI_F Foreign bank transfers RFFOCZ_U
Denmark DK_PAYMUL_DOMESTIC Domestic payments (EDIFACT format) New format
Finland LM03 Domestic payments New format (replaces format LM02,

program RFFOFI_L)
FI_LUM2 Foreign payments RFFOFI_U
TS Human Resources New format
FI_A_AUTOGIRO Direct debits/debit memos RFFOFI_A
France FR_ETEBAC_VRT-ETR Foreign bank transfers RFFOF__T
FR_ETEBAC_VRT-DOM Domestic bank transfers RFFOF__V
Hong Kong AUTOPLAN1 Domestic bank transfers/debit memos RFFOHK_A
Hungary HU_GIRO Domestic bank transfers New format
Ireland IE_AIB Domestic payments (Allied Irish Banks) RFFOGB_T
IE_BOI Domestic payments (Bank of Ireland) RFFOGB_T
Luxembourg LUX_VIR2000 Domestic and foreign payments RFFOLU_V
Netherlands BTL91 Foreign bank transfers RFFONL_A
CLIEOP03 Domestic bank transfers/debit memos RFFONL_I
New Zealand MTS Domestic bank transfers/debit memos RFFONZ_T
Norway NO_PAYMUL Outgoing domestic payments and foreign New format

payment orders
Portugal PS2 Bank transfers RFFOM100
Slovakia CZ_GEMINI Domestic bank transfers RFFOCZ_U
CZ_GEMINI_F Foreign bank transfers RFFOCZ_U
South Africa ACB_ZA Domestic bank transfers RFFOZA_A
Sweden SE_A_AUTOGIRO Direct debits/debit memos RFFOSE_A
SE_BANKGIROT Domestic payments RFFOSE_B
SE_POSTGIROT Domestic payments with Postgirot Bank RFFOSE_P
SE_UTLI_SISU UTLI/SISU via BGC/foreign bank RFFOSE_H

transfers
Switzerland CH_DD Direct debits/debit memos (Postfinance) New format
CH_DTA POR: domestic/foreign payments (bank) RFFOCH_U
CH_EZAG POR Domestic/foreign/ payments New format

(Postfinance)
CH_LSV Direct debits/debit memos (bank) RFFOCH_U
United Kingdom GB_BACS Domestic payments RFFOGB_T
Advance Return for Tax on Sales/Purchases (Tree Type UMS1)
Country Format Tree Description
Taiwan TW_GUI_403 Government Unified Invoice (GUI) 401/403
TW_GUI_DETAIL GUI detail list and summary form
Advance Return for Tax on Sales/Purchases (Tree Type UMS3)
Austria AUSTRIA_U30_XML Advance Return for Tax on Sales/Purchases with XML

(Austria)
Withholding Tax Reporting (Tree Type WTRE)
France IDWTFILE_FR_DAS2 Withholding tax Déclaration honoraires
South Korea KR_BUSINESSINCOME Withholding tax on business income
United Kingdom IDWTFILE_UK_CIS23E CIS23E: Construction Gross Payment Voucher
IDWTFILE_UK_CIS25E CIS25E: Tax Payment Voucher
IDWTFILE_UK_CIS36E CIS36E: End of Year Return
IDWTFILE_UK_S16TMA List of external service providers that you have paid

over GBP 1,000 to over the course of the fiscal year
United States IDWTFILE_US_1042 1042S reporting
IDWTFILE_US_1099 1099 reporting
IDWTFILE_US_1099G 1099-G reporting
IDWTFILE_US_1099INT 1099-INT reporting
EC Sales List (Tree Type ASLD)
Austria AUSTRIA_ZM_XML EC Sales List for Austria
Finland ASLD_FI EC Sales List for Finland
1099-C Cancellation of Debt (Tree Type DEBT)
United States IDUS99C_1099C 1099-C reporting
Incoming DME Files

The DMEE also supports the conversion of incoming DME files (in external, country-specific formats) to a standard format that the R/3 System can process.
Currently, only conversion to MultiCash is supported, and no format trees are delivered.

Payment Medium Workbench

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Payment Medium Workbench

Transféré par

Droits d'auteur :

Formats disponibles

Payment Medium Workbench

PDF download from SAP Help Portal:

Created on October 20, 2016

1 Payment Medium Workbench

Creating payment media without documents in file form

Creation of payment advice notes

1.1 Creating Payment Media

In the upper screen area choose Use in company codes .

In the selection tree choose Note to Payee by Origin .

1.2 Payment Medium Format

Payment medium without documents: DME or Internet payments

1.3 Payment Medium Format Supplement

1.4 Note to Payee

Line type 2 Internal short reference Payment document 6 785 987

1.4.1 Alternative Payer, Alternative Payee

1.5 Selection Variants

1.6 Data Medium Exchange Engine

1.6.1 Outgoing File

Creating Format Trees

1.6.1.1 Customizing Payment Methods for Use with DMEE

1. Create Payment Medium Formats

2. Assign Payment Medium Format and Note to Payee to Payment Method

Delivered Format Trees

1.6.1.2 UMS1, UMS2, and UMS3 Tree Types

UMS2 and UMS3

RFUMS2_TAX_ITE MWSKZ 2 = ’A1’ 1

Tax Code Description Transaction Key Group No.

A1 16% output tax MWS 6

A1 16% output tax MWS 10

A2 20% output tax MWS 10

1.6.2 Incoming File

Creating Format Trees

Convert Format of Incoming DME File

1.6.3.1 Screen Layout

Header data for outgoing files

1.6.3.2.1 Header Data for Outgoing Files

1.6.3.2.2 Header Data for Incoming Files

Assignment Rules for SAP_EXAMPLE

Rule No. Identifier ID Offset Ref.ID of Tgt Segmt

1.6.3.3 Creating Nodes

1.6.3.4 Node Types

Nodes for outgoing files

1.6.3.4.1 Nodes for Outgoing Files

Node Types for Flat Files

Segment group Used to group segments

Segment Represents a record in the target file

Composite Used to group elements

Element Represents a target field of the DME file

Node Types for XML Files

XML attribute Represents a subnode of an element; provides detailed information for an

1.6.3.4.2 Nodes for Incoming Files

Segment Represents a record in the target file;

Element Represents a target field of the DME file

Action node Represents a subnode of an element; it does not correspond to any

1.6.3.4.2.1 Optional Supplementary Segments

Segment Reference ID Level

Header record HEADER 1

Business partner BUPA 2

Payment record PAYM 3

Note to payee VWZW 3

Assume your incoming file contains the following data records:

1.6.3.5 Data Mapping

1.6.3.5.1 Mapping Outgoing Files

Select mapping procedure If