Parallel Price Master Database Lookup System

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current price calculation systems experience degraded response times due to resource-intensive database lookups in price master databases, which necessitate caching that increases memory usage and total cost of ownership, and complex cache management that affects system stability.

Innovation Solution

The system generates sub-procedures for price calculation rules that can be executed in parallel within an in-memory database, eliminating the need for caching and optimizing database lookups by grouping similar table accesses for faster execution.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of time

If price master data is cached in shared memory to avoid response time degradation, then response time is improved, but memory usage increases and total cost of ownership increases

Engineering Contradiction:
Improveresponse timeVSAvoidmemory usage
Core Design Contradiction:
Loss of timeVSQuantity of substance

Solution Approach 1:

The patent segments the monolithic database lookup process into multiple independent sub-procedures that can be executed in parallel. By dividing the pricing calculation into separate lookup operations for different price master data tables (e.g., condition tables, access tables, calculation tables), the system achieves faster overall processing without requiring large amounts of cache memory, thus resolving the contradiction between response time and memory usage.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent performs preliminary actions by pre-generating and storing SQL scripts for price master data lookups in a repository. These pre-prepared SQL statements are executed during pricing calculations, eliminating the need for complex real-time database queries and reducing response time without requiring extensive caching, thereby addressing the contradiction between response time and memory consumption.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If cache handlers employ additional services to manage cached data, then data freshness is maintained, but system resources are occupied and system stability deteriorates

Engineering Contradiction:
Improvedata freshnessVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent extracts the complex cache management functionality from the system and replaces it with a simplified approach using pre-generated SQL scripts stored in a repository. Instead of employing additional cache handler services to manage data freshness, the system uses straightforward script execution with optional validation against the price master database, significantly reducing system complexity while maintaining data reliability.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent uses disposable, short-lived SQL script objects stored in a repository instead of maintaining complex, long-lived cache structures. Each pricing calculation uses fresh or validated SQL scripts that can be quickly executed and discarded, eliminating the need for complex cache management services and reducing system complexity while ensuring data freshness through optional validation.

Inventive Principle:
Principle #27Cheap short-living objects (Disposable)

3Measurement precision

If multiple database lookups are performed sequentially for price calculations, then accuracy is maintained, but response time degrades

Engineering Contradiction:
Improvepricing accuracyVSAvoidresponse time
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The patent segments the sequential database lookup process into multiple independent sub-procedures that can execute in parallel. By dividing the pricing calculation into separate lookup operations for different price master data tables and executing them concurrently using thread pools or asynchronous processing, the system maintains pricing accuracy while dramatically reducing response time.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent transitions from sequential execution (one-dimensional time progression) to parallel execution by introducing a new dimension of concurrent processing. Multiple database lookups that were previously performed one after another are now executed simultaneously using multi-threading or asynchronous operations, maintaining accuracy through proper result aggregation while reducing overall response time.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

Data Source

PatentUS9811845B2System for accelerated price master database lookup
Publication Date: 2017.11.07 SAP SE
  • US9811845B2 patent drawing
  • US9811845B2 patent drawing
  • US9811845B2 patent drawing

AI summary

A system generates a plurality of price master data lookup procedures that are capable of being executed in parallel. The plurality of price master data lookup procedures is stored in a repository in an in-memory system. The in-memory system includes a parallel processor. The system accesses the repository of price master data lookup procedures, and retrieves price master data in parallel using the price master data lookup procedures. The system then calculates a price using the price master data retrieved from the price master database in the in-system memory.