Having seen a lot of folks posting for help on SEPA/DMEE/PMW, I decided to create a document from my experiences which I would like to share. Before presenting these config steps, I would like to reference a document which I used as a guide for my project work on SEPA Credit Transfer, and would also like to give credit to its author Juergen Weiss, Director, SEPA-now Consulting. His document helped me in my project and also proved to be a stepping stone in authoring this document. His original work is posted at:
Ready Your SAP System for the New Payment Methods within the Single Euro Payments Area
http://www.financialsexpertonline.com/article_printable.cfm?id=5637
Here goes my attempt to explain these settings:
What is SEPA?
SEPA stands for Single Euro Payments Area (SEPA). SEPA enables companies to make and receive payments using their bank within Europe. SEPA transactions are carried out solely in Euro currency. SEPA applies to all national and cross-border Euro zone payments among its 32 member states.
And what is SEPA Credit Transfer?
SEPA was originally launched in January 2008 with the introduction of the SEPA credit transfer payment instrument. The SEPA credit transfer does not differ significantly from the existing standard credit transfer within the EU, but it eliminates the current 50,000 Euro value limit.
***Important Note:SEPA credit transfer payment instruments require the use of the international bank account number (IBAN) and SWIFT code. Companies have to update their master data and maintain both IBAN and SWIFT.
Brief Introduction of PMW and DMEE:
In contrast to the classic RFFO payment medium programs, the PMW allows you to maintain, configure, and enhance your payment formats more easily. It reduces complexity and you only tool (PMW) needs to be maintained.
The DMEE is integrated within the PMW, which facilitates generating files for the defined payment formats. The DMEE provides a customizing tool in the form of a graphical editor, allowing you to model an externally defined file format to meet the requirements of your financial institution.
DMEE tree structure for SEPA_CT
Image may be NSFW.
Clik here to view.
Settings to be made for SEPA_CT:
The most recent version is SEPA_CT_00100103. Please check with your financial institution (bank) regarding their compatibility.
*** Important Note: It is advised to create a copy of the original SAP delivered format (in other words, copy SEPA_CT as ZSEPA_CT)
Tcode: OBPM1
Image may be NSFW.
Clik here to view.
Double-click the ZSEPA_CT payment medium format to validate that the following PMW settings are maintained correctly:
- Checkmark "Payment medium without docs". Type should be XML
- The Documentation module field should be DMEE_SEPA_CT (which contains some general text provided by SAP describing the SEPA format delivery)
- Checkmark "Mapping using DMEE engine"
- The Payment medium output divided by level of detail section should have "Company code" and "House bank" checked.
Image may be NSFW.
Clik here to view.
The Company Code/Housebank level of detail combines and groups your outgoing payments in a file. This happens immediately after the payment run (program F110) by the program RFPAYM_SCHEDULE, which sorts the pool of items to be cleared. In the case of the SEPA credit transfer, the PMW creates a separate payment file for each combination of company code and house bank that was used in the payment run. The logic of this step is similar to the selection variants of the classic RFFO* programs. You have to assign a selection variant of the generic payment medium program SAPFPAYM to each of these payment groups to ensure that each payment is contained in one payment medium.
Which takes us to creating our next setting: The Payment Medium Variant:
TCode: OBPM4
One of the advantages of the PMW is that you can maintain these selection variants centrally instead of assigning them for the classic RFFO* programs as a parameter in every payment run.
Image may be NSFW.
Clik here to view.
- Find the ZSEPA_CT format from the list, double click on it
- In the Sel. variant column/cell for your company code/housebank, enter a variant name (I chose to enter sepa_ct) and then press Enter
Image may be NSFW.
Clik here to view.
- Select Enter to the dialog message for creating a new variant and then save a you would normally do when creating a variant
Image may be NSFW.
Clik here to view.
Settings in Maintain Payment Program (FBZP):
Before we can actually use SEPA_CT, we need to make sure we setup this payment method in country and company code.
TCode: FBZP
- Click Payment Method by Country
***Important Note: The SEPA_CT already exists in country "DE". You can copy from here to setup for your country
Image may be NSFW.
Clik here to view.
Image may be NSFW.
Clik here to view.
- Select "Outgoing payments" radio button
- Select "Bank transf" radio button
- Checkmark Bank Details, and then checkmark IBAN Required and SWIFT Code Required ***Important Note: Within the Vendor Master Data (Bank Details tab), the IBAN and SWIFT fields will have to be maintained in order for SEPA_CT to accurately create proposals and payment run
- Posting Details document type for payment and clearing depends on your business scenario, but the fields will have to be populated
- Select "Use payment medium workbench" radio button and enter ZSEPA_CT as your format
- Double click "Allowed currency" folder on the left and enter Euros only
- Double click "Note to Payee", this should default to the SAP delivered assignment
- Next, from FBZP main screen, click "Pmnt methods in company code" and maintain this payment method in your co code. Here also you can copy from SAP delivered payment method from co code 1000 Germany payment method 5
Image may be NSFW.
Clik here to view.
Now when you use F110, under the Printout/data medium tab, you will see program RFFOAVIS_FPAYM. Here you will use your newly created variant. Then make sure to checkmark print DME option at the time of Proposal and Payment Run. This will generate an DME output file to send to the bank
Image may be NSFW.
Clik here to view.
Thanks,
-Amir