Report Part Computation Context for Data Lineage

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current Business Intelligence tools lack the ability to intuitively understand and visualize the semantics of complex report data, making it difficult for users to trace the exact definition of data values, dependencies, filters applied, and the original data sources used in computations, especially in complex reports with multiple data sources and nested elements.

Innovation Solution

The solution involves defining a report part with a computation context that includes a report identifier, element identifier, and context data path, allowing for the evaluation and export of report parts independently, which provides detailed insights into the computation process and data lineage, enabling users to understand the precise data used to compute individual report values.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If complex ad-hoc reports are built with multiple data sources and nested elements, then the reporting capability and data analysis power are improved, but the difficulty of understanding data semantics and computation context increases

Engineering Contradiction:
Improvereporting capabilityVSAvoiddata semantics understanding
Core Design Contradiction:
Adaptability or versatilityVSDifficulty of detecting and measuring

Solution Approach 1:

The patent segments complex reports into report parts with distinct computation contexts. Each report part is associated with a specific computation context that defines its data sources, filters, and calculation logic independently. This segmentation allows users to understand and trace individual report parts without being overwhelmed by the entire complex report structure.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces computation context as an intermediary layer between the report data and users. This computation context acts as a mediator that captures and preserves the semantic meaning, data sources, filters, and calculation logic for each report part, making complex data semantics accessible and understandable to users.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If report data is retrieved automatically from data sources according to report schema, then the report generation efficiency is improved, but the transparency of data computation process deteriorates

Engineering Contradiction:
Improvereport generation efficiencyVSAvoidcomputation process transparency
Core Design Contradiction:
ProductivityVSLoss of information

Solution Approach 1:

The patent performs preliminary action by capturing and storing the computation context (including data sources, filters, calculation logic, and semantic meaning) before the report is actually generated. This pre-captured context is then preserved and made accessible to users, allowing them to understand the computation process without slowing down the automated report generation.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent creates a copy of the computation context metadata alongside the report data. This copy contains all the information about how the data was computed, including data sources, filters, and calculation logic. Users can access this copied context information to understand the computation process while the automated report generation continues efficiently.

Inventive Principle:
Principle #26Copying

3Adaptability or versatility

If report values are defined in declarative self-sufficient way, then the report flexibility and reusability are improved, but the traceability of data lineage deteriorates

Engineering Contradiction:
Improvereport flexibilityVSAvoiddata lineage traceability
Core Design Contradiction:
Adaptability or versatilityVSLoss of information

Solution Approach 1:

The patent uses computation context as an intermediary that bridges declarative report definitions with data lineage traceability. Even though report values are defined in a declarative, self-sufficient manner, the associated computation context preserves the complete data lineage information, including data sources, transformation steps, and calculation logic, making traceability possible without compromising flexibility.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS8099383B2Apparatus and method for defining report parts
Publication Date: 2012.01.17 SAP IRELAND LTD
  • US8099383B2 patent drawing
  • US8099383B2 patent drawing
  • US8099383B2 patent drawing

AI summary

A computer readable storage medium includes executable instructions to define a report part with a report part element and a report part identifier. A report part computation context including a report identifier, a report part element identifier and a context data path is identified. The report part is associated with the report part computation context. The report part is evaluated according to the report part computation context. A report part value is returned.