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, SAP Deposits Management (Banking Services Release 7.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
  • 2. Create 1 posting
  • 3. Create 1 bank statement for account
  • 4. Read postings for account
  • 5. Read details of a posting
  • 6. Create 1 posting
  • 7. Create 1 bank statement for account
  • 8. Create 1 posting
  • 9. Create 1 bank statement for account
  • 10. Create 1 payment order
  • 11. Read balances of account
  • 12. Create 1 posting
  • 13. Create 1 bank statement for account
  • 14. balances of account
  • 15. Read account master data

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:

  • Determines balances
  • Calculates balancing-dependent interest and charges in accordance with the conditions assigned to the account and updates on the respective account
  • Increases the balancing date stored in the account master to the next date
  • Forwards the interest to the component to calculate interest-based income tax for further processing
  • Adjusts balancing of previous periods, when necessary, if there were value dates in the past or postings in the former account to already balanced periods

Want to learn more?

Contact us or call the SAP sales office nearest you.