Business Object Interfaces for Heterogeneous System Integration

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 programming, semantics, and formatting, requiring human intervention and lacking standardization.

Innovation Solution

The development of message-based interfaces that utilize business objects, such as freight order and maintenance plan services, to provide consistent and standardized communication across different business entities, enabling the exchange of information through a service registry and message-based services.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If message-based interfaces with business objects are implemented, then information exchange consistency is improved, but system complexity increases

Engineering Contradiction:
Improveinformation exchange consistencyVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces a service registry as an intermediary component that stores standardized service definitions and business object models. This registry acts as a mediator between heterogeneous business entities, providing a common reference point for information exchange without requiring direct integration between each pair of entities, thus improving consistency while managing complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The message-based interface framework implements universal service definitions that can be applied across multiple industries and business domains. The business object models are designed to be industry-agnostic, allowing the same interface framework to serve diverse business entities (manufacturing, logistics, finance, etc.), thereby improving consistency without proportionally increasing complexity through reuse.

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

2Adaptability or versatility

If standardized business object models are adopted across industries, then adaptability is improved, but implementation complexity increases

Engineering Contradiction:
Improvecross-industry adaptabilityVSAvoidimplementation complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The business object models are segmented into hierarchical layers: core business objects (industry-agnostic), extended business objects (industry-specific), and attribute-level details. This segmentation allows organizations to adopt only the necessary level of standardization for their needs, improving adaptability while controlling implementation complexity through progressive adoption.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The framework allows dynamic configuration of business object parameters and attributes to adapt to different industry requirements. Service definitions can be customized by modifying parameters within the standardized framework rather than redesigning entire interfaces, thereby improving cross-industry adaptability without proportionally increasing implementation complexity.

Inventive Principle:
Principle #35Parameter changes

3Productivity

If human intervention is eliminated for information exchange, then productivity is improved, but reliability may worsen due to automation errors

Engineering Contradiction:
Improvetransaction processing speedVSAvoidtransaction accuracy
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The message-based interface framework incorporates validation rules and error handling mechanisms that provide automated feedback loops. When messages are exchanged between business entities, the system automatically validates data formats, checks business logic constraints, and returns error feedback, thereby maintaining high productivity while ensuring reliability through automated quality control.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS8645228B2Managing consistent interfaces for business objects across heterogeneous systems
Publication Date: 2014.02.04 SAP SE
  • US8645228B2 patent drawing
  • US8645228B2 patent drawing
  • US8645228B2 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 freight order, a maintenance plan, a maintenance task list, a request for supplier freight quote, and/or a supplier freight quote business object.