In charm, you will define the customized transport layer based on clients. It should not allow you to define diffrent transport layers for same client.
Now, If you had diffrent clients and you have multiple layers, yes still can use charm you can create multiple logical components and later on assign to charm project.
If you are still unclear about that, you can check below blog
you can define several customized transport layer for one and the same client.
This allows you to separate the objects and to assign these objects to transport packages and to transport layers. So you have then for transport between your DEV and TST systems for one and the same client within TST several customized transport layers.
It depends on your system type, if you want to use ABAP systems you have to follow the standard process with SAP and Z layers and then connect the domain with solman, however if you want to integrate with java only systems then yes you will go with z layer on your cts system.
Yes charm supports that however please be aware that if you have multiple consolidation layers with diffrent clients then you had to configure your logical components accordingly and include in the charm project now you can have diffrent projects for the same as it will make it easier for you defining the target component. However there will be only single delievery route to PRD.
"When you generate the transport tracks for your project, only consolidation routes that are assigned to the standard transport layer of the relevant development system client are taken into account. All other layers, also the transport layer "SAP" will be ignored by the transport track generation."
Unfortunately this sap note was released on 30 October 2009.
Is this the curent state (SAP Solution Manager 7.1 SP13/14) that only sap transport layer will be supported within Charm?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.