Show TOC Start of Content Area

Procedure documentation Imports Locate the document in its SAP Library structure

Use

In an import, you import the content of the software component version (archives or source code) or change requests (source code) in the import queue into a specified system:

...

       1.      Transport of change requests

                            a.      The CMS imports the source code into the appropriate repository (DTR or XI).

                            b.      The CMS triggers the activation of the imported changes. A central build is performed for the source code in the CBS. If a runtime system has been configured, the source code is deployed here automatically.

                            c.      Finally, the CMS places the change request in the import queue of the follow-on system.

       2.      Transport of software component versions

                            a.      The CMS imports the source code into the appropriate repository (DTR or XI).

Note

When XI content is distributed, there is only a repository import; there is no activation (CBS) or deployment.

                            b.      The CMS imports the archives into the corresponding CBS buildspace and triggers the activation of the imported changes. A central build is performed for the source code in the CBS. If a runtime system has been configured, the source code is deployed here automatically.

                            c.      The CMS places the software component version in the import queue of the follow-on system.

 

Note

In both cases, the archives are deployed only if the import also generates or contains deploy archives. If the import contains only compilation libraries, there is no deployment.

Example

The SAP_BUILDT software component delivered by SAP contains only libraries, which is why there is no deployment when this component is imported.

Prerequisites

You are in Transport Studio.

You have modified and activated source code in SAP NetWeaver Developer Studio, and released it for transport. Alternatively, you have checked a software component version in to the Transport Studio, or received it from a predecessor track.

Procedure

...

       1.      In the track list, select the track in which you want to perform the transport.

       2.      Choose the tab page of the system into which you want to import the software changes.

       3.      In the list, select the transports that you want to import.

Recommendation

We recommend that you select all transports by choosing Select All.

       4.      Choose Import.

Result

You have imported one or more transport requests in to the selected system.

 

 

End of Content Area