What is DME in SAP? | End to End Process and Testing | SAP Financial Accounting

DME stands for Data Medium Exchange and you can associate it with SAP Payments. For this post I will use Belgium related scenarios to help you visualize.

This post assumes that you have already created the DME tree and it is ready for testing. If you need guidance for the creation of the actual DME tree, it will be covered in another blog post.

It more or less has the same cycle, but you can expect slight differences (i.e file format) in other countries or SAP systems. Either way, you can read through this post to understand the purpose of DME.

Overview

  • Process Flow
  • How does DME relate to SAP Payments?
  • SAP DME Configuration (High Level and Summary)
  • Testing Proper (DME Only – Quick)
  • How do I activate my tree? (Additional Help)
  • Testing Proper (Detailed)
  • Testing Steps Summary
  • Additional Information / Tips

Process Flow

  1. Accounting Documents exist that need to be paid through Payment Run (F110)
    • Let us consider Vendor items due for payment.
  2. Payment Run is executed (Proposal and Actual Run) which will generate a payment medium file or output.
    • Usually, payment medium file is generated for the Actual Run and NOT the Proposal to prevent risky or erroneous scenarios.
    • In this example, our payment medium file or output will be an XML file (pink box).
SAP DME Process Belgium
  1. This XML file will be provided to the bank or it will be uploaded to an online banking system or portal.
    • A good example would be Isabel since it has the capability to carry out multiple transactions for several banks in one portal.
    • .XML files usually have the payment information indicated.
    • NOTE: This is where the payment medium output checking stops but you may proceed up until the bank statement post processing.

  1. When transactions have completed, the bank sends an Electronic Bank Statement (EBS). In this example, Belgium banks send CODA or .COD files (white box) with the corresponding payment details / transactions.
SAP DME Process Belgium
  1. This .COD file or the Belgium Bank Statement is then uploaded to SAP through FEBC (program RFEBBE00) where it will be “consumed” and converted to Multicash Format.
    • If the file is interpreted and converted to Multicash Format, you will see the results in FEBAN where you can do bank statement post processing such as clearing etc.
    • If conditions are met upon file analysis, documents would be created. Here you can view if the necessary amounts are posted to the intermediary bank GL accounts etc.

  1. If SAP is able to see a fully met condition that triggers an Interpretation Algorithm, it will follow the configured settings accordingly.
    • For example: if conditions are met for Interpretation Algorithm 19 (Reference no. DME management), it will proceed with the “auto clearing” setup.

You may refer to the full image below where the green circle signifies the starting point while the red circle signifies the end point.

SAP DME End to End Process Belgium
Purple signifies SAP System, Blue signifies online banking, White signifies a file.

How does DME relate to SAP Payments?

From the process above, you can associate DME to the .XML file that generated as the payment medium file. In the image below, I have colored it pink.

You may be wondering why the word DME was indicated in the 1st box. The reason is because DME is triggered by the payment run (F110) and the output is the .XML file.

SAP DME End to End Process Belgium
DME Output = Payment Medium Output ; In our example it is the generated .xml file.

Formally speaking, DME creates a file that contains payment details and serves as instructions to the bank. In our example, this was the .XML file.

In order to create the right file (that will be understood by the bank or online bank portal), it needs to be setup in SAP.

Note: that DME does not solely pertain to .XML files. You can also generate the payment medium file as a flat file. It would also depend on the linked ABAP program that creates these files. A custom program can be built to accommodate different formats that are not doable in standard SAP.

SAP DME Configuration (High Level and Summary)

  • Create Payment Medium Formats (OBPM1)
  • Create Your DME Format Tree using the Data Medium Exchange Engine (DMEE)
  • Link Payment Method to the Payment Medium Format (FBZP)
  • Maintain Payment Medium Selection Variants / Assign Payment Medium Format to the house banks concerned (OBPM4)

Testing Proper (DME Only – Quick)

If you want to do a quick test on your DME Tree, you can do so via DMEE transaction code. Note that this will only show the sample output. It can be useful but if you want a realistic scenario you can follow the steps provided below in Testing Proper (Detailed).

  • DMEE Enter your Tree Type and Format Tree then click on the Test Active Version Button (highlighted in red).
SAP DMEE Create Tree
  • You will be shown the screen below. Click on the Test Button. Once clicked, a new window will show you the .xml sample output. There you can do a check of the .xml tags included and the details as well.
SAP DMEE Testing

NOTE: If you want to be sure, it is advisable that you do an actual test payment run to see the realistic populated values. This can give you peace of mind on the tree output.

How do I activate my DME Tree? (Additional Help)

  • In the DEV environment, go to transaction code DMEE and enter the Tree Type and Format Tree. Then click on the Change button.
Activate DME Tree in SAP
  • You should see a Wand Button (Activate). Click on it to activate your tree.
  • IMPORTANT: It is important to ensure that you save your DME Tree in a transport. It is equally important to ensure that the ACTIVATION status is saved in the transport as well. If you are making a change to an already existing DME Tree, be sure to create a copy and/or backup just in case.
Activate DME Tree in SAP
  • You will know it is your version by checking on the Last Changed By logs:
Check Change Log DME Tree in SAP
  • If there are other versions maintained, you can switch, compare, and do some checking by clicking on Utilities > Versions > Version Management
Check DME Tree Versions in SAP

Testing Proper (Detailed)

This will help you create test data and perform validations. It helps to have data you can reference from production or you can also find applicable test data and create from reference (if applicable).

  • FB01 Create Accounting Document for Payment Run
    • Example: Posting Key 25 Outgoing Payment Vendor Number and Posting Key 35 Incoming Payment. You can use the proper posting keys set up for your scenario / SAP system.
    • If you have a reference document (or a good document existing in the test system) you can Post With Reference and update the values according to your need.
Create Accounting Document SAP
  • F110 Create Payment Run and narrow down data by specifying parameters such as vendor number, company code, docs entered up to, payment methods, and even document number (in free selection tab).
    • When referencing from production, be sure to copy the entries in printout / data medium tab. If it is blank, then leave it blank.
    • I will create a separate post on detailed F110 inputs and testing.
    • Execute Payment Proposal (no need for payment medium if you don’t need). After this you can review the pulled documents and check if there are errors.
    • Execute Payment Run (IMPORTANT: be sure to tick the Create Payment Medium checkbox)
    • If successful, you should see a green square light with details on Posting Orders.
SAP F110 Payment Run Payment Medium
IMPORTANT: Do not forget to tick the Create Payment Medium checkbox
SAP F110 Payment Run Success
Posting orders generated and completed 2 because I created 2 test documents due for payment. The result also corresponds to the parameters set in F110.
  • AL11 Check on the generated .XML file. If you have access to the file repository, you can directly check there. If not, download the .XML file from AL11 via CG3Y (or refer to this post) to double check on entries.
    • Check on your payment medium output setup. If it is configured to save the payment medium in a secured folder or directory, you will find it there. Logs can be seen in the payment run of F110.
    • Refer to the purple highlight to know what the filename is and where it was saved.
    • Refer to the yellow highlight to check on the spool no. (if needed) through SP01.
SAP Payment Run Log F110
  • If you do not have an external .COD file generator you can pull any available .COD file from production and manipulate the data carefully to match the details from payment run.
    • If the .COD file can be provided from someone else, you can utilize it.
  • FEBC Upload the test .COD file to SAP.
    • If you encounter errors here it would most likely be the result of formatting issues.
  • FEBAN Double check results and perform post processing.
    • This is where you check the populated fields and auto-clearing (if applicable)

Testing Steps Summary

  • FB01
  • F110
  • AL11 (CG3Y to download if needed)
  • FEBC
  • FEBAN
  1. FB01 Create Accounting Document for Payment Run
  2. F110 Create Payment Run and narrow down data by specifying parameters such as vendor number, company code, docs entered up to, payment methods, and even document number (in free selection tab).
  3. AL11 Check on the generated .XML file. If you have access to the file repository, you can directly check there. If not, download the .XML file from AL11 via CG3Y (or refer to this post) to double check on entries.
  4. If you do not have an external .COD file generator you can pull any available .COD file from production and manipulate the data carefully to match the details from payment run.
  5. FEBC Upload the test .COD file to SAP.
  6. FEBAN Double check results and perform post processing.

Additional Information / Tips

It is understood that the end to end testing in SAP will help you validate your work (aside from business user confirmation). I personally tend to do an extra step outside of SAP. Allow me to explain why I do this.

Extra Step (Additional Test)

Ultimately, we are dealing with payments and bank related files. I mentioned that it is highly advisable to do a “penny test” or a “euro cent test” in production with the help of the concerned business user in prior to doing a bulk load of payments.

This small production test helps give the assurance that the changes are indeed working as expected. If something goes wrong, it will be seen in the penny / euro cent test and you would have avoided messing up bulk transactions in production.

As an added measure, I make use of an online tool called xml validator. IMPORTANT: I use this for Belgium related validations and SEPA payments. I am sharing this as an optional extra step for you.

Once I have generated my payment medium output (xml file) in the test environment, I head over to the online tool and upload the xml there for checking. Refer to the image below for what the tool looks like.

Banking XML Validation Tool DME SAP
Select the file and click on the Confirm File Button.

If the file is validated successfully, you will see green results (as seen in the image below). You also have the following options in line with the uploaded .xml file:

  • Download statement of account (CAMT)
  • View the Processed Payment Information
  • View the content of the uploaded file. There will be a black screen at the right side of the result page showing the .xml file content. I have not included it in the screenshot for confidentiality purposes.
Banking XML Validation Tool DME SAP
Successful Validation

The screens above are for SEPA / Belgium related payments. The online tool I shared is utilized specifically for that kind of validation. You might have noticed that it was able to understand the payment overview in the file.

If you want to do other checks that are not covered by this tool, you can try searching for others or using the usual xml validation tool found online but keep in mind that it more or less checks the syntax and not necessarily the validity of “payment transaction”.

I hope this helps. Good luck! 😊

This blog post has a YouTube version! Click here to see the video.

Coffee Corner: I remember tinkering around DME Trees for the first time. It took me hours to understand the structure and do some urgent comparisons. I definitely found it difficult to compare several versions which is why I included the XML download and Version Management tip. Did you have difficulties in DME Trees too?

4 thoughts on “What is DME in SAP? | End to End Process and Testing | SAP Financial Accounting

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.