Neutral Interface Data Migration System

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing data migration tools lack flexibility and customization, particularly when moving data from operational databases to data warehouses, as they do not fully cover the business objects of the target system, requiring additional post-processing steps and not providing the desired level of compatibility between different computer systems.

Innovation Solution

A migration system with a neutral interface that maps external data to business objects on the target system, allowing for a receiver-driven approach to building and customizing migration rules, enabling direct access to all business objects and supporting complex data models, along with a delete function for iterative testing without affecting the entire target system data.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If existing migration tools are used to move data from operational databases to data warehouses, then data transfer can be performed, but flexibility and customization are insufficient and additional post-processing steps are required

Engineering Contradiction:
Improveflexibility and customizationVSAvoidadditional post-processing steps
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The migration tool is designed with a universal interface that can handle multiple data sources and target systems through standardized mapping mechanisms. The tool provides built-in support for various data types and business objects, eliminating the need for custom post-processing steps while maintaining flexibility across different migration scenarios.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The system introduces a neutral interface as an intermediary layer between source and target systems. This interface includes mapping mechanisms that automatically translate data between different formats and business objects, serving as a mediator that handles conversion tasks without requiring additional post-processing steps.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If existing migration tools are used, then data can be transferred, but they do not cover the full scope of business objects of the destination system

Engineering Contradiction:
Improvecoverage of business objectsVSAvoidmigration accuracy
Core Design Contradiction:
Adaptability or versatilityVSManufacturing precision

Solution Approach 1:

The migration tool provides comprehensive coverage of all business objects in the target system through a universal interface. The mapping mechanisms are designed to handle every business object type, ensuring complete migration coverage without leaving any data uncovered or requiring manual intervention.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The system includes validation mechanisms that provide feedback during the migration process. This feedback ensures that all business objects are properly mapped and migrated, allowing the system to verify migration accuracy and completeness automatically, thereby ensuring both full coverage and high precision.

Inventive Principle:
Principle #23Feedback

3Ease of operation

If migration projects are executed multiple times for testing, then testing can be performed, but the entire data basis of the target system must be deleted each time

Engineering Contradiction:
Improveiterative testing capabilityVSAvoidtarget system data
Core Design Contradiction:
Ease of operationVSLoss of substance

Solution Approach 1:

The migration tool segments the data migration process into discrete, controllable units. Each migration project operates independently with its own data scope, allowing multiple testing iterations without affecting the entire target system data basis. The segmentation enables selective migration and testing of specific data subsets.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system implements selective data handling where only the migrated data from each project is temporarily stored, while the original target system data remains intact. After testing, the migrated data can be discarded or recovered without impacting the permanent target system data, enabling iterative testing without data loss.

Inventive Principle:
Principle #34Discarding and recovering

4Adaptability or versatility

If custom conversion software is created to move and convert data, then data can be transferred between incompatible systems, but the software is complex and requires extensive programming effort

Engineering Contradiction:
Improvesystem compatibilityVSAvoidsoftware complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system uses a neutral interface as an intermediary that provides standardized mapping mechanisms between different data formats and business objects. This intermediary layer handles the complexity of format conversion automatically, allowing the tool to work with incompatible systems without requiring custom programming for each pair of systems.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The migration tool provides a universal interface that can handle multiple data sources and target systems through standardized mapping mechanisms. The tool provides built-in support for various data types and business objects, eliminating the need for custom post-processing steps while maintaining flexibility across different migration scenarios.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentEP1857946B1Systems and methods for migrating data
Publication Date: 2018.04.04 SAP SE
  • EP1857946B1 patent drawingFigure 1
  • EP1857946B1 patent drawingFigure 2
  • EP1857946B1 patent drawingFigure 3

AI summary

The present invention provides systems and methods for migrating data from at least one data source to at least one data destination according to one ore more migration rules, where the migration rules may indicate how the data migration are done. In exemplary embodiments, a neutral interface which comprises a mapping of external data fields to business objects located on the destination system is provided. The migration rules, which may be customizable according to the business requirements, may describe how the source data are modified during the migration process in order to meet the requirements of the destination system.