Master Data Entity Relationship Management via Anchor Validation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current master data management systems lack the ability to effectively manage entity-level relationships when record transactions such as creating, updating, or deleting records occur, leading to inefficiencies in maintaining a single version of truth across all data copies.
Innovation Solution
A computer-implemented method that resolves record-level relationships at an entity level by determining a unified view of relationships using composite rules and identifying an anchor member for each entity, which is then used to validate or invalidate relationships based on the impact of record transactions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If record-level relationships are managed without entity-level resolution, then individual record transactions can be processed independently, but entity-level data consistency and relationship accuracy deteriorate
Solution Approach 1:
The patent segments relationship management into two distinct levels: record-level relationships (individual record transactions) and entity-level relationships (aggregated relationships between entities). This segmentation allows independent processing of record transactions while maintaining entity-level consistency through separate resolution mechanisms, directly addressing the contradiction between reliability and complexity.
Solution Approach 2:
The patent introduces entity-level relationships as an intermediary layer between record-level transactions and the final unified view. This intermediary resolves conflicts and inconsistencies that arise from individual record transactions, ensuring entity-level data consistency without requiring complex interdependencies between all record-level operations.
2Measurement precision
If a unified view of entity relationships is maintained, then data accuracy and semantic consistency improve, but processing time and computational resources increase
Solution Approach 1:
The patent performs preliminary resolution of record-level relationships into entity-level relationships in advance, before generating the unified view. This preliminary action pre-processes and structures the data, reducing the computational burden during unified view generation and minimizing processing time while maintaining high relationship accuracy.
Solution Approach 2:
The patent applies composite rules selectively to resolve entity-level relationships, focusing computational resources on critical relationship determinations rather than processing all possible relationships with equal depth. This partial action approach maintains necessary relationship accuracy while reducing overall processing time.
3Reliability
If anchor members are determined for all entities, then relationship validation accuracy improves, but system complexity and computational overhead increase
Solution Approach 1:
The patent determines anchor members locally for each entity based on specific criteria relevant to that entity's characteristics and relationships, rather than applying a uniform complex algorithm to all entities. This local quality approach maintains high validation accuracy for each entity while reducing overall system complexity by adapting the selection process to local needs.
Data Source
AI summary
A computer-implemented method, system and computer program product for managing relationships between entities in master data management based systems. Record level relationships at an entity level are resolved. Furthermore, a unified view of relationships between entities is determined using composite rules on the underlying resolved record level relationships. Additionally, an anchor member for each linked entity is determined, where the entities are linked together based on the determined unified view of relationships between entities. Furthermore, a record transaction involving creating, updating or deleting a record of an entity linked with another entity is received. The relationship between the linked entities is then validated or invalidated based on an impact of the record transaction with the anchor member of one of the linked entities. In this manner, relationships between entities are managed when record transactions involving creating, updating or deleting a record associated with such entities occur.