SAP Business Suite Network Solution Scopesapidp/012002523100014253842014E/… · SAP Rapid Deployment Solution Page 4/16 Public 1 Introduction This document describes the scope of

SAP Rapid Deployment Solution

Rapid deployment of SAP Business Suite Integration for SAP Financial Services Network

V3.607

March 2015

Solution Scope Rapid deployment of SAP Business Suite Integration for SAP Financial Services Network V3.607


Page 2/16 Public

Copyright © 2015 SAP SE or an SAP affiliate company. 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 SE or an SAP affiliate company.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. Please see http://global.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.

Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors.

National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP SE or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE or SAP affiliate company 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.

In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.

Revision Change Date Description

0

http://global.sap.com/corporate-en/legal/copyright/index.epx#trademark


Content 1 Introduction ................................................................................................................................................... 4

2 Scope Overview ........................................................................................................................................... 5

2.1 Solution Scope ................................................................................................................................... 5

2.2 Integration Scope ............................................................................................................................... 6

2.3 Organization Scope ............................................................................................................................ 7

2.4 Master Data Scope ............................................................................................................................ 7

2.5 Localization Scope ............................................................................................................................. 7

2.6 Software and System Prerequisites ................................................................................................... 7

3 Implementation Scope ................................................................................................................................ 11

3.1 Scope Item ....................................................................................................................................... 11


Page 4/16 Public

1 Introduction

This document describes the scope of SAP Business Suite Integration for SAP Financial Services Network rapid-deployment solution. It includes details on the scope, including:

Solution scope described in features and functions

Solution scope organized into scope items and building blocks

Solution scope organized with reference to target segments / deployment options or other criteria

Integration scope

This document is the basis for Scope Documents that can be turned into a customer project document updated with customer specific decisions and used to sign off the agreed scope.

This document provides also the basis for a Statement of Work.


Page 5/16 Public

2 Scope Overview SAP will implement the rapid deployment of SAP Business Suite Integration for SAP Financial Services Network V3.607 (“Project”) which is based upon standard SAP Best Practices.

The Project will enable secure and reliable connection of a back-end SAP solution to the Financial Services Network (“FSN”) utilizing preconfigured integration for the payment process and best practices inherent to the integration via Connector for SAP Financial Services Network 2.0.

To enable the connectivity between SAP Business Suite and the cloud based SAP Financial Services

Network, this package will use Connector for SAP Financial Services Network 2.0 technology delivered by

SAP. Using the Connector for SAP Financial Services Network 2.0, the RDS will provide the following three

different process integration technology options.

1. Corporate Customer and SAP Initiating Message Exchange (Push/Push communication pattern)

2. Corporate Customer Initiating Message Exchange (Push/Pull communication pattern)

3. Corporate Customer Initiating Message Exchange with existing SAP PI (Push/Pull communication

pattern with SAP Process Integration) Optionally, supported business services may additionally include payment status reporting from a financial institution (“Bank”) to Bank Communication Management (“BCM”) on the Licensee’s side. Alternative to Bank Communication Management customer can choose Business Cockpit on the Licensee’s side for Payment Monitoring and Approvals.

Optional:

1. Integration of payment status with BCM and payment approvals using BCM

2. Integration of Japanese based ZENGIN payment format

3. Integration of payment monitoring and approvals for Business Cockpit as part of SAP FSN

2.1 Solution Scope

The table below summarizes the scope to be delivered during the project. The scope is organized into scope options. Each scope option has one or more scope items that represent a business process or element of scope. Each scope item requires the implementation of a number of building blocks.

Scope Options Mandatory or Optional

Scope Item Scope Item / Business Process Name

Building Block IDs

M Mandatory Mandatory ED2/ED5/ED6

Integration of payment initiation and bank statements for:

a) Corporate customer initiating message exchange (ED2) (or)

b) Corporate customer and SAP initiating message exchange (ED5) (or)

c) Corporate customer initiating message exchange with existing SAP PI (ED6)

ED0


Page 6/16 Public

Scope Options Mandatory or Optional

Scope Item Scope Item / Business Process Name

Building Block IDs

01 Integration of BCM

Optional ED7 Integration of payment status with BCM and payment approvals using BCM

ED0, ED1

02 Integrate Business Cockpit

Optional ED9 Integration of payment monitoring and approvals for Business Cockpit as part of SAP FSN

ED0

03 Implement ZENGIN format

Optional EU1 Integration of Japanese based ZENGIN payment format

ED0, EU0

The above mentioned building block IDs are as follows:

1. ED0 – Connectivity of ERP to FSN either levering Scope Item ED2, ED5 or ED6

2. ED1 – BCM Integration (Scope Item ED7)

3. EU0 - Integration of Zengin format Configuration Guide (Scope Item EU1)

The dependencies of Scope Items and Buildings Blocks are given in the Prerequisites Matrix below.

Scenario Scenario Description 1 2 3 4 5 6

ED2 Corporate Customer and SAP Initiating Message Exchange ED0

ED5

Corporate Customer Initiating Message Exchange ED0

ED6

Corporate Customer Initiating Message Exchange with existing SAP PI ED0

ED7

Integration of Payment Status with BCM and Payment Approvals using BCM ED0 ED1

ED9

Integration of Payment Monitoring and Approvals for Business Cockpit ED0

EU1 Integration of Zengin format ED0 EU0

2.2 Integration Scope

The following integration points are included within this project:

Integration Point Product 1 Direction Product 2 Related

Scope Item

or Grouping

Building Block


Page 7/16 Public

Integration Point Product 1 Direction Product 2 Related

Scope Item

or Grouping

Building Block

Corporate customer and SAP initiating message exchange

ERP Bi-directional FSN ED2 ED0 – Push/Push communication pattern

Corporate customer initiating message exchange

ERP >> FSN ED5 ED0 – Push/Pull communication pattern

Corporate customer initiating message exchange with existing SAP PI

ERP (PI) >> FSN ED6 ED0 – Push/Pull communication pattern with Process Integration

Integration of payment monitoring and approvals for Business Cockpit as part of SAP FSN

ERP >> FSN ED9 ED0 – Push/Pull communication pattern

2.3 Organization Scope This Project is not limited by organization scope but rather by technical scope that is addressed in subsequent sections.

2.4 Master Data Scope This Project is not limited by master data scope but rather by technical scope that is addressed in subsequent sections.

2.5 Localization Scope The solution will display all business data in English only.

All service content will be delivered in English.

2.6 Software and System Prerequisites Refer to the Software and Delivery requirements document for a complete list of prerequisites.

This solution is delivered based on a two-tier system landscape: a development system and a production system.

The following software products and versions are required:

Product Product Version Components

SAP Solution Manager Logical Component

Comments Relevance


Page 8/16 Public

SAP Solution Manager

SAP Solution Manager 7.0 Enhancement Package 1

SP18 or higher

In case the SP is below 24, see SAP Note 1579267.

Or

SAP Solution Manager 7.1

SP01 or higher

Or

SAP Solution Manager 7.1 on HANA (ST 712)

SP00 or higher

Not applicable

Required implementation tool

SAP ERP

SAP ERP 600 with SAPKH60019






SAP ERP 616

SAP ERP 617

SAP_APPL

ERP60_EHP7_CENTRAL_APPLICATION

. All Integration Scope Items

SAP ERP

SAP ERP 6.0 EHP2

SAP ERP 6.0 EHP4 or above

Bank Communication Management

Yes Depending on the enterprise services used


Page 9/16 Public

SAP NetWeaver

SAP NetWeaver AS ABAP 7.0 SP14







Web Service Run Time

None Basis requirement for Web Service Run Time to support message transfer.

SAP NW V7.31 SPS07 is recommended.

All Scope Items

Connector for SAP Financial Services Network 2.0

BSNAGT 200 or high

Check NOTE 1781614 for more details for this solution.

If Electronic Payment Integration (China) business component has been activated in your system, then it will stop the business processing for Connector for SAP Financial Services Network 2.0 and must be inactivated if you choose this RDS solution.

SAP Netweav

SAP NetWeaver PI

7.11 or 7.3 SPS 10


Page 10/16 Public

er Process Integration

or 7.31 SPS 09 or 7.40 SPS 04 or higher

In this RDS package, the documentation for PI configuration is based on PI 7.4.


Page 11/16 Public

3 Implementation Scope This chapter describes the detailed scope of SAP Business Suite Integration for SAP Financial Services Network V3.607 organized in scope items or groups of scope items.

3.1 Scope Item The Project will enable secure and reliable connection of a back-end SAP solution to the Financial Services Network (“FSN”) utilizing preconfigured integration for the payment process and best practices inherent to the integration via Connector for SAP Financial Services Network 2.0.

Optionally, supported business services may additionally include payment status reporting from a financial institution (“Bank”) to Bank Communication Management (“BCM”) on the Licensee’s side. Alternative to Bank Communication Management customer can choose Business Cockpit for Payment Monitoring and Approvals.

Refer to the Scope Item Test Script document that provides the detailed process steps and required business (user) roles.

3.1.1 Business Process Overview This Project will configure the following SAP Best Practice Building Blocks:

3.1.1.1 Configuration Guide for Connecting SAP ERP with FSN using Connector for SAP Financial Services Network 2.0 (Building Block ED0) and/or PI

3.1.1.1.1 Corporate Customer and SAP Initiating Message Exchange (Default) – Scope Item ED2

In this scenario (which was used in the V1 RDS), the SAP ERP backend system sends the outbound

messages via the connector and receives an inbound message from SAP Financial Services Network to the

connector. This implementation requires the receiver's SAP ERP system to be opened to the Internet. Please

note that the integration will be done within FSN using SAP HANA Cloud Integration.


Page 12/16 Public

3.1.1.1.2 Corporate Customer Initiating Message Exchange – Scope Item ED5

Rather than the above scenario, the ERP backend system retrieves the inbound messages from the SAP

Financial Services Network. The outbound message exchange remains the same as the above scenario.

Customer SAP ERP system does not require to be accessible from FSN. Please note that the integration

will be done within FSN using SAP HANA Cloud Integration.

3.1.1.1.3 Corporate Customer Initiating Message Exchange with existing SAP PI – Scope Item ED6

Using the on-premise process integration middleware corporate customers can connect their SAP

Business Suite system to SAP FSN through SAP PI (release SAP PI 7.11 or higher) system. This option

enables corporates to connect with SAP FSN via the Web Services Reliable Messaging (WS-RM)

communication protocol. Please note that SAP PI will only be used as a gateway between SAP Business

Suite and SAP Financial Services Network. The main integration, mapping and transformation will be

realized using SAP HANA Cloud Integration.


Page 13/16 Public

3.1.1.2 Configuration Guide for Bank Communication Management - Building Block ED 1 – (Scope Item ED7) – optional

3.1.1.3 Integration of Zengin format Configuration Guide - Block EU0 - (Scope Item EU1) – optional

3.1.1.4 Integration of Payment Monitoring and Approvals for Business Cockpit - (Scope Item ED9) – optional

Refer to the Process Diagram document that summarizes the business process.

3.1.2 Solution Scope The following are the integration technologies used to integrate Connector for SAP Financial Services Network 2.0 with the SAP HCI Services:

Transmission protocol WS-RM over https

Medium – either tRFC for files or Web Services

Either Payment Medium Workbench (PMW) or ALE payment instruments

SAP ERP Outbound message formats o Based on ALE/IDOC

IDoc PAYEXT/PEXR2001 IDoc PAYEXT/PEXR2002 IDoc PAYEXT/PEXR2003

o Based on PMW ISO20022 CGI_XML_CT for PAIN.001.001.03CGI ISO20022 CGI_XML_CT for PAIN.001.001.04

o File pick-up Currently tested formats for PMW/ALE Zengin format

o Workstation Upload Utility Currently tested formats for PMW/ALE Zengin format

SAP ERP Inbound transmission formats for statements: o SWIFT MT940 with field 86 structured o SWIFT MT942 o CAMT.053.001.02CGI

SAP ERP Inbound message format for payment status for Option (i.e. for implementation that includes BCM):

o ISO20022 PAIN.002.001.03CGI o ISO20022 PAIN.002.001.04


Page 14/16 Public

3.1.3 Transactions and User Interface The user interface provides the following transactions:

The user interface provides the following transactions:

SPAM

SAINT

STRUST

SOAMANAGER

SPRO

FBZP

SSFA

FF_5

SARA

OBPM1

BD51

WE57

WE42

SM59

WE21

FILE

SFW5 (optional)

OBPM5 (optional)

BNK_BNK_INI_REL01 (optional)

SWETYPV (optional)

SM30 (optional)

PFTC_CHG (optional)

BNK_SIGN_MAINTAIN (optional)

BNK_SIGN_CONFIRM (optional)

ALRTCATDEF (optional)


Page 15/16 Public

OBXH(optional)

3.1.4 Implementation Scope and Refinement Options The solution provides the following scope item details:

Default Implementation Scope Customer Refinement Options

General Configuration

Installing Connector for SAP Financial Services Network 2.0 into Your SAP ERP System as an Add-on

Set up Security and Web Service Communication

Customizing the Connector for SAP Financial Services Network 2.0

Preparing Outbound Payment

ED2 Configuration for PUSH/PUSH Connectivity

Enabling Certificate-based Communication with FSN

Export Web Services Description Language File

Adding Certificates Provided by SAP

Import Web Services Description Language File

Configuring Web Service Consumer (Logical Port)

Adding a Distinguished Name to a Technical User

ED5 Configuration for PUSH/PULL Connectivity

Enabling Certificate-based Communication with FSN

Export Web Services Description Language File

Adding Certificates Provided by SAP

Import Web Services Description Language File

Configuring Web Service Consumer (Logical Port)

ED6 Configuration for PUSH/PULL using SAP Process Integration as Gateway

Exchange certificates between SAP ERP system and SAP PI system

Exchange certificates between SAP PI system and SAP FSN Tenant

Scope Item ED7 was selected - the following additional tasks related to implementation of BCM are included in scope:

Maintain basic BCM settings

Rule maintenance

Define release strategy

Refine workflow rules for batch approval

Mark rules for automatic payments

Assign roles to release steps

Assign workflow template to release procedure


Page 16/16 Public

BAdI: action on original payments on reject/resubmit

Define basic settings for digital signature

Specify signature method for approval

Define mappings for payment status management

Define mappings for bank statement monitor

Scope Item EU1 was selected - the following additional tasks related to implementation of BCM are included in scope:

Configuring Payment Method

Setup House Banks

Checking Clearing Procedures

Configuring the File Interface for File Pick-up Report