Configuration Guide - SAP IP SWIFT

Configuration Guide

SAP Integration Package for SWIFT Document Version 0.4 – February 2009

SAP AG Neurottstraße 16 69190 Walldorf Germany T +49/18 05/34 34 24 F +49/18 05/34 34 20 www.sap.com

© Copyright 2006 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, 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, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation in the United States and/or other countries. Oracle is a registered trademark of Oracle Corporation.

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. 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.

Disclaimer Some components of this product are based on Java™. Any

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

code change in these components may cause unpredictable

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.

prohibited, as is any decompilation of these components.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

be used by SAP’s Support Services and may not be modified or

and severe malfunctions and is therefore expressively

Any Java™ Source Code delivered with this product is only to altered in any way.

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.

Documentation in the SAP Service Marketplace You can find this documentation at the following address: http://service.sap.com/xi -> Media Library -> Guides

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

2

Typographic Conventions Type Style

Represents

Icons Icon

Meaning

Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths and options.

Caution

Cross-references to other documentation

Recommendation

Example text

Emphasized words or phrases in body text, titles of graphics and tables

Syntax

EXAMPLE TEXT

Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE.

Example Text

Example text

Screen output. This includes file and directory names and their paths, messages, names of variables and parameters, source code as well as names of installation, upgrade and database tools.

Example text

Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.



Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.

EXAMPLE TEXT

Keys on the keyboard, for example, function keys (such as F2) or the ENTER key.

Example Note

3

Installation Guide: SAP Integration Package for SWIFT

1 Preface ............................................................................................5 2 Using the SAP Integration Package for SWIFT ..........................6 2.1 2.2

Integration Process SWIFTMessageCollection ....................................... 6 Creating of Configuration Scenarios........................................................ 6

3 Examples for the Configuration of the Pay to Reconcile Business Scenarios for FIN...............................................................7 3.1 3.1.1 3.1.2

3.2 3.3 3.4

Sending SWIFT MT Messages and Using SWIFTMessageCollection Integration Process ................................................................................. 7 Configuring of File Adapter.................................................................................... 7 Configuring of SWIFTMessageCollection Intergration Process .............................. 9

Receiving SWIFT MT Messages using FIN........................................... 11 Receiving Status Messages using FIN.................................................. 13 Setting up E-mail Notifications in Error Cases for FIN........................... 15

4 Examples for the Configuration of the Pay to Reconcile Business Scenarios for FileAct ......................................................18 4.1 4.2

Sending Files using FileAct ................................................................... 18 Receiving Files using FileAct ................................................................ 20

5 Useful Notes .................................................................................21 Appendix A........................................................................................22

4

February 2009

Installation Guide: SAP Integration Package for SWIFT

1 Preface This document provides a configuration guideline for the SAP Integration Package for SWIFT if used together with SAP Bank Communication Management (former SAP Bank Relationship Management) as shipped with SAP Enhancement Package 2 for ERP 6.0. These installations are possible:

Backend

SAP XI / PI

SAP Integration Package for SWIFT

SAP Enhancement Package 2 for ERP 6.0

SAP XI 7.0 SP13 or higher

602

SAP Enhancement Package 3 for ERP 6.0

SAP XI 7.0 SP13 or higher

602

SAP Enhancement Package 4 for ERP 6.0

SAP XI 7.0 SP13 or higher

602

SAP Enhancement Package 2 for ERP 6.0

SAP PI 7.1 SP7 or higher

622

SAP Enhancement Package 3 for ERP 6.0

SAP PI 7.1 SP7 or higher

622

SAP Enhancement Package 4 for ERP 6.0

SAP PI 7.1 SP7 or higher

622

Refer to the corresponding Configuration Guide which covers the configuration aspects for the backend and the majority of the settings for the Integration Directory of SAP XI / PI.

For further information about S.W.I.F.T. (Society for Worldwide Interbank Financial Telecommunications) refer to http://www.swift.com/.

Constraints The steps described in this configuration guide are all based on the condition that an XI / PI is already installed.

For more information about configuring SAP XI 7.0 and SAP PI 7.1 see the documentation for SAP NetWeaver in SAP Library under SAP NetWeaver .

Purpose This configuration guide describes the steps necessary to successfully configure the SAP Integration Package for SWIFT.

The information in this guide refers to the most up-to-date support package of SAP XI / PI at the time this guide was created.

February 2009

5

Installation Guide: SAP Integration Package for SWIFT

Intended Audience All groups of users involved in the setup of cross-application-component business processes in which messages are exchanged using SAP Exchange Infrastructure and for which business scenarios are defined in the Integration Repository.

Prerequisites You already have knowledge of the following: SAP XI Integration Repository / SAP PI Enterprise Services Repository SDM (Software Deployment Manager) You have already completed the following: Installed Java Web Start for SAP XI / PI Established a system landscape for SAP XI / PI and the SAP ERP 6.0 Added the SAP ERP 6.0 in the System Landscape Directory (SLD) of your SAP XI / PI Set up RFC connections to the SAP ERP 6.0 in SAP XI / PI. Installed the SAP Integration Package for SWIFT

If you need more information how to install SAP Integration Package for SWIFT, refer to the Installation Guide for SAP Integration Package for SWIFT.

2 Using the SAP Integration Package for SWIFT 2.1 Integration Process SWIFTMessageCollection If you want use the SWIFTMessageCollection Integration Process you need to import the corresponding ccBPM Integration Process from the Integration Repository into the Integration Directory of XI / PI.

2.2 Creating of Configuration Scenarios This procedure describes how to create configuration scenarios in the Integration Directory of the XI / PI system.

Prerequisite The required technical and business systems are available in the SLD. In the integration directory, you assign these systems to specific configuration scenarios.

Procedure ...

SAP Integration Package for SWIFT contains modules for a File Adapter. So for each business scenario, you have to create an appropriate Configuration Scenario in Integration Directory usually using the delivered modules. You need the following: directories for file exchange Configuration Scenario for a File Adapter containing the following objects:

6

February 2009

Installation Guide: SAP Integration Package for SWIFT

Service without Party (Business Service) with Communication Channels (Receiver + Sender) . Please note, that ‘Business Service’ was renamed to ‘Communication Component in PI 7.1 Receiver Determination Interface Determination Sender Agreement Receiver Agreement Chapter 3 and 4 contain several examples of possible business scenarios. All necessary objects are listed. Only special configuration requirements are mentioned. Complete the configurations according to your needs. Use File as Adapter Type if it is not explicitly mentioned.

3 Examples for the Configuration of the Pay to Reconcile Business Scenarios for FIN 3.1 Sending SWIFT MT Messages and Using SWIFTMessageCollection Integration Process

SAP BCM

You can see the general processing flow in the picture below. The SWIFTMessageCollection Integration Process can be left out.

File

File Adapter: Sender Channel

SWIFTMessageCollection Integration Process

File Adapter: Receiver Channel

File

SWIFT input directory

3.1.1 Configuring of File Adapter Business Service Inbound interfaces on the Receiver tab page:

February 2009

7

Installation Guide: SAP Integration Package for SWIFT

Name

Namespace

SwiftMessage_FIN

http://sap.com/xi/SWIFT

SwiftMessage

http://sap.com/xi/SWIFT

Outbound interfaces on the Sender tab page: Name

Namespace

Empty

Empty

...

Communication Channels The Processing Sequence on the Module tab for both communication channels:

Number

Module Name

Type

1

localejbs/swift/FINConversionToSWIFTModule

Local Enterprise Bean

2

localejbs/CallSapAdapter

Local Enterprise Bean

These parameters are available for the module FINConversionToSWIFTModule (see Appendix A for explanation): UseLocalSecurity, KeyId, IsNotificationRequested, IsUrgent.

Sender Agreement Interface to be used in the Sender section: Interface Namespace

SwiftMessage http://sap.com/xi/SWIFT

Leave the Receiver section empty.

Receiver Determination Interface to be used in the Sender section: Interface SwiftMessage

8

February 2009

Installation Guide: SAP Integration Package for SWIFT

Namespace http://sap.com/xi/SWIFT

Entries in the Receiver section: Party * Service *

In the Configured Receivers section, choose SwiftMessageCollection in the Service column. In the Configuration Overview for Receiver Determination section, choose the following: Receiver Service Receiver Interface

SwiftMessageCollection SwiftMessage

Interface Determination In the Sender section, the following information should be displayed: Interface Namespace

SwiftMessage http://sap.com/xi/SWIFT

In the Receiver section, the service SwiftMessageCollection has to be entered. Under the Configured Inbound Interface, the following information should be displayed as Inbound Interface: Name Namespace

SwiftMessage http://sap.com/xi/SWIFT

Receiver Agreement In the header Sender section, the name of your business service has to be entered.

Under the header Receiver, the name of your business service has to be entered. Use the following interface: Interface

SwiftMessage

Namespace

http://sap.com/xi/SWIFT

3.1.2 Configuring of SWIFTMessageCollection Intergration Process Receiver Determination Entries for the the Sender section:

February 2009

9

Installation Guide: SAP Integration Package for SWIFT

Service

SwiftMessageCollection

Interface

SwiftMessage

Namespace

http://sap.com/xi/SWIFT

In the Configured Receivers section, choose the name of your File Adapter Business Service as Service.

Interface Determination Entries for the the Sender section: Service

SwiftMessageCollection

Interface

SwiftMessage

Namespace

http://sap.com/xi/SWIFT

In the Receiver section the name of the File Adapter Business Service should be displayed. In the Configured Inbound Interface section, the following information should be displayed. Name Namespace

SwiftMessage http://sap.com/xi/SWIFT

Receiver Agreement In the Sender section, use SwiftMessageCollection as Service. Entries for the Receiver section are: Service

your File Adapter Business Service

Interface

SwiftMessage

Namespace

http://sap.com/xi/SWIFT

Select the Receiver Communication Channel that belong to your File Adapter Business Service.

10

February 2009

Installation Guide: SAP Integration Package for SWIFT

3.2 Receiving SWIFT MT Messages using FIN

File

File SWIFT output directory

File Adapter

SAP BCM

This chapter describes the configuration of the following process:

Business Service Add these inbound interfaces to the business service in the Receiver and Sender tab page:

Name

Namespace

Empty

Empty

Communication Channels The Processing Sequence on the Module tab for both communication channels should be:

Number

Module Name

Type

1

localejbs/swift/FINConversionFromSWIFTModule

Local Enterprise Bean

2

CallSapAdapter

Local Enterprise Bean

February 2009

11

Installation Guide: SAP Integration Package for SWIFT

These parameters are available for the module FINConversionFromSWIFTModule (see Appendix A for explanation): UseLocalSecurity, KeyId.

Sender Agreement Interface to be used in the Sender section: Interface Namespace

SwiftMessage_FIN http://sap.com/xi/SWIFT

Receiver Determination Interface to be used in the Sender section: Interface

SwiftMessage_FIN

Namespace

http://sap.com/xi/SWIFT

In the Configured Receivers section, choose the name of your service in the Service column. In the Configuration Overview for Receiver Determination section, SwiftMessage_FIN should appear in the Receiver column.

Interface Determination Under the header Sender, the following interface has to be used: Interface Namespace

SwiftMessage_FIN http://sap.com/xi/SWIFT

Under the header Receiver, the name of your service should be displayed: Under the Configured Inbound Interface, check whether the following information is displayed. Add the information if it is still missing: Name Namespace

SwiftMessage_FIN http://sap.com/xi/SWIFT

Receiver Agreement Under the header Sender, enter the name of your service.

Under the header Receiver, use the following interface: Interface

SwiftMessage_FIN

Namespace

http://sap.com/xi/SWIFT

12

February 2009

Installation Guide: SAP Integration Package for SWIFT

3.3 Receiving Status Messages using FIN

File

File SWIFT log directory

File Adapter

SAP BCM

This chapter describes the configuration of the following process:

Business Service Add these inbound / outbound interfaces in the Receiver and Sender tab:

Name

Namespace

Empty

Empty

Communication Channels The Processing Sequence on the Module tab for both communication channels is:

Number

Module Name

Type

1

CallSapAdapter

Local Enterprise Bean

Sender Agreement

February 2009

13

Installation Guide: SAP Integration Package for SWIFT

Interface to be used in the Sender section: Interface Namespace

SwiftMessage_FTA http://sap.com/xi/SWIFT

Receiver Determination Interface to be used in the Sender section: Interface SwiftMessage_FTA Namespace http://sap.com/xi/SWIFT

In the Configured Receivers section, choose the name of your service in the Service column. In the Configuration Overview for Receiver Determination section, SwiftMessage_FTA should appear in the Receiver column.

Interface Determination Under the header Sender, use this interface: Interface Namespace

SwiftMessage_FTA http://sap.com/xi/SWIFT

Under the header Receiver, enter the name of your service. In the Configured Inbound Interfaces section, use this as Inbound Interface: Name Namespace

SwiftMessage_FTA http://sap.com/xi/SWIFT

Receiver Agreement Under the header Sender, the name of your service should be displayed.

Under the header Receiver, this interface should be displayed: Interface

SwiftMessage_FTA

Namespace

http://sap.com/xi/SWIFT

14

February 2009

Installation Guide: SAP Integration Package for SWIFT

3.4 Setting up E-mail Notifications in Error Cases for FIN This chapter describes the configuration of the following process:

File SWIFT error directory

File Adapter: Sender Channel

Mail Adapter: Receiver Channel

e-mail

Business Service Add thise inbound interface to the business service in the Receiver tab page: Name

Namespace

ErrorLog

http://sap.com/xi/SWIFT

Add thise outbound interface to the business service in the Sender tab page: Name

Namespace

Empty

Empty

Receiver Communication Channel Select Mail as Adapter Type on the Parameters tab page. The Mail Attribute ‘Keep Attachments’ should be flagged. The Processing Sequence on the Module tab should be:

February 2009

15

Installation Guide: SAP Integration Package for SWIFT

Number

Module Name

Type

1

localejbs/AF_Modules/MessageTransformBean

Local Enterprise Bean

2

sap.com/com.sap.aii.adapter.mail.app/

Local Enterprise Bean

XIMailAdapterBean

Use this parameter for the module MessageTransformBean:

Parameter Name

Parameter Value

Transform.ContentDisposition

inline

Sender Communication Channel Select File as Adapter Type on the Parameters tab page. The Processing Sequence on the Module tab should be:

Number

Module Name

Type

1

CallSapAdapter

Local Enterprise Bean

Sender Agreement Interface to be used in the Sender section: Interface Namespace

ErrorLog http://sap.com/xi/SWIFT

Receiver Determination Interface in the Sender section: Interface

ErrorLog

Namespace

http://sap.com/xi/SWIFT

In the Configured Receivers section, choose the name of your File Adapter business service in the Service column.

16

February 2009

Installation Guide: SAP Integration Package for SWIFT

In the Configuration Overview for Receiver Determination section, do this mapping: Receiver Interface

ErrorLog

Interface Mapping

ErrorToHTML

Interface Determination Under the header Sender, check whether the following information is displayed: Interface ErrorLog Namespace http://sap.com/xi/SWIFT Under the header Receiver, enter the name of your Mail Adapter business service. In the Configured Inbound Interfaces section, the following information should be displayed: a. Inbound Interface Name Namespace

ErrorLog http://sap.com/xi/SWIFT

b. Interface Mapping Name Namespace

ErrorToHtml http://sap.com/xi/SWIFT

Receiver Agreement Under the header Sender, the name of your File Adapter service should be entered.

Under the header Receiver, this interface should be entered: Service

the name of your Mail Adapter service

Interface

ErrorLog

Namespace

http://sap.com/xi/SWIFT

February 2009

17

Installation Guide: SAP Integration Package for SWIFT

4 Examples for the Configuration of the Pay to Reconcile Business Scenarios for FileAct 4.1 Sending Files using FileAct

SAP BCM

This chapter describes how to configure the sending of files to SWIFT via FileAct:

File

File File Adapter

SWIFT input directory

Business Service Add these inbound interfaces to the business service in the Receiver and Sender tab page:

Name

Namespace

Empty

Empty

Communication Channels The Adapter-Specific Message Attributes ‘File Name’ and ‘Directory’ must be flagged.

The Processing Sequence on the Module tab for both communication channels should be:

18

February 2009

Installation Guide: SAP Integration Package for SWIFT

Number

Module Name

Type

1

localejbs/swift/FileActConversion ToSWIFTModule

Local Enterprise Bean

2

CallSapAdapter

Local Enterprise Bean

These parameters are available for the module FileActConversionToSWIFTModule (see Appendix A for explanation): UseLocalSecurity, KeyId.

Sender Agreement Interface to be used for the Sender section: Interface Namespace

SwiftMessage_FTA http://sap.com/xi/SWIFT

Receiver Determination Interface to be used in the Sender section: Interface

SwiftMessage_FTA

Namespace

http://sap.com/xi/SWIFT

In the Configured Receivers section, choose the name of your service in the Service column. In the Configuration Overview for Receiver Determination section, SwiftMessage_FTA should appear as Receiver interface.

Interface Determination Under the header Sender, check whether the following information is displayed: Interface

SwiftMessage_FTA

Namespace

http://sap.com/xi/SWIFT

Under the Configured Inbound Interfaces, this Inbound Interface has to be used: Name Namespace

SwiftMessage_FTA http://sap.com/xi/SWIFT

Receiver Agreement Under the header Receiver, check whether the following information should be displayed:

February 2009

19

Installation Guide: SAP Integration Package for SWIFT

Interface

SwiftMessage_FTA

Namespace

http://sap.com/xi/SWIFT

4.2 Receiving Files using FileAct

SWIFT output directory

File

File File Adapter

SAP BCM

This is the process of receiving files from SWIFT via FileAct:

Business Service Add these inbound interfaces to the business service in the Receiver and Sender tab page:

Name

Namespace

Empty

Empty

Communication Channels The Processing Sequence on the Module tab for both communication channels should be:

20

Number

Module Name

Type

1

CallSapAdapter

Local Enterprise Bean

February 2009

Installation Guide: SAP Integration Package for SWIFT

Sender Agreement Interface to be used in the Sender section: Interface Namespace

SwiftMessage_FTA http://sap.com/xi/SWIFT

Receiver Determination Interface to be used in the Sender section: Interface SwiftMessage_FTA Namespace http://sap.com/xi/SWIFT

In the Configured Receivers section, choose the name of your service in the Service column. In the Configuration Overview for Receiver Determination section, SwiftMessage_FTA should appear as receiver interface.

Interface Determination Under the header Sender, check whether the following information is displayed: Interface Namespace

SwiftMessage_FTA http://sap.com/xi/SWIFT

Under the Configured Inbound Interfaces, this Inbound Interface has to be used: Interface Namespace

SwiftMessage_FTA http://sap.com/xi/SWIFT

Receiver Agreement Under the header Receiver, check whether the following information is displayed: Interface

SwiftMessage_FTA

Namespace

http://sap.com/xi/SWIFT

5 Useful Notes SAP Note Number

Title

1153053 + 1144603 1303428 1304387

Backend signature for data medium .par file is missing in FTP mode Transaction Counter

February 2009

21

Installation Guide: SAP Integration Package for SWIFT

Appendix A UseLocalSecurity This parameter specifies if the HMAC-SHA256 hash value for Local Authentication should be generated based on the value of the parameter KeyId and be added to the header of SWIFT XMLv2 file (FIN) or to the *.par file (FileAct). Possible values: true/ false Default value: true

KeyId Symmetric key used for hash value calculation and maintained via the KeyManager application that is part of the SAP Integration Package for SWIFT. The value must be identical to the concatenated left part and right part key used in SWIFTAlliance for the emission and / or reception profile. You can access the KeyManager application using the link http://:/webdynpro/dispatcher/sap.com/fscm~swiftwda/KeyManager.

Possible values: as specified in KeyManager application Default value: SWIFT

IsNotificationRequested Only applicable to FIN. The corresponding XML-tag in the SWIFT XMLv2 message will be set accordingly, specifying if a Delivery Notification is requested. Possible values: true/ false Default value: true

IsUrgent Only applicable to FIN. The corresponding XML-tag in the SWIFT XMLv2 message will be set accordingly, specifying if an urgent delivery is requested. Possible values: true/ false Default value: true

22

February 2009