SAP Deposits Management

Content

1. Purpose

2. Prerequisites

   2.1. Master Data and Organizational Data

   2.2. Preliminary Steps

   2.3. Roles    

3. Process Overview Table

4. Process Steps

   4.1. Transaction History Analysis in Dashboard

5. Appendix

   5.1. Optional Process Steps

   5.2.  Frequently Asked Questions (Optional)  

If you would like to become an SAP Hana Admin certified professional, then visit Tekslate - A Global online training platform:"SAP Hana Admin training and certification course". This course will help you to achieve excellence in this domain.

SAP Deposits Management  Transaction History Analysis with SAP HANA

1.Purpose

This document describes business process activities using the model for SAP Deposits Management Transaction History with SAP HANA in a logical sequence.

The Scenario includes the following process step:

  • Transaction history analysis by a bank-internal employee in SAP Business Objects Dashboards
  • The target groups for this document are SAP customers and consultants with no or little knowledge of the SAP Deposits Management concept and features.

Content target groups for this scenario are banks and financial institutes, particularly the departments within these, which are responsible for the managing, holding, and maintaining of bank accounts, consumer loans, and payment transactions.  

2. Prerequisites

Before you can use this business process, you must ensure the following connections have been set up:

  • Banking services from SAP Deposits Management (DSP DM) and SAP HANA TM system
  • SAP HANA TM system and SAP Business Objects Dashboards

For more information, see the quick guide for the SAP Deposits Management rapid-deployment solution for transaction history with SAP HANA, which is attached to the SAP Note 1626730. The following objects are used for reporting on the SAP Deposits Management transaction history:

SAP Business Objects Dashboard SAP_FS_TB_Deposits_SpendAnalysis.xlf

 2.1. Master Data and Organizational Data

The master data and organizational structure which includes the data required for the Rapid- Deployment solution model of your company are directly created in your SAP Deposits Management system.

  Screenshot_2

The data and structure for a business partner, current account, and reference account are created in the backend system. The organizational structure reflects the structure of your company regarding specific settings such as company name or house currency. The SAP Deposits Management data is replicated to the SAP HANA database.  

2.2. Preliminary Steps

The transaction data and required master data are replicated to the SAP HANA database.

2.3. Roles

No business roles are included in the delivery of the solution. However, the processes described below are modeled for particular users:

UserDescription
BankerBank internal employee, for example, call-center operative, customer adviser, who analyzes the transaction history of customer accounts
Technical Expert(optional)The technical expert verifies the proper replication of newly created data in the SAP HANA Studio 9this role is optional). See the Appendix of this document.

3. Process Overview Table

The following summary describes the relevant process steps:                                              

Business  Role       

Transaction History  Payment     

Transaction

Transaction History is Analysis in transaction analyzed in Dashboard

Business   Code 

A dashboard report is by banker displayed in Dashboard

Verify data in SAP                  

Data replication           

Expected Results condition                

The postings are HANA from SAP replicated and available Deposits in SAP HANA Management to SAP HANA system is set up  

4. Process Steps

4.1 Transaction History Analysis in Dashboard

Use: In this step, a dashboard displays banking users’ transactions for a period of up to two years. All data is filtered to the specific user when the dashboard is launched. This solution allows access to specific account transactions in real-time (that is, seconds). The dashboard structure is as follows:

  • The dashboard shows up to two years of payment transactions, selected details, and charting of debits and credits by day or month.
  • The first tab page, Transaction History, is sown by default. The account holder’s name is displayed and a list of the account holder’s accounts is available for selection a dropdown list. When the user selects an account, the current balance is displayed. The main body of the dashboard shows a list of transactions for the selected time frame.
  • The second tab page, Spend Analysis, retains the transaction type and time period from Transaction History. The dashboard displays a bar chart of the total in and out transactions by month. Changes can be made to the filter selections on this tab page.

Both pages include the following elements:

The top area has a dropdown list of user accounts, the account holder’s name and current balance for the selected account.

The filter is containing:

  • Search text box
  • Transaction Type (B/C/AII), Legend: D=debit, C=credit
  • From Ito dates

Prerequisites: The banker requires access and the necessary authorizations to display the account data and payment transaction data in the SAP Business Objects Dashboard. The transaction data for the account holder’s bank accounts are recorded in the SAP Deposits Management backend system and has been replicated to the SAP HANA database.

Check Out SAP Business Objects Explorer

Procedure

Log on to the dashboard:

The dashboard can be accessed directly from the BI launch pad, for example, for testing purposes. This procedure is described in the appendix in the Access the Dashboard SAP FS TB Spend Analysis Fin Directly from the BI Launch Pad chapter.

Dashboard:SAP_FS_TB_SpendAnalysisFin

From the Account Selection dropdown list, select an account.

The user and partner are passed from the online banking scenario and only those accounts are available in the dropdown list.

The current balance is displayed, and the current data displayed in the form and to date fields.

Choose the dates and select a date in the past.

Choose Apply.

The Apply button is only required when changing the information in the filter area.

The matching transactions for the time frame are listed in the main body of the display. By default, it is sorted by the date posted.

To find, sort, filter or retrieve additional details, choose the respective heading column

To display, for example, the recipient of a specific payment, choose the corresponding item line.

The recipient bank account of the item is displayed in the Transaction Details panel.

The transactions with the same description for six months prior to the selected item are displayed in the similar Transactions for Prior 6 Months panel.

Choose the Spend Analysis tab page.

The From and to dates are retained as the month and year.

choose to apply to display a bar chart of the total in and out transactions by month.

Hover the mouse over any element in the chart to display the detail for the balance

For more details on transactions in a particular month, choose the bar. The Account Activity and Amount per Category panels are populated for the selected month.

A trend over days of the month selected is displayed in the Account Activity panel

The transaction amount by category for the month selected is displayed in the Amount per Category panel

5. Appendix

5.1. Optional Process Steps

5.1.1. Access the Dashboard SAP_FS_TB_SpendAnalysisFin Directly from the Bi LaunchPad

Use: The dashboard SAP_FS_TB_SpendAnalysisFin can be accessed directly from the BI launch pad. The is no method that an end-user would be expected to carry out to access the dashboard, but it is useful for internal purposes, for example, for testing.

Procedure

Access SAP Business Objects Explorer through the following address the BI launchpad:

URLhttps://<server>:<sport>/BOE?BI

 <server> is the server for the SAP Business Objects system, and <port> is the port for the web application server.

  • Input your username and password and choose Log On.
  • Choose the Documents tab page.
  • In Folders, choose Public Folders  SAP, SAP.FS, SAP.FS.TB.
  • In Details, choose the dashboard:

Dashboard:SAP_FS_TB_SpendAnalysisFin

5.1.2. Verify Data in SAP HANA Studio (Optional)

Use: Master data and postings in the result data layer can be verified and checked via the SAP HANA Studio after the replication to SAP HANA. This activity can be carried out by the technical expert, an optional role which is included in the Roles Chapter.  

Prerequisites SAP HANA Studio must be installed on the client-side in order to access the data.

Procedure

  • To open your SAP HANA Studio, choose Start  All Programs  SAP HANA Studio.
  • In the Navigator panel, open the folder Content.
  • Open the folder sap.
  • Open the folder fs.
  • Open the folder tab.
  • Choose the respective Calculation Views / Analytic Views folder or Attribute Views folder.
  • Right-click the respective view (for example CA_BALANCE) and choose Data Preview,
  • Verify the replicated data by filtering according to the relevant object.

Result: Master data and postings in the Result Data Layer and verified and checked is SAP HANA Studio.

5.2. Frequently Asked Questions (Optional)

Q: Which SAP Deposits Managements tables are used in the transaction history analysis?

A: The following tables are used in the schema SAP_FS_TB as the data source for the views in the package sap.fs.ta:

TablesDescription
BCA_ACCTBALAccount Balance
BCA_CNSP_ACCTAssignment Table: Account Contract Specialization
BCA_CN_LINKAssignment Table: Contract Parts to a Contract
BCA_CN_PURPOSEContract Element: contract Purpose
BCA_CONTRACTAssignment Table: Contact Purpose
BCA_PAYMITEMPayment Items
BCA_PAYMITEM_NTPayment Notes of a payment item
BUTOOOBP: Customer General data
FSPR_PRODUCT_YProduct, Master Data
SVERSSAP Release
TOOOClients
TCURNQuotations
TCURRExchange Rates
TCURVExchange rate types for currency translation
DD01LDomains
Dd02lSAP Tables
Dd03lTable Fields
Dd04lData elements
Dd06lPool/cluster structures
Dd07lR/3 DD: values for the domains
Dd07tDD: Texts for Domain Fixed Values (Language-Dependent)

SAP Best Practices            

SAP HANA 1.0

January 2012

English