Wed. Feb 26th, 2020

E-Payment: A Customized Solution other than SAP Integration Package SWIFT – Part -3

3 min read

This blog is continuation of

E-Payment: A Customized Solution other than SAP Integration Package SWIFT – Part -1

E-Payment: A Customized Solution other than SAP Integration Package SWIFT – Part -2

Payment run will generate files in ECC and those files will be picked up by SAP PI. SAP PI will merge incoming files into one and then it will encrypt the file. Later, PI will fetch encrypted file to send it to bank network.

After this, bank will process the encrypted merge files and it will send the handshake and transactional files to banks out put folder to be fetched by customer. Let’s say, Handshake file as Acknowledgement files and Transactional files as Response files.

Once Acknowledgement and response files are placed on Bank’s output folder, Customer will send dummy file to execute the event set on the folders to receive Acknowledgement and Response files. The whole process will look like below diagram.


Scenario 3: Customer will send dummy files to receive Acknowledgement and Response files from Bank network and then other PI scenario will post decrypted files to SAP BCM.

SAP PI Developments

 Development for Receiving Acknowledgement and Response files

 ESR Configuration

This scenario doesn’t require any configuration in PI ESR.

ID Configuration

In Integration Directory, We need to create 3 Communication Channel of below types.

Sender:  File Adapter – To send Dummy Files.

Receiver: Http Receiver – Http receiver will be used to receive the files coming from bank network due to the service executed.)

Receiver: File Adapter -Once files are received using http receiver, we have to place it in some location for further processing.

Next step is to create one Sender agreement for Sender file adapter and one Receiver agreement for Http Receiver. We needn’t create receiver agreement for receiver File Adapter.

Next create 1 Receiver Determination and one Interface Determination.

Have a look into Communication channel for clear understanding.

Sender Communication Channel


Now go to Module tab of Sender File Adapter.


Here in the module tab, we are using standard modules for sending the incoming message to the target location after received by HTTP adapter. These settings in sender File adapter enable it to pass incoming message to next Communication channel without using BPM in ESR.

Next step is to Decrypt incoming data and send it to SAP BCM using SAP PI.

ESR Developments

First Import Source XSD and create one Service Interface of Outbound Asynchronous. For Target structure we will use standard SAP APPL 6.04 Service Interface CollectPaymentOrderNotification_In.

Create Message Mapping and map the fields as per your requirement.


Create Operation Mapping As below,


Integration Directory Configuration:

Create 1 sender communication channel, which will call OS Script for decrypting the incoming message before processing, 1 receiver Channel of type XI Proxy. Create one Sender and Receiver agreement for both channels. Create one Receiver Determination and Interface determination.

Activate all settings.

This is done with configuration of receiving side. The CollectPaymentOrderNotification service interface will update SAP BCM with the status of the payments sent by customer to Bank.

We can see status messages in Bnk_Moni Transaction in SAP ECC.

1 thought on “E-Payment: A Customized Solution other than SAP Integration Package SWIFT – Part -3

Leave a Reply

Your email address will not be published. Required fields are marked *