1. Multi-Entity Deployment Models
  2. Overview

1 Overview

This topic provides the overview about the various Multi-Entity Deployment models for Oracle Banking Liquidity Management.

Banks may have multiple implementations across geographies that necessitates the need to support multiple entities.

Multi Entity feature, introduced inOracle Banking Microservices Architecture products, enables a single instance of the product (and the underlying Oracle Banking Microservices Architecture platform) to onboard multiple entities of the bank onto the platform.

For Multi-Entity deployment and set up process, refer to the Oracle Banking Multi-Entity Deployment Guide.

Model 1: Multiple Entities

  • In this model, multiple independent entities would be set up across the different entities in which the bank would be operating ex: Entity_1, Entity_2 and Entity_3 entities.
  • Each of these entities would be distinct and independent from each other.
  • Each entity would have its own distinct Common Core, SMS and Oracle Banking Microservices Architecture set ups.
  • Each entity would have its own Liquidity static data\maintenances ex: Frequency codes.
  • Similarly, each of these entities would have its own branches.
  • An entity would be able to view only its own set of branches and account details.
  • In an entity if required other entity details can be captured but only as external banks.
  • Integrations with DDA and Payments engines would be through Oracle Banking Routing Hub.

Model 2: Single Central/Global Liquidity Management Entity

  • In this model, single entity would be set up across the different countries in which the bank would be operating ex: Entity_1, Entity_2 and Entity_3 entities.
  • A Group Entity (not a real entity) code would be set up ex GLM as the node.
  • All the other entities (True Entities) would be added to the node as branches.
  • All these entities would have a single shared Common Core, SMS and Oracle Banking Microservices Architecture set ups.
  • Similarly, all these entities would share the same static data\maintenances.
  • Customers and accounts across all the entities would be present in the same set up.
  • Integrations with DDA and Payments engines would be through Oracle Banking Routing Hub.