Decoupling Dependent Data Object Destruction via Backup Table

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

The existing framework for data object destruction is limited by the need to preserve the master data object until all dependent objects are destroyed, which restricts throughput and may violate compliance with regulations, as individual data objects are typically destroyed as a whole.

Innovation Solution

A framework that decouples the destruction of dependent data objects from the master data object by using a backup table to store relevant attributes, allowing the master data object to be destroyed before or concurrently with its dependents, and deleting the backup table entry once all dependents are destroyed.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the master data object is preserved until all dependent objects are destroyed, then data integrity is maintained, but destruction throughput is reduced and compliance timelines may be violated

Engineering Contradiction:

Improvedata integrityVSAvoiddestruction throughput

Core Design Contradiction:

ReliabilityVSProductivity

Solution Approach 1:

The patent segments the master data object into two parts: the original object and a backup table entry. The backup table stores only the attributes necessary for dependent object destruction decisions, allowing the master object to be destroyed independently while maintaining the ability to evaluate dependent objects.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent creates a copy of relevant attributes from the master data object and stores them in a backup table. This copy enables the destruction process to proceed without waiting for the master object, as the backup contains all necessary information for evaluating dependent objects.

Inventive Principle:

Principle #26Copying

2Reliability

If the master data object is preserved until all dependent objects are destroyed, then dependent object destruction can be properly evaluated, but retention of the master data object is extended beyond compliance requirements

Engineering Contradiction:

Improvedependent object destruction evaluationVSAvoidmaster data object retention time

Core Design Contradiction:

ReliabilityVSDuration of action of stationary object

Solution Approach 1:

The patent extracts the essential attributes from the master data object and places them in a backup table. This extraction allows the master object to be destroyed immediately while the backup table continues to support dependent object evaluation without extending master object retention.

Inventive Principle:

Principle #2Taking out (Extraction)

3Stability of the object's composition

If data objects are destroyed as a whole, then data consistency is maintained, but flexibility in destruction timing is lost

Engineering Contradiction:

Improvedata consistencyVSAvoiddestruction timing flexibility

Core Design Contradiction:

Stability of the object's compositionVSAdaptability or versatility

Solution Approach 1:

The patent segments the destruction process into independent evaluations of dependent objects based on stored attributes, allowing each dependent object to be destroyed at its appropriate time rather than requiring synchronized destruction with the master object.

Inventive Principle:

Principle #1Segmentation

Data Source

PatentUS10268694B2Decoupling of archiving and destruction for dependent business objects

Publication Date: 2019.04.23 SAP SE

AI summary

A framework for an improved destruction of interrelated data objects is described herein. In one embodiment, destruction and/or archiving of data objects are decoupled from the destruction and/or archiving of a master data object by using a backup table. Before being destructed, attributes relevant to destruction of dependent data objects are copied from the master data object to the backup table. Subsequent destruction operations performed on data objects dependent on the master data object may attempt to retrieve the attributes relevant to destruction from the master data object itself, or from the backup table. In this way, data object destruction orderings are avoided, enabling dependent data objects to be destructed at any time.