Unified Business Object Processing Framework

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Employees in companies often face difficulties in modeling and designing business objects due to the need to access scattered tools for back-end business software applications, which are less familiar to them compared to personal productivity applications, leading to increased developer implementation effort and reduced extensibility.

Innovation Solution

A method is introduced that involves a modeling module to analyze and model business object logic, an implementation module to implement the logic, and a repository to store and execute it, using a metadata repository workbench and Business Object Processing Framework, allowing for the creation and management of business objects in a meta-model-centric approach.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If employees use scattered on-premise tools for back-end business software applications, then business object modeling and design can be performed, but the complexity of accessing multiple tools increases and ease of operation decreases

Engineering Contradiction:
Improveease of accessing business object modeling toolsVSAvoidcomplexity of scattered on-premise tools
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent combines multiple scattered on-premise tools into a single cloud-based business object processing framework. The framework integrates business object modeling, design, and execution capabilities in one unified system accessible via web interface, eliminating the need to switch between multiple separate on-premise applications.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The cloud-based business object processing framework acts as an intermediary between employees and the underlying complex on-premise tools. It provides a simplified web interface that abstracts away the complexity of the underlying system, allowing users to interact with business object modeling and design functions without directly accessing the complex on-premise tools.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of manufacture

If traditional scattered tools are used for business object processing, then business object modeling is possible, but developer implementation effort increases

Engineering Contradiction:
Improveease of business object modelingVSAvoiddeveloper implementation effort
Core Design Contradiction:
Ease of manufactureVSLoss of time

Solution Approach 1:

The framework provides pre-built templates, validation rules, and determination logic that are prepared in advance. Developers can leverage these pre-configured elements when creating business objects, significantly reducing the time and effort required for implementation compared to building everything from scratch using scattered tools.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The business object processing framework provides universal, multi-functional capabilities that can be applied across different business objects and scenarios. Once configured, the same framework handles various business objects (sales orders, purchase orders, invoices, etc.), eliminating the need to develop separate tools for each business object type.

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

3Adaptability or versatility

If scattered on-premise tools are used, then business object design can be performed, but extensibility is reduced

Engineering Contradiction:
Improveextensibility of business object processingVSAvoidsystem architecture complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The framework provides dynamic and flexible business object processing capabilities. Business objects can be easily extended, modified, and adapted to changing business requirements through configuration rather than complex code changes. The system dynamically adjusts to different business objects and their specific processing needs.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The unified framework provides universal extensibility mechanisms that work across all business objects. The same extension points, validation rules, and determination logic can be applied to any business object type, providing consistent extensibility without requiring separate complex architectures for each tool.

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

Data Source

PatentUS9406044B2Rule-based determination and validation in business object processing
Publication Date: 2016.08.02 SAP SE
  • US9406044B2 patent drawing
  • US9406044B2 patent drawing
  • US9406044B2 patent drawing

AI summary

A method to model a business object is disclosed. An analysis module analyzes elements of a business object. A modeling module models business object logic based on the elements of the business object. An implementation module implements the modeled business object logic. A repository stores the modeled business object logic. A business object runtime module executes the modeled business object logic.