In this post, you will find some questions related to SAP Data Medium Exchange, XML DME Tree, and Payment Medium Output. We will go through each of them and discuss the corresponding answers. Relevant SAP Notes will be provided as well.
Most of these questions have been originally asked on Techlorean’s YouTube channel and were added as a part of this SAP Question Bucket post. Please note that some of the questions have been paraphrased and slightly modified for easier understanding.
Overview of Questions
- Is there an SAP DME Tree Template for SEPA_CT and SEPA_DD?
- How do you connect F110 to a specific DME XML template? For example, we have different Payment Methods in F110 and want each payment method to trigger a corresponding DME XML template.
- In SAP DMEE / DME, what is the purpose of Conversion Function?
- While creating company code and house bank, the level indicated in the DME node is 2. Why can’t it be in level 0 for DME XML file output?
- In SAP DMEE / DME, how do Reference ID’s work?
- What is the use of the FPM_SEPA structure fields XMLNS and XSI in SAP DME Tree Properties Format Attributes Tab?
Is there an SAP DME Tree Template for SEPA_CT and SEPA_DD?
Yes, there are existing templates for SEPA_CT and SEPA_DD DME Trees provided by SAP. You can refer to the following SAP Notes:
Important: Always ensure to search for latest updates on the SAP Notes for SEPA_CT and SEPA_DD. Please read and pay special attention to the attachments contained in the SAP Notes. That is where you will find the template, sample output, mapping guides, etc.
Remember: There are prerequisites stated in the SAP Notes. Be sure to implement and check on the prerequisites to avoid errors.
How do you connect F110 to a specific DME XML template? For example, we have different Payment Methods in F110 and want each payment method to trigger a corresponding DME XML template.
Other alternative versions of the question could be:
- “How do you generate multiple payment medium output files in one F110 run?”
- “How to Generate Multiple DME template output files in one F110 run?”
- “How to attach / link DME file in FBZP?”
To do this, you can:
- Go to Transaction Code FBZP
- Click on Payment Methods in Country Settings
- Select / Highlight the Country and Payment Method in concern
- Click on More Details or Ctrl+Shift+F2
- Navigate to the “payment medium” section (screenshot below)
For each payment method per country there is an entry where you can specify the Payment Medium Format (utilizing the payment medium workbench radio button). This is also seen in the image above.
It is a 1:1 setting meaning 1 payment method per country is to 1 Payment Medium Format. As long as you indicate the payment methods in your F110 Automatic Payment Program parameters, it should pull the corresponding DME config.
Important: This is also considering that your FBZP configurations are accurately configured to pull those payment methods during F110 run.
In SAP DMEE / DME, what is the purpose of Conversion Function?
As mentioned in the SAP Help Document “Conversion of Source Data”, this field or function allows you to convert data to the needed format in your DME file.
The screenshot below shows an example where the amount that is pulled from Structure FPAYH Field Name RWBTR should be converted to “AR.2” format.
This means that when the payment medium output file is generated, the data pulled for the (Amount) Node should follow the specified conversion format.
If you click on the puzzle icon / attributes button beside the Conv. Function field, you will notice a similar setting in the image below.
The conversion function is not limited to amounts. By exploring the list or available options further, you will find other conversion options for date, time, etc.
Important: To prevent errors ensure that you do not use standard conversion function and mapping procedure ‘Exit module’ simultaneously for the same node.
While creating company code and house bank, the level indicated in the DME node is 2. Why can’t payment details be in level 0 for DME XML file output?
This question refers to the images below:
You will notice that the DMEE tree properties has Level 0 and 2 with 9999999 as the repetition factor. This means that Level 0 and Level 9 tagged details can be expected to repeat multiple times.
In the next image, you will see that the house bank element shows Level 2 for its configuration.
Thus the question…“Why can’t it be set to Level 0 if Level 0 can repeat multiple times?”
The house bank is maintained at level 2 because in this example we are considering house bank as part of the payment details / information within the Level 1 tag. It considers hierarchy as visualized in the DMEE blog post.
One way of looking at this is that we are organizing the information using that hierarchy so the “other system” can read the xml file properly.
In the image below showing a high level example of an XML file, the <HouseBnk></HouseBnk> tags are within the <PaymentDetails></PaymentDetails> tags. As such, it wouldn’t be realistic to indicate House Bank as Level 0 because that detail should be within the Level 1 Tag.
Important: The scenario provided in the post is loosely based on existing standard DME trees for xml such as SEPA_CT payments but made simpler for tutorial purposes. You’ll notice that in the SAP template for SEPA_CT DME tree (SAP Note 1062489), it will contain the same levels tab configuration for Level 0,1,2 (where Level 0 is 999…9 and you will also see a level 3).
In SAP DMEE / DME, how do Reference ID’s work?
For Reference ID, you can refer to “Reference ID of Node” in the Additional Info section of the DMEE blog. The Reference ID’s basically allow you to “reuse the information later on” where you can call that ID in another node as mapping.
What is the use of the FPM_SEPA structure fields XMLNS and XSI in SAP DME Tree Properties Format Attributes Tab?
The question refers to the image below where FPM_SEPA was populated in the DMEE Format Specific Structure field under Format Attributes Tab.
The purpose for including the mentioned structure is mentioned in SAP Note 1360908 where it addresses some issues / concerns in the payment medium file output where attributes steer away from ISO (International Organization for Standardization).
The same SAP Note also mentions the need to include structure FPM_SEPA in the SEPA_CT Payment Medium Format configuration (OBPM1) Struct. for format parameters field. Refer to the image below.
On a high-level note, you can simply think of it as a way to standardize attributes relating to XML (XMLNS, XSI, SCHEMALOCATION) and prevent frequent modifications to the DME Tree.
Ideally, you want the XML payment medium output file to be utilized as needed and (of course) be readable for banks. The way to ensure that “readability” is to follow standardized formatting.
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“.