cancel
Showing results for 
Search instead for 
Did you mean: 

Transport does not map business systems

Former Member
0 Kudos

Hello,

we have a problem when transporting XI configuration objects (via normal file export/import, not CMS). In the SLD, we have configured business systems

T01CLNT010, belongs to group dev and has transport target PROCLNT010

T01CLNT020, belongs to group dev and has transport target PROCLNT020

the strange thing is the first business system is not converted correctly to the prod business system after transporting the XI config from XI dev to XI Prod. For the second business system, that works fine. I compared the entries in the SLD, both look fine. But one does not work, the other does.

For the one that does not work, the transport goes fine, does not show any error, but just does not convert the name. (which of course will lead to an error when trying to activate the objects, because T01CLNT010 does not exist in XI prod). So it seems it cannot find the SLD transport target for that object.

Does anyone know how XI exactly finds out how to convert the business system while transporting it to production ? How does it find the connection between the XI business system object and the corresponding SLD entry ? Just by name ? Or is some kind of internal GUID used which may have been broken ? Can I see that anywhere ?

Is it safe to re-associate the SLD business system to the XI business system in the XI integration builder ? Or are dependent objects (e.g. receiver det.) then lost ?

CSY

Accepted Solutions (0)

Answers (5)

Answers (5)

Former Member
0 Kudos

Problem is solved. There existed a service on production which had the same name as the business system. This confused the SAP transport manager. SAP says that will be fixed in SP 22. Until then, make sure you do not have services with same name like business system.

Reason for that service was that we receive ALE#KU idocs. Solution for that is to associate the business system to the needed sender partner in XI, but not create the same service name !

CSY

Former Member
0 Kudos

we have only one SLD for XI dev and prod, so no problems with multiple SLD's.

Any more hints ? The doc links did not show anything I did not know yet.

CSY

Former Member
0 Kudos

Hi,

At least having Two SLD's (One for DEv & One for PRD)is good practice

And Configure Transport groups & tarnsport Targets to get reflect the Business systems

REgards

Seshagiri

prateek
Active Contributor
0 Kudos

Does anyone know how XI exactly finds out how to convert the business system while transporting it to production ?

The only thing that matters here is properly defining the Transport Targets.

How does it find the connection between the XI business system object and the corresponding SLD entry?

Not sure about this but I think the name in the transport target would suffice for this requirement. Also, make sure that the groups are properly defined and target SLD has all business systems properly maintained.

Is it safe to re-associate the SLD business system to the XI business system in the XI integration builder ?

How will you be doing this re-association? If you are thinking of changing the Business system name in ID manually, then it would mean almost complete development in ID.

Regards,

Prateek

SudhirT
Active Contributor
0 Kudos
Former Member
0 Kudos

this is just a guess...

is the business system that needs to be mapped exists in SLD of Prod...Check the target business system first in Prod...

VijayKonam
Active Contributor
0 Kudos

Is the SLD same for both the systems? If not you need to create the target system in the target SLD and the association and system in source SLD.

You might want to refer to this -

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/soa/soa-management...

VJ