ChaRM Proof of Concept
I need some help with a ChaRM Proof of Concept TMS configuration.
I have this setup that I would like to make work.
logical component 1: DEV1 > QAS1 > PROD
logical component 2: DEV2 > QAS2 > PROD (this is the same prod as above)
I have ChaRM working fine with a maintenance project with logical component 1 assigned. My issues are arising when I try to have another maintenance project with logical component 2 assigned. The goal is to have maintenance project 1 for dev and customization on a yet to be decided maintenance cycle. And maintenance project 2 for production support on a weekly maintenance cycle.
These are all dummy Solution Manager clients numbers.
DEV1 is client 500
QAS1 is client 501
PROD is client 502
DEV2 is client 600
QAS2 is client 601
My TMS is set up with the following:
SAP > 501 transport
ZSM1 > 501 transport
these three worked fine to get the basic ChaRM setup working with maintenance project 1.
ZSM2 > 601 transport
601 > 502 delivery
I can't add:
SAP > 601 transport. It tells me the SAP transport layer is already being used. (above to 501)
My maintenance project 2 is having issues being setup because the TMS is not reflecting the DEV 600 > QAS 601 > PROD 502 system landscape.
Anyone have any experience on how to setup the TMS to test this setup? I imagine this would be easier with seperate boxes, rather than having client for 2 DEV, 2 QAS and 1 PROD on the same one.
Christian Kaunzner replied
consolidation routes are used from DEV to QAS and delivery is used for the rest (i.e. QAS to PPD or PPD to PRD). SAP layer is used to transport SAP obejcts (objects in SAP namespace are assigned to packages which use the SAP transport layer) and everything else uses Z transport layer.
I am not sure but probably it is the SAP default layer which is missing here (since you can assign one per system only). The system might check this.
You should try to get at least one other system and create a few clients there for your "second" landscape.