Exception condition "Logsys for GUID changed"

[Former Member]

Hi all, I am working in SRM 4.0 with a cliente "DSR", in the past I had a backend system with name "SWD" and now I want to create a connection between "DSR" and "SWR" (SWR is a copy from backend system SWD).

I do all configuration of users, RFC connections, etc...

But when I run reports for product categories reply, I have this error: Exception condition "Logsys for GUID changed" in Inbound queue in SRM.

I have to run transaction BDLS in backend? in this case SWR or in SRM system??

Please this is urgent....

Thanks in advance

Rosa

[Former Member · Accepted solution]

yr sys names are somewhat confusing

so I use simple naming convention

You have set up srmDEV and eccDEV

it's working fine and now you want to set up QA

i.e. srmQA and eccQA

you can not copy completely srmDEV to srmQA like ecc.

because when you download cust objects (eg prod cat) and bus objects (eg matls)

a GUID is created in SRM and one more guid is passed to backend.

Now if you copy srmDEV to srmQA completely with master data (SAP_ALL basis profile for copy)

then this sychronisation of GUIDs is lost and SRM starts giving erroe message which you are getting.

So for SRM copy SAP advises to copy with sap_cust profile

establish new backend connection

and down load cust objects and bus objects again.

We had faced this issue and worked the mentioned way.

BR

Dinesh

[Former Member · Accepted solution]

Hi Dinesh, in this case I have an old connection between SWD (backend) and DSR (DEV SRM).

I have a new project and in this case I have to connect and transport all data between SWR (backend and copy from SWD with data) and DSR (same DEV SRM).

When I reply product categories I have this error....

I have to run BDLS transaction no?

But when I go to this transaction, I have to put New Logical System and Old Logical System, but I think in this screen I have to put Logical System for SRM, but in my project I change backend system not SRM system....

Thanks

Rosa

[Former Member · Accepted solution]

you have prod cat in srm from old backend

now the backend is new

and you are trying to download prod cat again?

can you remove the already downloaded prod cat & products from srm

and then start fresh download from your new backend?

you can use

reports

COM_HIERARCHY_DELETE_ALL

COM_PRODUCT_DELETE_ALL

this will ensure correct guids and sync

BR

Dinesh

[Former Member · Accepted solution]

Hi Dinesh, Can I have two product categories replicated in SRM?

Do I have to run this report obligatory?

Thanks

ROsa

[Former Member]

I ran BDLS transaction and all is OK now

[former_member206968]

Hi

You need to check table CRMPRLS in SWR or SRM.The error comes when you change the logical system names or assign different client.

I am not sure which system you need to check but I think its mostly related to ECC backend.

Thanks

Sanjeev

[Former Member]

Hi. I can remember having a similar issue after changing logical system before.

I think there was a standard SAP table that ended up stuck with a GUID from the previous system name.

I think in the end SAP told us to do a direct update to change it.

I think you need to be asking SAP this question.

Regards,

Dave.