SAP - The Best-Run Businesses Run SAPGlobal

Home | Country Sites | Store | Log In | Create New Profile | Contact SAP


   

Skip Navigation

Industries

Solutions

SAP Business Suite

SAP BusinessObjects Portfolio

Executive View

Small & Midsize Companies

Standard Application Benchmarks

Benefits of Benchmark

Measuring in SAPS

Publications, Policy & Violations

Publications Archive

Services

Services By Role

Services by Subject

Services Portfolio

Education

Events

Platform

Service-Oriented Architecture

SAP NetWeaver

Ecosystem & Partners

Customers

Communities of Innovation

Partners

About SAP

Our Company

Our Vision for Business

SAP on Clarity

Sustainability at SAP

Corporate Governance

Corporate Social Responsibility

Investor Relations

Analyst Relations

SAP Newsroom

Corporate Videos

Stock Footage and Press Photos

Events


Your SAP.com resources
Subscriptions 
Saved Resources 
Save

Benchmark

Transaction Banking (TRBK)

The Transaction Banking (TRBK) Benchmark is divided into two business scenarios. The first scenario, day processing, reflects usage by users and integrated systems that generally occurs during the daytime. The second scenario, night processing, reflects account balancing that generally occurs overnight in batch mode.

This benchmark replaced the Bank Customer Accounts Benchmark.

Benchmark Results

Three-tier Internet configuration, Account Management 3.0, Deposits Management 4.0

Business Case Description of Day Processing

During the day processing scenario, the benchmark program simulates typical daily volumes of a retail bank, including the quantity of payment transaction operations received from external payment transaction systems, single real-time payment transactions received from ATM machines, real-time account statements, as well as the quantity of account information read from the system. The scenario was constructed to mirror a distribution of typical banking tasks. Since the usual integration into the bank IT infrastructure takes place via real-time interfaces (BAPIs) rather than SAPGUI, the simulation consists of a sequence of BAPI calls.

The following table shows in detail the sequence of all calls.

Day Processing: Steps in Detail

1. Create 30 postings in one call 9. Create 1 bank statement for account
2. Create 1 posting 10. Create 1 payment order
3. Create 1 bank statement for account 11. Read balances of account
4. Read postings for account 12. Create 1 posting
5. Read details of a posting 13. Create 1 bank statement for account
6. Create 1 posting 14. balances of account
7. Create 1 bank statement for account 15. Read account master data
8. Create 1 posting

In one loop a total of 35 postings are created in steps 1, 2, 6, 8, 10 (in this step one posting for sender part only), and 12.
The simulation works in such a way that a configurable amount of simulation agents simultaneously repeat the complete loop of all steps several times. During every loop, a set of 20 different accounts is accessed. This means that, as in real life, the system does not repeat operations on the same set of accounts.

Business Case Description of Night Processing

In the night processing scenario, account balancing is performed at regular intervals to settle an account. The benchmark simulates account balancing by calculating interest and charges for each account across 20 value date days. While the system triggers account balancing periodically, it is also possible to set the time periods manually.

During account balancing, the system performs the following tasks:


Want to learn more? Contact us or call the SAP sales office nearest you.

Investors |  Careers |  Inside Access |  Communities |  Using SAP.com |  Contact SAP
Copyright/Trademark |  Privacy |  Terms of Use |  Impressum |  Print View |  Full-Page View

Questions or comments about the Web site?
Contact the webmaster@sap.com.