New developments in the Enterprise Services Repository must be tested before productive operation. SAP recommends that new developments are tested separately from the production system. To do this you normally create a transport landscape that consists of a development system, a consolidation system (for testing), and a production system. In this way you can consolidate and test the development in a separate system and finally transport it to the production system.
More information: ESR Content Transports
If you only want to import the ESR content of a delivered product into your system, then proceed as described in section Importing ESR content
You have already created a system landscape that meets your requirements and consists of development, consolidation and production systems.
The system terminates the process in certain cases with an error message when you import or transport large object sets. For more information about solving this problem, refer to SAP Note 1004684.
...
1. On the basis of your system landscape consider a transport landscape with which you set out between which systems ESR content is to be transported.
2. You transport ESR content by selecting one of the following options:
¡
Transporting ESR
Content using the file system
For a file system-based transport you perform the transport by exporting the
configuration objects from the initial system as a file and you then import
this file into the target system.
¡
Transporting ESR
content using the Change Management Service
For a transport using the Change Management Service you define your transport
landscape using XI Tracks and you control the transport process using a
Transport Studio.
¡ Transporting Objects using CTS
For a transport using Change and Transport System (CTS) you configure the source and target systems
3. In the Enterprise Services Builder you can track which contents were imported or exported by which mechanism.
More information: Searching for Transports (Enterprise Services Builder)