Browse Prior Art Database

SAP Data Synchronization Mass Control Data Conversion Solution for Configuration data and associated Master Data and Transactional Data.(The Configuration data typically represents the business data standards that a company puts into place either formally or informally.)

IP.com Disclosure Number: IPCOM000013957D
Original Publication Date: 1999-Nov-01
Included in the Prior Art Database: 2003-Jun-19
Document File: 3 page(s) / 80K

Publishing Venue

IBM

Abstract

SAP R/3 Multi-Instance Data Synchronization and Data Conversion Solution. A solution is disclosed based upon a custom developed SAP R/3* data conversion tool and the associated expertise which combine to provide a standard mechanism for synchronizing configuration, master and transactional data across SAP production instances. This mechanism establishes a level of commonality across SAP systems and effectively retrofits existing and non-concurrent data models across SAP instances. The conversion tool systematically searches for all occurrences of the identified values and, following the analysis, the synchronization via the conversion process takes place. For a large multi-national corporation, it is typical to have several SAP production instances deployed. It is common for different basic configuration sets to be implemented across these systems. These configuration sets consist of enterprise organizational structures, units of measure and other basic business process definitions. Once these configuration sets are put in place, all subsequent master data (customers, materials, vendors, master chart of account listingsā€¦..) include this configuration data within their definition. Additionally, all corresponding transactional data, which is associated with this master data, carry the values forward. Hence, configuration set data permeates all subsequent master and transactional data of an SAP production instance, creating large amounts of data based upon the individual configuration set. However, it is often necessary to introduce common data values across these multiple SAP production instances for several business reasons. These business reasons include sharing data across these instances via Application Linking and Enabling (ALE*), introducing data standards, organizational changes or to consolidate the business operations onto fewer SAP instances. When the business need arises to introduce common data values, the issue of how to synchronize the data across these operational systems surfaces. The solution described here provides a unique approach at data conversion and synchronizing multiple SAP instances so that sharing data between the instances is simplified or that R/3 system consolidation is possible.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 52% of the total text.

Page 1 of 3

  SAP Data Synchronization Mass Control Data Conversion Solution for Configuration data and associated Master Data and Transactional Data.(The Configuration data typically represents the business data standards that a company puts into place either formally or informally.)

SAP R/3 Multi-Instance Data Synchronization and Data Conversion Solution.

A solution is disclosed based upon a custom developed SAP R/3* data conversion tool and the associated expertise which combine to provide a standard mechanism for synchronizing configuration, master and transactional data across SAP production instances. This mechanism establishes a level of commonality across SAP systems and effectively retrofits existing and non-concurrent data models across SAP instances. The conversion tool systematically searches for all occurrences of the identified values and, following the analysis, the synchronization via the conversion process takes place.

For a large multi-national corporation, it is typical to have several SAP production instances deployed. It is common for different basic configuration sets to be implemented across these systems. These configuration sets consist of enterprise organizational structures, units of measure and other basic business process definitions. Once these configuration sets are put in place, all subsequent master data (customers, materials, vendors, master chart of account listings.....) include this configuration data within their definition. Additionally, all corresponding transactional data, which is associated with this master data, carry the values forward. Hence, configuration set data permeates all subsequent master and transactional data of an SAP production instance, creating large amounts of data based upon the individual configuration set.

However, it is often necessary to introduce common data values across these multiple SAP production instances for several business reasons. These business reasons include sharing data across these instances via Application Linking and Enabling (ALE*), introducing data standards, organizational changes or to consolidate the business operations onto fewer SAP instances. When the business need arises to introduce common data values, the issue of how to synchronize the data across these operational systems surfaces. The solution described here provides a unique approach at data conversion and synchronizing multiple SAP instances so that sharing data between the instances is simplified or that R/3 system consolidation is possible.

The key elements to the solution are the custom developed R/3 programming data conversion tools and the associated expertise to invoke the synchronization of SAP systems. The expertise is necessary to guid...