OLAP Provider Model for Data Integration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Business information systems face difficulties in efficiently processing and interacting with external data sources due to format differences, requiring cumbersome translation and enrichment efforts, which are costly and time-consuming, and existing APIs lack features like traffic light reporting and list calculations.

Innovation Solution

A consumer services layer is introduced to facilitate access to both internal and external data, allowing external data providers to notify the system of their data model and capabilities, enabling enhanced features such as exception reporting and list calculations without forcing them to comply with the system's format, and providing a unified interface for client-oriented operations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If external data providers are forced to comply with the system's format, then data integration becomes straightforward, but it increases device complexity and reduces adaptability for external providers

Engineering Contradiction:
Improvedata integrationVSAvoidformat compliance requirements
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary layer (the business information system's data access layer) that mediates between external data providers and internal data consumers. This intermediary handles format translation and enrichment automatically, allowing external providers to maintain their native formats while internal consumers receive standardized data. The intermediary resolves the contradiction by absorbing the complexity of format compliance within itself rather than imposing it on external providers.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the data access architecture into distinct layers: external data providers, a middle data access layer with enrichment capabilities, and internal data consumers. This segmentation allows each layer to operate independently with its own format and complexity level. The middle layer specifically handles the enrichment and standardization of external data without requiring external providers to change their data formats, thus reducing device complexity for external systems while maintaining ease of operation for data integration.

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If translators are created for each calling application to convert query views, then application-specific query requirements are met, but it increases device complexity and development time

Engineering Contradiction:
Improveapplication-specific query supportVSAvoidtranslator development
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements a universal data access layer that serves multiple calling applications simultaneously. Instead of creating separate translators for each application, the system provides a single enrichment layer that can handle query views from any application. The universal layer contains the translation and enrichment logic that works with diverse query types and applications, reducing device complexity while maintaining adaptability through configuration rather than custom development.

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

Solution Approach 2:

The data access layer performs self-service by automatically enriching external data with internal business context without requiring manual translator creation for each application. The system autonomously handles the complexity of data integration, format conversion, and enrichment, freeing developers from the burden of creating and maintaining individual translators for each calling application.

Inventive Principle:
Principle #25Self-service

3Measurement precision

If external data is enriched with internal business context, then data accuracy and relevance improve, but it increases processing time and complexity

Engineering Contradiction:
Improvedata accuracyVSAvoiddata processing time
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The patent applies preliminary action by pre-defining enrichment rules and business context mappings in the data access layer. Instead of performing complex real-time enrichment for each query, the system prepares enrichment configurations in advance, storing business context, data mappings, and enrichment logic that can be quickly applied during data retrieval. This reduces processing time while maintaining data accuracy through pre-computed enrichment rules.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS8606814B2Business intelligence OLAP provider model and architecture
Publication Date: 2013.12.10 SAP SE
  • US8606814B2 patent drawing
  • US8606814B2 patent drawing
  • US8606814B2 patent drawing

AI summary

According to some embodiments, a system, method, means and computer program code is provided including identifying a provider interface, the provider interface configured to map data items from a provider data model to a system data model, identifying a set of capabilities of the provider data model, transmitting data from the information provider to the business information system through the provider interface, and communicating the set of capabilities of the provider data model to the business information system.