XML Implementation
XML Implementation
Copyright
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.
� SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, Duet, Business ByDesign, ByDesign,
PartnerEdge 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 in several other
countries all over the world. All other product and service names mentioned
and associated logos displayed are the trademarks of their respective companies. Data contained in this
document serves informational purposes only. National product specifications
may vary.
� The information in this document is proprietary to SAP. This document is a preliminary version and not
subject to your license agreement or any other agreement with SAP. This
document contains only intended strategies, developments, and functionalities of the SAP® product and is
not intended to be binding upon SAP to any particular course of business,
product strategy, and/or development. SAP assumes no responsibility for errors or omissions in this
document. SAP does not warrant the accuracy or completeness of the information,
text, graphics, links, or other items contained within this material. This document is provided without a
warranty of any kind, either express or implied, including but not limited to the
implied warranties of merchantability, fitness for a particular purpose, or non-infringement.
� SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or
consequential damages that may result from the use of these materials. This
limitation shall not apply in cases of intent or gross negligence.
� The statutory liability for personal injury and defective products is not affected. SAP has no control over
the information that you may access through the use of hot links contained in
these materials and does not endorse your use of third-party Web pages nor provide any warranty
whatsoever relating to third-party Web pages
�
© SAP
Inhalt
Seite 2/10
SEPA in der Schweiz CT pain.001.001.03 (XML-Datei implementieren)
Open the ZIP file and extract ZIP CH_SEPA_CT_yyymmdd to your device.
The name of the xml-file may be different to the name of the DMEE-tree it contains, usually the name is
enhanced with the last date of the tree-update.
Seite 3/10
SEPA in der Schweiz CT pain.001.001.03 (XML-Datei implementieren)
In popup window select Location ”P” as for presentation server (which means your PC). For XML file
please select with F4 help the file, which you have created in chapter 1.1
Seite 4/10
SEPA in der Schweiz CT pain.001.001.03 (XML-Datei implementieren)
Now you have copied the complete format tree with all mappings and validations to your SAP system.
Seite 5/10
SEPA in der Schweiz CT pain.001.001.03 (XML-Datei implementieren)
Click on the save button to store the uploaded DMEE.tree. Thean activate the Format Tree:
Format tree is copied successfully and may be found in the selection list (F4) of transaction DMEE.
1.3 Change Activate Data Medium and arrange it for payment run
F110 if necessary
Open transaction DMEE and select format tree CH_SEPA_CT.
Seite 6/10
SEPA in der Schweiz CT pain.001.001.03 (XML-Datei implementieren)
If the tree is consistent you have to activate the format tree to be used, if the tree is not consisten you
will get a message and a protocol sign in the function line..
Seite 7/10
SEPA in der Schweiz CT pain.001.001.03 (XML-Datei implementieren)
Seite 8/10
SEPA in der Schweiz CT pain.001.001.03 (XML-Datei implementieren)
Seite 9/10
SEPA in der Schweiz CT pain.001.001.03 (XML-Datei implementieren)
Don’t forget Payment methods in Company/Bank determination with FPZP and the selection variants
(OBPM4)!
Seite 10/10