Hierarchy
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ VEI (Package) Application development R/3 foreign trade
Basic Data
Data Element | SLLKA |
Short Description | Min. length of a key word from address of Sanct. Party List |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | DEC2 | |
Data Type | DEC | Counter or amount field with comma and sign |
Length | 2 | |
Decimal Places | 0 | |
Output Length | 2 | |
Value Table |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | ||
Default Component name | ||
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | Addr.: KW |
Medium | 15 | Addr.: Lgth KW |
Long | 20 | Addr.: Length key w. |
Heading | 40 | Addresses: Min. length of key words |
Documentation
Definition
In this field, you can define the minimum length of generated search terms. The smaller you define this value, the more search terms the system generates. The bigger you define this value, the smaller the number of search terms.
In general, the following rule applies:
a) Small value ==> many search terms ==> high hit rate during the check
against the Sanctioned Party List
BUT: high system load, that is, longer runtime of SLS (Sanctioned Party List Screening) check
b) High value ==> fewer search terms ==> lower hit rate during the check
against the Sanctioned Party List
BUT: lower system load, that is, shorter runtime of SLS check
Note
The runtime as well as the value for the minimum length of search terms depends on the number of SLS entries and the number of partner master records to be checked.
To ensure that your SLS check if efficient, carry out some test runs of the SLS check with different values for the minimum length of search terms. You should then select the value for which the SLS check runs fastest.
History
Last changed by/on | SAP | 19990827 |
SAP Release Created in |