ChaRM - External Transports

Hi,
How are External Transports like OSS Notes, SAP Support Packs, etc performed via ChaRM ?
Regards,
Vinod

Hi there,
- The different tasks are for the respective systems.
- If you have a project, then you create an SDCR, which is a Service Desk transaction. Tthen out of the SDCR you may create an SDMJ or an SDHFdepending on your needs. So no, no SDCR is created automatically from using SCMA task list actions, please work first in a SDCR.
- SDCRs go through the approval process necessarily
- The kind of correction depends on the subject you choose for the SDCR.
- About the SPAU, etc... sorry, no idea.
Please check the SDN blog /people/dolores.correa/blog/2009/07/23/change-request-management-scenario-working-examples , it might give you some insight on the ChaRM flow.
Best regards,
Miguel Ariñ

Similar Messages

Charm: Registering an External Transport

Hello,
Can one take an transport from and external system and register it with ChaRM and move the transport through the landscape?
I see in SAP note 1150426 that one can register a transport, but it appears that the transport must be modifiable. One must be able to set the attributes SAP_CTS_PROJECT with the value of the change request (M000*). This can not be done for a transport from outside.
Can one use ChaRM for external transports?

Hi
it's not possible to register external (or already released) transports for ChaRM or to transport them with ChaRM.
I recommend to transport them manually. Maybe you can documentate this in an admin change
What is possible but has cons:
-Import tranport into Dev manually
-Include all objects in a ChaRM transport
Cons:
-You need the same transport layer
-it is not 100% the same than importing the original transport
regards

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?

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

ChaRM External Reference Number Field

Hi
In ChaRM, we have used external reference number field for information. When a ChaRM CR is created, the requester fills required information in the field. In Normal Correction, this information is not automatically taken from the CR document to the correction document. When we search a normal correction by external reference number, it does not give any result, as the information is only shown in the CR document. This however works as expected in Ur.gent Corrections.
What could we do about this?
Many thanks for your answers in advance.
BR Li

Hello,
you need to check the mapping rules for field External Reference Number in copy control for Normal Corrections.
Go to the IMG: Scenario specific->change request management->Extended config->change trans types->copy control
Define Mapping rules.
Regards,
Raquel

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: 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 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

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

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

ChaRM: Edit Transport request Name

Hi Team,
I am implementing ChaRM in Sol Man. When i have creatd the transport request in ECC DEV through Sol Man, by default the transport request name is appearing as "EDDK". I would like the name of the transport request to appear as "MCCK instead of EDDK*. Is it possible?
Regards
PSK

hi
Transport Requests are SAP auto generated,cannot changed.(Experts kindly correct me if i m wrong).its in the format of
<source SID><k9><serial numbers>
however you can change this serioal number before TR get created, By manually changing the filed TRKORR in the table E070L
(index for assigning Numbers to TR)
for all the tables involved in TR, refer [trasnport guide|http://wiki.sdn.sap.com/wiki/display/ABAP/Transport%20Guide]
jansi

Charm and transport sequence

Hi,
If I have corrections A, B, C and D containing changes to the same object. A was released as a transport first, B second, C third and D fourth. They go through testing and the workflow in Charm, with final approval sequence of D, C, A. D was quickest to get tested, perhaps simplest change. C was second and A was last, perhaps the one to test longest. B on the other hand looks like it will need more time. I want to import A, C and D into production. I want to do mass imports into my production system. Using Charm, how can I ensure that (1) correction transport sequence in the import queue is A, C and D (transport release sequence is obeyed) and (2) B is not in the production system queue (release of transport in dev system does not add it automatically into the import queue in production)?
Don't worry about low level detail description, I am after guidance/ideas on how to achieve this.
Thank you,
Mike

Hi Prashant,
if you use normale correction SDMJ with project import, the import sequence A, C, D is secured, since the transports are imported in the sequence they were released in the development system.
If you want to prevent to import B you can use transport of copies.
Regards,
Christoph
Edited by: Christoph Kronauer on Oct 19, 2010 10:20 AM

CHARM Import Transport Request (Background) Error

Dear Experts,
We are Facing problem in Charm TR import with below error.
Current phase of project: Development with Release
Action to be checked: Schedule Manager: Import into Test Systems
Start Import (Project SID_P00005)...
Try to connect via TMS-internal RFC destination...
TMS communication error with TMSSUP#SID.DOMAIN_SID
Import error. Check TMS Alert Viewer in target system
RFC TMSSUP#SID.DOMAIN_SID is failing with authorization test.
Diagnosis
There was an error during communication with the RFC destination
TMSSUP#SID.DOMAIN_SID
System Response
The exact error message of the system is:
Name or password is incorrect (repeat logon)
please suggest how to correct this Authrization error
Regards,
Siva.

Dear Laxman,
Kindly give me a link for any authorization docs, for SOLMAN and MANAGED SYSTEMS which roles need to be assigned for general Team member , Change manager and BASIS admin.
Please provide any docs.
i reffered to standard , where i am littlebit confused.
please provide some docs.
Regards,
Siva

ChaRM - External Transports

Similar Messages

Maybe you are looking for