Businesswoman presenting Benchmarks on graphical screens

SAP Standard Application Benchmarks

SAP Standard Application Benchmarks help customers and partners find the appropriate hardware configuration for their IT solutions. Working in concert, SAP and our hardware partners developed the SAP Standard Application Benchmarks to test the hardware and database performance of SAP applications and components.

SAP quote-to-cash (Q2C) Benchmark

The SAP quote-to-cash (Q2C) benchmark was introduced in 2025 as a new Standard Application Benchmark as part of SAP’s Benchmark Portfolio. The Q2C-Benchmark is an SAP HANA only benchmark and is based on SAP S/4HANA 2021.

The Q2C OLTP scenario contains an order-to-cash component, including the credit limit check and the advanced ATP (Availability to promise) functionality. A fraction of 0.5% of the concurrent users execute an additional CDS query, which adds the OLAP component.

With the SAP Q2C benchmark SAP introduced an new advanced sizing metric (aSAPS - advanced SAPS) as the consequent evolution of SAPS .

The Q2C sizing metric aSAPS is derived from the SAP quote-to-cash Standard Application benchmark (Q2C), where 100 aSAPS is defined as 2,000 fully processed business order line items per hour in combination with the execution of two OLAP queries per hour.

It consists of the following transactions:

  • Execution of a CDS query to access data from ACDOCA. This CDS view provides access to all details of a journal entry item (database table ACDOCA) including the most important business entity, such as company code, G/L account, profit center, segment and many more. This query is executed by 0.5% of the benchmark users.
  • Create an order with five-line items. (VA01)
  • Create a delivery for this order. (VL01N)
  • Display the customer order. (VA03)
  • Post goods issue. (VL02N)
  • List 40 orders for one sold-to party. (VA05)
  • Create an invoice. (VF01)

Each benchmark user has his or her own master data, such as material, vendor, or customer master data to avoid data-locking situations.

  • 0. Logon
  • 1. Main screen
  • 2. Call /nVA05_AUART');
  • 3. First screen
  • 4. Second screen
  • 5. Call /n/Q2C/Q4 (Q2C Analytics)
  • 6. Fill screen and choose Execute
  • 7. Call /nVA01 (Create customer order)
  • 8. First screen
  • 9. Second screen (with five items)
  • 10. Choose Save
  • 11. Call /nVL01N (Create a delivery)
  • 12. First screen
  • 13. Choose Save
  • 14. Call /nVA03 (Display customer order)
  • 15. Choose Enter
  • 16. Call /nVL02N (Change delivery)
  • 17. Choose [F20] (Posts goods issue)
  • 18. Call /nVA05 (List orders)
  • 19. Choose Enter
  • 20. Call /nVF01 (Create invoice)
  • 21. Choose Save
  • 22. Call /nex

Use interaction steps 5 - 21 are repeated n times (17 user interaction steps --> min. 170 sec. duration).

Business aspect:

One loop (user interaction steps 5 - 21) corresponds to the selling of five items.

twitter pixeltwitter pixeltwitter pixeltwitter pixeltwitter pixeltwitter pixeltwitter pixeltwitter pixeltwitter pixeltwitter pixeltwitter pixeltwitter pixel