Existing Landscape:

CHARM Configuration :

(CHARM client)

Create three additional clients in GDE, like local client copy from client 000 with SAP_ALL profile (this will need some extra space in GDE system, but not too much), let say you create clients 150, 200 and 350.

We assume that GDE:150 is going to be the Development system, GDE:200 the Quality system and GDE:350 is the Production system. In SCC4 assign the following client settings, roles, etc. to these clients, this is important

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" inyour 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 ofyour project. See thatin two-system landscape no test transport will be generated for normal correction SDMJ, since officially this functionality is only designed for test system, see note1419150 ChaRM: Transport of Copies (ToC) with two-system landscape.

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

In Satellite system domain controller, in client 000, call STMS (the same must be done in the domain controller system of your real landscape)

For this test landscape initially you have system GDE 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 GDE 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.

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

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, dont 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 150, 200 and 350. Also to client 000of all the involved systems, DEV, QUA and PRD systems in our example

Also you need to create the RFC connections from Solution Manager SOL:120 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, dont 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 ConfigurationGeneral 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.0CHARM_DEST W NONE CUST620 1.0This means that Charm configuration has been done in this client.

2.2. Activate BC Sets: Check note 903527Bc Set for Charm: SOLMAN40_CHARM_BASICFUNC_001

NOTE: Activation ended with errors. Repeat activation with Expert mode. It should go fine. If its end with the warning it should be OK.

Refer to toolbox thread given below for more information: http://sap.ittoolbox.com/groups/technical-functional/sap-solution-manager/solman40_charm_basicfunc_001-4149554Under Transport Management System check the following in detail:

2.3. Define Transport Routes for System Landscape: already explain in steps above-DONE2.4 Activate Extended Transport Control: apply this point to all systems in real scenario-NA2.5 Configure Transport Strategy: apply this point to all systems in real scenario-NA2.6. Activate TMS Trusted Services: apply this point to all systems in real scenario-NA2.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_SOL for example.

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.

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_SOL in our example, and choose SAP Systems 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 SOL in this real example):

In satellite system on DEV (Domain Controller) of TMS Landscape :

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.

Step 4. In Solution Manager go to transaction SOLAR_PROJECT_ADMINPlease 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

(NOTE: Com back on the previous screen by clicking on BACK button as screen once confirmed Yes leads to an entirely different screen.)

While coming to this screen you should get a prompt informing you that 'Background job for generating the IMG project has been completed.To see the created project select project and click on Display as shown below:

(NOTE: You can check the status bar that you are in GDE system DEV client i.e. 150)

http://forums.sdn.sap.com/thread.jspa?threadID=801887

Usage Example: