Document Objective

Figure 1: Advantages and flow using BCM

• FIN (Financial Institution Transfer) – International Cross- Border Payments

• FTA (Federal Tax Application) – Domestic Payment within Country

Figure 2: Folder location for FIN(fin) and FTA(fileact) Payments in AL11

BCM & SwiftNet Integration with SAP PI

Figure 6: Flow diagram of Integration of SAP PI with BCM and SwiftNet

Figure 8: SFTP Module Deployed in ESR

All the files created in AL11 folder of ECC system will contain a signature. The verification of the signature is done in PI system using the Module Key and parameter from SWIFT Module.

In order to show the Encrypted and signed file we have taken the below screen as there are no files currently in fileAct folder in ECC system.

Figure 9: Encrypted and signed file

Configuration in Integration Directory for Payments

We have used different channels for different Banks. This makes easy for supporting testing for Banks whenever required. Channels for the banks which are not in scope for testing will be switched off.

The signature is verified using the parameter “VerifyBackendSignature” available in the SWIFT Module as under:

Figure 10: Module Parameters used for integration with ECC

• IsNotificationRequested – This parameter is marked ‘true’ to receive Notifications from Bank for the payments done.
• IsUrgent – The parameter is marked ‘false’ inorder to avoid the urgency.
• KeyId – This is the unique Key Id for every system integrated with SwiftNet in the Landscape. The value format is SWIFT_<SID>. SID – System ID of Development/Test/Production system
• UseLocalSecurity – Messages are securely and reliably exchanged between banks and other financial institutions
• VerifyBackendSignature – All incoming files from ECC will be checked if they are signed by BCM module. The unsinged files will not be processed and the channel will show error message in PI system.
• Exit is the standard module for in SFTP

• Msecs to Wait Before Modification
  Check where PI waits some time from first finding the file, until reading and processing it later, and the file is only processed if it had not changed over
  the waiting period. As shown below PI waits 10 minutes until the file is complete
• Masking – Suppose we want to process all files that have the extension ‘.nfs’, but want to exclude all files that begin with the letter ‘GB2’. To do this follow the below:

Figure 11: Channel configuration for polling payment files

Additionally mention the connection parameters like host name of the sending server, port, UserId and Password for Authentication. The UserId and Password should be maintained at the server Level and should not be a Dialog/System User.

We place the processed files in Archive folders in ECC system.

Receiver Channel Configuration:

The receiver channel will contain the Third Party information. We have used PGP (Pretty Good Privacy) Encryption also happens when the payment are sent from PI system

Figure 12: Encryption at Target

• armor – If the protocol (or) transmission channel supports only ASCII printable characters, the data to be transferred should be encoded as plain text. This is referred as binary to text encoding. If it is applied on the plain text itself, and decoded on the receiver end is called “ASCII Armoring”. To turn on the value we input is “true”.
• encryptionAlgorithm – In cryptography, Triple DES is the common name for the Triple Data Encryption Algorithm (TDEA or Triple DEA) block cipher, which applies the Data Encryption Standard (DES) cipher algorithm three times to each data block.
• publicKeyRing
  – The public key is used to code a digital message in order to make it unreadable without the use of a private key, which typically takes the form of
  a password.
• recipient – Target mail recipient ID.

Standard mappings are used for FIN and FTA payments as shown in below
figure:

Figure 13: Mapping for FTA Payments

Figure 14: Message Processing in PI

Figure 15: Mapping for FIN Payments

Bank Statements and Notifications from Banks/ Third Party System

As soon as the payment reaches the third Party system, that connects with different Banks, a technical acknowledgement is send back to PI system notifying the receipt of payments. These feedbacks files are sent by the Third Party for FTA and FIN Payments. In addition to these feedbacks, Banks sends a payment status notification PAIN back to SAP PI system after receiving the payment. The payment Status are sent to ECC system using Proxy and the status are changed accordingly in transaction BNK_MONI. We also receive notifications from Bank for FIN and FTA payments. These notifications have two different formats, namely TXT and XML file format. This will be discussed in next section.

Payment & Bank Statement Notifications

• The acknowledgement is received from Third Party system when a FIN payment is received at Third Party. There is not encryption done for the  acknowledgement process.
• The mappings used are from the standard Operation mapping SwiftFIN_PaymentStatus and SwiftFTA_PaymentStatus from the SWIFT Module. (Refer Figure: 7)

• The Acknowledgement sent by Bank to PI is in a different format and the same we refer as PAIN.
• No encryption or check done.
• The format for the file sent is a report which can be found in Software Component Version ISO20022 1.0 in namespace http://sap.com/xi/ISO20022
  and report name as PaymentStatusReportV02.
• This report is mapped to CollectivePaymentOrderNotificationMessage that is a structure from SAP APPL 6.04 in namespace http://sap.com/xi/APPL/Global2 .

Bank Statement Notifications

1. The file is send to AL11 directory directly to keep a track of the Banks statements
2. A service message is sent to ECC using SOAP.

XML Bank Statement Notification for FTA payments:

Issues and Resolution

• Duplicate payments are not processed at Third Party end that nullifies the risk.

• The version of the SFTP adapter had a bug of routing the payments to incorrect channels leading to inconsistencies and escalations. A new version
  was deployed that solved the issue.

• The Public Key for validating and handshake mechanism should be deployed at the server level in PI system. This Key is provided by Third Party.

• Due to network issues between SAP PI and Third Party or Third Party and Bank, the status get incorrectly assigned in BNK_MONI. For eg: Accepted By Bank is sent before Received By Bank. Network checks required to be done during connectivity tests to ensure there are no delay

• Lower TCO by becoming independent from proprietary payment standards and bank-specific e-banking products and setting up a single communication
  channel to SWIFTNet, which will enable your company to communicate with all the banking partners through this one channel.
• Minimize bank connections and enhance straight-through processing rates via end-to-end integration with SWIFTNet
• Full implementation of SAP Bank Communication Management application and SAP Integration Package for SWIFT is a SAP Ramp-Up program in less than 6 months