cancel
Showing results for 
Search instead for 
Did you mean: 

CTS transport cannot resolve target business system

Former Member
0 Kudos

Hello,

we are getting this error when trying to transport integration directory objects to production: "Obligatory transport target for business system XXX_DEV not found in System Landscape Directory".

We are on PI 7.30 and transport via CTS+ requests. It is a 3-tier landscape, DEV, QA and PROD. CTS Transport of integration directory objects from DEV to QA works fine. Also transport of ESR objects to production works fine.

We have 3 different SLD's (one for each tier). All have maintained the following as business system transport targets:

XXX_DEV -> XXX_QA

XXX_QA -> XXX_PROD

(this has been working fine for many years with file transport)

Can anybody confirm that we really need to setup XXX_DEV -> XXX_PROD as target in the SLD ?? This sounds very strange, because we do not want to transport from DEV to PROD, but from QA to PROD. If this is the only solution and the way CTS+ works, what would happen if we change an object on QA and want to transport this object and not the DEV one ?? Which object will CTS+ transport to PROD ? Will it always transport the dev object because the CTS+ request was created in dev ??

Or is there some misconfiguration on our side, which causes malfunction of transport from QA to PROD ? Why is the system working with source system XXX_DEV anyway when we move to production ? It should work with XXX_QA as source system.

There have been some similiar threads. e.g. this one, but there was no real explanation of the solution

We have switched from file transfer to CTS+ some time ago. With file transfer, we did not have the above issue.

Regards,

Christian

Accepted Solutions (1)

Accepted Solutions (1)

Harish
Active Contributor
0 Kudos

Hi Christian,

in cts+ transport dev version of object is attached and transported till prod.

so you need to maintain all business system in all three sld.

Dev sld

dev bs target is bs and prod bs

QA sld

qa bs source is dev bs and target is prod bs

PRod sld

prod bs and source is dev and qa bs

as you said the current setup is working for file transport, this is because you're transporting qa tpz tp prod,but in cts+ objects are only attached in dev.

hope this clear your doubt

Harish

Former Member
0 Kudos

thanks, this is indeed totally different compared to file based transport operations which are processed via QA into PROD. Only question then for me is why should we maintain any transport target for the QA business system at all (in case of CTS+), if it is never transported from there, but only from dev.

Probably this makes then only sense when using file based transport.

CSY

Harish
Active Contributor
0 Kudos

Hi Christian,

you are right, it is not required to maintain transport target of QA Business system. But it will be good to have in SLD to have overall architecture view.

regards,

Harish

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi

Yes the best practice is to create all the transport from DEV system and then import the same in quality and production.

Do not create transport from quality because in that case all the systems will not have the sync objects.

Add the production business system as the target of development business system and make sure you have created the groups in SLD for production,quality and dev.