Configuration Guide - SAP IP SWIFT

Configuration Guide

SAPIntegrationPackage for SWIFT

Document Version 0.4 February 2009

2 Copyright 2006 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted inany form or for any purpose without the express permission ofSAP AG. The information contained herein may be changedwithout prior notice.

Some software products marketed by SAP AG and itsdistributors contain proprietary software components of othersoftware vendors.

Microsoft, Windows, Outlook, and PowerPoint are registeredtrademarks 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 orregistered trademarks of IBM Corporation in the United Statesand/or other countries.

Oracle is a registered trademark of Oracle Corporation.

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

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

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

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc.,used under license for technology invented and implemented byNetscape.

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 wellas their respective logos are trademarks or registered

trademarks of SAP AG in Germany and in several othercountries all over the world. All other product and service namesmentioned are the trademarks of their respective companies.Data contained in this document serves informational purposesonly. National product specifications may vary.

These materials are subject to change without notice. Thesematerials are provided by SAP AG and its affiliated companies("SAP Group") for informational purposesonly, without representation or warranty of any kind, and SAPGroup shall not be liable for errors or omissions with respect tothe materials. The only warranties for SAP Group products andservices are those that are set forth in the express warrantystatements accompanying such products and services, if any.Nothing herein should be construed as constituting an additionalwarranty.

DisclaimerSome components of this product are based on Java. Anycode change in these components may cause unpredictableand severe malfunctions and is therefore expressivelyprohibited, as is any decompilation of these components.

Any Java Source Code delivered with this product is only tobe used by SAPs Support Services and may not be modified oraltered in any way.

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

SAP AGNeurottstrae 1669190 WalldorfGermanyT +49/18 05/34 34 24F +49/18 05/34 34 20www.sap.com

3Typographic Conventions

Type Style Represents

Example Text Words or characters thatappear on the screen. Theseinclude field names, screentitles, pushbuttons as well asmenu names, paths andoptions.

Cross-references to otherdocumentation

Example text Emphasized words orphrases in body text, titles ofgraphics and tables

EXAMPLE TEXT Names of elements in thesystem. These include reportnames, program names,transaction codes, tablenames, and individual keywords of a programminglanguage, when surroundedby body text, for example,SELECT and INCLUDE.

Example text Screen output. This includesfile and directory names andtheir paths, messages,names of variables andparameters, source code aswell as names of installation,upgrade and database tools.

Example text Exact user entry. These arewords or characters that youenter in the system exactlyas they appear in thedocumentation.

Variable user entry. Pointedbrackets indicate that youreplace these words andcharacters with appropriateentries.

EXAMPLE TEXT Keys on the keyboard, forexample, function keys (suchas F2) or the ENTER key.

Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Installation Guide: SAP Integration Package for SWIFT

4 February 2009

1 Preface ............................................................................................5

2 Using the SAP Integration Package for SWIFT ..........................62.1 Integration Process SWIFTMessageCollection ....................................... 62.2 Creating of Configuration Scenarios........................................................ 6

3 Examples for the Configuration of the Pay to ReconcileBusiness Scenarios for FIN...............................................................7

3.1 Sending SWIFT MT Messages and Using SWIFTMessageCollectionIntegration Process ................................................................................. 7

3.1.1 Configuring of File Adapter.................................................................................... 73.1.2 Configuring of SWIFTMessageCollection Intergration Process .............................. 9

3.2 Receiving SWIFT MT Messages using FIN........................................... 113.3 Receiving Status Messages using FIN.................................................. 133.4 Setting up E-mail Notifications in Error Cases for FIN........................... 15

4 Examples for the Configuration of the Pay to ReconcileBusiness Scenarios for FileAct ......................................................18

4.1 Sending Files using FileAct ................................................................... 184.2 Receiving Files using FileAct ................................................................ 20

5 Useful Notes .................................................................................21

Appendix A........................................................................................22


February 2009 5

1 PrefaceThis document provides a configuration guideline for the SAP Integration Package for SWIFTif used together with SAP Bank Communication Management (former SAP Bank RelationshipManagement) as shipped with SAP Enhancement Package 2 for ERP 6.0.

These installations are possible:

Backend SAP XI / PI SAP IntegrationPackage for SWIFT

SAP Enhancement Package 2for ERP 6.0

SAP XI 7.0 SP13 or higher 602






SAP PI 7.1 SP7 or higher 622





Refer to the corresponding Configuration Guide which covers the configuration aspects forthe 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 InterbankFinancial Telecommunications) refer to http://www.swift.com/.

ConstraintsThe steps described in this configuration guide are all based on the condition that an XI / PI isalready installed.

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

PurposeThis configuration guide describes the steps necessary to successfully configure the SAPIntegration Package for SWIFT.

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


6 February 2009

Intended AudienceAll groups of users involved in the setup of cross-application-component business processesin which messages are exchanged using SAP Exchange Infrastructure and for whichbusiness 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 SAPXI / 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 SWIFTMessageCollectionIf you want use the SWIFTMessageCollection Integration Process you need to import thecorresponding ccBPM Integration Process from the Integration Repository into the IntegrationDirectory of XI / PI.

2.2 Creating of Configuration ScenariosThis procedure describes how to create configuration scenarios in the Integration Directoryof the XI / PI system.

PrerequisiteThe required technical and business systems are available in the SLD. In the integrationdirectory, you assign these systems to specific configuration scenarios.

Procedure...

SAP Integration Package for SWIFT contains modules for a File Adapter. So for eachbusiness scenario, you have to create an appropriate Configuration Scenario in IntegrationDirectory usually using the delivered modules. You need the following:

? directories for file exchange? Configuration Scenario for a File Adapter containing the following objects:


February 2009 7

? Service without Party (Business Service) with Communication Channels(Receiver + Sender) . Please note, that Business Service was renamed toCommunication 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 necessaryobjects are listed. Only special configuration requirements are mentioned. Complete theconfigurations according to your needs. Use File as Adapter Type if it is not explicitlymentioned.

3 Examples for the Configuration of the Pay toReconcile Business Scenarios for FIN

3.1 Sending SWIFT MT Messages and UsingSWIFTMessageCollection Integration Process

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

File Adapter:Sender

Channel

SA

P B

CM

SA

P B

CM

FileSWIFT input

directorySWIFTMessageCollection

Integration Process

File Adapter:ReceiverChannel

File

3.1.1 Configuring of File Adapter

Business ServiceInbound interfaces on the Receiver tab page:


8 February 2009

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 ChannelsThe Processing Sequence on the Module tab for both communication channels:

Number Module Name Type

1 localejbs/swift/FINConversionToSWIFTModule LocalEnterpriseBean

2 localejbs/CallSapAdapter LocalEnterpriseBean

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

Sender AgreementInterface to be used in the Sender section:

Interface SwiftMessageNamespace http://sap.com/xi/SWIFT

Leave the Receiver section empty.

Receiver Determination

Interface to be used in the Sender section:

Interface SwiftMessage


February 2009 9

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

Entries in the Receiver section:

Party *

Service *

In the Configured Receivers section, choose SwiftMessageCollection in the Servicecolumn.

In the Configuration Overview for Receiver Determination section, choose the following:

Receiver Service SwiftMessageCollectionReceiver Interface SwiftMessage

Interface Determination

In the Sender section, the following information should be displayed:


In the Receiver section, the service SwiftMessageCollection has to be entered.

Under the Configured Inbound Interface, the following information should be displayed asInbound Interface:

Name SwiftMessageNamespace http://sap.com/xi/SWIFT

Receiver AgreementIn 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 thefollowing interface:


3.1.2 Configuring of SWIFTMessageCollection IntergrationProcess

Receiver DeterminationEntries for the the Sender section:


10 February 2009

Service SwiftMessageCollection


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

Interface DeterminationEntries for the the Sender section:

Service SwiftMessageCollection


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 SwiftMessageNamespace http://sap.com/xi/SWIFT

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

Service your File Adapter Business ServiceInterface SwiftMessageNamespace http://sap.com/xi/SWIFT

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


February 2009 11

3.2 Receiving SWIFT MT Messages using FINThis chapter describes the configuration of the following process:

File Adapter

SA

P B

CM

SA

P B

CM

FileSWIFT output

directory

File

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

Name Namespace

Empty Empty

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


1 localejbs/swift/FINConversionFromSWIFTModule LocalEnterpriseBean

2 CallSapAdapter LocalEnterpriseBean


12 February 2009

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

Sender Agreement


Interface SwiftMessage_FINNamespace http://sap.com/xi/SWIFT




In the Configured Receivers section, choose the name of your service in the Servicecolumn.

In the Configuration Overview for Receiver Determination section, SwiftMessage_FINshould appear in the Receiver column.

Interface Determination

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


Under the header Receiver, the name of your service should be displayed:

Under the Configured Inbound Interface, check whether the following information isdisplayed. Add the information if it is still missing:

Name SwiftMessage_FINNamespace http://sap.com/xi/SWIFT

Receiver AgreementUnder the header Sender, enter the name of your service.

Under the header Receiver, use the following interface:



February 2009 13

3.3 Receiving Status Messages using FINThis chapter describes the configuration of the following process:

File Adapter

SA

P B

CM

SA

P B

CM

FileSWIFT logdirectory

File

Business ServiceAdd 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:



Sender Agreement


14 February 2009


Interface SwiftMessage_FTANamespace http://sap.com/xi/SWIFT





In the Configuration Overview for Receiver Determination section, SwiftMessage_FTAshould appear in the Receiver column.

Interface DeterminationUnder the header Sender, use this interface:


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

In the Configured Inbound Interfaces section, use this as Inbound Interface:

Name SwiftMessage_FTANamespace http://sap.com/xi/SWIFT

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

Under the header Receiver, this interface should be displayed:



February 2009 15

3.4 Setting up E-mail Notifications in Error Cases forFIN

This chapter describes the configuration of the following process:

File Adapter:Sender

Channel e-mailSWIFT error

directory

File Mail Adapter:ReceiverChannel

Business ServiceAdd 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 ChannelSelect Mail as Adapter Type on the Parameters tab page. The Mail Attribute KeepAttachments should be flagged.

The Processing Sequence on the Module tab should be:


16 February 2009


1 localejbs/AF_Modules/MessageTransformBean LocalEnterpriseBean

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

LocalEnterpriseBean

Use this parameter for the module MessageTransformBean:

Parameter Name Parameter Value

Transform.ContentDisposition inline

Sender Communication ChannelSelect File as Adapter Type on the Parameters tab page. The Processing Sequence on theModule tab should be:




Interface ErrorLogNamespace http://sap.com/xi/SWIFT

Receiver DeterminationInterface in the Sender section:

Interface ErrorLogNamespace http://sap.com/xi/SWIFT

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


February 2009 17

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

Receiver Interface ErrorLogInterface Mapping ErrorToHTML

Interface DeterminationUnder the header Sender, check whether the following information is displayed:Interface ErrorLogNamespace 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 ErrorLogNamespace http://sap.com/xi/SWIFT

b. Interface Mapping

Name ErrorToHtmlNamespace http://sap.com/xi/SWIFT

Receiver AgreementUnder 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 serviceInterface ErrorLogNamespace http://sap.com/xi/SWIFT


18 February 2009

4 Examples for the Configuration of the Pay toReconcile Business Scenarios for FileAct

4.1 Sending Files using FileActThis chapter describes how to configure the sending of files to SWIFT via FileAct:

File Adapter

SA

P B

CM

SA

P B

CM

FileSWIFT input

directory

File


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:


February 2009 19


1 localejbs/swift/FileActConversionToSWIFTModule

Local Enterprise Bean

2 CallSapAdapter Local Enterprise Bean

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

Sender AgreementInterface to be used for the Sender section:


Receiver DeterminationInterface to be used in the Sender section:



In the Configuration Overview for Receiver Determination section, SwiftMessage_FTAshould appear as Receiver interface.

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


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

Name SwiftMessage_FTANamespace http://sap.com/xi/SWIFT

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


20 February 2009


4.2 Receiving Files using FileActThis is the process of receiving files from SWIFT via FileAct:

SWIFToutput

directoryFile Adapter

SA

P B

CM

SA

P B

CM

File File


Name Namespace

Empty Empty

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




February 2009 21



Receiver DeterminationInterface to be used in the Sender section:



In the Configuration Overview for Receiver Determination section, SwiftMessage_FTAshould appear as receiver interface.

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


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


Receiver AgreementUnder the header Receiver, check whether the following information is displayed:


5 Useful Notes

SAP Note Number Title1153053 + 1144603 Backend signature for data medium1303428 .par file is missing in FTP mode1304387 Transaction Counter


22 February 2009

Appendix AUseLocalSecurityThis parameter specifies if the HMAC-SHA256 hash value for Local Authentication should begenerated based on the value of the parameter KeyId and be added to the header of SWIFTXMLv2 file (FIN) or to the *.par file (FileAct).

Possible values: true/ falseDefault value: true

KeyIdSymmetric key used for hash value calculation and maintained via the KeyManagerapplication that is part of the SAP Integration Package for SWIFT. The value must beidentical to the concatenated left part and right part key used in SWIFTAlliance for theemission 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 applicationDefault value: SWIFT

IsNotificationRequestedOnly applicable to FIN. The corresponding XML-tag in the SWIFT XMLv2 messagewill be set accordingly, specifying if a Delivery Notification is requested.


IsUrgentOnly applicable to FIN. The corresponding XML-tag in the SWIFT XMLv2 messagewill be set accordingly, specifying if an urgent delivery is requested.


Documents

Configuration Guide - SAP IP SWIFT