Process-Based Data Reuse Framework for Software Transitions

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current data management systems fail to segregate and validate data based on business processes, leading to unreliability and resource wastage during software transitions, upgrades, or enhancements, as they primarily focus on business objects rather than organizational processes.

Innovation Solution

An intelligent framework that identifies, maps, and validates data for reuse by associating it with business processes, using an API to cleanse and correct data sets, and provides a graphical user interface for outputting validation results.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If data is managed without process classification, then data storage is simple, but data reliability and reusability deteriorate during software transitions

Engineering Contradiction:
Improvedata reliabilityVSAvoiddata management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments data into process-specific categories by introducing a process classification layer that divides data into distinct process groups (e.g., order management, inventory control). This segmentation enables reliable data reuse within each process while maintaining overall system manageability through structured organization.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a process classification intermediary layer between data storage and application logic. This intermediary classifies and maps data to specific business processes, enabling reliable data retrieval and reuse without directly complicating the core data storage mechanisms.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If data validation is performed manually, then validation thoroughness is limited, but system complexity and resource consumption increase

Engineering Contradiction:
Improvedata integrityVSAvoidvalidation efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent implements self-service validation where the system automatically validates data against predefined process-specific rules and schemas. The validation mechanism serves itself by automatically detecting data issues, generating reports, and suggesting corrections without requiring extensive manual intervention.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent incorporates feedback mechanisms that automatically validate data, compare it against process requirements, and provide immediate feedback reports. This feedback loop enables continuous validation improvement while maintaining high productivity through automated decision-making.

Inventive Principle:
Principle #23Feedback

3Adaptability or versatility

If data is not classified by process, then data access is straightforward, but data reusability and consistency across software changes deteriorate

Engineering Contradiction:
Improvedata reusabilityVSAvoiddata access simplicity
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent creates a universal process classification framework that serves multiple functions: data classification, access control, validation, and reuse guidance. This multi-functional approach enhances data reusability across different software versions while maintaining ease of access through a unified classification system.

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

Data Source

PatentUS12436939B2Data reuse framework
Publication Date: 2025.10.07 SAP SE
  • US12436939B2 patent drawing
  • US12436939B2 patent drawing
  • US12436939B2 patent drawing

AI summary

Systems and processes for validating data for reuse in a system are provided herein. An object type relating to a scenario of operations performed by a system of an organization may be identified. Database tables and characteristics related to an object corresponding to the object type, as well as an application programming interface (API) related to the object may be identified. Data in the database tables may be validated for reuse in the system using the API, and an indication of results of validating the data may be output to a user interface.