0% found this document useful (0 votes)
47 views37 pages

DMEE

COnfiguração DMEE

Uploaded by

A C Pom
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)
47 views37 pages

DMEE

COnfiguração DMEE

Uploaded by

A C Pom
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
  • Introduction and Setup
  • Creating Payment Medium Formats
  • DMEE Configuration Procedures
  • Bank Customization Settings
  • Selection Variants Setup
  • Automatic Payment Transactions
  • Conclusion

Formularios: ZCGI_XML_CT_CL

Exits:

DMEE_EXIT_CGI_XML

DMEE_EXIT_CGI_DEBT_NAME

ZFI4B_FM_RMV_BANK_DATA_VALEVIS (Flag Vale Vista)

ZFI4B_FM_DMEE_BANK_CHECK (Santander)

DMEE_EXIT_CGI_DEBT_NAME

ZFI4B_FM_DMEE_SWIFTCODE (Santander)

ZFI4B_FM_SUCCURSAL_72_VALE_VIS

DMEE_EXIT_SEPA_31

ZFI4B_FM_SUCCURSAL_72_VALE_VIS

PARTE 1

This is my First Document in the Forum and hope this will be helpful for all.

I have searched in Forum but I did not get any Document on DMEE where Step By Step
Configuration is Given.

Any Suggestion and Critics are always Welcome as this will help me to improve.

Introduction:
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 or tax authority. Basically these files contain financial
data which can be in flat file or xml file format. Different File formats can be created for
different countries and different banks based on their own norm which replaces
conventional ABAP programs.

                            

                                                                          DMEE Configuration:Step By
Step.
Create Payment Medium Formats (OBPM1) Accounts Receivable and Accounts
Payable  ® Business Transactions  ® Outgoing Payments  ® Automatic Outgoing
Payments  ® Payment Media ® Make Settings for Payment Medium Formats from Payment
Medium Workbench ® Create Payment Medium Formats

Select New Entries


Format                                              : Z_IDES

Description                                        : Z_IDES

Payment medium without docs.           : Select

Type                                                  : 01 File

Country                                              : IN

Mapping using DME engine                 : Select

Company Code                                  : Select

House Bank                                       : Select

Save!

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.
DME Engine: Initial Screen (DMEE):
Select Active Version and press Copy.
Click on Change.

Click on DMEE tree:Properties

Here you need to give the format attributes for your DMEE output File.

Please see the screen shot Below.


In the Field type you have two options 1 or 2

I have taken 1,Fields are separated by Delimiter.

In Delimiter Section I have taken | but you can use comma,semi colon or anything.

Delimiter separates the items in DMEE file by the input provided by you.

After this click on Sort/Key Fields.

Sort key Fileds controls the output of line in [Link] actually controls the levels of DMEE.

Please see the Screen Shot below.


Header data should appear only once, so a value like the payment run identifier (FPAYH-
LAUFD) is the same for the entire payment run and file created. Next level is usually the
single payment (FPAYH-LFDNR), so the DMEE creates a new line for every payment.
Alternatively and based on the requirements, this could be done also per vendor. Lowest
level is usually the invoice references, as you can group several vendor invoices in a single
payment.

After This Goto File Data where you need to tick on Carriage return and Line Feed.

The tick on Carriage return and Line feed is for creatin new line after the finish of Header
Part.

Carriage Return is used for creating new line in word or PDF formart and Line Feed  is
used for creating new line in XML format.

Please refer Screen Shot Given Below.


In Header Part you need to define the Level and the type of output you want..

Screen shot is attached for the same.

The tick on Carriage return and Line feed is for creatin new line after the finish of Header
Part.

Carriage Return is used for creating new line in word or PDF formart and Line Feed  is
used for creating new line in txt Format.

Add the fields to Header and Details as per the requirement and then save.
Now will show step by step for every Header and payment Details configured here.

A. P.S:Requirement may vary according to Client and Bank.

In Header Part I have made it Constant which you need to choose in Attributes tab of
DMEE.

Give name(as I have given Header),Give Length and choose character as shown in Screen
Shot Below.

Go to Source Tab and write what you want to get in the output as shown in screen shot
below.
The Next is Corporate ID,This is nothing but the paying Co code.

Give Name,Length and Type.

Please select Structure Field(I have taken Structure Field because it can be fetched from
the Tables and Field,Some data are there which you can fetch from tables so either you
have to make it constant or you have to use Exit Module).

Click on Source Tab.

You will find Field name,You can choose Field name according to your requirement.

Here I have taken FPAYH-ZBUKR as shown in screen shot below.


Now We will configure the payment details.

As I have copied the standard structure where Segment group and Elements were already
there but you can definitely create segment group,segment and elements according to the
requirement.

In my Configuration the first is payment type(Means the payment is NEFT or RTGS)

For this you can not use constant or structure field,here you need to use Exit Module and
you need the help of ABAPER to write a logic(The logic here is that if the amount is less
than or equal to rs 200000 then NEFT else RTGS).

Now click on the Source Tab and one need to provide structure and Field name(though we
are using Exit Module but we need to provide Structure and Field name so that the data
can be populated in the Structure and field given and system populates the data in DMEE
file through this Structure and Field)

I have Used FPAYH-FORMZ,.

Please refer the screen shot Below.

The Exit Function  “ZDMEE_EXIT_TEMPLATE_ABA” is done by ABAPER and you need to


assign this Exit Function as shown in Screen Shot Above.

I am giving the code as well which is done by ABAPER and it works according to NODE ID.

The Coding is as follows:

CASE i_extension–node–node_id.
WHEN ‘N_8559886880’ .
IF l_item–fpayp–dmbtr LT 200000.
l_item–fpayh–formz = ‘NEFT’.
o_value = l_item–fpayh–formz.
c_value = l_item–fpayh–formz.
ELSE.
l_item–fpayh–formz = ‘RTGS’.
o_value = l_item–fpayh–formz.
c_value = l_item–fpayh–formz.
ENDIF.

Now click on Payee IFSC Code and Configure as given in the screen shot below.
PS:Please maintain the IFSC code of Payee bank in Control Data Tab in SWIFT column in
House bank .
Click on Payee Bank Number and Configure According to Screen Shot.
Click on Receivers IFSC Code and configure as shown in Screen Shot Below.
I have used Exit Module here as well and the coding is as follows:

WHEN ‘N_9336226660’ .  “ifsc code
CLEAR: l_lifnr,l_bkref.
l_lifnr = l_item–fpayp–gpa2r.
SELECT SINGLE bkref FROM lfbk INTO l_bkref WHERE lifnr = l_lifnr.

l_item–fpayh–bkref = l_bkref . ” L_ITEM-FPAYH-EIKTO. ” L_BKREF.


o_value = l_item–fpayh–bkref.
c_value = l_item–fpayh–bkref.

Now in Vendor Master Data You need to maintain IFSC code in Reference Details Field as
shown in Screen Shot Below.
Now Click on Beneficiary Account No and configure as shown in Screen Shot Below.
Here also I have used Exit Module and the Coding is as follows:

WHEN ‘N_3908411670’.  “account no
CLEAR: l_lifnr,l_bankn.
l_lifnr = l_item–fpayp–gpa2r.
SELECT SINGLE bankn  FROM lfbk INTO l_bankn  WHERE lifnr = l_lifnr .”
L_ITEM-FPAYH-EIKTO.

l_item–fpayh–zbnkn = l_bankn.
o_value = l_item–fpayh–zbnkn.
c_value = l_item–fpayh–zbnkn.

Maintain bank account in vendor master in Bank account Column as Shown in Screen Shot
Below.
Now Click on Transaction Currency and configure as shown below.
Now Click on Amount and configure as Shown in Screen Shot.
Click on Name of Payee(Vendor) and configure as shown in Screen Shot Below.
Click on Vendor Email Id and Configure as shown in Screen Shot Below.
Here also I have used Exit Module.

Coding is as follows:

WHEN ‘N_9785488450’.           ”   Vendor Email ID


CLEAR: l_lifnr,l_adrnr,l_emailid.
l_lifnr = l_item–fpayp–gpa2r.
SELECT SINGLE adrnr FROM lfa1 INTO l_adrnr  WHERE lifnr = l_lifnr .
IF sy–subrc IS INITIAL.
SELECT
SINGLE smtp_addr FROM adr6 INTO l_emailid WHERE ADDRNUMBER = l_adrnr.
ENDIF.

l_item–fpayh–INTAD = l_emailid.
o_value = l_item–fpayh–INTAD.
c_value = l_item–fpayh–INTAD.

WHEN OTHERS.
ENDCASE.

Click on User Mobile No(Vendor) and Configure as shown in Screen Shot.


                               Settings in Bank Customization (FBZP):

a) Payment Methods in Country: Create Pymt. Method ‘E’ for country ‘IN’. Define the
Currency.
In Payment Medium,Put Z_IDES in Format Column.

b) Bank Determination: For Paying Company Code ‘1000’, select Ranking Order.
Create New Entries for “E”

c) Bank Accounts
Create Bank Account for 1000.

PARTE 2

                                                   Create/Assign Selection Variants (OBPM4)

A. Accounts Receivable and Accounts Payable  ® Business Transactions  ® Outgoing


Payments  ® Automatic Outgoing Payments  ® Payment Media  ® Make Settings for
Payment Medium Formats from Payment Medium Workbench  ® Create/Assign
Selection Variants
 
  

Double click on the Format Created Earlier, i.e-Z_IDES.


Create ‘For All Selection Screens’ and then continue.

Give Payment Medium Format ‘Z_IDES’

Then select Print Parameters and give the name of the printer.
Then Save.

Reservation for Cross-Payment Run Payment Media (OBPM5)


Select 
Run APP (F110)
ID should End with ‘E’ and there should at least one space left.
Complete APP Run.
Go to ENVIRONMENT-PAYMENT MEDIUM-DMEE Administration

Select the File and save the Output File.

Hope you all will find the Document Helpful.

Any Suggestions and Critics are always Welcome as this will help me to Improve in Future.

Regards
Eugene

Common questions

Powered by AI

Flat files and XML files differ in their structure and usage. Flat files typically have a simpler structure, using delimiters like commas or pipes to separate fields, and are often used for straightforward data exchange where complex hierarchical data is not involved. In contrast, XML files support nested data and hierarchical structures, making them more suitable for representing complex data relationships and metadata. In the context of DME, XML is often preferred for its flexibility and ability to include detailed data structures, whereas flat files are used for simpler data representations .

The 'Payment Medium Without Docs' option is used in the payment medium format to streamline the data exchange process by excluding additional documentation data that may not be necessary for the payment process. This option reduces the size of data files, speeds up the data exchange process, and focuses on transmitting only the essential financial information needed by banks for processing transactions. It is particularly beneficial when handling high volumes of transactions where further documentation can be burdensome or unnecessary .

Using delimiters like pipes or commas in DMEE configurations offers several advantages including simplicity and compatibility. Delimiters help in easily separating fields within flat files, making it straightforward to parse data upon receipt. This approach reduces complexity in data handling and allows for simple text processing, enhancing compatibility with different systems that may not support complex structured data formats like XML. Delimiters provide a flexible, lightweight solution for transmitting structured data efficiently across systems .

Payment run identifiers, such as FPAYH-LAUFD, are crucial for ensuring data integrity because they uniquely identify each payment run. This identifier appears once in the header data and remains consistent throughout the entire payment file, linking every single payment back to the original run. This prevents discrepancies and ensures that data is consistent across different levels of the DMEE file .

Node IDs in exit module coding allow the implementation of custom logic for different sections of a payment processing file. By associating specific node IDs with sections of the configuration, developers can execute conditional logic to handle different scenarios, such as determining payment methods or fetching bank details dynamically. This capability ensures that different payment processing needs are met efficiently and accurately by executing specialized logic only when required, based on the node in processing .

Maintaining the correct structure and field names in the Source Tab is vital for accurate data retrieval during DMEE file generation. Each field maps to specific database objects or constants that provide the necessary data to populate corresponding elements of the DME file. Incorrect mappings can lead to data discrepancies or missing information, affecting the integrity and accuracy of the financial data exchanged. Proper structuring and correct field assignments ensure that the system retrieves and populates data correctly for each part of the payment file, supporting seamless and faultless transaction executions .

The DME engine facilitates the creation and customization of payment medium formats by providing a graphical interface to define format attributes. It allows users to map company codes, house banks, and other necessary information directly into the payment medium configuration. The DME engine also manages the tree structures used for format definitions, supporting the separation and hierarchical organization of data into header, detail, and footer information. This ensures that payment files are generated accurately according to specific country and bank requirements .

Exit modules are necessary in DMEE configuration for dynamic data processing requirements that cannot be achieved using constant values or simple structure fields. For instance, when determining payment methods like NEFT or RTGS based on amount thresholds or handling complex logic to populate fields like bank details and vendor information dynamically from external sources. These modules allow the insertion of custom ABAP code to handle specific business logic that standard configurations cannot accommodate, providing flexibility in meeting diverse client and bank requirements .

Defining the 'Level' and 'Type' in the Header Part is critical as it determines how data hierarchy is represented within the DMEE file. The 'Level' sets the position of the header data within the overall file structure, ensuring it appears only once and effectively precedes the detail lines. Meanwhile, the 'Type' defines the kind of data expected, whether constant, dynamic, or sourced from external tables, ensuring that the correct header information is captured and maintained consistently across payment runs. This setup maintains structural integrity and ensures proper data parsing by recipient systems .

Configuring IFSC codes properly in a DMEE file is essential for ensuring the correct routing of payment transactions. IFSC codes uniquely identify bank branches, allowing payments to be directed accurately to the recipient's specific bank location. An incorrect IFSC code can result in failed transactions or delays, affecting the reliability of financial operations. By setting up these codes correctly in both the control data tab and vendor reference details, organizations ensure seamless processing and reduce the risk of manual errors in bank data transmission .

Formularios: ZCGI_XML_CT_CL
Exits:
DMEE_EXIT_CGI_XML
DMEE_EXIT_CGI_DEBT_NAME
ZFI4B_FM_RMV_BANK_DATA_VALEVIS (Flag Vale Vista)
(https://blogs.sap.com/wp-content/uploads/2015/06/1_733839.png)Create Payment Medium Formats (OBPM1) Accounts Receivable and
(https://blogs.sap.com/wp-content/uploads/2015/06/1_733840.png)Format                                              : Z_IDES
 (https://blogs.sap.com/wp-content/uploads/2015/06/1_733895.png)DME Engine: Initial Screen (DMEE):
(https://blogs.sap.com/wp-content/uploads/2015/06/1_733897.png) (https://blogs.sap.com/wp-content/uploads/2015/06/1_733896.p
(https://blogs.sap.com/wp-content/uploads/2015/06/1_733901.png)Click on Change.
Click on DMEE tree:Properties
Here you need
(https://blogs.sap.com/wp-content/uploads/2015/06/1_733936.png) (https://blogs.sap.com/wp-content/uploads/2015/06/1_733903.p
(https://blogs.sap.com/wp-content/uploads/2015/06/1_733964.png)Header data should appear only once, so a value like the paym
(https://blogs.sap.com/wp-content/uploads/2015/06/1_733966.png) (https://blogs.sap.com/wp-content/uploads/2015/06/1_733965.p
(https://blogs.sap.com/wp-content/uploads/2015/06/1_733974.png) (https://blogs.sap.com/wp-content/uploads/2015/06/1_733973.p

You might also like