Sanctioned Party List Screening with SAP HANA Search

In a previous blog we discussed Sanctioned Party List screening with HANA Search and gave a configuration overview. In this blog we’d like to delve into more details and examples of how SPL with SAP HANA Search can be applied in real world scenarios. 

Comparison of SPL Screening in SAP GTS 10 and GTS 11

While both options can work for you, you may want to take advantage of some benefits of screening with SAP HANA search.

• Simplified Configuration
• Ease of Operation
• Improved Results
• Performance Improvements
• Ad-Hoc Analytic Capabilities

In this post we will focus on how Simplified Configuration can be applied in real world examples.

Simplified Configuration

With SAP GTS 10.0 and 10.1, the SPL Screening enables 15+ customizable settings and while it is flexible, it does require additional knowledge.

SPL with SAP GTS on HANA simplifies testing and setup and improves implementation time. SPL with SAP GTS 11.0 on HANA commonly uses SAP HANA Fuzzy Search algorithm and is simplified to four search parameters to control SPL engine.

Existing Sanctioned Party List screening with SAP GTS 10.0 and 10.1

SAP GTS 11.0 with Sanctioned Party List on HANA

As mentioned, a previous blog discussed configuring SPL with HANA. Setting up Sanctioned Party List Screening with HANA is much simpler and requires fewer steps. Without getting into the setup details, there are a few search parameters which should be defined when using SAP HANA Search.

SAP HANA Search Parameters

In an effort to emphasize and demonstrate the benefits of SAP HANA Search, we will outline some examples using SAP HANA Search Parameter options.

Number of Packages:

To get better performance for SAP HANA Search, you can select proper number of packages to execute SAP HANA Search on multi-core CPUs in parallel in accordance with hardware configuration.

Search Pattern:

Defines which address element(s) will be involved in comparison by SAP HANA Search. Instead of the flexible address elements checking rules in SAP GTS search and SAP TREX search, SAP HANA Search pre-defines 4 patterns which contain the most frequently used address elements to achieve better performance.

• Screen Name and Country
  To get a hit, both the name and country in the addresses must match the respective elements in the sanctioned party lists.
• Screen Name Only
  To get a hit, only the name in the addresses must match the respective element in the sanctioned party lists.
• Screen Name, Country, and Street Address
  To get a hit, the name, the country and the street address in the addresses must match the respective elements in the sanctioned party lists.
• Screen Name, Country, City, and Street Address
  To get a hit, the name, the country, the city and the street address in the addresses must match the respective elements in the sanctioned party lists.

Exactness:

Defines the level of error tolerance for single search term for SAP HANA Search

Example

• An exactness of 70% will match “Jose” to “Jase”.
• An exactness of 90% will not match “Jose” to “Jase”.

Minimum Score:

Defines the minimum score the whole content of address element in business partner address and document partner address to be compared has to reach

Example

• A minimum score of 50% will produce “Tomas Meyer” as a hit for “Thomas Mayer”.
• A minimum score of 100% will not produce a hit.

Percentage Rate of Matching Words:

Defines the percentage of matched search terms in business partner address or document partner address

Example

• A percentage rate of matching words of 66% will produce “Jose Maria Sison” as a hit for “Jose Maria”.
• A percentage rate of matching words of 80% will not produce a hit.

Symmetric Search:

Activates symmetric search will also use the number of matched terms in SPL entity to calculate “Percentage Rate of Term Matches’. If any percentage calculated from SPL entity and business partner address/document partner address meets the threshold, they system recognize the result as a hit. With this option, more hits will be produced.

Example

You decide to check whether a business partner with the name “Jose Maria Sison” is listed in the sanctioned-party list. The sanctioned party list contains an entry for “Jose Maria” and 70% has been defined in Customizing as percentage rate of matching words.

• If you have not selected the Symmetric Search checkbox, the system only uses the number of words in business partner name to calculate the matching percentage rate.
  In this case, the matching percentage rate is calculated as follows:
  2 divided by 3 = 66.67%. Hence, the name is not treated as a hit.
• If you selected the checkbox, the system uses both the number of words in business partner name as well as the sanctioned-party name when calculating the matching percentage rate.
  In this case, the matching percentage rate for the sanctioned party list is calculated as follows:
  2 divided by 2 = 100%. Hence, the name is treated as a hit.