Emigall says success, migration data not saved

[Former Member]

Hi all,

I am pushing legacy device data using Emigall. When I execute, I get no errors, and I DO get a key saved in KSM as if it saved the row. But when I double click the key SAP generated, which should take me to the device created, I get an error "Runtime object with IS-U key <key> has not been defined".

The key is not in EQUI, it is skipped in the sequence so it was obviously used when I executed the migration.

I have never actually gotten a key back as a result of migration, and not had the row actually stored, so I'm stumped.

Anyone have any ideas about this?

Thanks

CN

[Former Member]

Hi,

Did you uploaded data in test run mode? If yes, then you need to delete values from KSM table for object DEVICE and reprocess the file in actual run mode.

Regards,

Avinash

[Former Member]

Hi Avinash, thanks for your input.

Good thought, but no I did not execute as Test Run. Actually when I execute in Test Run it doesn't store a key in KSM.

Any other thoughts?

Thanks,

CN

[Former Member]

Hi Cathy,

The device number.. is this getting generated externally (meaning are you passing this as EQUNR/SERNR/GERNR) in the file or is it being generated internally? I believe that this number comes up in the New Key column of TEMKSV.

Also, have you kept the Equipment Type as ISU Equipment?

Thanks,

Sachin

[Former Member]

Hi Sachin,

Thanks for the input. I am using internal numbering, so what's being returned is just the next incremental number, which is correctly sequenced.

I'm using equipment type of Meters, which is configured under the IS-U Equipment Categories, and has the IS-U data indicator checked. Is this what you are referring to?

I can create the same meter manually, using the same input data into the same fields, in IQ01 and everything is saved properly.

[Former Member]

Hi Cathy,

I think the GERNR/SERNR field is not getting populated correctly. Can you check the value of these fields for the manually created device and the device created through EMIGALL, in the EQUI table. Do add 0's before EQUNR so that the total length is 18.

I am currently jobless, so I do not have a system to check

Thanks,

Sachin

[Former Member]

Hi,

We faced with similar issue where we got the SAP key back and was stored in KSM table. However, we were not able to display device. There was an entry in EQUI table but EGERH table did not had an entry. Later when we validated, we found, we were not passing one of the valid from date (which was relevant for EGERH) which was causing problem.

Request you to import your data in debug mode and ask your developer to let you know the exact message. Also, you may re-visit your data which you are passing.

Regards,

Avinash

[Former Member]

Hi Sachin,

We are using internal numbering for GERNR/SERNR - and it is getting populated correctly (the expected sequence #) on a manually created deivce.

Just for grins I threw in a value for GERNER and SERNER in my Emigall file, expecting an error to come back saying it is internally generated. But Emigall still acts happy as if it added the meter (which it did not). No error coming back about those fields being populated. That seems strange to me too.

Thanks

CN

[Former Member]

Hi Cathy.

You can check is the CONTR automatic structure has been enabled and correctly set (CONV, INDIV and UPDATE should have EMG_MARKED fixed value, and COMMIT should have EMG_COMMIT_S value).

Hope it helps!

Marko