Procure-to-pay
A procure-to-pay test crosses purchasing, inventory and finance, and fails the moment a goods receipt or an invoice is missing. Synthesized copies or generates whole chains, from purchase requisition to payment run, and masks every supplier's contacts and bank details the same way everywhere.
The chain
| Step | Main tables in S/4HANA | What the test data needs |
|---|---|---|
| Supplier | BUT000, LFA1, LFB1, LFBK | A business partner with company code data, payment terms and bank details |
| Purchase requisition | EBAN | Requirements with materials, plants and the right release status |
| Purchase order | EKKO, EKPO | Orders with conditions and the purchase order history in EKBE |
| Goods receipt | MATDOC | Receipts against open order items, in the right plant and storage location |
| Supplier invoice | RBKP, RSEG | Invoices that match the order and the receipt, or deliberately don't |
| Payment run | REGUH, ACDOCA | Open items due for payment, with bank details in a valid format |
Your configuration may add more tables, including custom Z-tables.
Why it breaks
010203
04What Synthesized does
SubsettingKeeps chains wholeSubsets follow the purchase order history, so every order brings its receipts, invoices and payments.
MaskingMasks suppliersContacts and bank details are replaced, with IBANs that keep a valid format so payment runs still post.GenerationCreates exceptionsVariances, blocked invoices and partial deliveries, generated when production has none to hand.
ProvisioningResets for rerunsFresh open items for every automated run in Tosca or UiPath. See test automation.Supplier data
| Data | Example tables | Masked as |
|---|---|---|
| Names and addresses | LFA1, BUT000, ADRC | Realistic company names and addresses |
| Bank details | LFBK, BUT0BK | IBANs and account numbers in a valid format |
| Tax numbers | LFA1, DFKKBPTAXNUM | Valid-format tax numbers |
| Contacts | ADR6, ADR2 | Names, emails and phone numbers |
Procure-to-pay is one of the prebuilt SAP process templates, alongside order-to-cash and hire-to-retire. Extend it with your own steps and custom tables.
Validate procure-to-pay in 10 days
We've got you covered
The process from a purchase requisition to paying the supplier: requisition, purchase order, goods receipt, invoice verification and the payment run. In S/4HANA it spans purchasing, inventory management and finance.
Source-to-pay adds the steps before buying: sourcing, supplier selection and contracts, often in SAP Ariba. Procure-to-pay starts once there is something to order. Test data for both needs the same masked suppliers.
Requisitions in EBAN, purchase orders in EKKO and EKPO with their history in EKBE, goods movements in MATDOC, supplier invoices in RBKP and RSEG, payment runs in REGUH, and the accounting postings in ACDOCA.
Invoice verification checks the supplier invoice against the purchase order and the goods receipt. If quantities or prices differ beyond tolerance, the invoice is blocked for payment. Test data needs both matching and deliberately mismatched cases.
Yes. Supplier bank details are masked in a valid format, so payment runs and payment files work in test without pointing to any real account.
A supplier masked in S/4HANA keeps the same pseudonym in Ariba test systems. See how one policy covers SAP apps.
Yes. The same chain exists in ECC, with goods movements in MSEG and MKPF and postings in BSEG and BKPF.
Next step
We refresh one QA client with complete procure-to-pay chains for the company codes and plants you choose.
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.
