1/6/2016 First steps to work with Change Request Managem... | SCN

http://scn.sap.com/people/dolores.correa/blog/2008/07/26/firststepstoworkwithchangerequestmanagementscenario 1/22

Getting Started Newsletters Store

Products Services & Support About SCN Downloads

Industries Training & Education Partnership Developer Center

Lines of Business University Alliances Events & Webinars Innovation

Log On Join UsHi, Guest Search the Community

Activity Communications Actions

Browse

dolores.correa

3 Tweet

First steps to work with Change Request Managementscenario in SAP Solution Manager 7.0With the following steps you will be able to create a test landscape to practice with the Charm scenario in SolutionManager 7.0 without creating interferences with real TMS landscapes.

Also I will try to give tips and tricks for the common mistakes in the configuration of this scenario.

The configurations given are valid for Solution Manager 7.0 since SP9 and above.

Note: If you have a Solman 7.1 system then see SCN doc First steps to work with Change Request Managementscenario in Solution Manager 7.1

Step 1 Create the test landscapeUsually you would like to use Charm to manage the changes in this kind of TMS landscapes:

DEV:100 >QUA:200 >PRD:300

The test landscape that I am proposing is this one: your Solution Manager is installed in system SMM for example, andyou are configuring client 001 for being used as Charm client, them SMM:001 is your Charm client.

Create three additional clients in SMM, like local client copy from client 000 with SAP_ALL profile (this will need someextra space in SMM system, but not too much), let say you create clients 100, 200 and 300.

We assume that SMM:100 is going to be the Development system, SMM:200 the Quality system and SMM:300 is theProduction system.

In SCC4 assign the following client settings, roles, etc. to these clients, this is important!

Customizing role for SMM client 100

Test role for SMM:200

Production role for SMM:300

First steps to work with Change Request Managementscenario in SAP Solution Manager 7.0Posted by Dolores Correa in dolores.correa on Jul 26, 2008 6:20:06 AM

Share 3Like

1/6/2016 First steps to work with Change Request Managem... | SCN

http://scn.sap.com/people/dolores.correa/blog/2008/07/26/firststepstoworkwithchangerequestmanagementscenario 2/22

The indications given for this test case from now on also apply to for your real TMS landscape, to DEV, QUA and PRDsystem.

Note:

In ChaRM we do support twosystem landscape, to use it you should firstly configure the consolidation route in STMScorrectly.

Then set up the development system as type of role "Source System", and production system as type of role"Production System" in your project system landscape. In such projects there should be no target system needed.

Please always keep in mind that production system is very special in ChaRM so make sure there is at least one ineach of your project.

See that in twosystem landscape no test transport will be generated for normal correction SDMJ, since officially this

1/6/2016 First steps to work with Change Request Managem... | SCN

http://scn.sap.com/people/dolores.correa/blog/2008/07/26/firststepstoworkwithchangerequestmanagementscenario 3/22

functionality is only designed for test system, see note 1419150 ChaRM: Transport of Copies (ToC) with twosystemlandscape.

Step 2 Configuration of TMS for this scenario according to CharmprerequisitesIn Solution Manager, in client 000, call STMS (the same must be done in the domain controller system of your reallandscape)

Note: SMM client 001 does not need to take part of your TMS landscape.

Select Transport Routes icon:

For this test landscape initially you have system SMM and none transport route defined (for a real landscape you willhave the three system boxes DEV, QUA and PRD):

Make doubleclick on system SMM and fill the following values (or in the box of the development system and after inthe quality box):

In System Attributes tab: the use of Single transport is a prerequisite for Charm for all the systems in the landscape;you will see this in detail in section Step 3.

1/6/2016 First steps to work with Change Request Managem... | SCN

http://scn.sap.com/people/dolores.correa/blog/2008/07/26/firststepstoworkwithchangerequestmanagementscenario 4/22

In Standard Transport Layer tab: ensure you enter the client 100, (client with customizing role for the development box,client with test role for the quality box).

Create the consolidation transport routes to SMM:200, transport route must be CLIENT SPECIFIC for the use in Charmscenario, this is real important!

From development system to quality system you need at least two consolidation routes, SAP and ZXXX.

1/6/2016 First steps to work with Change Request Managem... | SCN

http://scn.sap.com/people/dolores.correa/blog/2008/07/26/firststepstoworkwithchangerequestmanagementscenario 5/22

Go with the pencil from the system SMM to system SMM and get this popup:

I create the consolidation route for transport layer SAP and I do the same to create transport route for transport layerZSMM (for customer developments).

In case of a real landscape you need to choose from which system to which system and client.

1/6/2016 First steps to work with Change Request Managem... | SCN

http://scn.sap.com/people/dolores.correa/blog/2008/07/26/firststepstoworkwithchangerequestmanagementscenario 6/22

I make the same to create the Delivery transport route from SMM:200 to SMM:300, delivery routes are always fromquality to production systems.

Finally you will get the following situation:

1/6/2016 First steps to work with Change Request Managem... | SCN

http://scn.sap.com/people/dolores.correa/blog/2008/07/26/firststepstoworkwithchangerequestmanagementscenario 7/22

Save and distribute the changes:

All the previous work has to be done in the satellite systems in real landscapes.

Step 3 Review of the main configuration points in SPRO1. All point under SAP Solution Manager >Configuration >Basis Settings must be performed.

Especially important point is:

RFC connections from Solution Manager to DEV, QUA and PRD system, don’t forget to create also SM_..._TMWconnection 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 andPRD systems in our example.

In transaction SMSY:

Also you need to create the RFC connections from Solution Manager SMM:001 to client 000 in the system that is thedomain controller of your real landscape, this is really IMPORTANT!!! You will see more information about this in spropoint “Generate RFC Destinations to Client 000"

Note: usually the domain controller is always in DEV system as this was the first system in the landscape to beinstalled. If you move the domain controller to PRD system, as it is recommended, don´t forget to create the RFCconnection to client 000 of this domain controller system.

2. In SPRO go to ScenarioSpecific Settings>Change Request Management >Standard Configuration

General Activities:

1/6/2016 First steps to work with Change Request Managem... | SCN

http://scn.sap.com/people/dolores.correa/blog/2008/07/26/firststepstoworkwithchangerequestmanagementscenario 8/22

2.1. Run “Activate Integration with Change Request Management”

After this check in SM30 that view BCOS_CUST has the following entries:

CHARM W NONE CUST620 1.0

CHARM_DEST W NONE CUST620 1.0

This means that Charm configuration has been done in this client.

2.2. Activate BC Sets: Check note 903527

Bc Set for Charm: SOLMAN40_CHARM_BASICFUNC_001

Under Transport Management System check the following in detail:

2.3. Define Transport Routes for System Landscape: already explain in steps above

2.4 Activate Extended Transport Control: apply this point to all systems in real scenario

2.5 Configure Transport Strategy: apply this point to all systems in real scenario

2.6. Activate TMS Trusted Services: apply this point to all systems in real scenario

2.7. Activate Domain Links: you have to create interdomain links

If you go to STMS in the solman system you can see that the solman system is in transport domain DOMAIN_SMM forexample.

In your real landscape, DEV, QUA and PRD will belong to another transport domain, usually called DOMAIN_DEV.

What you need to do in this spro point is to make these two transport domains known each other, I mean as the solmansystem is going to call TMS functions in the transport domain of DEV, QUA and PRD, the TMS of solman must knowthis other transport domain.

From help.sap.com:

To request a link between two transport domains, proceed as follows:

Log on to one of the two domain controller systems, in solman system for example.

1/6/2016 First steps to work with Change Request Managem... | SCN

http://scn.sap.com/people/dolores.correa/blog/2008/07/26/firststepstoworkwithchangerequestmanagementscenario 9/22

Call transaction STMS (always being in client 000).

Choose Overview > Systems.

The system overview appears.

Choose SAP System>Create > Domain link.

The dialog box Request for Linking 2 Domains appears.

Enter system name, DEV for example, hostname where is installed the system and system number, all this informationis in SM51 of this DEV system, if DEV system is the domain controller of your real landscape.Your SAP System performs the following actions automatically: Generates the required RFC destinations. Sends theaddress data of the controller to the controller in the other domain.After you have to logon in the domain controller,client 000, of your real landscape and confirm the link between these two domains as follows:

Log on to the domain controller in the other domain.

Call Transaction STMS in client 000.

Choose Overview >Systems. The system overview appears.

Position the cursor on the domain controller where you requested the domain link, DOMAIN_SMM in our example,and choose SAP Systemà Approve.

Confirm the prompt and distribute the configuration.

The two domain controllers now exchange all necessary information about the systems in their domains. Thisinformation is distributed to all systems in the domain whose controller you are currently logged on to. A transportprofile is generated, which contains all systems in both domains.

You have to see something like this in your solman system (called SSM in this real example):

1/6/2016 First steps to work with Change Request Managem... | SCN

http://scn.sap.com/people/dolores.correa/blog/2008/07/26/firststepstoworkwithchangerequestmanagementscenario 10/22

And this in the DEV system (called ED4 in this real example):

To check that the domain link is ok go in solman system and in development system to STMS>transport routes, in thetop of the screen you will see that in solman system the systems belonging to the other transport domain appear likeboxes and the same if you go to STMS in DEV system, the box of the solman system can be seen.

The information about the systems in the other domain is not automatically distributed to the systems in the domainwhere you requested the domain link. This means that you must distribute the new configuration to these systems.

2.8. Generate RFC Destinations to Client 000: already explained.

2.9. Add Import Authorization to Operator/Administrator: According to note 913232

"Therefore, the TMS requires that the people responsible for the import (operator or administrators with importauthorization) have a user in the client 000 of the target system".

This means that you need to define these users in the client 000 of all target systems involved in the landscape withimport authorizations.

Under Change Request Management:

2. 10. Set Project Assignment of Requests as Mandatory: not totally mandatory but this will avoid users creatingtransport orders directly in development system. All transport orders in development system in your real landscapemust be created from the solman system via a Change Request.

2. 11. Maintain Number Ranges: run this.

None of the configuration points under “Extended configuration” are required if you want to use the standard Charmscenario.

Now you are ready to create a project.

Step 4. In Solution Manager go to transactionSOLAR_PROJECT_ADMINPlease go to http://service.sap.com/rktsolman

Select SAP Solution Manager 7.0, select Learning Map for Supp Organizations/Serv providers, open Change RequestManagement section and see the iTutor called:

“Create a Project”

The main points in the creation of a project for Change Request Scenario are:

Decide if your project is an implementation or a Maintenance project; see the differences in the Solution ManagerDocumentation. For our test case select a maintenance project.

1/6/2016 First steps to work with Change Request Managem... | SCN

http://scn.sap.com/people/dolores.correa/blog/2008/07/26/firststepstoworkwithchangerequestmanagementscenario 11/22

In System Landscape TabSystems: here you have to enter your logical componentTake into account that all systems that belongs to the TMS landscape must be assigned to the same logicalcomponent, because all system must have thesame product version (exception in case of an upgrade).This means that in the same logical component each system must have assigned a role, you can have a minimum oftwo systems for Charm scenario but you can have for example 5 systems with different roles in your real landscape.In our test case you will have this:

Always define here the same landscape that you have defined in the STMS of the real landscape, if not the Charmscenario can not be activated. This point is always the point that more problems gives in the activation of Charmscenario!!!

In IMG project tab: define always a project in the development system ONLY! You need to define this project in thedevelopment system in order to assign to this project all transport orders that you are going to create via a Changerequest in the solman system, this is a prerequisite for Charm scenario!

See the above iTutor to see how to define this IMG project.

Don’t define IMG projects in other roles, systems, different to development.

In Change Request tab: Select “Activate Change Request Management”

1/6/2016 First steps to work with Change Request Managem... | SCN

http://scn.sap.com/people/dolores.correa/blog/2008/07/26/firststepstoworkwithchangerequestmanagementscenario 12/22

Select Create Task List

Select the name of your Maintenance Cycle also called Project Cycle.

1/6/2016 First steps to work with Change Request Managem... | SCN

http://scn.sap.com/people/dolores.correa/blog/2008/07/26/firststepstoworkwithchangerequestmanagementscenario 13/22

Note: Choose Lock/Unlock Grroup/Subsequent Groups to unlock the tasks in the task list.If all is working correctly a Task List and a Maintenance transaction type SDMN (called Service Desk Transaction inthe screenshot) is being created.

Service Desk Transaction Tab: This tab is not appearing in SP9 but appears in SP13 and above and shows the SDMNdocument for this project cycle.

1/6/2016 First steps to work with Change Request Managem... | SCN

http://scn.sap.com/people/dolores.correa/blog/2008/07/26/firststepstoworkwithchangerequestmanagementscenario 14/22

The task list is one representative of the cycle and represents the system landscape tracks with tasks to be used by anIT operator for managing project related IT activities, especially imports.

The SDMN transaction represents the service request for managing the phase changes.

In SP9 you went to Task List to Activate the maintenance cycle and also to change the phases of this maintenancecycle, in SP13 and above it are recommended to go to the maintenance transaction directly, viaCRM_DNO_MONITOR (select transaction type SDMN) and activate and change the phase via Actions in thetransaction directly.

So, phase shifts should be done from within the cycle transaction SDMN but not from within the tasklist.

In case of the Task list in not created please run the Check (transaction /n/tmwflow/charmchk) or go to the ApplicationLog via the button or calling SLG1 directly.

In both place you will get information above the reasons why the Task List and the Maintenance Cycle is not beingcreated.

As summary pay special attention to the following points:

Ensure that the Logical Component in Systems tab and the TMS information in STMS in the domain controller of yourreal landscape fits together

Transport routes must be set client specific

Now is time to check the RKT material, iTutors:

Regular correction

Urgent correction

to fully understand the complete process.

When everything in the test scenario is running fine, then you can connect the Production System landscape toSolman system.

This will ensure that you do not stop the TMS in the productionlandscape. Update information of Charm can be found in:907768 “General note for Change Request Management ST 400”881553 “Roles for Change Request Management (SAP Solution Man 7.0)” For further information about the Charm scenario see also the following SDN blogs: Change Request Management scenario: Usual questions and known errors Change Request Management scenario: Working examples

1/6/2016 First steps to work with Change Request Managem... | SCN

http://scn.sap.com/people/dolores.correa/blog/2008/07/26/firststepstoworkwithchangerequestmanagementscenario 15/22

Average User Rating

(10 ratings)

My Rating:

3 Tweet

Change Request Management scenario: Retrofit Functionality

34959 Views

Share 3Like

42 Comments

Like (0)

Anand Rangarajan Jul 26, 2008 8:47 PM

This was the Most frequently asked question in SDN solman forum...One of the best Compilation...

Keep it up...Regards,Anand

Like (0)

Aldo Ortiz Feb 26, 2009 6:45 AM

Hello Dolores,Thanks for your very complete definition. We have a case where we are using a Solman DEV, client100 and SolMan PRD, client 300. We have a transport layer already defined where we can createtransport request and send to the Solman PRD (for example for Service Desk customizing). Now weare implementing ChaRM and creating a test landscape of 3 clients in the same SolMan Dev system,in our case 500, 600, and 700 (dev, qa, prd. Can we have these two transport layer in the sameSolMan DEV?

I appreciate your comments.

Regards

Aldo

Like (0)

Dolores Correa Feb 26, 2009 10:27 PM (in response to Aldo Ortiz)

Hi Aldo, In this case you have a real TMS landscape from DEV:100>PRD:300 so consolidationroutes SAP and ZXXX are already used for the real TMS landscape.This means that you can not create the test scenarion in DEV without interfering the realTMS.So, in this case I would suggest to create the test scenario in PRD or in other developmentsystem of other product, for example in the development system of your R/3 system.Hope this helps, Dolores

Like (0)

Boris Milosevic Aug 5, 2009 1:55 AM (in response to Dolores Correa)

In our case we have standard transport route ZDEV for the standard CHARMtransports ( DEV:330PRD:100). We created test clients in our DEV environmentand created new consolidations route ZCHM with source client charmdevelopment client 800. (qas 801 prd 802) and CHARM test environment worksfine :)

rgdsBoris

HAI HUYNH Sep 24, 2009 6:44 AM (in response to Dolores Correa)

Hi Dolores,

Great Article and contribution to SDN on CHARM.On EHP1 Solman, do we still follow the OSS Note number to activate CHARM.There is no NOTE# indicated on the IMG Documentation in EHP1.

1/6/2016 First steps to work with Change Request Managem... | SCN

http://scn.sap.com/people/dolores.correa/blog/2008/07/26/firststepstoworkwithchangerequestmanagementscenario 16/22

Like (0)

When I run it automatically in EHP1 after hitting execute in the IMG, I check the BCSets and nothing is activated. So, should I manually activate BC SetSolman40_CHARM_BASICFUN001 in SCPR20.

Thanks

Like (0)

Dolores Correa Sep 24, 2009 7:33 AM (in response to HAI HUYNH)

Hello, For EhP1 firstly you run solman_setup. In the Basic Configuration in point7 BC Set SOLMAN40_CHARM_PROXYFACT_001 is activated.After you have to follow the spro point Change Request Managementspecailly an entry called "Activate Activate BC Sets".Hope this helps, Dolores

Like (0)

HAI HUYNH Sep 24, 2009 8:22 AM (in response to Dolores Correa)

Thanks for the quick response...

I ran the automatic configuration when i executed Activate BCSet for CHARM in the IMG.If I check in SCPR20, SOLMAN40_CHARM_BASICFUNC001has not been activated. If I click on the Manual, it does nothing...Is this a bug in the system?I would assume this should be activated...

I did see Solman40_proxyfact_001 activated in the system...

Like (0)

Dolores Correa Sep 24, 2009 10:10 AM (in response to HAIHUYNH)

Hello, I checked this and the correct name for the BC Set isSOLMAN40_CHARM_BASICFUNC_001, as far as Iknow this BC set should be activated running theindicated spro point but also running Activate BC Set inthe Basic Configuration point of solman_setupaccording to the activation time in my solman testsystem.Anyway follow note 903527 in order to activate this BCSet in expert mode and chosing overwrite option too.Hope this helps,Dolores

Like (0)

HAI HUYNH Sep 24, 2009 10:19 AM (in responseto Dolores Correa)

Thanks Dolores... I'm use to using that note inthe past. I just think there is a bug with EHP1for that img activity...

Take care and great work. Much appreciated

Like (0)

HAI HUYNH Oct 5, 2009 1:29 PM (in response to HAIHUYNH)

Hi Dolores,

For EHP1, how should we take the approach to movetransport across clients. We are doing an upgrade andwould like to to move transport as well to our GoldenClient in DEV. (DEV 100 Custom Development , DEV200Golden Client)

Do we configure a different route in the TMS and justinclude DEV200 in the Locigical Component. I wouldassume that we use the Task List to do the importmanually.

Thanks for your advice...

1/6/2016 First steps to work with Change Request Managem... | SCN

http://scn.sap.com/people/dolores.correa/blog/2008/07/26/firststepstoworkwithchangerequestmanagementscenario 17/22

Like (0)

HAI HUYNH Oct 5, 2009 1:29 PM (in response to HAIHUYNH)

Hi Dolores,

For EHP1, how should we take the approach to movetransport across clients. We are doing an upgrade andwould like to to move transport as well to our GoldenClient in DEV. (DEV 100 Custom Development , DEV200Golden Client)

Do we configure a different route in the TMS and justinclude DEV200 in the Locigical Component. I wouldassume that we use the Task List to do the importmanually.

Thanks for your advice...

Like (1)

Jamuna Nithyanandam Mar 26, 2009 1:46 AM

Thank you for a very detailed blog.

After we have the tms set up for satellite systems, project created and activated for CTS in solutionmanager:

How do we set the status in the CHaRM workflow with the corresponding task in Scheduler? Can youplease help me with this query.. I am really not sure how to proceed further.

Thank you very much,Jamuna Nithyanandam

Like (0)

Carol Wang Apr 30, 2009 7:24 PM

do you meet such scenario: one DEV > one QAS> two prd? can this possibe?

Like (0)

Brad Donovan May 6, 2009 10:27 AM

Hi We have a complex landscape, in which we have multiple DEV (AGD/AGM) and QA (AGQ/AGV)systems. Is it possible to configure CHARM to use in this scenario?

Like (0)

Sadi Yilmaz Jul 3, 2009 2:20 AM (in response to Brad Donovan)

Hi Brad,

We have the same landscape, could you find any solution for this scenario?

Like (0)

Brad Donovan Jun 4, 2011 12:38 PM (in response to Sadi Yilmaz)

Hi Sadi, yes, we have set up cons route from AGDAGV, and delivery route fromAGVAGP. For AGM, there is an autoimport job that is set up an run (every 15minutes) to pick up transport requests released from AGD.

Like (0)

Fabio Sato Jun 15, 2009 4:44 PM

Hello Dolores.

Your posts are perfect! I made a SDesk and a ChaRM only with your informations. Thank you somuch. Now i have a issue and i believe then only you can help me to resolved.

In ChaRM, on schedule plan, before the request importation to QAS, if i change the status to "GoLive", is able to me to import the request to productive environment. Wouldn't have a check or a lockon this schedule. The status of the correct document is "in develop". Can you help me?

Sorry for this inconvenience. I already try everything.

Dolores Correa Jun 16, 2009 1:06 PM (in response to Fabio Sato)

Hi Fabio, Could you please give me your email address? I will send you some slides where you cansee which action can be done in each phase for normal and urgent correction.Best regards,

1/6/2016 First steps to work with Change Request Managem... | SCN

http://scn.sap.com/people/dolores.correa/blog/2008/07/26/firststepstoworkwithchangerequestmanagementscenario 18/22

Like (0)

Dolores

Like (0)

Fabio Sato Jun 17, 2009 5:46 AM (in response to Dolores Correa)

Hello Dolores.

Thank you so much. You are my reference in Solution Manager.

My email: fabiosato@globo.com

Best regards,

Fabio Sato.

Like (0)

Srujan Kumar Jakkampudi Jun 18, 2009 1:17 PM (in response to Dolores Correa)

Hi Dolores,

Your compilation helped me a lot in understanding the underlying concept ofService Desk and Charm Activation. Can you pls share the slides that youmentioned to send Fabio.

My email id is srujan.sap@gmail.com

Thanks in advance.Srujan

Like (0)

nsingh sihag Sep 16, 2009 5:05 AM (in response to Dolores Correa)

Hi Dolores!

we are having a different scenario. Our Landscape is something like this.

ECD(DEV)>EC1(QA1) andEA2(QA2)>EAP(PRD)

we are not having any network connectivity in between DEVQA1 to QA2 and PRD.DEV and QA1 are in one network and QA2 and PRD are on other network.

Now we need to implement ChaRM from Dev to PRD, so please suggest me howto implemet this. Whether this is possible or not? what different settings we have todo from standards.

Aslp please send me the configuration Docs and Slides on my mail IDnarpal.singh@gmail.com.

It would be very great if you suggest us on this.thanksnarpal

Like (0)

Amrita Amrita Jul 9, 2009 11:23 PM

Its really helpful blog. Very good effort.

Amrita

Like (0)

Sandeep Menon Aug 11, 2009 5:09 AM

Hi Dolores ,

I have a requirement to do a workflow for Transaction 'CRM_DNO_MONITOR' In Solution Manager. Ifyou have any information details on the configuration for workflow, Any business object that can beused for workflow . Please do provide me the details.

There are two process,1. I need the workflow to trigger when a ticket is created2. When the status of the ticket is changed.

Sistemas 1 Mar 2, 2010 4:14 AM

Hello Dolores,

1/6/2016 First steps to work with Change Request Managem... | SCN

http://scn.sap.com/people/dolores.correa/blog/2008/07/26/firststepstoworkwithchangerequestmanagementscenario 19/22

Like (0)

I'm following your detailed steps to configure the charm, but I allways get the following errors: Warning: Problems occurred during synchronization of the system landscape > When I activate thechange request management in solar_project_admin transaction.

The project is not released. Hence cycle can not be created when I push the buttom "create taskList" in the same transaction.

The system landscape are two system: dev > prod, we don't have quality system. Could it be thecause of the errors?

How can I follow the configuration?

Thanks for you help and you great blog and best regards,

Ana.

Like (0)

Dolores Correa Mar 2, 2010 5:02 AM (in response to Sistemas 1)

Hi Ana, Send me an email to d.correa@sap.com, I will call you if you want.Best regards, Dolores

Like (0)

Vadivambal Paramasivam Aug 30, 2011 3:17 AM (in response to Dolores Correa)

Hi,

Currently CHARM allows tranport across 3 system landscape DEV>Qual>Prod.Can we create project with mulitple 3 sys landscape (for e.g ECC 3sys,cProjec3sys,CRM3 sys)and control the transports.

ERP and cProject systems are tightly integrated here and changes are beingmoved in both the systems.

Please let me know if its possible

Thanks,Vadi

Like (0)

Kevin Richman Mar 10, 2010 12:27 PM (in response to Sistemas 1)

Ana,

From what I have seen and experienced, ChaRM really wants a 3 system landscape at aminimum. Even if this means creating a logical component and transport route that goesthrough 2 clients on your dev system (1 for Config/Dev, and 1 that can be used for Test)before going to prod, or creating a virtual QA system that can be included in your transportroutes and landscape.

Like (0)

Jose Garcia May 13, 2010 2:13 PM

Thanks for taking the time to do this; well done.

Jose

Like (0)

kalenthiran p May 25, 2010 10:03 PM

HI,Really help me lot,in my case We have three system landscape (DEV,QA,PRD),in dev we havetwo client (100,200)we are doing customizing in client 100 and workbench changes in client 200,QA300 PRD 330.for charm configuration how i have do define transport layer and route and logicalcomponet

Like (0)

Dolores Correa May 27, 2010 6:59 AM (in response to kalenthiran p)

Hello, See SDN blog:Change Request Management scenario: Usual questions and known errors

Change Request Management scenario: Usual questions and known errors Point 1 and 2.Hope this helps, Dolores

1/6/2016 First steps to work with Change Request Managem... | SCN

http://scn.sap.com/people/dolores.correa/blog/2008/07/26/firststepstoworkwithchangerequestmanagementscenario 20/22

Like (0)

kalenthiran p Jun 3, 2010 11:56 PM (in response to Dolores Correa)

Hi,

Thanks,its working.How and where i can define change manager for a system orIbase.

Like (0)

Nenad Nikolic Jun 17, 2010 12:44 AM

Hi Dolores, thank you for nice blog. However, I have a problem performing the described steps.

How do you create multiple trusted RFCs from one client in SolMan to other clients in the sameSolman (step 3)?

Please take a look at forum's toppic where I explained my problem:

No authorization to logon as trusted system (Trusted RC=2)

Thank You in advance for Your help. Nenad

Like (0)

Nayab Siddiqui Jul 7, 2010 10:13 PM

Hi,

This error occurs if the background job is not scheduled

Error in background job for program RSGET_SMSY error message No active job found

Why it is required and do I need to schedule background job, each time the project is created.

Regards,Nayab

Like (0)

Natalyia Veleva Dec 15, 2010 4:32 AM

Hello Dolores,

you wrote:

"When everything in the test scenario is running fine, then you can connect the Production Systemlandscape to Solman system.This will ensure that you do not stop the TMS in the production landscape."

Could you please explain this step in detail? As far as I know, you need to switch the production landscape to client specific and completelychange the transport routes so that they can be client specific. One also has to create a new ChaRMproject and activate it. The production project can not be activated if the production landscape is notclient specific.

Like (0)

Shawn Grant Nov 10, 2011 7:20 AM

I am trying to prototype ChaRM by following this details (which are fantastic!). Unfortunately, I amstuck at the step to Activate BC Sets. When I execute this step I receive the following message, "Thereis a production client in the system. SAP Change Request Management cannot be configured." Doesanyone know what the problem might be?

Thanks,Shawn

Like (1)

Dolores Correa Nov 13, 2011 11:53 PM (in response to Shawn Grant)

Hi Shawn, Go to scc4 and change the role of your client to Test for example and run again the bcsetactivation.Hope this helps, Dolores

Ravi Kanth May 18, 2012 1:13 PM (in response to Dolores Correa)

Hi Dolores,

1/6/2016 First steps to work with Change Request Managem... | SCN

http://scn.sap.com/people/dolores.correa/blog/2008/07/26/firststepstoworkwithchangerequestmanagementscenario 21/22

Like (0)

I am New to SAP Solution Manager. Can you please help me in understanding astep by step procedure on how to migrate Incident/Change request data from NonSAP system to SAP Solution Manager. One of my client has already installed SAP Solution Manager last year and but notbeen used till now. Wtih respective handling Incident tickets/Change request andTaking reports, they have been maintaining in Non SAP system (Service Support).Now management has decided that only one system (SAP SolMan) should be theirfor maintaining Change request and Taking reports. Client is asking me to give solution on how to go about it. I am requesting you toplease share a document which talks about a stepbystep with respective aboverequirements. If you have documents, request you to please mail to

ravikanth8141@gmail.com Please help. ThanksRavi Kanth

Like (0)

Shawn Grant Jul 27, 2012 6:56 PM (in response to Dolores Correa)

Hi Dolores, that worked. Thank you (and sorry for the real tardyacknowledgement). Can anyone answer this question? Our Solution Manager system in which I set up the prototype as outlined in thisblog is our development SM system. We hooked this system up to our productionSM system for transports. Since then my prototype will not work. Can mydevelopment SM system be part of both a prototype and production set up? Or do Ineed a third, sandbox, system in which to prototype? Thanks,Shawn

Like (0)

Ravindran Pather Mar 6, 2013 8:07 AM

Hi Dolores , i am new to SCN and this is my first attempt at adding a comment so i am quite chaffed

with myself yes this a fantastic blogi am engaging with a client for the implementation of SOlman 7.1so we hada couple of consultnats come in and give some direction and advice.they painted a very strange scenario regarding transportsin brief they are saying that when a change document is created , 2 transport are allocatedautomaticallynow the abaper completes his developemnt and it is tested in the Dev client , the consultaant will thenrequest end user testing in the QA enviroment client . any errors detected in QA can then becommunciated to the the developer for corrections . now here is the punchline ! , i am told that thedeveloper will still be able to do the corrections on the orginal wokbench ?to my knowledge after the transport is realese to QA and further developements are required a newtransport is allocated and the process continues until final release into Prod . please can you give mesome insight into this scenario .once again thanks for sharing your knowledge and expertise Be BlessedRavi

Like (0)

Shawn Grant Mar 6, 2013 1:40 PM (in response to Ravindran Pather)

Hi Ravi, Development can be moved to QA using transport of copies. This leaves the originaltransport request open and editable in DEV. Cheers,Shawn

Herik Ribeiro Mar 9, 2013 2:48 PM

Hi Dolores, Your Blog is the best ..! Congratulations ..! I'm starting in world charm and wonder how I can get the guide (step by step) with the first steps to setup the charm in my Landscape and a checklist for this setting. Best Regards,Herik

1/6/2016 First steps to work with Change Request Managem... | SCN

http://scn.sap.com/people/dolores.correa/blog/2008/07/26/firststepstoworkwithchangerequestmanagementscenario 22/22

Follow SCNSite Index Contact Us SAP Help PortalPrivacy Terms of Use Legal Disclosure Copyright

Like (0)

Like (0)

Ying Ye Aug 6, 2015 11:25 PM

Hi Dolores, We have three BI systems DBC, ABC and PBC and we are working on ChaRM setup for this. We usePBC as domain controller and include DBC and ABC to PBC. We setup transport route from DBC >ABC > PBC and verified TMS configuration works fine. After that we logon to our solution manager (the other domain controller), follow the steps youmentioned regarding domain link creation, request domain link from SolMan and approve it in PBC.Then we see all the systems in SolMan domain controller shows up in PBC but in SolMan we don'tsee any of the DBC/ABC/PBC. In which way should we create domain link? Should we request it from SolMan or should we reqeustit from PBC? If from PBC, after approve from SolMan and those boxes show up in SolMan STMS, should we createtransport route again in SolMan or it will reference to the one already exist in PBC? The SolMan we have is in 7.1 version but this article has detailed steps about how to create domainlink so I post my question here. Thanks in advance if you can provide any suggestion. Best Regards,Ying Ye