Consolidation Data Artifact Maintaining Source Separation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Complex software use scenarios involving multiple software applications or instances pose challenges in data management and integration, particularly in maintaining data separation and filtering, due to differing functionalities and legal constraints across regions, leading to increased complexity and ambiguity in landscape configurations.

Innovation Solution

The introduction of a consolidation data artifact that maintains data separation by associating each set of data with an identifier of its source instance, allowing for selective data retrieval from specific instances, and the use of consolidation spaces to group and consolidate data from multiple instances of a data artifact, enabling efficient data management and integration across diverse applications.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If data from multiple instances is consolidated into a single data artifact, then data integration and accessibility are improved, but data separation and source identification deteriorate

Engineering Contradiction:
Improvedata integrationVSAvoiddata source identification
Core Design Contradiction:
Adaptability or versatilityVSLoss of information

Solution Approach 1:

The patent introduces an intermediary identifier field that mediates between consolidated data and source instances. This identifier acts as a mediator that links consolidated data back to its source instance without requiring data duplication, thus maintaining data separation while achieving integration.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the consolidated data artifact by including source instance identifiers that divide and categorize data according to its origin. This segmentation allows the system to treat consolidated data as if it were separated, enabling source identification and instance-specific operations on unified data.

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If cross-application content is included in an application, then functionality is enhanced, but application size and complexity increase

Engineering Contradiction:
Improveapplication functionalityVSAvoidapplication complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements universality by creating a consolidation data artifact that serves multiple applications and instances simultaneously. This single artifact provides cross-application content to multiple consumers without duplicating the content in each application, thus enhancing functionality while maintaining manageable size and complexity.

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

3Reliability

If multiple instances of software applications are run, then regional compliance and data sovereignty are improved, but system complexity and configuration ambiguity increase

Engineering Contradiction:
Improveregional complianceVSAvoidlandscape configuration complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements feedback mechanisms where the consolidation data artifact includes identifiers that provide information about source instances. This feedback loop allows the system to track and manage data provenance across multiple instances, enabling automated compliance verification and reducing configuration complexity through intelligent data routing.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS12135707B2Maintaining data separation for data consolidated from multiple data artifact instances
Publication Date: 2024.11.05 SAP SE
  • US12135707B2 patent drawing
  • US12135707B2 patent drawing
  • US12135707B2 patent drawing

AI summary

Techniques and solutions are provided for maintaining data separation, such as when consolidating data for two instances of a data artifact. If data separation is not maintained, it may not be possible, or as easy, to determine from which instance particular data came, which can also limit filtering/selectively searching data for a particular instance. The present disclosure addresses this issue by providing a consolidation data artifact. For particular sets of data in the consolidation data artifact, the consolidation artifact maintains the data in association with an identifier of the instance that serves as the source of the data.