Transport Management
Guided Procedures (GP) content may be created and designed in one system and transported for use to another system. GP content are all development objects, folders and attribute types available in the system.
The transport procedure includes:
...
1. Exporting content from the source system
2. Importing content to the target system
3. Releasing imported content automatically or manually, depending on the settings of the target system
Depending on the transport medium, GP content can be transported in two basic ways:
· Transport to local system using the SAP NetWeaver Developer Studio (NWDS)
...
a. You create a transport request and store it as a Software Deployment Archive (SDA) file on your local computer.
More information: Creating a Transport Request
b. You deploy the transport archive to the system using the SAP NetWeaver Development Infrastructure (NWDI) or the Deploy View of NWDS.
More information:
Transporting GP
Content Using NWDI
● Transport using an SAP system endpoint
...
a. You create a transport request and export it to an SAP transport system using a previously defined RFC destination.
More information: Creating a Transport Request
b. You create an RFC destination in the target system (specifying the connection properties of the SAP transport system) and import content using the Import Transport Requests option of the Administration workset.
More information: Importing Transport Requests
Once you have transported content between systems, you need to release the imported objects. For more information, see Postprocessing Imported Objects.