ChaRM: Several Transport layers

Hi!
We would like to implement ChaRM for the 3 tier landscape (DEV:100 --> QAS:200 --> PRD:100) with several transport layers and transport routes:
a) u201CZDEVu201D u2013 Standard transport layer
b) u201CSAPu201D u2013 SAP transport layer
c) u201CYCSTu201D u2013 transport layer for internal customizing
d) u201CZEXTu201D u2013 transport layer for external vendor
The problem we have is that transports within ChaRM are supported in the standard transport layer of each client.
It means that the transport requests of transport layers u201CYCSTu201D and u201CZEXTu201D that are non-standard transport layer will be ignored by CHaRM.
Has some one of you experience with configuration of ChaRM with several transport layers and can give an advice what is the best solution in my case?
Possible solutions:
a) Creation of additional clients in DEV system and assigning them other standard transport layer (e.g. DEV:200 gets u201CYCSTu201D, DEV:300 gets u201CZEXTu201D as standard transport layer)
Then it should be possible to create three maintenance projects:
1) MP1: (DEV:100 --> QAS:200 --> PRD:100) with transport layer u201CZDEVu201D
2) MP2: (DEV:200 --> QAS:200 --> PRD:100) with transport layer u201CYCSTu201D
3) MP3: (DEV:300 --> QAS:200 --> PRD:100) with transport layer u201CZEXTu201D
b) Migration of all the non-standard layers to standard transport layer.
c) Separation of ChaRM and none-ChaRM transport layers (TMS)
It would be great to get some feedback/suggestions/input
Thank you very much indeed!
regards

Hi
Sorry for my ignorance but the Transport/Routes/Layer are releated to the Development Class.. and ChaRM dont take in count this...
At the end you have 3 Development Clients...100/200/300..you need to create 3 project..
thxs
Wence

Similar Messages

ChaRM: usage of several transport layers in different maintenance projects

Hi!
I have heared on SAP TechED about the following possibility:
it should be possible to have several maintenance projects with different standard transport layers.
Can some one of you confirm or reject this statement?
Our problem is we work in same client in DEV system and transport in same client in QAS system and have several transport layers. All of them should be used by ChaRM.
Other question:
which new functions will be come with SPS 18 in ChaRM?
Thank you very much!
Holger Thomasson

Hi
Sorry for my ignorance but the Transport/Routes/Layer are releated to the Development Class.. and ChaRM dont take in count this...
At the end you have 3 Development Clients...100/200/300..you need to create 3 project..
thxs
Wence

ChaRM with several transport layers/routes

Hi!
We have a very comprehensive transport landscape where more than one transport layer is necessary.
The reasons therefore:
we implement none-SAP software and need an extra transport layer therefore
the developers still need an extra transport layer because of they assigned them their packages
Currently we have one and the same client in DEV system where all the transport layers reside.
Now we are thinking to implement ChaRM for all the transport layers.
1) Approach of splitting transport layers and working with different DEV clients
We split the transport layer and assign them the different standard layer
transport layer ZDV1: client 100
transport layer ZDV2: client 200
transport layer ZDV3: client 300
Question:
Is that possible to have here one maintenance project with more that one DEV system
(DEV:100, DEV:200 and DEV:300)?
Any helpful information will be very appreciated.
Thom

Hi Thom..
transport layer ZDV1: client 100
transport layer ZDV2: client 200
transport layer ZDV3: client 300
Why you have 3 Transports Layer???...
if you have
DEV100                QAS100    PRD100
DEV200
DEV300
Usually you have only 1 Layer from DEV100 to QAS100 (Consolidation Type)
To move from DEV100 to DEV200/300 use SCC1
IF you have
DEV100     -
> QAS100   -
>   PRD100
DEV200                QAS200
DEV300
You create 1 transport group
DEV100 -
> QAS100 ---> PRD100
                 |-->QAS200
Thanks
Wen

ChaRM with several transport layers

Hi!
We would like to use Solman ChaRM approach.
According to SPRO-documentation ChaRM only supports consolidation routes from standard transport layer.
We have besides the standard transport layer other transport layer and have the following question
1)What will happen when the developer try to change and import into QAS system object assigning to none-standard transport layer?
1a) ChaRM does not allow to change this object and the appropriate pop up window comes up
1b) ChaRM integrate this transport layer as standard transport layer
Any helpful information will be very appreciated
Thank you very much!
regards
Thom

Hello Thom,
I think, your question is almost independent from CHaRM. This is handled by the transport management system (TMS). If your developer changes the object assignment to a transport layer, and there is a transport track for this layer to the (same) QAS it should work. But if this QAS is not configured in CHaRM as a target system (in SOLAR_PROJECT_ADMIN), SolMan will probably raise an error message.
Also if the transport layer assignment / dev package not valid for this transport track, you will not able to release the transport -> SolMan is just using TMS mechanism and this will bring up an error message in CRMD_ORDER.
Unfortunately you can't see the transport logs in CRMD_ORDER directly, so the answer to 1a) is: In case of trouble releasing the transport you will get an error, but not the full error message.
1b) ChaRM cannot change a transport layer to a standard transport layer, this must be done using STMS on the transport daimn controller.
Regards,
Holger

ChaRM: Standard transport layer

Hi!
I have one question regarding transport layers for usage of ChaRM.
Which standard transport layer does the ChaRM need?
a) "SAP" transport layer
2) standard transport layer "ZDEV"
What will happen when one of this (SAP or ZDEV) will be mised or used outside of ChaRM?
Thank you very much!
regards
Thom

Thom Heinemann wrote:>
>
> Which standard transport layer does the ChaRM need?
> a) "SAP" transport layer
> b) standard transport layer "ZDEV"
Anand: ZDEV should be the standard transport layer......
All SAP standard objects will only follow SAP transport layer......irrespective of whatever standard layer is mentioned.....
> What will happen when one of this (SAP or ZDEV) will be mised or used outside of ChaRM?
Anand: Little more clarity is desired on this query....can you please be more specfic about what you meant..
Inspire ppl by rewwarding !!
Regards,
Anand....

ChaRM without transport

We'd like to implement ChaRM without transport management yet. But we still need to create transport requests from the UC, so we do need to create a maintenance cycle. Or is there a way to create UCs with transport requests without project and maintenance cycle?
However, upon creation of MC full configuration of the TMS is required! All transports to QAS and PRD are going to be done manually. Do we still need to configure the transport routes?

So, I need to create two consolidation routes for the two layers from DEV to QAS and one delivery route from QAS to PRD ADDITIONALY to the already existing transport routes and this won't be a problem for the existing configuration?
> "Create the consolidation transport routes to SMM:200, transport route must be CLIENT SPECIFIC for the use in Charm scenario, this is real important!"
If I change the transport strategy of the three systems to "client specific", won't this require change of ALL other transport routes that have already been defined for those systems?
> "RFC connections from Solution Manager to DEV, QUA and PRD system, donu2019t forget to create also SM_..._TMW connection to all satellites DEV, QUA and PRD, to clients with customizing, test and production roles, in our example, we will create the RFC connection to 100, 200 and 300. Also to client 000 of all the involved systems, DEV, QUA and PRD systems in our example."
Does this mean I have to have an user in all three systems including in all three 000-clients?

Transport Layers and sharing of transport directories

Hello Experts,
We are on R/3 4.7 Enterprise extension set 1.10 with oracle 9i .
In a three tier architecture in R/3 with development , quality and production , how do we assign transport layers and how many transport layers do we need at the time of TMS configuration ?
Secondly in our R/3 three tier landscape , we hv transport directories (trans ) on every system on all the three systems ,then how are they shared with each other , i mean on wt basis do they recognise each other and transport continues frm DEV to QUA and then to production
Requested to revert at earliest as this is very urgent . points guaranteed .
Regards,
Somya

Hi ,
1) sap and Zdev are transport layers....which will be assigned by default when you configure TMS.
what does SAP and ZDEV do ?you can take it like this..standard programs..will go through sap...and customized like (Z or Y programs )will go thorough Zdev path.
the program routing is taken care automatically..(just for your info)
you never need to define transport layer between QA and PRD unless you want add one more Sandbox system for more quality testing..(normally in 3 system landscape you dont configure transport layers between QA and PRD
2) as of now in your scenerio ..its not being shared..
if you plan your DEV as transport domain controller..then in QAS system execute STMS-->system Overview >QAS double click>Communication (change transport domain to Domain controller transport domain) and also transport tool >transdir>(should poing to
<domain controller>\sapmnt\trans)
save the changes..
on the domain controller . in TMS you will see a system waiting for inclusion onto domain ..approve that..and follow the same procedure to add PRD system also..
then all the systems will share the same transport directory..
(Caution: once you setup the landscape like this ..changes to any system using STMS like QAS and DEV has to be done only on Domain controller.)
Cheers
Kamal

ChaRM - Import Transport Request - Production

Hello Dears,
I have some issues/doubts with my ChaRM process.
- Before the u201CImport Transport Request (Background)u201D on QAS environment, if I change the status to u201CGo Liveu201D in SCMA, I can u201CImport Transport Request (Background)u201D on PRD environment, without any verification in the support message.
Example: If the support message was in u201CTest statusu201D, on SCMA I can import to production environment. Wouldnu2019t have be a check or lock to not allow this action?
- Exist any way to select the requests to import to PRD environment?
Regards to all,
FS
Edited by: Fabio Sato on Jun 15, 2009 7:29 PM

Fabio
you have several options to schedule transports for like every hour
TMS jobs must be scheduled via STMS. To do this:
1) Goto transaction STMS
2) Select 'Overview --> Imports'
3) Double click on the system you wish to schedule the job for
4) Click on the truck icon to schedule an import all job (only import
   all jobs may be scheduled as periodic)
5) Fill in target client, if necessary
6) Select 'At start time' and fill in the date and time
7) Next to 'Period' there is a box with a gray background. If you
   click in the box a drop-down arrow will appear. Click on this.
8) Select your period from the menu options and click on the green
   check.
9) Click on the green check again and your job will be scheduled.
or
you schedule the automatic import of u_rgent corrections via /TMWFLOW/SCMA_BTCH_SYNC_UC
see this link for details
http://help.sap.com/saphelp_sm40/helpdata/en/96/0737423df2b26be10000000a155106/content.htm
nesimi
Edited by: Nesimi Buelbuel on Jun 18, 2009 11:49 AM

ChaRM: Several maintenance cycles in one maintenance project?

Hi!
We are working with urgent correction within ChaRM and thinking about to implement the normal corrections as well.
Our ChaRM workflow for normal corrections is characterized by:
a)corrections with different Life cycle (those who will be processed within 1 week, other with 2 week, etc.)
Questions:
1) Is it possible to have several maintenance cycles for one maintenance project to handle condition u201Ca)u201D?
2) What will happen with all the normal corrections and urgent corrections that have a long life cycle (status: in development, test, etc.) when the charm manager set the status of maintenance cycle in u201CGo liveu201D?
Thank you very much!
H. Thomasson

Hi Holger,
Maintenance cycle and SMI project is a 1:1 relationship.
In status GoLive you will be able to continue developement/work on normal corrections but you will not be able to release any transport requests/create transport of copies so your testings in QA will be limited.
In phase GoLive you are able to import requests into production.
Normal Corrections which have not been released yet are not lost. Depending on your scenario you may switch phases back to "in dev with rel." after you imported into production. It is not necessary to close and recreate maintenance cycles if you use one project for daily/weekly maintenance.
/cheers

ChaRM Reporting - Transport Request, Tak and Owner columns not filled

I am using ChaRM reporting functionalities (/TMWFLOW/REPORTING transaction). When I select "display header, project, task list and transport", transport request, task and owner columns are not filled with values.
What is the problem?
Thanks
Antonello

Hi,
1. Is it configurd for ChaRM functionality in your systme landscape.
2. If not, please do the ChaRM configuration using by tcode SPRO.
Regards,
Srini Nookala

CHARM Project transports out of sequence

Hi All.
We've implemented a project using CHARM but we found that 7 out of 287 transports were imported not in the proper sequence as they were in the PRD queue.
The 7 transports were attached to 1 Urgent Correction with 8 transports altogether. The 8th transport request was imported first before the first 7
when the project import was done. This Urgent Correction was implemented along during the project import (was not imported to prod prior to the project implementation) .
Is there a way to make sure that when using CHARM for project import, the transports will be imported in correct sequence as per release date in the prod. queue?
Thanks,
Tess

We will create a a seperate maintenance cycle

ChaRM - Moving Transports to Production

Hi,
In ChaRM when we move transports to the production system either via a batch job or manually from the SCMA transaction we find that some SDHF corrections which are in the To Be Tested state are moved to production system along with the normal corrections. can this be prevented in some way ?
Regards,
Vinod

Let me add some more information....
We are having an issue where SDHF Transports in a status of "To Be Tested" are imported in production along with Normal Correction Transports when the Maintenance Cycle is set to "Go-Live". It was previously our understanding that when SCMA is used to import Transports for a Maintenance Cycle project, SDHF Transports that are still in a "To Be Tested" status will not be imported until they were successfully tested and received Change Manager approval. SAP recommends that we implement a manual process to review / address open SDHFcorrections and ensure they are either in the status of "In Development" or have been manually imported prior to setting the Maintenance Cycle to "Go Live". Due to the amount of SDHF Corrections that we implement for the HCM system, this will be a difficult manual task.
Regards,
Vinod

ChaRM: Release transport Error

Hi Team,
I have configured ChaRM in my Sol Man system (EHP1, SP24). When i try to release the transport request in Sol Man, i ma getting below error:
Error RFC destination SM_GDDCLNT300_TMW: Screen output without connection to user.
In SM59, both connection test & Authorization test is OK.
Your valuable input will be very much appreciated....
Thanks
Kumar

Hi All,
If i execute this RFC in SM59 (Connection Test & Authorization Test) in Sol Man system, it is OK. But when i try to release the transport request thro Sol MAn using the action "Release Transport Request", i am seeing this error in task list.
How this RFC can fail during transport request release, even it is working SM59?
Need your advise...
Thanks
Kumar

Solution Manager/Charm and Transport Dependency Check

Hello Everyone,
I apologize if this question has an obvious answer. I have searched SDN and could not get a 100% answer.
We are just now in the process of rolling out Charm/Solution Manager and I have noticed that it appears to not perform transport dependency checks. For example, let's say I am working on object ABC and have completed my testing (ready for transport to production) and then another developer also starts development on object ABC. When my change is moved to production, it will pick up the other developers modifications without giving a warning or an error that a dependency has been encountered between the two transport requests.
Does Charm/Solution Manager offer the option of producing a warning should a transport depedency be identified? If so, will someone explain (or point me to the appropriate documentation) how this can be set up?
Best Regards,
Scott

Hi Scott,
ChaRM supports imports from DEV->QAS->PRD by transport by transport requests level not by transport request task level. So don't worry(i.e., You can't import only your change of object ABC to production. It allows to import your change and other user's change of object ABC together to production).
This is how it works(if more than an user works on the same object):
1. Requester creates a support message from satelitte system to report a problem.
2. Service desk employee creates a change document because some changes need to be done on object ABC to correct that reported problem.
3. Change Manager approves the change document. So a normal correction is created automatically.
4. This normal correction is assigned to 2 developers(your scenario) like for an example DVPR1 and DVPR2.
5. DVPR1 creates a transport request and does some changes on object ABC. So a transport task will be created for DVPR1 under that transport request automatically.
6. When DVPR2 tries to do some changes on the same object ABC, a seperate transport task(not a transport request) will be created for DVPR2 under the same transport request because the object ABC is locked under the transport request. So DVPR2 can't create a separate transport request for the same object if any transport request is pending(not released).
7. Now object ABC will have one transport request. That transport request will have 2 transport tasks(1 for DVPR1 and 1 for DVPR2).
8. Each developer relases their transport task only(not transport request) once he/she completes his/her change on the object ABC.
9. DVPR1 or DVPR2 will change the status of normal correction to "Development Completed".
10. Now, IT operator or DVPR1 or DVPR2 can release the transport request. The transport request can be released only if all tasks are released under the same transport request.
(In this example: DVPR1 completed his change and released his transport task. Next DVPR2 completed and released his transport task).
11. Finally IT operator import the transport request to QAS and PRD.
Hope you are clear now. Let me know if you have any doubts.
Regards,
Sanjai

Combining several adjustment layers into a easily accessable preset

Hello,
the past couple of hours I've been trying to combine multiple Adjustment Layers (For example Curves, Black & White, Exposure and Color Fill) into one final preset that I can easily access later. I've been having problems finding that out, not a single input in google was able to clear up my problem. I know how to save a preset for e.g. Curves only or Levels only. But using several layers of adjustments?
Some help required (:

I will try my best. Thank you very much for the answer
Edit:
So, I just did it. You were right, easy to understand, working perfectly fine! Thanks very much!

ChaRM: Several Transport layers

Similar Messages

Maybe you are looking for