Database Business Object Retrieval via Single Roundtrip

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional techniques for retrieving business objects from databases require multiple roundtrips between the client and the database server, consuming significant resources and preventing parallelization due to uncertainty about which tables contain relevant data, leading to inefficient data transport and processing.

Innovation Solution

A method where the database identifies records across multiple tables using a primary key column, allowing for parallel reading of all relevant tables in a single roundtrip, eliminating the need for joins and reducing the number of roundtrips by using a bit vector column to identify data-containing tables, and enabling the retrieval of a business object or its portion with minimal client-server communication.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If retrieve by association is used to retrieve business objects from database, then the business object can be retrieved using separate table selections, but the number of roundtrips between client and database server increases significantly (70+ roundtrips for objects with 70+ tables)

Engineering Contradiction:
ImproveBusiness object retrieval capabilityVSAvoidNumber of roundtrips
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The patent merges multiple separate table selection operations into a single database operation by implementing server-side logic that retrieves data from multiple tables in one roundtrip. The database server executes coordinated queries across related tables and returns consolidated results, eliminating the need for sequential client-side table selections.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent performs preliminary identification of relevant tables and data requirements on the server side before execution. The system pre-determines which tables contain necessary data for the requested business object and prepares the retrieval strategy in advance, allowing efficient single-roundtrip data gathering without client-side uncertainty about table contents.

Inventive Principle:
Principle #10Preliminary action

2Quantity of substance

If separate table selections are performed for each table in a business object, then complete data can be retrieved, but data transport resources and client-side processing resources are significantly consumed

Engineering Contradiction:
ImproveComplete business object dataVSAvoidData transport and processing resources
Core Design Contradiction:
Quantity of substanceVSLoss of energy

Solution Approach 1:

The patent combines multiple small data transfers into a single consolidated data transport operation. By retrieving data from all necessary tables in one database roundtrip and returning consolidated results, the system reduces network overhead and client-side processing burden compared to sequential table-by-table retrieval.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent implements server-side data consolidation where the database server assembles complete business object data from multiple tables and returns it as a unified result set. This eliminates the need for clients to perform multiple separate data receptions and assemble pieces incrementally, reducing overall processing overhead.

Inventive Principle:
Principle #26Copying

3Productivity

If optimization techniques are applied to retrieve business objects, then retrieval efficiency can be improved, but parallelization cannot be achieved because it is not clear which tables contain relevant data

Engineering Contradiction:
ImproveRetrieval efficiencyVSAvoidRequest parallelization capability
Core Design Contradiction:
ProductivityVSExtent of automation

Solution Approach 1:

The patent performs preliminary analysis on the server side to identify which tables contain relevant data for the requested business object before execution. This pre-determination of data locations enables the system to optimize retrieval strategies and allows parallel processing of table selections since the dependency structure is already resolved server-side.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS9465836B2Enhanced business object retrieval
Publication Date: 2016.10.11 SAP SE
  • US9465836B2 patent drawing
  • US9465836B2 patent drawing
  • US9465836B2 patent drawing

AI summary

A request for at least a portion of a business object is received by a database from a client in a first half of a roundtrip between the client and the database. Each of the tables includes a primary key column and a plurality of records. The primary key column provides, for each record in the table, a primary key for one of a plurality of business objects. Thereafter, the database identifies records within a set of tables among a larger number of tables in the database by matching a primary key associated with the business object with the primary key in the primary key column. Once this identification has been made, the database obtains all values responsive to the request from the identified record and transmits, in a second half of the roundtrip between the client and the database, the obtained values for the business object to the client.