For data communication between ERP systems and SAP Claud Multi-Bank Connectivity tenant, SAP first provided the Multi-Bank Connectivity connection. For the purpose of exchanging payment data between regional ABB SAP systems and the central GCM SAP, we will use the MBC connection in this scenario.

Here, we’ll go over the procedures that must be followed in the sending system in order to use the MBC connector to send payments from regional systems to a global GCM. The instructions involve the following actions:

• How to install the local system’s BSNAGT 200 component:

SAP Notes implementation
  • 2949014 – Message Creation API Function Module
  • Maintenance View for RFC-API Settings, version 2969746
  • Configuration Table for RFC-API settings (2969603)
  • Extended Header Parameter: 3077799 numerous creations of the origin
  • Establishing RFC Destinations for the Target System
  • Customizing the MBC connector in relation to the payment programme

Here, we’re going to presume that the local systems’ payment programmes use the Payment Workbench Medium to create payment files.

Step 1:

Installation of the BSNAGT 200 SP 06 add-on component (latest available package on SMP)
software packages from SMP were downloaded to a local PC.

SAP Notes implementation

Prior to reviewing these notes, please confirm that the system has been updated to Version 30 of SAP Note 1668882.

Following which, the following notes might be reviewed and added to the system:

  • 2969746
  • 2949014

We should be able to move forward with the steps noted in the correct status for when they are ready for implementation once the 1668882 notice has been implemented.

To avoid problems while downloading or implementing the note, please make sure that your system has the name space /BSNAGT/ set to changeable.

Since we already implemented it in my case, note 2969747, it appears to be fully completed.

RFC Destination Creation for the Target System

With the assistance of the Basis team, create an RFC connection and assign it to each of the three environments (Dev, QAS, and PRD).

Configuration of FI:

SAP According to the instructions in the manual, the following settings should be kept with SPRO under the node of the Multi-Bank Connectivity Connector.
Table maintenance had to be utilised because the SPRO node lacked the functionality listed below, as illustrated below.

Setting Up and Maintaining Routing Settings

Transfer – SM30


Customer number submitted into the house bank as Sender ID (see Maintaining Sender ID for Payment Medium Workbench)

House Bank BIC – Receiver ID – Message Recipient

Files to be sent must be sent as a certain message type.

Routing – To Be Used Routing Type

Setting Up the RFC API’s Maintain Settings


This viewpoint must be maintained along with the prior one.

The RFC Destination to be used to transmit messages outside of the system is specified by the setting below.

Use origin FIPWM only if the payment programme makes use of PWM.

Use PICKUP as the origin for file pickup.

Keep SSF (Secure Store and Forward) Profile Data current


Enter BSNAGT in the application.

Additional FI configuration is as follows:


Keeping Sender ID for Workbench of Payment Medium

If not already present, a customer number is added to the House Bank database.

Later, the customer number appears as the SenderID field’s content in the MBC monitor.

Exchange FBZP House banks

The following naming pattern is what we advise for customer numbers (Sender ID in MBC connector)

the sending system’s IGAR number, which is 8 characters long.

Code for the country where the business is located: 2 characters

Fixed ID (HR for payroll paym. or AP for AP paym.) – 2 characters

All potential side effects for the XML file content need to be examined if the Customer Number filed was previously empty and will be filled out for the first time.

if the same bank is used for both AP and HR payments, or if the customer number field is currently in use for another purpose and cannot be altered. The sender ID can be changed in the BADI /BSNAGT/BADI MESSAGE FACTORY that comes after. A separate document describes the necessary programming.


Making Payment Medium Formats Configurable (PMW)

OBPM1 transaction

For each Format that is utilised, it must be done.

The following adjustments are required for the MBC connector:

  • Type: Connector for SAP Multibank Connectivity (field behind Electronic Payment Medium)
  • “Message Type” is the external format description in the MBC connector.

Addition of Event Module 21 under “Customer Format Settings.”

Additional code access is necessary, and it may be used to introduce new roles, such as /n/bsnagt/monitor admin with programme /BSNAGT/MONITOR ADMIN.


Feel free to remark, like, or ask a question here.

Enjoy your reading!