DME-DATA MEDIUM EXCHANGE
DME stands for Data Medium Exchange
A data medium exchange (DME) is a data exchange file which is used to send payment information of an enterprise to banks o
which can be in flat file or xml file format. Different File formats can be created for different countries and different banks bas
programs.
There are some important payment methods
APP Cheques - In this Company will print Cheque and send to Vendors.
APP IDOC- In this Bank will print Cheque and send to Vendors.
APP DME - In this output file will be submitted to Bank, and Bank will Transfer the amount to vendors
Some Important key Points of DME
1. Transaction to create DME Tree: DMEE
2. Each DME tree must contain a Root level.
3. A DME tree must be activated before it can be used.
4. All DME Format trees for payments are driven by SAP standard program SAPFPAYM.
5. Each field in a DME tree is named an “Element.”
6. An Element’s subfield is called an “Atoms.” These atoms can be used to add additional flexibility to a field.
There are 5 main types of attributes which can be assigned to an Element or Atom.
1. Constant
2. Structure Field
3. Reference Tree Node
4. Aggregation
5. Exit Module
DMEE Configuration Steps :-
Steps Descriptions T-code
1 Create Payment Medium Formats (OBPM1
2 Assign Payment Medium Format to Payment Method at Country (FBZP)
3 Create and Assign variants for the House bank (OBPM4
4 Data Medium Exchange (DME) - Mapping (DMEE)
M EXCHANGE
an enterprise to banks or tax authority. Basically these files contain financial data
and different banks based on their own norm which replaces conventional ABAP
/ZDME_ICICI
Transaction SA38 SAPFPAYM
(DMEE)
Header Level
Nodes Structure-Field Name Length Mapping Procedure Node Value
Date FPAYH-LAUFD C10 Structure Field 5/8/2023
Company Code FPAYH-ZBUKR C(4) Structure Field HP01
Bank Referance FPAYH-DOC1R C(24) Structure Field HP01111231
Transaction Level
Nodes Structure -Fieldname Length Mapping Procedure Node Value
Sequence No FPAYH-LFDNR C(5) Structure Field
Payment Type #NA C(4) Constant RTGS/NEFT
House Bank FPAYH-HBKID C(15) Structure Field
Payer IFSC FPAYHX-USWIF C(11) Structure Field
Payer Bank A/c FPAYHX-UBKNT C(35) Structure Field
Vendor Name FPAYH-ZNME1 C(40) Structure Field
Vendor IFSC FPAYH-ZSWIF C(11) Structure Field
Vendor Bank Ac FPAYH-ZBNKN C(15) Structure Field
Currency FPAYH-WAERS C(5) Structure Field
Amount FPAYH-RWBTR P(12) Structure Field
Level Node Order
Level 1 1
Level 1 2
Level 1 3
Level Node Order
Level 2 1
Level 2 2 Payment Type RTGS NEFT
Level 2 3 Amount <20000 NEFT Payment
Level 2 4 Amount >=20000 RTGS Payment
Level 2 5
Level 2 6
Level 2 7
Level 2 8
Level 2 9
Level 2 10
Types of Nodes in DMEE Tree
1. Segment Group
Segment groups are used for arranging segments. Segment groups can be followed by these nodes: segment groups or segme
begins with a segment group.
2. Segment
A segment represents a record in the target file. In an active format tree, each segment must have at least one composite
or one element as a subnode. If you created a segment that contains only segments and segment groups as subnodes, you can
3. Element
An element represents a field in the target file. For each element, you specify with which value or from which source field this
mapping rule applies to an element - if the rules are dependent on conditions or if different parts of the element are to be fil
define several atoms as subnodes of the element.
4. Technical Node
A technical node is an element that is not output to the target file. It stores values that are used in other tree nodes (elements
reference to the technical node. For this reason, a technical node generally contains a reference ID. If you wish to output the c
file, then you can convert the node to an element.
4.Atom
You need to create an atom when you define more than one mapping rule for an element.
5. Reference ID of Node
A node that contains a reference ID can be referenced from other nodes in the format tree. You can specify such a reference w
or aggregation. You must assign unique reference IDs (within the tree). When you delete a node that contains a reference ID,
des: segment groups or segments. In most cases, a new level in a DMEE tree
ve at least one composite
nt groups as subnodes, you can convert the node to a segment group.
or from which source field this file field is to be filled. If more than one
ts of the element are to be filled from different sources - then you should
in other tree nodes (elements, atoms) by
ID. If you wish to output the contents of the technical node to the target
can specify such a reference when you define mapping rules, conditions,
that contains a reference ID, be sure that no references to this node exist.
FI Enterprises Structure Configuration
1 Edit, Copy, Delete, Check Company Code
2 Define Field Status Variants
3 Assign Company Code to Field Status Variants
4 Assign Company Code to a Fiscal Year Variant
5 Define Variants for Open Posting Periods
6 Assign Variants to Company Code
7 Open and Close Posting Periods
8 Copy to Company Code
9 Define Tolerance Groups for Employees
10 Edit Chart of Accounts List
11 Assign Company Code to Chart of Accounts
12 Define Account Group
13 Define Retained Earnings Account
14 Define Settings for Ledgers and Currency Types
Accounts Payable Configuration
Step to Configure Business Partner(Vendor Master - Configuration)
1 Define Account Groups with Screen Layout (Vendors) -T-code: OBD3
Display IMG -> Financial Accounting -> Accounts Receivable and Accounts Payable -> Vendor Accounts -> Master Data -> Prepa
Account Groups \with Screen Layout (Vendors)
2 Create Number Ranges for Vendor Accounts - T-code: XKN1
Display IMG -> Financial Accounting -> Accounts Receivable and Accounts Payable -> Vendor Accounts -> Master Data -> Prepa
Data -> Create Number Ranges for Vendor Accounts
3 Assign Number Ranges to Vendor Account Groups - T-code: DBAS
Display IMG -> Financial Accounting -> Accounts Receivable and Accounts Payable -> Vendor Accounts -> Master Data -> Prepa
Data -> Assign Number Ranges to Vendor Account Groups
BP Master & Link to Vendor Master - Config
1 Define Number Ranges-T-code: BUCF
Display IMG -> Cross-Application Components -> SAP Business Partner -> Business Partner -> Basic Settings -> Number Ranges
2 Define Groupings and Assign Number Ranges
Display IMG -> Cross-Application Components -> SAP Business Partner-> Business Partner -> Basic Settings -> Number Ranges
and Assign Number Ranges
3 Define Number Assignment for Direction BP to Vendor
Display IMG -> Cross-Application Components -> Master Data Synchronization -> Customer/Vendor Integration -> Business Pa
Assignment for Vendor Integration -> Assign Keys -> Define Number Assignment for Direction BP to Vendor
Note:- If client requirement is same no. for both business partner and vendor/customer master
Define Vendor Number Range is Externally and BP Number Range is Internally.
guration)
ounts -> Master Data -> Preparations for Creating Vendor Master Data -> Define
ounts -> Master Data -> Preparations for Creating Vendor Master
ounts -> Master Data -> Preparations for Creating Vendor Master
c Settings -> Number Ranges and Groupings -> Define Number Ranges
c Settings -> Number Ranges and Groupings -> Define Groupings
or Integration -> Business Partner Settings -> Settings for Vendor Integration -> Field
to Vendor
