0% found this document useful (0 votes)
53 views9 pages

Data Medium Exchange - Notes - 28.11.2023

Uploaded by

ravi ganta
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
53 views9 pages

Data Medium Exchange - Notes - 28.11.2023

Uploaded by

ravi ganta
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 9

APP with DATA MEDIUM EXCHANGE (DME)

 DME or Data Medium Exchange is a data Exchange file, which is


used to send payment information of an Enterprise to Banks or
Tax information to the Tax Authority.
 Basically these files contain financial Data which can be in FLAT
file /CSV formate/Text formate or XML file format.

Different file formats can be created for different countries and


different Banks based on their own node which replaces conventional
ABAP Programs.

You send it to your Bank and Bank transfers the money from your
account to third party’s A/C. So alternatively, you can use DME to Debit
money from your Customer’s A/C or you can send a DME file with tax
data to tax authorities.

PAYMENT MEDIUM WORKBENCH (PMW):

It is a tool used to configure and create payment media sent by


organizations to their House Banks.( To generate payment File)

BANK FORMATS:

The various Bank formats that are supported

MT940, MT100, SEPA, SWIFT, BAI, ……, etc.

There exists many formats for Banks globally.


MT940 is supporting XML file or FLAT/CSV/TEXT format.

Depends on Bank supporting, can choose format.

NOTE:

In present case, i.e. in own example,

Bank=HDFC

Bank format=CSV format, i.e. MT940.

BANK OUTGOINT FILE:

We can generate the Bank outgoing file by using the Payment


Medium Workbench (PMW) along with the DME tree structure.

When Running APP in F110, DME is performed through Tree


Structure. In order to send outgoing payment orders to the Bank, a file
is to be imported in a pre-defined Structure into Bank Payment
Application (i.e. to get output as per Bank Structure, we are defining
DME Tree Structure as per Bank requirement).

The DME Tree Structure need to be assigned in the automatic


Payment Programme Configuration Settings (i.e. is FBZP, Payment
Method Per Country).

While executing F110, system generates Bank outgoing file as per


DME Tree Structure, than be uploaded either manually in the Bank
portal (site).

(OR)
We can send the file through the Interface (third party tools usage)
between SAP system and Bank system.

THE BELOW POINTS ARE TO BE DISCUSSED WITH THE BANK AND ALSO
BUSINESS WHILE IMPLEMENTING THE DME.

(a) Need to discuss with the Bank, along with the client (Business), to
get the required information from the Bank. This information
includes

- Which type of format is supported by Bank.

E.g. MT940, MT100, BAI, SEPA, FCHI, SWIFT, …, etc.

- Which type of file Bank is supporting.,

E.g. XML, TEXT/CSV/FLAT format

- Interface (i.e. which third party tool to be used)

- What Functionality supporting by bank.

(b) Need to ask Bank to send or get format for sample file, i.e. check
and study the Bank format, then note the points which is not cleared
and which is required clarification from the Bank.

(c) Need to discuss with Business, get the clarification of the below
points.

- Whether business want to send the payment advice notes to


the Vendor either through the Bank or directly from the Business.

- In case, if the Business want to send the payment advisice details


through Bank, than need to ask the business what details to be
displayed in the payment advisory notes (annexures) like Invoice
No. (SAP No.), Vendor invoice No (Vendor bil No.), Invoice Date
paid amount, deductions, etc.

- Whether Business want to process the Foreign Currency


Payment and also advance payment.

(d) Role of FICO Consultant to define structure in SAP

We need to prepare the functional specifications and need to


specify the logic for each field of the format.

(e) Need to identify how many Enhancements or Technical


Developments required. The Enhancements include

- To get the file name with client ID.

- To get Email address from Vendor Master Data address table

- To get the invoice No in the Annexure (i.e. Payment Advisory


Note).

- To specify the NEFT (Net Transfer), RTGS, funds transfer


between banks based on the conditions.

E.g. Process the payment through NEFT, if amount is less than


2,00,000/- and otherwise transfer the amount through RTGS.

- To sorting the sequence of the line of the annexures to be


displayed in the outgoing file as per presided format.

KEY TERMINOLOGIES:

Following are some of the terminologies to be understood, in order to


follow the process of DME.
SEGMENT GROUP:

It represents the Grouping of the Segments and we can specify the


conditions, rules and Segment levels.

E.g. Payment Group Segment levels

Bank Header Group

HDFC Bank = Segment Group

SEGMENT:

Contains Structure of the format or Element or Structure of the


contents.

E.g. Segment (1) – Payment Heads

Segment (2) – Payment Instructions

Segment (3) – Payment Details

Segment (4) – Annexures, etc.

ELEMENT:

Each Element represents the field of the format (or) in the format, each
content can be defined as an Element.

E.g. Vendor name, Customer name, Company Code, Amount,


Payment Date, Invoice No, Payment Transaction, Payment location, file
name, etc.

MAPPING PROCEDURE:

The Mapping procedures specifies how to get the values for each
element. The Below are the type of the mapping procedures.
- Constant
- Structure field
- Reference to Tree Node
- Aggregation
- Exit Mode
- Atom
 Constant to specify the fixed values
 Structure field uses to read the data from the DME Structure
tables, where the DME Structure tables include

DME FPAYH – Payment Data can be

Payment FPAYHX – Prepared data for the Payment checked in

Tables FPAYP – Data on Paid item SE11

 DMEE_PAYD
 Reference to Tree Node to get the values from the other
Reference Node.
 Aggregation is to count or summation of the values.
 Exit Mode is to apply or use the Enhancement logic.
 Atom is to combine/group the multiple fields (i.e. more than one
element) into single field.

REFERENCE ID:

Identification of the Element or Node. This can be used as a Reference


Node in the other Element.
CONVERSION FUNCTION INDICATOR:

How the values to be displayed in the file

E.g. Date format ----- YYYY/MM/DD

YYYY/DD/MM

DD/MM/YYYY

MM/DD/YYYY, Etc.

Eg : Amount Formate ---- 1,00,000.00

--100.00.000,000

STATUS INDICATOR:

By using the status, we can make the specific field as a required,


optional .

CARRIAGE RETURN:

Is to End the Segment by using “(. Full Stop)”

LINE FIELD:

To create/ make the separate line after End of the Segment.

SORT/KEY FIELDS:

To make and display the sequence in the file.

DME TREE PROPERTIES:


Contains DME properties like type of format, no of levels, sorting key
fields, etc.

FILE TYPE:

DME file supports below file formats like

 XML file format


 CSV/TEXT/FLAT FORMAT

CREATION OF DME TREE STRUCTURE: (TC=DMEE) (in ECC) or


DMEEX( in S/4)

TO CREATE DME TREE STRUCTURE, FOLLOW THE BELOW PROCESS:

 DME Tree Structure Defines the Structure/format of a particular


file.
 Tree type is already pre-defined where values are already existed
in SAP.
 Here Tree Type used is (PAYM)
 PAYM = Data Medium Exchange for Payment Program.

Example:

 If I have 10 A/C’S in HDFC Bank, I will use 1 Tree Type.

 If I have 1 A/C in HDFC and other A/C in Canara Bank, than I shall
use 2 tree types.

You might also like