In-Memory Database Business Object Replication Views

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Users face challenges in accessing business objects across different systems due to system-specific views, preventing efficient and cost-effective use of applications and services that rely on these objects, such as those stored in in-memory databases like HANA.

Innovation Solution

A method for generating and replicating business objects between systems, including an enterprise resource planning system and a high-performance analytic appliance, using a data replicator module that performs operations like column management, foreign key handling, and data type mapping to create replication projection views and external views for OpenSQL access.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If business objects are stored in different systems with system-specific views, then each system can maintain its own data structure and access methods, but users cannot efficiently access business objects across different systems

Engineering Contradiction:
Improveaccess to business objectsVSAvoidsystem-specific views
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent introduces a view layer as an intermediary between the database engine and users. This view layer provides a unified interface that abstracts away the underlying system-specific data structures, allowing users to access business objects consistently across different systems without being affected by the complexity of individual system views.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The view mechanism provides universal access to business objects across multiple systems. A single view can aggregate data from different data sources and present a unified interface, enabling users to access business objects regardless of which system they are stored in, thereby eliminating the need to understand system-specific views.

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

2Adaptability or versatility

If data is replicated between systems with different data structures, then data can be accessed across systems, but data type mapping and structure alignment become complex

Engineering Contradiction:
Improvecross-system data accessVSAvoiddata structure alignment
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent employs parameter changes through view definitions that map data elements between different data structures. The view layer transforms data parameters from source system structures to target system structures, handling data type mapping and structure alignment automatically without requiring complex manual configuration.

Inventive Principle:
Principle #35Parameter changes

Solution Approach 2:

The view mechanism creates virtual copies of data structures that represent the actual data in different systems. These copied views allow cross-system data access while maintaining the original data structures unchanged, eliminating the need for complex data structure alignment between systems.

Inventive Principle:
Principle #26Copying

3Speed

If in-memory database is used for high-performance applications, then data access speed is improved, but data synchronization and replication between systems becomes challenging

Engineering Contradiction:
Improvedata access speedVSAvoiddata synchronization
Core Design Contradiction:
SpeedVSDevice complexity

Solution Approach 1:

The view layer acts as an intermediary that handles data synchronization between in-memory databases and other systems. It provides a unified access point that can retrieve data from in-memory storage at high speed while simultaneously managing replication and synchronization to external systems, isolating the complexity of synchronization from the performance benefits of in-memory access.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentEP2746965B1Systems and methods for in-memory database processing
Publication Date: 2019.03.06 SAP SE
  • EP2746965B1 patent drawingFigure 1
  • EP2746965B1 patent drawingFigure 2
  • EP2746965B1 patent drawingFigure 3

AI summary

A system, a method, and a computer program product for in-memory database processing are provided. A business object is generated in a first system. The generated business object is replicated from the first system to a second system. A high performance application implementing the replicated business object is executed based on at least one system specific view.