How does a Transport of Copies differ from a Workbench Request? Note: There are 2 correct answers to this question

Question

Options

• AWhen creating the transport request, a target system without a consolidation route can be selected
• BNo cofile is created, when releasing the transport request with the Transport Organizer (SE09).
• CWhen importing, the transport request is not forwarded to subsequent delivery systems.
• DAfter the import, repository objects in the target system are classified as copies

• A
  8% (2)
• B
  8% (2)
• C
  85% (22)

Explanation

A Transport of Copies is used in SAP systems to transport objects without the intention of them being part of a consistent change management process. Unlike Workbench Requests, which are meant for transporting development changes through the system landscape, Transports of Copies do not enforce a sequence and do not require a consolidation or delivery route. Therefore, when importing a Transport of Copies (C), it is not forwarded to subsequent systems in the landscape as a normal Workbench Request would be, allowing for more flexibility in transporting objects to specific systems without affecting the entire landscape. After the import (D), repository objects in the target system are classified as copies, emphasizing their nature as potentially temporary or test changes that are not part of the standard transport route, providing a clear distinction from objects transported via Workbench Requests.

No community discussion yet for this question.