Event-Based Data Object Processing for Real-Time Costing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current data processing methods in electronic systems and cost accounting are limited by hardware restrictions, leading to reduced security and detailed analysis capabilities, as well as time constraints for period-end reporting, which necessitates less detailed costing and manual input for overhead costs.

Innovation Solution

A method and system for processing data objects by creating a second data object upon storing a first data object, using an object processor to apply pre-settable rules and generate a third data object, allowing for immediate and automatic handling of business transactions and costing, reducing the need for manual input and enabling detailed, real-time cost assignment.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If data processing is done periodically with limited time constraints, then hardware restrictions are avoided, but security and detailed analysis capabilities are reduced

Engineering Contradiction:
ImprovesecurityVSAvoidtime for detailed analysis
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by immediately creating a second data object when a first data object is stored, and automatically triggers processing before the period-end deadline. This advance preparation allows detailed analysis to be completed within the limited time window without requiring extended processing periods.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements continuous processing by automatically triggering the object processor as soon as a first data object is stored, rather than waiting for periodic batch processing. This continuous action ensures that security analysis is performed immediately and consistently, maximizing both security coverage and detailed analysis capability within the constrained time frame.

Inventive Principle:
Principle #20Continuity of useful action

2Measurement precision

If more detailed costing analysis is performed, then accuracy improves, but processing time and hardware resources increase

Engineering Contradiction:
Improvecosting accuracyVSAvoidperiod-end closing time
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The system performs self-service by automatically creating second data objects and triggering processing without manual intervention. The object processor autonomously applies pre-settable rules to generate third data objects, eliminating the need for manual cost assignment and reducing period-end closing time while maintaining detailed costing accuracy.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent applies preliminary action by pre-configuring the object processor with pre-settable rules that define how costing should be performed. This preparation allows the system to execute detailed costing analysis automatically and efficiently during the period-end closing period without requiring extended processing time or manual configuration.

Inventive Principle:
Principle #10Preliminary action

3Productivity

If manual input is used for overhead costs, then flexibility is maintained, but processing efficiency and detail level are reduced

Engineering Contradiction:
Improveprocessing efficiencyVSAvoidautomatic cost assignment
Core Design Contradiction:
ProductivityVSExtent of automation

Solution Approach 1:

The system implements self-service automation where the object processor automatically creates second data objects from first data objects and generates third data objects by applying pre-settable rules. This automatic process eliminates manual input requirements for overhead costs while maintaining flexibility through configurable rules, significantly improving processing efficiency.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent applies universality by designing a multi-functional object processor that handles multiple operations: creating second data objects, applying pre-settable rules, generating third data objects, and managing overhead costs. This unified approach consolidates multiple manual processes into a single automated system, improving efficiency while maintaining adaptability.

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

4Reliability

If period-end data collection is used, then comprehensive data is available, but system availability and response time are reduced

Engineering Contradiction:
Improvesystem availabilityVSAvoiddata collection time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent implements continuous useful action by automatically triggering the object processor immediately when a first data object is stored, rather than waiting for periodic data collection. This continuous processing maintains system availability and provides immediate response time, while still accessing comprehensive data through the automated retrieval of first, second, and third data objects.

Inventive Principle:
Principle #20Continuity of useful action

Data Source

PatentUS10031963B2Methods, systems, and software applications for event based data processing
Publication Date: 2018.07.24 SAP SE
  • US10031963B2 patent drawing
  • US10031963B2 patent drawing
  • US10031963B2 patent drawing

AI summary

Methods and systems are provided for processing data objects in a computer system. In one embodiment, a method is provided that comprises (a) storing a first data object in a database in a non volatile storage, (b) creating a second data object assigned to the first data object, step (b) being triggered by step (a), and (c) processing the second data object by means of an object processor, the object processor creating a third data object using data contained in the second data object, data contained in the first data object and data contained in the database by applying a set of one or more pre-settable rules to the data contained in the first and second data objects and in the database.