You are on page 1of 8

Extending DME Transfer Files

According to Spanish Banking


Control Council to Support NonEuro Payments

Applies to:
SAP ECC 6.0, SAP_APPL 604, FI-AP-AP-PT Payment Transactions, Financial Accounting Spain.

Summary
The SAP standard supports the creation of DME (Data Medium Exchange) files for Spanish transfers
according to the specification issued by the Association of Spanish banks (A.E.B.).
However this specification regards payments in Euro only. In real life payments are often done in a different
currency. In these cases the DME files created by the standard programs are not usable.
This article describes which coding and customizing changes to do in order to create DME files with the
correct format for non Euro payments.
Authors:

Rainer Zilch

Company: SAP Deutschland AG & Co. KG


Created on: 15 December 2010

Author Bio
Rainer Zilch is consultant for Enterprise Application Integration. He has been working for SAP
since more than 10 years. After having worked with the classical integration technologies like
RFC, IDoc, ALE and Business Connector, he acts now mainly as PI Coach and Integration
Architect.

SAP COMMUNITY NETWORK


2010 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com


1

Extending DME Transfer Files According to Spanish Banking Control Council to Support Non-Euro Payments

Table of Contents
Creation of DME (Data Medium Exchange) Files in the Standard ................................................................. 3
Coding Changes ............................................................................................................................................. 3
Customizing Changes ..................................................................................................................................... 5
Checking the results ....................................................................................... Error! Bookmark not defined.

SAP COMMUNITY NETWORK


2010 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com


2

Extending DME Transfer Files According to Spanish Banking Control Council to Support Non-Euro Payments

Creation of DME (Data Medium Exchange) Files in the Standard


In the standard the program RFFOES_T is used to create data medium exchange (DME) files for Spanish
transfers and/or bank checks. It creates files that correspond to Norm 34-1 of the Spanish Banking Control
Council, 'Consejo Superior Bancario' ('rdenes en soporte magntico para emisin de transferencias y
cheques').
However there are two issues when payments are done in a currency other than Euro.
1. The currency information is missing in the DME files created.
The currency field is optional, but if not given, the currency is always considered to be Euro.
2. The format of the amounts is not correct
According to the specification the total amount needs to have 2 decimals without any punctuation.
However the standard shifts the amounts by two digits
Coding Changes
The coding sections that cause the issues mentioned above are in the program RFFORIE3 which is included
in RFFOES_T.
In order to fix the issues without a modification, you copy both programs to a suitable namespace, e.g.
RFFOES_T to ZRFFOES_T and RFFORIE3 to ZRFFORIE3.
In ZRFFORIE3 you need to do the following changes:
1. In FORM REG_ABRD_LINE_ITEM_FUELLEN
After
DTAXESREG_2_ABRD-F3 = REGUH-ZBNKS.
the following coding needs to be inserted:
if REGUH-WAERS ne 'EUR'.
DTAXESREG_2_ABRD-F4 = REGUH-WAERS.
ENDIF.
2. In FORM REG_SPL_LINE_ITEM_FUELLEN
After
DTAXESREG_2_SPL-F3 = REGUH-ZBNKS.
the following coding needs to be inserted:
if REGUH-WAERS ne 'EUR'.
DTAXESREG_2_SPL-F4 = REGUH-WAERS.
ENDIF.
3. There are 7 spots where the amount is shifted.
The structure is always like this:
IF EURO IS INITIAL.
SHIFT DTAXESREG_1-F1 BY 2 PLACES LEFT CIRCULAR.
ENDIF.
Only the name of the structure is slightly different. Instead of DTAXESREG_1 it is called e.g.
DTAXESTOT, DTAXESTOT_O or similar in the other sections. You best search for
BY 2 PLACES LEFT CIRCULAR to find these sections.
All these sections must be commented out to avoid that the amount gets shifted.

SAP COMMUNITY NETWORK


2010 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com


3

Extending DME Transfer Files According to Spanish Banking Control Council to Support Non-Euro Payments

Having done that, you need to do one change in ZRFFOES_T.


Replace
INCLUDE RFFORIE3.
by
INCLUDE ZRFFORIE3.
to make the program execute your form routines instead of the standard ones.

SAP COMMUNITY NETWORK


2010 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com


4

Extending DME Transfer Files According to Spanish Banking Control Council to Support Non-Euro Payments

Customizing Changes
Finally you need to change the customizing to make the system use ZRFFOES_T instead of the standard
program for creating the DME files.
Execute transaction /spro, click on SAP Reference IMG and go to
Financial Accounting (New) > Accounts Receivable and Accounts Payable > Business Transactions >
Outgoing Payments > Automatic Outgoing Payments > Payment Media > Make Setting for Classic
Payment Medium Programs > Assign Payment Medium Program for Payment Method in Country

SAP COMMUNITY NETWORK


2010 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com


5

Extending DME Transfer Files According to Spanish Banking Control Council to Support Non-Euro Payments

There you can assign the program that is used for each Payment Method. The standard Payment Method for
the DME file creation for Spain is T, however you may have defined a different one.
Enter ZRFFOES_T in column Program in the relevant line.

SAP COMMUNITY NETWORK


2010 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com


6

Extending DME Transfer Files According to Spanish Banking Control Council to Support Non-Euro Payments

Checking the results


After performing a payment run you can check the status of the Payment Transaction in transaction /f110.
On tab Printout/data medium you can see which program with which variant has been executed to generate
the DME file.

When ZRFFOES_T has been used, the DME files have the correct format for the amounts and the currency
information filled.
See example below for a DME file for a payment in British Pounds (GBP).

DME file created with RFFOES_T

DME file created with ZRFFOES_T

SAP COMMUNITY NETWORK


2010 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com


7

Extending DME Transfer Files According to Spanish Banking Control Council to Support Non-Euro Payments

Copyright
Copyright 2010 SAP AG. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG.
The information contained herein may be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.
Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9,
iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server,
PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes,
BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX,
Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.
Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems
Incorporated in the United States and/or other countries.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of
Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, World Wide Web Consortium, Massachusetts
Institute of Technology.
Java is a registered trademark of Sun Microsystems, Inc.
JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by
Netscape.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentioned
herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.
Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and
other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered
trademarks of Business Objects S.A. in the United States and in other countries. Business Objects is an SAP company.
All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document
serves informational purposes only. National product specifications may vary.
These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP
Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the
express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an
additional warranty.

SAP COMMUNITY NETWORK


2010 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com


8