Message-Based Interface System for Heterogeneous Business Data

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, enabling the exchange of information through standardized message packages and services, which are hierarchically organized and processed to provide consistent semantics across different applications and systems.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If standardized interfaces are implemented across heterogeneous systems, then information exchange efficiency is improved, but system complexity increases due to the need for common business object models and message-based service frameworks

Engineering Contradiction:
Improveinformation exchange efficiencyVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent implements a universal message-based service interface framework that can handle multiple types of business transactions (currency conversion, date/time operations, business partner management) through a single standardized protocol. This allows heterogeneous systems to exchange information efficiently without requiring separate integration mechanisms for each transaction type, thus improving productivity while managing complexity through reuse.

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

Solution Approach 2:

The patent introduces a message-based service interface as an intermediary layer between heterogeneous business entities. This mediator translates diverse business object models into standardized messages, enabling information exchange without direct system-to-system complexity. The intermediary handles the complexity of mapping different business entities to a common framework, isolating the complexity from the transactional systems.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Loss of time

If human intervention is eliminated for information exchange between heterogeneous businesses, then transaction speed is improved, but reliability decreases due to the difficulty of achieving consistent semantics across different business entities

Engineering Contradiction:
Improvetransaction speedVSAvoidsemantic consistency
Core Design Contradiction:
Loss of timeVSReliability

Solution Approach 1:

The patent changes the parameters of information exchange by transforming diverse business data into a standardized message format with defined schemas. This parameter transformation ensures that semantic meaning is preserved during automated translation between different business entities. The standardized message structure acts as a contract that maintains reliability while enabling automated processing.

Inventive Principle:
Principle #35Parameter changes

Solution Approach 2:

The patent performs preliminary action by pre-defining message schemas and service interfaces before actual transactions occur. This advance preparation ensures that semantic consistency is built into the exchange mechanism itself, allowing automated processing without human intervention while maintaining reliability through pre-established agreements on data meaning and structure.

Inventive Principle:
Principle #10Preliminary action

3Adaptability or versatility

If industry-specific interfaces are used for different business transactions, then adaptability to specific industries is improved, but consistency across different industries and departments is worsened

Engineering Contradiction:
Improveindustry-specific adaptabilityVSAvoidinterface consistency
Core Design Contradiction:
Adaptability or versatilityVSStability of the object's composition

Solution Approach 1:

The patent segments the interface framework into two layers: a standardized message-based service interface layer that ensures consistency, and industry-specific business object model layers that provide adaptability. This segmentation allows each layer to fulfill its specific function without compromising the other, enabling both industry-specific customization and cross-industry consistency.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent adds a dimensional layer of abstraction by introducing message-based service interfaces as an intermediate dimension between industry-specific business logic and universal information exchange requirements. This dimensional change allows specific industry needs to be addressed in the business object layer while maintaining consistency in the message exchange layer, effectively resolving the contradiction through hierarchical organization.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

Data Source

PatentUS8412603B2Managing consistent interfaces for currency conversion and date and time business objects across heterogeneous systems
Publication Date: 2013.04.02 SAP SE
  • US8412603B2 patent drawing
  • US8412603B2 patent drawing
  • US8412603B2 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 Currency Conversion and Date and Time business objects.