Master Data Synchronization via Local Replica Tables
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Cloud-based software applications face challenges in synchronizing master data between development and production systems, leading to discrepancies in function performance across different instances, as existing methods often rely on transferring base data to recreate master data, which can result in errors and incomplete deployments.
Innovation Solution
A system and method that utilizes a master data engine to detect changes in database tables, apply these changes to a replica, and send a transport request to the production system, including the replica data, to ensure accurate synchronization and deployment of customizations, with a transport controller verifying the contents to correct any errors and ensure complete data transfer.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If base data is transferred to recreate master data, then data synchronization is achieved, but errors and incomplete deployments occur
Solution Approach 1:
The patent creates a replica of the master data table in the development system that mirrors the production system's table structure. This replica is used to store customized data locally during development, eliminating the need to transfer and recreate base data, thereby preventing errors and incomplete deployments while maintaining synchronization accuracy.
Solution Approach 2:
The patent segments the master data into base data (stored in the production system) and customized data (stored in the development system's replica). This segmentation allows the development system to work with a localized copy for customization while maintaining the ability to synchronize only the necessary customized portions to production, improving both reliability and deployment completeness.
2Stability of the object's composition
If master data is synchronized between systems, then function performance consistency is maintained, but data transfer errors occur
Solution Approach 1:
By creating a local replica of the master data table in the development system, the patent eliminates the need for continuous data transfer during development. The replica is updated locally through database triggers, ensuring function performance consistency without exposing the development system to data transfer errors that would occur with base data transfer methods.
Solution Approach 2:
The replica acts as an intermediary between the development system's customization needs and the production system's master data. It allows the development system to operate independently with localized data while maintaining the ability to synchronize customized data to production without direct, error-prone transfers of entire master data sets.
3Adaptability or versatility
If customization is applied to master data, then system adaptability is improved, but synchronization complexity increases
Solution Approach 1:
The patent creates a copy of the master data table structure in the development system, allowing full customization capabilities locally without affecting the production system. This simplifies the synchronization process by enabling developers to work independently with the replica and only transferring customized data portions to production, rather than managing complex synchronization of entire master data sets.
Solution Approach 2:
The patent performs preliminary actions by creating the replica table structure and database triggers in advance during system setup. This preliminary configuration enables straightforward customization operations and simplifies subsequent synchronization, as the infrastructure is already in place to handle customization data transfer without adding complexity during the customization process itself.
Data Source
AI summary
A method may include detecting, at a development system hosting a first software application, a change to a first database table storing a master data associated with the first software application. The change may correspond to a customization applied to the first software application. The master data may include data objects that the first software application requires for performing a function of the first software application. In response to detecting the change to the first database table, the change may be applied to a second database table storing a replica of the master data. A transport request may be generated to include the customization and at least a portion of the second database table including the change. The transport request may be sent to a production system hosting a second software application to deploy the customization at the production system. Related systems and articles of manufacture are also provided.