SAP Transport Requests: Workbench, Customizing and Transport of Copies

CTS organizes changes into requests and tasks. Workbench requests normally contain repository objects such as programs, classes, Dictionary objects and other cross-client development content, moving through the configured transport layer. Customizing requests record client-dependent configuration changes from IMG/table maintenance according to object category. Transport of Copies (ToC) is a separate request type used to copy selected objects to a target for testing or urgent controlled transfer without releasing/replacing the original main development request. It is not a universal substitute for proper release sequencing.

Use Workbench for repository/cross-client development changes captured by the Workbench Organizer. Use Customizing for client-dependent configuration when the application records it that way. Use ToC for controlled early testing of unreleased objects, selective copies or specific retrofit/support workflows approved by transport governance. Do not manually force object types into a request just to move them; understand how the object is registered in TADIR/customizing/object catalog and what dependencies must travel with it.

SE09/SE10 organize requests/tasks; STMS manages routes/import queues. Packages/transport layers determine standard target paths for Workbench objects. Customizing changes can be client-specific and imports may behave differently by client. Request tasks collect individual developer/configurer changes and are released before the parent request. Import logs/cofiles/data files prove technical import, but functional regression and sequence remain project responsibilities.

A developer changes a class and DDIC structure but wants QA testing before the main feature request is released. A Transport of Copies contains the current versions and is imported to QA. The main Workbench request remains open and later continues through the normal route with final changes. In another case, a company-code configuration changed in SPRO belongs in a Customizing request targeted to the correct client; putting it into a random Workbench request would obscure governance and can behave differently.

CTS transport concepts remain fundamental in S/4HANA on-premise/private cloud. ABAP Cloud/BTP introduce different transport mechanisms such as software components/gCTS/Cloud Transport Management depending on environment, but the same principles—versioned artifact sets, dependencies, route and import evidence—remain. Clean core does not remove transport governance.

Developers/configurers own correct request assignment; release managers own sequencing/routes; Basis owns STMS infrastructure/imports; architects/application leads own dependency and retrofit strategy.

SE09/SE10 show organizers and request contents; STMS handles queues/imports. The transport sequencing topic covers dependency ordering and return-code diagnosis.

Production verification: Capture request and task numbers, object list, source and target systems or clients, release and import timestamps, queue sequence, import return codes, and the exact log entry for warnings or errors. Compare repository versions when the same object appears in more than one request so an older transport cannot silently overwrite a newer fix.

Operational readiness: For production readiness of SAP Transport Requests: Workbench, Customizing and Transport of Copies, define the normal baseline and the abnormal threshold that should trigger action, plus the exact monitor or log and retention window used for diagnosis. Administrative cleanup or restart actions should be the last step after evidence is captured, because deleting requests, jobs, spool entries or logs can remove information needed to prove root cause. Document system or client dependencies and environment-specific configuration separately from transportable application content.