Transport Management Without Losing Your Sanity
Transport management is the leading cause of production incidents in SAP landscapes. Not HANA performance. Not authorisation gaps. Transports.
Why Transports Go Wrong
The Correction and Transport System (CTS) was designed in an era when SAP landscapes were simpler. Three systems, one development path, regular maintenance windows. Modern landscapes are nothing like that.
Today you have parallel development tracks, hotfix lanes, emergency patches, and business units that each believe their change is the most critical. The CTS wasn't designed to arbitrate those conflicts — that's your job.
The Three-Way Mistake
The most common failure pattern: developers move transports directly to production without a test system import first. "We already tested it in DEV," they say. DEV and PRD have been diverging for six months. This is always wrong.
Rule without exceptions: every transport touches QAS before PRD. No matter how small. No matter how urgent. If the CFO is standing over your shoulder, especially then.
Building a Sensible Release Cycle
A sustainable transport cycle has three layers:
1. Regular release window — weekly or biweekly, planned, communicated. Business knows when changes land. 2. Emergency lane — a documented, fast-track process for P1 fixes. Not a shortcut, a defined path. 3. Freeze calendar — locked periods around month-end, year-end, audits. Non-negotiable.
The Friday Embargo
Do not import to production on Friday afternoon. This isn't a guideline — it's a hard rule that every team eventually learns after breaking it once.
Transport Sequencing: The Hidden Trap
Transports have implicit dependencies that the system doesn't enforce. If transport B was created after transport A and touches the same objects, you must import A before B. Import them out of order and you've overwritten A with an older state.
Monitoring Your Import Queue
SM37 for background jobs, STMS for queue state, and the tp logs in the work directory. Know where these are before you need them under pressure.
The tp log is in `/usr/sap/trans/log`. The filename pattern is `<SID><MMDDHHMM>.log`. Grep for `ERROR`, not just the return code — RC=8 can be informational or fatal depending on context.