Dynamic View Lifecycle Management in Multi-Tenant ERP Systems

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Enterprise resource planning (ERP) systems face challenges in managing the life cycle of views, particularly in multi-tenant environments where unused views impact cost and performance due to memory consumption and the need for on-demand management during runtime.

Innovation Solution

A method for generating, validating, and deleting views at runtime using a timestamp indicator, allowing for dynamic management of data structures and query parameters, with views stored in shared memory to accommodate both core and client-specific data, enabling efficient query handling and customization.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Speed

If views are maintained in multi-tenant ERP systems, then query efficiency is improved, but memory consumption increases and performance deteriorates due to unused views

Engineering Contradiction:
Improvequery efficiencyVSAvoidmemory consumption
Core Design Contradiction:
SpeedVSQuantity of substance

Solution Approach 1:

The patent implements automatic deletion of views that are no longer valid based on timestamp comparison. When a view's timestamp does not match the current system timestamp, the view is discarded (deleted) to free memory resources. This resolves the contradiction by eliminating unused views that consume memory while maintaining valid views for query efficiency.

Inventive Principle:
Principle #34Discarding and recovering

Solution Approach 2:

The system performs self-service by automatically detecting and deleting invalid views without manual intervention. The timestamp mechanism enables the system to autonomously manage view lifecycle, identifying and removing views that have become obsolete due to system changes, thereby freeing memory resources while maintaining performance.

Inventive Principle:
Principle #25Self-service

2Quantity of substance

If views are deleted at runtime based on timestamp validation, then memory consumption is reduced, but system complexity increases

Engineering Contradiction:
Improvememory consumptionVSAvoidsystem complexity
Core Design Contradiction:
Quantity of substanceVSDevice complexity

Solution Approach 1:

The patent uses timestamp parameters to manage view lifecycle. Each view is associated with a timestamp that reflects the state of the system when the view was created. By comparing timestamps, the system determines view validity without complex validation logic. This simple parameter-based approach reduces system complexity while enabling automatic view management and memory optimization.

Inventive Principle:
Principle #35Parameter changes

3Speed

If views are regenerated at runtime, then query efficiency is maintained, but processing time increases

Engineering Contradiction:
Improvequery efficiencyVSAvoidprocessing time
Core Design Contradiction:
SpeedVSLoss of time

Solution Approach 1:

The patent performs preliminary validation of views using timestamp comparison before query execution. This preliminary check determines whether a view is still valid or needs to be deleted and regenerated. By validating views in advance rather than waiting for query failures, the system maintains query efficiency while minimizing unnecessary processing time for view regeneration.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS8977608B2View life cycle management
Publication Date: 2015.03.10 SAP SE
  • US8977608B2 patent drawing
  • US8977608B2 patent drawing
  • US8977608B2 patent drawing

AI summary

The subject matter disclosed herein provides, methods and apparatus, including computer program products for the management of a view of a data structure. In one aspect, there is provided a method that may include generating a view of a data structure. The data structure and the view may include a plurality of nodes and at least one association. This method may further include determining, at run time, whether the generated view is invalid based on an indicator. The indicator may represent whether a change has occurred to a system including the view. This method may further include deleting, at run time, the view based on the results of the determining. Related apparatus, systems, techniques and articles are also described.