Dump while creating Full Installation

[suneel_uggina]

Hi Gurus,

I am trying to create Full Installation through EMIGALL.

I am filling the following fields in the structure below.

DI_INT - DEVLOC

ANLAGE

EADAT

ACTION

DI_ZW - ZWNUMMERA

ZWNUMMERE

KONDIGRE

ZWSTANDCE

TARIFART

PERVERBR

EQUNRE

DI_GER GERWECHS

EQUNRNEU

I am getting the dump while saving data. The LOCK tables causes the dump.

Could you please help me which field do I need to pass data in order to avoid dumping.

Thank you,

Suneel.Uggina

[ashvinder_rana · Accepted solution]

Suneel, I have never had to enabled the locks in in EMIGALL. These were also left unchecked. The standard migration objects, are also delivered with those two indicators in the "via ksm" tab as unchecked. As mentioned earlier, I again suggest and recommend that you try to uncheck these lock indicators on via ksm screen and as well as disable "ObjLockMechanism" indicator (that you have now enabled). Try loading without these lock indicators set. More than likely, this should resolve your error.

Please also check for any data inconsistencies in either the Device data or the INST_MGMT data record. Without knowing the data and your system, it will be difficult to provide any further accurate guidance. If even after unchecking the lock indicators, you still have the ABAP dump, then you may want to search if there are any existing SAP Note regarding this error and perhaps open up an SAP message.

Regards,

Ashvinder

[suneel_uggina · Accepted solution]

Hi Rana.

Thank you very much for your support. As you suggested, I removed all the Locks. I am able to resolve the Dump issue after configuring COMMIT_SAVE as 'X' in Migration Object Interface level.

Thank you,

Suneel.Uggina

[suneel_uggina]

Hi Rana,

I tried as you suggested. I tried using"ObjLockMechanism" indicator is checked/enabled at the Migration Object Level. But Still I am not able to resolve the issue. Could you please let me know if I need mention any other check boxes that effects locking mechanism.

Thank you very much for your support.

Suneel. Uggina

[ashvinder_rana]

Hi Suneel, please uncheck the "Check lock" and "Lock Object" checkboxes on the Via KSM config screen. And then try again. This should resolve your ABAP dump error. Standard Migration object is delivered with these unchecked for KSM configuration.

Update - if you do want to use these lock indicators, then please ensure that the "ObjLockMechanism" indicator is checked/enabled at the Migration Object Level.

Hope this helps.

Ashvinder

[suneel_uggina]

Hi Rana,

Thanks for your reply.

1) The dump is related to PM ITOB: Buffer Management (Equipment).

While Creating Full Installation through transaction EG31 I am able to see the Equipment number in Lock table. When I am using Emigall I am not getting this Equipment Number in Lock Table.

2) I am able to create device through EMIGALL and I am using KSM way to transfer the device data for Full Installation Migration.

3) I have tried by providing value to ZWNUMMERE only. Still, I am facing a dump due to unable to lock the Equipment Number in Emigall.

Please let me know if there is any specific configuration to lock the equipment number while doing Full Installation through Emigall.

Thank you,

Suneel.Uggina

[ashvinder_rana]

Hi Suneel, to be able to help you better, need more information about the error:

1. What is the Abap dump error message?

2. Did you successfully create the higher level object DEVICE?

3. What data are you transferring in the EQUNR (equipment number) fields in the auto structures DI_ZW and DI_GER? Is it he Oldkey for the Device or just the device serial number or the material number?

Also, please note that you should not transfer any value to field DI_ZW-ZWNUMMERA. Use/map to field ZWNUMMERE. (You can retry your test with this one change if you want and see if that helps too).

Ashvinder