Analytical Report Extension via Business Object Segmentation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional systems do not facilitate the usage of extension fields within analytical reports, limiting the ability to customize and extend business object models for strategic analysis and reporting.

Innovation Solution

The system allows extension fields to be added to business objects and associated with multi-dimensional analytical view models, enabling the extension of analytical reports by determining reference fields, creating new extension fields, and merging them with existing metadata models at runtime, thereby facilitating their use in analytical reports.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If extension fields are added to business objects for customization, then adaptability is improved, but device complexity increases

Engineering Contradiction:
Improvecustomization capabilityVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system segments business objects into base models and extension fields. Base business objects maintain a stable core structure while extensions are added as separate, manageable units. This segmentation allows customization without complicating the base model, resolving the contradiction between adaptability and complexity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Extension fields are nested within the business object framework at runtime. The extension mechanism is contained within the existing system architecture, allowing customization capabilities to be embedded without expanding overall system complexity. The extension fields are integrated into the data model hierarchy in a contained manner.

Inventive Principle:
Principle #7Nested doll (Nesting)

2Ease of operation

If extension fields are added to user interfaces, then ease of operation is improved, but device complexity increases

Engineering Contradiction:
Improveuser interface customizationVSAvoidinterface complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The system pre-establishes extension field definitions and metadata before runtime execution. Extension fields are declared with their properties in advance, allowing the user interface to automatically incorporate them without requiring complex runtime configuration. This preliminary setup simplifies the operational process while managing complexity.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The user interface framework automatically detects and integrates extension fields without requiring manual configuration. The system self-adapts to include new fields in appropriate interfaces and forms, reducing the operational burden on users while avoiding the complexity of manual interface customization.

Inventive Principle:
Principle #25Self-service

3Adaptability or versatility

If extension fields are integrated into analytical reports, then adaptability is improved, but device complexity increases

Engineering Contradiction:
Improvereport customizationVSAvoidreporting system complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The extension field integration mechanism serves multiple functions: it enables report customization, maintains data consistency, and preserves analytical capabilities. The same extension infrastructure used for business objects also serves reporting, eliminating the need for separate reporting complexity and achieving multi-functionality.

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

Solution Approach 2:

The system introduces an intermediary layer between extension fields and analytical reports. This intermediary mechanism automatically bridges extension fields to report templates, enabling report customization without directly complicating the reporting system architecture. The intermediary translates extension field additions into report updates automatically.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS8886646B2Field extensibility for analytical reports
Publication Date: 2014.11.11 SAP SE
  • US8886646B2 patent drawing
  • US8886646B2 patent drawing
  • US8886646B2 patent drawing

AI summary

A system may include reception of an instruction to add an extension field to a node of a business object object model, identification of at least one multi-dimensional analytical view object model including a reference field referring to the node of the business object object model, determination of at least one report associated with the determined at least one multi-dimensional analytical view object model, reception of a selection of one of the at least one report, extension of the one of the at least one multi-dimensional analytical view object model associated with the report based on the extension field, and extension of the selected report based on the extension field.