Message-Based Interface for Consistent Business Data Exchange

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current interfaces for exchanging business information across different business entities are inconsistent and industry-specific, leading to difficulties in transactions due to varying semantics, formatting, and currency usage, requiring a consistent method for information exchange.

Innovation Solution

A message-based interface system that generates consistent interfaces from a business object model, using a hierarchical organization with universally unique identifiers and access control lists, allowing for standardized message packages to facilitate communication across heterogeneous applications.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If heterogeneous programs with different semantics and formatting are used by different business entities, then each business entity can maintain its own program for handling its part of the transaction, but information exchange between business entities becomes difficult and requires human interaction

Engineering Contradiction:
Improveability to maintain own programVSAvoidinformation 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 entity programs. This interface uses standardized message packages with consistent semantics and formatting rules, allowing different programs to communicate without direct human interaction. The message package acts as a mediator that translates between different business entity formats while maintaining universal understanding.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent creates a universal message package structure that can be used across different industries, businesses, and departments. The standardized interface design allows the same message format to handle various types of business transactions (sales, finance, warehouse, etc.) while maintaining consistency in semantics, formatting, and data representation.

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

2Adaptability or versatility

If industry-specific interfaces are used for exchanging business information, then interfaces can be tailored to specific industry needs, but consistency across different industries and departments is lost

Engineering Contradiction:
Improveindustry-specific customizationVSAvoidinterface consistency
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent segments the interface into two layers: a standardized core message package structure that ensures consistency across all industries, and extensible fields that allow industry-specific customizations. This segmentation maintains reliable consistent communication while accommodating specialized needs through optional extensions rather than fundamental differences.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent enforces homogeneous formatting rules, semantic definitions, and data structures across all message packages. By requiring consistent use of UUIDs, access control lists, and standardized field formats, the system ensures that messages from different industries follow the same structural patterns, enabling automated processing without human intervention.

Inventive Principle:
Principle #33Homogeneity

3Adaptability or versatility

If different semantics and formatting are used by different business entities, then each entity can use its own terminology and format, but the transaction process becomes complex and error-prone

Engineering Contradiction:
Improveentity-specific semanticsVSAvoidtransaction process
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The standardized message package serves as an intermediary that resolves semantic differences between business entities. Each entity can maintain its own internal semantics while translating to the standardized message format for communication, thereby simplifying the transaction process and reducing errors caused by semantic mismatches.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent uses universally unique identifiers (UUIDs) to create standardized copies of business objects across different systems. Instead of directly exchanging complex entity-specific data structures, systems exchange standardized message packages that reference objects by UUID, simplifying the transaction process while preserving entity-specific details in the background.

Inventive Principle:
Principle #26Copying

4Reliability

If human interaction is required to facilitate transactions between businesses, then information exchange can be customized and verified, but transaction efficiency and speed are reduced

Engineering Contradiction:
Improveinformation verificationVSAvoidtransaction efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The standardized message-based interface enables systems to automatically verify and process information without human intervention. The consistent semantics, formatting rules, and access control lists built into the message packages allow automated validation and processing, significantly improving transaction efficiency while maintaining reliability through systematic verification rather than human review.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS9261950B2Consistent interface for document output request
Publication Date: 2016.02.16 SAP SE
  • US9261950B2 patent drawing
  • US9261950B2 patent drawing
  • US9261950B2 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 document output request business object.