Business Object Verification for SOA Data Consistency

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In software application systems, data inconsistencies arise when data is copied and sent between deployment units, leading to accuracy and integrity issues, particularly in Service-Oriented Architecture (SOA) and other frameworks, causing problems like distorted inventory levels and financial errors.

Innovation Solution

A verification manager system is implemented to generate and compare business objects, using metadata to identify and reconcile inconsistencies between deployment units, ensuring data consistency by selecting data for comparison and implementing reconciliation procedures as needed.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If data is copied and sent between decoupled deployment units in an SOA system, then system flexibility and modularity are improved, but data consistency and integrity deteriorate

Engineering Contradiction:
Improvesystem flexibilityVSAvoiddata consistency
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent implements a feedback mechanism where the sending deployment unit waits for an acknowledgment message from the receiving deployment unit to confirm successful data receipt and processing. This feedback loop ensures data consistency while maintaining the decoupled architecture, as the acknowledgment confirms that the copied data was successfully received and processed without compromising system flexibility.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The patent employs preliminary action by creating a local copy of the data at the sending deployment unit before transmitting it to the receiving deployment unit. This preliminary copying allows the sending unit to retain the original data for verification purposes while enabling the receiving unit to process the data independently, thus maintaining both system modularity and data consistency.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If acknowledgment messages are implemented to verify data receipt, then data consistency is improved, but system complexity and processing time increase

Engineering Contradiction:
Improvedata consistencyVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent merges the acknowledgment mechanism with the existing message queue infrastructure of the SOA system. The acknowledgment messages utilize the same communication channels and processing mechanisms already in place for data transmission, thereby verifying data consistency without significantly increasing system complexity or requiring separate verification infrastructure.

Inventive Principle:
Principle #5Merging (Combining)

3Adaptability or versatility

If data copying is performed between deployment units, then system modularity is improved, but data accuracy deteriorates due to copying errors

Engineering Contradiction:
Improvesystem modularityVSAvoiddata accuracy
Core Design Contradiction:
Adaptability or versatilityVSManufacturing precision

Solution Approach 1:

The patent implements a verification mechanism that compares the copied data at the receiving deployment unit with the original data at the sending deployment unit using checksums or hash values. This copying verification ensures data accuracy is maintained despite the necessary data copying operations between modular deployment units, allowing modularity without sacrificing precision.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS7519614B2Data verification systems and methods using business objects
Publication Date: 2009.04.14 SAP SE
  • US7519614B2 patent drawing
  • US7519614B2 patent drawing
  • US7519614B2 patent drawing

AI summary

Embodiments consistent with the present invention relate to methods and systems for verifying data of an application system. Consistent with exemplary embodiments, the method may generate a first business object and generate a second business object from the data related to the first business object. The method may then access metadata defining content included in the first and second business objects. The method may then verify a consistency of data in the first and second business objects according to a comparison of the first and second business objects based on the accessed metadata.