Professional Documents
Culture Documents
SampleSettings CH ISO20022 - 20170502 - EN
SampleSettings CH ISO20022 - 20170502 - EN
The Information shown in the following slides is intended as a support for customizing the settings needed for processing ISO20022 files (pain.001,
pain.002, pain.008, camt.053, camt.054) without any obligation. The slides are not exhaustive. The notes shown can be replaced or updated by newer
ones at any time.
Payment Types 2.1 and 2.2 aren’t supported anymore by recommendation of Postfinance regarding to «IBAN
only». They are covered with Payment Type 3.
Prerequisite: Maintain IBAN in the master data in tab Bank Account data.
• Parameters Batch booking / Type of Advice allow the following combinations (refer to page 45 of SIX Business Rules):
• https://www.six-interbank-clearing.com/dam/downloads/en/standardization/iso/swiss-recommendations/business-rules.pdf
In OBPM4 you will set the name space of the XML File
and e.g. Batch Booking and Type of Advice Parameters.
Country assignment:
• The two different formats are customized in the payment methods customizing via supplements for
payment formats.
• It is important, to make the settings in V_T001I for the parameters like it is shown in the ‘Implementation
Guideline’ attached to note 2324390, if You use CH-DD. For CH-TA You could reuse the existing LSV+
parameters. In the company code’s parameters you maintain the according entries.
• Maintain the settings in sequence 1) to 4). You can maintain CH-DD the same way as CH-TA as an own
payment method with supplement for payment methods CH-DD.
• For CH-DD Postfinance recommends to start with the open accounting method: this implies to use payment
orders like with CH-TA. Open items are cleared when receiving CAMT files. Don’t forget to use Prefix ZR in
the XBLNR interval for the payment order number range.
XSLT
FF_5 CAMT053/54 FEBAN-Tables
Transformation
• Transformations from note 2283622 can be created with transaction XSLT_TOOL. (Developer key is needed).
• After pressing the «Create» Button (1) You have to choose the type of the transformation (XSLT, (2)),
after that You save and choose a package in Your namespace (3), then You first delete the proposed code
in the tab ‘Source Code’ and then copy/paste the code from the word document (4).
FF_5
https://www.six-interbank-clearing.com/dam/downloads/de/standardization/iso/swiss-recommendations/implementation-
guidelines-camt.pdf
© 2017 SAP AG. All rights reserved. 16
Electronic Bank Statement CAMT.053/054
Implementation
Transaction type
UNALLOCATED is
used for all BTC’s that
are not assigned.
To put the relevant positions into the Payment lot, View V_TFK028G has to
be maintained with SM30:
‘‘ no transfer
• The existing processing of ISR incoming payments files of type V11 with transaction FESR (Report RFESR000) doesn’t exist anymore and is replaced by the
processing of camt.054 files.
• Customizing transaction OBAV for table T049E is still existing, in OBAV you set e.g. per ISR-participant, on what position of the ISR reference You’ll find the document
number and the customer number. The account numbers customized in OBAV could be used according to the next two slides.
• To interpret the information of the ISR reference, interpretation algorithm 909 is used that is attached to note 2283622. Algorithm 909 has to be assigned in OT83 to
BTC’s that are used in ISR-Processing, i.e. for example PMNTRCDTVCOM. System tries to clear the open item based on OBAV settings. If it is unsuccessful,
standard interpretation is taken. We assume the banks will provide a dedicated BTC (like VCOM) for incoming ISR Payments.
• In the above example the assignment for the processing with transaction type ZAMT5354 with camt.053 (sums) and camt.054 (details) is set under the assumption,
that there are also other BTC’s than ISR processed. If You would only replace FESR standalone with camt.054, You could use the settings for a transaction type that is
used to post sums and detail at once accordingly to post Bank- and Subledger Accounting from one single file.
2)
Refer to Notes
1075859 – 1722284 – 1769711 – 1957980 Bank Communication Management
Result:
REJ7 (DD) und REJ8 (CT) are used, if additional activities are needed for
RJCT (refer to slides about returns customizing).
REJ9 can be used when no additional activities are needed. E.g. you could
default all not explicitly customized RJCT’s to REJ9.
Define Transaction Type and External Transaction Types (Business Transaction Codes BTC)
zuordnen
External Transaction REJ7 und REJ8 are shown only for illustration: RJCT is the
external Transaction Type where the Posting-Rule’s settings are overridden by the
Returns Processing setting!
© 2017 SAP AG. All rights reserved. 39
PAIN.002 Status Messages / Confirmations
for FI / Credit Transfer / Sample Settings
Because you can assign only one transaction type to a bank account the examples
shown on the slides before need to be integrated into your usually used transaction
type:
Transactions / Reports
Before ISO 20022:
FPBMC Report RFKKCHINC00 EBS to Multi Cash
FPB7 Report RFKKKA00 Creation Lot from EBS
FPB17 Report RFKKKA00 Creation Lot from MultiCash
Validation portals
SIX https://validation.iso-payments.ch
PostFinance https://isotest.postfinance.ch/corporates/login
UBS https://ubs-paymentstandards.ch/vp/login
Credit Suisse https://iso20022test.credit-suisse.com/login
ZKB https://testplattform.zkb.ch/login
Raiffeisen https://isotestbank.raiffeisen.ch/corporates/login
General Links:
www.migration-zv.ch Information and Roadmap Financial Center Switzerland
www.iso-payments.ch Recommendations on exchanging of data between customers and banks
• 2283622 ISO20022 CAMT053 CAMT054 PAIN002 processing / recommendations and templates for Switzerland
• Contains PPT Templates for camt.053/camt.054 as Attachment
Contains CAMT.053_V4 and CAMT.054_V4 transformations as Attachment
Contains pain.002 Transformation for BCM
Contains OBAV Settings / Exit FEB00001
• 2358814 CGI_XML_CT for FI-CA: contains documentation “Note 2358814 manual preimpl steps.pdf”
• 2282051: Pain.002 for FI-CA: Contains transformation TRANS_SEPA_DD_RJCT_CURR , implement also notes 2286740,
2379495, maintain view V_FKK_SEPA_XSLT (like in note 1995926).
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.
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 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.
Please see http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.