CN114556319A

CN114556319A - Digital decoupling

Info

Publication number: CN114556319A
Application number: CN202080069190.6A
Authority: CN
Inventors: A·泽尔; D·瓦根内克特; A·克勒贝尔
Original assignee: Accenture Global Solutions Ltd
Current assignee: Accenture Global Solutions Ltd
Priority date: 2019-08-15
Filing date: 2020-08-12
Publication date: 2022-05-27
Also published as: AU2020328920A1; US11494406B2; US20210342364A1; AU2020328920B2; EP3779678A1; WO2021028859A1; EP3779678B1; US20210049186A1; US11036757B2; BR112022002745A2

Abstract

This document describes a digital decoupling architecture that enables existing computing systems to run in parallel with new computing technologies. In some aspects, a method includes receiving, by a digital decoupling system, one or more updated data sets from a source computing system, each updated data set including data that has been updated at the source computing system. Source data entries of source tables of a database of the digital decoupling system are updated on a per updated data set basis. In response to detecting the change to the source table, a target data entry comprising data of the updated source data entry is added to a target table of the database. The adapter module obtains data for the target data entry and generates an event specifying the data for the target data entry. The event is sent to one or more destination computing elements.

Description

Digital decoupling

Cross Reference to Related Applications

This application claims the benefit of U.S. patent application No. 16/814,577 filed on 10/3/2020 and U.S. provisional application No. 62/887,096 filed on 15/8/2019, which are incorporated herein by reference in their entirety.

Background

This specification relates to digital decoupling techniques that enable existing computing systems to run in parallel with new computing techniques.

Computing techniques continue to improve at a very fast pace. To some extent, organizations can adapt and upgrade their systems over time to make them compatible with newer technologies. However, to the extent that existing systems are unable to support newer technologies or become so low-grade that significant upgrades are required. Migrating completely to a new system can be expensive and time consuming.

Disclosure of Invention

This specification generally describes a digital decoupling architecture that enables existing computing systems to run in parallel with new computing technologies.

In general, one innovative aspect of the subject matter described in this specification can be embodied in methods that include the actions of: receiving, by the digital decoupling system, one or more updated datasets from a data configuration agent (provisioning agent) installed on the source computing system, each updated dataset including data that has been updated at the source computing system. For each updated data set, source data entries of source tables of a database of the digital decoupling system are updated based on data of each updated data set. A database trigger of the digital decoupling system detects a change to the source data table in response to an update to a source data entry. In response to detecting the change to the source table, a target data entry comprising data of the updated source data entry is added to a target table of the database. An adapter module of the digital decoupling system obtains data of the target data entry from the target table. The adapter module generates an event specifying at least a portion of the data of the target data entry. The event is sent to one or more destination computing elements different from the source computing system. Other embodiments of this aspect include corresponding computer systems, apparatus, and computer programs recorded on one or more computer storage devices, each configured to perform the actions of the methods. A system of one or more computers may be configured to perform particular operations or actions by virtue of software, firmware, hardware, or a combination thereof being installed on the system that causes the system to perform the actions when in operation. The one or more computer programs may be configured to perform particular operations or actions by virtue of comprising instructions that, when executed by the data processing apparatus, cause the apparatus to perform the actions.

The foregoing and other embodiments may each optionally include one or more of the following features (alone or in combination). In some aspects, updating the source data entry comprises one of: (i) adding a source data entry to a source table, wherein the source data entry includes data of the updated data set; or (ii) modify the source data entry based on the data of the updated data set.

In some aspects, the database trigger initiates an event in response to detecting the addition of a source data entry to the source table. Some implementations may include removing, by the adapter module, data of the updated data set from the target table after the event is sent to the one or more destination computing elements.

In some aspects, sending the event to the one or more destination computing elements includes sending the event to a cloud platform. Some aspects include configuring the data configuration agent to detect changes to a database of the source computing system and push a respective updated data set to the digital decoupling system in response to each detected change.

Some aspects include: determining, by the adapter module, a type of the event based on the data of the updated data set; and including data specifying the type of event in the event. In some implementations, the source computing system includes a SAP ECC platform and the destination computing system includes a SAP HANA platform. The source and target tables may comprise SAP HANA database tables.

The subject matter described in this specification can be implemented in particular embodiments and can realize one or more of the following advantages. The digital decoupling system described in this document enables existing computing systems and new computing systems to operate in parallel using the same data. This allows newer technologies to consume data of an existing computing system before migrating completely from the existing computing system. This also allows newer software platforms to be used with older platforms without waiting for a full migration that may take several years to complete. Thus, newer technologies can be built on top of existing systems to enable faster use of newer technologies.

The digital decoupling system may be configured to receive pushed updated data from an existing computing system and may convert the updated data into events that may be consumed by a plurality of different computing elements (e.g., a plurality of cloud applications, micro-services, cloud platforms, user interfaces, etc.). In this manner, a plurality of different custom interfaces to the database of existing computing systems need not be developed for the various computing systems. Instead, each consumer of the data of the existing computing system may receive a copy of the same event that specifies the updated data. This results in less complexity, fewer interfaces, and less bandwidth to send data to each computing system.

The digital decoupling system may include a data management system, such as a SAP HANA system, configured to generate an event based on updates to an existing computing system, and the event will be used later at a data management system of a new computing system to which the existing computing system is migrated. This enables newer technologies (e.g., new applications) to be built on the data management system during migration and continue to be used after migration is complete.

The details of one or more implementations of the subject matter described in this specification are set forth in the accompanying drawings and the description below. Other features, aspects, and advantages of the subject matter will become apparent from the description, the drawings, and the claims.

Drawings

FIG. 1 is an example of an environment in which a digital decoupling system generates events based on updated data received from a source computing system.

FIG. 2 is a block diagram illustrating an example decoupling pipeline.

FIG. 3 is a flow diagram of an example process for generating events based on updated data received from a source computing system.

FIG. 4 is a block diagram of a computing system that may be used in connection with the computer-implemented methods described in this document.

Like reference numbers and designations in the various drawings indicate like elements.

Detailed Description

This specification generally describes a digital decoupling architecture that enables existing computing systems to run in parallel with new computing technologies. Existing computing systems may receive, generate, and process data in a normal manner. The data configuration agent may be deployed on an existing computing system and may be configured to send new and modified data from the existing computing system to the digital decoupling system.

The digital decoupling system may be configured to receive new or modified data from existing computing systems and convert the data into events consumable by applications and/or other computing systems (e.g., cloud-based applications and/or microservices). In this manner, new computing systems and applications that may be incompatible with and otherwise unable to interact with existing computing systems may operate in parallel with the existing computing systems until a complete migration from the existing computing systems to the new computing systems (e.g., cloud-based computing systems) may be achieved.

Fig. 1 is an example of an environment 100 in which a digital decoupling system 120 generates events based on updated data received from a source computing system 110. The source computing system 110 may be an existing computing system that includes custom applications and/or custom business logic that perform functions using data stored by the source computing system 110 (which may also be referred to as a database for brevity). For example, the source computing system 110 may be an enterprise computing system of an organization, and the source database 112 may be an enterprise database system.

In a particular example, the source computing system 110 may be a running premise Enterprise Resource Planning (ERP) system, such as SAP^TMERP central component (SAP ECC)). In this example, the source database 112 may be a SAP^TMA database system. SAP^TMECC systems can be migrated to, for example, SAP HANA^TMA platform. Such migration may take a long period of time for a large computing system (e.g., an enterprise system of a large corporation or other large organization). The digital decoupling system 120 may enable the source computing system 110 to continue performing its processes and enable one or more destination computing elements 150 to perform the processes using the same (or similar) data. The digital decoupling system 120 may be different from the source computing system 110, e.g., two computing systems may be connected via a network.

The source database 112 may store data used and generated by various applications of the source computing system 110. For example, the source database 112 may store all or a large portion of the organization's primary data. To enable access to at least some of the data in the source database 112, a data configuration agent 114 may be deployed on the source computing system 110, such as within the source database 112.

The data configuration agent 114 may be configured, for example, by a user to push data from the source database 112 to the digital decoupling system 120. The data configuration agent 114 may be configured to push updates to specified data to a corresponding data configuration server 122 of the digital decoupling system 120. In other words, the data configuration agent 114 can be configured to propagate changes to certain data in the source database 112 to the digital decoupling system 120.

The user may specify data for which updates are sent to the digital decoupling system 120 using a set of propagation criteria. The propagation criteria may include a particular table within database 120, a particular field within a table, a particular row or column of a table, a particular type of data, and/or other suitable criteria. The data configuration agent 114 may use propagation criteria to determine what data to send to the digital decoupling system 120.

The data configuration agent 114 may monitor the source database 112 for changes to the data that satisfy the propagation criteria. The data configuration agent 114 may monitor for new data added to the source database 112, modifications to data already stored in the source database 112, and/or deletions of data previously stored in the source database 112. When the data configuration agent 114 detects a change to the data that satisfies the propagation criteria, the data configuration agent 114 may send the updated data set 116 to the data configuration server 122. The updated data set 116 may include data that has been updated in the source database 112 and that satisfies the propagation criteria.

For example, assume that the source database 112 includes data about books in a library. The propagation criteria may specify that when the borrowing status of a book is changed, data configuration agent 114 is to send an identifier of the book (e.g., the title of the book or the International Standard Book Number (ISBN) of the book) and the borrowing status of the book to digital decoupling system 120. In this example, when the source database 112 is updated to indicate that a particular book has been borrowed, the data configuration agent 114 may detect a change to the borrowing status of the book and generate an updated data set 116 that includes the title of the borrowed book and the borrowing status of the book. If the copyright data for the book is changed in this example, the data configuration agent 114 will not send the updated copyright date when the date does not meet the propagation criteria.

In some implementations, the data configuration agent 114 can use the adapter to monitor changes in the source database 112. In implementations where the source computing system 110 is an SAP ECC system, the adapter may be an Oracle ECC adapter.

The data configuration server 122 may receive the updated data set 116 and update the decoupling database 124 of the digital decoupling system 124 based on the updated data set 116. The decoupling database 124 may be a database system that stores data for use by the destination computing element 150. In some implementations, the decoupled database may also be a database system that will later be used as a core data system for the computing system to which the source computing system 110 is migrating. In other words, the decoupling database 124 may ultimately be the master database that replaces the database 112. In other implementations, the decoupling database 124 may be used only until the new computing system is in place in the organization.

In some implementations, the decoupling database 124 is an in-memory (in-memory) relational database management system that stores data at the item level. For example, the decoupling database 124 may be a SAP HANA^TMA memory-oriented column relational database management system. The use of item level storage prevents information loss due to aggregation of information, which may be important for other operations that use the data. Item level storage also enables additional logic to be implemented prior to generating events based on the data. For example, additional logic may provide mapping, translation, and/or analysis using the data. Project level storage may also help connect cloud-based services and other services that are limited in integration capabilities, where it may be desirable to pre-establish logic that cannot be implemented by the service.

The decoupled database 124 includes one or more source tables 132, a database trigger module 134, and one or more target tables 136. Upon receiving the updated data set 116 from the data configuration agent 114, the data configuration server 122 may update the source data entries of the source table 132 based on the updated data set 116. In some implementations, the source table 132 tracks changes to data stored in the source database 112 that satisfy propagation criteria. In this manner, data that satisfies the propagation criteria is the same in the source table 132 and the source database 112. In which the decoupling database 124 is SAP HANA ^TMIn memory database implementations, the source tables 132 and target tables 136 may be virtual memory tables.

For example, if the updated data set 116 includes new data that was not previously stored in the source database 112, the data configuration server 122 may add a source data entry (e.g., a row or column) to the source table 132. The source data entry may include the new data added to the source database 112. If the updated data set 116 includes modified data, the data configuration server 122 may modify existing source data entries in the source table 132 based on the updated data set 116. If the updated data set 116 specifies that data be deleted from the source database 112, the data configuration server 122 may delete the source data entry corresponding to the deleted data from the source table 132.

The database trigger module 134 may be a software module configured to monitor and detect changes in the source tables 132 and update the target tables 136 based on the detected changes in the source tables 132. For example, the database trigger module 134 may be configured to monitor any changes to the source tables 132, such as new data, modified data, or deleted data. In response to detecting the change, the database trigger module 134 may add the target data entry to the target table 136.

The target data entry may include the data of the changed source data entry. For example, the target data entry may match the updated source data entry. Continuing with the previous library book example, assume the source data entry is a row in source table 132 that includes data about a book in the library. If the data of the book is updated in the source database 112 and the updated data is propagated to the source table 132, the database trigger 134 may add a target data entry as a row in the target table 136, the target data entry including the same data as the updated row in the source table 132.

The source table 132 and the target table 136 may have the same structure, e.g., the same row and column configuration. In this manner, the database trigger 134 may simply copy the updated row from the source table 132 to the target table 136.

Unlike the source table 132, the target table 136 may only store data until the data is sent to the destination computing element 150. In this manner, the source table 136 may match the relevant data in the source database 132, while the target table 136 is used to generate events for consumption by the destination computing element 150. The use of two different tables may provide the technical advantages of the described digital decoupling technique. For example, the use of different tables facilitates keeping tables 132 and 136 clean (e.g., not storing necessary data) and reducing the size of tables 132 and 136 by storing data only when it may be needed. This prevents the decoupling database 124 from being overloaded. The use of two tables enables the decoupling database 124 to apply logic to data while transferring data from one table to another, providing additional flexibility.

The digital decoupling system 120 also includes an adapter module 126. The adapter module 126 may be a software module configured to detect when data is added to the target table 136 and generate events based on the data. For example, the adapter module 126 may monitor the target table 136 for the addition of data (e.g., a new target data entry).

When a target data entry is added to the target table, the adapter module 126 may generate an event 142 for the target data entry. The events 142 may include event data based on data of the target data entry. The adapter module 126 may generate the event 142 by configuring the data of the target data entry into the format of the event. For example, the computing system 150 may be configured to receive events having a particular format (e.g., a particular set of fields, each field including a particular type of data). The adapter module 126 may take the data of the target data entry and place each piece of data into the appropriate field of the event 142. The adapter module 126 may then send the event 142 to the destination computing element 150.

The destination computing element 150 may include a cloud computing platform, a cloud application, a premise application running on a premise computer connected to the digital decoupling system, a cloud microservice, a user interface of a computer, and so forth. Each destination computing element 150 may be configured to listen for events sent by the adapter module 126. For example, each destination computing element 150 may subscribe to messages that include an event 142.

In some implementations, each destination computing element 150 may subscribe to a particular type of event (e.g., less than all events) or all events sent by the adapter module 126. In this example, the adapter module 126 may specify a type of event for each event in the event data for the event. The type of event may be based on the type of data change, addition, modification, or deletion, or the type of data being updated, such as a title change, a loan status change, and so forth.

In some implementations, the adapter module 126 streams the event to the data streaming platform. For example, the adapter module 126 may stream events to Apache Kafka^TMA data streaming platform. In another example, the adapter module 126 may be deployed at Apache Kafka^TMIn a data streaming platform. For example, the adapter module 126 may include a module for monitoring the target table and converting data in the target table 136 to Apache Kafka^TMCustom code for events streamed by a data streaming platform. The data streaming platform may stream the event to the destination computing element 150.

Using the digital decoupling system 120, each destination computing element 150 can receive relevant data from the existing computing system 110. In some implementations, the digital decoupling system 120 can provide the data in real time or near real time, e.g., within a few seconds after the data is updated in the source database 112. For example, the data configuration agent 114, the database trigger 134, and the adapter module 126 may all be configured to continuously monitor their respective data and respond immediately (or within a short period of time) in response to detecting a change in the data. In this manner, from a technical perspective, it appears as if the destination computing element 150 is directly connected to the source database 112.

In addition, the digital decoupling system 120 eliminates the need for a custom interface to be created for each destination computing element 150. Without the digital decoupling system 120, each destination computing element 150 that wants to access data of the source database 112 would require a custom interface to the source database 112. The digital decoupling system 120 creates a less complex system and a more efficient system in which each destination computing element 150 can receive updated data from the source database 112 from the same event 142, which also reduces the amount of data that must be transferred from the source database 112.

In some implementationsThe digital decoupling system 120 may provide two-way communication between the source database 112 and the destination computing element 150. For example, if an application wants to provide an acknowledgement or other data to the source database 112, the application may provide the data to the digital decoupling system 120. In turn, the digital decoupling system 120 can configure data for the source database 112 and provide the configured data to the source database 112. If the source database 112 is a SAP^TMDatabase, then the digital decoupling system 120 can provide the data to the SAP^TMAn application layer of the database.

Fig. 2 is a block diagram illustrating an example decoupling pipeline 200. The decoupling pipeline 200 includes an existing computing system 210 having existing logic 214 that performs operations based on input data 212 and a data master 216 (which may be a database system that stores master data for the existing computing system 210). The existing computing system 210 may also include an application programming interface API 218.

When the data of the data owner 216 is updated, the data may be replicated as a replication event 230. The replication event 230 may include updated data, which may be stored in the source table and/or the target table, as described above with reference to FIG. 1. The event handler 232 (e.g., an adapter module) may convert the replication event 230 into a business event 240 for consumption by other computing elements (e.g., a new application 250, a new microservice 260, or a user interface push application 270). Data for the business events may also be stored in a data storage unit 242, which may be a long-term storage device, such as a hard drive, flash memory, cloud storage, data lake, and so forth.

New application 250 and new microservice 260 may each include local data 252 and local data 262, respectively. The local data is generated by the new application 250 or the new microservice 260 and/or stored locally. New application 250 includes API 254 and new microservice 260 includes API 264. The

APIs

218, 254, and 264 enable the existing computing system 210, the new application 250, and the new microservice 260, respectively, to receive pushed data 280 from the user interface push application 270. The

APIs

218, 254, and 264 are optional and may facilitate implementation of a digital decoupling architecture. Implementing the

APIs

218, 254, and 264 may further decouple the different components in the architecture and may add more monitoring capabilities to manage the architecture in the long run.

FIG. 3 is a flow diagram of an example process 300 for generating events based on updated data received from a source computing system. Process 300 may be implemented by digital decoupling system 120. The operations of process 300 may also be implemented as instructions stored on a non-transitory computer readable medium, and execution of the instructions by one or more data processing apparatus may cause the one or more data processing apparatus to perform the operations of process 300.

One or more updated data sets are received (302). The updated data set may be received by a data configuration server of the digital decoupling system. A data configuration agent deployed on the source computing system may send the updated data set to the data configuration server in response to an update to data stored by the source computing system. Each updated data set may include updated data that has been updated at the source computing system. For example, the data configuration agent may push the updated data set to the digital decoupling system in response to detecting an update to the data.

The source table is updated based on the updated data set (304). The data configuration server may update the source data entries of the source table based on the data of the updated data set. For example, if the updated data set specifies new data that is added to an existing computing system, the data configuration server may add a new source data entry to the source table. The source data entry may include data of the updated data set.

The target data entry is added to the target table (306). As described above, the database trigger module may be configured to detect a change to the source table and to add the target data entry to the target table in response to the addition. The target data entry may include data of the source data entry.

The adapter module obtains data for the target data entry (308). For example, the adapter module may monitor the target table for any new additions to the target table. In response to detecting a new target data entry in the target table, the adapter module may retrieve data for the new target data entry.

The adapter module generates an event specifying at least a portion of the data of the target data entry (310). The adapter module may generate event data for the event based on the particular format for the event data. The particular format may be based on the format in which the data streaming platform streams the event, or the format of the destination computing element that will receive and consume the event data.

The adapter module sends the event to one or more destination computing elements (312). The adapter module may send the event to the destination computing element by streaming the event to the data streaming platform. As described above, the destination computing element may include an application, a microservice, a cloud computing platform, and so forth.

Embodiments of the subject matter and the functional operations described in this specification can be implemented in digital electronic circuitry, tangibly embodied in computer software or firmware, in computer hardware including the structures disclosed in this specification and their structural equivalents, or in combinations of one or more of them. Embodiments of the subject matter described in this specification can be implemented as one or more computer programs, i.e., one or more modules of computer program instructions, encoded on a tangible, non-transitory program carrier for execution by, or to control the operation of, data processing apparatus. Alternatively or additionally, the program instructions may be encoded on an artificially generated propagated signal (e.g., a machine-generated electrical, optical, or electromagnetic signal) that is generated to encode information for transmission to suitable receiver apparatus for execution by the data processing apparatus. The computer storage medium may be a machine-readable storage device, a machine-readable storage substrate, a random or serial access memory device, or a combination of one or more of them.

The term "data processing apparatus" refers to data processing hardware and encompasses all kinds of apparatus, devices, and machines for processing data, including by way of example a programmable processor, a computer, or multiple processors or computers. The apparatus can also be or include special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application-specific integrated circuit). The apparatus can optionally include, in addition to hardware, code that creates an execution environment for the computer program, e.g., code that constitutes processor firmware, a protocol stack, a database management system, an operating system, or a combination of one or more of them.

A computer program (which may also be referred to or described as a program, software application, module, software module, script, or code) can be written in any form of programming language, including compiled or interpreted languages, or declarative or procedural languages, and it can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. A computer program may, but need not, correspond to a file in a file system. A program can be stored in a portion of a file that holds other programs or data (e.g., one or more scripts stored in a markup language document), in a single file dedicated to the program in question, or in multiple coordinated files (e.g., files that store one or more modules, sub programs, or portions of code). A computer program can be deployed to be run on one computer or on multiple computers at one site or distributed across multiple sites and interconnected by a communication network.

The processes and logic flows described in this specification can be performed by one or more programmable computers executing one or more computer programs to perform functions by operating on input data and generating output. The processes and logic flows can also be performed by, and apparatus can also be implemented as, special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application-specific integrated circuit).

Computers suitable for the execution of a computer program include, by way of example, a general purpose microprocessor, or a special purpose microprocessor, or both, or any other kind of central processing unit. Generally, a central processing unit will receive instructions and data from a read-only memory or a random access memory or both. The main elements of a computer are a central processing unit for executing (performing) or executing (executing) instructions and one or more memory devices for storing instructions and data. Generally, a computer will also include, or be operatively coupled to receive data from or transfer data to, or both, one or more mass storage devices for storing data, e.g., magnetic, magneto-optical disks, or optical disks. However, a computer need not have such devices. Further, a computer may be embedded in another device, e.g., a mobile telephone, a Personal Digital Assistant (PDA), a mobile audio or video player, a game console, a Global Positioning System (GPS) receiver, or a portable storage device such as a Universal Serial Bus (USB) flash drive, to name a few.

Computer-readable media suitable for storing computer program instructions and data include all forms of non-volatile memory, media and memory devices, including by way of example semiconductor memory devices, e.g., EPROM, EEPROM, and flash memory devices; magnetic disks, such as internal hard disks or removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks. The processor and the memory can be supplemented by, or incorporated in, special purpose logic circuitry.

To provide for interaction with a user, embodiments of the subject matter described in this specification can be implemented on a computer having a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user and a keyboard and a pointing device (e.g., a mouse or a trackball) by which the user can provide input to the computer. Other kinds of devices may also be used to provide for interaction with a user; for example, feedback provided to the user can be any form of sensory feedback, such as visual feedback, auditory feedback, or tactile feedback; and input from the user can be received in any form, including acoustic, speech, or tactile input. In addition, the computer may interact with the user by sending documents to and receiving documents from the device used by the user; for example, by sending a web page to a web browser on the user device in response to a request received from the web browser.

Embodiments of the subject matter described in this specification can be implemented in a computing system that includes a back-end component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a client computer having a graphical user interface or a Web browser through which a user can interact with an implementation of the subject matter described in this specification), or any combination of one or more such back-end, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include a Local Area Network (LAN) and a Wide Area Network (WAN), such as the Internet.

The computing system may include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. In some embodiments, the server sends data (e.g., HTML pages) to the user device, for example, for displaying data to and receiving user input from a user interacting with the user device (which acts as a client). Data generated at the user device (e.g., a result of the user interaction) may be received at the server from the user device.

An example of one such type of computer is shown in FIG. 4, which illustrates a schematic diagram of a general-purpose computer system 400. The system 400 can be used for the operations described in association with any of the computer-implemented methods previously described according to one implementation. System 400 includes a processor 410, a memory 420, a storage device 430, and an input/output device 440. Each of the

components

410, 420, 430, and 440 are interconnected using a system bus 450. The processor 410 is capable of processing instructions for execution within the system 400. In one implementation, the processor 410 is a single-threaded processor. In another implementation, the processor 410 is a multi-threaded processor. The processor 410 is capable of processing instructions stored in the memory 420 or on the storage device 430 to display graphical information for a user interface on the input/output device 440.

Memory 420 stores information within system 400. In one implementation, the memory 420 is a computer-readable medium. In one implementation, the memory 420 is a volatile memory unit or units. In another implementation, the memory 420 is a non-volatile memory unit or units.

The storage device 430 is capable of providing mass storage for the system 400. In one implementation, the storage device 430 is a computer-readable medium. In various different implementations, the storage device 430 may be a floppy disk device, a hard disk device, an optical disk device, or a tape device.

Input/output device 440 provides input/output operations for system 400. In one implementation, the input/output device 440 includes a keyboard and/or pointing device. In another implementation, the input/output device 440 includes a display unit for displaying a graphical user interface.

While this specification contains many specific implementation details, these should not be construed as limitations on the scope of what may be claimed, but rather as descriptions of features that may be specific to particular embodiments. Certain features that are described in this specification in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination. Moreover, although features may be described above as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination, and the claimed combination may be directed to a subcombination or variation of a subcombination.

Similarly, while operations are depicted in the drawings in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In some cases, multitasking parallel processing may be advantageous. Moreover, the separation of various system modules and components in the embodiments described above should not be understood as requiring such separation in all embodiments, and it should be understood that the described program components and systems can generally be integrated together in a single software product or packaged into multiple software products.

Specific embodiments of the present subject matter have been described. Other embodiments are within the scope of the following claims. For example, the actions recited in the claims can be performed in a different order and still achieve desirable results. As one example, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some cases, multitasking parallel processing may be advantageous.

Claims

1. A computer-implemented method, comprising:

receiving, by a digital decoupling system, one or more updated data sets from a data configuration agent installed on a source computing system, each updated data set comprising data that has been updated at the source computing system;

For each updated data set:

updating source data entries of a source table of a database of the digital decoupling system based on the data of the updated dataset;

detecting, by a database trigger of the digital decoupling system, a change to the source data table, the change to the source data table responsive to the update to the source data entry;

in response to detecting the change to the source table, adding a target data entry to a target table of the database, the target data entry comprising updated data of the source data entry;

obtaining, by an adapter module of the digital decoupling system, the data of the target data entry from the target table;

generating, by the adapter module, an event specifying at least a portion of the data of the target data entry; and is

Sending the event to one or more destination computing elements different from the source computing system.

2. The computer-implemented method of claim 1, wherein updating the source data entry comprises one of: (i) adding the source data entry to the source table, wherein the source data entry comprises the data of the updated data set; or (ii) modify the source data entry based on the data of the updated data set.

3. The computer-implemented method of claim 1, wherein the database trigger initiates the event in response to detecting the addition of the source data entry to the source table.

4. The computer-implemented method of claim 1, further comprising: removing, by the adapter module, the data of the updated data set from the target table after the event is sent to the one or more destination computing elements.

5. The computer-implemented method of claim 1, wherein sending the event to one or more destination computing elements comprises sending the event to a cloud platform.

6. The computer-implemented method of claim 1, further comprising configuring the data configuration agent to: detecting changes to a database of the source computing system, and pushing a respective updated data set to the digital decoupling system in response to each detected change.

7. The computer-implemented method of claim 1, further comprising:

determining, by the adapter module, a type of the event based on the data of the updated data set; and

Including data specifying the type of the event in the event.

8. The computer-implemented method of claim 1, wherein the source computing system comprises an SAP ECC platform and the destination computing element comprises an SAP HANA platform.

9. The computer-implemented method of claim 8, wherein the source table and the target table comprise SAP HANA database tables.

10. A computer-implemented system, comprising:

one or more computers; and

one or more computer memory devices interoperably coupled with the one or more computers and having a tangible, non-transitory machine-readable medium storing one or more instructions that when executed by the one or more computers perform operations comprising:

for each updated data set:

11. The computer-implemented system of claim 10, wherein updating the source data entry comprises one of: (i) adding the source data entry to the source table, wherein the source data entry comprises the data of the updated data set; or (ii) modify the source data entry based on the data of the updated data set.

12. The computer-implemented system of claim 10, wherein the database trigger initiates the event in response to detecting the addition of the source data entry to the source table.

13. The computer-implemented system of claim 10, wherein the operations comprise: removing, by the adapter module, the data of the updated data set from the target table after the event is sent to the one or more destination computing elements.

14. The computer-implemented system of claim 10, wherein sending the event to one or more destination computing elements comprises sending the event to a cloud platform.

15. The computer-implemented system of claim 10, wherein the operations comprise configuring the data configuration agent to: detecting changes to a database of the source computing system, and pushing a respective updated data set to the digital decoupling system in response to each detected change.

16. The computer-implemented system of claim 10, wherein the operations comprise:

including data specifying the type of the event in the event.

17. The computer-implemented system of claim 10, wherein the source computing system comprises a SAP ECC platform and the destination computing element comprises a SAP HANA platform.

18. The computer-implemented system of claim 17, wherein the source table and the target table comprise SAP HANA database tables.

19. A non-transitory computer-readable medium storing one or more instructions executable by a computer system to perform operations comprising:

for each updated data set:

Generating, by the adapter module, an event specifying at least a portion of the data of the target data entry; and is provided with

20. The non-transitory computer-readable medium of claim 19, wherein updating the source data entry comprises one of: (i) adding the source data entry to the source table, wherein the source data entry comprises the data of the updated data set; or (ii) modify the source data entry based on the data of the updated data set.