SAP Multi-Bank Connectivity solution - ConVista Asia India
asiaconvista.blogspot.com/2022/09/sap-multi-bank-connectivity-solution.html
SAP Multi-Bank connectivity is a cloud-based arrangement that offers a multi-bank digital channel among SAP and banks. The MBC arrangement has installed Quick availability MBC has incorporated several measures of security.
The outline of Multi-Bank Connectivity and its combination with other sub-modules in SAP alongside the design arrangement required. The focal point of this blog is to comprehend what changes are acquired by MBC administrations presented by SAP. We will begin by figuring out the idea of SAP Multi-Bank Availability (to be perused as MBC in this archive), its scene, and its benefits.
Who can use SAP MBC?
SAP customers ON ECC (assuming that on ECC it should be SAP ERP 6.0 or EHP 0 or higher)
SAP customers on S/4 HANA Cloud
SAP customers on S/4 Hana on-premise release
What changes with SAP MBC?
customers associate with banks on a consistent schedule. Different records are shipped off and gotten from the bank. Correspondence with banks has expanded radically in the present time. Organizations these days anticipate secure and ongoing correspondence with banks. To have effective correspondence with the bank, laying out an association with the bank is required.
Communication with banks was going on even without SAP MBC being set up. In any case, with the presentation of SAP MBC, correspondence with banks has become exceptionally helpful and financially savvy. The following are a few pointers on when SAP MBC solution.
Before MBC
Host-to-host connection for each bank
Without a connection to the bank, users need to login into the bank portal and download files manually
Difficult/expensive to change business to another bank once a host-to-host connection is established
Increase in operational cost to maintain connections with multiple banks
SAP MBC message types:
After MBC No host-to-host connection required
Real-time responses and data updates since MBC is closely integrated with BCM
No more a challenge Cost-effective solution
The following are the sorts of documents that are moved to and from the bank on a consistent schedule in an overall business situation:
Active installment documents
Approaching installment affirmation document (PSR)
Approaching bank articulation
Approaching lockbox documents
Approaching and active exchange affirmation documents
Bank charge examination report
Formats supported by MBC:
1. Payment file formats
PAIN.001
PAIN.002
2. Bank statements/lockbox
CAMT.53
CAMT.52 CAMT.54 MT940 MT942 BAI/BAI2
3. TRM inbound/outbound document designs:
MT300 MT320
SAP MBC can connect to the bank in the following different ways securely: Quick network (client is a Quick client)
Direct bank availability
Availability utilizing client oversaw arrangement e.g., in-house banking arrangement Network to a non-part bank or outsider supplier like EBICS (client is an individual from EBICS)
Note:
SAP will interface clients to their banks regardless of the participation status of the bank
EBICS: Electronic Financial Web Correspondence Standard.
SAP accomplices with Quick
A Quick specialist co-op is not generally required for SAP clients to send messages through the Quick organization. With this organization, the Quick layer to coordinate with the Quick organization is implanted in SAP MBC. Accordingly, clients can use the bank to arrive at what the Quick organization gives.
Note: A sap client expected to associate with the quick organization should be an individual from Quick. Nonetheless, the main change here is Quick participation is required yet Quick administrations are currently being given by SAP which guarantees consistent coordination with different modules and ongoing correspondence with banks
MBC mix with different modules
Bank information documents are created from SAP back-end frameworks and are not a piece of SAP MBC. SAP MBC is firmly coordinated with a few modules that process/consume the information from records. SAP MBC is firmly coordinated with Settlement ahead of time the board which is an installment processing plant (made sense of in my next blog) and BCM-which is liable for clumping and refreshing PSRs was given message types.
SAP MBC security
SAP MBC gives a start to finish security highlights for SSF (Secure Store and Forward)
The following is the rundown of correspondence conventions upheld by SAP MBC: SFTP HTTPS AS2 Cleanser EBICS Quick
Clients can pick encryption/decoding and marks relying upon prerequisites.
Member bank services
As depicted above SAP is presently a Quick accomplice consequently guaranteeing consistent correspondence with banks and incorporation with other sub-modules. Banks, if decide to become part of keeps money with SAP, can give extra advantages to their clients through SAP MBC since it is coordinated with different modules like in-house banking, BCM, TRM, Settlement ahead of time the board, and substantially more.
MBC Landscape
SAP MBC has an extremely straightforward scene. The client can be on any framework ECC or S/4 HANA Cloud or S/4 HANA On-premise. It is feasible to associate with MBC.
SAP's Multi bank network has a connector. MBC connector is on SAP's client framework. SAP MBC connector interfaces with the SAP MBC application. All messages to and from SAP MBC will go through the MBC connector.
A message checking application is accessible at the MBC connector-clients can utilize the Oversee Bank messages application or connector screen application.
For every client who is interfacing with SAP MBC, an occupant is made which addresses the assets of a cloud-based stage. Likewise, for every client with SAP MBC separate got assets are allotted to the cloud stage (memory, central processor, and record framework)
these assets are alluded to as occupants.
Enrollment and availability are not open to public
Advanced marks and encryption of information guarantee uprightness and validation
Each organization member has a one-of-a-kind inhabitant; meaning, each client on SAP MBC has a remarkable occupant guaranteeing the trustworthiness of information
Each occupant has separate data set scenes
Separate incorporation information stream for each inhabitant
The messages are passed from the client to the bank utilizing the MBC network. Every client on MBC has an inhabitant who goes about as beneficiary and source occupant for messages given the message type. The client occupant goes about as a shipper occupant when a message is going out from the client's SAP framework and the bank occupant goes about as a collector inhabitant as well as the other way around in the event of approaching messages from the bank to the SAP framework. Information detachment is accomplished by parting the message among shipper and collector occupants.
Beneath outline shows information is handled independently by separate inhabitants: Clients have the choice to add encryption and a computerized signature for this correspondence way
Setup
MBC Connector:
MBC connector gives a recording interface that gives a coherent document way Intelligent document way definitions should be characterized by utilizing code Records. Arrangement for MBC connector is same for S/4 Hana cloud broadened release, S/4 Hana on-reason or ECC.
Source and beneficiary ID arrangement
Source and beneficiary IDs are utilized for directing messages to and for in SAP MBC. These source and collector IDs are settled upon by the client and bank from start. The source id is kept up at the house bank level.
Way: Monetary Bookkeeping → Bank Bookkeeping → Financial balances → Characterize House Banks
Exchange Code: FI12
Shipper id is a corporate identifier that is pre-concurred by the bank and client and is kept up with as a client number at the house bank level.
The collector id is Quick/BIC of the beneficiary bank. This is gotten from bank ace information if there should arise an occurrence of installments. BIC code in recipient ID is kept up with at the house bank level. Custom recipient IDs can be kept up with under the MBC connector → Keep up with custom shipper/collector ID. This setup will abrogate the default collector ID of the BIC code.
PMW setup while utilizing SAP MBC
The design stands great assuming that the client is on SAP S/4 HANA Cloud 1909/expanded or above.
Bank handling arrangement is done freely by SAP MBC. Select SAP MBC connector in exchange code OBPM1 while making DME structure for installment documents. Bank EBS handling of installment documents is an independent structure MBC.
Quick Boundaries setup:
Quick record ack contains control data that deals with the trading of messages. This data is included in the header to Quick. Quick boundaries are designed utilizing the setup settings and a similar will be shipped off SAP MBC with each message.
Set Quick boundary setting in modifying that is utilized in the header of Quick message, this design depends on recipient ID and message type.
Following Quick boundaries can be set:
Ack Pointer
Ack Solicitation Type
Document Portrayal
Document Data
Non-Disavowal
Need
Recipient BIC
Demand Ref Demand Type Responder
Source BIC