No source system ID exists for source system (logical system)

[Former Member]

Hello Guys :

I Have a particular Case.

We arein an upgrade from BI 3.5 to 7 and to Sap NW 7

Our BI conlsutant inform us about this error in the monitor of Administrator WOrkbenck

Requests (messages): Everything OK

Extraction (messages): Errors occurred

Data request received

Data selection scheduled

17585 Records sent ( 17585 Records received ) ---> Yellow

Data selection ended

Transfer (IDocs and TRFC): Missing messages or warnings

Info IDoc 1 : Application document posted

Info IDoc 2 : Application document posted

Info IDoc 3 : Application document posted

Info IDoc 4 : Application document posted

Data Package 1 : arrived in BW ; Processing : Data packet not yet processed --Yellow

Processing (data packet): Errors occurred - RED

Update PSA ( 17585 Records posted ) : No errors --> Green

Transfer Rules ( 17585 Records ) : Errors occurred

Master data received. Processing being started.

Record 1 :No source system ID exists for source system (logical system) DEVCLT200

Record :No source system ID exists for source system (logical system) DEVCLT200

Too many error records - update terminated

Whe checked and tested the logical systems and are OK , this is to weird because everything elseis working fine about logical systems.

Regards

[Former Member · Accepted solution]

I dont have so much experience with BW. Could you explain how do i "repeat" the load ?

Edited by: Marcos Damián López on Oct 21, 2009 10:39 PM

[Former Member · Accepted solution]

Delete the failed request (red request) from the target and goto the corresponding infopackage schedule it.

your BI consultant can do this I guess.

[Former Member · Accepted solution]

JE JE

We already done that 5 times.

and always the same.

[Former Member · Accepted solution]

so what???

jejeje and tell me what is the table name?

i think that you BI consultant should be supporting to you, but you could try to modify in RSA1 the logical conections, and then you should erase the infopackage and do it again.

[Former Member · Accepted solution]

0gl_acount_attr

[Former Member · Accepted solution]

sorry my friend i dont know about BW , but i hope helps my coment XD , hey guys help to marcos ¡¡¡

[Former Member · Accepted solution]

Marcos, you should to enter on bd54 and check the logical systems then you should go to rsa1 transaccion , tool-> asg source systems etc..-> check the and assig the source system, then you should to enter in RSA1 again and the left side search sorce system menu there you must restore the logical source system

thanks regards.

[mohit_agrawall]

HI All,

I faced this very same issue after copyback from production. I checked in RSA1 (Tools -> Assign Src system ID..) and all the systems were already assigned the IDs.

In the details tab of Monitor window I saw that the error occurred during Processing so I activated the Transfer structure and then repeated the failed step. I went smooth then.

You may like to try that and like this post if it works.

Thanks

Mohit

[Former Member]

Thanks but i already done that...

Regards

[Former Member]

Do you see any Short Dumps in ST22 and system logs in SM21 related to this error?

[Former Member]

I readed a short Dump that indicates "Message_type_X"

Regards

[Former Member]

The same short dump we are also getting in our Project but when we repeat the load it is going to successful. You may try repeating the load.

Veerendra.

[former_member197610]

Hi,

Check the source system assignments in Datawarehousing Workbench.

Tools-Assgnt of srce systen - srce system ID.

Hope this helps.

[Former Member]

We alredy checked that... my systemn was tested and cheked and its ok.

[Former Member]

Hi Marcos,

Below note may help you.

Note 336351 - Maintaining the source system ID

Veerendra.