Order-to-cash

SAP order-to-cash test data, with every document in the chain

An order-to-cash test touches sales, logistics and finance, and fails if any document in the chain is missing. Synthesized copies or generates whole chains, from sales order to cleared payment, with each customer masked the same way in SAP and the CRM.

Order-to-cash chain, kept wholeExample
Sales order
Sales
VBAK 0000451209
Delivery and goods issue
Logistics
LIKP 0080016533
Billing document
Sales
VBRK 0090023117
Journal entry
Finance
ACDOCA 5100000874
Incoming payment
Finance
Cleared
Customer 100231 appears in every document as Berg Handels GmbH, a masked name.
Chain kept whole
Masked once, everywhere
Built for the SAP & Enterprise QA toolchain
SAP S/4HANASAP AribaSAP HANASalesforceUiPathTricentis

The chain

Every step depends on the one before it

CustomerBUT000 · KNA1
Sales orderVBAK · VBAP
DeliveryLIKP · MATDOC
BillingVBRK · VBRP
Journal entryACDOCA
ClearingACDOCA
CRMSame masked name
Data warehouseSame values
Synthesized keeps every chain whole and masks each customer once, everywhere
Document flow · VBFA
An order-to-cash subset keeps every document from customer to clearing. Customer 100231 is masked once and reused everywhere.
StepMain tables in S/4HANAWhat the test data needs
CustomerBUT000, KNA1, KNVVA business partner with sales area data and a credit limit
Sales orderVBAK, VBAPPrices and availability that match your configuration
Delivery and goods issueLIKP, LIPS, MATDOCStock in the right plant and storage location
BillingVBRK, VBRPBilling documents linked to their deliveries in the document flow, VBFA
AccountingACDOCAJournal entries and open items for the customer
Payment and clearingACDOCAOpen items to clear, with amounts that match

Your configuration may add more tables, including custom Z-tables.

Why it breaks

Why order-to-cash tests fail on data

01
Broken chainsA subset that keeps orders but drops their deliveries leaves the test with nothing to bill.
02
Used-up documentsA delivery can be goods-issued once. Every rerun needs a fresh one.
03
Missing statesTests need customers on credit hold and materials out of stock, which production rarely has on demand.
04
Mismatched systemsThe CRM shows a different customer name from SAP, so the integration test fails.

Platform

Subset whole chains, mask them, generate what's missing

Find and mask personal data

A scan flags personal data in SAP tables and the systems around them, then masking replaces it with realistic values, the same way everywhere.

  • Sensitive columns found by the scan, including Z-tables
  • Same replacement values in SAP and the CRM
  • A record of every run
Automated masking with a sensitive data scan report

Copy only what your tests need

Choose company codes, date ranges or business objects, and the subset keeps every related record so tests still run end to end.

  • Business keys and date ranges in scope
  • Document chains kept whole
  • Smaller, faster test systems
Automated subsetting with system statistics

Create the data production doesn't have

Generate customers, orders and edge cases for scenarios production doesn't contain yet, configured as code or in the UI.

  • Edge cases on request
  • Configuration as YAML or in the UI
  • Runs from the API, CLI or a pipeline
Automated generation configured as YAML

What Synthesized does

Whole chains, masked the same way everywhere

SubsettingKeeps chains wholeSubsets follow the document flow, so every order brings its deliveries, invoices and postings.
MaskingMasks consistentlyA customer's masked name is the same in SAP, the CRM and the data warehouse.
GenerationCreates missing statesCustomers on credit hold or orders for blocked materials, when production has none.
ProvisioningResets for rerunsFresh chains for each automated run in Tosca or UiPath. See test automation.

Order-to-cash is where to start

It's the most developed of our SAP process templates and the process most SAP test packs cover first. Procure-to-pay and hire-to-retire are prebuilt too, and you can extend any template with your own steps.

Validate order-to-cash in 10 days

SAP process templates

Order-to-cash
Available today
Procure-to-pay
Prebuilt template · Procure-to-pay test data
Hire-to-retire
Prebuilt template
Your own processes
Extend a template or build your own

We've got you covered

Questions about order-to-cash data

What is the SAP document flow?

The links between the documents in a sales process, stored in table VBFA: each sales order points to its deliveries, and each delivery to its billing documents. Transaction VA03 shows the flow for a sales order.

Which tables hold order-to-cash data in S/4HANA?

Sales orders in VBAK and VBAP, deliveries in LIKP and LIPS, goods movements in MATDOC, billing documents in VBRK and VBRP, the document flow in VBFA, and the accounting postings in ACDOCA.

Does it work on SAP ECC?

The same chain exists in ECC, with postings in BSEG and BKPF instead of ACDOCA.

What about pricing conditions and configuration?

Configuration such as pricing conditions comes from your system. The subset keeps references to it intact.

Which customers end up in the subset?

You choose by company code, sales organisation, date range or business object, and the chain for each selected document comes with it.

Next step

See an order-to-cash refresh on your system

We refresh one QA client with complete order-to-cash chains for the company codes you choose.

Runs in your environmentNothing installed in SAPRead-only access to SAPSecurity and deployment
Updated October 2026

SAP, S/4HANA, SAP HANA, SuccessFactors, Ariba, Concur and other SAP products and services mentioned herein, as well as their respective logos, are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names mentioned are the trademarks of their respective companies.