Stacked Calculation View Merge with High-Level Logic Translation

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

The integration of high-level programming logic into database analyses often leads to inefficiencies and calculation cycle breaks due to conflicts between how high-level programming logic and database analyses are processed, particularly when dealing with complex user privileges and multiple user groups, which hinders real-time data analysis and decision-making in competitive economic environments.

Innovation Solution

A method is introduced where a high-level programming logic layer resolves and converts sub-queries into a database system format, applying high-level programming logic tags to facilitate merging with the calculation engine layer, enabling the separation and application of high-level programming logic filters within the database system, thus optimizing query processing and avoiding breaks in the calculation engine's processing.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If high-level programming logic is directly applied to database analyses, then complex analytical privileges and user group permissions can be enforced, but processing conflicts occur that break calculation cycles and reduce efficiency

Engineering Contradiction:

Improvecorrect enforcement of analytical privilegesVSAvoidquery processing efficiency

Core Design Contradiction:

ReliabilityVSProductivity

Solution Approach 1:

The patent segments the processing of high-level programming logic from database analysis by introducing a separate translation layer. The high-level logic is translated into database-specific syntax before execution, allowing privilege enforcement to be separated from the main calculation cycle. This segmentation prevents processing conflicts while maintaining correct privilege enforcement.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary translation layer that converts high-level programming logic into database-specific syntax. This intermediary component acts as a mediator between the high-level logic and the database calculation engine, preventing direct conflicts while ensuring correct privilege enforcement. The translation layer resolves syntax differences and enables seamless integration without breaking calculation cycles.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Adaptability or versatility

If high-level programming logic is integrated into database queries, then complex analytical privileges can be enforced, but the processing manner conflicts cause calculation cycle breaks

Engineering Contradiction:

Improveintegration of complex analytical privilegesVSAvoidcalculation cycle continuity

Core Design Contradiction:

Adaptability or versatilityVSStability of the object's composition

Solution Approach 1:

The patent applies preliminary action by translating high-level programming logic into database-specific syntax before the calculation cycle begins. This pre-processing step ensures that the logic is in the correct format for database execution, preventing conflicts that would otherwise break the calculation cycle. The translation occurs in advance, allowing the main calculation cycle to proceed smoothly.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The translation layer serves as an intermediary that adapts high-level programming logic to database-specific syntax. This intermediary enables the integration of complex analytical privileges while maintaining calculation cycle stability by converting potentially conflicting logic into compatible database queries before execution.

Inventive Principle:

Principle #24Intermediary (Mediator)

3Productivity

If stacked calculation views are merged, then query processing efficiency is improved, but conflicts with high-level programming logic processing reduce overall performance

Engineering Contradiction:

Improvequery processing speedVSAvoidprocessing conflict management

Core Design Contradiction:

ProductivityVSDevice complexity

Solution Approach 1:

The patent segments the processing of stacked calculation views from high-level programming logic by translating the latter into database-specific syntax. This allows calculation views to be merged and processed efficiently without encountering conflicts from high-level logic, as the logic has already been converted to compatible database queries.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent substitutes the mechanical processing of high-level programming logic with an automated translation mechanism. Instead of manually managing conflicts between high-level logic and calculation view merging, the system automatically translates the logic into database-specific syntax, eliminating the need for complex conflict management while maintaining query processing efficiency.

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

Data Source

PatentUS10169410B2Merge of stacked calculation views with higher level programming language logic

Publication Date: 2019.01.01 SAP SE

AI summary

A stacked calculation view, defining a calculation scenario, having calculation views associated with high-level programming logic which can include complex analytical privileges. Resolving, using a high-level programming logic layer, a calculation view having associated high-level programming logic with the next calculation view in the stack to generate a sub-query. Converting the sub-query into a format readable by a database system and separating the part of the sub-query provided by the high-level programming logic from the sub-query to form a high-level programming logic filter in the database system format. Merge the high-level programming logic filter into the calculation scenario to provide a calculation scenario including high-level programming logic information in the database system format.