SAP SD Go-Live and Cutover Readiness Checklist
SD is where cutover mistakes get noticed first, because a wrong price, block or invoice reaches customers within hours. This checklist covers the sales and distribution items that should be confirmed before go-live and during hypercare.
0 of 34 items complete
16 critical items still open - these are the highest-risk gaps.
Master data and migration
Configuration and process
Integration, finance and security
Testing and training
Cutover and hypercare
Every critical item must be checked before go-live. If any critical item is open, record an owner, a workaround and an explicit risk acceptance by the business, or move the date.
Cutover plan second opinion
Optional: a short independent review of your SD cutover plan and hypercare monitoring.
Optional. The tool and every export work without this. No spam.
How to use the checklist
Work through the groups with the SD lead, the business process owners and finance. Tick items only when someone has seen evidence, such as a test case result or a reconciliation report. Items marked critical block go-live until they are checked, or until a named owner accepts the risk in writing. Export the result to PDF or Excel for the go/no-go meeting.
Where SD cutovers usually fail
The recurring failures are open order migration, copy control gaps, pricing records with wrong validity dates, and account determination that is missing for a combination. Open orders are hard because the business must decide what happens to partly delivered documents. Pricing fails when old price lists contain overlapping validity. Test with real customers and materials, not clean demo data.
Hypercare routine
In the first weeks, check daily for blocked orders, billing documents blocked for accounting in VFX3, failed output and EDI errors. Keep a list of issues by cause, so a single fix can close many tickets. Ask finance to reconcile SD billing to FI at the first period end, since this catches account determination errors that individual tests miss.
Frequently Asked Questions
How should open sales orders be migrated in SAP?
Agree rules with the business first: which orders are in scope, how partly delivered quantities are handled, and how prices are treated, as copied or repriced. Then load with a migration tool, reconcile quantities and values, and run a test delivery and billing on a sample.
What are the main SD tests before go-live?
End to end order to cash for each order type, pricing for key customers, blocks and release, returns and credit memos, output and EDI, and the FI postings from billing. Add authorization tests by role and a volume test for billing runs.
What is hypercare in an SAP project?
Hypercare is the period after go-live, often two to six weeks, with extra support and daily issue triage. For SD it focuses on blocked orders, billing errors, output, interfaces and the first period end reconciliation with finance.
Who should sign off the SD go-live?
The business process owners for sales, logistics and billing, plus finance for the postings, and the project manager. IT should confirm technical readiness. The decision owner should be named in the go/no-go criteria before the meeting.
If you want an independent second look at your cutover plan, or a read-only way to monitor blocks and failures after go-live, Netray can help. Ask for a review.
Related Tools
SAP Order-to-Cash (SD) Health Assessment
Eight questions that score how well your SAP SD order to cash design and operation hold up, with recommendations by band.
SAPSAP SD Configuration Transactions and IMG Reference
Find the SAP SD customizing transaction for a setting, with the table it maintains and the question it answers.
SAPSAP SD Transaction Codes Reference
A searchable list of common SAP sales and distribution transaction codes, grouped by process area, for daily use and onboarding.
SAPSAP SD Tables Reference (VBAK, VBAP, LIKP, VBRK and More)
Lookup of the main SAP SD tables with their key fields and what changed in S/4HANA. Search, then export to Excel or PDF.
More SAP tools
See all- SAP Sales Document Types Reference
- SAP Pricing Procedure Design Worksheet
- SAP Item Category Determination Reference
- SAP Delivery Block Reasons Template
- SAP Credit Management Checklist
- SAP Output Determination Checklist
- SAP Billing Types Reference
- SAP Incompletion Log Checklist
- SAP SD Pricing Condition Types Reference (PR00, K004, MWST)
Keep exploring
Free tools
- SAP PP Go-Live Master Data and Cutover ChecklistA tick-box readiness check for production planning go-live, covering master data, configuration, cutover and support.
- SAP PM Go-Live Readiness ChecklistA checklist to test whether your SAP PM implementation or rollout is ready to go live, grouped by master data, configuration, planning, access and cutover.
- SAP QM Go-Live and Cutover ChecklistA checklist of what to confirm before switching on SAP Quality Management: master data, integration, authorizations, migration and hypercare.
Guides
- ERP Go-Live Readiness Assessment ChecklistValidate ERP go-live readiness with a 100-point checklist covering data, integrations, training, cutover, and support. Prevent post-go-live emergencies.
- ERP Cutover Planning Best PracticesPlan and execute a flawless ERP cutover with rehearsal strategies, task sequencing, and rollback procedures. Minimize downtime and operational disruption.
AI on your ERP
- AI for SAP S/4HANA Sales and Distribution (SD) That Explains Orders, Pricing and BlocksAI for SAP S/4HANA SD: order status, delivery and billing blocks, pricing explanations and credit holds in plain English. Read-only, on-prem option.
- Is Your ERP Ready for AI? A Readiness Assessment ChecklistIs your ERP actually ready for AI? A practical checklist covering master data quality, access and permissions, GPU sizing, and governance before you fund a pilot.