Business Object Identifier Mapping for Cross-System Data Synchronization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Integration of business applications like SAP ERP and SAP Business ByDesign poses challenges due to unclear data ownership and lack of awareness of business objects across systems, making data synchronization difficult.
Innovation Solution
A method that involves receiving business object information from one system, creating or updating local business objects based on correspondence verification, and using mapping tables to establish and verify relationships between objects across systems.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If business applications maintain their own local business objects and identifiers, then each system operates independently with clear local data ownership, but data synchronization between systems becomes difficult due to lack of awareness of foreign business objects
Solution Approach 1:
The patent introduces a mapping table as an intermediary structure that connects local business objects with foreign business objects through identifier mappings. This mapping table enables systems to recognize and synchronize foreign business objects without requiring direct awareness or integration complexity between the actual business applications, thus resolving the contradiction between maintaining independent local data ownership and achieving data synchronization.
2Reliability
If a mapping table is created to synchronize business objects between systems, then data consistency can be achieved, but the complexity of managing identifier mappings and verification processes increases
Solution Approach 1:
The patent implements preliminary verification processes that check whether identifier mappings in the mapping table are verified before attempting synchronization. The system pre-establishes verification status for each mapping relationship and performs verification checks before synchronization operations, thereby managing the complexity of identifier mappings through structured preliminary actions rather than ad-hoc handling during synchronization.
3Measurement precision
If verification processes are implemented to confirm correspondence between local and inbound business objects, then data accuracy improves, but processing time increases due to additional comparison and validation steps
Solution Approach 1:
The patent implements a verification status mechanism where mappings can be marked as verified or unverified. The system performs full verification processes only when necessary (e.g., when correspondence is uncertain or initially establishing mappings), while skipping verification for already-verified mappings during subsequent synchronization operations. This partial verification approach maintains data accuracy while reducing unnecessary processing time for routine synchronizations.
Data Source
AI summary
Disclosed is a mechanism to process business object IDs in inbound and outbound processing. The mechanism takes into account a mapping table, matching capabilities, number ranges, inbound error and conflict handling, inbound processing, outbound processing, initial load, and data migration.