Unified Entity Data Aggregation for Cross-Application Search

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Software applications generate scattered data about entities across multiple systems, requiring separate searches and increased bandwidth usage for comprehensive entity information retrieval.

Innovation Solution

A system that aggregates master data and associated data into a unified entity record using a unified data model, enabling a single search interface through a search system.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If separate searches are performed on each application to retrieve entity information, then comprehensive entity information can be obtained, but the search time and number of system interactions increase

Engineering Contradiction:
Improvecompleteness of entity informationVSAvoidsearch time
Core Design Contradiction:
Loss of informationVSLoss of time

Solution Approach 1:

The patent merges data from multiple applications into a unified data model where entity information is consolidated. The search system receives queries and returns aggregated results from all applications simultaneously, eliminating the need for separate searches on each application while maintaining complete entity information.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent introduces a search system as an intermediary between users and multiple applications. This search system receives entity search queries, coordinates with the unified data model to retrieve comprehensive information, and returns consolidated results, thereby reducing the number of direct system interactions required.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Loss of information

If separate searches are performed on each application, then complete entity information can be retrieved, but the number of system interactions increases

Engineering Contradiction:
Improvecompleteness of entity informationVSAvoidnumber of system interactions
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The patent merges the data structures and search interfaces of multiple applications into a unified system. By consolidating entity data across applications into a single searchable model, the system reduces the number of separate search operations and system interactions needed to retrieve complete entity information.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent creates a universal search system that can handle entity search queries across multiple applications through a single interface. This multi-functional search capability eliminates the need for application-specific search operations, thereby reducing system interaction complexity.

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

3Adaptability or versatility

If data is scattered across multiple applications, then each application can manage its data independently, but data aggregation for search becomes inefficient

Engineering Contradiction:
Improveindependent data managementVSAvoidsearch efficiency
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent segments data into a unified data model structure that maintains logical separation of entity attributes while enabling efficient aggregation. The search system can query this segmented structure to retrieve complete entity information across applications without requiring centralized data storage, thus maintaining independent data management while improving search efficiency.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS12367196B2Managing data for unified entity search
Publication Date: 2025.07.22 SAP SE
  • US12367196B2 patent drawing
  • US12367196B2 patent drawing
  • US12367196B2 patent drawing

AI summary

Some embodiments provide a non-transitory machine-readable medium that stores a program. The program receives a set of master data for an entity from a master data system. The set of master data for the entity comprises a master data entity ID for uniquely identifying the entity. The program further receives a set of data associated with the entity from a set of applications configured to generate data associated with the entity and reference the entity using the master data entity ID when generating the of set data associated with the entity. The program also sends the set of master and the set of data associated with the entity to a search system for the search system to aggregate the set of master data for the entity and the set of data associated with the entity into a single record of data for the entity.