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

Similar Messages

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

Email notification in Charm with several status changes

Hello,
according to OSS 1275036 I tried to implement email notification in my Charm-process using BADI AGS_SDK_SCHED_ST_CHD in my schedule condition. If a new partner is responible in Charm-process, this partner should be notified by email. The email should be send if user status is changing.
It still works for my change request (notification of change manager) and the first step of my change document (notification of developer). But for all following steps (e.g. notification of tester) no action for email-notification is found in my change document.
In my actions I only use schedule conditions (according to OSS) and no start condition. To use the BADI for several user status, I maintained my user status in field value instead of inital value.
Does anybody know, how to use this BADI for several status changes in my change document?
Thanks,
Laura

Hello together,
I solved my problem by using CRM Standardcustomizing. Forgot SAP note 1275036 and 865619. They are all bad and not sufficient for a complex Charm scenario.
I only used note 1275036 for the first mail in my change document (email to developer). For all following mail notifcations I'm using actions based on workflow conditions instead of BADI.
Just using normal CRM-Customizing and create one schedule and start condition for every used action.
E.g. send mail to tester:
schedule condition:
&Servicevorgang CRM.Anwenderstatus& [*] E0002+DHFHEAD
and &Servicevorgang CRM.ErrorFreeFlag& = X
start condition:
&Servicevorgang CRM.Anwenderstatus& [*] E0004+DHFHEAD
and &Servicevorgang CRM.ErrorFreeFlag& = X
This works perfect, because you won't get several mails for one status if you save your document more than one time, which is a problem with note 865619.
Regards,
Laura Mathes

I have several layers for this image: Background, Moon, Tree, Grass and Clouds. When I try to use the Move tool to move the Moon, the tool jumps to the Tree layer. The same thing happens with the other layers as well (except the background layer). How

I have several layers for my image: Background, Moon, Tree, Grass and Clouds. When I try to use the Move tool to move the Moon, the tool jumps to the Tree layer. The same thing happens with the other layers as well (except the background layer). How can I keep the move tool from jumpimg to the Tree layer?

1. Pre-select (highlight) the layer to move in the Layers panel. or-
2. [ALT+Right mouse click] to select the wanted layer in the image window.
and maybe
3. Set the PS option to "Auto-select" a layer with cursor hover. (can be very confusing!)

How to configure TMS for ChaRM with Customizing routes?

Hi Experts,
We have succesfully configured three system landscape TMS for ChaRM for several pipelines already. Now we are facing a situation where TMS is as follows:
DEV to QAS contains routes:
Customizing: ZEBP => 100
Transport: ZDEV => 100
Customizing: ZSUS => 200
Transport: SAP => 100
The question with these is how to add ZEBP and ZSUS to ChaRM configuration?
QAS to PRD:
Delivery: 200 => 200
Delivery: 100 => 100
Here the question is how to enable transports between 200s alongside 100?
When looking at SMSY in SolMan, SUS is a logical system only.
Has anyone of you come across a situation like this? I'm glad for any hints you may give me!
Our SolMan is 4.0 SP13.
Best Regards,
Auli

Hi
in my opinion you can configure it the following way:
Customizing: ZEBP => 100
Transport: ZEBP => 100 (not ZDEV)
Customizing: ZSUS => 200
Transport: SAP => 100
Then assign ZEBP as default transport layer for client 100 and ZSUS for client 200.
It is not possible to configure ZEBP and ZDEV for client 100 if you want to use charm
regards, Andy

CHARM cannot create transport of copies for BW transport

Hello Colleagues,
I am facing a problem using CHARM with BW system:
I create Request for Change --> Normal Change --> Transport request
then BW developer uses a task in my transport (takes the task under her name) and attaches several BW objects.
At that time objects in the task are locked.
Then Developer releases the task. At which point the objects are unlocked in the Task, but got instead locked in the transport header.
I am trying to "Pass NC to Test", but facing error: TOC is created but cannot be released because of locked objects.
Releasing created TOC manually gives me the same error.
Is there a solution to this issue?
Thank you
Elena

Yes, OSS message came back with recommendation to apply note 1816332 in BW DEV system, after which TOC got created and released with no issues.

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

Need help in configuring CHARM with R/3 System landscape with seven systems

Hi All,
we are planning to configure CHARM for our R/3 landscape.our current STMS includes seven systems.in the current STMS the transports flow as below.
D20->C20->C21->C22->C23->T20->P20
we require the transports to move in the same way as stated above even after CHARM is configured
1.please let me know if we can configure CHARM with seven systems.
2.if yes, how would the import happen( ie Action for import appears for all systems?).
Regards,
Anand Reddy

HI andy,
the transports will move in the following order.
D20(DEV)->C20(Consolidation)->C21(integ)->C22(reg)->C23(unit)->T20(final test)->P20(production)
transport will start in D20,then imported C20 followed by C21,C22,C23,T20 imports and finally reach P20
the systems are not in parallel they are one behind the other
Anand Reddy

Charm implemenation for transports in solman 7.1

Hi Guru's,
Can anyone help me to get knowledge in charm implementation for transports in solman.
I am new to solman , can anyone help here.
Help is much appreicated.
Thanks,
Pradeep.

Hi Pradeep.
Please check the following blogs:
http://scn.sap.com/people/dolores.correa/blog/2008/07/26/first-steps-to-work-with-change-request-management-scenario
http://scn.sap.com/people/dolores.correa/blog/2009/07/23/change-request-management-scenario-working-examples
http://scn.sap.com/people/dolores.correa/blog/2009/07/22/change-request-management-scenario-usual-questions-and-known-errors
Thanks
Vikram

CHARM : Sequence of transport request to import

Hi,
I'm configuring CHARM and found out below issue.
Scenario.
1) Charm project with project type implementation was created in SOLMAN. The type of change is normal correction. All transport request was created under 1 task plan. The transport was created based on configuration and some of the transport request have dependency to others transport request.
For example.
a)GL account need to be created in FI and was assigned to TR002.
b) MM need to configure the GL account that was created in a) and was assign to TR001
Issue
When the TR was release, how do we ensure that the sequence of import to QAS client and PRD client must follow the dependency of the TR created?
Appreciate your input.
regards,
Biah

Hi Sir,
I am working in SAP Solution Manager. I would like to know some concepts regarding CHaRM:
Currently our project is using Transoport Proposal. We will soon shift using CHaRM. But I am not aware of the Technical concepts.
1. How to configure CHaRM with the Tranport Proposal Flow.
2. How to navigate in CHaRM? (screenshots can help).
3. I am aware of the process but still after creating a CHaRM how do the Developer navigate to do a change in DEV system.
will he go through CHaRM. (please explain me).
4. Also explain me the total process from technical point of view till the CHaRM closure.
5. I am aware of SOLMAN in this process where the Charm requests are collected and monitored.
Hope I will get a good guidance from your end....

ChaRM: combination of transport strategies

Hi ChaRM-experts!
I plan to map the existing transport landscape into ChaRM scenario of SOLMAN and have the following questions:
1) Is it possible to combine ChaRM-functionality and still use the old transport settings (without ChaRM) for the same system landscape, letu2019s say:
DEV --> QAS --> VO1 (Without ChaRM and with virtual system)
DEV:101 --> QAS:101 --> PRD:101 (With SOLMAN ChaRM)
2) What will happen with existing transport, transport in pipeline by switching into ChaRM scenario?
3) Is there some restrictions for the implementation of ChaRM for SAP R/3 4.7 systems?
Thank you very much!
Holger

Hi Holger,
1) Is it possible to combine ChaRM-functionality and still use the old transport settings for the same system landscape, letu2019s say:
DEV --> QAS --> VO1 (Without ChaRM and with virtual system)
DEV:101 --> QAS:101 --> PRD:101 (With SOLMAN ChaRM)
For Charm we need the transport route to be client specific.Once you have done the client specific transport route,you cannot use the older Transport route.
2) What will happen with existing transport, transport in pipeline by switching into ChaRM scenario?
TPs created before charm will be moved manually(normal process),as they will not be captured under charm project.
3) Is there some restrictions for the implementation of ChaRM for SAP R/3 4.7 systems?
No.
Please revert for any clarifications,
Regards,
Avinash.

CHARM with a 2 system landscape

Hello ,
we have only a 2 system landscape for our ERP systems.
When I now click on the check button on the maintainance project. I receive an error :
No consolidation system found for DEV-001 (project TEST_CHARM)
No track for project TEST_CHARM with log. system P23/001
Message from function module /TMWFLOW/CHECK_PRJ_CONS: No export system for DEV-001
TMS ( without any client routes)
DEV->PROD
Any suggestions ?
Regards

Hi Daniel,
we are using CHaRM in various transport landscapes with 2 and up to 5 systems. This is all working fine. Please make sure there is a consolidation transport route from DEV, also all RFC connections from Solution Manager to your Transport Landscape are set up, inlcuding 000 clients.
TMS settings need CTC=1, and Trusted Services in STMS need to be activated.
Other prerequsites are:
- Systems are deined in SMSY
- Transport Domain link between Transport domain controllers
- Logical components defined in SMSY (with correct system roles)
- Lofical component added to SMI project
If this is all fine, please hit button "Shipment Routes" in SOLAR_PROJECT_ADMIN in tab page "System Landscape" => "Systems" You should see all transport routes required for this project.
If this works, you are in a good shape.
Best Regards,
Holger Slomka

CHARM - Refresh and Transport Log

Hi
We have configured charm if i refresh Dev or Qas system what will happen to the transport change log created by Charm.
is there any procedure to save the transport log(out side the system) or to take back up of the data before refreshing the systems.
Thanks
Nanda.

Hi Nanda,
the transport logs are neither stored in Solution Manager nor in the database of the refreshed system. They are stored in the transport file system /usr/sap/trans/log. So a system refresh should not have any impact to ChaRM regarding the transport logs. As Solution Manager is only controlling tp in satellite systems, there is no big difference in a system copy with Change request management and without (as long as you don't overwrite the transport domain controller).
So you can follow the same procedure as you did before activating ChaRM. Just make sure, that all RFCs between Solution Manager and Satellite system still work and user and roles in the satellite system after the refresh are being restored (but this you should always do even without ChaRM).
If you mean the history of change documents in Solution Manager: They are not affected by the system copy.
Best Regards,
Holger Slomka

ChaRM with several transport layers

Similar Messages

Maybe you are looking for