The Sales and Distribution (SD) Benchmark covers a sell-from-stock scenario, which includes the creation of a customer order with five line items and the corresponding delivery with subsequent goods movement and invoicing. It consists of the following transactions:
Each benchmark user has his or her own master data, such as material, vendor, or customer master data to avoid data-locking situations.
Important note: On January 1, 2009, the SAP SD Benchmark was updated. Alongside the upgrade to SAP Business Suite 7 and the SAP enhancement package 4 for SAP ERP 6.0, a number of additional, necessary updates were implemented. Business changes constantly, for example, Unicode and the use of the new general ledger are now common practice for SAP customers across all industries, and the SAP standard application benchmarks need to reflect this change. The updates are transparent; that is, the steps of the benchmark scenario remain unchanged. Please be aware that these changes make the SD benchmark more resource-intensive, which has a direct impact on the benchmark results.
Two-tier Internet configuration, SAP R/3 Releases 2.2 - 4.70, mySAP ERP 2004, SAP ERP 2005, and SAP enhancement package 4 for SAP ERP 6.0 › Three-tier Internet configuration, SAP R/3 Releases 2.2 - 4.70, mySAP ERP 2004, mySAP ERP 2005, and SAP enhancement package 4 for SAP ERP 6.0 ›
The SD-Parallel Benchmark consists of the same transactions and user interaction steps as the SD Benchmark. This means that the SD-Parallel Benchmark runs the same business processes as the SD Benchmark. The difference between the benchmarks is the technical data distribution.
It is generally accepted that data distribution can significantly influence the benchmark result in a parallel environment. Therefore, in May 1996, the SAP Benchmark Council redefined data distribution to establish a means to reproduce and compare results within parallel benchmarks. The additional rule is: Equally distribute the benchmark users across all database nodes for the used benchmark clients (round-robin-method).
Following this rule, all database nodes work on data of all clients. This avoids unrealistic configurations such as having only one client per database node. From a theoretical point of view, the rule yields comparable and reproducible parallel benchmarks.
The SAP Benchmark Council agreed to give the parallel benchmark a different name so that the difference can be easily recognized by any interested parties – customers, prospects, and analysts. The naming convention is SD-Parallel for Sales & Distribution - Parallel.
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.
User interaction steps 2 - 16 are repeated n times (15 user interaction steps --> min. 150 sec. duration).
One run (user interaction steps 2 - 16) corresponds to the selling of five items.