Master Data Transport Objects for Database Customization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Database management systems face challenges in optimizing performance and providing quick data access due to complex customizations and dependencies on master data, leading to errors when master data is not transported from the development to the production environment.

Innovation Solution

A method for transporting master data dependent configuration data by generating transport objects that identify required master data and foreign key connections, ensuring that necessary master data is imported alongside customization data from the development to the production environment, thereby enabling accurate execution of transactions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If complex customizations are made to data structures in database management systems, then the system can handle complex multidimensional analysis and transaction requirements, but the system performance and data access speed deteriorate due to increased complexity and dependencies on master data

Engineering Contradiction:
Improvecustomization capabilityVSAvoiddata access speed
Core Design Contradiction:
Adaptability or versatilityVSSpeed

Solution Approach 1:

The patent segments the data structure into customizable portions and fixed portions. The customizable portions can be adapted to specific transaction requirements while the fixed portions maintain optimal performance characteristics. This segmentation allows the system to handle complex customizations without compromising the performance of core data access operations.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent extracts the customization logic and dependencies from the core data access paths. By separating customizable data structure elements from the fixed, performance-critical portions, the system can apply complex customizations where needed while maintaining fast data access through the extracted, optimized core structures.

Inventive Principle:
Principle #2Taking out (Extraction)

2Reliability

If master data is not transported from development to production environment, then the production environment can operate independently, but errors occur due to missing dependencies for transaction execution

Engineering Contradiction:
Improvetransaction execution reliabilityVSAvoiddata transport complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements preliminary action by automatically identifying and transporting required master data from the development environment to the production environment before transaction execution. The system analyzes data structure dependencies in advance, determines which master data is required, and transports it proactively, preventing errors before they occur.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent employs feedback mechanisms where the system continuously monitors transaction execution requirements and automatically triggers data transport operations when dependencies are detected. The system receives feedback about missing master data, processes this information, and initiates corrective transport actions to maintain reliability.

Inventive Principle:
Principle #23Feedback

3Productivity

If manual transport of master data is performed, then data can be moved between environments, but time is lost due to manual identification and transfer processes

Engineering Contradiction:
Improvedata transport efficiencyVSAvoidmanual processing time
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The patent implements self-service by enabling the system to automatically identify, analyze, and transport its own required master data without human intervention. The system autonomously determines which data needs to be transported based on transaction requirements and executes the transport operation independently, eliminating manual processing time and improving productivity.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent introduces an intermediary automated data transport mechanism that mediates between the development and production environments. This intermediary system automatically analyzes dependencies, identifies required master data, and facilitates its transport, replacing manual processes and significantly reducing the time required for data movement.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS12197460B2Transport of master data dependent customizations
Publication Date: 2025.01.14 SAP SE
  • US12197460B2 patent drawing
  • US12197460B2 patent drawing
  • US12197460B2 patent drawing

AI summary

A method, a system, and a computer program product for transporting master data dependent configuration data for execution of a transaction. A request to import a transaction data from a first computing system to a second computing system is received. The transaction data is associated with execution of a transaction by the second computing system. Based on the received request, a determination that a first type of data is required for execution of the transaction by the second system. The first type of data includes one or more keys identifying dependencies of the first type of data on a second type of data. One or more transport objects for transporting the transaction data from the first to the second system are generated. The transaction data identifies the first and second types of data and the keys. The transaction is executed using the transport objects imported to the second system.