Initialization cannot be deleted in source system

[Former Member]

Hi All,

While doing an Init Load for the first time, the load failed sinc there was a dump in the source R3 system.

Then I corrected the error (a CMOD coding error) in R3 and tested it in RSA3. The simulation worked fine.

Now I am trying to do a second INIT for which I need to delete the first failed INIT (from Scheduler->Initialization options for this source->Delete).

It says "<b>Initialization for Data Source 0CA_TS_IS_1 Can Not Be Deleted in Source System...There was a dump in source system...Check the short dumps in the source system (/nst22 and /nsm21)...</b>."

Please suggest how to correct this.

Any help will be greatly appreciated.

Thanks

Vishno

[Former Member]

It could be because the data or say IDOCs are not posted properly so u would need to post them,either u can manaully trigger infopackage or go to BD87 AND PROCESS THE IDOCS

[Former Member]

Hi,

Check OSS Note 424848 and try to use the RSM1_CHECK_FOR_DELTAUPD program.

Hope it helps.

Bye,

Zsolt

[Former Member]

Hi,

It is better to make sure that the previous delta init is in red,even though it is red in manage sceen of Datatarget.You better do this status to red from Scheduler->Initialization options for this source-> double click on the status and make the status to red.

Or delete the row for this datasource in RSA7 in R/3.

With rgds,

Anil Kumar Sharma .P

[Former Member]

Anil,

Firstly thanks for ur reply.

As per your suggestions:

1. I made it red and tried to delete from the Info pkg screen but it didnt allow.

2. Then I tried to delete from RSA7. It dumped.

3. So I deleted the two entries in two tables ROOSPRMSC & RSSDLINIT

in R3 and .

4. I recreated, replicated the Datasource.

5. But now on trying to open a Info Pkg its dumping (Message type X). It also doesnt allow to create one.

Our BW DEV box is BW 700 Level 010 SupPack KW70010

I tried OSS notes 852443, 888677 and 872278 but didnt allow me to implement.

Please suggest.

Thanks

Vishno

[Former Member]

Hi,

Make sure do u have proper authorizations

goto SU53 to knw the last authorization check