Financials CO-OM, CO-PC, FI-GL
Logistics MM-IM, LE-WM, LO-VC, CS, SD-BIL, SD-SHP, SD-SLS, PP-BD, PP-ATO
Basis BC-BMT, BC-SRV
Human resources PD-OM
Cross application CA-CL

Published results of the ATO Benchmark contain throughput numbers; for example 2,500 assembly orders per hour. An assembly order is a request to assemble pre-manufactured parts and assemblies to finished products based to an existing sales order.

• 0. Logon
• 1. Main screen
• 2. Call /nVA01 (create customer order)
• 3. Enter order and organizational data
• 4. Enter customer and material
• 5. First level characteristic value assignment
• 6. Second level characteristic value assignment
• 7. Second level characteristic value assignment
• 8. Choose Back (Control of resulting price)
• 9. Choose Save (Create assembly order)
• 10. Call /nMFBF (Repetitive Manufacturing backflush)
• 11. Enter sales order data
• 12. Choose Save
• 13. Call /nVL01N (Create outbound delivery)
• 14. Select sales order
• 15. Choose Save
• 16. Call /nLT03 (create transfer order)
• 17. Save transfer order
• 18. Call /nLT12 (confirm transfer order)
• 19. Confirm transfer
• 20. Call /nSO01 (SAP office - inbox)
• 21. Select workflow-item
• 22. Start goods issue via workflow
• 23. Call /nVF01 (create invoice)
• 24. Choose Save invoice
• 25. Call /nend
• 26. Confirm log off

User interaction steps 2 - 24 are repeated n times (23 user interaction steps --> min. 230 sec. duration).

Business aspect:
One run corresponds to the full assemble-to-order scenario for one item.

• 0. Logon
• 1. Call transaction CAC2
• 2. Sort employees
• 3. Choose four employees (scroll down once)
• 4. Choose Create time data
• 5. Enter time data and choose Return
• 6. Choose Save
• 7. Choose Sort
• 8. Select another employee
• 9. Call help requests for cost center
• 10. Select cost center
• 11. Call help request for internal order
• 12. Select internal order
• 13. Enter new time data and choose Return
• 14. Choose Save
• 15. Choose Sort
• 16. Select five employees
• 17. Change data
• 18. Choose Last page
• 19. Select last line
• 20. Select all
• 21. Choose Delete
• 22. Choose Save
• 23. Log off

Business aspect:
One run corresponds to the processing of 80 activity reports for 5 employees

• 0. Logon
• 1. Main screen
• 2. Call Post Document
• 3. Create customer item
• 4. Create general ledger account item
• 5. Choose Post
• 6. Call Display document
• 7. Enter previous posted document
• 8. Double-click first line
• 9. Call Customer line item display
• 10. Enter data and choose Execute
• 11. Select first line
• 12. Call Post incoming payments
• 13. Enter header data
• 14. Choose Process open items
• 15. Select item 5 of the list
• 16. Scroll down to the end
• 17. Select last item
• 18. Deactivate all selected items
• 19. Choose Post
• 20. Call /nend
• 21. Confirm log off

While the procedure for this report is complex, the following features can provide insight into its underlying business processes. Starting with the personal number and the payroll period, the report runs through these transactions in the German payroll program:

• Basic data
• Last payroll results
• Capital formation
• Company pension plan
• Net payments/deductions and transfers
• Final processing

The benchmark run has the following procedure:

• 1. Two users log on to the system.
• 2. The first user resets the data.
• 3. When the high-load phase of the run has come to an end (when the first batch process has come to an end), the first user logs off.
• 4. The second user waits until all processes have finished and then triggers the evaluation before logging off.

• 0. Logon
• 1. Main screen
• 2. Call /nME51N (Create purchase requisition)
• 3. Enter data
• 4. Choose Post
• 5. Call /nME21N (Create purchase order)
• 6. Enter data
• 7. Choose Post
• 8. Call /nMIGO (Goods receipt purchase order)
• 9. Enter data
• 10. Choose Execute
• 11. Choose Post
• 12. Call /nMIRO (Create invoice), enter company code
• 13. Enter basic data
• 14. Choose Payment
• 15. Enter data
• 16. Choose Post
• 17. Call /nend
• 18. Confirm log off

• 0. Logon
• 1. Main screen
• 2. Call Create production order
• 3. Enter general data
• 4. Enter data
• 5. Choose Save
• 6. Call Change production order
• 7. Enter order number, choose Return
• 8. Change data
• 9. Select order
• 10. Choose Functions
• 11. Choose Release
• 12. Choose Order
• 13. Choose Print
• 14. Choose OK
• 15. Choose Save
• 16. Call Create completion confirmation
• 17. Enter data
• 18. Choose Save
• 19. Call Create completion confirmation
• 20. Enter data
• 21. Choose Save
• 22. Call Create goods receipt
• 23. Enter data
• 24. Copy data
• 25. Choose Save
• 26. Call Change production order
• 27. Choose Environment
• 28. Choose Individual processing
• 29. Enter data and choose execute
• 30. Call /nend
• 31. Confirm log off

Parallel benchmarks depend on the additional parameter "data distribution," which, by definition, does not exist in single database benchmarks. All tests show that the scalability of parallel databases significantly depends on the data distribution. When you compare SD Benchmark with SD-Parallel Benchmark results, you have to remember this difference.

• 0. Logon
• 1. Main screen
• 2. Call /nVA01 (Create customer order)
• 3. First screen
• 4. Second screen (with five items)
• 5. Choose Save
• 6. Call /nVL01N (Create a delivery)
• 7. First screen
• 8. Choose Save
• 9. Call /nVA03 (Display customer order)
• 10. Choose Enter
• 11. Call /nVL02n (Change delivery)
• 12. Choose [F20] (Posts goods issue)
• 13. Call /nVA05 (List orders)
• 14. Choose Enter
• 15. Call /nVF01 (Create invoice)
• 16. Choose Save
• 17. Call /nend
• 18. Confirm log off

User interaction steps 2 - 16 are repeated n times (15 user interaction steps --> min. 150 sec. duration).

Business aspect:
One run (user interaction steps 2 - 16) corresponds to the selling of five items.