Skip to Content

Westpac Connector Solution was developed by SAP in collaboration with Westpac (WIB). This solution utilizes SAP PI to transfer/receive vendor payment files and bank statements between Client’s SAP system and Westpac. This document outlines the configuration steps required to implement the solution when SAP is on Hana Enterprise Cloud Platform (Sybase Database).

Prerequisites

  • Vendor and GL master data set up to run Payment Program.
  • Payment Run Configuration with Payment Methods (Westpac Bank Transfer & Westpac Cheque).
  • Payment Medium Workbench Configuration for DMEE File – Westpac requires the payment files in XML format (CGI ISO20022 Pain.001) and send the payment acknowledgement messages in Pain.002 format and bank statements in CAMT053 format.
  • SAP PI Connectivity(Web Services) with Westpac WIBS system(Westpac Integrated Banking Service).

Configuration Steps

  • Operating System Command – On SAP HEC environment SAP servers will be on Linux Operating System. The Operating System Command has to be updated using transaction code SM69.

SAP Menu Path: SAP Menu –> Tools –> CCMS –> Configuration –> Display/Change External           Commands

If your SAP Servers are on Windows Operating System, we need to update respective entry               for Windows Operating System.

  •  Installation of PGP application on Linux Operation System – This task has to be performed by SAP HEC support/project team.

Below directories have to be created at OS level and replicated in AL11(by SAP BASIS).

/usr/sap/<SID>/pgpenc/in

/usr/sap/<SID>/pgpenc/out

/usr/sap/<SID>/pgpdec/in

/usr/sap/<SID>/pgpdec/out

/usr/sap/<SID>/PGP_<SID>

755 access rights must be provided to the above directories. PGP Software has to be                          installed on all application servers.

We need to get the Public Key from Westpac Qvalent team and share it with SAP HEC team.            In turn, SAP shares the public key and it has to be sent to Westpac Qvalent Team.

 

  • Update the parameter values in /CBCOM/T_CONFIG Table with Linux OS Paths.

SPRO –> IMG –> Financial Supply Chain Management –> Corporate Connectivity for                        Westpac –> Corporate Technical Configurations –> Maintain Technical Configurations                        (Inbound, Outbound and Encryption).

 

 

Change the parameter value for DOWNLOAD_XML_INB to represent actual system ID instead of <SYSID> — Decryption Scenario

The Encryption and Decryption files(Pgpencrypt.sh & Pgpdecrypt.sh) have to be modified to adapt to our scenario.

  • Implement OSS Message Implement OSS Message 1936892 to download the Outbound Payment File in .XML Format.

 

  • Implement an implicit enhancement to replace the SYSID with SAP system ID(Encryption Scenario) in Function Module /CBCOM/FM_FILE_VALIDATE_NAME.

Monitoring the Payment Files and Status:

After the Payment Run is executed, you can check the status of the payment files in Cockpit Transaction (/CBCOM/MSG_COCKPIT – Payment Message Cockpit).

Click on Display XML File in the above screen

For each Payment File, Westpac sends three acknowledgement messages (PAIN.0002). These messages tells us whether the payment file processed successfully or not at Westpac side.

If Payment is Successful, the Payment Inf Status is updated as shown in the below screen shot.

If Payment is rejected, the Payment Inf Status is updated as shown in the below screen shot.

On Further drill down, we can view the actual rejection reason

 

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply