SAP for Utilities Discussions
Connect with fellow SAP users to share best practices, troubleshoot challenges, and collaborate on building a sustainable energy future. Join the discussion.
cancel
Showing results for 
Search instead for 
Did you mean: 

EMIGALL: Import file transformation structure

mrio_espinheira
Participant
0 Kudos
916

Hi!

We are trying to use EMIGALL to migrate PARTNER data from various legacy systems to SAP. Our legacy systems can't create import files in the required binary format, only text files. The problem is that we don't know what's the structure of the text file to import. We've tried every structure possible, we use the REMIG_FILE_TRANSFORM report to convert the text file into another binary file, but when we try to see the data in the Import File Editor it shows nothing. We also can't migrate the binary file successfully.

Can anyone help us understand what is the structure of the file to use with the Import File Transformations?

Kind regards,

Mário Espinheira

5 REPLIES 5

Former Member
0 Kudos
544

For EMIGALL layout format, please select your object and follow menu option i.e. Utilities --> Structure Display --> Display Customer Display and click on 'Import File Layout' button. There you will see the required EMIGALL format for legacy flat file. The legacy flat file should always be in tab deliminated format. Once you recieve flat file from legacy system (as per EMIGALL layout format) then follow below steps :

1. Select your object and click on 'Data Import' button

2. Select menu option Utilities --> Convert Migration File

3. Select file location i.e. application/workstation

4. Provide path for flat file (from application/workstation)

5. Execute the transaction, it will convert received flat file into EMIGALL format.

6. Upload this converted data into SAP.

Hope these steps helps you to resolve your query.

0 Kudos
544

I know all the steps in EMIGALL that you mentioned. The only thing I don´t get is the Structure of the file prior to the conversion to Binary. I'm testing the PARTNER migration object with the following structure:

PARTNER CHAR10 (e.g. 0000000001)

MUSTER_KUN CHAR10 (e.g. 0000000001)

BU_RLTYP CHAR6 (e.g. 000001)

BU_TYPE CHAR1 (e.g. 1)

BU_GROUP CHAR4 (e.g. 0001)

If i want to migrate just one Partner, what would be the structure of the text file (prior to the transformation to Binary)?

Kind regards,

Mário Espinheira

0 Kudos
544

Its already mentioned in my reply "For EMIGALL layout format, please select your object and follow menu option i.e. Utilities --> Structure Display --> Display Customer Display and click on 'Import File Layout' button. There you will see the required EMIGALL format for legacy flat file." eg.

OLDKEY INIT SSSSSSSSSS TTTTTTTTTT UUUUUU S TTTT

OLDKEY BUT000 SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS TTTTTTTTTTTTTTTTTTTTTTTT

OLDKEY BUTCOM SSS T UUU SSS TTTTTTTTTTTTTTTTTTTTTTTTTTTTTT UUUUUUUUUU S TTTTTTTTTTTTT

OLDKEY BUTCOM SSS T UUU SSS TTTTTTTTTTTTTTTTTTTTTTTTTTTTTT UUUUUUUUUU S TTTTTTTTTTTTT

OLDKEY BUT0BK SSSS TTT UUUUUUUUUUUUUUU SSSSSSSSSSSSSSSSSS TT UUUUUUUUUUUUUUUUUUUU SS

OLDKEY BUT0BK SSSS TTT UUUUUUUUUUUUUUU SSSSSSSSSSSSSSSSSS TT UUUUUUUUUUUUUUUUUUUU SS

OLDKEY BUT020 S T UUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUU SSSSSSSSSSSSSSSSSSSSSS

OLDKEY BUT020 S T UUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUU SSSSSSSSSSSSSSSSSSSSSS

OLDKEY BUT0ID SSSSSSSS TTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTT

OLDKEY BUT0ID SSSSSSSS TTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTT

OLDKEY &ENDE

The legacy flat file should always be in tab deliminated format.

Please let me know if you are looking for any other information.

0 Kudos
544

Finally I got it

Using the example previously mentioned I created this text file, in tab deliminated format:

PAR001 INIT 0000000001 0000000001 000001 1 0001

PAR001 &ENDE

I then converted it to Binary format and was able to migrate it.

Thank you so much!

Kind regards,

Mário Espinheira

Former Member
0 Kudos
544

Hello Mário,

Shailesh is absolutely correct concerning the required tab stop character in the text file. I only would like to add that you might want to have a look at chapter 2.6.2 in where the file transformation process is described.

Kind regards,

Fritz