Rule Handling Component for Business Transaction Processing

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing enterprise IT systems lack the ability for non-technical users, such as business analysts or system administrators, to easily customize business process rules for transaction processing without modifying the underlying application programs, especially in complex systems with numerous rules and data structures.

Innovation Solution

A rule handling component that allows users to define and assign business process rules at predefined points in the transaction process, using data structures for rule collections, rule data, and rule conditions, enabling customization of transaction processing without requiring programming knowledge.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If application programs are modified to customize business process rules, then the system can be tailored to specific business requirements, but the complexity and cost of customization increases significantly

Engineering Contradiction:

Improvecustomization capabilityVSAvoidcustomization complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system segments business process rules into discrete, independently configurable units that can be selected and applied at specific execution points. Each rule is a separate entity that can be defined, stored, and executed independently, allowing customization without modifying the core application program.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary rule execution mechanism that sits between the generic application program and the business logic. This intermediary layer handles rule selection, evaluation, and execution, allowing business customization without direct modification of the application code.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Adaptability or versatility

If a second custom application program is developed to perform customized processes, then specific business requirements can be met, but the system complexity and integration requirements increase

Engineering Contradiction:

Improvebusiness process customizationVSAvoidsystem integration complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent merges the customization capability directly into the existing application program by integrating a rule handling component. This allows the generic application and custom business logic to coexist and work together within a single system, eliminating the need for separate custom application programs and reducing integration complexity.

Inventive Principle:

Principle #5Merging (Combining)

3Ease of operation

If users without programming knowledge attempt to customize application programs, then business users can directly modify processes, but the ease of customization is reduced due to technical barriers

Engineering Contradiction:

Improveuser accessibilityVSAvoidcustomization capability

Core Design Contradiction:

Ease of operationVSAdaptability or versatility

Solution Approach 1:

The system enables business users to perform self-service customization by providing tools and interfaces that allow them to define, configure, and manage business process rules without requiring programming knowledge. Users can directly interact with the rule handling component to customize processes according to their needs.

Inventive Principle:

Principle #25Self-service

4Adaptability or versatility

If multiple rules are applied at execution points in a business process, then the system can handle complex business logic, but the processing time and computational resources increase

Engineering Contradiction:

Improvebusiness logic complexityVSAvoidtransaction processing speed

Core Design Contradiction:

Adaptability or versatilityVSProductivity

Solution Approach 1:

The system performs preliminary actions by pre-defining and storing business process rules in a rule base before execution. During transaction processing, the rule handling component efficiently retrieves and applies the relevant rules, reducing the computational burden during actual execution and improving processing speed.

Inventive Principle:

Principle #10Preliminary action

Data Source

PatentUS7756809B2Apparatus and product of manufacture using execution points to select conditions and rules for business transaction processing

Publication Date: 2010.07.13 SAP SE

AI summary

Techniques enable a user, such as a business analyst or a system administrator, to define business process rules that control the processing of transaction data by a computer application. A data structure is used to store business process rules. The data structure includes a condition portion and an execution portion of a rule. A rule may be associated with an external execution point, which, in turn, is associated with an application execution point in the transaction process. At runtime, the computer system executing a computer application when determines that an application execution point is reached, the computer system determines whether there is an external execution point associated with the application execution point, and if so, executes the execution portion of a rule associated with the external execution point if the condition portion of the rule is met.