# Transport of Copies

## **Import via TOC**

Once a transport is released, no further changes can be made to it. If a fix is required, a new transport must be created. However, a more efficient alternative is **Transport of Copies (TOC)**.

Instead of releasing the transport, you can create copies of the changes and move them to a target system for testing. Any required fixes can be added as tasks to the same transport. After successful testing, the transport can be released. This approach reduces the number of transports needed for a specific feature or user story.

#### Steps to Import via TOC:

1\. Go to the required transport and click **Actions**.

2\. Choose **Import via TOC.**

3\. Select a target system id from the drop down and click **Import.**

<figure><img src="/files/oiv12iRYF9FWEVT0OD1V" alt=""><figcaption></figcaption></figure>

4\. The successful import creates a transport of copy which gets listed in the **Transport Management** screen as shown below:

<figure><img src="/files/EmPyT7nlZZXTHx1q0pkN" alt=""><figcaption></figcaption></figure>

5. The newly created TOC request can now be used for further processing.

<figure><img src="/files/Uzh156knF34ai9tW52gc" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://releaseowl.gitbook.io/releaseowl-docs/releaseowl-user-guide/sap-on-premise/transport-of-copies.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.