Logical Data Object Web Services for Enterprise Interoperability

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Customizable web applications typically limit access to modified data structures to their user interface, preventing other applications from accessing or integrating these structures, which restricts their utility and interoperability within broader enterprise solutions.

Innovation Solution

The development of logical data object (LDO) web services and extension node web services allows for the creation and processing of web service requests, enabling access and manipulation of data structures across applications by generating consumable web services based on LDOs and extension nodes, and processing requests targeting operations associated with these entities.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If access to customized data structures is limited to the user interface of the web application, then the application maintains security and control over its data, but other applications are unable to access or integrate these data structures

Engineering Contradiction:
Improveaccessibility of data structuresVSAvoidsystem architecture complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary layer (web service interface) that sits between the customized data structures and external applications. This intermediary enables controlled access without exposing the internal structure directly, resolving the contradiction by allowing versatility while maintaining security and control.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the system into distinct layers: the data structure layer, the web service interface layer, and the application layer. This segmentation allows external applications to access data through standardized interfaces without complexity of the underlying data structures, improving accessibility while managing complexity.

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If web services are generated based on logical data objects and extension nodes, then interoperability and integration across applications are enhanced, but the complexity of service definition and management increases

Engineering Contradiction:
ImproveinteroperabilityVSAvoidservice definition complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent creates universal web service interfaces that can work with multiple types of logical data objects and extension nodes through standardized operations. This universality enables interoperability across different applications while reducing the need for application-specific service definitions, counteracting the increase in complexity.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The patent uses parameter-based service definitions where service behavior is controlled through configurable parameters rather than hard-coded logic. This allows flexible adaptation to different data structures while maintaining a consistent service framework, enhancing interoperability without proportionally increasing definition complexity.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS10412149B2Logical data object web services
Publication Date: 2019.09.10 SAP SE
  • US10412149B2 patent drawing
  • US10412149B2 patent drawing
  • US10412149B2 patent drawing

AI summary

Technologies are provided for implementing logical data object (LDO) web services. A web service definition can be received that comprises a LDO view and one or more service operation definitions. A LDO web service can be generated based on the web service definition and registered with a service endpoint. Web service requests received at the registered endpoint can be processed using the LDO web service. The runtime engine can perform service operations defined in the web service definition using one or more instances of the LDO associated with the LDO service. The LDO view can include one or more custom LDO extension nodes and/or extension data elements. A design-time application can be provided that comprises a user interface for creating a LDO web service definition. The created web service definition can be transmitted to an application server where a LDO web service can be generated based on the definition.