Previously, we had a deep dive discussion on transaction code DMEE where most of the configurations are for the DME Tree creation. This time, we will focus on the overall configurations involved for DME.
The whole DME topic can be complex depending on the requirements and can be a handful to learn in one sitting. As such, I have created a separate and detailed post for transaction code DMEE or DME Tree creation. The rest of the configurations will be found in this post.
If you are looking for the specific post focusing on DMEE, you can refer to: “SAP DME Tree Configuration – DMEE Focused (Simple Explanation)”.
Recall: As seen in previous posts, DME or Data Medium Exchange goes hand in hand with SAP Payments. It is triggered through payment run where you can expect a payment medium output.
- Configuration Objectives
- Additional Information
Before we start with the actual configuration proper, let us try to understand our objectives. Ideally, we want to be able to create a payment medium output. In this scenario (or for our example), we want to be able to:
- Generate a payment medium output (XML file output) upon automatic payment run (F110).
- Ensure that SAP will pull the right payment medium output template by linking the concerned payment method and country combination.
In this part of the configuration, you will create a payment medium format and define its settings. Please use the same name as your DMEE tree later on.
The payment medium format screen consists of the following sub folder settings:
- Event Modules for Payment Medium Formats
- Format Parameter Required Fields
- Supplements for Payment Medium Formats
- Text Fields for Reference Information
In the image below, we created payment medium format “SEPA_CT”, selected that entry, and clicked on more details (see arrow).
You will encounter a similar screen below. This is where you will define the payment medium format settings according to the format requirements.
Notice how we specified “Electronic Payment Medium”and File Type “XML” since our example scenario expects to generate an XML file.
For those wondering “What is FPM_SEPA?” You can refer to linked post.
Moving forward to our sub folder settings, click on “Event Modules for Payment Medium Formats”.
Here you need to define all concerned exit modules / function modules that you will utilize in your DME Tree creation / DMEE.
The next 2 sub folders are not necessarily needed for our scenario.
If you need to indicate settings for “Format Parameter Required Fields (required fields from the format structure)” and “Supplements for Payment Medium Formats (additional format supplements), you may do so.
The last sub folder “Text Fields for Reference Information”, is only utilized for Note to Payee functionality. If you need to more about this setup, you can refer to “SAP DME Note to Payee Functionality”. Else, you can just leave this blank for now and come back to it later on.
For more information about the format of the Payment Medium Workbench and the necessary Customizing settings for SEPA CT, please check SAP Note 1062489.
In this part of the configuration, you will configure the SAP Automatic Payment Program (transaction code: F110).
The idea is to link the DME template to the proper payment method in FBZP such that when F110 is executed, the linked payment medium format for our payment medium output will be generated.
In FBZP, we will focus on 2 buttons for the linkage proper.
- Pmnt methods in country (priority when using DME Engine)
- Pmnt methods in company code (additional information only)
Pmnt methods in country (priority when using DME Engine)
Here you will select the country and payment method combination and click on more details as seen in the image below.
You should be presented with the screen below.
This is where we will configure the settings for our payment method. The basic settings are highlighted below as well.
The significant part of this configuration lies in the yellow highlighted area. This is where you specify or link the payment medium format.
Here we selected “use payment medium workbench” and specified the format “SEPA_CT”.
Ideally for each payment method and country combination, you should define the following basic requirements:
- Payment type (orange highlight): Specify if the payment method will be for outgoing or incoming payments.
- Characteristics for classifying the payment method (green highlight): The method of payment and its characteristics. In our example, we specified bank transfer and allowed for personnel payments. The rest of the settings will be up to your requirements.
- Master record requirements (purple highlight): Requirements of a particular payment method (such as the address requirement) that should be met for invoices to be paid with the payment method. In our example, we required Bank Details, IBAN, and SWIFT Code. If those are not maintained, then the payment run using this payment method should not push through.
- Document types (pink highlight): The document types used for posting and clearing documents. These are standard SAP document types.
- Print program (yellow highlight): The print program and the print data set for the payment method. This is where we linked the payment medium format.
For the next images, we will move on to the sub folders in this configuration:
- Currencies Allowed: This allows you to restrict the payment methods to a specific currency. If you leave this blank, then the payment method is valid for all currencies. In our example, we restricted the payment method “S” to EUR currency only.
- Permitted Destination Countries: This allows you to restrict payment methods to specific destination countries. In our example, we left the entry blank so that this payment method will be allowed for ALL countries.
- Note to Payee by Origin: This allows you to link Note to Payee settings from transaction code OBPM2. You may refer to “SAP DME Note to Payee Functionality” for more information.
To avoid information overload, this section will simply focus on the linkage of DME template.
Pmnt methods in company code
Going back to FBZP and clicking on the “Pmnt methods in company code” button, you will see the screen below. Select the company code and corresponding payment method (emphasized in blue), then click on more details (see arrow).
The following settings below are simply provided for additional information purposes only.
For example, if I use Payment Method “S” and indicated a minimum amount of 1.000.000.000,00 EUR then I should expect an error in F110 if I try to pay an invoice worth 100 EUR.
On the bottom of the same screen, let us focus on the payment advice control area. This is another Note to Payee functionality setting.
Note that we will cover other FBZP settings in a separate post. For now, we will focus on DME related settings.
In essence: when it comes to linking a DME template or payment medium format, we focus on the payment method – country level setting not on the company code level.
In this part of the configuration, you will be creating the actual DME tree. Here you will configure the actual settings, formatting, details, mapping, etc. of the DME tree. Basically, your payment medium output should follow the format and structure as configured in transaction code DMEE.
As mentioned, you can refer to: “SAP DME Tree Configuration – DMEE Focused (Simple Explanation)” for a detailed step by step guide. This post will mainly focus on the rest of the configurations to avoid information overload.
In this part of the configuration, you will specify your payment medium format per company code and house bank.
To edit a specific variant, click on Variant > Edit Variant.
This action will redirect you to the screen below. This setting focuses on the payment medium format and print/output settings.
For those curious on the filename above, this is an example path that points to a server folder where the payment medium files will be stored upon generation.
Meaning to say, when F110 is run and a payment medium output is created, the file should be stored in the maintained server location.
- OBPM1 – Create Payment Medium Format
- FBZP- Link Payment Medium Output to Payment Method and Country Combination
- DMEE – Creation of DME Tree Structure and Format
- OBPM4 – Payment Medium Output separation (specify per company code and house bank combination) + Payment Medium Format Print / Output Settings
Question & Answer
For those of you who are interested to know more about DME, you can refer to this Q&A post: “SAP Question Bucket 1 | SAP Data Medium Exchange, XML DME Tree, Payment Medium Output”
The example above is loosely based on SEPA Credit Transfer payment method so you may find some similarities. The information below is created for tutorial purposes only but the general idea remains the same for other payment methods. You need to be able to create the payment medium output format and link it to the concerned payment method and country combination.
Hopefully by the end of this post, you will understand the purpose of the configurations.
The proper payment medium output may differ from country to country (country-specific) and some banks may have other specific requirements. Be sure to consider those when you do your configurations.
I hope this helps. Good luck! 🙂
Other Learning Alternatives
Looking for an on-the-go copy of all DME topics? Check out “SAP Data Medium Exchange eBook by Techlorean“.
- 2 formats readily available upon purchase (.kpf for Kindle and .pdf for PDF)
- 109 in-depth visual pages
- Take advantage of the Referral discount: Refer a friend and get 20% off! They’ll get 20% off too.