SAP Integration

Package for SWIFT

Overview
Status: (05/07/07)

SAP AG

Objectives

After completing this presentation, you will be able to:

Explain the Concept of SAP Integration Package for
SWIFT
Describe the Main Features of SAP Integration
Package for SWIFT
Understand the Architecture of SAP Integration
Package for SWIFT
Get an overview of the Main Components of SAP
Integration Package for SWIFT

SAP AG 2007

SAP AG

SAP Integration Package for SWIFT

Features
Availability
Architecture Overview
SAP Consulting Service Offerings

SAP AG

SAP Integration Package for SWIFT

Enables companies to access multiple banks through a single
connection for real-time exchange of payment and settlement
messages via SWIFTNet
It is architected with pre-configured message and process
mapping between the application interfaces and business logic of
the SAP Financial Supply Chain Management application, SAP
ERP Financials and the SWIFT infrastructure
Covers the entire pay-to-reconcile business scenario
Initially supports FIN and FileAct messaging services, enabling
companies to send and receive both MT- and MX-based messages
Supports the new ISO 20022 payment standards, which are
compatible with the upcoming Single Euro Payments Area (SEPA) to
become effective on January 1, 2008
Provides technical message mappings for positive and negative
acknowledgements and delivery notifications
SAP AG 2007

SAP AG

Bank Communication Today: Looks Familiar to you?

Bank
Corporate client
Accounts
Payable
Accounts
Receivable

VAN
Host to Host
Leased line

e-banking

Treasury

Internet
Other

e-banking
PSTN

fax-banking
SAP AG 2007

In todays corporate to bank communication, we have an array of multiple standards and communication
protocols to interface software solutions, in order to enable transmission of payment related information:
y From Host to Host communication via VAN
y E-banking solutions using a leased line or via the Internet
y Even communication via fax using the telephone network

SAP AG

Bank Communication Tomorrow: SAP Integration Package

for SWIFT
Bank

Corporate client

Accounts
Receivable
Treasury

Other

Bank Relationship Management*

Accounts
Payable

SAP
NetWeaver
Process
Integration
(formerly XI)

SWIFTNet
SWIFTNet
interface

SAP
Integration
Package
for SWIFT

* available from SAP ERP 2005 onwards

SAP AG 2007

Tomorrow, we can benefit from the new solution: SAP Integration Package for SWIFT, embedded within
our SAP Exchange Infrastructure. This will enable communication from the corporate client to the bank
using a single gateway via SWIFTNet software.

Additionally, the Financial Supply Chain Management product within SAP Financials, will be enhanced
by SAP Bank Relationship Management, available from SAP ERP 2005 onwards, which will enable
monitoring of the end to end financial supply chain, from the creation of the payment file to the upload of
the bank statement, covering the full end-to-end pay-to-reconcile business scenario, as well as grouping of
different payment programs and batching of files in a way that they can meet banking deadlines, allowing
for cost savings and improved cash management.

SAP AG

Pain Points for Corporates (I)

Interface costs (hardware/software/network)
Global companies typically operate between 8 to 15 different bank
relationships
Requiring just as many different interfaces (online banking tools)
Costs per interface: estimated EUR 20.000 50.000 per year
That means in total EUR 240.000 to 450.000 spent per year only
for bank communication

SAP AG 2007

These slides describe the pain points experienced today by corporates. These paint points illustrate the
reasoning behind the development of SAP Integration Package for SWIFT and SAP Bank Relationship
Management functionality.

Today many corporations are struggling with a very complex system landscape in order to integrate their
multiple ERP systems with their banks. This results in multiple, often proprietary bank communication
systems and high annual interface costs.

SAP AG

Pain Points for Corporates (II)

Manual processing costs
Payment Orders for each bank have to be manually handled
separately per bank relationship in the ERP System
Bank Statements have to be collected from each bank separately
and manually handled in the ERP System
Manual handling of 8 to 15 different e-Banking tools (upload,
authorize, send)
Current solution for payment transfers is inefficient:
Many
No

different people involved - takes too much time

straight-through-processing

Changes

in used media sometimes required (e.g. file-to-

paper)

SAP AG 2007

SAP AG

Pain Points for Corporates (III)

Cost of Working Capital
Lack of visibility of Financial Supply Chain. Status and
confirmation messages are often not received
Errors in payment orders are identified too late
Certain level of liquidity must be kept on transaction accounts
due to lack of information
Dependency on house banks

High dependency on house banks without standardized

interfaces due to cost of changing bank relationship
Security issues
Security gaps during payment file transfer (authorization,
signature and encryption often not part of the solution)

SAP AG 2007

The lack of transparency leads to suboptimal working capital usage and a below-average financial supply
chain.

Customers often face also corporate governance issues in order to keep up with compliance directives and
operational risks to achieve accounting transparency.

SAP AG

End-to-End Financial Supply Chain

Corporate

Supplier
Invoice
Processing
Payroll
Processing
Treasury
Cash
Management

Financial Supply Chain Management

Customer
Invoice
Processing

Network

Bank

Payment Initiation
Status Message
Payment Confirmation
Request for Cancellation
Cancellation Status

Payment
Processing
Deposits
Management

Intraday-Statement
End-of-Day Statement

SAP AG 2007

This slide describes the flow of communications between a corporate and its bank

SAP AG

10

End-to-End Financial Supply Chain with SAP

SAP ERP

Network

SAP for Banking

SRM

Treasury
Cash
Management

Payment Initiation
Status Message
Payment Confirmation
Request for Cancellation
Cancellation Status
Credit/Debit Advice
Bank Statement
.

SAP Exchange Infrastructure (XI)

Payroll
Processing

SAP Exchange Infrastructure (XI)

Customer
Invoice
Processing
Supplier
Invoice
Processing

Financial Supply Chain

Management

Global Trade Services

CRM

Payment
Processing

Deposits
Management

SAP AG 2007

These communications are now enhanced with the usage of full portfolio of solutions from SAP, in
particular, with the Financial Supply Chain functionality of Bank Relationship Management, and the SAP
Integration Package for SWIFT embedded in the SAP Exchange Infrastructure (XI).

SAP AG

11

Enhanced Bank Communication with SAP - Overview

SAP ERP

SAP
Bank
Relationship
Management

Accounts
Payable

Batching

Accounts
Receivable

Approval Rules

Treasury

Digital Signature

Human
Capital
Management

SAP
Exchange
Infrastructure

SWIFT Net
FileAct and FIN

SAP
Integration
Package
for
SWIFT

SWIFT
Alliance
Access

Mapping
Routing

Payment Monitor

Workflow

SWIFT
Alliance
Gateway

SAP XI
Resource
Adapter

SAP AG 2007

This is an overview of enhanced bank communication with SAP.

In the SAP ERP side, we have functionality for handling of Accounts Payable, Accounts Receivable,
Treasury transactions and the handling of Human Capital Management transactions.

New is the SAP Bank Relationship Management functionality, integrated in the SAP Financial Supply
Chain Management module within ERP. Below are the main steps that take place in the SAP BRM:
Batching, Approvals, handling of digital signatures, the new Payment Monitor, and Workflow
functionality for approval of payment files.

The SAP Exchange Infrastructure contains the SAP Integration Package for SWIFT, which performs
Mapping and Routing of payment messages.

Also integrated with SAP is the SWIFTNet software for FIN and FileAct messages. In one side the
SWIFT Alliance Access and in another side, the Gateway.

Finally we have the Banks, receiving and sending payment messages to corporates.

SAP AG

12

Bank Communication with SAP ERP PRESENT

SAP ERP
System

3rd Party
System

Execute
Payment
Program

Upload File

File
Server

Send Payment
Order to Bank

Import
Bank
Statement

Collect Bank
Statement

Post/Processing
and
Clearing

Security

Bank

Create
Payment
Order

Security:
Authorization
Encryption
Digital Signature

Download
File

SAP AG 2007

Today, all communication of payment transactions is routed via the File Server, and a myriad of 3rd. Party
Systems to upload the file, introduce security for the handling of the file (including authorization handling,
encryption, and digital signatures), until we are able to send the payment order to the bank, collect the
bank statement, more security, download the bank statement file and route it via the file server until is
imported in SAP

SAP AG

13

Bank Communication with SAP ERP FUTURE

SAP ERP
System

Execute
Payment
Program
Create
Payment
Order

SAP Bank
Relationship
Management

Post/Processing
and
Clearing

Bank

Create Batch

Routing

Payment
Approval

Mapping

SWIFTNet
FileAct / FIN

Worklist

Security
Approval Workflow
Authorisation
Digital Signature

Import
Bank
Statement

SAP Exchange
Infrastructure

Receive
Status
Messages
Exception
Handling
Bank Statement

Security
Encryption
Digital Signature

SAP Integration
Package for
SWIFT

SWIFT Alliance
Access / Gateway

Resource
Adapter

SAP AG 2007

Tomorrow, all the different steps involved in handling of payment communication between the corporates
and their banks will be done inside SAP

This graphic illustrates all these different steps within each of the SAP solutions

SAP AG

14

End-to-End Financial Supply Chain with SAP and SWIFT

Corporate

Bank

SAP ERP
Payment
Engine

SAP XI

SAP XI

SAP Integration Package for

SWIFT
2

3a

4a

13

SWIFTAlliance
Gateway

11
Bank
Statement

Deposits
Management

Status
Message

14
Bank
Statement

10

Delivery
Notification

Acknowledgement

Payment
Order

4b

Status
Message

3b

Payment
Order

SAP Bank
Relationship
Management

Payment Order initiated in mySAP ERP and sent to SAP XI.

Format: CustomerCredit-TransferInitiation" (pain.001.001.02).

Payment order is sent from SAP XI to SwiftNet via

SwiftAlliance Gateway (FileAct).

3a

Swift sends confirmation (acknowledgement) to SAP XI and

SAP XI forwards it to mySAP ERP.

3b

Swift sends confirmation (delivery notification) to SAP XI and

SAP XI forwards it to mySAP ERP.

4a

mySAP ERP receives acknowledgement (no mapping/direct

import) and updates payment status in SAP Bank
Relationship Management.

4b

mySAP ERP receives delivery notification (no mapping/direct

import) and updates payment status in SAP Bank
Relationship Management.

Payment order is transferred via SwiftAlliance Gateway

(FileAct) to SAP XI.

Payment order is transferred from SAP XI to Payment Engine

to be processed (no mapping).

After validation of the payment order the Payment Engine

sends a status message back for validation. Format:
PaymentStatusReport (pain.002.001.02).

Status message is sent from SAP XI to SwiftNet via

SwiftAlliance Gateway (FileAct).

Status message is forwarded via SAP XI to mySAP ERP (no

mapping/direct import).

10

mySAP ERP receives status message and updates payment

status in SAP Bank Relationship Management.

11

Deposit Management system creates a bank statement

(MT940) to be sent to mySAP ERP.

12

Bank Statement is sent through SAP XI via SWIFTAlliance

Gateway (FileAct) to SwiftNet.

13

Swift send bank statement to SAP XI (no mapping).

14

ERP system receives bank statement and performs automatic

reconciliation.

12

SWIFTAlliance
Gateway

SAP AG 2007

An overview of all messages exchanged between a corporate and its bank, and how they are routed in the
context of SAP Bank Relationship Management, SAP Integration Package for SWIFT and SWIFT
Alliance Gateway.

In this example, a coporate sends a SEPA CustomerCreditTransferInitiation Message (pain.001.001.02), in

the new XML format.

SAP AG

15

SAP Value Proposition

SAP would like to improve direct bank communication within SAP

ERP and allow corporations to seamlessly integrate their ERP

systems via SWIFTNet or other connections (i.e. the internet) with
financial institutions
In addition, corporations should be able to track and monitor the
status of their payments to improve the visibility into their financial
supply chain
Another improvement will be the segregation of duties during the
outgoing payment process to reduce operational risks and to
improve secure approval of outgoing payments

SAP AG 2007

SAP AG

16

Benefits of Improved Bank Communication

SAP Integration Package for SWIFT offers:
Independency from proprietary payment standards and bankspecific e-banking products
Single communication channel to SWIFTNet
Standardised and uniform Payment Gateway
Enhanced Straight-Through-Processing (STP) rates
More cash flow transparency and visibility of working capital
Reduced maintenance costs by using global payment standards
Increased security and compliance
Readiness for SEPA and UNIFI/ISO20022 standard

Lower Total Cost of Ownership

SAP AG 2007

A summary of the benefits of improved Bank Communication:

Single communication channel to SWIFTNet: will enable your company to communicate with all your
banking partners through this one channel. Your company can realize cost savings for the support and
maintenance of your payments infrastructure.

SAP AG

17

In Addition
Combining SAP Integration Package for SWIFT with other SAP
applications, such as SAP Bank Relationship Management or the
SAP In-House Cash application, can create even more value
regarding the tracking of the payment life cycle or the setup of a
payment factory

SAP AG 2007

SAP AG

18

SAP Integration Package for SWIFT

Features
Availability
Architecture Overview
SAP Consulting Service Offerings

SAP AG

19

SAP Integration Package For SWIFT: Features (I)

SWIFTNet Integration
Inbound and outbound support of SWIFT FileAct and SWIFT FIN
Integration with SWIFT architecture (SWIFT Alliance Access and
SWIFT Alliance Gateway)
Management of local authentication and integrity between SAP
NetWeaver XI and SWIFT Alliance Access and Gateway (HMACSHA256)
SWIFT Standards XML Support
Standard XI mappings for UNIFI / ISO20022 messages. Initial
implementation of:
Customer Credit Transfer Initiation (pain.001.001.02)
Customer Direct Debit Transfer Initiation (pain.008.001.01)
Payment Status Report (pain.002.001.02)
Cash management advice message
Cash management statement message
SAP AG 2007

SWIFTNet Integration: Comment: HMAC stands for Hash Message Authentication Code

SWIFT Standards XML Support: It supports the newly designed XML payment schemes as defined by the
European Payments Council, the governance body that guides and implements SEPA initiatives.

Initially the following XML schemes are supported by the application (subject to change without notice):
y Pain.001.001.02
y Pain.008.001.01
y Pain.002.001.02
y Cash Management Advice Message
y Cash Management Statement Message

SAP AG

20

Chapter 2 - Ins and Outs of the FIN Messages

SAP Integration Package For SWIFT: Features (II)

SWIFT Standards MT Support
Processing of:
Payment related
Payment Initiation (MT 101)
Notice to Receive (MT 210)
Foreign Exchange Transaction (MT300)
Fixed-Term Deposit Money market Transaction (MT320)
Account Status related
Confirmation of Debit (MT 900)
Confirmation of Credit (MT 910)
Statement related
Customer Statement Message (MT 940)
Interim Transaction Report (MT 942)

SAP AG 2007

In addition to the messages listed above, SAP Integration Package for SWIFT supports the following
traditional SWIFT

SAP AG

21

SAP Integration Package for SWIFT

Features
Availability
Architecture Overview
SAP Consulting Service Offerings

SAP AG

22

SAP Integration Package for SWIFT: Availability

Tight SAP Integration
SAP Integration Package for SWIFT will be available for SAP R/3
4.6C and upwards
Support of various Status Messages in conjunction with SAP
Bank Relationship Management (prerequisite: SAP ERP 2005)

SAP AG 2007

At this point of time, the SWIFT Adapter will support FIN and FileAct.

The exact schedule of the ERP 2005 downgrade for the Bank Relationship Management is still open. The
downgrade is however planned to start in Oct. 2006.

Note: XI proxies, UNIFI messages and mappings will be available with this ECC Support Package
earliest.

Open: Availability of InterAct.

SAP AG

23

SAP Integration Package for SWIFT

Features
Availability
Architecture Overview
SAP Consulting Service Offerings

SAP AG

24

Bank Communication: SAP Integration Package for SWIFT

SAP Integration
Package for SWIFT

SWIFTNet FIN
SWIFTNet FileAct
SWIFTNet
Interface

Includes XI Content and SWIFTAlliance Access

additional modules
SWIFTAlliance Gateway
for the File Adapter:
(Conversion, Transfer,
Management of
Authentication)

SAP AG 2007

A more detailed view of what will be delivered with the SAP Integration Package for SWIFT: XI Content
and additional modules for the File Adapter

SAP AG

25

System Landscape
Internal
Network
SAP

Supplier
Invoice
Processing
Payroll
Processing
Treasury

Cash
Management

Firewall
USB Dongle

SAP Exchange
Infrastructure
File Adapter

input

FIN-Module

output

FileAct

error

Outside
World

Firewall
ARP
Proxy

Financial Supply Chain Management

Customer
Invoice
Processing

Internet

SWIFT
Alliance
SWIFTAlliance
Access

Secure Card
Reader
RS-232
ICC

SWIFTAlliance
Gateway

VPN
Box

SWIFTNet Link
Modem

Files to/from the

shared folders of
SWIFT Alliance
(triggered by XI)

Dial-Up

SWIFTNet FIN
SWIFTNet FileAct

Communication
through SIPN

SAP AG 2007

SAP AG

26

Architecture Overview SAP Integration Package for SWIFT

Messaging
Layer

SAP
Exchange
Infrastructure
Message

Communication
Layer

SWIFT

SWIFT

Alliance
Access

Alliance
Gateway
MT

SAP File Adapter

File
Exchange
(FTP,
shared
folders)

AFT
Adapter

FIN
File Act

MX

HMAC-SHA256

Native SAP
FILE ADAPTER
with extended
modules

Keyed-hash
message
authentication
code

SWIFT
Alliance Access
native Automated
File Transfer
Adapter

SAP AG 2007

SAP AG

27

Architecture Overview in SAP Exchange Infrastructure (XI)

Swift Adapter puts payload into
a technical XML envelope
Envelope is removed again by
SWIFT Gateway

XI

file
envelope

create
SWIFT

SWIFT
Adapter
2
1

SWIFT Alliance
Gateway

Other
Adapter

XI
Interfaces

Interface

Download
Proxy

Payment
Program or

File Adapter

ERP

Mapping
to ISO 20022

SAP AG 2007

Note: SWIFT Adapter refers to Enhancements of the XI File Adapter.

SAP AG

28

Software Components for XI Content

ERP Service Enabling Component containing the SAP Interfaces

For example: CollectivePaymentOrderRequest

Mapping between XI Interfaces and ISO20022 interfaces

For example: CollectivePaymentOrderRequest is mapped to
CustomerCreditTransferInitiation

Component containing the ISO20022 Interfaces

Component containing enhancements for the XI File Adapter

(security, file envelope)

SAP AG 2007

SAP AG

29

Software Components for XI Content

Product: SAP INTEGRATION FOR
SWIFT 1.0

This title appears in the

Integration Builder

ISO20022 ERP 1.0

ISO20022_ERP
(Dummy)

ISO20022 1.0
ISO20022
(Dummy)

4a

Swift 1.0
SWIFT
SWIFT-Adapter for ERP

Adapter Modules

SWCV

Java

Techn. Comp.
ESA ECC-SE 700
1

ECC-SE
ESA FAST TRACK (ERP)

XI CONTENT ISO20022 ERP 1.0

2 XI_CNT_ISO20022_ERP

XI CONTENT ISO20022 1.0

3 XI_CNT_ISO20022

XI CONTENT ISO20022 ERP

XI CONTENT ISO20022

Swift Adapter 1.0 for ERP

4b XI_CNT_SWIFT
SWIFT-Adapter for ERP

CustomerCreditTransferInitiation
Techn. Adapter Interfaces

CollectivePaymentOrderRequest

CustomerDirectDebitInitiation
PaymentStatusReport

XI Interfaces

Mapping SAP / ERP ISO20022

ISO20022 Interfaces

SAP AG 2007

Note: SWIFT-Adapter for ERP refers to Enhancements of the XI File Adapter.

Note: Headers are examples of naming convention

SAP AG

30

1. ERP SE Component containing the SAP Interfaces

Delivery of Interface Objects in the Integration Repository of SAP
XI
Message Interface: CollectivePaymentOrderRequest_Out
Message Type: CollectivePaymentOrderRequest
Data Type: CollectivePaymentOrderRequest

SAP AG 2007

Note: Names of objects are subject to change

SAP AG

31

1. Snapshot Integration Repository: Message Interface

SAP AG 2007

SAP AG

32

1. Snapshot Integration Repository: Message Type

SAP AG 2007

SAP AG

33

1. Snapshot Integration Repository: Data Type

SAP AG 2007

SAP AG

34

2. Mapping between XI Interfaces and ISO20022

Interfaces
Delivery of archive programs (format .XSL) for mapping of
Collective Payment Order Requests to ISO20022 Messages:
Customer Credit Transfer Initiation
Customer Direct Debit Initiation
Delivery of archive programs (format .XSL) for mapping of
ISO20022 Status Messages (Payment Status Report) to Collective
Payment Order Notifications
Interface Mappings:
CollectivePaymentOrder_2_CustomerCreditTransferInitiation
CollectivePaymentOrder_2_CustomerDirectDebitInitiation
PaymentStatusReport_2_CollectivePaymentOrderNotification

SAP AG 2007

Delivered Archives:

cpor_to_iso20022_mapping -> cpor_to_CustomerCreditTransferInitiationV02.xsl and

cpor_to_CustomerDirectDebitInitiationV01.xsl

iso20022_to_cporNotification_mapping ->
PaymentStatusReportV02_to_CollectivePaymentOrderNotification.xsl

SAP AG

35

2. Snapshot Integration Repository: Interface Mappings

SAP AG 2007

SAP AG

36

3. Component Containing the ISO20022 Interfaces

Delivery of Interface Objects in the Integration Repository of SAP
XI:
Message Interfaces, Data Types and External Definitions
Message Interfaces:
CustomerCreditTransferInitiationV02
CustomerDirectDebitInitiationV01
PaymentStatusReportV02
Data Types:
ExchangeFaultData
ExchangeLogData

SAP AG 2007

SAP AG

37

3. Snapshot Integration Repository (I)

SAP AG 2007

SAP AG

38

3. Snapshot Integration Repository (II)

SAP AG 2007

SAP AG

39

4. Enhancements of the XI File Adapter for SWIFT (I)

SAP delivers predefined XI-Content in the form of archive files,
which are imported into the XI Integration Repository, and are
available in the SAP Service Marketplace
The package is contained in a XI 7.0 Content for SWIFT.ZIP
file
The archive contains the following files:
XI7_0_SWIFT_602.tpz
sap_integration_package_for_swift_602.sda

= contains the

Adapter Modules
SAP also delivers an Installation Guide and a Configuration Guide
to deploy the SAP Integration Package for SWIFT
Deployment of the Adapter Modules is done via the SAP System
Delivery Manager
As an additional requirement, the Java Cryptography Extension
(JCE) for the Java 2 SDK v.1.4 needs to be installed
SAP AG 2007

SAP AG

40

4. Enhancements of the XI File Adapter for SWIFT (II)

SWIFTNet MT FIN Messaging Service:
Creation of SWIFT-specific files that are formatted as Protocol
Data Units (PDUs) of the Automated File Transfer (AFT) format and
can be processed by the SWIFT infrastructure (SWIFTAlliance
Access)
Management of the local authentication mechanism between
SAP NetWeaver XI and SWIFTAlliance Access. (Each record of the
file containing an MT message is signed using the HMAC-SHA256
algorithm)
Transfer of files between SAP NetWeaver XI and SWIFTAlliance
Access. (The files are made available to SWIFTAlliance Access or
SAP NetWeaver XI either by FTP or through a shared folder)
Interpretation and conversion of SWIFT-specific files that are
formatted as PDUs of the AFT format and can be processed
directly by SAP ERP Financials
SAP AG 2007

SAP AG

41

4. Enhancements of the XI File Adapter for SWIFT (III)

SWIFTNet FileAct Messaging Service:
If FileAct (in the store-and-forward mode) is used as a messaging
service, the following functionality is provided:
Bulk messages made available to the File Transfer Agent can be
processed by SWIFTAlliance Gateway and automatically transferred
over SWIFTNet
Management is provided for the local authentication mechanism
between SAP NetWeaver XI and SWIFTAlliance Gateway. (Every
bulk file that contains a domestic or SWIFT payment format will be
signed using the HMAC-SHA256 algorithm)
Transfer of files is enabled between SAP NetWeaver XI and
SWIFTAlliance Gateway. (The files are made available to
SWIFTAlliance Gateway or SAP NetWeaver XI either by FTP or
through a shared folder)
SAP AG 2007

SAP AG

42

4. Delivered Archives in Integration Directory

Delivery of archive program (format .XSL) for mapping of SWIFT
FIN Status Messages to Collective Payment Order Notifications:
SwiftFIN_to_CollectivePaymentOrderNotification.xsl
Delivery of archive program (format .XSL) for mapping of SWIFT
FTA Status Messages to Collective Payment Order Notifications:
SwiftFTA_to_CollectivePaymentOrderNotification.xsl
Delivery of archive program (format .class) for mapping of Error
Messages to HTML E-mail

SAP AG 2007

Archives:

SWIFT_to_CollectivePaymentOrderNotification -> SwiftFIN_to_CollectivePaymentOrderNotification.xsl

and SwiftFTA_to_CollectivePaymentOrderNotification.xsl

ErrorToHTML -> ErrorNotificationEmailMapping$1.class

SAP AG

43

4. Interface Objects in Integration Directory

Message Interfaces, Message Types,
Data Types and External Definitions

Message Types
Dummy: interface for plain file
transfer
ErrorLog: interface for transfer of
error.log file
SWIFT_FIN: interface for transfer of
FIN status messages
SWIFT_FTA: interface for transfer
of FTA status messages
SwiftMessage: Generic
SwiftMessage interface
SwiftMessage_FIN:
SwiftMessage_FIN interface
SwiftMessage_FTA:
SwiftMessage_FTA interface

SAP AG 2007

SAP AG

44

Software Components for XI Content

Software Component

Software Component
Version

Technical
Software
Component

Description

SWIFT

SWIFT 1.0

SWIFT

SAP Fileadapter
Enhancement for Swift 1.0
Java Modules

XI CONTENT SWIFT

XI CONTENT SWIFT
1.0

SAP Fileadapter
XI_CNT_SWIFT Enhancement for Swift 1.0
technical interfaces

ISO20022

ISO20022 1.0

ISO20022

XI CONTENT ISO20022

XI CONTENT ISO20022 XI_CNT_ISO20

1.0
022

ISO20022

ISO20022 ERP

ISO20022 ERP 1.0

ISO20022 ERP 1.0 (Dummy

entry necessary for XI
Content creation)

XI CONTENT ISO20022
ERP

XI CONTENT ISO20022 XI_CNT_ISO20

ERP 1.0
022_ERP

ISO20022_ERP

ISO20022 1.0 (Dummy entry

necessary for XI Content
creation)

XI CONTENT ISO20022 ERP

SAP AG 2007

Note: This is an example containing all Software Components. Naming convention in the XI System for
delivered objects may change.

SAP AG

45

Options for SWIFT/ISO20022 Content

Bank
Relationship
Management
New PMW
Formats*

Release

R/3 4.6C

R/3 Enterprise

SAP ERP 2004

File Adapter File Adapter

(FIN/MT and
(MX and
Domestic)
Proxies)

File Adapter
(MX and
Proxies)

U
U

U
U

SAP ERP 2005

* without XI

SAP AG 2007

SAP AG

46

Message Flow Possibilities Between ERP and SWIFT (I)

ERP software sends SWIFT FIN Messages to SWIFT software
using SWIFTNet FIN
ERP software receives SWIFT FIN Messages from SWIFT software
using SWFTNet FIN
Reception of FIN Messages
Reception of FIN Status Messages
ERP software sends SWIFT FileAct (MX) Messages to SWIFT
software using SWIFTNet FileAct
ERP software receives SWIFT FileAct (MX) Messages from SWIFT
software using SWIFTNet FileAct
Reception of E-Mail notifications from SWIFTNet FIN in error
cases

SAP AG 2007

Above are some examples of what type of messages can be routed via XI through SWIFTNet.

Other combinations should also be possible.

SAP AG

47

Message Flow Possibilities Between ERP and SWIFT (II)

Via Proxies:
Sending and Receiving Collective Payment Order Requests
(CPOR) and mapping in XI into Customer Credit Transfer Initiation
Messages in XML format (SEPA Credit Transfer), from ERP software
to SWIFT Alliance Gateway and vice versa
Sending and Receiving Collective Payment Order Requests
(CPOR) and mapping in XI into Customer Direct Debit Initiation
Messages in XML format (SEPA Direct Debit), from ERP software to
SWIFT Alliance Gateway and vice versa
Sending and Receiving Bank Statements in XML format

SAP AG 2007

Note: Usage of proxies need an Add-On to be installed in the backend systems.

Other combinations of message types should be possible.

SAP AG

48

Configuration in the Integration Directory of SAP XI

Message flows are configured in SAP Exchange Infrastructure by
defining:
Business Services
Communication Channels
Sender and Receiver Agreements
Receiver Determinations
Interface Determinations
ERP communicates with the XI system using the File Adapter as
its Communication Channel
The Communication Channel determines the exact location of the
files being written and their naming schemes
The enhanced SAP File Adapter for SWIFT is called from the
configured Communication Channels

SAP AG 2007

SAP AG

49

SAP Integration Package for SWIFT

Features
Availability
Architecture Overview
SAP Consulting Service Offerings

SAP AG

50

SAP Consulting: Service Offering

SAP Integration Package for SWIFT
Will help to achieve lower TCO by becoming independent from
proprietary payment standards and bank-specific e-banking products
and setting up a single communication channel to SWIFTNet, which will
enable a company to communicate with all the banking partners
through this one channel
Assessment
Initial workshop to identify
the customer scenario
Analysis of existing banking
landscape
Transparency on value of the
SAP Integration Package for
SWIFT
Identification how many
current banking applications
will become obsolete
Evaluation which banks to
connect via which format

Provisioning
Support on SWIFT application,
installation and configuration
of the system landscape
SWIFTNet Infrastructure

SAP Exchange
Infrastructure
Ensure landscape is available
and support further integration
efforts

Implementation
Configuration of
SWIFTAlliance Access and
Gateway according to the
scenario
End-to-end SWIFTNet
Integration
Import of XI content and
configuration of the SAP
Exchange Infrastructure
Adapt customizing of ERP
to use with the SAP Bank
Relationship Management

SAP AG 2007

SAP AG

51

SAP Consulting: Quick Assessment SWIFT Integration

Assessment of SWIFT Integration in 5 days / Contact:
Steffen Karsch (steffen.karsch@sap.com) or Jrgen Weiss (juergen.weiss@sap.com)
Situation / Objective

Customer is using SAP R/3 >= Release 4.6C or higher

Usage of Payment Medium Workbench (SAP
Financials) and/or SAP Treasury on the same client
Ideally customer has SAP Exchange Infrastructure
no prerequisite
Customer is eligible member of SWIFT and already
part of MA-CUG or SCORE no prerequisite

Customer Benefit

Procedure

Fewer bank connections and enhanced straightthrough processing rates through full SWIFT
Integration via
SWIFT Alliance Access/Gateway
Reduced maintenance costs by using global payment
standards
Increased security and compliance
Readiness for SEPA and UNIFI/ISO20022 standard

References

Additional Info

aSAP1: Definition of scope based on existing bank

connections, used formats and payment volume
according to questionnaire provided upfront
aSAP2: Analysis of existing system landscape and
payment processes during 1 day workshop
aSAP3: Recommendation on future process flows
(level 1), rough effort estimation and suggested
project plan including required skill set from customer
aSAP4: Preparation of deliverables in written form and
advice for next steps

SAP AG 2007

SAP AG

52

SAP Consulting: Quick Assessment SWIFT Integration and

SAP Bank Relationship Management
Assessment of SWIFT Integration and Bank Relationship Management in 10 days / Contact:
Steffen Karsch (steffen.karsch@sap.com) or Jrgen Weiss (juergen.weiss@sap.com)
Situation / Objective

Customer is using SAP ERP 2005 and upgrading

to Enhancement Package 2
Usage of Payment Medium Workbench (SAP
Financials) and/or SAP Treasury on the same client
Ideally customer has SAP NetWeaver 2004s
Exchange Infrastructure no prerequisite
Customer is eligible member of SWIFT and already
part of MA-CUG or SCORE no prerequisite

Customer Benefit

Procedure

Fewer bank connections and enhanced straightthrough processing rates through full SWIFT
Integration via
SWIFT Alliance Access/Gateway
More cash flow transparency and visibility of working
capital due to better payment handling
Reduced maintenance costs by using global payment
standards
Increased security and compliance
Readiness for SEPA and UNIFI/ISO20022 standards

References

Additional Info

aSAP1: Definition of scope based on existing bank

connections, internal payment release procedures,
used bank connections and formats and payment
volume according to questionnaire provided upfront
aSAP2: Analysis of existing system landscape and
payment processes during 2 day workshop
aSAP3: Recommendation on future process flows
(level 1), rough effort estimation and suggested
project plan including required skill set from customer
aSAP4: Preparation of deliverables in written form and
advice for next steps

SAP AG 2007

SAP AG

53

Summary

Now you are able to

z Explain the Concept of SAP Integration Package for
SWIFT
z Describe the Main Features of SAP Integration
Package for SWIFT
z Understand the Architecture of SAP Integration
Package for SWIFT
z Get an overview of the Main Components of SAP
Integration Package for SWIFT

SAP AG 2007

SAP AG

54

Copyright 2007 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, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, System i, System i5, System p,
System p5, System x, System z, System z9, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, POWER5+, OpenPower and PowerPC
are trademarks or registered trademarks of IBM Corporation.
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.
MaxDB is a trademark of MySQL AB, Sweden.
SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, 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 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. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose without the express prior
written permission of SAP AG.
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. Please note that this
document is subject to change and may be changed by SAP at any time without notice.
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 AG 2007

SAP AG

55