Web Dynpro Table Population Using Attribute IDs

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Populating a UI Web Dynpro table with data from multiple model nodes is a lengthy and performance-costly process due to the need for looping through all nodes to extract the correct data.

Innovation Solution

The method involves populating a table node with attribute IDs, which are used to dynamically calculate other attributes, reducing the number of loops required and utilizing node indexing to retrieve data efficiently, thereby minimizing the need for backend system calls.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Manufacturing precision

If data is extracted from multiple model nodes using a looping process, then the table can be populated with complete data, but the operation becomes lengthy and performance-costly

Engineering Contradiction:
Improvedata population completenessVSAvoiddata population speed
Core Design Contradiction:
Manufacturing precisionVSProductivity

Solution Approach 1:

The patent applies preliminary action by pre-generating identification (ID) data for all table rows before the actual data population process. This ID data structure is prepared in advance, allowing the system to quickly map and populate actual data without performing lengthy looping operations during runtime. The pre-computed ID structures enable rapid data extraction from multiple model nodes by providing a ready-made framework for data mapping.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent extracts only the essential identification (ID) elements from the complete data set during the preliminary phase. Instead of extracting and processing all data attributes through looping, the system extracts minimal ID structures that serve as keys or pointers. This extracted ID framework then guides the efficient population of complete data, significantly reducing the computational burden of data extraction operations.

Inventive Principle:
Principle #2Taking out (Extraction)

2Loss of information

If all attributes are populated immediately, then the table displays complete information, but the processing time and backend system calls increase

Engineering Contradiction:
Improvedata completenessVSAvoidresponse time
Core Design Contradiction:
Loss of informationVSLoss of time

Solution Approach 1:

The patent segments the data population process into distinct phases: first populating only identification (ID) attributes in the preliminary phase, and then populating remaining data attributes on-demand or in subsequent phases. This segmentation allows the table structure to be quickly established with essential ID data, while complete information is populated only when needed, reducing unnecessary processing time and backend system calls.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent applies partial action by populating only the necessary ID attributes initially rather than all attributes at once. This partial population strategy provides sufficient information for table structure establishment and basic operations, while avoiding the time cost of populating all attributes immediately. Additional attributes are populated selectively based on actual user interactions or specific operational requirements.

Inventive Principle:
Principle #16Partial or excessive action

3Quantity of substance

If looping processes are used to extract data from model nodes, then all data can be retrieved, but the number of backend system calls increases

Engineering Contradiction:
Improvedata volume retrievedVSAvoidbackend system call frequency
Core Design Contradiction:
Quantity of substanceVSDevice complexity

Solution Approach 1:

The patent performs preliminary extraction of identification (ID) data structures before actual data retrieval operations. This pre-extraction creates a framework of ID pointers that map to the actual data in model nodes. During subsequent data population, the system uses these pre-established ID mappings to directly access required data without performing repeated looping and multiple backend system calls, thereby reducing the overall complexity of data retrieval operations.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces identification (ID) data structures as intermediary elements between the table population process and the actual model node data. These ID structures serve as mediators that pre-establish the mapping relationships, allowing the system to efficiently retrieve and populate actual data without direct, repeated access to model nodes through looping. The ID intermediaries simplify and reduce the number of backend system calls required.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS7712054B2Populating a table in a business application
Publication Date: 2010.05.04 SAP SE
  • US7712054B2 patent drawing
  • US7712054B2 patent drawing
  • US7712054B2 patent drawing

AI summary

Methods and apparatus, including computer program products, for populating a table in a business application. A computer-implemented method of displaying information on a computer display device includes displaying a first view on the display device, the first view including dropdown values and data in a table of rows and columns, the data received from a table node data structure stored in a memory, the table node data structure including node elements and attributes, and generating a second view in response to a change in a dropdown value by repopulating the table of rows and columns using attribute identifications (IDs).