Skip to Content

This document was originaly created in January 2013 by Kosana Avinash Reddy. Since the screenshots were not visible, I decided to rewrite the document, extend it with comments and include the screenshots, for the reference and easier use of others who need the procedure.

Objective


The main objective to load legacy data into SAP using EMIGALL distributed mode is to speed up the process when there is big amount of data to import. EMIGALL distributed mode also reduce efforts in scheduling jobs and easy to monitor them. Document is divided into following four topics:

  1. Converting Legacy file into Binary format (SAP format)
  2. Scheduling Distributed Import Jobs
  3. Changing scheduling parameters
  4. Monitoring Distributed Import Jobs

1. Converting Legacy File

     1.1 Go to transaction EMIGALL

     1.2 Double click on Migration Object for which we want to process import file

     1.3 Click Data Import

/wp-content/uploads/2015/10/1_3_812336.jpg

     1.4 In data import screen, go to menu: Utilities -> Convert migration file

/wp-content/uploads/2015/10/1_4_812337.jpg

     1.5 Enter Input directory (remember to put “\” at the end of input directory path)

     1.6 Enter input file name (including file extension)


     *Note: Input directory and file name should not be long. Sometimes, long file path and file name will cause system not to recognize file.


     1.7 Enter output directory (remember to put “\” at the end of input directory path)

     1.6 Enter output file name (including file extension)

     1.8 Check Migration company and migration object values

/wp-content/uploads/2015/10/1_5_812339.jpg

     1.9 After entering values, go to menu: Program à Execute in Background


     Note: Remember the output file path and file name. This will be used in schedule distributed import job.

/wp-content/uploads/2015/10/1_9_812340.jpg

     1.10 In Background Print Parameters, Press OK


     /wp-content/uploads/2015/10/1_10_812341.jpg

     1.11 Press Immediate

    

/wp-content/uploads/2015/10/1_12_812342.jpg

     1.12 After scheduling the job Immediately, press save

   

     1.13 Go to Transaction SM37 and monitor job till it finishes

2. Schedule Distributed Import

     2.1 Use Transaction EMIGMASSRUN to launch Administration & Monitoring Screen

     2.2 Press Create button

/wp-content/uploads/2015/10/2_1_812343.jpg

   

     2.3 Enter Company and enter Migration Object

     2.4 Press OK

/wp-content/uploads/2015/10/2_3_812344.jpg

    

     2.5 Enter Migration Path & file name (Output file path & file name which was used earlier to convert input file)

     2.6 Enter Error File (with file extension “err”

     2.7 Enter Input file (generated) with ‘&’. ‘&’ will be replaced by sequence number when file split happens

     2.8 Enter Error file (generated) with ‘&’.

     2.9 Commit Interval: This should be maintained only if this field is enabled for input

/wp-content/uploads/2015/10/2_5_812348.jpg

     2.10 Press Analyse button adjacent to file name. This will list of import statistics

/wp-content/uploads/2015/10/2_10_812349.jpg

   

     2.11 Compare import statistics with legacy file statistics (if shared)

     2.12 Validate number of data types (if there is a relationship). For example in device groups for Meter and Module – Every one record, will have two device data types.

     2.13 After Analysis, go back to main screen

/wp-content/uploads/2015/10/2_13_812350.jpg

     2.14 Define number of Background Work Processes which we intent to use

     2.15 Enter Mass Import file size

     2.16 Save the Distributed Import identification


     Note: Based on mass import file size, main file will be split into multiple files for parallel processing. This is the number of the master data records per file.

     2.17 Press Import Run


/wp-content/uploads/2015/10/2_17_812351.jpg

     2.18 Choose option – Start Later

     2.19 Change Start Date and Time well in future

     2.20 Press Distributed Import

     2.21 Distributed import job will be released

/wp-content/uploads/2015/10/2_18_812352.jpg

3. Change Job Scheduling Parameters

     3.1 Go to transaction SM37

     3.2 List jobs which were released

/wp-content/uploads/2015/10/3_2_812353.jpg    

     3.3 Choose the job whose status is “Released”    

     3.4 Go to menu: Job -> Change

/wp-content/uploads/2015/10/3_4_812354.jpg

     3.5 Press Step

/wp-content/uploads/2015/10/3_4_2_812356.jpg

     3.6 Place your cursor on the step and press change icon


     Note: Job is currently scheduled with user who has created distributed import job identification

/wp-content/uploads/2015/10/3_6_812355.jpg

     3.7 Change User to “MIGRATION” (or user id which has been setup for migration purpose)

     3.8 Press Save to save step

/wp-content/uploads/2015/10/3_7_812360.jpg

     3.9 Verify user for job is changed to “MIGRATION”

     3.10 Go back to main screen

     3.11 Press Start condition

/wp-content/uploads/2015/10/3_11_812361.jpg

     3.12 Press Immediately

     3.13 Press Save

/wp-content/uploads/2015/10/3_12_812362.jpg

     3.14 Press Save on job main screen

/wp-content/uploads/2015/10/3_14_812363.jpg

     3.15 Distributed Import job is now started with “MIGRATION” User id

/wp-content/uploads/2015/10/3_15_812364.jpg

4. Monitoring Job

     4.1 Use transaction EMIGMASSRUN

     4.2 Press “List of Distributed jobs” button and select job with your identification

/wp-content/uploads/2015/10/4_2_1_812365.jpg

/wp-content/uploads/2015/10/4_2_2_812366.jpg

     4.3 Go to Data for last import for statistics and monitor import job

/wp-content/uploads/2015/10/4_3_812367.jpg

     4.4 Go to Statistics for import runs for further details

     4.5 Double click on line item for further analysis

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply