SAP Transport Import Checklist (Free, PDF)

0%

0 of 27 items complete

9 critical items still open - these are the highest-risk gaps.

Download checklist:

Before release

Request contains only objects for one change ticketCRITICALPeer code review completed and comments closedCRITICALCode Inspector or ABAP Test Cockpit run with no unresolved errorsCRITICALUnit tests and manual test cases recorded as passedAuthorization checks present in custom code and roles updatedNo debug breakpoints, hard-coded users or test data in the codeDependent transports and customizing identified and ordered

QA validation

Request imported to the quality system in the agreed orderCRITICALBusiness tester signed off with evidence attachedCRITICALRegression test of related processes completedInterfaces tested with a representative file or messagePerformance checked with realistic data volumesBackground job definitions and variants prepared if needed

Approval and planning

Change approval recorded by the change owner or boardCRITICALImport window agreed and users informedBasis confirmed that the import queue holds no unrelated requestsRollback or correction plan written, including who decidesSupport team briefed on what changed and what to watch

Production import

Import order confirmed in STMS against the planCRITICALImport return code checked and any warnings readCRITICALGeneration or activation errors checked after importSmoke test run by the owner immediately after importRelated jobs, authorizations and number ranges verified

After import

Ticket updated with import date and resultCRITICALTransport log updatedMonitoring of dumps (ST22) and logs (SM21) for first business dayLessons from any incident recorded for the next release

Every critical item must be checked before importing to production. If a critical item is open, delay the import or document an approved exception.

Automate change evidence

Optional: talk to us about collecting test and approval evidence for each SAP change automatically.

Optional. The tool and every export work without this. No spam.

How to use the checklist

Work through the groups in order for each change, or for a release bundle. Tick items as evidence appears, and export a PDF to attach to the change ticket. Critical items are the ones that should block an import when missing. For emergency changes, keep the same list but record which items were postponed and who approved the exception. Reviewing completed lists regularly shows where your process fails.

One list per release or change
Attach evidence to the ticket
Record exceptions with an approver
Review failed items monthly

Why order and evidence matter

Transports often depend on each other: a data element, then a table, then a program that uses it. Importing out of order can produce activation errors or short dumps. Evidence matters too: auditors and customers increasingly ask who approved a production change and what was tested. Segregation of duties is part of this, since the person who writes the change should not be the sole approver of the import.

Common mistakes

Frequent problems include emergency imports with no retrospective approval, mixed requests that carry unrelated work, and no named person for post-import checks. Another is relying on developers to test in QA with their own authorizations. Run QA with a business role, and keep a short, written rollback plan, even if the plan is to import a corrective transport.

Emergency changes with no review afterwards
Mixed-purpose requests
Testing with developer authorizations
No rollback plan

Frequently Asked Questions

Does SAP have its own tooling for this?

Yes. The Transport Management System (STMS) controls imports, and tools such as Change Request Management in SAP Solution Manager or SAP Cloud ALM can add approvals and traceability. This checklist works alongside them or where they are not in use.

Which items are truly critical?

Those that, if missed, can stop production or break compliance: review, static checks, QA sign-off, approval, import order and return code, and ticket update. Your organisation may add others.

How do I handle emergency fixes?

Follow a shorter path with the same controls recorded afterwards. Define in advance who can approve an emergency, require a retrospective review and log the exception in your transport record.

Is this suitable for S/4HANA Cloud?

Not directly. Public cloud editions use different lifecycle tooling for extensions and configuration. The principles of testing, approval and evidence still apply.

If your change process is slow because evidence is gathered by hand, we can talk about collecting it automatically from your landscape.

Talk to an Expert Explore More Free Tools

Related Tools

SAP

More SAP tools

See all

SAP Transport Import and Go-Live Checklist for Production