Error: Exception condition "GUID_FOR_LOGSYS_CHANGED" raised

[Former Member]

Hi,

We recently did a client refresh/copy of one of our backend (R/3) systems. So I checked and re configured (where necessary) the following tables in R/3:

CRMCONSUM

CRMSUBTAB

CRMRFCPAR

CRMPAROLTP

I only had to recreate the logical system for CRMRFCPAR, but when I try to replicate Master data, I now get the following message?

<b>Exception condition "GUID_FOR_LOGSYS_CHANGED" raised</b>

Any suggestions on how I can rectify the GUID?

[Former Member]

HI Shayne,

Pls check the <b>table crmmlsguid in srm</b>, u have to remove the entry in case the logical system is different from your backend logical sys which u r using for replication.....Thanks

Debu

[Former Member]

Hi,

Pls see the foll notes:

Note 588701 - Change of the logical system name in R/3 Backend system

Note 765018 - Problems with logical system during data exchange

BR,

Disha.

Pls reward points for useful answers.

[yann_bouillut]

Hi,

Also, read the following thread even if for CRM...(2 pages)

https://forums.sdn.sap.com/click.jspa?searchID=4060901&messageID=3267006

Kind regards,

Yann

[yann_bouillut]

Hi,

I guess you also have changed other table content...

Did you use BDLS ?

Kind regards,

Yann

[Former Member]

Hi Yann,

Nope, haven't changed any other tables and not sure what BDLS is??

[yann_bouillut]

Hi,

BDLS enable you to change the logical system name in your system.

of course, as you can imaginate, this feature has to be used carefully.

You will find OSS note dealing with transaction BDLS.

Kind regards,

Yann

[yann_bouillut]

Hi,

Also read the followng threads :

https://forums.sdn.sap.com/click.jspa?searchID=4061447&messageID=1549224

https://forums.sdn.sap.com/click.jspa?searchID=4060901&messageID=3267006

Kind regards,

Yann

Message was edited by:

Yann Bouillut

[Former Member]

Hi,

See the foll note for BDLS:

Note 995771 - System Landscape Copy for SAP SRM 4.0 and 5.0

BR,

Disha.

Pls reward points for useful answers.

[Former Member]

Hi to all,

OK a few more questions:

I've read the notes mentioned and I can confirm that I get symptom 2 for both the notes i.e. the error occurs in the inbound queues in EBP.

Only our R/3 system was copied (Prod to Dev) so does this mean that the BDLS changes only have to be done in R/3 then?

[yann_bouillut]

Hi,

If the logical systems are ok on SRm side then Yes .

Please check that the logical system pointing on R/3 on the SRM side are correct

Kind regards,

Yann

[Former Member]

> Hi to all,

>

> OK a few more questions:

>

> I've read the notes mentioned and I can confirm that

> I get symptom 2 for both the notes i.e. the error

> occurs in the inbound queues in EBP.

>

> Only our R/3 system was copied (Prod to Dev) so does

> this mean that the BDLS changes only have to be done

> in R/3 then?

Hello Shayne,

We have the same problem - have you solved yours? Can yuou advise what was the problem?

kind regards,

Robert