# SAP Transport Import and Go-Live Checklist for Production > Source: https://netray.co/tools/sap-transport-go-live-checklist > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer A checklist for importing transports into production, covering approvals, sequence, testing, timing and rollback. ## Category sap ## Erp SAP ECC / S/4HANA ## Audience - Basis administrator - ABAP developer - Release manager ## Tool **Kind:** checklist **Scoring Note:** Every critical item must be checked before importing to production. If a critical item is open, delay the import or document an approved exception. **Groups:** #### Before release **Items:** **Text:** Request contains only objects for one change ticket **Critical:** true **Text:** Peer code review completed and comments closed **Critical:** true **Text:** Code Inspector or ABAP Test Cockpit run with no unresolved errors **Critical:** true Unit tests and manual test cases recorded as passed Authorization checks present in custom code and roles updated No debug breakpoints, hard-coded users or test data in the code Dependent transports and customizing identified and ordered #### QA validation **Items:** **Text:** Request imported to the quality system in the agreed order **Critical:** true **Text:** Business tester signed off with evidence attached **Critical:** true Regression test of related processes completed Interfaces tested with a representative file or message Performance checked with realistic data volumes Background job definitions and variants prepared if needed #### Approval and planning **Items:** **Text:** Change approval recorded by the change owner or board **Critical:** true Import window agreed and users informed Basis confirmed that the import queue holds no unrelated requests Rollback or correction plan written, including who decides Support team briefed on what changed and what to watch #### Production import **Items:** **Text:** Import order confirmed in STMS against the plan **Critical:** true **Text:** Import return code checked and any warnings read **Critical:** true Generation or activation errors checked after import Smoke test run by the owner immediately after import Related jobs, authorizations and number ranges verified #### After import **Items:** **Text:** Ticket updated with import date and result **Critical:** true Transport log updated Monitoring of dumps (ST22) and logs (SM21) for first business day Lessons from any incident recorded for the next release ## Content **Intro:** Most production incidents from SAP changes come from process gaps, not from clever bugs: missing dependencies, untested requests and imports in the wrong order. This checklist walks through the controls before, during and after a transport import. **Sections:** #### How to use the checklist **Body:** 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. **Bullets:** - 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 **Body:** 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 **Body:** 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. **Bullets:** - Emergency changes with no review afterwards - Mixed-purpose requests - Testing with developer authorizations - No rollback plan **Cta:** If your change process is slow because evidence is gathered by hand, we can talk about collecting it automatically from your landscape. **Faq:** #### Does SAP have its own tooling for this? **Answer:** 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? **Answer:** 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? **Answer:** 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? **Answer:** Not directly. Public cloud editions use different lifecycle tooling for extensions and configuration. The principles of testing, approval and evidence still apply. ## Search terms sap transport import checklist, sap production transport checklist, sap go-live checklist abap, stms import checklist, sap change release checklist, sap transport approval process --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json