Message-Based Interface for Heterogeneous Business Systems

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current business interfaces are not consistent across industries and departments, leading to difficulties in exchanging information between heterogeneous business entities due to differences in semantics, formatting, and programming systems, requiring human intervention and lacking standardized solutions.

Innovation Solution

A message-based interface system derived from a common business object model, using a service registry to provide consistent semantics and processing messages with universally unique identifiers, enabling consistent communication across heterogeneous applications.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If heterogeneous business entities use their own proprietary programs and semantics, then each business entity can maintain its own business logic and formatting, but information exchange between different business entities becomes difficult and requires human intervention

Engineering Contradiction:
Improvebusiness entity autonomyVSAvoidinformation exchange
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent introduces a message-based interface as an intermediary layer between heterogeneous business entities. This interface uses standardized message packages with consistent semantics to mediate information exchange, allowing proprietary business programs to communicate without direct human intervention while maintaining their own business logic

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The message-based interface is designed as a universal communication framework that can handle multiple types of business transactions and data formats. The standardized message packages can carry various business information (orders, invoices, shipments) across different industries and business entities, enabling one interface to serve multiple functions

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

2Adaptability or versatility

If different business entities use different semantics and formatting, then each entity can represent its data in its own way, but consistency in information representation across entities is lost

Engineering Contradiction:
Improvedata representation flexibilityVSAvoidinformation consistency
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent applies local quality by allowing each business entity to maintain its own data representation standards within its proprietary program, while the message-based interface applies consistent semantics only where needed for communication. Each message package contains data in a standardized format suitable for its specific purpose, rather than forcing global standardization

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The message-based interface acts as a mediator that translates between different business entity data representations and a consistent intermediate format. This ensures information consistency during exchange while preserving the flexibility of local data representation in proprietary systems

Inventive Principle:
Principle #24Intermediary (Mediator)

3Ease of manufacture

If proprietary programs are used by different business entities, then each entity can optimize its program for its specific business needs, but the complexity of integrating these programs increases

Engineering Contradiction:
Improveprogram optimizationVSAvoidsystem integration
Core Design Contradiction:
Ease of manufactureVSDevice complexity

Solution Approach 1:

The message-based interface serves as a simplifying intermediary that abstracts away the complexity of integrating proprietary programs. Each business entity only needs to implement the standardized message sending and receiving functionality, while the interface handles the complex tasks of semantic mapping, format conversion, and protocol management

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system is segmented into independent components: proprietary business programs on one side, the standardized message-based interface in the middle, and receiving business programs on the other side. This segmentation allows each component to be optimized independently while reducing overall integration complexity through the standardized interface contract

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS8601490B2Managing consistent interfaces for business rule business object across heterogeneous systems
Publication Date: 2013.12.03 SAP SE
  • US8601490B2 patent drawing
  • US8601490B2 patent drawing
  • US8601490B2 patent drawing

AI summary

A business object model, which reflects data that is used during a given business transaction, is utilized to generate interfaces. This business object model facilitates commercial transactions by providing consistent interfaces that are suitable for use across industries, across businesses, and across different departments within a business during a business transaction. In some operations, software creates, updates, or otherwise processes information related to a business rule business object.