Change & Transport Management (CTS/TMS)

Which system should hold the TMS domain controller role, and what's the reasoning behind SAP's recommendation?

At what levels is repository modifiability controlled, and what's the hard cap for SAP_ABA / SAP_BASIS?

A developer can't change a repository object even though the client is open for customizing. Is that controlled by the system or the client change option, and where do you set it?

A new system requested to join the transport domain. Which step actually converts it from virtual to real, and who does it where?

A developer edits an SAP standard object in the development system. Is that a 'repair', and why does the classification matter?

TMS QA offers three approval levels — what are they, and must all three be used?

Imports are stuck — dictionary activation and ABAP generation never run. tp doesn't call those tools directly, so what mechanism is supposed to trigger them, and what to check?

TMS QA is enabled. A request is imported into QA but not yet approved. What's its state in the production buffer, and what happens if someone tries to import it?

A new system joins an existing transport domain. Do you need to create and set a password for TMSADM on it, and why?

A transport import is failing. To decide whether the problem is orchestration vs actual data writing, which tool does which job — tp or R3trans?

You opened production (system + client) for an urgent manual fix. The fix is done — what's the cost of leaving it open 'just in case'?

A site activates ChaRM (Change Request Management). What changes about where developers create and release change requests?

On a single-system sandbox, why does every change request come out local no matter what the developer does?

Is a TMS transport domain limited to a single DEV-to-QA-to-PRD landscape?

A future QA system won't be installed for months, but dev teams need to keep releasing transports now. Why define it as a virtual system instead of just waiting?

A developer needs a modification to an SAP standard object to travel to QA and production. What makes that transportable, and what's the precondition?

What distinguishes a consolidation route from a delivery route in TMS, and which one carries the transport layer?

You're moving repository objects between dev systems. Which relocation type changes the source system but keeps the package — vs moves a whole package onto a new transport layer?

On the transport directory you see files for request SIDK9nnnnn. Which file is the cofile vs the datafile, and what's the export op code in a log name?

Why does a change request give each developer their own task rather than letting everyone write into the request directly?

A developer releases their task, then realizes they need one more change. Can they keep using that task?

You release a local change request. What does and doesn't happen compared to releasing a transportable one?

In a name like R3TR PROG ZFOO, which part tells you it's a whole container vs a subobject — and which part is the object type?

In request name SIDK9nnnnn, what does the K9 segment tell you, and what happens after nnnnn hits 99999?

What does a CTS project actually give you operationally, and what's the CTS Project Status Switch for?

Where can you run transport imports from — and how does that differ from where TMS configuration must be done?

Is the workbench-vs-customizing request distinction about the kind of change (code vs config)?

You're wiring up transports from dev to QA. Which pieces must all be in place, and what's the one teams forget?

When you change one screen of a big ABAP program, why does the transport record only that LIMU subobject and not the whole R3TR PROG?

You just built a system as a copy of another. Why must you re-initialize CTS, where, and what's the trap?

You need customizing to route to a specific client (not just a system), or to multiple consolidation targets. What setting enables that, and what construct does it introduce?

A developer fixes an object in a system that isn't its source system. What happens to that change over time?

Transports won't import at all. Which background job must be scheduled, in which client, as which user — and which scheduling program should you avoid?

Why must a customer package start with Z or Y, and what constraint does that put on what it can contain?

In terms of client scope, what's the reliable rule for workbench vs customizing changes — and where's the exception?

Given a development object name, how do you tell which name range it's in — SAP, customer, or reserved namespace?

A mass import throws syntax errors on code that you know is correct. Why does TMS import by phase across all requests rather than finishing one request at a time?

Import-all and single-import icons sit dangerously next to each other in STMS. How do you actually prevent an accidental full-queue import?

A developer ignores the warning and creates a custom object in the SAP name range. What's the real risk, and why isn't the warning cosmetic?

TMS calls tp and R3trans to do transports. What infrastructure must all servers in the landscape share, and what breaks if they don't?

A request was imported into the consolidation (QA) system. How does it get into the production import buffer — automatically or by hand?

You're running tp from the command line for buffer recovery. What must you always pass it, and where does that file live?

A tp import finishes with return code 8. Is the transport usable, and how does that differ from a 12?

Map the CTS terms integration, consolidation, and delivery onto a standard 3-system DEV/QA/PRD landscape.

A change was put in a transportable request but still won't export. How does the source system decide transportable vs local?

The owner releases a transportable change request. Which four things happen automatically — and is buffer entry one of them?

What are the principal transport import phases, in order — and which phase must precede which to avoid failures?

What are the three task types, and which one do you actually get when editing an SAP standard object in your own dev system?

A colleague says 'just transport the parameter change through CTS.' What does CTS actually manage, and what falls outside it?

You need to move the TMS domain controller to another system. What are the two ways, and which preserves your transport routes?

How can you tell from its source system whether an object is customer-created vs SAP-delivered?

How does the system decide, at edit time, whether a changed object is 'at home' (transportable) or 'foreign' (local)?

What system change option does SAP recommend for each tier, and what's the risk of leaving QA Modifiable?

You need to move specific objects to an arbitrary system without affecting their source-system identity. Why a transport of copies, and how does it differ from a normal transport?

You need piece lists and delivery functions, not just normal transport handling. Which of SE01 / SE09 / SE10 do you open, and how do they relate?

What does a package's transport layer control?

Why is transporting Customizing through gCTS awkward, and what does SAP recommend to make it manageable?

With gCTS you pulled Customizing into one client; why is it missing in the other clients of the same system?

The gCTS Fiori app is unavailable but you need basic gCTS operations; what fallback does SAP provide?

Users say requesting a transport through Cloud ALM has no value help and takes ages; what causes these quirks?

To let SAP Cloud ALM steer your transports, what must the admin activate on the connected S/4HANA systems, and where?

You refreshed the QA system from a production database backup; why is its STMS import queue now untrustworthy, and what do you rebuild it from?

Your team wants Git-style continuous integration for ABAP transports; what is gCTS, and does adopting it mean retiring STMS?

In gCTS, where does a released development transport actually go, compared with classic CTS?

You want to use the gCTS Fiori app on SAP S/4HANA 2023; can you just switch it on, or is there an install step first?

Before rolling out gCTS across dev, QA and prod, what must exist on every participating SAP system?

What exactly happens behind the scenes each time you release a gCTS transport request?

Your developers build side-by-side extensions on SAP BTP; how can CTS+ bring those under the same transport governance as your ABAP systems?

When you create a gCTS repository it asks for a virtual SID; what constraint applies to it and what does it change in your transport landscape?

Under gCTS, what are the two ways a target system gets its transports, and how is the data ultimately applied?

gCTS lets you roll a target system back to an earlier commit; why does that not save you when a transport dropped a table column?

Can you retire classic STMS once gCTS is live, or are there change requests gCTS simply will not carry?

In S/4HANA you do not have to configure TMS by hand in STMS. How can the setup happen automatically, and what does it create behind the scenes?