# SAP PP Test Scenarios: Test Script Worksheet for Production Planning > Source: https://netray.co/tools/sap-pp-test-scenarios-test-script-template > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer Editable SAP PP test script sheet covering master data, MRP, production order, confirmation, goods movements and settlement, ready to export to Excel. ## Category sap ## Erp SAP S/4HANA ## Industry Discrete Manufacturing ## Audience - SAP PP consultant - Test lead - Key user ## Tool **Kind:** worksheet **Mode:** editable **Columns:** #### Test ID **Key:** id **Type:** text #### Process area **Key:** area **Type:** select **Options:** - Master data - Planning - Order execution - Confirmation - Goods movement - Settlement - Reporting #### Scenario **Key:** scenario **Type:** text #### Transaction **Key:** tcode **Type:** text #### Test data **Key:** data **Type:** text #### Expected result **Key:** expected **Type:** text #### Actual result **Key:** actual **Type:** text #### Status **Key:** status **Type:** select **Options:** - Not run - Passed - Failed - Blocked #### Tester **Key:** tester **Type:** text **Rows:** **Id:** PP-01 **Area:** Master data **Scenario:** Create multi-level BOM for finished good **Tcode:** CS01 **Data:** Plant 1000, usage 1, material FG-100 with 4 components **Expected:** BOM saved, explosion shows all levels and correct quantities **Status:** Not run **Id:** PP-02 **Area:** Master data **Scenario:** Create routing with 3 operations and work centers **Tcode:** CA01 / CR01 **Data:** Work center WC-MILL, WC-ASSY; standard values set **Expected:** Routing saved, status released, operation times present **Status:** Not run **Id:** PP-03 **Area:** Planning **Scenario:** Run MRP for single item and check planned order **Tcode:** MD03 / MD04 **Data:** FG-100 with independent requirement of 100 EA **Expected:** Planned order created, dependent requirements on components **Status:** Not run **Id:** PP-04 **Area:** Order execution **Scenario:** Convert planned order to production order **Tcode:** MD04 / CO40 **Data:** Planned order from PP-03 **Expected:** Production order created, BOM and routing copied, costs planned **Status:** Not run **Id:** PP-05 **Area:** Order execution **Scenario:** Release production order and check availability **Tcode:** CO02 **Data:** Order from PP-04 **Expected:** Status REL, components available or shortage shown **Status:** Not run **Id:** PP-06 **Area:** Goods movement **Scenario:** Issue components to order (movement 261) **Tcode:** MIGO **Data:** Order from PP-05 **Expected:** Material document posted, order actual cost updated **Status:** Not run **Id:** PP-07 **Area:** Confirmation **Scenario:** Confirm final operation with yield and scrap **Tcode:** CO11N **Data:** Yield 98, scrap 2, activity hours entered **Expected:** Confirmation saved, operation status CNF, activity cost posted **Status:** Not run **Id:** PP-08 **Area:** Goods movement **Scenario:** Goods receipt for order (movement 101) **Tcode:** MIGO **Data:** Quantity 98 EA to storage location 0001 **Expected:** Stock increased, order delivered quantity updated **Status:** Not run **Id:** PP-09 **Area:** Settlement **Scenario:** TECO order and settle variances **Tcode:** CO02 / CO88 **Data:** Order from PP-08, settlement rule to material **Expected:** Order settled, variance posted, status SETL **Status:** Not run **Totals:** #### Test cases **Key:** id **Agg:** count **Notes:** Add one row per variant: make-to-order, repetitive, subcontracting, split lot, backflush. Set the Status column as you execute, then export to Excel for the UAT sign-off pack. Transaction codes shown are common SAP ECC and S/4HANA codes; confirm Fiori app equivalents in your release. ## Content **Intro:** SAP PP testing proves that the chain from master data to settlement works with your data, not just SAP demo data. This worksheet gives you the standard scenario list, test data prompts and expected results so you can run unit, integration and user acceptance tests and export the evidence to Excel. **Sections:** #### How to use this test script sheet **Body:** Start with the nine pre-filled rows, which follow the natural order of a production order: create BOM and routing, plan with MRP, convert to a production order, release, issue components, confirm, receive the goods and settle. Replace the test data column with your own materials, plants and work centers. Add rows for each variant your plant runs, then assign a tester per row and record actual results and status as you go. Export to Excel for sign-off. **Bullets:** - One row per testable outcome, not per screen - Write the expected result before running the test - Keep material documents and order numbers in the Actual result column as evidence - Re-run failed rows after each fix and keep the history #### What a complete SAP PP test cycle covers **Body:** Unit tests check one function, such as a BOM explosion or a routing release. Integration tests follow a document chain across modules, for example MRP creating a purchase requisition in MM, goods issue posting to FI and settlement to CO. User acceptance tests are run by key users with their own data and confirm that the process matches the business blueprint. Add negative tests: a component shortage at release, a confirmation exceeding order quantity, a missing routing, a blocked material. #### Typical defects found in PP testing **Body:** Most failures trace back to master data rather than program errors. Look for missing MRP views, wrong procurement type or special procurement key, unreleased routings, work centers without cost center links, and scheduling margin keys that push dates unexpectedly. Backflush settings in the routing or material master explain many unexpected goods issue postings. Settlement failures usually come from a missing settlement profile or allocation structure on the order type. **Bullets:** - MRP does not plan the item: check MRP type and the plant status - Order will not release: check missing components, status or authorization - Confirmation posts no activity: check the control key and standard value keys - Settlement errors: check the settlement rule and the allocation structure **Cta:** If you want these scenarios run automatically against a sandbox client, Netray can build a private agent that executes the transaction steps and records results, on your own servers. **Faq:** #### What are the main SAP PP test scenarios? **Answer:** The core scenarios are BOM and routing creation, MRP run, planned order conversion, order release, component issue, confirmation, goods receipt and order settlement. Add variants for make-to-order, repetitive manufacturing, subcontracting, co-products and rework based on what your plants run. #### How many test cases does an SAP PP project need? **Answer:** It depends on variants and plants. A single-plant discrete implementation often needs 60 to 150 cases across unit, integration and UAT. Count the process variants and organizational units, then multiply by the happy path plus the key exception paths. #### Who should execute SAP PP user acceptance tests? **Answer:** Key users from planning, production, warehouse and costing should run UAT with real materials and work centers. Consultants support them but should not execute the tests, otherwise gaps in training and process understanding stay hidden until go-live. #### Can I use this for S/4HANA Fiori apps? **Answer:** Yes. Keep the process steps and expected results, and replace or add the Fiori app name in the Transaction column. Many GUI codes such as CO02 and CO11N still exist in S/4HANA, but your release may favor a Fiori app. ## Search terms sap pp test scenarios, sap pp testing, sap pp test script template, sap pp uat test cases, sap production planning test cases excel, sap pp end to end test scenario, sap pp integration testing, sap pp order to settlement test --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json