Never lose in-flight work to a Quality refresh again.
A reusable, standard-ABAP framework that reconciles every transport before you refresh Quality from Production — identifying what is at risk, confirming what is still needed in writing, and handing Basis a correctly sequenced re-import list.
The refresh testers rely on is the event developers fear.
Copying Production over Quality gives testers realistic data — and quietly erases every transport that has not yet reached Production. These are not abandoned objects. They are active work: passed unit test, awaiting sign-off, queued behind a release freeze.
Work in progress vanishes
A QAS refresh copies Production over Quality. Any transport imported to Quality but not yet in Production is silently destroyed — every unreleased fix, phased-project object and in-test enhancement, gone.
Reconciliation is manual
Someone exports transport lists, compares them by hand in spreadsheets, emails developers one by one, and chases replies. A year of transports runs into hundreds of requests across teams.
It is error-prone
Spreadsheet comparison misses requests. A transport imported to Quality in March and Production in July is easily mis-classified — and the mistake surfaces as a defect weeks later.
No trail, no owner
When something is lost there is no record of who was asked, what they said, or when. The knowledge sits with one or two people and does not survive their absence.
One governed cycle — six stages, fully attributed.
Identify
The framework reads the import history of both Quality and Production, compares them, and derives the exact set of transports that exist in Quality but never reached Production. Transports of copies and other configured exclusions are filtered out automatically.
An invisible annual risk becomes a governed, measurable process.
No lost development
In-flight work is identified before the refresh — not discovered missing afterwards by a failed test or a production defect.
Days of effort removed
The identification and chasing that consumes days of manual spreadsheet work becomes a scheduled job plus a review.
Documented accountability
Every decision is attributed to a named owner with a timestamp. “Nobody told me” is no longer possible.
Audit & compliance ready
A complete, permanent trail of the reconciliation — evidence for change-management and IT audit reviews.
Repeatable, not heroic
The process runs the same way every year regardless of who is on duty. Institutional knowledge is captured in the tool.
Faster refresh window
The list is agreed and frozen before the refresh, so restoration is a controlled execution — not an investigation.
Deliberate choices, not technical accidents.
Safe by default
Where an owner never responds despite reminders and escalation, the framework can be configured to treat the transport as still required. A needlessly re-imported transport is normally harmless; a lost one causes a defect. The asymmetry is a deliberate, configurable business decision.
Survives the refresh
The framework is installed in the Development system, not Quality. Development is untouched by the refresh — so the framework and all of its collected confirmations survive the very event they manage.
Adapted, not rewritten
All landscape-specific logic — how import history is read — is isolated in a single component. Moving to a different landscape or a ChaRM-managed environment means changing one place, not reworking the solution.
Humans stay in control
The framework produces the re-import list; it never imports anything itself. The actual transport import stays a deliberate action performed by Basis through standard tools. Automation supports the decision — it does not replace the control.
Small footprint. Standard tools. No new licences.
Built entirely inside your existing landscape. The bulk of the work is a one-time build and configuration; each annual cycle thereafter is a scheduled sequence of steps with a documented result.
From first pilot to embedded runbook.
Confirm the data source
Agree with Basis how import history is read in your landscape — the transport-management API, a controlled remote read, or existing ChaRM data.
Agree the policy
Decide the default treatment for non-responses, the reminder cadence, and the escalation path.
Pilot one cycle
Run the identification step against the last twelve months and review the volume and accuracy of the candidate list before enabling notifications.
Embed in the runbook
Add the framework's timeline to the standard refresh plan so it becomes part of the governed process.
Make the refresh a controlled step — not an event to fear.
Run TransportGuard against your last twelve months and see, on your own transports, exactly what a refresh would have destroyed.