Database Table Import Sequence Determination

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

In complex computer systems like ERP and CRM, determining the proper order for importing database tables with foreign key associations and after import methods is challenging due to circular dependencies and missing after import methods, which can lead to incorrect data import sequences.

Innovation Solution

An automated process using metadata from a data dictionary to create an order table, where tables without after import methods are stored directly, and those with methods are scanned for dependencies, with circular connections handled by storing tables in a specific order to avoid data inconsistencies.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If database tables are imported using a simple sequential order, then the import process is fast and simple, but data integrity is compromised due to circular dependencies and missing after import methods

Engineering Contradiction:

Improvedata integrityVSAvoidimport sequence determination complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The system performs preliminary analysis of foreign key associations and after import methods before the actual import process. It pre-determines the import sequence by scanning metadata, identifying circular dependencies, and calculating proper ordering, so that when import begins, the sequence is already optimized for data integrity.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system introduces an intermediary layer (the import sequence determination mechanism) that sits between the raw database tables and the import process. This intermediary analyzes metadata, resolves circular dependencies, and produces an optimized import sequence, acting as a mediator that ensures data integrity without requiring changes to the underlying database structure.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Measurement precision

If the system scans all after import methods to determine import order, then accurate dependency tracking is achieved, but processing time increases significantly

Engineering Contradiction:

Improvedependency detection accuracyVSAvoidmetadata scanning time

Core Design Contradiction:

Measurement precisionVSLoss of time

Solution Approach 1:

The system extracts only the necessary metadata information (foreign key associations and after import method signatures) required for dependency determination, rather than analyzing entire method implementations. This selective extraction maintains accurate dependency tracking while significantly reducing the time required for metadata scanning.

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

The system performs partial scanning of after import methods, focusing only on method signatures and declared dependencies rather than complete code analysis. This partial action provides sufficient information for sequence determination without the excessive time cost of full code scanning.

Inventive Principle:

Principle #16Partial or excessive action

3Stability of the object's composition

If circular dependencies are resolved by leaving blank fields, then data consistency is maintained, but additional processing steps are required

Engineering Contradiction:

Improvedata consistencyVSAvoidimport processing efficiency

Core Design Contradiction:

Stability of the object's compositionVSProductivity

Solution Approach 1:

The system performs preliminary identification of circular dependencies before import begins. By detecting circular relationships in advance and pre-planning the import sequence, it can strategically leave blank fields only where necessary while maintaining overall import efficiency, rather than dealing with circular dependencies ad hoc during the import process.

Inventive Principle:

Principle #10Preliminary action

Data Source

PatentUS11556523B2Calculating order dependency in configuration activation for complex scenarios

Publication Date: 2023.01.17 SAP SE

AI summary

In some implementations a method may be providing that includes importing database tables from a source system to a target system; obtaining, from a data dictionary, a first metadata about a foreign key association for a first database table to at least one of the database tables; obtaining, from a scan of code, a second metadata about an after import method for the first database table; in response to the second metadata representing that the after import method does not exist for the first database table, storing the first database table in the order table; and in response to the second metadata representing that the after import method does exist for the first database table, scanning for a first indication that the after import method corresponds to a read of at least one other database table before storing the first database table in the order table.