Networked Database Meta-View for Cross-System Reporting

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current networked database systems face complexity in generating cross-system reports due to heterogeneous legacy systems with different data organization and runtime environments, requiring manual modifications and specialized interfaces for each system, which is time-consuming and inefficient.

Innovation Solution

A networked database system with an in-memory database that automatically identifies and creates database views for selected source databases, using a meta-view to dynamically combine data from multiple sources, eliminating the need for specialized interfaces and facilitating flexible reporting across various subsets of source databases.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If manual modifications of query interface and special program routines are implemented for each legacy system, then cross-system report generation becomes possible, but system complexity and implementation time increase significantly

Engineering Contradiction:
Improvecross-system report generation capabilityVSAvoidsystem implementation complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements a universal query interface that can access multiple heterogeneous legacy systems through a common architecture. The system provides multi-functional capabilities by supporting different data formats, query types, and system protocols through a single unified interface, eliminating the need for separate specialized interfaces for each system.

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

Solution Approach 2:

The patent introduces an intermediary layer consisting of a query processor and data format converter that mediates between the user interface and legacy systems. This intermediary handles protocol translation, data format conversion, and query optimization, shielding users from the complexity of individual system differences while enabling cross-system reporting.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If specialized program routines are created for each sub-system, then data integration across systems is achieved, but development time and resource requirements increase

Engineering Contradiction:
Improvedata integration capabilityVSAvoidreport generation time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent performs preliminary actions by pre-defining data formats, query templates, and integration protocols for common legacy systems. The system pre-processes and standardizes data structures during system setup, so that when reports are generated, the integration work has already been done, significantly reducing actual report generation time.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent uses template copying mechanisms where a single query template or data integration routine can be copied and automatically adapted for multiple systems. The system replicates proven integration patterns across different legacy systems, reducing development time by avoiding redundant customization work for each system.

Inventive Principle:
Principle #26Copying

3Adaptability or versatility

If multiple specialized interfaces are implemented for different report types, then specific reporting requirements are met, but system maintenance and updates become more difficult

Engineering Contradiction:
Improvereport type coverageVSAvoidsystem maintenance ease
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent implements a universal query interface that can access multiple heterogeneous legacy systems through a common architecture. The system provides multi-functional capabilities by supporting different data formats, query types, and system protocols through a single unified interface, eliminating the need for separate specialized interfaces for each system.

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

Solution Approach 2:

The patent introduces dynamic query generation capabilities that allow the system to adaptively construct queries based on user requirements rather than relying on fixed specialized interfaces. The query processor dynamically adjusts parameters, data sources, and processing logic to handle different report types, making the system more flexible and easier to maintain.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentEP2869220B1Networked database system
Publication Date: 2019.07.17 SAP SE
  • EP2869220B1 patent drawingFigure 1~2
  • EP2869220B1 patent drawingFigure 3~4B
  • EP2869220B1 patent drawingFigure 5

AI summary

The invention relates to a networked database system (100) comprising a computer processor, an in-memory database, a configuration and a network interface. Each computer system comprises a source database. The configuration comprises a selection of one or more of the source databases. The database system comprises an interface to a portable battery powered telecommunication device for enabling a user to modify the configuration. The in-memory database comprises, for each of the source databases, a database view configured to create a report for said source database in response to being called. The processor is configured for: - receiving a request for a cross-system report from the telecommunication device via a telecommunication network; - in response to receiving the request, evaluating the configuration for automatically creating a meta view, the meta view being a configured to create the cross-system report by: o selectively calling, upon being called, the database views associated with the source databases selected in the configuration, thereby selectively retrieving data from said selected source databases, and o combining, by executing a database operation provided by the in-memory database, the data retrieved by each of the called database views for providing the cross-system report; - automatically creating the meta view and calling the generated meta view for generating the cross-system report; and - returning the generated cross-system report.