# US 11,907,252 B2 · On-demand cross data center data replication for multi-cloud software applications > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 11,907,252 B2 - Document ID: US11907252B2 - Status: Granted - Kind: B2 - Application number: 17/541,739 - Filed: 2021-12-03 - Published: 2023-06-08 - Granted: 2024-02-20 - Earliest claimed: 2021-12-03 - Assignees: Sap SE - Applicants: Sap SE - Inventors: Tanmoy Pal; Rajesh Hegde - Web page: https://patentgrep.com/patent/US11907252B2 ## CPC - G06F 16/27: Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor - G06F 16/2358: {Change logging, detection, and notification (replication G06F16/27)} - G06F 16/256: {in federated or virtual databases} - G06F 21/604: {Tools and structures for managing or administering access control systems} - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract A method may include detecting one or more trigger events at a first data center hosting a software application having a first customer onboarded at the first data center but not a second data center also hosting the software application. In response to the trigger events, a first data associated with the first customer may be replicated at the second data center to enable a collaboration between the first customer and a second customer of the software application onboarded at the second data center but not the first data center. One or more data replication relevant settings may be applied to prevent a second data associated with the first customer from being replicated at the second data center. Furthermore, the data replication relevant settings may be applied to prevent the first data from being replicated at a third data center. Related systems and computer program products are also provided. ## Claims ### Claim 1 A system, comprising: at least one processor; and at least one memory comprising program code which when executed by the at least one processor provides operations comprising: detecting one or more trigger events at a first data center hosting a software application having first customer data of a first customer onboarded at the first data center, without being onboarded at a second data center hosting the software application; determining a portion of the first customer data comprising first data, based on replication settings comprising permissions to replicate the portion of the first customer data to a second customer of the software application having second customer data onboarded at the second data center without being onboarded at the first data center; and generating, based on the one or more trigger events, a replication, at the second data center, of the first data, the replication of the first data rendering the first data onboarded at the first data center visible to the second customer of the software application onboarded at the second data center for enabling a collaboration between the first customer and the second customer. ### Claim 2 (depends on 1) The system of claim 1, wherein the one or more trigger events comprise a creation, an update, and/or a deletion of the first customer. ### Claim 3 (depends on 2) The system of claim 2, wherein the first data replicated at the second data center comprises a profile of the first customer. ### Claim 4 (depends on 3) The system of claim 3, wherein rendering the first customer data visible to the second customer data onboarded at the second data center comprises providing connection details of the first customer data. ### Claim 5 (depends on 1) The system of claim 1, wherein the one or more trigger events comprise sharing the first data with the second customer. ### Claim 6 (depends on 1) The system of claim 1, wherein the first data comprises one or more documents associated with the software application. ### Claim 7 (depends on 1) The system of claim 1, wherein the operations further comprise: applying one or more data replication relevant settings to prevent the first data from being replicated at a third data center. ### Claim 8 (depends on 1) The system of claim 1, wherein the operations further comprise: applying one or more data replication relevant settings to prevent a second data associated with the first customer from being replicated at the second data center. ### Claim 9 (depends on 1) The system of claim 1, wherein the software application comprises an enterprise resource planning (ERP) application, a customer relationship management (CRM) application, a process management application, a process intelligence application, a sales engagement application, a territory and quota management application, an agent performance management (APM) application, a social networking application, a data warehousing application, and/or a logistics collaboration application. ### Claim 10 (depends on 1) The system of claim 1, wherein the one or more trigger events are detected by a replication client at the first data center, and wherein the replication of the first data is performed by a replication service. ### Claim 11 (depends on 10) The system of claim 10, wherein the one or more trigger events comprises an invocation of a replication method associated with the replication client, and wherein the replication client is configured to respond to the invocation of the replication method by calling an application programming interface (API) of the replication service. ### Claim 12 (depends on 11) The system of claim 11, wherein the calling of the application programming interface (API) generates a replication request that is inserted into a first queue for publication to an event broker, and wherein the event broker inserts the replication request into a second queue for consumption by the second data center. ### Claim 13 A computer-implemented method, comprising: detecting one or more trigger events at a first data center hosting a software application having first customer data of a first customer onboarded at the first data center, without being onboarded at a second data center hosting the software application; determining a portion of the first customer data comprising first data, based on replication settings comprising permissions to replicate the portion of the first customer data to a second customer of the software application having second customer data onboarded at the second data center without being onboarded at the first data center; and generating, based on the one or more trigger events, a replication, at the second data center, of the first data, the replication of the first data rendering the first data onboarded at the first data center visible to the second customer of the software application onboarded at the second data center for enabling a collaboration between the first customer and the second customer. ### Claim 14 (depends on 13) The method of claim 13, wherein the one or more trigger events comprise a creation, an update, and/or a deletion of the first customer. ### Claim 15 (depends on 14) The method of claim 14, wherein the first data replicated at the second data center comprises a profile of the first customer, and wherein rendering the first customer data visible to the second customer data onboarded at the second data center comprises providing connection details of the first customer data. ### Claim 16 (depends on 13) The method of claim 13, wherein the one or more trigger events comprise the first customer sharing the first data with the second customer. ### Claim 17 (depends on 13) The method of claim 13, wherein the first data comprises one or more documents associated with the software application. ### Claim 18 (depends on 13) The method of claim 13, further comprising: applying one or more data replication relevant settings to prevent the first data from being replicated at a third data center. ### Claim 19 (depends on 13) The method of claim 13, further comprising: applying one or more data replication relevant settings to prevent a second data associated with the first customer from being replicated at the second data center. ### Claim 20 A non-transitory computer readable medium storing instructions, which when executed by at least one data processor, result in operations comprising: detecting one or more trigger events at a first data center hosting a software application having first customer data of a first customer onboarded at the first data center, without being onboarded at a second data center hosting the software application; determining a portion of the first customer data comprising first data, based on replication settings comprising permissions to replicate the portion of the first customer data to a second customer of the software application having second customer data onboarded at the second data center without being onboarded at the first data center; and generating, based on the one or more trigger events, a replication, at the second data center, of the first data, the replication of the first data rendering the first data onboarded at the first data center visible to the second customer of the software application onboarded at the second data center for enabling a collaboration between the first customer and the second customer.