Oracle Applications 11.5.9 Workload
Oracle Applications 11.5.10 Workload

Workload Description
The Oracle Applications Standard Benchmark is focused on ERP applications and represents a mixed workload intended to model the most common transactions operating on the most widely used enterprise application modules. Definitions of transactions that compose the benchmark load were obtained through collaboration with functional consultants and are representative of typical customer workloads, with batch transactions representing 25% of the total workload.

To ensure that the benchmarks workload characteristics remain constant across a variety of user counts the concept of atomic user group has been defined. The atomic user group is the smallest number of users that can be added at any given time while still ensuring that the workload remains unchanged, specifically in terms of the percentages of each type of user in the mix. The atomic user group consists of the sum of all the base user counts specified in the table. To run more users you simply add an integer number of atomic groups, and thereby the characteristics of the workload remain constant.

For the eBS 11.5.10 benchmark, performance comparison(s) between benchmark kits of different sizes such as small, medium and large is not encouraged. By the same token, for benchmark kit of the same size, results comparison(s) between Single Instance versus RAC is also discouraged.

11.5.10 eBS Kit Workload

The EBS 11.5.10 Standard Benchmark supports three types of configurations : Small, Medium and Large. The volume of data loaded into Oracle Applications schema and the max number of users allowed for benchmark run depend upon the type of configuration selected.

The data should be loaded as per the data size specified here.

The throughput requirement for Order to Cash and Payroll batch processes is as follows.

Oracle Application 11.5.9 Benchmark

The eleven modules used by the Ebusiness 11.5.9 benchmark are:

	Oracle Financials: Payables (AP), Receivables (AR), General Ledger (GL), and Assets (FA)
	Supply Chain Management: Purchase Orders (PO), Order Entry (OE), and Inventory (Inv)
	Self Service : Internet Expenses, iProcurement, Employee Self Service and Self Service Time

A list of the transactions and their suggested completion rate is specified below in Table 1. The workload is composed of 18 Forms OLTP transactions, 4 transactions that explicitly submit requests for batch reports and 7 self-service transactions.

For a description of each transaction, please click on the transaction name in the left column.

Table 1: The 11.5.9 Atomic Group

Name of Transaction	Trans/HR/User	Base User Count
AP Enter Asset Invoice	6	4
AP Enter Inv Multi Dist	6	4
AP Invoice Dist Inquiry	7	8
AP Invoice Inquiry	7	6
AR Collections Report	4	2
AR Customer Summary	8	8
AR Insert Manual Invoice	6	3
AR View Customer Trans	6	4
FA Asset Inquiry	7	4
GL Account Inquiry	10	6
GL Journal Entry	8	8
INV Detail Report	4	2
INV Insert Misc Trans	9	8
INV View Item Attribs	8	6
INV View Item Cost	8	6
OE Detail Report	4	2
OE Insert Order	8	6
OE View Order	7	4
PO Detail Report	4	2
PO Enter Purchase Order	6	6
PO New Purchase Req	6	6
PO View Purchase Order	6	4
SS Enter Cash Expense Report	10	1
SS Enter Credit Card Expenses	10	1
SS Query Cash Expense Report	20	2
SS Enter TimeCard	10	2
SS View Employee Payslip	20	2
SS Enter Requisition	10	2
SS Query Requisition	20	2
Total	245	124

Batch Benchmark
The batch component of the Oracle Applications Standard Benchmark focuses on executing the core concurrent programs in the eBusiness Suite such as the High Volume Order Import program, which is part of the order to cash business flow. The batch benchmark is extremely useful in providing sizing and capacity planning information for the core Oracle Applications batch flows and concurrent programs.

High Volume Order Processing (HVOP)
The Release 11i Order Management HVOP benchmark focuses exclusively on meeting the high order volumes originating from the new electronic channels, such as consumer and business web sites, B2B exchanges, and EDI. The benchmark is designed to represent a core component of the order to cash business flow demonstrating the overall order processing throughput. Oracle Workflow, a high performance process control engine that guides sales order headers and lines through a series of consecutive steps from order creation through Shipping, controls order processing. The HVOP program processes orders by reading the rows from the Order Management Interface tables and converting the interface records into permanent Oracle Applications? order headers and their respective order lines. The orders are then booked and advanced to the shipping state.

Oracle Application 11.5.10 Benchmark

The modules used by the E-Business 11.5.10 benchmark are:

	Oracle Financials: Accounts Payable, Accounts Receivable, Fixed Assets, General Ledger
	Human Resource Management System
	Sales and Marketing
	Customer Support: Service
	Supply Chain Management (SCM): Logistics, Order Management, Purchasing, Shipping
	Self-Service Applications: Employee Self-Service, iExpenses, iProcurement, Oracle Time & Labor

A list of the transactions and their suggested completion rate is specified below in Table 2.

For a description of each transaction, please click on the transaction name in the left column.

Table 2: The 11.5.10 Atomic Group

Batch Benchmark

There are two batch processes included in the E-Business 11.5.10 benchmark, the HRMS-Payroll process and the Order to Cash batch process.

The HRMS-Payroll process involves the complete payroll process flow i.e. Payroll process, pre-payments, NACHA, archive, check writing, costing and transfer to GL and GL Autopost.

The Order to Cash process involves the entire flow from Order to Cash i.e. High Volume Order Processing (HVOP), Pick Release, Process Deliveries, Ship Confirm, Interface Trip Stop (ITS), Autoinvoice, Revenue Recognition, Transfer to GL and GL Autopost.

For a description of each of these processes, please click on the process name below:

HRMS-Payroll

Order to Cash

The batch benchmark is extremely useful in providing sizing and capacity planning information for the core Oracle Applications batch.