Hands-on SAP Basis guidance — transports and the Change and Transport System, system refreshes and client copies, and the operational discipline that keeps landscapes stable.
SAP Basis is the technical layer every SAP application runs on, and most of the incidents that reach a CIO start here: a transport imported out of order, a refresh whose post-processing was incomplete, a landscape whose configuration nobody has reviewed since it was built. The articles in this category are written for the people doing that work, with the specifics — transaction codes, tables, return codes, runbook steps — rather than a summary of what Basis is.
The emphasis throughout is on the process failures behind the technical ones. Most transport errors are release-discipline problems that surface at import time; most refresh problems are checklist problems. Where a topic has an authoritative SAP definition, it is cited so you can check it against the source rather than take our word for it.
When to run a client copy and when you need a full system refresh, the copy profiles explained, and the post-refresh steps teams forget until production breaks.
A diagnostic guide to failed SAP transports: what each return code means, which import step failed, and how to fix the common causes without making it worse.
How the SAP Transport Management System actually works: transport domains, routes and layers, request types, the import queue, and where transports go wrong.
A reference for the SAP transport request tables — E070, E071, E07T, E071K, TRBAT — what each stores, how they join, and the queries worth knowing.
How to tell when your SAP Basis team is stretched too thin — warning signs in patching, monitoring, projects, and on-call, and what to do about it.
Practical ways to cut SAP Basis workload and team cost in 2026 — automation, AI, managed services, and the operating-model changes that actually stick.