Emigall data import: Error message EM102

peter_podgorsek — Wed, 23 Jun 2010 09:59:41 GMT

Hi!

I am trying to import a simple "DOCUMENT" object. I took an in-system existing DOCUMENT and replicated it in a import file in emigall transaction. At data import I am getting error message EM102 stating:

"The higher-level object for LSK05, 700000020, does not exist"

"The higher-level object for LSK05, 1004700, does not exist"

...where LSK05 is a legacy system key, 700000020 is a business partner and 1004700 is a contract account.

What is a "higher-level object" in this case?

Thank you for your help!

Best regards,

Peter

Re: Emigall data import: Error message EM102

Former Member — Mon, 13 Sep 2010 23:47:22 GMT

Hello Peter & everybody...

Inside the EMIGALL tx there's a user's handbook that explains this problem:

"Higher-Level Migration Object"

The legacy system keys are replaced by the corresponding IS-U keys through Key and Status Management (KSM). The following techniques can be used in this process:

Specify a higher-level migration object in the field rule

The field in the automation data is supplied with the legacy system key of the specified higher-level migration object, and the value in KSM is replaced by its allocated IS-U key. To do this, the object with the specified legacy system key must have been successfully migrated first. If no IS-U key can be determined in KSM, then message EM 102 is written to the error log.

To access the note call the tx emigall - then choose company - IS-U migration - User handbook - general information - special technologies

Regards, JC

topic Emigall data import: Error message EM102 in Application Development and Automation Discussions

Emigall data import: Error message EM102

Re: Emigall data import: Error message EM102