on 07-24-2017 3:25 PM
Dear Community,
Together with my team, I am developing and implementing strategies for fraud detection using SAP Fraud Managment. We encounter a problem passing our detection results from the back-end (SAP HANA Studio) to the front-end (SAP Fiori) and could not make progress in solving it.
Consider the following situation:
Our interest lies on a table of transactions (Detection Object):
TRANS_ID (KEY) | CLIENT_ID | ATRIBUTE_1 | ATRIBUTE_2 ....etc
1 | A | xxx | xxx
2 | B | xxx | xxx
3 | B | xxx | xxx
Now we apply our detection methods (Procedures: SELE, EXEC), resulting in a table with the same structure but only containing fraudulent transactions.
Here the problem Begins: In the SAP Fiori front end, we would like to group the resulting fraudulent transactions in respect to the CLIENTS_ID. This is, we want to generate a list of clients (CLIENTS_ID), that are connected to at least one fraudulent transaction (TRANS_ID) and the ability to connect additional information of those transactions like:
CLIENT_ID | TRANS_ID (KEY) | ATRIBUTE_1 | ATRIBUTE_2 ....etc
A ------------------------------------------------------------------------------------
1 | xxx | xxx
B ------------------------------------------------------------------------------------
2 | xxx | xxx
3 | xxx | xxx
We failed to define the investigation object. We want the CLIENTS_ID as the hierarchical top ID, but in our list of transactions, it is inevitably not unique and therefore leading to an error because of duplicates . On the other side, If we aggregate on CLIENT_ID to make it unique, we lose important information about our transactions.
Is it possible to display the results in the desired way in the front-end?
If yes, how we need to define the key ID's of investigation and detection object to achieve the desired result?
User | Count |
---|---|
88 | |
10 | |
10 | |
9 | |
7 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.