Expand +



IS-U Data Migration Workbench a.k.a. EMIGALL

by Jodee Hale-Schmid

August 18, 2010

Authored by Ashvinder Rana, Data Migration Lead, Utopia, Inc.

IS-U Data Migration is a broad topic of discussion. This blog post just covers the basic introduction of the Migration Tool without going into any technical details.

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

Hopefully, I will blog about the other aspects of IS-U Data Migration in the coming days too!!


An email has been sent to:

More from SAPinsider


Please log in to post a comment.

No comments have been submitted on this article. Be the first to comment!