SAP VC Sales Order UAT Script Template
Configurable materials fail in ways that standard sales orders do not: a value combination nobody tried, a missing price record or a BOM item with the wrong selection condition. A scripted UAT run with recorded inputs makes those defects reproducible.
Fill in
SAP Variant Configuration Sales Order UAT Script Template
Test header
Company: Acme Pumps Ltd Test case: VC-UAT-012 Material: PUMP-CONFIG-100 Scenario: Option with surcharge System: QAS / 200 Tester: S. Rao Date: 2026-10-20
Inputs
MOTOR_POWER = 22 kW SEAL_TYPE = Mechanical WETTED_MATERIAL = SS316 PAINT_COLOR = Special RAL
Expected result
Configuration is consistent, BOM explodes with the SS316 housing item, price includes four variant surcharges.
Steps and results
| Step | Action | Expected | Actual | Pass/Fail |
|---|---|---|---|---|
| 1 | Create sales order and enter configurable material | Configuration screen opens | ||
| 2 | Enter characteristic values | Only allowed values offered | ||
| 3 | Try an invalid combination | Message from dependency | ||
| 4 | Check configuration status | Complete and consistent | ||
| 5 | Open pricing analysis | Variant surcharges present | ||
| 6 | Check BOM explosion for the item | Correct items selected | ||
| 7 | Save order and record number | Order number returned |
Sign-off
Adapt the steps to your own materials. Record the sales order number and screenshots as evidence. Defects should be logged with the characteristic values used, because the same material can pass with one set and fail with another.
Test case generation
Optional help generating VC test combinations from your class data.
Optional. The tool and every export work without this. No spam.
How to use the script
Copy the template for each scenario. Fill the characteristic values you will enter and the expected outcome before you start. Run the steps in a quality system, record the actual results and mark pass or fail. Export to PDF as evidence for the project. Plan at least one run per option group and several for invalid combinations.
- Write expected results before running
- Record the order number of every run
- Test invalid combinations on purpose
- Repeat after each dependency or price change
What to test
A good VC test set covers four areas: allowed values and defaults, dependency messages for rejected combinations, the exploded BOM for the chosen options, and the price with all variant surcharges. Add a change test where the user changes a value after BOM explosion, because it exposes missing re-explosion or stale price.
Reading the results
A pass means all steps match expected values. A fail needs the exact characteristic values, the dependency or condition involved and a screenshot. Group failures: if many tests fail on one characteristic, the cause is likely in the class or dependency, not in the individual orders.
Common mistakes
Testers use only the happy path and miss invalid combinations. Others test in a client where dependencies are not released or where pricing records are missing. A frequent gap is not retesting after transports, so a fix in one object breaks another.
Frequently Asked Questions
How many VC test cases do I need?
It depends on the combinations. Cover every characteristic value at least once, every dependency rule with a passing and failing case, and the main price and BOM paths. Use risk to pick the rest.
Should I test in a production copy?
A quality system with current master data is best. A production copy gives realistic data but check that sensitive customer data is masked according to your policy.
What evidence do auditors want?
Typically the script, the actual results, the order number and screenshots or reports, signed by the tester and business owner. Keep them with the change record or release notes.
Can I automate VC testing?
Yes, with test automation tools or custom scripts that create orders with defined value sets. Start with the manual script to find the cases worth automating.
If you want help generating test combinations from your class and dependency data, we can build a read-only generator for your system.
Related Tools
SAP Variant Combination and Test Scope Calculator
Estimate the raw and valid number of variants for a configurable product and size a realistic sample for testing.
SAPSAP Variant Condition Pricing Worksheet
Plan variant condition surcharges per characteristic value before you load them into SAP pricing, and total the configured price for test cases.
SAPSAP Configuration Profile Setup Template
Document the configuration profile of a configurable material: class assignment, dependencies, BOM explosion level and the checks before release.
SAPSAP Variant Table Maintenance Worksheet
Lay out valid characteristic combinations for a variant table, with lead time and price class per row, before you maintain the table in SAP.