No results found

Your search did not match any results.

We suggest you try the following to help find what you’re looking for:

  • Check the spelling of your keyword search.
  • Use synonyms for the keyword you typed, for example, try “application” instead of “software.”
  • Try one of the popular searches shown below.
  • Start a new search.
Trending Questions

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.

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 R12 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.

Oracle Application R12 Benchmark

The EBS R12 Standard Benchmark supports four types of configurations: Small, Medium, Large and Extra-Large. The volume of data loaded into Oracle Applications schema is one of two sizes for Release 12.0.4 and only one size for Release 12.1.2. The batch workload and the maximum number of users allowed for benchmark run depend upon the type of configuration selected.

Category Order to Cash Payroll Number of Users
Small 10,000 lines/Hr 5,000 Employees/Hr 1 – 1000
Medium 50,000 lines/Hr 10,000 Employees/Hr 1100 – 3000
Large 100,000 lines/Hr 50,000 Employees/Hr 3100 – 10000
Extra-Large 250,000 lines/Hr 250,000 Employees/H 10100 -20000
XX-Large 750,000 lines/Hr NA NA

Prior to Release 12.1.2, there were 'Medium' and 'Extra-Large' kits available to cover the Small/Medium and Large/Extra-Large workloads. With Release 12.1.2, there is a single 'Extra-Large' kit available to cover all workloads. Thus the data setup is the same for all sizes; with only the number of users, or the number of lines or employees processed varying with the model size.

Application Business Objects Row Counts / Extra-Large
TCA Organizations 1,100,000
  Contacts 4,900,000
  Contact Points 3,700,000
  Account 1,100,000
  Account Sites 1,090,000
  Account Site Uses 2,180,000
Contracts Contracts 222,000
IB Instances 1,300,000
IB Items Items 5
Items Reservable 1,100,000
Managers   800
Employees   250,000
Payroll Users   250,000
Self Service Employees   40,000
Users   20,000
Credit Card Entries   4,000,000
Supplier   10,000
Asset Categories   900
GL Code Combinations   93,000

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

  • Oracle Financials: Accounts Payable, Accounts Receivable, Fixed Assets, General Ledger
  • Human Resource Management System
  • 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 3.

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

Table 3: The R12 Atomic Group


Also new to R12, partners can execute individual flows from the complete atomic group. This offers more combinations of running users and may address business case situations that are of interest to particular partners.

Table 4: The R12 OLTP Flows

OLTP Flow Transaction Transactions Percentage Users (X-L)  
Order Management Flow   6 14% 2,800  
  Insert Order   28.56% 800 Forms
  Pick Release   14.28% 400 Forms
  OM Ship Order   14.28% 400 Forms
Manual Invoice
  14.28% 400 Forms
  AR Customer Summary   14.28% 400 Web
  OM Order Summary Report   14.28% 400 Forms
Procurement-to-Pay Flow   6 12% 2,400  
  SS Create Query Req.   16.6% 400 Web
  Create Approve PO   16.6% 400 Web
  View Purchase Order   16.6% 400 Web
  Create Payables Invoice   16.6% 400 Forms
  View Payables Invoice   16.6% 400 Forms
  Printed PO Report   16.6% 400 Forms
Customer Service Flow


  3 40% 8,000  
  Create Service Request   40% 3,200 Forms
  Update Service Request   40% 3,200 Forms
  Close Service Request   20% 1,600 Web
HR Self-Service Flow   4 20% 4,000  
  Create Query Cash Expense   20% 800 Web
  Create Query Credit Expense   20% 800 Web
  View Payslip   30% 1,200 Web
  Create Timecard   30% 1,200 Web
Financials Flow   7 14% 2,800  
  AR View Cust. Transaction   14.28% 400 Web
  FA Create & Query Asset   14.28% 400 Forms
  GL Journal Entry   14.28% 400 Forms
  INV View Item Attributes   14.28% 400 Forms
  INV Insert Misc. Transactions   14.28% 400 Forms
  AR Aging Report   14.28% 400 Forms
  Min/Max Inventory Report   14.28% 400 Forms
Totals:   26 100% 20,000  

R12 Functional Updates from 11.5.10

There are several changes and modifications in the R12 E-Business Benchmark Kit that reflect changes from Release 11i

Four online transactions have changed from Forms based (11i) to Web based (R12). They are:

1. AR View Customer Transactions
2. AR Customer Summary (ARCS)
3. PO Create Approve Purchase Order (SS)
4. PO View Purchase Order (SS)

Due to changes in R12 application the following batch processes are now capable of being multi-threaded for better performance. In addition, the SUBMITO2C.SQL script has been modified to incorporate this change.

1. Pick release
2. Pick confirm date
3. Create Accounting

With changes to the R12.1.2 kit, the following batch processes are now capable of being multi-threaded for better performance.
1. Auto Invoice
2. Revenue Recognition


When running the R12.1.3 kit at the X-L user count, it may improve performance to slightly adjust the specific transaction user counts and pacing from the first transaction to the last transaction along the business flow to insure that certain queues have ample entries.

Table 5: The R12 OLTP Dependency by Flows

Business Flow Order Management iProcurement Customer Service
1. Start OM_Insert_Order Create_Query_Requisition Create_Service_Request
2. OM_Pick_Release Create_Approve_PO  
3. OM_Ship_Confirm View_PO Update_Service_Request
4. Insert_Manual_Invoice Create_Payables_Invoice  
5. End OM_Order_Summary View_Payables_Invoice Close_Service_Request