3398869 - FAQs about SAP MBC for S/4HANA Public Cloud Customers

You have question about SAP Multi bank connectivity (SAP MBC)

1. What is SAP MBC?
2. Is really I need SAP Multi-Bank connectivity for my organization?
3. I want to use SWIFT via SAP MBC is it possible?
4. Is there any operation model available for SAP MBC Setup?
5. How SAP MBC will be integrated within your landscape?
6. I work for a bank and my organization want to join SAP Multi-Bank Connectivity as a member bank. Is this possible?
7. How SAP Multi-Bank connectivity get integrated in different SAP solutions?
8. How can I request for SAP MBC setup in SAP S/4 HANA Public cloud?
9. How Can I reach out to SAP in case any outage happens?

SAP Business Technology Platform

1. What is SAP MBC?
   

   SAP Multi bank connectivity is a sap business technology platform (BTP) solution managed by SAP to provide customers connectivity with their banks.

   It is based on integration services deployed in the SAP Cloud that enables the integration of business process spanning different departments, organization or companies. The onboarding to this solution is straight forward and delivered through a private cloud owner and managed by SAP that is secure and partitioned by each customer and their network bank.

   With the help of Multi Bank Connectivity setup your organization can connect to different financial service institutions (FSI’s). As SAP MBC is closely integrated with your SAP ERP system it can seamlessly update various other modules in your SAP system once the messages are available from the bank.

2. Is really I need SAP Multi-Bank connectivity for my organization?
   

   If your organization has a large-scale business and on day-to-day basis you must connect with different financial service institution it become very difficult to handle all these critical financial transactions and updating these transactions into different modules of ERP system is a tremendous task. Due to which sometimes if the transactions are not handled properly it result in financial loss.

   But with the help MBC setup you can connect with your FSI’s and make sure that the financial transactions are safely handled and updated in the ERP system. SAP Multi Bank connectivity provides measurable improvements to the account payable and accounts receivable functions through automation of all the manual and error-prone steps associated with the execution and reconciliation of payments, order-to cash application and order entity documents.

   Also, SAP MBC result in improved control, efficiency, and transparency of the financial accounting process. It automatically updates payment status and cash position in ERP system once updates are available from the banks.

3. I want to use SWIFT via SAP MBC, is it possible?
   

   Yes, it is possible to use SWIFT (Society for Worldwide Interbank Financial Telecommunications) via SAP Multi-Bank Connectivity. SAP MBC seamlessly integrates into the SWIFT network, which allow sap customers to leverage the bank reach that SWIFT network provides.

   If your organization want to connect SWIFT network from SAP, you must have membership to SWIFT such as SWIFT Alliance 2. SAP is not a reseller of swift so corporates must subscribe separately to swift to get their BIC code or ask for migration of their existing BIC and sign an agreement to cover messages passed via SWIFT.

   To establish the connection with swift, SAP operates SWIFT software’s, SWIFT-Specific hardware, and dedicated internet connections to swift. SAP MBC and the connector for SAP Multi-Bank connectivity use this setup for the connection between the corporate customer and their banks. In addition, SWIFT Parameters are added via configuration in the connector for SAP Multi-Bank connectivity. These parameters are passed as additional attributes with the message to SAP Multi Bank connectivity.

   On the inbound side from the SWIFT network to a corporate customer. SAP MBC receives the message from the SWIFT network. After validating the message signature. SAP MBC forwards these messages without SWIFT specific XML envelope to the connector for SAP MBC in the respective SAP ERP system. Acknowledgement and delivery notification are mapped to an ISO 2022 PAIN.002 format before they get forwarded to ERP system for automated processing.

   Acknowledgement are pushed to SAP Bank communication management module where reporting on payment batches and corresponding status messages are available.
    
   
4. Is there any operation/lifecycle model available for SAP MBC?
   
   Please find the details of the different activity and responsible entity.
   
   

   Activity	Description	Responsible
   Communication Management	Appoint an English-Speaking contact person and communicate name to SAP	Customer
   Asset Management	Management of the hardware and infrastructure resources from acquisition and disposal	SAP
   Provisioning	Provisioning of the resources and systems to customer	SAP
   Integration Content development	Proper testing of the integration content under realistic condition before it’s productive usage	SAP & Customer
   Security Material Management	Proper testing of the security material under realistic condition before it’s productive usage	SAP & Customer
   Message content	Create message format and content, which includes ensuring the accuracy and completeness of such message content	Customer
   Message Transmission	Transmit messages correctly according to the constraints offered by the application	SAP
   Change management	Apply regular improvements as well as corrections to the applications and infrastructure to avoid incidents with minimal possible disruption of normal operations. Perform upgrades of the applications and infrastructure Consume the latest version of the infrastructure. Prompt delivery of patches for security vulnerabilities in the OS and DB hosting the application	SAP
   Change Management	Collaborate with SAP to ensure timely processing of change requests affecting the resources in the customer account	Customer
   Incident management	Process incident reported by the customer according to the service level agreement.	SAP
   Incident management	In the event of incident make reasonable effort to support end users and manage their incidents, to explore self-help tools to find already documented solution. Also confirm incident & service requests resolution in the incident tracking system.	Customer
   Service Requests	Process service requests reported by customer according to the service level agreement	SAP
   Backup & restore	Perform a backup of the database systems hosted in the customer account. Restore previously backed up data to recover to a consistent state. Give regular update to the customer throughout the complete restore procedure.	SAP
   Backup & restore	Collaborate with SAP to ensure timely processing of data restore if required. Validate consistency of the restored data	Customer
   User Access Management	Grant the Admin role for the customer account to the user nominated by the customer. Manage the SAP MBC team-specific users, permissions, and security configuration within the customer account	SAP
   User Access Management	Provide a proper user to SAP to which account administrator role for the customer account is to be granted by sap. Grant the administrator role for the customer account to the user nominated by SAP MBC (security officer)	Customer
   System Monitoring	Ensure the availability of the customer system according to the service level agreement. Monitor the resource consumption	SAP
   Malware Management	Ensure that the infrastructure and platform are free of virus, spam, spyware, and other malicious software	SAP
   Application Management	Design, develop, deploy, configure, maintain, and operate the application within the customer account. Provide infrastructure, tools and APIs for the lifecycle management and operations	SAP
   Network Management	Mange the network isolation of the accounts Operate the network infrastructure. Create and manage own web domain for the application	SAP
   Penetration Testing	Inform SAP about any penetration testing that shall be performed for the customer system and ask their approval	Customer
   Decommissioning	Ensure the secure deletion of data and/or hardware disposal	SAP
   Decommissioning	Request a final export of customer data from the application within the time state in terms & conditions. Perform a final export of the customer data from the service using the provided data export self-services.	Customer

   
   
   
5. How SAP MBC will be integrated within your landscape?
   

   During the SAP MBC integration there are three different tenants take part first the SAP S/4HANA Cloud Public Edition that is present on the customer side second the MBC tenant and third Bank tenant. MBC tenant will sit between the customer and bank tenants, and it will help in the sharing of the transactions related information.

   Generally Multi-Bank connectivity setup will be performed on the test and production environment in the case of 2-SL system and in case of 3-SL systems it is setup on development and production system. Test tenants of the customer and bank are integrated with the help of test MBC tenant and production tenants are integrated using the production MBC tenant. Both the test and production tenants are kept isolated from each other.

   While performing the initial configuration, scop item 16R will be activated in the respective SAP S/4HANA Cloud Public Edition system [test/prod system according to the request] in which the SAP MBC setup needs to be performed and then MBC tenants will be assigned according to the nature of your tenants is it test or prod. Once the scop item is activated and MBC tenant is assigned then different RFC destinations will be created (SAP_COM_1002) for connectivity between the MBC tenant and ERP system.

   After creation of the destinations certificate exchange will happen between the MBC tenant and the ERP system. Once all this is done there are some tests that needs to be performed like RFC destination connection test and ping test.  All the tests should be successful only after that the system will be hand overed to the customer.
   

   /BSNAGT/MESSAGE_PULL job will be running in your S/4 system every 10 minutes which checks if the connectivity is fine between theS/4 HANA Public Cloud tenant and the MBC tenant.

6. I work for a bank and my organization want to join SAP Multi-Bank Connectivity as a member bank. Is this possible?
   

   Yes, it is possible, bank can opt to join SAP Multi-Bank Connectivity as a member which will make the integration process of connecting to the corporates using SAP MBC less complicated. For this the banks need to join the Member Banks network provide by SAP for this purpose.

   Banks will be provided with one test and one production tenant in the SAP Multi-Bank connectivity network much like corporate customer.

   It provides multiple benefits such as:

   • Easier onboarding
   • Dedicated bank support
   • Reduced effort.
   • Faster kick off to go-live by utilizing a pre-configured connection to the bank.

   If a member bank is on the list of banks the customer would like to onboard, the member bank onboarding is the default connection method.

   SAP always recommend prioritizing member banks for go-live to obtain value from SAP MBC as quick as possible.
   
   Member can connect to SAP MBC in below mentioned ways:

   1. SFTP (Secure File Transfer protocol):
       For most banks that can support it, SAP recommends bank hosted SFTP connectivity for message exchange as it provides simple and effective scalability options. It also            provides file access, file transfer, and file management over any reliable data stream.
   
   2. API (Application programming interface):
       SAP MBC also offers the possibility to enable a digital connection using banking API. After the banks specification have been verified to meet the technical standards of the        product. SAP Multi-Bank connectivity adheres to the APIs provided by the member bank.
   
   
   

7. How SAP Multi-Bank connectivity get integrated in different SAP solutions?
   

   There are different deployment options available according to the solutions provided by SAP. The Connector for SAP Multi-Bank Connectivity is designed to interact with the cloud services to standardize the integration and it is independent of the technical connectivity from ERP to SAP MBC.

   Also, The Configuration of the connector for SAP MBC is not part of the onboarding service but customer can follow the configuration guide to connect to the cloud service.

   SAP System Type	Connector	Ownership	Notes
   SAP S/4HANA Cloud Public Edition	Activation	SAP	Customer only needs to log a ticket to activate the respective scop item
   SAP S/4HANA Cloud Public Edition Private Edition	Configuration	Customer/Partner	Connector is available and only configuration is required
   SAP S/4 HANA	Configuration	Customer/Partner	Connector is available and only configuration is required
   SAP ECC 6.0	Installation	Customer/Partner	Installation is required

8. How can I request for SAP MBC setup in SAP S/4 HANA Public cloud?
   

   You can create support ticket for “XX-S4C-OPR-SRV” with below mentioned subject lines:

   “SAP_COM_1002 Configuration”

   “Activation of Scop Item 16R”

   “SAP Multi-Bank Connectivity setup”

   It will take around 24-48 Hrs to complete the configuration. In case you have further question to how to log ticket to SAP please refer SAP KBA 1296527 or you can reach out to your CEE/CSM.

9. How Can I reach out to SAP in case any outage happens?
   

   In case if you are facing any software issues in the application, a platform problem, or any other service disruption with respect to SAP Multi-Bank Connectivity. You can create incidents in SAP for Me.

   To create an incident in SAP for Me please use component “LOD-FSN-INT” and team will reach out to you with the solution in the give service level agreement.

   You can use below mentioned components in case of incident related to SAP MBC:

   Component	Use in case of
   LOD-FSN-SUP	Productive Issue
   XX-SER-SAPSMP-SUP	S-USER issue or issues related to get cloud alert notifications
   LOD-FSN-REQ	To initiate the onboarding process of adding banks
   LOD-FSN-INT	Non-Productive Issues
   LOD-FSN-AGT	Issues with the connector for SAP MBC
   LOD-FSN-CER	Certificate related issues

Payments and Bank Communications

Connector for SAP Multi-Bank Connectivity

Connector for SAP Multi-Bank Connectivity, MBC , KBA , XX-S4C-OPR-SRV , S/4HANA Cloud service requests , LOD-FSN-AGT , Connector for SAP Multi-Bank Connectivity , LOD-FSN-CER , SAP Multi Bank Connectivity Certificates exchange , LOD-FSN-INT , Integration for SAP Multi-Bank Connectivity , LOD-FSN-REQ , Onboarding Request for SAP Multi-Bank Connectivity , LOD-FSN-SUP , SAP Multi-Bank Connectivity Support , XX-SER-SAPSMP-SUP , Support Applications , How To