ChaRM Proof of Concept

[Former Member]

Hi All,

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

501>502 Delivery

these three worked fine to get the basic ChaRM setup working with maintenance project 1.

I added:

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.

regards,

Jason

[Former Member · Accepted solution]

Hi Jason,

you cannot use SAP transport layer twice for the same system, thats correct.

But do you have any other problems beside this? Because your config should work the way you described.

Regards

[Former Member · Accepted solution]

Hi Christian,

well my ChaRM Check is throwing a few errors which usually have to do with the TMS being setup incorrectly.

"No consolidation system found for SMD600 and "No track for project... for log. sys SMD/600"

My TMS knowledge is a bit lacking here. The SAP and ZSM1 are both consolidation routes, but I'm not exactly clear when and how each one is used. Should I just create another consolidation transport route? i.e. ZSM3 > 601 to go along with the ZSM2 > 601 I already created? Is it really just enough to have two consolidation transport routes?

thanks,

Jason

[Former Member · Accepted solution]

Hi Jason,

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.

Regards

[Former Member · Accepted solution]

ok, that was my understanding of the transport routes as well. I too think it is the SAP layer missing and I didn't think just making another Z one would make it work. My thinking was I needed another SAP layer, but I didn't think that was possible on the same system.

I'll see if I can swing getting another system to act as the second DEV and QAS. I think it would be pretty straight foward from there.

Thanks for the discussion.