Business Object Model Interfaces for Heterogeneous System Integration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current business transaction systems face challenges in exchanging information across different industries and business entities due to heterogeneous programming systems, which require human intervention and lack consistent interfaces, leading to inefficiencies and complexity.

Innovation Solution

The generation of consistent interfaces using a business object model that defines business-related concepts and their relationships, allowing for the creation of standardized interfaces across industries and departments, enabling seamless information exchange without human interaction.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If heterogeneous programs are used by different business entities to handle their specific transaction requirements, then each business entity can use its own specialized program with custom semantics and formatting, but information exchange between business entities becomes difficult and requires human interaction

Engineering Contradiction:
Improvespecialized program functionalityVSAvoidinformation exchange difficulty
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent introduces a message-oriented middleware system that acts as an intermediary between heterogeneous business entities. This middleware provides standardized message formats, protocols, and translation capabilities that enable different programs to exchange information without requiring human intervention, thus resolving the contradiction between specialized functionality and ease of information exchange

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent creates a universal messaging framework that can handle multiple types of business transactions and communications through a single standardized interface. This universal system supports various message types (requests, responses, notifications, errors) and can adapt to different business entities' needs while maintaining consistent communication protocols, eliminating the need for separate specialized exchange mechanisms

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

2Productivity

If each business entity uses its own program with different semantics and formatting standards, then each entity can optimize for its specific business needs, but the complexity of integrating these heterogeneous systems increases significantly

Engineering Contradiction:
Improvebusiness entity optimizationVSAvoidsystem integration complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent segments the integration complexity by separating the messaging infrastructure from the business logic. Each business entity maintains its own optimized program, but the standardized message framework handles the integration concerns, dividing the system into independent, manageable components that can be developed and maintained separately

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The messaging middleware serves as an intermediary layer that absorbs the integration complexity, providing translation, validation, and routing services between heterogeneous systems. This allows business entities to optimize their programs independently while the middleware handles the complexity of interoperability

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If human interaction is required to facilitate transactions between heterogeneous business entities, then information exchange can be achieved through manual coordination, but the efficiency and speed of business transactions are significantly reduced

Engineering Contradiction:
Improvetransaction completionVSAvoidtransaction efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent implements self-service automation where the messaging system automatically handles message composition, validation, routing, and error handling without human intervention. Business entities' programs can autonomously exchange information through standardized protocols, maintaining reliable transaction completion while dramatically improving efficiency and speed

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS8566193B2Consistent set of interfaces derived from a business object model
Publication Date: 2013.10.22 SAP SE
  • US8566193B2 patent drawing
  • US8566193B2 patent drawing
  • US8566193B2 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.