FSN OVERVIEW

About SAP Financial Services Network

SAP Financial Services Network (SAP FSN) is an innovative on-demand solution that connects
financial institutions and other financial service providers with their corporate customers on a
secure network owned and managed by SAP. The network offers multiple services in one single
channel while supporting the deployment of new services. As key benefits, the solution simplifies
connectivity, automates financial transactions, reduces payment rejection rates, eases
reconciliation, and provides enhanced visibility to corporate treasury.

SAP FSN is an integration platform that enables multiple participants (financial service providers
and their corporate customers) to exchange financial data in a reliable and secure way.
For each participant connected to SAP FSN, separate resources (memory, CPU, and file system) are
allocated in the SAP HANA Cloud. In the runtime of an SAP FSN scenario, these resources are
referred to as tenants.
E.G Let us assume that two participants (participant 1 and participant 2) exchange financial data
with each other through SAP FSN. Tenant 1 is allocated to (assigned to) participant 1, and tenant 2
is assigned to participant 2. The exchange of data through SAP FSN then works in the following way:

Participant 1 sends the financial data to tenant 1.

Tenant 1 forwards the data to tenant 2.

Tenant 2 sends the data to participant 2.

SHIP22 CORE#1
| CONFIDENTIALITY
Monitoring 21 July 2015 LEVEL
 Summary of Benefits Provided by SAP FSN
SAP FSN provides the following benefits:

• Pay-as-you-go subscription model

• Faster onboarding of financial institutions and corporations

• Reduced operational risk

• Better visibility and control

• No additional cost for maintaining hardware and software

• Lower total cost of ownership (TCO)

• Standardized integration between financial institutions and their customers

SHIP23 CORE#1
| CONFIDENTIALITY
Monitoring 21 July 2015 LEVEL
 Security Information
Security in SAP FSN includes the following aspects:

• Security aspects of the involved components of the technical system landscape

Scenarios based on SAP FSN include SAP’s cloud-based integration platform as well as back-end systems on the connected
participant's side.

• Tenant isolation
For each participant connected to SAP FSN, separate resources (memory, CPU, and file system) of the cloud-based
integration platform are allocated – although all participants might share the same hardware. This concept is also
referred to as tenant isolation.

• Communication security
During the operation of an SAP FSN scenario, the connected participants exchange data with each other based on the
configured transport protocol. The content of the exchanged messages can also be protected by means of digital
encryption and signature.

• Data storage security

At several phases of the lifecycle of an SAP FSN scenario, data is stored and, therefore, exposed to the risk of
unauthorized access. There are several measures to protect stored data in SAP FSN.

• Security aspects of the onboarding process

During the connection setup between a participant and SAP FSN, data has to be exchanged between experts on the SAP
and customers side. Several measures are applied to secure this data exchange.

• High availability
Several measures are taken to ensure robust operation and a high level of operational performance of the SAP FSN
runtime.
SHIP24 CORE#1
| CONFIDENTIALITY
Monitoring 21 July 2015 LEVEL
 Bank Connectivity with S/4HANA Cloud –Three Routes

SHIP25 CORE#1
| CONFIDENTIALITY
Monitoring 21 July 2015 LEVEL
 SAP Bank Integration with File Interface (1EG) & SAP FSN (16R)
SAP Bank Integration with SAP Bank Integration with SAP FSN 16R
Bank Interface 1EG Process Flows Process Flows

SHIP26 CORE#1
| CONFIDENTIALITY
Monitoring 21 July 2015 LEVEL
 Message Choreography

SHIP27 CORE#1
| CONFIDENTIALITY
Monitoring 21 July 2015 LEVEL
 Banks that are available on FSN Network

• Deutsche Bank

• BOFA

• Standard Chartered

• Credit Suisse

• Others in Process

SHIP28 CORE#1
| CONFIDENTIALITY
Monitoring 21 July 2015 LEVEL
 Connectivity (Adapters)
Adapter Type Enables tenant to ...
Ariba Connect a tenant to the Ariba network (this allows SAP and non-
SAP cloud applications to send and receive business-specific
documents in cXML format to and from the Ariba network).

Facebook Access and extract information from Facebook based on certain

criteria such as keywords or user data.

HTTP Connect to a receiver system using the HTTP protocol.

HTTPS Connect to a sender system using the HTTPS protocol.

Idoc Exchange IDoc messages with another system.

JMS Process asynchronous messages by using message queues.

Mail Exchange e-mails with an e-mail server.

Odata Connect to systems exposing OData services (OData service
providers).
OData stands for the Open Data Protocol.
SFTP Connect to a remote system using the SSH File Transfer protocol
(also referred to as Secure File Transfer protocol).

SOAP /SOAP 1.x Exchange messages with another system that supports SOAP 1.1 or
SOAP 1.2.

SHIP29 CORE#1
| CONFIDENTIALITY
Monitoring 21 July 2015 LEVEL
 Adapter Type Enables tenant to ...
SOAP / SOAP RM Exchange messages with another system based on the SOAP
communication protocol and SAP RM as the message protocol.

SuccessFactors Connect to a SuccessFactors system using the SOAP, OData, and

REST message protocol.

Twitter Access Twitter and either read or post tweets.

XI Connect a tenant to a remote system that can process the XI

message protocol.
ODC Connect to SAP Gateway OData Channel.
LDAP Connect to LDAP directory service.

10 CORE#1
SHIP2 | CONFIDENTIALITY
Monitoring 21 July 2015 LEVEL