Facts about detection methods:
- Detection methods are used to search for irregularities in your data.
- Within detection methods, you can define a business logic that is used to determine if an incident, such as a claim, tax declaration, or a bank transfer, is a potential fraud. A detection method can be used in multiple detection strategies and can be used for online detection as well as for mass detection.
- A detection method represents a single executable step that detects fraud candidates in a given set of detection objects and assigns scores to them.
- Several detection methods can be sequentially applied on the same data set by grouping them with a detection strategy. The result of a detection method is independent from the result of any other detection method used within the strategy.
Since SAP BIS supports different types of detection methods, you can use the following algorithm to decide what kind of automated controls you need to use as a starting point.

The following types of detection methods can be created:
- Detection methods based on ABAP-managed database procedures
You can use ABAP-managed database procedures, which are created in the back-end system in ABAP and contain the SQLScript-logic that is executed in the SAP HANA database.
- Detection methods used for address screening
You can use detection methods to screen names and addresses in business data against provider-defined lists.
- Detection methods used for predictive detection
You can use your historical data to create detection methods that are based on a predictive model.
- Detection methods based on SQLScript procedures in the SAP HANA Repository
You can use SQLScript procedures which are defined in the SAP HANA Repository and contain the logic that is also executed in the SAP HANA database.
- Detection methods based on business rules
You can use detection methods which use either a text rule or decision table using HANA Rules Framework.
Note
Please note, that usage of detection methods based on the HANA Repository and HANA Rules Framework is not recommended. They remain in the solution for backward compatibility purposes only and are not to be used for any new implementations.
For this reason, they are not covered in this course.


