# SAP SD Go-Live and Cutover Readiness Checklist > Source: https://netray.co/tools/sap-sd-go-live-cutover-checklist > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer A readiness checklist for sales and distribution cutover: data, configuration, interfaces, testing and hypercare. ## Category sap ## Erp SAP ECC / S/4HANA ## Audience - SAP SD consultant - Project manager - Cutover lead ## Tool **Kind:** checklist **Groups:** #### Master data and migration **Items:** **Text:** Customer master (business partners) loaded and reconciled for sales area, partner functions, payment terms and incoterms **Critical:** true **Text:** Material master sales views loaded: sales org, distribution channel, item category group, availability check, tax classification **Critical:** true **Text:** Condition records (prices, discounts, freight, taxes) loaded and spot checked against the legacy price lists **Critical:** true Customer material info records and output records migrated where used Open sales orders, contracts and scheduling agreements cut over with agreed rules on quantities already delivered Open deliveries and open billing items have a documented cutover decision per document **Text:** Migration reconciliation reports signed by business owners **Critical:** true #### Configuration and process **Items:** **Text:** Sales document types assigned to the sales areas, with item category and schedule line determination tested **Critical:** true **Text:** Pricing procedures determined correctly for each customer and document pricing procedure **Critical:** true **Text:** Copy control tested for every order, delivery and billing combination in scope **Critical:** true Delivery blocks, billing blocks and credit blocks tested including release authorization Availability check and requirements transfer tested with MRP **Text:** Revenue account determination tested for each material and customer account group **Critical:** true Output determination tested for order confirmation, delivery note and invoice, incl. print, email or EDI Returns, credit and debit memo processes tested end to end Incompletion procedures checked for each document type #### Integration, finance and security **Items:** **Text:** Billing documents post correctly to FI, including tax, with a test of cancellation **Critical:** true Goods issue posts the right stock and COGS entries **Text:** Interfaces for EDI, e-commerce, warehouse, tax and e-invoicing tested with realistic volume **Critical:** true Credit management data and credit limits loaded and tested **Text:** Roles and authorizations tested by role, with segregation of duties conflicts reviewed **Critical:** true Batch jobs for delivery due list, billing due list and output scheduled and documented **Text:** Number ranges for documents set in each client and aligned with the migrated numbers **Critical:** true #### Testing and training **Items:** **Text:** End to end order to cash scenarios passed in user acceptance testing with business sign off **Critical:** true Performance test of order entry, delivery creation and billing run done Key users trained, with work instructions for order entry, blocks, returns and billing **Text:** Defect list reviewed: no open severity one or two items without an agreed workaround **Critical:** true Dress rehearsal of cutover with timings recorded #### Cutover and hypercare **Items:** **Text:** Go/no-go criteria agreed and a decision owner named **Critical:** true **Text:** Rollback plan documented with the point of no return clearly marked **Critical:** true Legacy order entry frozen on an agreed time, with a process for orders in the gap Support rota for hypercare with contacts for each SD area Daily monitoring of blocked orders, failed output, failed billing and interface errors First month end close checked by finance with SD billing reconciliation **Scoring Note:** 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. ## Content **Intro:** 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. **Sections:** #### How to use the checklist **Body:** 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 **Body:** 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 **Body:** 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. **Cta:** 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. **Faq:** #### How should open sales orders be migrated in SAP? **Answer:** 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? **Answer:** 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? **Answer:** 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? **Answer:** 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. ## Search terms sap sd go live checklist, sap cutover checklist sales, sap sd cutover plan, sap open sales orders migration, sap sd hypercare checklist, sap go live readiness, sap sd uat checklist, s4hana sd cutover --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json