Changing association between TS and BS. Routing error.

[Former Member]

Hi experts,

I have an ABAP Technical System(TS_1) associated with a Business System(BS_1). I have changed the association between this TS_1 to another BS (BS_2) in SLD.

When activating the routing objects in Integration Directory we receive the error:

SAP system ID XXX client XXX already exists in service |BS_1|

Is there any way of breaking the old association in order to avoid the error. Do we have to delete all old routing first?

Regards

Gonzalo

[stefan_grube · Accepted solution]

> Do we have to delete all old routing first?

Yes. After life start you should never change the name of any business system.

If you want to change the name, you have to delete the old one first in SLD and ID.

Then you create a new one.

[Former Member · Accepted solution]

Hi Stefan,

I have done that, but the old routing is still in the directory. And this routing referred to the old BS. So I suppose that regarding the integration directory it have kept the old references so even if I have changed the objects in the SLD somehow it remains in the directory. So I have to delete old routings too. What do you think about?

Regards

Gonzalo

[RKothari · Accepted solution]

Hello,

Try Environment--> Clear SLD cache in Integration directory.

I guess, if you have new Business system in place than new routing which uses this BS must be created in intergration directory.

Edited by: Rahul Kothari on Jan 12, 2011 3:25 PM

[stefan_grube · Accepted solution]

> I have done that, but the old routing is still in the directory. And this routing referred to the old BS. So I suppose that regarding the integration directory it have kept the old references so even if I have changed the objects in the SLD somehow it remains in the directory. So I have to delete old routings too. What do you think about?

One idea (I do not know if this works)

You assign the old business system to a 3rd party technical system.

Then in ID you open the business system in edit mode, choose from menu 'adapter specific identifiers' -> get data from SLD.

When the R/3 system ID and client are removed, save and activate.

Then import the new business system and copy the routing.

You should consider to work with a Process Integration Scenario in ESR. Then you can easily delete configuration and generate a new one.

[Former Member · Accepted solution]

It worked!! thank you!

[former_member4985]

Hi Gonzalo,

This error, " system already exists in service", indicates that there are two Services in the Directory with

the same logical system name. Two services with the same (SID, client) pair are also not allowed.

It is necessary that logical system name as well as SID and client are unique.

See the SDN thread below for possible solutions to this:

This can be worked out either by using a Business Service or by creating another client on the system so that the LS name changes.

Regards,

Caio Cagnani