Extending Data Flows in Enterprise Systems

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing data processing systems lack the ability to extend complex data types and data flows after deployment, limiting their adaptability to specific operational contexts and business needs.

Innovation Solution

The system allows for the extension of data flows by adding attributes to objects and mapping information between objects, enabling the conveyance of information across the data processing system landscape without user input, using a data flow registry and extension infrastructure logic to identify and extend relevant data flows and objects.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If data processing systems use fixed data types and data flows defined before deployment, then system stability and predictability are maintained, but the system lacks adaptability to specific operational contexts and business needs

Engineering Contradiction:
Improveadaptability to operational contextsVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system segments data flows into modular units that can be independently extended. Extension sets contain collections of object identifiers and data flow identifiers that can be selectively applied to specific objects and data flows, allowing granular customization without redesigning the entire system.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs preliminary actions by pre-defining extension sets that contain all necessary extension information before deployment. These extension sets are stored and can be automatically applied later when specific adaptation needs arise, eliminating the need for complex post-deployment customization processes.

Inventive Principle:
Principle #10Preliminary action

2Adaptability or versatility

If the system allows extension of data types and data flows after deployment, then adaptability to business scenarios is enhanced, but the complexity of managing extensions increases

Engineering Contradiction:
Improvesoftware tailoring capabilityVSAvoidextension management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system performs self-service by automatically identifying which data flows involve extended objects and extending them without user input. The extension infrastructure logic autonomously processes extension information, retrieves relevant data flow information, and applies extensions to the appropriate data flows, eliminating manual intervention and reducing management complexity.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system uses feedback mechanisms where extension information about an object triggers automatic identification of related data flows through data flow information retrieval. This feedback loop ensures that all necessary data flows are consistently extended when object extensions are applied, maintaining system integrity without requiring manual tracking.

Inventive Principle:
Principle #23Feedback

3Productivity

If manual user input is required to extend data flows, then precision and control over extensions are maintained, but productivity and ease of operation are reduced

Engineering Contradiction:
Improveextension application speedVSAvoiduser operation simplicity
Core Design Contradiction:
ProductivityVSEase of operation

Solution Approach 1:

The extension infrastructure logic provides self-service by automatically extending data flows without requiring user input. When extension information is provided for an object, the system autonomously identifies all data flows involving that object and applies the extensions, significantly improving productivity and simplifying user operations.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The extension infrastructure logic acts as an intermediary between extension information and data flow extension. It receives extension information, automatically retrieves relevant data flow information, and applies extensions to the appropriate data flows, eliminating the need for users to manually manage the complex process of extending multiple data flows.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS7505983B2Extending data flows
Publication Date: 2009.03.17 SAP SE
  • US7505983B2 patent drawing
  • US7505983B2 patent drawing
  • US7505983B2 patent drawing

AI summary

Systems and techniques for extending data flows are thus described. In one aspect, an article includes one or more machine-readable media storing instructions operable to cause one or more machines to perform operations. The operations can include receiving extension information identifying an extension of a first object in a data processing system landscape, accessing data flow information to identify one or more data flows that involve the first object, and extending, on the basis of identifying the one or more data flows as involving the first object, at least some of the one or more data flows so that information in the extension is conveyed between instances of the first object and instances of a second object during data processing in the data processing system landscape. The identified data flows convey stored information from one object to another.