Skip to Content
Former Member
Mar 06, 2012 at 06:10 PM

Emigall says success, migration data not saved


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?