Change & Transport Requests (CTS)

When a transport request is exported, what two files are written and where do they go?

What do the transport step letters E, I, A, G, and P mean?

What does Transport Organizer Tools (SE03) provide, and why is caution needed?

What is the difference between a Customizing request and a Workbench request?

What registration is needed before developers create or modify objects?

What is a package in the ABAP repository, and what is special about $TMP?

What is a project IMG, and how are IMG activities classified?

What extra options does the extended Transport Organizer (SE01) add?

How do you find and delete obsolete transport requests, and which parameters govern retention?

Which programs perform the import at OS and SAP level, and how must RDDIMPDP be scheduled?

What is the difference between a correction and a repair in CTS?

Which object version does an import bring in, even if the source changed again?

How are changes recorded in CTS, and what is the format of a request/task ID?

Where do released transports go, and how is the import queue ordered?

Where is object versioning normally kept, and how can downstream systems retain versions?

What is Customizing, and which tool and transaction guide it?

What does the tp parameter NO_IMPORT_ALL=1 do, and when is it the standard?

How do customer objects avoid name conflicts with SAP objects?

What do transport return codes 0, 4, and 8+ mean?

What is an end mark in the import queue?

What does the Transport Organizer (SE09) do, and in what order is a customizing request released?

What do the manual tp commands connect, addtobuffer, import, and import all do?

How does a local change request become transportable?

When do Customizing changes become permanent?

What does assigning an object to a task do, and what happens when the request is released?

What does CTS+ transport, and why is AS ABAP always required?