Hierarchical EDI Database Architecture for Data Storage
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Receiving, verifying, and completing data transactions between two entities in an EDI environment are complicated and prone to errors due to the complexity of managing various data types and the need for frequent table creation in database systems.
Innovation Solution
An information storage and retrieval system that uses a scalable and hierarchical database architecture with a master self-referential table and child tables to store and retrieve EDI document information without creating new data tables, simplifying queries and reducing memory usage by storing third-party information in existing tables.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If new data tables are created for each third-party system and data type in EDI environment, then data storage capability is improved, but device complexity and memory requirements increase
Solution Approach 1:
The patent implements a universal data table structure that can store multiple third-party system information and various data types within the same table framework. The hierarchical database architecture uses a master table with foreign keys that reference child tables, allowing a single table structure to accommodate diverse EDI data from different trading partners without requiring separate tables for each system or data type.
2Ease of manufacture
If new data tables are created frequently for different data types, then data organization is improved, but loss of time increases due to frequent table creation
Solution Approach 1:
The patent establishes a pre-configured hierarchical database structure with master tables and child tables before data storage is needed. The master table contains foreign keys that are pre-defined to reference child tables, creating a ready-to-use framework that can immediately accommodate new EDI data without requiring table creation at the time of data ingestion or retrieval.
3Loss of information
If complex queries are used to retrieve EDI document information from multiple tables, then data retrieval completeness is improved, but loss of time increases
Solution Approach 1:
The patent divides the database into segmented hierarchical levels with a master table containing foreign keys and child tables containing specific data. This segmentation allows queries to start from the master table and efficiently navigate to specific child tables using the foreign key relationships, reducing the complexity of queries compared to searching across multiple independent tables while maintaining complete data retrieval capability.
Data Source
AI summary
Described in detail herein are systems and methods a data repository for an Electronic Document Interchange (EDI) system. A data repository management system can receive from a party system, at least one EDI document type, information associated with the third party system, a first set of data requests and a first set of data responses. The data repository management system can be operatively coupled to a data repository including a master self-referential table defining a hierarchy for the data repository. The data repository can further include a child table, a first sub-child table and a second sub-child table. The data repository management system can generate a rows in the master self-relational table, child table, first sub-child table and second sub-child table to store the information associated with the third party system and an associated EDI document.