Business Object View Entity for Efficient Data Access

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Complexity in enterprise computing systems makes it inefficient to selectively define and expose relevant business objects and attributes to users, processes, or services, as existing business object models span multiple industries and include thousands of nodes and attributes, leading to resource inefficiency and relevance issues.

Innovation Solution

A model-based extension of the business object model is introduced, utilizing a 'View' entity that defines a set of attributes linked by database joins across multiple business object nodes, allowing selective exposure of relevant attributes through a graphical user interface, enabling efficient data retrieval and query execution without structural transformations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If the complete business object model with all nodes and attributes is exposed to users and applications, then comprehensive data access is achieved, but resource efficiency deteriorates and complexity increases

Engineering Contradiction:
Improvedata access comprehensivenessVSAvoidresource efficiency
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent segments the large business object model into multiple views, where each view contains only the subset of nodes and attributes relevant to specific users or applications. This allows comprehensive data access to be maintained across different views while each individual view remains efficient and focused.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent extracts only the necessary nodes and attributes from the complete business object model to create targeted views. This extraction process eliminates irrelevant data from each view, improving resource efficiency while maintaining adaptability through multiple specialized views.

Inventive Principle:
Principle #2Taking out (Extraction)

2Loss of information

If all business objects and attributes are made visible to users, then complete information availability is achieved, but system complexity and difficulty of operation increase

Engineering Contradiction:
Improveinformation availabilityVSAvoidsystem operability
Core Design Contradiction:
Loss of informationVSEase of operation

Solution Approach 1:

The patent divides the comprehensive business object model into multiple segmented views, each tailored to specific user needs. This segmentation ensures complete information availability across the system while making each individual view simple and easy to operate.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces views as intermediary layers between users and the complete business object model. These views act as mediators that filter and present only relevant information, maintaining full information availability while simplifying user interaction.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Productivity

If selective exposure of business objects is implemented, then resource efficiency improves, but the complexity of defining and managing visibility increases

Engineering Contradiction:
Improveresource efficiencyVSAvoidmodel management complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent performs preliminary action by pre-defining views with specific subsets of business objects and attributes before users interact with the system. This preliminary structuring maintains resource efficiency while reducing the complexity users face during operation.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent creates simplified copies (views) of the complete business object model that contain only necessary elements. These copied views maintain the efficiency benefits of selective exposure while reducing management complexity by working with smaller, focused data structures.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS8239371B2Fast search views over business objects
Publication Date: 2012.08.07 SAP SE
  • US8239371B2 patent drawing
  • US8239371B2 patent drawing
  • US8239371B2 patent drawing

AI summary

A method and means, the method includes selecting a plurality of data sources having attributes to be included in a view entity; defining join conditions on the selected plurality of data sources; defining a set of attributes for the view entity by selecting attributes from the attributes of the plurality of data sources; and saving the view entity. The means includes a graphical user interface having a join builder tool to define join conditions on a selected plurality of data sources each including a pre-defined business object data structure having attributes; a view field definition tool to define a set of attributes for the view entity by selecting attributes from the attributes of the plurality of data sources; and a data source tree tool to display all of the attributes of the plurality of data sources.