You must perform. all TMS activities in your satellite systems and not in your SAP Solution Manager system.
2. Define Transport Routes for System Landscape
In this IMG activity, you define transport routes between the systems in your system landscape. For more information, see the TMS online documentation in transaction STMS by choosing Help -> Application Help -> Configuring TMS.
Transports are supported in the standard transport layer of each client. When you configure transport routes, note that only consolidation routes that are assigned to the standard transport layer of the relevant exporting client are taken into consideration. For each exporting client, exactly one target client and one target group are permitted.
We recommend that you assign exactly one development system to a production system, and that these two systems are connected by exactly one unique transport track.
If a development system and a production system are connected by more than one transport track, this may lead to inconsistencies within the transport distribution. This type of transport configuration cannot be supported by Change Request Management, and may cause inconsistencies within the tools involved.
In this IMG activity, you activate extended transport control in the Transport Management System. For more information, see the online documentation in transaction STMS by choosing Help -> Application Help.
In this IMG activity, you:
In the transport tracks where the software distribution is controlled by Change Request Management, you must deactivate the QA approval procedure in the TMS, since this procedure is incompatible with the approval procedure in Change Request Management. Additionally, you have to activate the "Single transports" strategy. This prevents you from accidentally executing "Import All". All transports within the system landscape of Change Request Management must be processed by project imports.
For more information, see the online documentation about the TMS in transaction STMS by choosing Help -> Application Help.
Proceed as follows:
(The quality assurance mechanism is used implicitly but not within the TMS context.)
When you activate "Single transports", manually executed single imports cannot be imported again by using "Import Project". If you want to execute these single imports again by using a subsequent "Import Project", you have to set the corresponding transport option. We recommend that you only use the transport functions of Change Request Management.
In this IMG activity, you activate TMS Trusted Services in the system where the transport domain controller runs.
In this IMG activity, you define inter-domain links.
If multiple transport domains are used and projects in the Solution Manager have been defined as cross-domain projects, you must define inter-domain links between the transport domains, regardless of whether change requests are moved between domains or not. If, for example, the Change Request Management system is in domain A , but the satellite systems between which requests are transported is in domain B, Change Request Management has to trigger transports in a foreign domain. This is only possible by means of domain links.
There is a permanent network connection between the systems in the domains, similar to the connection between systems within the same domain.
The domain controller systems in all the domains run on SAP Web AS 6.10, or higher.
Create inter-domain links as described in the online documentation. You can access the documentation In transaction STMS by choosing Help -> Application Help -> Configuring TMS -> Configuring Links Between Transport Domains -> Domain Links.
In this IMG activity, you check whether your transport domain has been configured correctly.
For more information, choose Help -> Application Help -> Configuring TMS.
Since Change Request Management reads important information about the system landscape (such as the transport routes) from the individual domain controllers, you must make sure that you generate RFC destinations from the Change Request Management system to client 000 of all domain controllers in the system landscape.
For more information about generating RFC destinations, see the following IMG activity: SAP Solution Manager -> Basic Settings -> SAP Solution Manager System -> System Landscape -> System Landscape Settings -> Generate RFCs.
Change Request Management uses the import functions of the Transport Management System (TMS). The TMS remote infrastructure is based on RFC connections that point solely to the 000 client of a target system. The operator and administrator users need to have import authorization for client 000 of all target systems.
For more information about import authorizations and the trusted systems concept, see Configuration Guide: SAP Solution Manager 4.0, and the online documentation for Change Request Management.
can 參考notes：913232 關於import權限
来自 “ ITPUB博客 ” ，链接：http://blog.itpub.net/47406/viewspace-720304/，如需转载，请注明出处，否则将追究法律责任。