1.

1 Introduction to the IS Migration Workbench A migration workbench in an SAP system

usually represents the third phase in the extraction, transformation and loading process (ETL
process). It is a tool to support the loading or importing of data into the SAP system. SAP has
many migration workbenches like batch input, the Legacy System Migration Workbench
(LSMW), or the Data Transfer Workbench (DX-WB). The IS Migration Workbench completes
these known migration tools. The IS Migration Workbench supports the initial data load of
business master data and transaction data into an SAP system; it also supports the
synchronization of data during a phased data migration process. The IS Migration Workbench
represents an open and documented interface based on business objects. A data migration
using the IS Migration Workbench ensures high quality and consistency of the migrated data.
Direct input modules create or change all data in the database, instead of updating the
database directly. Almost the same code is executed during data migration as during the
creation or change of information using dialog transactions. This includes the available check
and verification routines of the respective dialog transactions. . The IS Migration Workbench is
available for data migration into the following SAP industry solutions: o SAP Contract Accounts
Receivable and Payable o SAP for Utilities o SAP for Telecommunication o SAP for Insurance o
SAP for Public Sector For data migration into these SAP industry solutions, the IS Migration
Workbench is the primary load tool used.
1.2 Proven Concepts In the IS Migration Workbench many concepts and techniques are
implemented based on experience in migration projects from earlier SAP ERP releases like R/2
and R/3. These are: o Migration of business objects instead of direct updates in the database
tables o Definition of flexible field rules that can be customized easily o Generation of load
programs including the defined field rules o Display and print of the interface structure to
support the creation of import files o Execution and monitoring of the data import of high data
volumes o Administration of import files o The following additional functions: x Administration
of all keys and relationships between objects in the legacy system and SAP system x Usage and
transfer of required fields instead of transferring all fields of an interface structure x
Comprehensive and detailed migration specific documentation of migration objects, interface
structures and fields x Generation of test data with an import file editor specifically for a
support in the test phase x Definition of own migration objects

IS-U Data Migration Workbench, more commonly referred to as EMIGALL Tool these days, is the
mandatory Data Migration Tool for SAP’s IS-UT or the CRM&B data model. This can be accessed via t-
code EMIGALL. Essentially, this tool is utilized for the data transfer from the legacy system(s) to the IS-UT
or the CRM&B application.

This tool represents migration objects as logical units corresponding to the IS-U business objects instead of
database tables. In other words, data is not represented and inserted into the dB table by table; instead all
table updates required to create a business object entity (e.g., business partner) are executed together.
This is achieved by utilizing the standard IS-U function modules that correspond to the dialog
transactions/functions. This also ensures optimal data consistency check for all the required transactional
validations. These function modules are direct input based and not batch input. Thus, avoiding the
transactional screen processing and thereby, results in improved performance.

The migration objects are represented in a predefined migration hierarchy and the data transfer should be
executed in this hierarchical order. For example, contract account cannot be migrated unless a zero-error
data transfer or, an acceptable conversion su ccess threshold is achieved, for its higher-level
object business partner has been accomplished. The picture below gives an overview of most of the
migration objects generally utilized across various utility implementations. This list could be slightly different
from project to project.

Key and status management is a key component of the IS-U Data Migration Workbench that facilitates the
maintenance of cross-reference between legacy system keys (external) and the newly generated (internally
or externally) SAP object keys. Essentially, each data object will be transferred with a unique OLDKEY
(easily identifiable legacy system key). And during the data transfer, for each of the successful conversion,
this OLDKEY to NEWKEY (internally / externally generated SAP number) relationship is updated and
stored in the KSM table that is maintained dynamically within the workbench. It also ensures the smooth
data transfer in the predefined hierarchical order. Wherein the higher-level object is referred using its
OLDKEY when converting the lower-level objects that are dependent on it.

Subsequently, the migration function modules will go “fetch” the corresponding NEWKEY from the KSM
table to correctly associate the lower-level object to its higher-level object.

Of course, the scope of ISU Migration Workbench is not just limited to the above.

The tool, in fact, allows for:

 Customization of migration objects th at minimize the ABAP coding typically required for various data
conversion programs
 Dynamic generation of migration object import programs
 Distributed data import
 Import job monitoring
 Detailed error analysis and correction
 Customization for performance optimization during data imports