Composite Business Object for Data Retrieval Overhead

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Business process platforms face significant processing and operation overhead when accessing and retrieving attributes from multiple business object nodes, particularly when attributes are shared across different screens, leading to inefficient data retrieval and potential performance issues.

Innovation Solution

The implementation of Retrieve Transformation Nodes (RTNs) allows for fast and efficient access to data by temporarily storing node instances in a secondary buffer, using an alternative key for access, and restricting editing operations to ensure optimal performance during retrieval transactions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If attributes are retrieved from multiple business object nodes, then data completeness is improved, but processing overhead increases

Engineering Contradiction:
Improvedata completenessVSAvoidprocessing overhead
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The patent merges attributes from multiple business object nodes into a single composite business object. When a screen requires attributes from different nodes (e.g., sales order attributes and customer attributes), the system combines these into one unified object, eliminating the need to access multiple nodes separately and reducing processing overhead while maintaining data completeness

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The system performs preliminary actions by pre-computing and storing composite business objects that contain aggregated attributes from multiple nodes. This allows subsequent screen displays to retrieve data from a single pre-prepared object rather than assembling data from multiple sources in real-time, reducing retrieval overhead

Inventive Principle:
Principle #10Preliminary action

2Loss of information

If multiple disk or memory access operations are performed to retrieve attributes, then data retrieval completeness is improved, but operation overhead increases

Engineering Contradiction:
Improveattribute retrieval completenessVSAvoidoperation overhead
Core Design Contradiction:
Loss of informationVSLoss of time

Solution Approach 1:

The patent combines multiple attribute retrieval operations into a single memory access by creating a composite business object that contains all required attributes from multiple nodes. This single object can be retrieved in one operation rather than requiring separate disk or memory accesses for each attribute, significantly reducing operation overhead while ensuring all required data is retrieved

Inventive Principle:
Principle #5Merging (Combining)

3Loss of information

If attributes are accessed that are not shown on the screen, then data completeness is improved, but processing overhead increases

Engineering Contradiction:
Improvedata completenessVSAvoidprocessing efficiency
Core Design Contradiction:
Loss of informationVSProductivity

Solution Approach 1:

The patent applies local quality by creating different versions or projections of the composite business object based on specific screen requirements. Each screen receives only the attributes it needs from the composite object, rather than retrieving all possible attributes. This selective retrieval maintains data completeness for each specific use case while improving processing efficiency by avoiding unnecessary data transfer

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS8135689B2Performance optimized retrieve transformation nodes
Publication Date: 2012.03.13 SAP SE
  • US8135689B2 patent drawing
  • US8135689B2 patent drawing
  • US8135689B2 patent drawing

AI summary

Systems, methods, computer program code, and means are provided for processing retrieve requests received in a business software system. Pursuant to some embodiments, a retrieve request is processed by identifying that the requested node is a retrieve transformation node, determining that the node relates to one of a currently selected business object and a secondary business object, and retrieving the node data from one of a persistence buffer and a secondary buffer based on the determining.