Reporting System Table Replication Analysis

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Business organizations face inefficiencies in utilizing their business suite applications due to unawareness of additional analytical scenarios that can be executed with minimal effort, as users lack the means to identify and access the necessary tables and resources required for these scenarios.

Innovation Solution

An algorithm and tool that compare the tables used for current reports with those needed for additional scenarios, providing users with a list of potential enhancements and recommendations for efficient usage of in-memory database resources, allowing for direct execution of analytical applications without changing existing data structures.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If additional analytical scenarios are made available to users, then the usage efficiency of business suite applications is improved, but users lack awareness and opportunity to access these scenarios

Engineering Contradiction:

Improveusage efficiency of business suite applicationsVSAvoiduser awareness of available analytical scenarios

Core Design Contradiction:

ProductivityVSLoss of information

Solution Approach 1:

The system implements feedback by automatically analyzing currently replicated tables and generating information about additional analytical scenarios that could be executed with minimal additional replication effort. This feedback loop informs users of available capabilities they would otherwise remain unaware of, thereby improving usage efficiency without requiring users to actively search for options.

Inventive Principle:

Principle #23Feedback

Solution Approach 2:

The system performs self-service by autonomously identifying and presenting additional analytical scenarios based on existing table replications. Rather than requiring users to manually analyze what scenarios are possible, the system automatically generates this information and presents it to users, enabling them to make informed decisions about additional scenarios with minimal effort.

Inventive Principle:

Principle #25Self-service

2Quantity of substance

If memory size and replicated data are restrictively handled to conserve resources, then resource management is improved, but additional analytical scenarios become inaccessible

Engineering Contradiction:

Improveamount of replicated dataVSAvoidavailability of additional analytical scenarios

Core Design Contradiction:

Quantity of substanceVSAdaptability or versatility

Solution Approach 1:

The system applies partial action by identifying additional analytical scenarios that require only a small subset of additional table replications rather than full replication. By analyzing the specific data requirements of each potential scenario against currently replicated tables, the system enables users to activate additional scenarios with minimal additional resource investment, rather than requiring complete data replication.

Inventive Principle:

Principle #16Partial or excessive action

Solution Approach 2:

The system changes the parameter of table replication from an all-or-nothing approach to a selective, scenario-based approach. By evaluating which specific tables are needed for additional analytical scenarios and comparing them against currently replicated tables, the system determines minimal additional replication requirements, thereby maintaining resource constraints while enabling scenario versatility.

Inventive Principle:

Principle #35Parameter changes

3Loss of information

If users manually analyze all views and reports to determine table dependencies, then complete information is obtained, but significant time and effort are required

Engineering Contradiction:

Improvecompleteness of table dependency informationVSAvoidtime required for manual analysis

Core Design Contradiction:

Loss of informationVSLoss of time

Solution Approach 1:

The system replaces the manual mechanical process of analyzing views and reports to determine table dependencies with an automated computational system. The patent describes an algorithm that automatically identifies table dependencies for additional analytical scenarios by analyzing currently replicated tables, eliminating the need for users to manually perform this complex analysis while maintaining complete and accurate information.

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

Solution Approach 2:

The system introduces an intermediary algorithm that acts as a mediator between the complex database structure and the user. This intermediary automatically analyzes table dependencies, view relationships, and report requirements, then presents simplified information about additional executable scenarios to users, thereby complete information accuracy while significantly reducing the time and effort required.

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS10114822B2Enhanced reporting system

Publication Date: 2018.10.30 SAP SE

AI summary

A computer system includes a first database system that includes a plurality of tables, and a second database system that includes a subset of the tables in the first database system. The system identifies a plurality of reports that are currently generated using the second database system. The system also identifies a plurality of reports that are not currently generated using the second database system, but that are capable of being generated using the second database system, and displays a list of these reports on a computer display device. In an embodiment, the system further replicates one or more tables that are required for generation of additional reports from the first database system to the second database system.