Á } } v v } ^ W &^E - archive.sap.com

Iƻǿ ǘƻ /ƻƴƴŜŎǘ ǘƻ {!t C{b This comprehensive guide for corporate consultants helps integrating the SAP ERP system to SAP FSN. It provides an overview, analysis, implementation guidance and detailed step by step instructions lists. Links to other specific documentation are included as well.

www.sap.com

TABLE OF CONTENTS

ABOUT THIS DOCUMENT ............................................................................................................................... 4

ACRONYMS ...................................................................................................................................................... 4

QUICK INTRODUCTION TO SAP FSN ............................................................................................................ 4 Deployment ...................................................................................................................................................... 4 Supported Business Services ........................................................................................................................ 5 Payments forwarding ......................................................................................................................................... 5 Electronic Statement Integration ....................................................................................................................... 5 How SAP ERP automatic payments work in a nutshell ............................................................................... 6 More information about SAP ERP Financials Integration technologies .................................................... 7 Supported SAP FSN Integration Mediums and Connectivity ...................................................................... 7 Supported Message Formats ......................................................................................................................... 7

INTEGRATION .................................................................................................................................................. 8 Implementation Project Overview .................................................................................................................. 8 Steps in Detail .................................................................................................................................................. 8 1. Planning the Integration Strategy ..................................................................................................... 9 1.1. Understanding the Customer Installation ......................................................................................... 9 1.2. Financial Institution Integration Landscape ...................................................................................... 9 1.3. Corporate Security ........................................................................................................................... 9 1.4. Implemented Scenarios.................................................................................................................... 9 1.5. Corporate Scope Identification ....................................................................................................... 10 2. SAP FSN Onboarding (Service activation and cloud environment setup) ..................................... 10 3. SAP FSN integration with SAP ERP back-end .............................................................................. 11 3.1. SAP FSN Connector Add-on Installation and Configuration .......................................................... 11 3.1.1. Introduction ..................................................................................................................................... 11 3.1.2. Download ....................................................................................................................................... 11 3.1.3. Installation ...................................................................................................................................... 12 3.1.4. General Configuration Guide ......................................................................................................... 12 3.1.5. Maintain Number Ranges for Message ID (Optional) .................................................................... 13 3.1.6. Maintain SSF Profile Data .............................................................................................................. 13 3.1.7. Maintain Residence Time for Message Archiving .......................................................................... 13 3.1.8. Maintain Sender ID ......................................................................................................................... 14 3.1.9. Maintain Custom Sender IDs ......................................................................................................... 15 3.1.10. Create Bank Statement import format Variant ............................................................................... 16 3.1.11. Maintain Selection Variants for Bank Statements .......................................................................... 17 3.1.12. SAP FSN WSDL file ....................................................................................................................... 17 3.1.13. Web Services Configuration ........................................................................................................... 17 Outbound Communication ............................................................................................................................... 18

Inbound Communication .................................................................................................................................. 19

3.1.14. Maintain alternative Logical Ports for Outbound Messages ........................................................... 20 Additional options for redirection: .................................................................................................................... 20

3.1.15. Download the client and server certificate ..................................................................................... 21 3.1.16. Configure Certificates ..................................................................................................................... 21 3.1.17. Adding a Distinguished name to a technical user .......................................................................... 21 3.1.18. Maintain SSFA parameters ............................................................................................................ 22

HOW TO CONNECT TO SAP FSN

3

3.1.19. Encryption Configure SSF (message level Security) ............................................................... 23 3.1.20. Archiving Process Configuration .................................................................................................... 23 3.1.21. Input Configuration ......................................................................................................................... 23 Customer configuration overview – payment medium scope verification ....................................................... 24

3.1.19.1 Payment Medium Workbench ........................................................................................................ 24 3.1.19.2 ALE/IDoc ........................................................................................................................................ 26 Outbound processing configuration ................................................................................................................. 30

Inbound configuration ...................................................................................................................................... 35

3.1.19.3 File .................................................................................................................................................. 38 3.1.20 Integrating with SAP NetWeaver PI/PO ......................................................................................... 40 3.1.21 Integration using other middleware components ........................................................................... 41 3.2 SAP Web Dispatcher ...................................................................................................................... 41 4. SAP ERP Configuration ................................................................................................................. 42 4.1 Understanding the configuration options........................................................................................ 42 4.2 Technical Redirection ..................................................................................................................... 42 4.3 House Banks Specific Redirection ................................................................................................. 42 4.3.19 ALE ................................................................................................................................................. 42 4.3.20 PMW ............................................................................................................................................... 43 4.4 Payment Method Specific Redirection ........................................................................................... 43 4.4.19 ALE ................................................................................................................................................. 43 4.4.20 PMW ............................................................................................................................................... 43 4.5 Vendor Specific Redirection ........................................................................................................... 43 4.5.19 ALE ................................................................................................................................................. 43 4.5.20 PMW ............................................................................................................................................... 43 4.6 Implementing new payment methods or house banks for SAP FSN ............................................. 43 4.7 Gathering relevant information for payments transformations ....................................................... 44 4.8 Gathering relevant information for the electronic bank statements generation ............................. 44 5. SAP FSN Integration Implementation ............................................................................................ 47 6. Setting up Authorizations ............................................................................................................... 47 7. (Optional) SAP Financials FSCM-BCM Integration (as of SAP ERP 6.0 Ehp2) ............................ 47

APPENDIXES .................................................................................................................................................. 48 Appendix 1: Installation Information Gathering ......................................................................................... 48 Motivation ........................................................................................................................................................ 48 Financial Institution Integration Landscape ..................................................................................................... 48 Corporate Security ........................................................................................................................................... 49 Scenarios ......................................................................................................................................................... 49 Integration Technologies ................................................................................................................................. 49 Payment Methods ............................................................................................................................................ 50 Accounts Payable & Accounts Receivable ...................................................................................................... 51 Bank Accounts Configuration .......................................................................................................................... 51 Vendor Payments Configurations .................................................................................................................... 51 Appendix 2: Documentation ......................................................................................................................... 53


4

ABOUT THIS DOCUMENT

This document is aimed for consultants connecting corporate companies running SAP ERP to SAP FSN. There are several additional required tasks referenced here and explained in the documentation Appendix 2 This document covers the implementation of the SAP FSN Connector Version 2.0. There is not implementation methodology enforced or documented in this system. It is not covering transports, documentation, etc. This document assumes no inconsistencies between the customer development, QA and productive SAP ERP systems. It is anyways strongly recommended to validate and manage possible inconsistencies in the landscape accordingly. ACRONYMS

Acronym Meaning

(SAP ERP FI-FSCM) BCM

Banks Communication Manager

ALE Application Link & Enabling: Integration Layer in SAP NetWeaver

DMEE Data Medium Exchange Engine

HCI SAP Hana Cloud Integration Services

PMW Payments Medium Workbench

WS-RM Web Services Reliable Messaging QUICK INTRODUCTION TO SAP FSN

SAP FSN is a SAP Hana Cloud based solution that allows SAP ERP customers to integrate with banks as well as other financial service providers. SAP HCI Services are exploited as integration broker. It provides connectivity, routing and transformation services. Deployment SAP FSN is structured in 2 components:

1- SAP FSN Connector: SAP ERP Add-on.

2- SAP FSN itself in the cloud.

SAP Hana Cloud hosts tenants for every party connected to SAP FSN. SAP HCI Services are also used for inter tenant communications.


5

Supported Business Services SAP FSN currently supports:

Payments Initiation forwarding from SAP ERP to a Bank

Payment Status reporting from a Bank to SAP ERP FI-FSCM BCM

Electronic Bank Statement reporting from a Bank to SAP ERP FI

Payments forwarding 1. Creation 2. Forward to FSN 3. FSN Processing

1. Document Validations 2. Format & Values

Conversion 4. Forward to Bank 5. Execution 6. Status Update* 7. FSN Processing 8. Forward to Customer 9. SAP ERP Processing

*NOTE: Status update is only available for customers using SAP ERP FI-FSCM BCM (as of SAP ERP 6.0 Ehp2)

Electronic Statement Integration 1. Banks forward statements

to FSN 2. FSN Processing

1. Document Validations 2. Format & Values

Conversion 3. Forward to SAP ERP


6

How SAP ERP automatic payments work in a nutshell Process Steps:

1. Payment Method Selection: Payments Generation is based on methods

like checks, ACH, etc..

2. Medium Determination

Determines the container and format, e.g. flat file or xml file.

Connects to Integration Layer

3. Integration Layer: Performs the actual medium transfer among other

services

Payment methods at country level allow to select the output generation technology, namely:

• Payment Medium Workbench: This is a SAP FI tool that works in

conjunction with the Data Medium Exchange Engine to produce XML files.

It supports transformations. Many built in templates delivered.

• ALE : It is an SAP NetWeaver level tool widely used to integrate ABAP

based applications

• Classic Payment Medium Programs: about 70 programs delivered.


7

More information about SAP ERP Financials Integration technologies As introduce above, there are mainly 3 technologies used in financial integration in the SAP ERP:

PMW/DMEE: It is an SAP ERP application level tool that provides good transformation and

enrichment capabilities. It is the natural choice from application perspective but not so

comprehensive from the technical and administration perspective.

ALE: It is a generic SAP NetWeaver level integration technology, does not provide good data

manipulation tools but stronger in administration.

Files: SAP ERP Financials provides built in programs to produce and read files

All these technologies have been coexisting for a long time. The best choice largely depends on the customer integration strategy. SAP FSN connector supports to certain degree all of them, corporate are not required to migrate, decommission or change the way they are currently using these tools. Supported SAP FSN Integration Mediums and Connectivity These are the integration technologies used to integrate SAP FSN Connector with the SAP HCI Services:

Medium Transmission Protocol Details

File WS-RM over https File integration allows existing integrations to be easily integrated to SAP FSN. There are no restrictions in terms of file formats.

Web Service An Introduction to WS-RM can be seen in SCN: Preview of Web Services Reliable Messaging

Supported Message Formats

Direction Message Format Details

SAP ERP Outbound

PAYEXT/PEXR2001,2,3 PAIN.001.001.03

Other ALE messages compatible with PEXR200<N> are not supported at the current version.

SAP ERP Inbound

SWIFT MT940, MT942 These are the formats already supported by SAP ERP transaction FF_5 and also the SAP FSN Connector.

ISO20022 CAMT.053(...)

In order to import messages not supported by SAP ERP, it is required to import a support package or implement and advance development. Ref: SAP support note 1686264

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/304335f7-f33c-2a10-ae80-9c9ffdc86415?QuickLink=index&overridelayout=true&17390322584034

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/304335f7-f33c-2a10-ae80-9c9ffdc86415?QuickLink=index&overridelayout=true&17390322584034

https://service.sap.com/sap/support/notes/1686264


8

INTEGRATION

Implementation Project Overview To integrate with SAP FSN, there are several tasks to be executed as depicted in the following Gant diagram: OnBoarding Integratio

n

Testin

g

Go

Liv

e

OnDemand 1. Activation & Cloud Env.setup

2. Transformation development

3. iFlow Development

OnPremise 4. Connectivity Set up

5. SAP FSN Connector Installation

6. Configuration

7. SAP ERP Configuration

1- Activation and Cloud Environment Setup: It comprises the list of task from the parties agreement to

the basic corporate cloud environment setup.

2- Transformation Development: Format and field level transformations in payments, statements and

payment status updates.

3- Iflow Development: They handle connectivity, routing and invoke transformation. They also

interoperate with the canonical database.

4- Connectivity Setup: Corporate side connectivity with SAP FSN. Involves several tasks around

security and technical access to SAP Hana Cloud and its Integration Services.

5- SAP FSN Connector Installation: Involves the SAP ERP Add-On installation as well as the

prerequisites when required.

6- Configuration: SAP ERP FSN Connector configuration ranging from SAP NetWeaver web service

runtime to payment medium handling.

7- SAP ERP Configuration: Potential review of SAP ERP FI payment mediums, house banks or

statement customization if required.

Steps in Detail The steps are split in different sections; some of them are described in this document, while others are referenced. OnDemand Steps are not described in this guide, it’s already covered in the referenced documentation.


9

1. Planning the Integration Strategy

Appendix 1 includes all the following items structured in a convenient questionnaire to be used during corporate onboarding. It includes specific questions as well as other more generic to help better understand the customer situation.

1.1. Understanding the Customer Installation

In order to determine the complete scope, it is required to understand the number of SAP ERP systems and companies that are going to be integrated. Furthermore it is recommended to also determine the complete relevant software landscape, more specifically in terms of SAP foot print. The rationale for this is the existence of industry specific or custom modules affecting the expected interaction.

1.2. Financial Institution Integration Landscape

SAP ERP does not have strong integration capabilities and rely on external components (e.g. SAP NetWeaver PO). So it should be usual to find customers already running financial integrations integrated via a middleware component. It is recommended to understand and analyze the existing integration landscape and how the customer initially plans to integrate with SAP FSN. There are 2 basic options to integrate existing middleware (others may be implemented but may require more analysis and compatibility checks):

Using the SAP FSN Connector File picker functionality: The middleware component generates or read

files.

Using SAP NetWeaver PO WS Adapter: here the SAP FSN Connector WS-Runtime configuration must

be linked to SAP NetWeaver PO (any version with WS Adapter is supported) and SAP NetWeaver PO

linked to SAP FSN.

Another important question is whether SAP Financials FSCM-BCM is going to be integrated or not. For BCM integration is supported as of SAP ERP EHp2.

1.3. Corporate Security

There are different levels of security. SAP FSN Connector supports both transport and message level security. Should message level security be required by the corporate, it is necessary to implement the related sections of this document. Another important decision in terms of corporate security is the possibility to forward incoming requests to the SAP ERP. Should it be allowed, a reverse proxy or SAP web dispatcher is required, if not, the SAP FSN connector should be polling on a regular basis running as an ABAP batch job (aka “Push/Pull” scenario).

1.4. Implemented Scenarios

SAP ERP offers different technologies for payments, status and statements integrations. It is required to determine what customers are currently using, what’s supported from SAP FSN side, and how to combine both scenarios. Going into further level of details, payments can be:

Generated using the SAP ERP FI Payment Medium Workbench (PMW) and distributed via the Data

Medium Exchange Engine (DMEE).

Generated via RFFO programs:

o ALE

o SAP RFFO Programs

o Custom Programs

Currently SAP FSN supports the following methods for payments:

PMW:

o ISO20022 PAIN.001.001.03 with payload monitoring capabilities if not encrypted

o Other formats without specific SAP FSN connector payload monitoring

ALE: PAYEXT with any existing IDoc format (PEXR200<N>). Related ALE messages DIRDEB,

CREADV, DEBADV, CREEXT, EUPEXR and ALEAUD are not supported.

Others: Any local file can be picked up and transmitted.


10

In terms of Electronic Statements, the SAP FSN Connector works in conjunction with SAP ERP transaction FF_5. ALE and DMEE integration is not present at the moment. Currently SAP FSN supports the following transmission formats for statements:

SWIFT MT940 and MT942 messages.

Implementing and advanced development it is also possible to import ISO 20022 CAMT.053

messages.

These formats are generated from SAP FSN, that is, it is transparent to the corporate since monitoring is not affected by the transmission format. As mentioned above, neither DMEE nor ALE FINSTA/LOCKBOX are present at the moment, representing only a minor impact in integration monitoring. Posting payment status information via SAP ERP electronic statement functionality is not supported, and cannot be migrated to the current SAP FSN version. For customers using SAP ERP FI-FSCM BCM, payment status is supported (ISO 20022 PAIN.002…) Another very important consideration is how enriched or customized the payment medium is. Many customers implement different variations for customers, countries, vendors, banks, etc… It is required to gather information on field level conversions and enrichments executed either inside the SAP ERP system or outside if a middleware component involved is going to be decommissioned.

1.5. Corporate Scope Identification

To identify the complete scope of the implementation it’s required to determine the list of systems, companies and other organizational or master data objects involved in the exchange and plan the integration accordingly. Here is a list of possible object involved:

SAP ERP system/client (ALE Logical System): All client wide payments are forwarded to SAP FSN.

Company Codes: All the sending company payments methods are redirected to SAP FSN.

Vendors: Only some particular vendor payments are forwarded to bank via SAP FSN.

Payment Methods: Particular payment methods or even new payment methods are created to be

forwarded via SAP FSN.

House Banks: It is also possible to redirect a house bank to SAP FSN. All payment methods

involved are forwarded to SAP FSN.

2. SAP FSN Onboarding (Service activation and cloud environment setup)

This step comprises the mutual agreement among the 3 parties involved (SAP ERP user as the corporate customer, SAP FSN as the forwarder and the Financial Service Provider entity). Then the SAP Cloud environment set up takes place, and finally the implementation process. The SAP FSN Onboarding Guide a document comprehensively describing all the procedures and the tools involved (e.g. SAP StreamWork). It is recommended for technical roles to read this document before proceeding with this guide.


11

3. SAP FSN integration with SAP ERP back-end

3.1. SAP FSN Connector Add-on Installation and Configuration

3.1.1. Introduction

Read the SAP FSN Connector SAP support note 1781614 on release strategy and prerequisites. SAP FSN Connector runs on SAP ERP 6.0 Ehp0 or above. For SAP FI FSCM-BCM Integration Ehp2 minimum is required. SAP FSN Connectors uses the SAP NetWeaver Web Services Runtime (and thus the ICM) to interact with the outside world.

3.1.2. Download

Access the software download center in the SAP Service Marketplace. Execute http://service.sap.com/swdc

Access the “Installation and Upgrades”

Select “C”

https://service.sap.com/sap/support/notes/1781614

http://service.sap.com/swdc


12

Select “CONNECT.F. SAP FIN.SERV.NW.”

Select “CONNECT.F.SAP FIN.SERV.NW. 2.0”

Select “Installation”

Right click to download directly.

3.1.3. Installation

Follow the SAP ERP Add-on Installation Tool documentation

3.1.4. General Configuration Guide

To Configure the SAP FSN Connector, access the customizing transaction (SPRO) Reference Implementation Guide (F5) “Financial Services Network Connector”.

http://help.sap.com/saphelp_nw04/helpdata/en/49/3e896728ab2222e10000000a42189d/frameset.htm


13

3.1.5. Maintain Number Ranges for Message ID (Optional)

Should the number range be adjusted, access the “Maintain Number Range for Message ID” This step is typically required after transport

Go to “Status”

Reset the number to the appropriate value for the current environment. Explain more “N2” check

Save your entries

3.1.6. Maintain SSF Profile Data

This step will be executed later as part of the security configuration.

3.1.7. Maintain Residence Time for Message Archiving

The residence time defines the length of time messages are stored before becoming eligible for archiving.

Access the configuration option


14

The system lists the already existing message types.

Save your entries

3.1.8. Maintain Sender ID

This is not a mandatory step since an alternate identifier in the following item “Maintain Custom Sender IDs”. For payments integrations using the Payment Medium Workbench, the corporate customer identification is taken from the house bank.

Start menu “FBZP” in every participant SAP ERP system (development system)

Access house banks

Execute for each participant company code

Select each participant house bank and go to the details:


15

Expand “Data medium exchange”

Fill up the “Customer number” with the corporate real house bank customer identification.

Save your entries.

3.1.9. Maintain Custom Sender IDs

These custom Sender IDs are used by the connector for the SAP Financial Services Network whenever a message is created. For payment messages created via Payment Medium Workbench, the system uses the Customer Number maintained at House Bank level as the Sender ID (the corresponding custom Sender ID entries are ignored). However, the system uses the custom Sender ID maintained in this Customizing activity as a fallback, and it is used in the event that the Customer Number has not been maintained at House Bank level.

You can leave the Message Type and/or Receiver ID blank. The system treats such entries as relevant for all Message Types and/or Receiver IDs. In the event of multiple valid entries, the system uses the most specific one.

This method is based on the “SWIFT code”, available as part of the house bank address control data. For the SAP FSN connector, the SWIFT code represents the “Receiver ID”:

House bank Swift Code = SAP FSN Connector Receiver ID.

Access the configuration Option

Execute “New Entries”


16

Specify the message type, the SWIFT Code and the desired “Sender ID” to be used

Save your entries

3.1.10. Create Bank Statement import format Variant

This step allows configuring the import format. This section will create –if not present- the import variant.

Start transaction “Import Bank Statement” Ref: (trx FF_5 or FF.5 report RFEBKA00)

Select the existing variant or create a new one

Save it. In this example we name if “MT940”.


17

3.1.11. Maintain Selection Variants for Bank Statements

In the SAP FSN Connector Implementation Guide start transaction “Maintain Selection Variant for Bank Statements”


If required, specify the specific “Sender ID” or leave it empty. Type the message type (It is possible to select from the existing messages in the system as well using the drop down) Add the variant recently created (“MT940”).

Save your entries

3.1.12. SAP FSN WSDL file

In order to communicate with the SAP HCI Services, it is required to download the appropriate web service description file and configure the involved SAP NetWeaver web service runtime layers where SAP ERP system is running. This file is provided by SAP to the corporate as part of the OnBoarding procedure.

3.1.13. Web Services Configuration

This step will configure the Web service connectivity

Start Transaction SOAMANAGER

Go to “Business Administration”


18

Click on “Web Service Administration”

Outbound Communication

Here it’s required to determine in advance whether the SAP ERP will be receiving incoming requests from Internet or pulling information. It will also influence the network topology. SAP FSN Connector provides an asynchronous proxy for scenarios where SAP ERP is allowed to receive incoming request and a synchronous process for installations where SAP ERP has to actively fetch information from SAP FSN.

Search by “Consumer Proxy” the search pattern “/BSNAGT/*” as internal name. Execute “Go”

Notice 2 different proxies appear as explained above. Choose the one appropriate for the installation. Execute “Apply Selection”

Go to “Configurations”

Create new logical port


19

Create the port as described in the OnBoarding Guide Configuring WS Consumer (Logical Port)

This port should be marked as “default” and will be used for all use cases where no receiver specific port is set up(Maintain alternative Logical Ports for Outbound Messages).

Inbound Communication

This step is only required of the asynchronous consumer proxy was used.

Select “Service”, pattern “/BSNAGT” and execute “Go”.

Highlight the service and execute “Apply Selection”.

Go to “Configurations”


20

Create another endpoint following the Onboarding Guide Configuring WS Provider Endpoint

3.1.14. Maintain alternative Logical Ports for Outbound Messages

This activity is relevant for Web Services communication. Customizing activity, you can optionally define the alternative logical port to be used for outbound messages. You use this Customizing activity in cases where the default logical port, which is defined in transaction SOAMANAGER, should not be used. You enter the logical port for each Receiver ID. When sending messages, the system checks this table. If an entry is found for the current Receiver ID, then the system uses the corresponding logical port to send the message. Otherwise, the default port defined in transaction SOAMANAGER is used.

In the SAP FSN Connector IMG access “Maintain alternative Logical Ports for Outbound Messages”


Select the Receiver ID and specify the specific Logical Port to be used. Notice this logical port has to be previously created in SOAMANAGER as shown above.

Save

Additional options for redirection:

It is also possible to programmatically alter the port determination.

The implementation guide provides access and documentation to business add ins for this purpose


21

3.1.15. Download the client and server certificate

During OnBoarding procedure, SAP also delivers the required certificates to be imported in the following step.

3.1.16. Configure Certificates

3.1.17. Adding a Distinguished name to a technical user

This step assigns a systems user name mapped to the certificate being used to log on.

Start Transaction “STRUST”

Choose “SSL server Standard”

Import the certificate

Save the entries


22

Start transaction SPRO, execute Reference IMG (F5) SAP NetWeaver Application Server System Administration Management of External Security Systems Maintain External Identifications for Users External Identification for Users (Type DN).

Maintain the relationship.

Save your entry.

3.1.18. Maintain SSFA parameters

Start transaction SSFA

Add new entries

Specify “BSNAGT”


23

Maintain parameters

Save Entries

3.1.19. Encryption Configure SSF (message level Security)

Maintain the entries for every sender and receiver.

3.1.20. Archiving Process Configuration

Access transaction SARA and .configure archiving object /BSNAGT/AO.

3.1.21. Input Configuration

This section explains the 3 method to send information to the SAP FSN Connector:


24

It is important to mention that the following 3 procedures cover the redirection process comprehensively starting from the SAP ERP FI transaction, but it does not mean all these steps are compulsory, since most of this configuration could be reused as is. The following chapter will provide additional analysis on the options available. Customer configuration overview – payment medium scope verification

A simple way to overview the existing payment medium configurations in the current SAP ERP system, is to query table T042z as shown:

Start transaction SE16

Specify table t042z

Execute “List”

Select the countries involved and execute the query

The list provides a simple overview of payment methods and the PMW format ( Payment medium format)or RFFO* program in use ( Program):

3.1.19.1 Payment Medium Workbench

This step list will be executed either starting from the payment method configuration (typically starting transaction FBZP) or directly from transaction OBPM1.


25

Start transaction OBPM1 to customize the PMW formats.

Choose the formats that are to be redirected to SAP FSN.

Go to the details

Configure the format to produce “Payment medium without docs.”…

…and switch the Type to “SAP Financial Services Network Connector. This configuration instructs the SAP FSN Connector to intercept the payment medium during generation and redirect to the SAP FSN hub.

In the “Format Information” subscreen, document the “External format description”. It will allow the SAP FSN Connector Monitor to parse know formats. Encrypted payloads are not shown.

PAIN .001.001.03 is one of the payload formats the SAP FSN Connector is able to parse for monitoring purposes

Save your work.

To validate or update format usage (if not already done) follow this instructions:

Start transaction fbzp


26

Select “Payment methods in country”

Choose the payment method involved.

Go to the details.

Make sure the customized PMW format is in place.

Save your work

3.1.19.2 ALE/IDoc

The SAP FSN Connector ALE inbound capability is implemented as a local logical system receiver running in the local system (loop back). It means current IDocs are redirected to this new receiver. The following steps are executed in the development system and transported.

Before the actual redirection it is also required to customize the inbound process codes as well. Start transaction BD51 to add the ALE inbound process code, which is an ABAP function module


27

Add a new entry

Specify Function module “/BSNAGT/IDOC_INPUT_GENERIC” The input type is “0”, and dialog (processing) is not allowed. Save your entries

The new inbound function module needs to be assigned to the appropriate ALE message types and IDoc types:

Now start transactions WE57 to assign the ALE message and IDoc types that can be handled by the module

Switch to change mode

Add a new entry


28

Create an entry for basic type PEXR2001, PEXR2002 and PEXR2003, all for message type PAYEXT (outbound)

Then create the ALE inbound process code for the ABAP function module, ALE Message and IDoc format:

Start transaction WE42

Switch to change mode

Add a new entry


29

Create process code “SAP FSN” and add a description accordingly. It is for ALE processing via Function module as shown:

Select the function module previously customized:

Save your work

Now specify all the ALE messages that can be processed by the function module using this specific process code. Select “Logical Message”

Add a new entry:


30

Add ALE message type “PAYEXT” All message codes and functions are allowed. Message Code and Functions are typically exploited to identify use case specific functionalities

Save your work

Outbound processing configuration

This step aims to either determine or configure the “partner” representing the bank. This partner concept connects the house bank to the communication port: House bank EDI Partner Number Outbound configuration Outbound PortCommunication medium. It is not required to create all new objects, existing configuration can be reused. In order to understand current system configuration and possible inconsistencies, query table T012D as show before for payment methods.

Start transaction FBZP

Go to House Banks

Specify the Company Code

Choose the house bank to be configured:


31

If the EDI partner number is already specified, you can navigate for configuration proposals. Specify the partner number The system will trigger a warning notifying the partner number is new, and needs further configurations

Save your work

The next step (system dependent) creates the technical link between the sender process (SAP ERP FI payment medium generation) and the receiver process (SAP FSN Connector).

Start transaction sm59 to create an ABAP RFC destination Notice this steps typically is executed by the system administrator and may require additional configurations. At least the system administrator should be contacted to validate the destination is not already created.

Position in “ABAP Connections” and execute “Create” as shown:


32

Name the destination (here “SAPFSNCONNECTOR – case sensitive). Add a description and switch to the “Technical Settings” tab strip. Target host is “localhost” and the system number is to be provided by the system administrator, (alternatively function module “GET_SYSTEM_NUMBER” provides temporary information for testing purposes). It is recommended to validate al this configurations with the system administrator including the usage of required Unicode settings.

Now the outbound port is to be created (if not already available)

Start transaction we21

Select “Transactional RFC”

Execute “Create”


33

Select “Own Port Name” and name it, e.g. “SAPFSNCONN”

Add a description and specify the “RFC destination” previously created as shown:

Save your work

The next step creates the “EDI partner number” previously created as a real partner B for communications. These entire configurations are client dependent.

Start transaction we20. Alternatively you can jump from the EDI partner number configuration in FBZP.

Select “Partner Type B” and execute “Create”


34

Specify the Partner number previously created in the house bank EDI partner number configuration and type “B” for “bank” as partner type. Post processing configuration points to the agent in charge of monitoring and should be provided by the customer. If not required, simply specify type “US” and the current user name and logon language.

In the outbound parameters section, click on the green cross icon to add a row.


35

Specify message type “PAYEXT”, the receive port previously configured and the IDoc in use, which can be any “PEXR*” or customer extension, etc…. Extensions to “PEXR*” IDocs may impact some of the SAP FSN Connector built in capabilities. Involve a customer ALE consultant to understand further configuration options and eliminate any impact in the current ALE operations.

Save your entries

At this moment, the system is configured to generate IDocs for the SAP FSN Connector. The next steps configure the SAP FSN Connector to actually receive them. Inbound configuration

This configuration instructs the SAP FSN Connector to process the IDocs previously generated. Now it’s time to find out the current ALE configuration, to redirect the IDocs to the SAP FSN Connector running in the local system (own logical name). These steps are system specific and need to be executed in every system and client involved. This procedure is similar to running function module “OWN_LOGICAL_SYSTEM_GET” in test mode.

Start transaction “SALE”

Execute “Assign logical system to client”


36

Highlight the row belonging to the client currently being used:

Notice the current logical system is “ZJPCLNT300”. Documen the value for the following steps to configure the inbound processing Typically, logical systems are named as a combination of SAP ERP system ID and client number, here:

JZP300

ZJPCLNT300

Etc…

Now the SAP FSN Connector is created as a valid partner in the IDoc exchange

Start transaction we20.

Create a new partner type “Logical System” It is only required if the current logical system is not already created as a partner.


37

Create the logical system previously documented.

Save your work.

Add an new Inbound parameter

Specify the inbound process code created for SAP FSN a

Save your work.


38

3.1.19.3 File

The SAP FSN Connector provider a file interface, it relies on the logical file path configurations

Start transaction FILE

Add a new entry

Create a logical path for the SAP FSN files

Select the row

Specify the assignment to physical paths

Add a new entry

Specify the real physical path in the current system, including the filename placeholder as usual

Save your work


39

Go to “Logical File Name Definition”

Add a new entry

Create the file name. Physical file name is <PARAM_1> since it is totally variable. Specify the logical path previously created as well.

The file name with be structured like this:

<PARAM_1> Order Description Maximum Characters

Mandatory/Optional

1 Message Type

32 Mandatory

2 Sender ID 64 Mandatory

3 Receiver ID 64 Mandatory

4 Number of Records

10 Mandatory

5 File Name 80 Mandatory

6 Message ID 20 Optional (if not provided, the Pick-up Files report generates a Message ID)

<MESSAGE TYPE>;<SENDER ID>;<RECEIVER ID>;<NUMBER OF RECORDS>;<FILENAME>;<FSN CONNECTOR MESSAGE ID>

File name example: PAIN.001.001.003;CUST2345;REC6789;125;FILE9876;10902032456

Now it is possible to specify a client dependent variation (recommended):

Start transaction SF01

Add a new entry


40

Select the appropriate file previously created and customize accordingly

Save your work

The SAP FSN connector provides a program to read the files:

Start transaction /BSNAGT/PICK_FILES

Customize accordingly, using the filename created in SF01 (or FILE) This process will scan the directory contained in the file name definition looking for compatible files

Execute the report of schedule as a recurring batch job in accordance with the customer needs.

3.1.20 Integrating with SAP NetWeaver PI/PO

Corporates implementing SAP NetWeaver PO (or older SAP NetWeaver PI versions supporting WS-RM) can integrate directly with SAP FSN.


41

This SAP FSN version still requires the usage of SAP FSN Connector as a path-through for basic enrichment, security and header level routing, among other services. That is, the SAP FSN Connector will not be in contact with the SAP Hana Cloud, but SAP NetWeaver PI/PO: SAP ERP <->SAP FSN Connector<->SAP NetWeaver PI/PO<->SAP HANA Cloud

3.1.21 Integration using other middleware components

SAP FSN do not enforce any middleware decommission (message brokers). Existing middleware can be integrated as well. The only requirement is the capability to interact via Files. That is the middleware component should be capable of reading and writing files to a common folder accessible from SAP ERP (e.g. using NFS).

3.2 SAP Web Dispatcher

The SAP Web Dispatcher is similar to a reverse proxy and may be only required when SAP ERP is receiving incoming requests. SAP ERP documentation describes the SAP Web Dispatcher in detail.

http://help.sap.com/saphelp_erp60_sp/helpdata/en/42/5cfd3b0e59774ee10000000a114084/frameset.htm


42

4. SAP ERP Configuration

4.1 Understanding the configuration options

As previously mentioned, there are several options to determine and filter the scope of payment documents to be forwarded to SAP FSN. From a general perspective SAP FSN should be seen as forwarding party, that is, it is not a payment medium, but a transmission medium. As such the more appropriate redirection option is closer to the technical layer (e.g. the house bank EDI partner number). Should a customer choose to onboard to SAP FSN gradually, then it is possible that, as mentioned in the beginning, there’s a need to segregate what payments are routed to SAP FSN. It is also important to mention that while ALE natural redirection is at house bank level (EDI oriented), PMW is payment medium oriented (some type of file communication).PMW actually supports different types of payment mediums including IDocs, but this options is not described within the scope of this guide, which seems to be not so widely adopted.

4.2 Technical Redirection

The technical redirection has already been covered in the SAP FSN Connector Input Configuration Chapter. It assumes no changes in SAP FI configuration (FBZP), but on the underlying technical components:

ALE: the bank party partner profile is updated in transaction WE20. A tRFC receiver port (WE21) pointing to the local host must be used.

e.g. “SAPFSNCONN” here

PMW: The format must use a medium without documents and pointing to type “SAP Financial Services Network Connection” (It is also possible to access the format directly via transaction OBPM1)

Files: Files are to be left in an accessible location and a logical file (FILE/SF01) needs to be created pointing to the logical path to be scanned for appropriate files.

4.3 House Banks Specific Redirection

4.3.19 ALE

If only a subset of the banks is going to be redirected to SAPFSN, the best options are: 1. Create a generic EDI partner number (type Bank in WE20) pointing to a common SAP FSN port

(technical redirection)


43

2. Maintain a house bank specific EDI partner number pointing to a common SAP FSN port (technical

redirection)

The difference in the approach resides in ALE monitoring. If the corporate customer prefers to see the bank in the monitoring (BD87/WE05/WE02), then a house bank specific EDI partner number is required. The recommended approach is to create just one EDI partner representing SAP FSN (Option 1). Also the EDI compatible payment methods need to be specified and house bank level:

4.3.20 PMW

Since PMW is directly linked to the payment method (country level), redirecting the house bank communication is not supported

4.4 Payment Method Specific Redirection

One important comment is that the payment method helps determining the house bank (OBVCU), thas is there is a close relationship between the payment method and the house bank.

4.4.19 ALE

These are the 2 configuration steps: 1. The payment method must be configured to use the classic RFFO* program for EDI

2. All involved house banks must be tentatively configured as well as described in the previous step.

4.4.20 PMW

If the PMW formats involved are specifically used for SAP FSN, then the output can be redirected (as shown in the technical redirection). If, on the other hand, the PMW format is shared among different payment methods requiring diverse outputs, it is required to duplicate the format or choose another one specific for SAP FSN.

4.5 Vendor Specific Redirection

4.5.19 ALE

Configure the only payment methods and house banks already redirected to SAP FSN in the company level vendor master record (automatic payment transaction sub screen).

4.5.20 PMW

Configure the only payment methods already redirected to SAP FSN in the company level vendor master record (automatic payment transaction sub screen).

4.6 Implementing new payment methods or house banks for SAP FSN

This configuration is required when SAP FSN is linked to new payment methods, meaning those not supported by the SAP ERP natively, e.g. card payments.

There are 3 basic steps:

1- Create the payment method to be used in conjunction with SAP FSN choosing the desired payment

medium. Choose whenever possible a compatible payment medium already implemented

Payment Method Creation

Create or Update the payment methods similar to electronic transfers:

• For IDoc configure RFFOEDI program

• For PMW configure PAIN.001.001.03

House Bank Creation

Create the new house bank:

• Configure the EDI partner if ALE is used

• Configure the Customer Number to be used in SAP FSN Connector

Assignment

Assign house bank to payment method (and

currency code if required)


44

2- If the payment method is bank specific, create the new house bank.

3- In the House Bank Determination strategy, add the payment method and bank :

4.7 Gathering relevant information for payments transformations

Once the payment method and house bank configuration is finished, it is required to determine what field level conversions are going to be required in the transformation to the ISO20022 canonical model. This example shows field business function in an IDoc segment (PAYEXT/PEXR/E1IDKU2). Business function represents the type of commercial transaction. Here “001” represents “Purchases and Sales”. Domain tables need to be documented to be later used during the transformation development.

Other transformation related objects like ALE Global Organizational Units and Conversion rules also need to be documented.

4.8 Gathering relevant information for the electronic bank statements generation

This process is like reverse engineering and a follow up step after the payment scope has been determined, that is the entry point to the electronic bank statement configuration is the house bank and account:

The “Bank Key” and “Bank Account” point to “Transaction Types” that must be informed by SAP FSN. In summary this is the procedure to determine the involved transaction types to be created by SAP FSN:

1. Create the list of participating Bank Keys + Bank Accounts from the payments configurations


45

2. Start the implementation guide, go to “Make global settings for electronic bank statement” as shown:

3. Select the appropriate char of accounts. (do it for all)

4. Go to “Assign Bank Accounts to Transaction Types”

5. Document the involve transaction types. E.g. “JP” and “ZA”.

6. Go to “Create Transaction Type” for each

7. Select the desired transactions type, e.g. “JP” here


46

8. Go to the posting rule assignment

9. Document all the external transactions that need to be supported from SAP FSN and the rules when to be used.

This list and the usage rules must be hand over to the team implementing transformations External transactions indirectly represent the impact in financial accounting. E.g. 110: Payment Processed 120: Payment Cancelled Every customer creates the external transaction in their own environment.


47

5. SAP FSN Integration Implementation

All the OnDemand implementation is described as part of the SAP FSN Developers Guides.

6. Setting up Authorizations

All the authorization objects involved in the SAP FSN connector are described in the masterguide attached below.

7. (Optional) SAP Financials FSCM-BCM Integration (as of SAP ERP 6.0 Ehp2)

SAP FSN Connector accepts incoming payment status files and forwards them to BCM. Required BCM configuration is without the scope of this guide.


48

APPENDIXES

Appendix 1: Installation Information Gathering Motivation This section aims to gather information on SAP ERP implementation to identify the corporation integration options with SAP FSN. For simplification reasons the term “SAP ERP” is used in this document to reference any version of the product family evolved from SAP R/3 where the Finance Account Payable and Receivable modules are implemented. It is not meant to denote version specific restrictions whatsoever. List of Implemented FSN-Relevant Products & Modules:

SAP Product

Implemented Modules

Current Version* # prod Inst

# prod Clients

Column Reference Column Meaning

SAP Product Installed & Implemented product or application

Modules SAP FSN relevant modules, sub modules, add-ons or industry extensions

Current Version Both to SAP application version (including enhancement package level) and also SAP NetWeaver version if present.

Number of Productive Installations

Number of productive Instances worldwide (One instance == One SID)

Number of Productive Clients For Installations with multiple productive clients, specify that number, otherwise blank.

Financial Institution Integration Landscape This section refers strictly to B2B integration with financial institutions, other integrations for logistics, etc. should not be considered.

Question Yes

Is SAP FSN to be directly connected to SAP ERP? If no, please explain

Is it planned to connect to FSN via middleware components? (e.g.: SAP NetWeaver PI, Microsoft BizTalk , IBM WebSphere, SAP Business Connection, Custom Development)

If yes, what format and communication protocol it is required to support to integrate?

Names:_____________________________________________________________________________________ Format/Protocols: __________________________________________________________________________________________________________________________________________

Is SAP ERP FSCM-BCM (Banks Communication Manager) Implemented for some SAP ERP instance? If yes, Is it required to integrate SAP FSN with SAP BCM?

Version:

Is SAP NetWeaver PI Implemented** If yes: B2B financial adapters implemented? (e.g. Seeburger, Advanco, iWay, etc.)

Version: Name:


49

Is SAP Business Connector implemented?

Is there any middleware process running outside the SAP ERP for payment/statement for enrichment purposes?

Yes

** refers to the family of products: SAP NetWeaver Exchange Infrastructure, SAP NetWeaver Process Integration & SAP NetWeaver Process Orchestration. Corporate Security

Question

Is Message Level Security Required? Optional Required

Specify message encryption technologies allowed Any Specifics:

Is it possible to run the FSN connector add-on in the productive SAP ERP environment

Yes No

Is it allowed to accept remote incoming requests? (always considering all the additional network security related components)

tRFC https

Is SAP Web Dispatcher already implemented? Yes

What secure connection options are allowed?

Technology Allowed Suggested

WS-RM over https

sFTP

Native SAP (transactional RFC)

Any over VPN

Other Required:

Is the internet being used for payment related communications or dedicated line?

Internet Dedicated Line

Is the internet being used for financial statements related reception or dedicated line?

Internet Dedicated Line

Is there any additional relevant company specific corporation policy to be considered beyond the regular IT common practices?

Scenarios Integration Technologies

Question

Are there complex user-exits (enhancements) or custom output programs (ZRFFO…) in use? Please detail purpose for all FSN relevant country/payment methods (e.g.: enrichment, format conversion, etc.)

Is ALE used for Payments & Statements? (IHC or other internal should not be considered) List Message types and IDoc Versions

PAYEXT / PEXR200 <1/2/3> DIRDEB / PEXR200 <1/2/3> DEBADV / PEXR200 <1/2/3> CREEXT / PEXR200 <1/2/3> FINSTA / FINSTA01


50

LOCKBX / FINSTA01 Extended Messages or IDocs Custom Messages or IDocs

Is ALE payment signature required?(EUPEXR) Yes

IS ALE Disaster Recovery required? (RCY*) Yes

IS ALE audit message required? (ALEAUD) Yes

Are the ALE payments routed to a generic or financial institution specific receiver bank? background: SAP ERP house banks allows the specification of a “bank partner type” as defined in the “Partner Profile” (trx: WE20), as an alternative the payment may be directed to a single middleware component with routing capabilities or a “country payment method” specific payment medium processor process.

Generic Specific

Are the ALE logical system names and company codes unique across all the systems connecting to SAP FSN?

Yes No

Is the Payment Medium Workbench in use? Yes

If yes. Is some global/ industry/country/regional standard, bank specific or business network specific format being generated? (from the system that will be connected to SAP FSN)

_______________ _______________ _______________ _______________ _______________ _______________ _______________ _______________ _______________ _______________ _______________

What are the current formats in use for payments transmission?

Custom Flat Files XML Files IDocs plain HTTP _______________ _______________

What are the current formats in use for statement reception?

Custom Flat Files XML Files IDocs plain HTTP _______________ _______________

Is any service provider to be integrated in the distribution of payments / statements?

Yes ______________________________

Expected Volumes

Technology Avg Daily Quantity

Max Peak [msg/sec]

Avg Volume [Gb/day]

Payments _____ at __:__ __

Statements _____ at __ :__ __

Payment Methods

Question


51

What payment methods are going to be integrated into FSN?

Transfer Payment Card Check ACH Others: __________________________________________________________________________________________________________________________________________________________________________________________

Accounts Payable & Accounts Receivable

Question

What countries are going to be integrated into FSN in the first implementation phase?

What payment methods are going to be integrated into FSN in the first implementation phase?

How many company codes

Yes

Is the SAP ERP “In house cash” (IHC) scenario implemented?

Bank Accounts Configuration This section refers to House Banks Configurations in the SAP ERP (trx FI12)

Question

What fields are being used in the SAP ERP to identify the house bank number in a unique way (considering all the country and company codes involved)

House Bank Bank Key Swift Code EDI Partner Number Others:________________________________________________________

What fields are being used in the SAP ERP to identify the customer number given to corporation by the bank? (considering all the country and company codes involved)

Customer Number Company Number Swift Code Others:________________________________________________________

What fields are being used in the SAP ERP to identify the house bank account in a unique way (considering all the country and company codes involved)

Bank Account Number Bank Key IBAN Country Specific Alternative acct no. Others:________________________________________________________

Vendor Payments Configurations

Question

What information is used in the vendor master Bank Key


52

record to uniquely identify the target account for the payment? (considering all the country and company codes involved)

Bank Account Account Holder SWIFT Agent Bank Control Key (CK) IBan Reference Detail Others:________________________________________________________


53

Appendix 2: Documentation

SAP FSN Connector

service.sap.com/instguides

Scenarios & Processes Configuration

SAP Service Market Place Link http://help.sap.com/saphelp_fsnagt20/helpdata/EN/bsn_index.htm

SAP Web Dispatcher


http://aiokeh.wdf.sap.corp:50000/SAPIKS2/contentShow.sap?IWB_INDUSTRY=SOLMANCONT&TMP_IWB_TASK=PREVIEW2&_CLASS=BCO_COMMON&_LOIO=00429F1623A9490C93F8C23A64A551D7&_SLOIO=465213478E494CB093FAEB2320FB5BDA&LANGUAGE=EN&RELEASE=2012_SP35&_SCLASS=XDP_STRUCT

http://aiokeh.wdf.sap.corp:50000/SAPIKS2/contentShow.sap?IWB_INDUSTRY=SOLMANCONT&TMP_IWB_TASK=PREVIEW2&_CLASS=BCO_COMMON&_LOIO=82DEA35A9413437DA00C82DE5B1AFBB9&_SLOIO=073A3A13B0A049AFAECA4C52DED8CF38&LANGUAGE=EN&RELEASE=2012_SP35&_SCLASS=XDP_STRUCT

http://help.sap.com/fsnagent20#section2

http://help.sap.com/saphelp_fsnagt20/helpdata/EN/bsn_index.htm



www.sap.com

© 2013 SAP AG. All rights reserved.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP

BusinessObjects Explorer, StreamWork, SAP HANA, 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.

Business Objects and the Business Objects logo, BusinessObjects,

Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and

other Business Objects products and services mentioned herein as

well as their respective logos are trademarks or registered trademarks

of Business Objects Software Ltd. Business Objects is an SAP

company.

Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL

Anywhere, and other Sybase products and services mentioned herein

as well as their respective logos are trademarks or registered

trademarks of Sybase Inc. Sybase is an SAP company.

Crossgate, m@gic EDDY, B2B 360°, and B2B 360° Services are

registered trademarks of Crossgate AG in Germany and other

countries. Crossgate is an SAP company.

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.

These materials are subject to change without notice. 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. .

Date post:	16-Nov-2021
Category:	Documents
Upload:	others
View:	4 times
Download:	0 times

Á } } v v } ^ W &^E - archive.sap.com

Documents