ERP Integration via Intermediary Layer and Data Mapping
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Data integration between corporate headquarters ERP management systems and subsidiary ERP systems is challenging due to system diversity, compatibility issues, and disparities in computing capabilities, making it difficult and costly to connect and share information across diverse locations.
Innovation Solution
An information exchange component with standardized query and response interfaces and a data mapping tool is used to integrate headquarters ERP systems with subsidiary and supplier ERP systems, facilitating connectivity and data sharing through a data exchange interface, allowing for seamless data mapping and reconciliation across different systems.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If different ERP systems are implemented at subsidiary locations, then local business needs can be met with customized solutions, but system compatibility and data integration become difficult and costly
Solution Approach 1:
The patent introduces an intermediary layer between the headquarters ERP system and subsidiary ERP systems. This intermediary component handles the complexity of data format conversion, protocol translation, and communication protocol standardization, allowing heterogeneous systems to interact without direct compatibility issues. The intermediary absorbs the complexity of system diversity while maintaining standardized interfaces.
Solution Approach 2:
The patent implements a universal communication protocol and standardized interface that can work across multiple different ERP systems. The system provides multi-functional capabilities by supporting various data formats, communication protocols, and system architectures through a single unified approach, enabling one-to-many integration scenarios without requiring system-specific customizations.
2Device complexity
If centralized planning and control is used to design compatible systems, then data integration is simplified, but flexibility in meeting local business needs is reduced
Solution Approach 1:
The patent segments the ERP system into hierarchical levels with distinct responsibilities. The headquarters level handles centralized planning and control functions, while subsidiary levels maintain operational flexibility. The segmentation allows each level to optimize for its specific purposes while maintaining integration through standardized interfaces that enable data flow between segments.
Solution Approach 2:
The patent implements local quality by allowing each subsidiary to configure its ERP system according to local business requirements while maintaining compatibility with the headquarters system. The standardized interfaces enable local customization without compromising overall system integration, as each local system adapts to its specific needs while communicating through uniform protocols.
3Productivity
If standardized interfaces are implemented, then data sharing efficiency is improved, but system adaptability to different local requirements is reduced
Solution Approach 1:
The patent implements dynamic adaptability within standardized interfaces by allowing the system to automatically adjust data formats, field mappings, and communication parameters based on the specific requirements of each subsidiary. The standardized interface provides a stable foundation while incorporating dynamic elements that can adapt to varying local business needs without requiring interface changes.
Solution Approach 2:
The patent enables parameter changes within the standardized framework by allowing configuration of data formats, validation rules, and communication parameters to match local requirements. The standardized interface maintains consistent structure while parameters such as data types, field lengths, and communication protocols can be adjusted to accommodate different local systems and business needs.
4Loss of time
If diverse ERP systems are connected without standardization, then implementation speed is increased, but maintenance costs and complexity increase significantly
Solution Approach 1:
The patent implements preliminary action by pre-defining standardized interfaces, communication protocols, and data formats before subsidiary systems are deployed or modified. This preliminary standardization framework is established in advance, allowing new subsidiaries to be integrated quickly without requiring complex custom integration work, thereby reducing both implementation time and long-term maintenance costs.
Data Source
AI summary
The present invention pertains to an enterprise-wide enterprise resource planning (ERP) system, and in particular, to methods and systems for interfacing the enterprise-wide ERP system with ERP systems at subsidiary organizations. In accordance with an embodiment of the present invention, a method includes connecting to an enterprise data management system through a data base server, a web service and a data interface application programming interface (API) in a remote data system and through a data mapping component and an intermediate documents (IDOC) adapter in a data exchange interface using simple object address protocol (SOAP) messages and extensible markup language (XML) messages.