First Steps To Work With Charm

SAP Network Blog: First steps to work with Change Request Manageme... http://weblogs.sdn.sap.
com/pub/wlg/10429
Blogs
First steps to work with Change Request Management Subscribe
scenario Print
Dolores Correa Permalink
Business Card Share
Company: SAP Spain
Posted on Jul. 26, 2008 06:20 AM in SAP Solution Manager
First steps to work with Change Request Management

scenario
With the following steps you will be able to create a test landscape to practice with the Charm scenario in Solution Manager 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.
Step 1- Create the test landscape

Usually 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, and you 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 some extra 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 the Production
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
1 of 27 26-01-2011 18:54
SAP Network Blog: First steps to work with Change Request Manageme... http://weblogs.sdn.sap.com/pub/wlg/10429
The indications given for this test case from now on also apply to for your real TMS landscape, to DEV, QUA and PRD system.
2 of 27 26-01-2011 18:54
Note:
In ChaRM we do support two-system landscape, to use it you should firstly configure the consolidation route in STMS correctly.
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 in each of your project.
See that in two-system landscape no test transport will be generated for normal correction SDMJ, since officially this functionality is
only designed for test system, see note 1419150 ChaRM: Transport of Copies (ToC) with two-system landscape.
Step 2- Configuration of TMS for this scenario according to Charm prerequisites

In Solution Manager, in client 000, call STMS (the same must be done in the domain controller system of your real landscape)
Note: SMM client 001 does not need to take part of your TMS landscape.
3 of 27 26-01-2011 18:54
Select Transport Routes icon:
For this test landscape initially you have system SMM and none transport route defined (for a real landscape you will have the three
system boxes DEV, QUA and PRD):
Make double-click on system SMM and fill the following values (or in the box of the development system and after in the 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.
4 of 27 26-01-2011 18:54
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).
5 of 27 26-01-2011 18:54
Create the consolidation transport routes to SMM:200, transport route must be CLIENT SPECIFIC for the use in Charm scenario, this is
real important!
From development system to quality system you need at least two consolidation routes, SAP and ZXXX.
Go with the pencil from the system SMM to system SMM and get this pop-up:
6 of 27 26-01-2011 18:54
I create the consolidation route for transport layer SAP and I do the same to create transport route for transport layer ZSMM (for
customer developments).
In case of a real landscape you need to choose from which system to which system and client.
7 of 27 26-01-2011 18:54
I make the same to create the Delivery transport route from SMM:200 to SMM:300, delivery routes are always from quality to
production systems.
8 of 27 26-01-2011 18:54
Finally you will get the following situation:
Save and distribute the changes:
9 of 27 26-01-2011 18:54
All the previous work has to be done in the satellite systems in real landscapes.
Step 3- Review of the main configuration points in SPRO

1. 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_..._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.
In transaction SMSY:
Also you need to create the RFC connections from Solution Manager SMM:001 to client 000 in the system that is the domain controller
of your real landscape, this is really IMPORTANT!!! You will see more information about this in spro point “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 be installed. If you move
the domain controller to PRD system, as it is recommended, don´t forget to create the RFC connection to client 000 of this domain
controller system.
2. In SPRO go to Scenario-Specific Settings-->Change Request Management -->Standard Configuration
10 of 27 26-01-2011 18:54
General Activities:
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 inter-domain links
If you go to STMS in the solman system you can see that the solman system is in transport domain DOMAIN_SMM for example.
11 of 27 26-01-2011 18:54
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 solman system is
going to call TMS functions in the transport domain of DEV, QUA and PRD, the TMS of solman must know this 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.
- 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.
12 of 27 26-01-2011 18:54
Enter system name, DEV for example, hostname where is installed the system and system number, all this information is 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 the address 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. This information is distributed
to all systems in the domain whose controller you are currently logged on to. A transport profile 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):
And this in the DEV system (called ED4 in this real example):
13 of 27 26-01-2011 18:54
To check that the domain link is ok go in solman system and in development system to STMS->transport routes, in the top of the
screen you will see that in solman system the systems belonging to the other transport domain appear like boxes 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 domain where 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 import authorization) 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 with import
authorizations.
Under Change Request Management:
2. 10. Set Project Assignment of Requests as Mandatory: not totally mandatory but this will avoid users creating transport orders
directly in development system. All transport orders in development system in your real landscape must 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 Charm scenario.
Now you are ready to create a project.
Step 4. In Solution Manager go to transaction SOLAR_PROJECT_ADMIN

Please go to http://service.sap.com/rkt-solman
Select SAP Solution Manager 7.0, select Learning Map for Supp Organizations/Serv providers, open Change Request Management
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 Manager Documentation. For
our test case select a maintenance project.
14 of 27 26-01-2011 18:54
- In System Landscape Tab
o Systems: here you have to enter your logical component
Take into account that all systems that belongs to the TMS landscape must be assigned to the same logical component,
because all system must have the same 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 of two
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 Charm scenario can not be
activated. This point is always the point that more problems gives in the activation of Charm scenario!!!
- In IMG project tab: define always a project in the development system ONLY! You need to define this project in the development
system in order to assign to this project all transport orders that you are going to create via a Change request 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.
15 of 27 26-01-2011 18:54
- In Change Request tab: Select “Activate Change Request Management”
Select Create Task List
16 of 27 26-01-2011 18:54
Select the name of your Maintenance Cycle also called Project Cycle.
17 of 27 26-01-2011 18:54
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 in the screenshot) is
being created.
18 of 27 26-01-2011 18:54
Service Desk Transaction Tab: This tab is not appearing in SP9 but appears in SP13 and above and shows the SDMN document for this
project cycle.
The task list is one representative of the cycle and represents the system landscape tracks with tasks to be used by an IT 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 maintenance cycle, in SP13 and
above it are recommended to go to the maintenance transaction directly, via CRM_DNO_MONITOR (select transaction type SDMN) and
activate and change the phase via Actions in the transaction 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 Application Log 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 being created.
19 of 27 26-01-2011 18:54
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 your real 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 to Solman system.
This will ensure that you do not stop the TMS in the production landscape.
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
- Change Request Management scenario: Working examples
- Change Request Management scenario: Retrofit Functionality
Dolores Correa is a technology consultant for SAP Spain.
Your comments and experiences about the contents are very welcome.
Comment on this weblog
Showing messages 1 through 31 of 31.
Titles Only Main Topics Oldest First

Connect to production landscape
2010-12-15 04:32:15 Natalyia Veleva Business Card [Reply]
Hello Dolores,
you wrote:
"When everything in the test scenario is running fine, then you can connect the Production System landscape to Solman system.
This will ensure that you do not stop the TMS in the production landscape."
20 of 27 26-01-2011 18:54
Could you please explain this step in detail?

As far as I know, you need to switch the production landscape to client specific and completely change the transport routes so that
they can be client specific. One also has to create a new ChaRM project and activate it. The production project can not be activated
if the production landscape is not client specific.
Background job
2010-07-07 22:13:26 Nayab Siddiqui Business Card [Reply]
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
Problems with creating _TRUSTED RFC conns to SolMan clients

2010-06-17 00:44:30 Nenad Nikolic Business Card [Reply]
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 same Solman (step 3)?
Please take a look at forum's toppic where I explained my problem:
http://forums.sdn.sap.com/thread.jspa?forumID=156&threadID=1712261
Thank You in advance for Your help.

Nenad
Grate Work
2010-05-25 22:03:36 kalenthiran p Business Card [Reply]
HI,Really help me lot,in my case We have three system landscape (DEV,QA,PRD),in dev we have two client (100,200)we are doing
customizing in client 100 and workbench changes in client 200,QA 300 PRD 330.for charm configuration how i have do define
transport layer and route and logical componet
Grate Work
2010-05-27 06:59:44 Dolores Correa Business Card [Reply]
Hello,
See SDN blog:
Change Request Management scenario: Usual questions and known errors
https://weblogs.sdn.sap.com/pub/wlg/15116
Point 1 and 2.
Hope this helps,
Dolores
Grate Work
21 of 27 26-01-2011 18:54
2010-06-03 23:56:11 kalenthiran p Business Card [Reply]
Hi,
Thanks,its working.How and where i can define change manager for a system or Ibase.
Outstanding!
2010-05-13 14:13:40 Jose Garcia Business Card [Reply]
Thanks for taking the time to do this; well done.
Jose
Charm configuration
2010-03-02 04:14:13 Ana Abad Business Card [Reply]
Hello Dolores,
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 the change request management
in solar_project_admin transaction.
- The project is not released. Hence cycle can not be created -- when I push the buttom "create task List" in the same transaction.
The system landscape are two system: dev --> prod, we don't have quality system. Could it be the cause of the errors?
How can I follow the configuration?
Thanks for you help and you great blog and best regards,
Ana.
Charm configuration
2010-03-10 12:27:32 Kevin Richman Business Card [Reply]
Ana,
From what I have seen and experienced, ChaRM really wants a 3 system landscape at a minimum. Even if this means creating
a logical component and transport route that goes through 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 transport routes and
landscape.
Charm configuration
Hi Ana,
Send me an email to d.correa@sap.com, I will call you if you want.
Best regards,
Dolores
Configuration For WorkFlow In Solution Manager

2009-08-11 05:09:27 Sandeep Menon Business Card [Reply]
22 of 27 26-01-2011 18:54
Hi Dolores ,
I have a requirement to do a workflow for Transaction 'CRM_DNO_MONITOR' In Solution Manager. If you have any information
details on the configuration for workflow, Any business object that can be used for workflow . Please do provide me the details.
There are two process,

1. I need the workflow to trigger when a ticket is created
2. When the status of the ticket is changed.
Very helpful Blog

2009-07-09 23:23:38 Amrita Amrita Business Card [Reply]
Its really helpful blog. Very good effort.
Amrita
Great post!
2009-06-15 16:44:51 Fabio Sato Business Card [Reply]
Hello Dolores.
Your posts are perfect! I made a SDesk and a ChaRM only with your informations. Thank you so much. 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 "Go Live", is able to me to import the
request to productive environment. Wouldn't have a check or a lock on this schedule. The status of the correct document is "in
develop". Can you help me?
Sorry for this inconvenience. I already try everything.

Great post!
Hi Fabio,
Could you please give me your e-mail address? I will send you some slides where you can see which action can be done in each
phase for normal and urgent correction.
Best regards,
Dolores
Great post!
2009-09-16 05:05:42 nsingh sihag Business Card [Reply]
Hi Dolores!
we are having a different scenario. Our Landscape is something like this.
ECD(DEV)->EC1(QA1) and
EA2(QA2)->EAP(PRD)
we are not having any network connectivity in between DEV-QA1 to QA2 and PRD. DEV and QA1 are in one network and
QA2 and PRD are on other network.
23 of 27 26-01-2011 18:54
Now we need to implement ChaRM from Dev to PRD, so please suggest me how to implemet this. Whether this is possible
or not? what different settings we have to do from standards.
Aslp please send me the configuration Docs and Slides on my mail ID narpal.singh@gmail.com.
It would be very great if you suggest us on this.

thanks
narpal
Great post!
2009-06-18 13:17:22 Srujan Kumar Jakkampudi Business Card [Reply]
Hi Dolores,
Your compilation helped me a lot in understanding the underlying concept of Service Desk and Charm Activation. Can you
pls share the slides that you mentioned to send Fabio.
My email id is srujan.sap@gmail.com
Thanks in advance.
Srujan
Great post!
2009-06-17 05:46:11 Fabio Sato Business Card [Reply]
Hello Dolores.
Thank you so much. You are my reference in Solution Manager.
My email: fabiosato@globo.com
Best regards,
Fabio Sato.
CHARM with multiple DEV and QA systems

2009-05-06 10:27:45 Brad Donovan Business Card [Reply]
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?
CHARM with multiple DEV and QA systems
2009-07-03 02:20:01 Sadi Yilmaz Business Card [Reply]
Hi Brad,
We have the same landscape, could you find any solution for this scenario?
one question about charm landscape

2009-04-30 19:24:11 Carol Wang Business Card [Reply]
do you meet such scenario: one DEV -> one QAS-> two prd? can this possibe?
24 of 27 26-01-2011 18:54
Status in CHaRM workflow with tasks in TMS

2009-03-26 01:46:31 Jamuna Nithyanandam Business Card [Reply]
Thank you for a very detailed blog.
After we have the tms set up for satellite systems, project created and activated for CTS in solution manager:
How do we set the status in the CHaRM workflow with the corresponding task in Scheduler? Can you please help me with this
query.. I am really not sure how to proceed further.
Thank you very much,

Jamuna Nithyanandam
using Solman DEV and Solman PRD

2009-02-26 06:45:48 Aldo Ortiz Business Card [Reply]
Hello Dolores,
Thanks for your very complete definition. We have a case where we are using a Solman DEV, client 100 and SolMan PRD, client
300. We have a transport layer already defined where we can create transport request and send to the Solman PRD (for example
for Service Desk customizing). Now we are 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 same SolMan DEV?
I appreciate your comments.
Regards
Aldo

Hi Aldo,
In this case you have a real TMS landscape from DEV:100-->PRD:300 so consolidation routes 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 real TMS.
So, in this case I would suggest to create the test scenario in PRD or in other development system of other product, for
example in the development system of your R/3 system.
Hope this helps,
Dolores
2009-09-24 06:44:14 HAI HUYNH Business Card [Reply]
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.
When I run it automatically in EHP1 after hitting execute in the IMG, I check the BC Sets and nothing is activated. So,
should I manually activate BC Set Solman40_CHARM_BASICFUN001 in SCPR20.
25 of 27 26-01-2011 18:54
Thanks
Hello,
For EhP1 firstly you run solman_setup. In the Basic Configuration in point 7 BC Set
SOLMAN40_CHARM_PROXYFACT_001 is activated.
After you have to follow the spro point Change Request Management specailly an entry called "Activate Activate BC
Sets".
Hope this helps,
Dolores
Thanks for the quick response...
I ran the automatic configuration when i executed Activate BC Set for CHARM in the IMG.
If I check in SCPR20, SOLMAN40_CHARM_BASICFUNC001 has 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...

Hi Dolores,
For EHP1, how should we take the approach to move transport across clients. We are doing an upgrade and
would like to to move transport as well to our Golden Client in DEV. (DEV 100- Custom Development , DEV
200-Golden Client)
Do we configure a different route in the TMS and just include DEV-200 in the Locigical Component. I would
assume that we use the Task List to do the import manually.
Thanks for your advice...

Hello,
I checked this and the correct name for the BC Set is SOLMAN40_CHARM_BASICFUNC_001, as far as I know
this BC set should be activated running the indicated spro point but also running Activate BC Set in the Basic
Configuration point of solman_setup according to the activation time in my solman test system.
Anyway follow note 903527 in order to activate this BC Set in expert mode and chosing overwrite option too.
Hope this helps,
Dolores
26 of 27 26-01-2011 18:54
Thanks Dolores... I'm use to using that note in the past. I just think there is a bug with EHP1 for that img
activity...
Take care and great work. Much appreciated

2009-08-05 01:55:23 Boris Milosevic Business Card [Reply]
In our case we have standard transport route ZDEV for the standard CHARM transports ( DEV:330-PRD:100). We created
test clients in our DEV environment and created new consolidations route ZCHM with source client charm development
client 800. (qas 801 prd 802) and CHARM test environment works fine :)
rgds
Boris
Gr8 Job Done !!

2008-07-26 20:47:22 Anand Rangarajan Business Card [Reply]
This was the Most frequently asked question in SDN solman forum...One of the best Compilation...
Keep it up...
Regards,
Anand
Showing messages 1 through 31 of 31.
27 of 27 26-01-2011 18:54

First Steps To Work With Charm

Загружено:

Сведения о документе

Исходное описание:

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

First Steps To Work With Charm

Загружено:

Авторское право:

Доступные форматы

SAP Network Blog: First steps to work with Change Request Manageme... http://weblogs.sdn.sap.

First steps to work with Change Request Management Subscribe

First steps to work with Change Request Management

Step 1- Create the test landscape

DEV:100 -->QUA:200 -->PRD:300

Customizing role for SMM client 100

Test role for SMM:200

Production role for SMM:300

Step 2- Configuration of TMS for this scenario according to Charm prerequisites

Select Transport Routes icon:

Finally you will get the following situation:

Save and distribute the changes:

Step 3- Review of the main configuration points in SPRO

Especially important point is:

2. In SPRO go to Scenario-Specific Settings-->Change Request Management -->Standard Configuration

2.1. Run “Activate Integration with Change Request Management”

CHARM W NONE CUST620 1.0

CHARM_DEST W NONE CUST620 1.0

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.7. Activate Domain Links: you have to create inter-domain links

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

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

- Log on to the domain controller in the other domain.

- Call Transaction STMS in client 000.

- Choose Overview -->Systems. The system overview appears.

- Confirm the prompt and distribute the configuration.

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

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

Under Change Request Management:

2. 11. Maintain Number Ranges: run this.

Now you are ready to create a project.

Step 4. In Solution Manager go to transaction SOLAR_PROJECT_ADMIN

- In System Landscape Tab

o Systems: here you have to enter your logical component

In our test case you will have this:

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

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

Select Create Task List

As summary pay special attention to the following points:

- Transport routes must be set client specific

Now is time to check the RKT material, iTutors:

to fully understand the complete process.

Dolores Correa is a technology consultant for SAP Spain.

Titles Only Main Topics Oldest First

Could you please explain this step in detail?

This error occurs if the background job is not scheduled

Problems with creating _TRUSTED RFC conns to SolMan clients

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

Thank You in advance for Your help.

2010-06-03 23:56:11 kalenthiran p Business Card [Reply]

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

How can I follow the configuration?

Configuration For WorkFlow In Solution Manager

There are two process,

Very helpful Blog

Its really helpful blog. Very good effort.