Skip to Content
avatar image
Former Member

Use of Emigall for creation of masters in the production environment


The EMIGALL objects are normally used for migrating legacy master data and/or cut-over data before production environment is up.

I am contemplating to use EMIGALL object for creation of contract account masters in production environment. One more option that I have is to use standard BAPI for creating contract account masters.

Can anyone tell me whether it is proper to use EMIGALL object for day to day creation of master day in production environment. Is there any disadvantage or risk involved in it.

Kindly reply soon.



Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Oct 22, 2008 at 09:35 AM

    I've already used emigall multiple times to do delta migrations into an operational prod environment.

    Purely looking at the functionalities, it should/would/must be possible to use emigall as a master data generator. I just think you need to look into the requirements:

    • who will use it? end-user/application manager/...

    • what's the amount of data to be loaded?

    • what's the time window of the load? Day/night

    • how is the data supplied?

    As you know, emigall EATS system resources like mad, so using it during the day might not be preferable. emigall is also very picky about the file format, whereas in a custom report you can define the input structure yourself.

    On the other hand, the error handling and follow-up of emigall is great...

    Personally, I'd go for a custom report with a BAPI... It'll give you more flexibility than emigall.

    Add comment
    10|10000 characters needed characters exceeded